A step-by-step guide to governing Business Partner master data in SAP Master Data Governance, cloud edition and distributing it to SAP S/4HANA Public Cloud using SAP Master Data Integration.
Many enterprises want SAP Master Data Governance (MDG), cloud edition to be the single source of truth for Business Partner data, with automatic distribution to Cloud ERP (alias SAP S/4HANA Public Cloud ). This blog walks you through the strategic integration path — using SAP Master Data Integration (MDI) as the hub .
Overview & Solution Architecture
SAP’s recommended and strategic integration topology for Business Partner master data distribution in a Public Cloud landscape is
MDG, cloud editiongoverns the full lifecycle of Business Partner records — creation, enrichment, validation, approval, and deactivation — through structured change requests.
SAP Master Data Integration (MDI)acts as the cloud-native distribution backbone. It uses SAP’s One Domain Model (ODM) to normalize Business Partner data across systems and routes approved records to all registered consumer systems.
S/4HANA Public Cloudreceives the Business Partner data via a standard inbound API, making it immediately available for Accounts Receivable, Accounts Payable, Sales, and Purchasing processes.
Prerequisites
Before starting the configuration, ensure the following are in place:
SAP MDG, Cloud Edition tenant provisioned
SAP Master Data Integration (MDI) tenant
Cloud ERP (alias S/4HANA Public Cloud ) tenant active
SAP BTP subaccount with MDI service instance
Communication Admin role in Cloud ERP (alias S/4HANA Public Cloud )
MDG Administrator role in MDG CE
Number range strategy agreed upon
Step 1 — Configure S/4HANA Public Cloud
S/4HANA Public Cloud must be prepared to receive inbound Business Partner data from MDI. This is done by setting up a Communication Arrangement that opens the inbound API channel.
Activate the Master Data Integration scope
In your S/4HANA Cloud tenant, confirm that scope item 1RO – Integration of Core Master Data is activated. This scope activates the relevant Fiori apps and communication scenarios for inbound master data replication.
Create a Communication User
Go to theMaintain Communication UsersFiori app. Create a dedicated technical user (e.g.,MDI_INBOUND) with a strong password. This user will authenticate MDI inbound calls.
Create a Communication System
Go to theCommunication SystemsFiori app. Create a new system entry representing your MDI tenant. Provide the MDI tenant hostname and assign the communication user you created.
Create a Communication Arrangement
Go toCommunication Arrangements. Create a new arrangement for the Business Partner – Master Data Integration Inbound scenario (look for the MDI inbound orSAP_COM_0008-family scenario relevant to your release). Assign the communication system created above. This exposes the inbound OData endpoint that MDI will call.
Note the Service URL
Once saved, copy the inbound service URL shown in the arrangement. You will register this in MDI as the S/4HANA Cloud consumer endpoint.
Step 2 — Set Up SAP Master Data Integration
MDI is provisioned on SAP Business Technology Platform (BTP). You configure it to know about both your MDG CE tenant (provider) and your S/4HANA Cloud tenant (consumer).
Create an MDI Service Instance on SAP BTP
In your BTP subaccount, subscribe to the SAP Master Data Integration service and create a service instance. Generate a service key — this provides the MDI API credentials and endpoint URL.
Register S/4HANA Cloud as a Consumer
In the MDI administration UI (or via MDI API), register the S/4HANA Cloud endpoint using the service URL and credentials noted in Step 1. Assign theBusiness Partnerand (if needed)Business Partner Relationshipdomains to this consumer.
Register MDG CE as a Provider
Register your MDG CE tenant in MDI as the provider for the Business Partner domain. MDI will accept events from MDG CE and distribute them to all registered consumers.
Enable ODM Domains
In MDI, enable the relevant One Domain Model (ODM) entity types: typicallysap.odm.businesspartner.BusinessPartner. If you distribute relationships, also enablesap.odm.businesspartner.BusinessPartnerRelationship.
Configure Field Mappings (if needed)
If MDG CE carries custom/extension fields that must flow to S/4HANA Cloud, define the field mappings in MDI. Standard SAP fields follow the ODM and require no mapping.
Step 3 — Configure MDG, Cloud Edition
MDG CE must be configured to govern Business Partners according to your process requirements and to publish approved data to MDI.
Set Up Governance Processes
Define the change request types for Business Partner creation (and change/block/unblock workflows). Configure validations, duplicate checks, and enrichment rules as required by your data governance policies.
Configure the Distribution Model
Configure the Distribution Model in SAP Master Data Integration (MDI) using the application Manage Distribution Model . Add your MDI tenant as the distribution target for the Business Partner entity. This tells MDG CE to emit events to MDI upon change request approval.
Activate the model. Once active, MDI will route Business Partner events from MDG CE to S/4HANA Cloud on every approved change request.
Maintain MDI Connectivity
Provide the MDI service instance URL and credentials (from the BTP service key) in MDG CE’s outbound connectivity configuration. This enables MDG CE to push ODM-compliant events to MDI.
Model BP Roles and Structures
Ensure that the BP roles (Customer, Supplier, Contact Person, etc. , except the Employee role.), organization types, and relevant data segments (company code data, sales area data, purchasing data) are represented in the MDG CE data model and change request forms. What is not governed in MDG CE will not be distributed to S/4HANA Cloud.
Step 4 — Run the Initial Load
Before go-live, you need to populate S/4HANA Cloud with the existing approved Business Partner records from MDG CE.
Trigger the Initial Load in MDG CE
From MDG CE, initiate a full export of the relevant Business Partner set to MDI. This generates creation events for all in-scope Business Partners and pushes them through MDI to S/4HANA Cloud.
Monitor in MDI Cockpit
Track message processing in the MDI monitoring dashboard. Resolve any mapping or validation errors before proceeding. Common issues at this stage include missing required fields in ODM format and number range conflicts.
Validate in S/4HANA Cloud
Use theManage Business Partner Master DataorMaintain Business PartnerFiori apps in S/4HANA Cloud to verify that Business Partners have been created correctly, with the expected roles, company code data, and relationships.
Step 5 — Delta Distribution (Ongoing Operations)
Once the initial load is complete and go-live is confirmed, all subsequent changes follow the delta distribution path automatically:
A data steward creates or modifies a Business Partner in MDG CE via a change request.
The change request goes through the configured approval workflow (single-step or multi-step).
Upon approval, MDG CE emits an ODM-compliant event to MDI.
MDI processes the event and calls the S/4HANA Cloud inbound API.
S/4HANA Cloud creates or updates the Business Partner record in near real time
Common Pitfalls to Avoid
Number Range Mismatch
Not aligning external vs. internal numbering before go-live causes duplicate or conflicting BP records that are difficult to reconcile after the fact.
Incomplete BP Roles
Distributing a Business Partner without the customer or supplier role and the required transactional data means the BP cannot be used in S/4HANA Cloud processes.
Unmapped Extension Fields
Custom fields added in MDG CE that have no ODM mapping are silently dropped by MDI. Validate field coverage before go-live.
No Error Monitoring
Ignoring the MDI message monitor means failed distributions go unnoticed. Always set up alerting for error states in the MDI cockpit.
Skipping Duplicate Check
Not configuring MDG CE duplicate detection leads to multiple governance records for the same real-world Business Partner being distributed to S/4HANA Cloud.
Mixed Governance & Direct Entry
Allowing data stewards to create Business Partners directly in S/4HANA Cloud alongside MDG CE creates shadow records and breaks the single-source-of-truth model.
A step-by-step guide to governing Business Partner master data in SAP Master Data Governance, cloud edition and distributing it to SAP S/4HANA Public Cloud using SAP Master Data Integration.Many enterprises want SAP Master Data Governance (MDG), cloud edition to be the single source of truth for Business Partner data, with automatic distribution to Cloud ERP (alias SAP S/4HANA Public Cloud ). This blog walks you through the strategic integration path — using SAP Master Data Integration (MDI) as the hub .Overview & Solution ArchitectureSAP’s recommended and strategic integration topology for Business Partner master data distribution in a Public Cloud landscape is MDG, cloud edition governs the full lifecycle of Business Partner records — creation, enrichment, validation, approval, and deactivation — through structured change requests.SAP Master Data Integration (MDI) acts as the cloud-native distribution backbone. It uses SAP’s One Domain Model (ODM) to normalize Business Partner data across systems and routes approved records to all registered consumer systems.S/4HANA Public Cloud receives the Business Partner data via a standard inbound API, making it immediately available for Accounts Receivable, Accounts Payable, Sales, and Purchasing processes. PrerequisitesBefore starting the configuration, ensure the following are in place:SAP MDG, Cloud Edition tenant provisionedSAP Master Data Integration (MDI) tenantCloud ERP (alias S/4HANA Public Cloud ) tenant activeSAP BTP subaccount with MDI service instanceCommunication Admin role in Cloud ERP (alias S/4HANA Public Cloud )MDG Administrator role in MDG CENumber range strategy agreed upon Step 1 — Configure S/4HANA Public CloudS/4HANA Public Cloud must be prepared to receive inbound Business Partner data from MDI. This is done by setting up a Communication Arrangement that opens the inbound API channel.Activate the Master Data Integration scopeIn your S/4HANA Cloud tenant, confirm that scope item 1RO – Integration of Core Master Data is activated. This scope activates the relevant Fiori apps and communication scenarios for inbound master data replication. Create a Communication UserGo to the Maintain Communication Users Fiori app. Create a dedicated technical user (e.g., MDI_INBOUND) with a strong password. This user will authenticate MDI inbound calls. Create a Communication SystemGo to the Communication Systems Fiori app. Create a new system entry representing your MDI tenant. Provide the MDI tenant hostname and assign the communication user you created. Create a Communication ArrangementGo to Communication Arrangements. Create a new arrangement for the Business Partner – Master Data Integration Inbound scenario (look for the MDI inbound or SAP_COM_0008-family scenario relevant to your release). Assign the communication system created above. This exposes the inbound OData endpoint that MDI will call. Note the Service URLOnce saved, copy the inbound service URL shown in the arrangement. You will register this in MDI as the S/4HANA Cloud consumer endpoint. Step 2 — Set Up SAP Master Data IntegrationMDI is provisioned on SAP Business Technology Platform (BTP). You configure it to know about both your MDG CE tenant (provider) and your S/4HANA Cloud tenant (consumer).Create an MDI Service Instance on SAP BTPIn your BTP subaccount, subscribe to the SAP Master Data Integration service and create a service instance. Generate a service key — this provides the MDI API credentials and endpoint URL.Register S/4HANA Cloud as a ConsumerIn the MDI administration UI (or via MDI API), register the S/4HANA Cloud endpoint using the service URL and credentials noted in Step 1. Assign theBusiness Partnerand (if needed)Business Partner Relationshipdomains to this consumer. Register MDG CE as a ProviderRegister your MDG CE tenant in MDI as the provider for the Business Partner domain. MDI will accept events from MDG CE and distribute them to all registered consumers. Enable ODM DomainsIn MDI, enable the relevant One Domain Model (ODM) entity types: typicallysap.odm.businesspartner.BusinessPartner. If you distribute relationships, also enablesap.odm.businesspartner.BusinessPartnerRelationship. Configure Field Mappings (if needed)If MDG CE carries custom/extension fields that must flow to S/4HANA Cloud, define the field mappings in MDI. Standard SAP fields follow the ODM and require no mapping. Step 3 — Configure MDG, Cloud EditionMDG CE must be configured to govern Business Partners according to your process requirements and to publish approved data to MDI.Set Up Governance ProcessesDefine the change request types for Business Partner creation (and change/block/unblock workflows). Configure validations, duplicate checks, and enrichment rules as required by your data governance policies. Configure the Distribution ModelConfigure the Distribution Model in SAP Master Data Integration (MDI) using the application Manage Distribution Model . Add your MDI tenant as the distribution target for the Business Partner entity. This tells MDG CE to emit events to MDI upon change request approval. Activate the model. Once active, MDI will route Business Partner events from MDG CE to S/4HANA Cloud on every approved change request. Maintain MDI ConnectivityProvide the MDI service instance URL and credentials (from the BTP service key) in MDG CE’s outbound connectivity configuration. This enables MDG CE to push ODM-compliant events to MDI. Model BP Roles and StructuresEnsure that the BP roles (Customer, Supplier, Contact Person, etc. , except the Employee role.), organization types, and relevant data segments (company code data, sales area data, purchasing data) are represented in the MDG CE data model and change request forms. What is not governed in MDG CE will not be distributed to S/4HANA Cloud. Step 4 — Run the Initial LoadBefore go-live, you need to populate S/4HANA Cloud with the existing approved Business Partner records from MDG CE.Trigger the Initial Load in MDG CEFrom MDG CE, initiate a full export of the relevant Business Partner set to MDI. This generates creation events for all in-scope Business Partners and pushes them through MDI to S/4HANA Cloud. Monitor in MDI CockpitTrack message processing in the MDI monitoring dashboard. Resolve any mapping or validation errors before proceeding. Common issues at this stage include missing required fields in ODM format and number range conflicts. Validate in S/4HANA CloudUse the Manage Business Partner Master Data or Maintain Business Partner Fiori apps in S/4HANA Cloud to verify that Business Partners have been created correctly, with the expected roles, company code data, and relationships. Step 5 — Delta Distribution (Ongoing Operations)Once the initial load is complete and go-live is confirmed, all subsequent changes follow the delta distribution path automatically:A data steward creates or modifies a Business Partner in MDG CE via a change request.The change request goes through the configured approval workflow (single-step or multi-step).Upon approval, MDG CE emits an ODM-compliant event to MDI.MDI processes the event and calls the S/4HANA Cloud inbound API.S/4HANA Cloud creates or updates the Business Partner record in near real time Common Pitfalls to AvoidNumber Range MismatchNot aligning external vs. internal numbering before go-live causes duplicate or conflicting BP records that are difficult to reconcile after the fact.Incomplete BP RolesDistributing a Business Partner without the customer or supplier role and the required transactional data means the BP cannot be used in S/4HANA Cloud processes.Unmapped Extension FieldsCustom fields added in MDG CE that have no ODM mapping are silently dropped by MDI. Validate field coverage before go-live. No Error MonitoringIgnoring the MDI message monitor means failed distributions go unnoticed. Always set up alerting for error states in the MDI cockpit.Skipping Duplicate CheckNot configuring MDG CE duplicate detection leads to multiple governance records for the same real-world Business Partner being distributed to S/4HANA Cloud.Mixed Governance & Direct EntryAllowing data stewards to create Business Partners directly in S/4HANA Cloud alongside MDG CE creates shadow records and breaks the single-source-of-truth model. Read More Technology Blog Posts by SAP articles
