B2B Integration – Pushing the Mapping Artifacts to SAP Cloud Platform Integration
This is my first blog post on Integration Content Advisor and I would like to share my learning experience on Integration Content Advisor.
In this blog post, I would be explaining the basic steps to be followed to create Message Implementation Guidelines (MIGs) and Mapping Guidelines (MAGs).
SAP Integration Advisor is a cloud application that helps to simplify and streamline the implementation flow of B2B/A2A and B2G integration process. It uses a crowd-based machine learning approach which helps to create integration content easily.
Integration Advisor solves the biggest problem that we face in B2B/A2A/B2G integration scenarios.
- Integration Content Advisor capability added to the Integration Suite.
- License for the Type Systems to create Message Implementation Guidelines(ASC_X12, UNEDIFACT,ETC)
All set…. Let us start! 🙂
The following steps explain the step-by-step procedure of creating MIGs and MAGs.
Creating Message Implementation Guideline(MIG):
Let us consider the scenario of implementing B2B integration of sending the Purchase Order Request with source as SAP IDOC (ORDERS.ORDERS05) and target as cXML.
STEP -1: Selecting the Type System to create source MIG:
Ensure the License type of the selected Type system.
STEP -2: Select the Message type and version:
Here I am using the example Payload to create Message Implementation Guideline.
STEP -3: Creating MIG:
Direction: Direction is used together with your Own Business Context and your Partners Business Context to make the Proposal Service more precise. The values given describe the direction from a B2B interaction point of view.
- In – The MIG describes a message that you receive from a Business Partner.
- Out – The MIG describes a message that you send to a Business Partner.
- Both – The MIG describes a message that can both be received from a partner or sent to a partner.
STEP -4:Adding the Business Context:
The business context is a very important part of the MIG. It labels the MIG so that the system can give you an appropriate proposal based on the defined business context.
We can scroll through the definition proposal and decide which portions to accept, which to remove, and finally which additional fields or segments to enhance the Message Implementation Guideline definition with.
Now the MIG is created and saved in Draft mode with all the given details.
Once all done, save the MIG and Activate it.
Once you click on confirm, the MIG will be activated and stored in the Knowledge Graph and adds to the possible proposals for the next user (which maybe you!).
The changes that we make in the MIG will be saved as a New Version.
Follow all the above steps to create the Target Message Implementation Guideline by selecting Type System cXML and also the appropriate message type and version.
And ensure that the MIG is in “Active” state.
Creating Mapping Guidelines(MAG):
Here comes the important part!!!
In this step, we are creating the Mapping Guideline for the source and Target Message Implementation Guidelines.
Select the source and Target Message Implementation Guidelines to create Mapping Guidelines.
We can map the source and target nodes based on the best proposal that we get from the Integration Advisor knowledge graph.
Save and Activate the Mapping Guideline (MAG).
EDI Integration Templates for SAP Integration Advisor:
One more amazing feature from SAP!!
In SAP Cloud Platform Integration, SAP provides the Integration flow templates for SAP Integration Advisor (IA) related to EDI integration scenarios.
And we can access the below integration package via the API Business Hub.
We can copy or download the entire the package to the Design part of the Cloud Integration to perform the B2B integration process.
Pushing the Runtime Artifact to SAP Cloud Integration:
- By exporting the runtime artifacts, the Integration Advisor automatically generates number of schemas, scripts from a mapping guideline.
We can also export MIG and MAG as a documentation artifact, which is a PDF files which can be used as reference documentation for bookkeeping purposes.
- In order to use the inject method; the destination has to be created in SAP BTP Subaccount.
In the next step, select the artifact template based on the Source and target Message type.
Now we can see the Resource Injection Successful message… We are good to go…:)
And finally we are done!!!
Our B2B integration scenario is ready to run with the communication Adapter configurations.
This blog post explains a detailed step-by-step procedure to create the basic Message Implementation Guidelines, Mapping Guidelines and pushing the Runtime Artifact to the SAP Cloud Platform Integration.
Please do like the blog post, if you find the content helpful. Also, do share your inputs and opinions as comments.
Happy Learning!… 🙂
For more such informative technical articles on SAP Businness Technology Platform,