Core Architectural Mandate: With the end-of-life of SAP Process Orchestration (PO/PI), enterprises must retire legacy IDocs/RFC adapters and graphical message mappings. In SAP Clean Core, B2B integration is standardized on SAP Integration Advisor, leveraging crowdsourced machine learning to generate Message Implementation Guidelines (MIG) and Mapping Guidelines (MAG) that execute as native XSLT 3.0 artifacts in SAP Cloud Integration.
In traditional SAP PO/PI, creating a single EDIFACT or ANSI X12 B2B interface required weeks of manual work: reading 300-page customer specifications, writing user-defined Java functions (UDFs), and hand-mapping hundreds of fields.
| Integration Dimension | Legacy SAP PO/PI | SAP Integration Advisor (BTP) |
|---|---|---|
| Mapping Approach | Manual Graphical Message Mapping + Java UDFs | AI & Crowdsourced Mapping Proposal Engine |
| Implementation Time | 2 - 4 weeks per partner message format | 2 - 4 hours with automated MAG proposals |
| Runtime Execution | Proprietary PO Java stack engine | Compiled XSLT 3.0 & Schematron validation |
| Core Interface | Direct IDocs / RFCs (Tiers 2 & 3) | Released OData V4 / SOAP Clean Core APIs (Tier 1) |
SAP Integration Advisor is structured around two fundamental building blocks:
A customized subset of a B2B standard (e.g. UN/EDIFACT D.96A ORDERS or ANSI X12 850). Instead of exposing thousands of unused elements, a MIG defines:
A declarative mapping definition between two specific MIGs (e.g., EDIFACT ORDERS MIG -> SAP S/4HANA Sales Order OData V4 MIG). Integration Advisor evaluates millions of anonymized community mappings to auto-propose 70% to 90% of all field mappings, including complex date formats and code list translations.
Explore complete architectural patterns for SAP Integration Suite, Trading Partner Management (TPM), AS2 adapters, and B2B pipelines in The SAP Enterprise Architecture Suite.
Get the Full Architecture Suite (FLASH80 - 80% Off) →Once a MAG is completed in Integration Advisor, developers export the Runtime Artifacts with one click. These include:
MAG_Transform.xsl: A highly optimized XSLT 3.0 stylesheet executed by the Cloud Integration XSLT Mapping step.Source_Validator.xsd: Source schema validation rules.Schematron.sch: Business rule validations (e.g., verifying that line item totals equal header gross amount).In Clean Core architecture, external B2B partner EDI messages are terminated in SAP Integration Suite on BTP. The iFlow transforms the EDI into standard SAP Cloud OData V4 API calls. The core S/4HANA system is never exposed to raw EDI parser dependencies or legacy ALE/IDoc configurations.