SAP MDG · UTILITIES
How do I integrate SAP MDG with Ariba SLP without using a Default Logical Port?
Configure the outbound BP integration in SOAMANAGER using Services Registry, Provider System routing, and Local Integration Scenario setup instead of a Default Logical Port. The critical rule is that the SOAMANAGER Provider System name must exactly match the Ariba SLP Business System ID used in DRFIMG.
Configure the outbound BP integration in SOAMANAGER using Services Registry, Provider System routing, and Local Integration Scenario setup instead of a Default Logical Port. The critical rule is that the SOAMANAGER Provider System name must exactly match the Ariba SLP Business System ID used in DRFIMG.
This guide explains how to route SAP MDG / S/4HANA Business Partner replication to Ariba SLP without a Default Logical Port. The setup is done in SOAMANAGER, uses Services Registry and Local Integration Scenario configuration, and relies on one critical naming rule: the SOAMANAGER Provider System name must match the Ariba SLP Business System ID used in DRFIMG. It also requires the BP relationship service groups so Local Integration Scenario generation can complete.
Process flow
- Start transaction `SPROXY` and download the four outbound WSDLs for the required Service Interfaces.
- Modify each WSDL as shown in the guide, adding the required elements at the end of the definition and replacing `<Ariba CIG URL>` with the actual endpoint.
- Start transaction `SOAMANAGER` and open `Tools -> WSDL Upload`.
- Upload all four modified WSDL files with `WSDL Base = Via File`.
- Open `Services Registry -> Publication of External WSDL` and publish each uploaded WSDL.
- Create one Physical System for Ariba SLP; use the DRF IMG Business System ID as the System Name and set System Type to `Third Party`.
- Create the Ariba CIG Profile under `Technical Administration -> Profiles` and activate it.
- Create the Provider System under `Technical Administration -> Provider Systems` and make sure its name exactly matches the Ariba SLP Business System ID used in `DRFIMG`. Use the created profile and select `SR_LOCAL` in Services Registry / S
SOAMANAGERTools -> WSDL Upload
Upload the four modified outbound WSDL files via file.
SOAMANAGERServices Registry -> Publication of External WSDL
Publish each uploaded WSDL and register the generated service definitions.
SOAMANAGERServices Registry -> Published Service Definitions
Verify the service definitions generated from the WSDL publications.
SOAMANAGERTechnical Administration -> Profiles
Create and activate the Ariba CIG access profile.
SOAMANAGERTechnical Administration -> Provider Systems
Create the Ariba Provider System and make its name exactly match the Ariba SLP Business System ID used in DRFIMG.
SOAMANAGERService Administration -> Logon Data Management
Create and activate the Ariba CIG Logon Data.
Referenced tables
| Object | Purpose |
|---|---|
MDG_BS_SUPPLIERREPLICATEREQ | Service Group for replication/request routing; source says it contains BP replication and BP relationship replication interfaces. |
MDG_BS_SUPPLIERREPLICATECONF | Service Group for confirmation routing; source says it contains BP replication confirmation and BP relationship replication confirmation interfaces. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is this guide about?
- How can S/4HANA route BP replication to Ariba SLP without a default port?
- How does SOAMANAGER know which target system to use?
Possible questions
- What must already be configured before following this guide?
- Which Service Groups are required?
- Why does Local Integration Scenario generation fail without BP relationships?
- How do I verify the generated logical ports?
- What should I check if routing to Ariba fails?