Skip to Content

Step by Step multiple idocs to file 2


Step 6.10 :
Same as NOM1 we have to add receive and container operation for NOM2 and NOM3 also.

For NOM2: Receive2 and Container2
For NOM3: Receive3 and Container3

As shown in figure below we find three branches in our fork and each branch is collecting NOM1, NOM2 and NOM3 IDOCs respectively for the time interval which we have specified in our deadline branch.

Step 6.11 :
Till now we have done everything to collect our IDOCs in our BPM. Once IDOCs are collected after the specified time interval (2 minutes in our case) a transformation step is required to convert the N collected IDOCs into one.

Add a TRANSFORMATION step in the BPM. This step is for the N:1 conversion. Our BPM will look like:

Set the Properties of TRANSFORMATION as follows:
Interface Mapping property is place where we specify our Interface mapping which will convert our N collected IDOCs into one. In our paradigm as soon as we select our Interface Mapping program we will get the three different source messages in our Source Messages property (In interface mapping program we have three input Abstract Data).We then fill this value into CollectNOM1List , CollectNOM2List, CollectNOM3List for NOM1, NOM2, NOM3 IDOCs respectively.
These Lists are output of Container Operations of Block.

In Third property of transformation we specify the Target Messages . Here we set it as TargetFile which is of Abstract Target Type as shown in figure below.

Step 6.12 :

Once we complete the N:1 transformation of data a SEND step follows. This is as stated in the figure below

We set the Property of Send as follows:
Set the Message property as TargetFile which is of Abstract type of output file and output of our N:1 transformation step as shown in figure below.

That is what we nedd to do in BPM,remaining is Configuration that is same and can be done.


1 Comment
You must be Logged on to comment or reply to a post.