XI - Inter Company Stock Transfer Order between 2 SAP systems achieved by designing a BPM

By Venkata Narayana Marella, YASH PI Competency Core Team, Yash Technologies

Business Scenario:

Inter Company Stock Transfer Order between 2 SAP systems achieved by designing a BPM   

 When a Purchase Order in the System A is created, then the output type NEU is triggered to generate the IDOC and Post it to System B.

In System B, Sales Order is created for Corresponding Purchase Order in System B. As this Sales Order is rush order, it would create delivery automatically and would then generate another IDOC and send back to System A. 

Some settings would be required in R/3 (Business system) before sending to other system. 

Mappings:

Purchase Order to Sales Order:

Map the customer number, Customer material, Sales organization, Distribution channel and division in the enhancement EXIT_SAPLVEDA_001 in source system and to pass the PO number in delivery note IDOC the exit EXIT_SAPLV56K_002 in target system are used, below are the segments used to map the required data. 

E1EDK14 – Sale area

E1EDP01 – Item data

E1EDK02 – Purchase order and date

E1EDP19 – Material identification 

This is achieved by designing BPM in XI and following steps illustrate how to achieve it.

BPM

A business process is an aggregation of operations performed by people and software systems containing the information used in the process, along with the applicable business rules.

BPM Sync/Async  

With this exercise we will be able to model a 'Sync/Asyn' pattern using BPM and apply it to IDOC communication. 

The requirement is to receive the PO from system A and send it to System B in synchronous mode. And receive the Delivery notification from System B and send it back to the System A as response using the BPM Sync/Async.  

Communication between a synchronous and an asynchronous business system: 

Ø       Create business process management “IP_STO_PO_OR_Sync_Async”

Ø       Create container variables

Ø       DELIDOC (Abstract interface, MI_DEL_ABS)

Ø       POIDOC (Abstract interface, MI_PO_ABS 

Create correlation object ‘ID’ with the messages MI_DEL_ABS, MI_PO_ABS with the fields /ORDERS05/IDOC/E1EDK01/BELNR from PO and /DELVRY03/IDOC/E1EDL20/XABLN from Delivery. 

Switch to the Graphical design editor and design the BPM by dragging the required steps and filling the properties. 

Ø       You can only define one sync/async bridge per integration process.  

Ø       Synchronous receive (Opening Receive): Receives the Request message from the synchronous business system and opens the sync/async bridge. The receive step must be the first in the IP. In the receive step you specify the synchronous interface receiving the message from the synchronous business system. The IP is started when the message is received. The message type of the message to be received and the request message from the synchronous interface must be identical. 

This step receives the PO IDOC and opens the bridge. Give the properties as shown below: 

Ø       Asynchronous Send: Sends the received request message asynchronously to the asynchronous business system.     

Send step: This step sends the received PO IDOC asynchronously and uses the correlation 

Ø       Asynchronous Receive: Receives the response message from the synchronous business system.

Receive step: This step receives the Delivery IDOC asynchronously by using the   correlation.       

Ø       Synchronous Send: Sends the response message from the asynchronous business system synchronously to the synchronous business system and closed the Sync/asynch Bridge.

 This step sends the Delivery IDOC and closes the sync bridge         

Ø       Block Step: This is required to define the exception and handle the exception. Here exception is required as Synchronous Receive message (PO) is different from the Synchronous Send Message (delivery).  

Ø       Exception Handler: This is required to catch the exceptions  

Ø       Send Delivery IDOC in the Exception block

Click here to continue...