In this Blog, I would like to share the effective way of using Message Mapping in B2B Scenarios using TPM and SAP Integration Suite.
Prerequisites:
Knowledge in SAP Integration Suite, Integration Advisor, TPM, Message Mapping, B2B Concepts.
Lets get Started:
TPM allows us to use a custom mapping instead of the standard MAG/XSLT mappings.
In case if you use the above approach, you have to create a Custom Integration Flow using Process Direct Sender with the address mentioned as above,
Normally what we tend to do is, create “N” number of Integration Flows because of either of the following reason,
1. You maintain different addresses in TPM for different agreements.
OR
2. You maintain the same address in TPM, but you have different message mapping for partners and EDI messages.
Here, What we will do is eliminate the number of Integration Flows created in this process, Instead we will try to achieve all B2B transformations through just one single Integration Flow.
To achieve this, Proceed as below:
Step 1:
Maintain a parameter in TPM agreement,
For each inbound/outbound agreement, provide an activity parameter.
Key: Put any Parameter Name of your choice but should be same for all B2B agreements. (Inbound/Outbound)
Value: Your Message Mapping ID value. (Reference shown below)
Step 2:
Create a package and create your Integration Flow.
Step 3:
Access the Custom Parameters of the Agreement using Groovy.
In this case:
Property Name <==> Activity Parameter Key
Property Value <==> Activity Parameter value (Refer Step 1)
Step 4:
Add “ref:” to Property Value
Step 5:
Use this property in Message Mapping
Step 6:
Add Global reference to your Groovy and Message Mappings.
So next time, you onboard a new Customer / Vendor / 3PL, All you have to do is
A. Maintain agreements in TPM.
B. Create Message Mapping as per your need.
C. Add global reference of the message mapping into the Integration Flow (Created in Step 2).
PS: You can refer the Groovy scripts from Accelerator Hub,
Thanks for your time.
Regards,
Kottiyil Ramnath