File Content Conversion In Sap Pi At Receiver
Dear SAP Community Member, In order to fully benefit from what. Basic File Adapter Content Conversion. This is a very simple way of importing flat files into PI. Dear SAP Community Member, In order to fully benefit. Message Protocol: File content conversion specify the source directory and the file. I'm reading a flat file using receiver file adapter in PI 7.5, and then converting it to xml using FCC. However, I need to save the file name to an element of the resulting XML after conversion, to later pass that value to a RFC. The Receiver File Adapter is configured, using the following settings: Choose File Content Conversion as the Message Protocol. You may or may not give the ‘addHeaderLine’ parameter.
Launch This is certainly a simple overview of content conversion making use of the file adapter. Situation This is usually a basic asynchronous Document to File scenario. A toned file is deposited on a local FTP machine; it'beds go through by a Marketing communications Channel, transformed to XML, mappéd to an inbóund XML record and sent back again to the FTP machine I'm heading to generate two Information Varieties, two Communications Forms, two Information Interfaces and a one Interface Mapping.
The flat file is usually being go through by a File Adapter so I'll want to configure 'Content material Transformation' on the sender marketing communications route. Input/Result The insight file consists of a checklist of workers and their prior employers as demonstrated below. Make sure you be aware that the first two rows are for reference point only and received't become incorporated when testing. The information are assembled by worker, the first record being the header.
Each Header Report includes a key, employee number, first name, current employer and cell phone number. Following rows contain detail records. The detail records hold the worker's earlier employers and organization locations. The initial character will be the essential industry, 'H' for header and 'Chemical' for details. I've thought that the information are provided in the correct sequence - one header report, an limitless number of fine detail records, implemented by another header report and therefore on.
Design 1) The initial data kind will hold the outbound file (toned file) once it's been recently obtained by PI. You need to be conscious that the Sender Marketing communications Channel 'Articles Conversion' settings has recommendations to elements within this XML document so they require to become an precise go with. The second data type will include the inbound fiIe. I've tidiéd it up á little, the 'essential' offers been fell and the prior employers sit underneath the worker record. 2) Create two Information Sorts. 3) Generate an outbound asynchronous Message User interface that sources the level file Information Kind and an inbound asynchronous Information User interface that sources the XML Information Type. Create a individual User interface Mapping and a individual Message Mapping.
Map as required. Settings 1) The pursuing objects are needed. Sender communications station. Sender Contract. Receiver Determination. Interface Determination. Receiver Agreement.
Receiver Marketing communications Approach I'm heading to focus on the Sender Conversation Route as the rest of the configuration is definitely straightforward. When producing the Marketing communications Approach select 'File Content Transformation' as the message process. Configure the Document or FTP server details as needed and click on the 'Content Transformation' tabs.
OK, right now we can concentrate on the 'Content Transformation' variables which are proven below. Name: The title of the XML framework getting the document. This is usually will be the Outbound Information Type. Namespace: Namespace óf the Outbound Message Type. Counter: Number of outlines to become disregarded at the beginning of the document. Name: Title of the recordset structure. Namespace: Namespace to end up being appended to the record structure.
Framework: The title of substructurés within the óutbound record followed by the quantity of occasions the substructures take place. signifies an unknown amount of substructures. Series: The help documentation is definitely a confusing when explaining series. I've still left this as Ascending on the presumption that the information within the Outbound file is certainly formatted correctly and appears in ascending purchase. If anyone can supply a detailed explanation of this paraméter it would become valued.
Per Message: Quantity of recordsets that should be incorporated in the information. If this quantity is surpassed another message is made. Key. Field Name: Name of the key field within the file. Field Kind: I left this as string and didn'testosterone levels notice any reason why it should be changed.
Right now we can proceed on to the Recordset variables. This is certainly the where I inform PI how to locate the substructures, the components contained within them and the industry measures. Each parameter is usually prefixed with the title of the element it relates to. All of this provides to be typed in therefore double check everything before you trigger the item.
As you noticed previous I possess two recordset substructurés, Header and Fine detail. The guidelines I utilized are demonstrated below. FieldNames - These names match to the elements within the óutbound XML.
FieldFixedLengths - Thé size of each field. It is certainly suspected that each field begins after the earlier field. KeyFieldValue - The worth contained within the crucial field. In this instance the important values are 'L' for header and 'Deb' for details.
ProcessConfiguration - I'meters not sure why I used this parameter ór where I got it from. If anyone can supply some details or a link to the appropriate help record it would be appreciated. The adhering to screen shot displays the connection between the 'Content Conversion' parameters and the input file. For example the header line contains 5 elements. Essential, EmpID, Name, Firm and Telephone.
The essential is indicated by 'L' in column one and will end up being one character very long. EmpID will end up being eight figures lengthy and starts in column two and therefore on. This is certainly a little choice of the accessible recordset parameters. More detailed info can end up being found on SAP Assist. Testing Right now its just a case of placing the outbound fiIe in the suitable directory site on your FTP server.
Make certain the file has the correct filename. In my situation the Sender Communications Channel bank checks for documents every 60 secs. Once the file provides been learn it't aged to another directory. You won't notice any content convérsion in SXMBMONI só I presume this is certainly done within the adapter (please correct if I'm wrong).
Overview This is usually a very simple method of importing flat data files into PI. The just troubles I experienced were with the 'Content Conversion' variables. With a little test and error I handled to get it working. I'd advise obtaining yourself a good text manager as this helped me when creating the content conversion.
Receiver File Content Conversion In Sap Pi Step By Step
Situation: This situation represents the measures involved in settings of the réceiver file adaptér with file contént conversion. File Content Conversion Scenario Insight Message: This can be the insight information to the réceiver file adapter delivered from XI. Input XML information Output Information: Fig3. Result CSV Message Ways: XI transmits a XML message as insight to the receiver adapter.Right now this XML desires to become transformed to a File in CSV file format, i.age. It may end up being a comma separated, tab divided etc.
To generate the needed output, the information kind at the receivert side performs a crucial guideline. The data kind should abide to the guidelines of well produced XML. The Recipient File Adapter is certainly configured, making use of the following settings:. Choose Document Content Conversion as the Message Protocol.
You may or may not really provide the addHeaderLine paraméter. For the fieIdSeparator parameter you require to provide field separator for both checklist and substructure (referring to the data type above). For ég: it may end up being a , (comma) for substructure in a comma divided file. The endSeparator parameter demands to given for substructure only. For eg: it may end up being a nl (brand-new collection). Fig4.
Sap Modules List
Conversion Variables in Adapter. Provide the file name, the directory website and the Construction setting. Activate all the configurations.
Receiver File Adapter with N.C.G. Encyclopedia of general knowledge by jahangir success series pdf. Is configured.
Outcome: The file with desired output produced. Recommended Reading.