Overview
In this exercise we can focus on the Business Process Management capabilities. The goal is to send a Purchase order Request from Mail interface to a particular receiver out of couple of receivers and get back sales order. Sending a Request Selectively to a Receiver out of Receivers pool and Getting Response back from Receiver. (Using BPM includes steps Switch, Correlation, and containers).
Description
Send purchase order from mail then mail adapter takes this purchase order from mail server inbox and sends to corresponding receiver for generating sales order. The Receiver selection is done based on vendor number. Sender is Mail server and Receivers are SAP and Peoplesoft and FileSystem.
Note: This is not a productive example, I hope it helps you to understand BPM scenarios based on switch and synchronous mechanism.
BPM Diagram
Exercise steps
Step 1-System Landscape Directory
1. Create SLD objects for File system or reuse. (Receiver)
2.Create SLD objects for People soft system or reuse. (Receiver)
3.Create SLD objects for SAP R/3 or reuse. (Receiver)
4.Create SLD objects for Mail System (Sender)
Step 2-Integration Repository
2.1.Import RFC for SAP R/3 ZRFC_SALESORDER_CREATEFROMDAT1
2.2.Prepare Interface objects for Mail system (Req Data type, Req Message type, Res Data type, Res Message Type, Outbound Synchronous Interface) or reuse.
2.3 Purchase Order Req Data type
2.4 Purchase Order Message type
2.5 Res Data Type (Sales Order DT_SO )
2.6 Res Message Type (Sales Order MT_SO)
2.7 Message interface (Out bound Synchronous Out :MT_PO, Inp :MT_SO)
2.8 Inbound Synchronous Message Interface (Out: MT_SO, Inp: MT_SO) for File and PeopleSoft.
Note: Req Data type MT_PO, Req Message Type: MT_PO Res Data type: MT_SO, Res Message Type: MT_SO are common for all File System and Mail System and People Soft System.
2.9 Abstract Asynchronous Interface for Purchase Order (MT_PO).
2.10 Abstract Asynchronous Interface for Sales Order (MT_SO)
2.11 Abstract synchronous Interface ( MT_PO,MT_SO)
Mapping Objects: Message mapping
2.12 .Message Mapping between MT_PO and RFC Req.
2.13 Message Mapping between RFC response to MT_SO
2.14 Message Mapping between MT_PO and MT_PO.
2.15 Message Mapping between MT_SO and MT_SO
Mapping Objects : Interface Mapping
2.16 Interface mapping between synchronous abstract interface and RFC called IM_PO_SO.
2.17 Interface mapping between synchronous abstract interface(MI_PO_SO_ABS) and inbound synchronous interface (MI_PSFT_FILE)
Step 3 BPM
3.1.Create Integration Process.
3.2.Create Following Containers.
1.PO (Category: Abstract Interface, Type: MI_PO_ABS)
2.SO (Category: Abstract Interface, Type: MI_SO_ABS)
3.3 Create Correlation Object.
1.Correlation Name: CO
2.Correlation Container: CR, type: string, Involved messages: MI_PO_ABS,MI_SO_ABS
3.4.Receiver Step 1.
Step Name: PO_Rec
Message: PO
StartProcess: yes
Active Correlation: CO
3.5 Switch 1.
Step Name: Sel_Rec
Branch1 Condition: (PO./p1:MT_PO/DT_ORDER_PARTNERSNEW/PARTN_NUMB = PSFT )
Branch2 Conditions: (PO./p1:MT_PO/DT_ORDER_PARTNERSNEW/PARTN_ROLE = FILE)
Branch3 Condition : (PO./p1:MT_PO/DT_ORDER_PARTNERSNEW/PARTN_NUMB = SAP)
3.6 Sender 1.(Branch1)
Step Name: PSFT
Mode: Synchronous
Synchronous Interface: MI_PO_SO_ABS
Request Message: PO
Response Message: SO
Activate Correlation: CO
3.7 Sender 2(Branch 2)
Step Name: FILE
Mode: Synchronous
Synchronous Interface: MI_PO_SO_ABS
Request Message: PO
Response Message: SO
Activate Correlation: CO
3.8 Sender 3 (Branch 3)
Step Name: SAP
Mode: Synchronous
Synchronous Interface: MI_PO_SO_ABS
Request Message: PO
Response Message: SO
Activate Correlation: CO
3.9 Sender 4
Step Name: PSFT
Mode: Asynchronous
Message: SO
Activate Correlation: CO
