Skip to Content

Collecting and Bundling vendor records from different multiple interfaces (file system,Peoplesoft ) and sending to SAP-R/3 system. part-1


In this exercise we can focus on the Business Process Management capabilities. The goal is to collect messages from different multiple interfaces and bundle them forward to a single receiver. Using Fork, transformation steps and containers and correlation and multi mapping can fulfill this.This part-1 covers SLD and IR.If there is any other weblog like this you can refer that also.


Collect incoming vendor records from File and PeopleSoft. The incoming messages arrive via File adapter and HTTP adapter. After these messages are collected from File and Peoplsoft, they are bundled and mapped to package of IDocs. This package of IDocs is then posted into the R/3 system via the IDoc adapter

Exercise steps

Step 1-System Landscape Directory

1. Create SLD objects for File system or reuse.

2. Create SLD objects for People soft system or reuse

3. Create SLD objects for SAP R/3 or reuse.

Step 2-Integration Repository

1.Prepare Interface objects for File system (Data type, Message type, Message Interface) or reuse.

2.Prepare Interface objects for Peoplesoft system (Data type, Message type, Message Interface) or reuse.

3.Import IDoc (CREMAS.CREMAS03).

4.Create an abstract asynchronous interface for File system (based on IDoc CREMAS03). This will be input to the process from File system.


5.Create an abstract asynchronous interface for Peoplesoft system (based on IDoc CREMAS03). This will be input to the process from Peoplesoft system



7.Create an external definition object called CREMAS_package. Import modified xsd file.


8.Create an asynchronous abstract interface


(based on external object called CREMAS_package). This will be the output of the integration process



Choose Message from external Definitions

9. Mapping objects

9.1 Message mapping between File message type and CREMAS03 (original IDoc)
Called “



9.2 Interface mapping between File Interface and abstract interface of File.
Use above message mapping. It is called



9.3 Message mapping between Peoplesoft message type and CREMAS03 (IDoc)
Called “



9.4 Interface mapping between Peoplesoft interface and abstract interface of use above message mapping .It is called



9.5 Message mapping between Original IDoc and CREMAS_package, make it as multi mapping called


In Messages tab make the occurrence to 0 to unbound for source message.

Map the node “CREMAS03” from source to the node “IDOC” of target


9.6 Perform interface mapping from file abstract and psft abstract to CREMAS_package called


Make sure the occurrence of the source interfaces should be “o.. Unbound”.


Note: Here two source interfaces (file abstract and Peoplesoft abstract interfaces ) and target interface (multi package CREMAS_package )..

10.Create context object type string. For correlation id in BPM

Step 3 BPM

1.Create Integration process

2.Create following containers

2.1.File_abs (Category: Abstract interface type: file_ abs)

2.2.Psft_abs (Category: Abstract interface type: psft_abs)

2.3.cremaspackae (Category: Abstract interface type: CREMAS_package).

3.Receice step 1:

Step Name: FileRec

Message: file_abs

Start process: yes

Use Correlation: zip

Activate Correlation: zip

Zipcode-> zip:file_abs (Select your context object for container file_abs )

4.Receive step 2:

Step Name : PsftRec

Message : psft_abs

Start process: yes

Use Correlation: zip

Activate Correlation: zip

Zipcode-> zip: file_abs (Select your context object for container psft_abs)

5.Transformation step:

Step Name : Bundle

Interface mapping: IM_multi_cremaspackage

Source messages : File_abs

Target message : cremaspackage.

6. Sender step:

Step Name : Send

Mode : Asynchronous

Message :cremaspackage

Activate correlation: zip: crmpackage (Select your context object for container crmpackage).

Be the first to leave a comment
You must be Logged on to comment or reply to a post.