Migrate Outbound B2B ASCX12 interfaces from SAP PI/PO to CI(CPI) using BIMA Package

[adarshrao_rao]

Many customers use SAP PI/PO systems for B2B transactions that use ASC X12 message types. When they decide to migrate to SAP Cloud Integration, they encounter some challenges. Specifically, SAP PI/PO uses XML Schema Definition (XSD) format that aren't compatible with Cloud Integration - XML to EDI or EDI to XML converters, making it difficult to re-use existing SAP PI/PO mappings in Cloud Integration.

To solve this problem, we have created a package called the B2B Interface Migration Accelerator – ASCX12 which is in SAP Business Accelerator Hub. This package helps move your B2B ASCX12 interfaces to the cloud easily, saving time and effort by using your existing SAP PI/PO message mappings.

1.  Concept:

Whenever xml file which is PI/PO xsd specific or Cloud Integration xsd specific enters Cloud Integration iFlow, the structure is modified with the help of XSLT mapping based on the reference xml file which is stored in the Partner directory. This also depends on the flow. When the files are triggered from Company to the Trading Partner then it is Outbound Flow. When the files are triggered from Trading Partner to the Company then it is Inbound Flow. 

In this blog, we'll explore at how to migrate outbound B2B interfaces that use ASCX12 message types.

For migration ASCX12 inbound interfaces, please refer to blog

2.  High-Level Design – Outbound Flow

In an outbound flow, a file triggered from the Company, enters a specific iFlow in Cloud Integration. Then, a generic iFlow is called which compares the structure of this file with a reference XML file stored in the Partner directory. After making necessary changes, the revised file is sent to the Trading Partner. This setup ensures the file is in the right format for the Trading Partner.

In the above depiction,

1. XML file is received by the iFlow outbound template (specific iFlow)
2. XML file sent to existing message mapping which is imported from SAP PI/PO
3. Check whether standard solution to support PI/PO specific xsd file in the converter is available
4. If not, call the XML structure modifier flow (Generic iFlow)
5. Modified XML file from Generic iFlow is sent to XML-EDI converter
6. Output is sent to Trading Partner

3.  Migration Steps – Outbound Flow

Example: Migrate an outbound ASCX12 interface which has message type, 810 and version, 004010 from SAP PI/PO to CI

Preparation:

Refer the Configuration Guide maintained in the Document section of this package, complete Pre-requisites and copy the package to your workspace/tenant.

1. Go to Integrations under Discover, select the package and copy it to your tenant

2. Refer Configuration Guide maintained in the Document Section

3. From the package, copy the outbound template flow to a separate package which is Trading Partner specific

4. To create a reference file for outbound flow of message type 810 and version 004010, Go to Type Systems, Select ASC X12, Messages 810 and version 004010

Click on Create MIG, Select with Envelope

Upload a sample EDI flat file which contains all the segments and fields required by all the Trading Partners for ASC 810 004010 integration

Select the Nodes based on the payload, Click on Next, provide required name, direction as outbound and Create Invoice as Business Process under Own Business Context

Click on Create and this created MIG can be exported as SAP Cloud Integration Runtime Artifacts

In this exported artifact, we would need the below highlighted ones. Xml file to upload as reference xml file in the Partner Directory and xsd to upload in the XML to EDI Converter

5. Create Partner Directories with names mentioned in the Configuration Guide

I have uploaded test data from above downloaded artifact  which has all the fields utilized by all the partners in the landscape for 810 message type and 04010 message version. Hence, this payload can be the reference xml file and it is sufficient for me to migrate all the 810 message type interfaces for all the Trading Partners.

Configuration:

1. In this Trading Partner Specific Outbound flow, I will configure the sender and receiver systems

2. Under Mapping Flow, I will configure the existing message mapping for this Trading Partner which is imported from SAP PI/PO

3. In the XML to EDI converter under converter flow, upload Cloud Integration specific ASC 810 message type of version 004010 xsd from the downloaded artificat which was exported from Integration Advisor in step#4 of Preparation

4. Deploy the following Artifacts

Testing:

I have completed the configuration and in my outbound flow Company is sending an INVOIC IDOC which needs to be converted to EDI format before sending it to Trading Partner

Triggered INVOIC IDOC should be passed through the imported message mapping from SAP PI/PO

Outbound INVOIC IDOC from the company:      

Output of the message mapping which EDI XML file which is in PI/PO specific structure:

This file can’t be passed directly to XML to EDI Converter because the converter uses CI specific xsd for conversion. Hence the Structure Modifier Generic flow is called which will modify this PI/PO specific structure to CI specific structure by referring to the reference file uploaded in the Partner Directory.

Output of XML Structure Modifier Flow:

This modified file can be sent to XML to EDI converter and the output can be forwarded to Trading Partner

Out EDI file sent to Trading Partner:

Status in the Message Monitor:

4.  Summary – Outbound Flow

Migrating outbound B2B interfaces using ASC X12 message types to SAP Cloud Integration is a structured process that effectively utilizes existing SAP PI/PO mappings. The outbound template plays a central role, enabling file structure transformation through specific and generic iFlows to meet Trading Partner needs. Furthermore, the outbound template is flexible, allowing for extensions in mapping logic and the incorporation of a retry mechanism through the exception flow, catering to varied business requirements. Once the standard solution is available by SAP to support SAP PI/PO xsds in the converters, structure modification flow can be easily switched off in the Decider Flow.

A key aspect of this migration is the creation and maintenance of Partner directories and reference XML files. This setup is a one-time task that significantly simplifies ongoing operations. For instance, if your business needs outbound interfaces for ASC X12 message type 810, version 004010 across 50 Trading Partners, you only need to maintain one reference XML file with all necessary segments for these 50 partners. This reference file serves as a benchmark, allowing inbound XML files to be compared and altered accordingly.

The Partner directory SAP_PI_to_CPI_Outbound is created once and used universally for all outbound flows and message versions. For example, If there is a Purchase order change outbound interface which used message type 860 with version 004010 then the reference file for this flow is added in the same Partner director,  SAP_PI_to_CPI_Outbound without further setup.

This approach streamlines the migration process, reduces redundancy, and ensures efficient modification and management of XML structures, making it a cost-effective solution for transitioning to Cloud Integration  while maintaining reliable communication with Trading Partners

5.  Additional Read

Migration Guide : https://help.sap.com/docs/migration-guide-po/migration-guide-for-sap-process-orchestration/interface...

Feel free to share your thoughts and experiences in the comments section below. Whether you have questions about the migration process, insights from your own experiences, or suggestions for further improvements, we'd love to hear from you. Your feedback can help enhance understanding and provide valuable knowledge to others navigating similar transitions.