Introduction
Integration Advisor (IA) supports from the current release(
Increment 1810) the generation of Mapping artifacts for SAP Process Integration.
In our previous blogs we described about the
ICA capabilities, how to
work with the supported B2B/A2A Standard libraries and how to
create customized interface definitions tailored to the business needs.
The blog explains the steps to be executed within IA to be able to consume the customized interface mappings for SAP Process Integration.
Step 1: Create message implementation guidelines (MIG) for the source and target interfaces
Reference about interface customization is described in our previous blog
Create a customized interface using MIG editor
Step 2: Create a new mapping implementation guideline (MAG)
Reference about creating a mapping between source and target interface in previous
blogs as well help
documentation.
Step 3: Export the runtime artifacts for SAP Process Integration.
In the Integration Advisor open the desired Mapping Guideline. Under the Export menu, select “Process Integration Runtime Artifacts”. Below example illustrates an IDoc to ASC X12 mapping.
This downloads a zip file containing the following artifacts:
- IA pre-processing script: this script prepares the source payload (depending on the source MIG type system, an EDI to XML conversion might have to be performed before this step) for the message mapping.
- Message mapping
- IA post-processing script: this script transforms the mapping result into desired target payload (depending on the target MIG type system, an XML to EDI conversion might have to be performed after this step).
Step 4: Import the zip file as an archive in the Enterprise Service Repository (ESR).
Open the ESR of the SAP Process Integration system and under the desire Software Component version & namespace, import the IA runtime artifacts zip file as an archive.
Step 5: Create source and target service interfaces
In the ESR, create the source and target message definitions and the corresponding service interfaces. Assign the service interfaces to corresponding Business Components or Business Systems.
Step 6: Configure an external XSLT processor
ICA mapping scripts use XSLT 2.0 and hence an external XSLT processor that supports the XSLT 2.0 version (for e.g., Saxonica 9.x) must be configured to be used in the mapping runtime.
This blog explains the steps to configure an external XSLT processor.
Step 7: Create an EDI Header Mapping, if needed
A header mapping for the EDI message would be necessary in an EDI outbound scenario (i.e., if an ASC X12 or EDIFACT document is to be sent to an external business partner). In such cases, using the EDI message interface defined in Step 5, create a one-to-one mapping by using the same EDI message interface as both source and target message type of the message mapping in the ESR. Make sure that every field except the fields of the header segments (i.e. ISA, GS, GE and IEA segments of an ASC X12 EDI interface) are mapping directly. Map the fields of the header segments as needed.
Step 8: Create an Operation Mapping
In the ESR, create an Operation Mapping with the following mapping steps:
Step |
Message Mapping |
Type |
1 |
IA pre-processing |
XSL |
2 |
IA message mapping |
XSL |
3 |
IA post-processing |
XSL |
4 |
Header mapping, if any, as defined in Step 7 |
mmap or any type supported by ESR |
Step 9: Test the Operation Mapping
The operation mapping can be tested directly in the ESR.
Summary
This blog is an overview about the generation of the consumable runtime artifacts with an example of the outbound scenario for SAP Process Integration. Stay tuned for a follow up blog for a detailed overview of the configuration steps within SAP Process Integration.
