File content conversion in sap pi at receiver how to#

In this blog, we will see how to convert flat file to XML file when file structure is bit complex. Description: File Content Conversion is used to convert non-XML file (flat file) to XML file and vice-versa. Sender and receiver BS doesn't have a LS name By Punit J, YASH PI Competency Team, Yash Technologies.ATTRIBUTE_INV_SND_SERV or unable to convert sender service to an ALE Logical system.There may be a problem in File Content Conversion Parameters.The only problems I encountered were with the 'Content Conversion' parameters.

This is a very simple way of importing flat files into PI. You won't see any content conversion in SXMBMONI so I assume this is done within the adapter (please correct if I'm wrong). This problem could be the file structure length, DT lengths in IR are not same. Once the file has been read it's archived to another directory.File is picked up successfully but not getting converted into xml format.Check if the adapter status is active in Sender File CC.Check if the given source file location path and source file name is same in sender CC.File is not getting picked up from the source.Here I am presenting some commonly occurred errors in file-idoc scenario Find out why using the error mentioned in the IDoc monitoring. If the IDoc exists, does it have status 03? If not, the IDoc was not sent to PI. Check the error message to find out why the IDoc was not sent to PI.Д¬an you find the IDoc in the IDoc monitor (transaction we02/we05/вЂ¦) in SAP ECC? If not, the IDoc was never generated and therefore never received at the other end of the line. Use the RWB to find further evidence of problems.Д¬an you find the IDoc in transaction idx5 in SAP PI? And is it without errors?Д¬an you find an entry in the transactional RFC monitor in SAP ECC (transaction SM58)? If so, this indicates a communication failure between ECC and PI. In this case the poblem lies in PI, the receiver of the message or the communication between the two. Can you find the message in the runtime workbench? If you can, find out whether it really did not reach the receiver and, if so, why.