In this article, we will understand the concept of File Content Conversion in SAP PI using an example of a comma-separated text file as source. File Content Conversion helps in converting the file formats to/from XML.
Here we will understand how to use File Content Conversion (FCC) in sender & receiver file adapter.
File Content Conversion in Sender Adapter
Let’s say we have a simple CSV (Comma-separated values) file something like the one shown in the below figure. It contains employee details.
The figure below shows a typical configuration for the sender adapter.
Channel Parameters
Document Name and namespace indicate the message type used (from the Integration Repository). Recordset Name specifies the name of the root node that should be created while generating the corresponding XML. This should be in sync with the message structure in the Integration Repository. If you don’t specify this, PI creates a default root node called Recordset.
In Recordset Structure you specify the substructure and its occurrence. In our case ‘Emp,*’ indicates that node Emp can occur any number of times within the root node.
Three mandatory parameters that must be provided are –
- <node>.fieldSeparator – can be a comma for a CSV file or any other separator. You can specify the hex code here, e.g. for a tab-separated file, you could provide ‘0x09’ (including quotes).
- <node> .endSeparator – signifies the end of a record, ‘nl’ (including quotes) indicates a new line character.
- <node> .fieldNames – list of field names in each record.
For an exhaustive list of parameters available for record set structure please go through this link.
File Content Conversion in Receiver Adapter
Assume you have XML content as generated by the sender adapter above and are required to generate a tab-separated file (as shown in the below figure) at the receiver end. File Content Conversion comes in handy here.
Specify the Recordset Structure giving the list of nodes including the root and substructure that needs to be read.
The mandatory parameters are –
<node>.fieldSeparator and <node>.endSeparator. The description is the same as in the sender adapter.
For an exhaustive list of parameters available for record set structure please go through this link.
For complete scenario refer to the blog File to IDOC Scenario in SAP PI 7.31 (AEX- Java Only)