XI - BPM Scenario using Fork and correlation



The container elements are the variables used in BPM. We cannot use directly the abstract interfaces. So we need container elements.


The Receive step is used to receive messages. Here we are having two input messages, so we need to have two receive steps. We will two receive steps in Fork. You use a fork This graphic is explained in the accompanying text) when you want to continue a process in branches that are independent of each other, for example, to communicate with two systems that are independent of each other. The branches of the fork join in a union operator.

You can specify the required number of branches and then define whether the process must run through all branches, or just a particular number of branches. Furthermore, you can define an end condition for the fork


A correlation enables you to identify objects that belong together, for example, a quotation and the relevant sales order. This involves correlating the objects by using one or more common elements, for example, the quotation number. When you define a Workflow, you can specify the object that the Workflow must wait for, without having to enter the ID of the object.

You define a correlation with the correlation editor.  In the correlation editor, first you need to define the correlation name. Then Mention the container elements under correlation container. There you have to give the common field which is having in both the input files. Select the input messages interfaces in the involved messages. In the properties you need to mention the value. Select the value from the expression editor.

Defining a Correlation 



Below is the expression editor. You need to select the Xpath for the two input messages.(for File1 and File2)



Receive Step1                                    


Receive Step2

Transformation Step

If you want to collect messages, split messages you need to use Transformation step after the receive step that refers to N: 1 Interface Mapping or 1: N Interface Mapping created.

Send Step

Once messages are received and processed, these processed messages are to send by the BPM using Send Step.

Save all the objects and activate it. Integration Repository part completed.

Click here to continue...


Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image