- SAP Managed Tags
Introduction
In this blog, I’m excited to share insights from a recent integration project involving SAP Ariba Supplier Lifecycle and Performance (SLP) and S/4HANA Public Cloud. The experience was both technically enriching and rewarding—especially as it involved stitching together configurations spread across multiple SAP systems into a single, streamlined guide. This post serves as a one-stop reference for consultants and integration specialists who are tasked with delivering similar projects. Working across four SAP products makes this a unique and valuable experience for any functional consultant.
Ariba supplier integration flow
Prerequisite
Before you begin, ensure the following systems are provisioned and configured:
- SAP Ariba SLP realm
- Set SM configuration parameters as mentioned here
- SAP Business Technology Platform (BTP)
- S/4HANA Public Cloud with:
- Activated countries
- Configured organizational structure
- ERP master data setup for supplier business partners
Configuration in SAP Ariba SLP
SAP Ariba SLP acts as the front-end system for supplier onboarding, so we start our configuration here.
- Activate Feature SM-30016: Raise a case with SAP to enable this feature. It’s best to do this immediately after realm provisioning.
- Set Parameters:
- Application.SM.MDI.MdiEnabled = True: Enables SAP MDI integration in SLP.
- Application.SM.MDI.MdiPrimaryBpId = Own system ID of S/4HANA public cloud
- Application.SM.BPKM.KeyMappingEnabled = True: Enables key mapping and sets default values for related parameters.
- Application.SM.BusinessPartner.EnableBup007Sync = True: Adds the ANID of the supplier to the payload.
- Perform SLP Administration Tasks:
- Publish supplier management templates
- Set Default_properties.csv
- Choose initial supplier synchronization options
- ERP Integration Settings:
- Navigate to SM Administration > ERP Integration
- Set Integration Type to SAP Ariba Cloud Integration Gateway
- Set ERP Business System ID to the SAP MDI Subdomain ID in lower case (explained later). Note it is not the S/4HANA own system ID
- SAP Ariba Business System ID is auto populated with the realm ID
Configuration in SAP Master Data Integration
SAP BTP Setup
- In the SAP BTP Cockpit, create a subaccount with the sap-integration service plan.
- Create two service instances—one each for:
- SAP Ariba SLP
- S/4HANA Public Cloud
- Generate a service key/binding for each instance:
- Use the values below to maintain the parameters
| System | application | businessSystemId |
| Ariba SLP | ariba | Realm ID |
| S/4HANA Public Cloud | s4 | Own system ID (7-chars) |
Ariba parameters
S/4HANA parameter
Configure distribution model
- Launch Master Data Integration (Orchestration)
- Open app Configure Business System Name:
- Enter the Subdomain ID in lowercase as the Business System.
- Activate it.
- Open app Configure SOAP Replication:
- Select the Business System.
- Click Edit, check SOAP Business Partner Active, and save.
- Open app Manage Distribution Model:
- Create a new model with:
- Provider: MDI
- Consumer: Destination defined for BPOUTBOUND
- Application Category: SAP S/4HANA Cloud
- Enable Distribute Key Mapping
- Save and activate
- Create a new model with:
Refer to picture below
Configure destination
Configure three destinations as outlined below.
- The first destination replicates suppliers from SAP MDI to S/4HANA Public Cloud.
- The second sends a Business Partner (BP) confirmation message from SAP MDI to the Cloud Integration Gateway (CIG) upon supplier creation in MDI.
- The third replicates key mapping data from SAP MDI to CIG.
The URL for S4ID_BPOUTBOUND is taken from the communication arrangement SAPCOM_0008.
Note: It is important to follow the destination naming conventions exactly as shown.
| Name | URL |
| S/4ID_BPOUTBOUND | https://my123456-api.s4hana.cloud.sap/sap/bc/srt/scs_ext/sap/businesspartnersuitebulkreplic |
| RealmID_BPCONFIRM | https://test-integration.us.managedgateway.cloud.sap/cxf/receiveERPMD |
| RealmID_KMOUTBOUND | https://test-integration.us.managedgateway.cloud.sap/cxf/receiveERPMD |
S4ID_BPOUTBOUND
Here, MDOBusinessSystem is S/4HANA's own system ID, and MDIInstanceId is taken from the service key or binding created for the S/4HANA system.
For RealmID_BPCONFIRM and RealmID_KMOUTBOUND, refer to the details below. URLs for different CIG data centers can be found here.
Configuration in SAP Integration Suite, managed gateway (CIG)
Activate SAP Integration Suite (CIG) by selecting the webservice shown below.
In CIG basic data, add a trading partner system as shown below. The System ID is the Subdomain ID (convert to lowercase) from the SAP BTP cockpit of the subaccount created for SAP MDI (SLP integration).
Create a new integration project, select the product Ariba Sourcing, and add two connections - one for BP replication and the other for BP confirmation.
| Field | Value |
| BP Create | |
| Transport Type | HTTPS |
| Environment | Choose TEST / PRODUCTION |
| Name | Enter a name for the connection i.e., BPREPL |
| System ID | Enter identityzone from the service key created for Ariba |
| Document Type | BusinessPartnerSUITEReplicateRequest |
| URL | "https://one-mds.cfapps.xxxx.hana.ondemand.com:443/businesspartner/v0/soap/BusinessPartnerBulkReplicateRequestIn?tenantId=identityzone" XXXX: Data center where SAP MDI subaccount is hosted. Refer to subdomain value in BTP cockpit subaccount overview. identityzone: Subdomain ID in lower case |
| Authentication Type | For basic authentication, specify the following: User: Value of clientid from the service key or binding Password: Value of clientsecret from the service key or binding |
| BP Confirm | |
| Transport Type | HTTPS |
| Environment | Choose TEST / PRODUCTION |
| Name | Enter a name for the connection i.e., BPREPLCONF |
| System ID | Enter identityzone from the service key created for Ariba |
| Document Type | BusinessPartnerSUITEReplicateConfirmation |
| URL | "https://one-mds.cfapps.xxxx.hana.ondemand.com:443/businesspartner/v0/soap/BusinessPartnerBulkReplicateRequestConfIn?tenantId=identityzone" XXXX: Data center where SAP MDI subaccount is hosted. Refer to subdomain value in BTP cockpit subaccount overview. identityzone: Subdomain ID in lower case |
| Authentication Type | For basic authentication, specify the following: User: Value of clientid from the service key or binding Password: Value of clientsecret from the service key or binding |
A sample messages from CIG
Configuration in SAP S/4HANA Public Cloud
In S/4HANA, add the critical configuration data required for a business partner, such as bank master data, tax category, payment terms, payment method, supplier reconciliation account, etc. Once completed, create a communication user, communication system, and a communication arrangement for scenario ID SAP_COM_0008 as described here. However, it is only necessary to activate the outbound service Business Partner – Send Confirmation from SAP S/4HANA Cloud to Client, instead of all four services mentioned in the documentation.
Assign Recipients to Users
To receive alerts related to BP inbound messages, add your email ID in the app Assign Recipients to Users, as shown below.
App Message Monitoring – SAP Application Interface Framework
Use the app to view inbound and outbound BP creation and confirmation messages. The message types are:
- /CMDBP - BP_IN - 00002 (Inbound)
- /CMDBP - BPCONF_OUT - 00001 (Outbound Confirmation)
Message Monitoring for Integration Experts - Use the app to download the payload
Learnings
- A PUSH based Business Data Orchestration model for Business Partners also includes distribution of Business Partners Relationships and Key Mapping. A separate SOAP PUSH distribution model is not required for Business Partners Relationships and Key Mapping. However, a separate destination configuration setup is required for Business Partners Relationships and Key Mapping. For example, <businessSystemId>_BPRELOUTBOUND and <businessSystemId>_KMOUTBOUND
- CIG webservice sends Ariba supplier (RequestIn) to SAP MDI where it is stored in its database, then SAP MDI distributes supplier to S/4HANA and receives the confirmation message, so SAP MDI sends RequestConfIn message back to CIG, not S/4HANA.
- Destination KMOUTBOUND needs to be defined in order to get BP number from S/4HANA and Key Mapping message can be seen in CIG. Key Mapping is sent to CIG when a supplier is created but not when updated.
- When defining connections in CIG, use clientid and client secret from service key/binding of service instance created for Ariba in BTP cockpit, not the S/4HANA’s.
Common errors
- Error > Region AGS is not defined for MX.
- Solution – Get the region codes from SAP and maintain in SM Manager in Ariba.
- Error > Country/Region Key: Plausibility check failed.
- Solution: configure supplier reconciliation account in registration questionnaire or in set in Default_properties file
- Error > Tax number category XX01 does not exist in TFKTAXNUMTYPE table.
- Solution: Send a valid tax ID, not a dummy ID because SAP will reject it even when syntax is correct
- Error > Receiver for Sender Business System ID Could Not be Determined.
- Solution: In the Communication Arrangements app, for SAP_COM_0008 you have to ensure that the Business Partner - Send Confirmation from SAP S/4HANA Cloud to Client checkbox is activated
Useful links
- About Supplier Data Integration with SAP S/4HANA Cloud Using SAP Master Data Integration
- Configuring Destinations for SOAP
- CIG data center endpoint destinations
- Endpoints for SOAP Replication for Business Partners
- Connecting from SAP S/4HANA Cloud to SAP Master Data Integration service
- Assigning recipients to users
