PI 7.11 introduced a new Java adapter user-module which can translate between flat IDoc formatted messages and IDoc-XML formatted messages. In this blog, we will take a look at how we can use PI to integrate directly with our external business partners through flat IDoc formatted messages. Conversely, when we receive messages from our external business partners, they are also often in flat IDoc format.

The IDocs would be sent in flat IDoc format to our business partner. Map the id attribute in the target with the globalCounter function.When we exchange messages with our external business partners, IDocs are often used. The variable used to store the count is a global variable and is incremented every time a node is found in the source structure (irrespective of the node name).Ĭreate one-to-one message mapping between source message and the intermediate message. The id attribute is mapped using a user defined function globalCounter which records the order in which the nodes appear in the source structure. We have achieved this by adding id attributes to each of the nodes as shown below. Hence, we need to create an intermediate message type which will establish a relationship between the parent and child nodes. Node2 and Node3, or Node3 and Node4) which we could use to determine corresponding parent node for each child node. Note that there is no common element between parent and child nodes (e.g. Our aim is to convert the above flat structure to a nested shown below – Figure below shows the flat XML structure generated by the file adapter using file content conversion. We will then use two-step message mapping to convert the flat XML to a nested XML. Click the image on the right to see an enlarged view. Hence we will use a two step message mapping to attain the required result.įirst, we will use file content conversion as shown to covert the incoming file to flat XML structure as supported by the adapter. Node4 – Occurs 0.unbounded and repeats under the preceding Node3ĭue to limitation of the standard File adapter, it is not possible to directly convert the incoming file to the deeply nested target structure. Node3 – Occurs 0.unbounded and repeats under the preceding Node2 Lets say we have an incoming flat file with structure as described below –Īnd the target structure is as shown below – William had a similar requirement, and we came up with a generic solution which is described below. This article provides a workaround to accomplish the same thing by using only the graphical mapping. Converting incoming file to deeply nested structures would require use of either custom developed adapter modules or third-party conversion agents.

Standard File Content Conversion allows you to convert the incoming file to flat XML structures only i.e. Many a times, you are required to convert flat file structures to deeply nested structures like IDocs.

Sap idoc flat file format