Prepackaged Integration With SAP Master Data Governance: Public 2021-03-09

PUBLIC
2021-03-09
Prepackaged Integration with SAP Master Data

Governance
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Business Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Integration of MDG-C with SAP Cloud for Customer (C4C). . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

3.1 Set Up Integration of MDG-C with SAP Cloud for Customer (C4C). . . . . . . . . . . . . . . . . . . . . . . . . . .6
4 Technical Setup in SAP Cloud for Customer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.1 Business Partner Replication from SAP Master Data Governance with SAP Cloud for Customer
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Business Partner Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Confirmation of Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Business Partner Relationship Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.2 Business Partner Replication from SAP Cloud for Customer to SAP Master Data Governance. . . . . . .18
Business Partner Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Confirmation of Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Business Partner Relationship Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Confirmation of Business Partner Relationship Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.3 Key Mapping Replication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Prepackaged Integration with SAP Master Data Governance

2 PUBLIC Content
1 Overview
This document describes how to integrate SAP Cloud for Customer with SAP Master Data Governance for
business partner replication.

Overview PUBLIC 3
2 Business Scenario
An out-of-the box bi-directional replication with SAP Master Data Governance (MDG) is available for use in
business partner merge scenarios.
Following scenarios are supported:
● In the event of a business partner cleansing and consolidation process in SAP MDG, a merge case is
created in SAP Cloud for Customer.
● SAP Cloud for Customer executes merge process and automatically marks the oldest available record
(using creation date) as golden record.

4 PUBLIC Business Scenario
3 Integration of MDG-C with SAP Cloud for
Customer (C4C)
This documentation provides the information you need for the MDG-related configuration and Customizing
activities that must be carried out for the integration of SAP Cloud four Customer (C4C) with SAP Master Data
Governance (MDG) for Customer.
The figure below shows the communication between the systems involved.
Overview of MDG/C4C System Communication
For more information about Data Replication, see
Set Up Integration of MDG-C with SAP Cloud for Customer (C4C) [page 6]

Integration of MDG-C with SAP Cloud for Customer (C4C) PUBLIC 5
3.1 Set Up Integration of MDG-C with SAP Cloud for
Customer (C4C)
Use
This document describes the configuration steps that are required to enable the integration between SAP
Cloud for Customer (C4C) and SAP Master Data Governance (MDG) for Customer.
Prerequisites
Both Master Data Governance for Customer and Master Data Governance, Consolidation and Mass Processing
need to be set up according to the respective Configuration Guides.
The following SAP notes are a prerequisite and need to be implemented:
● 2414514
● 2733112
 Note
If this SAP Note is not implemented, there is a risk of data loss during data replication.
● 2734155
● 2704411
● 2573445
 Note
The data models used by C4C and SAP S/4HANA and those used by C4C and SAP ERP differ. This
difference is resolved by a C4C-specific application logic in the webservice inbound and outbound
processing. The application logic can be summarized as follows:
● A new system customizing parameter identifies the C4C system during data replication (both inbound
and outbound). The parameter invokes the specific business processing logic.
● C4C can use a different customer ID compared to the standard SAP business partner / customer ID.
The C4C ID can consist of up to 100 characters. Its format can be configured (e.g. length, pattern
format, alphanumeric). A corresponding attribute is added to the SAP business partner related web
services. The new ExternalID attribute is also included in the key mapping.
● C4C supports a single attribute for industries only. The SAP business partner can have one to many
assigned industries. One of the industries has to be marked as default. This difference has to be
considered during data replication. Therefore, C4C needs to send a new or updated industry without
setting the corresponding complete list transmission indicator. Setting this indicator is only required
for the deletion of the industry in C4C. In that case, C4C will not send any industries at all.
● C4C supports only a single attribute for landline and mobile phone numbers. The SAP business partner
can have one to many assigned (mobile) phone numbers. This difference has to be considered during
data replication. The implementation is done in the same way as for the industries.

6 PUBLIC Integration of MDG-C with SAP Cloud for Customer (C4C)
● The modelling of addresses and address usages differs. C4C stores all addresses and always sends the
addresses with a complete list transmission indicator. It is necessary to maintain the list of supported
address usages in segment filters of the data replication framework (DRF). The filters are used to
prevent that unknown address usages are sent to C4C. The inbound processing of messages from C4C
is enhanced, too. The incoming data is checked against existing data and, if needed, enriched with
existing data. This prevents the deletion of unknown data in SAP S/4HANA.
● Identifiers (identification numbers) and roles are handled in the same way as the address usages.
● Reduced model scope is supported for addresses. If attributes are not part of the sent record this will
not affect the record. For this, the Complete Transmission Indicator (CTI) must be set to false. All
addresses that are not part of the message will be deleted in MDG, even if the CTI is set to false.
Business partner central data (Common) is handled in the same way.
 Note
MDG-specific Customizing is located under SAP Customizing Implementation Guide Cross-Application

Components Processes and Tools for Enterprise Applications Master Data Governance . You can also
directly access MDG-specific Customizing using transaction MDGIMG for MDG-C and transaction MDCIMG
for Consolidation and Mass Processing.
Procedure
1. Define Data Replication Framework (DRF) Settings for Business Partner

1. Run transaction DRFIMG to open the Data Replication-specific Customizing.
2. Open the Customizing activity Define Technical Settings for Business Systems under Data
Replication Define Custom Settings for Data Replication Define Technical Settings .
3. In the Change View Define Bus. Systems, BOs, choose New Entries.
4. In the Define Bus. Systems, BOs table, enter the details for the new business system.
 Note
Make sure that you enter the same business system that is maintained as My System in the
Communication Arrangement in SAP Cloud for Customer.
5. Save your entries, and leave this view open to continue with the next steps.
2. Define C4C Business System and Define Storage Settings for Data Replication
1. Select the row that contains the business system you just added, and double-click on Define Bus.
Systems, BOs in the Dialog Structure on the left.
2. Choose New Entries and add BO Type 147 using the input help. Select the Sys. Filt. checkbox, and
select Direct Output as the Output Mode.
3. Select the row that contains the BO Type 147, and double-click on Define Bus. Systems, BOs,
Communication Channel in the Dialog Structure on the left.
4. Choose New Entries.
5. In the Define Bus. Systems, BOs, Communication Channel table, make the following entries, and save
your settings:

Communi Sup. Time Create Change
cation Key Harmo Update Key Depend Process Process
Channel nization Mapping Storage ency Template Template Reliable
Replication Key Map Deselect Staging Not Defined Select a Do not use Select
via Services ping checkbox Area Consolida Consolida checkbox
tion Process tion Process
Template. Template
You can add

templates
either by ac
tivating a BC
set, or by
creating
your own
templates
manually.
With these settings, an automatic consolidation process is triggered when a new data record is
created, while a change request process is triggered in central governance when a record is changed.
6. Save your entry.

7. Navigate back to the Data Replication-specific Customizing, or run transaction DRFIMG to open it.
8. Open the Customizing activity Define Replication Models under Data Replication Define Custom
Settings for Data Replication .
9. In the Change View Define Replication Model, choose New Entries.
10. In the Define Replication Model table, enter the details for the new replication model.
For example, enter C4C_BP as the Replication Model, and Business Partner C4C as the
Description. You can enter a number of Log Days to specify the log expiry time, for example, 50.
11. Save your entries.
12. In the Define Replication Model table, select the row that contains the replication model you just
created, and double-click on Assign Outbound Implementation in the Dialog Structure on the left.
13. Choose New Entries to define an Outbound Implementation, and enter the following values using the
input help:
○ Outbound Implementation: 986_3 Outbound Impl. for BP/REL via Services
○ Sequence: 1
○ Communication Channel: Replication via Services
○ Filter time: Filter After Change Analysis
14. Select the row added and double-click on Assign Target Systems for Repl. Model /Outb.Impl. in the
Dialog Structure.
15. In the Assign Target Systems for Repl. Model/Outb.Impl. table, choose New Entries, and use the input
help to add the name of the business system you entered in step 1d above.
16. Select the row that contains the business system you added, and choose Assign Outbound Parameter
in the Dialog Structure. Choose New Entry, and enter the following values:
○ Outb. Parameter: PACK_SIZE_BULK
○ Outb. Parameter Value: 20 (example value; enter a value to meet your requirements)

18. Return to the Define Replication Model view. Optionally, you can also add an expiration time for the log.
19. Save your replication model.
20.Select the newly created replication model, and choose Activate to activate it.
3. Configure the SOA Manager for Business Partner

1. Run transaction SOAMANAGER.
2. On the Service Administration tab, select Web Service Configuration.
3. In the Search Criteria, select Object Type as Consumer Proxy, and enter CO_MDG_BP_RPLCTRQ as
Object Name.
4. Choose Search, and select the CO_MDG_BP_RPLCTRQ link in the search results.
5. In the Define Logical Ports section, choose Create Manual Configuration .
6. Enter a Logical Port Name (for example, LP_C4C_BP) and a Description (for example, MDG C4C BP
Replication), select the Logical Port is Default checkbox, and choose Next.
7. Under Authentication Settings, select X.509 SSL Client Certificate, and select the SSL Client PSE
configured in STRUST.
 Note
For integration using basic authentication, select the User ID/Password (Basic) checkbox.
8. Choose Next.
9. For the HTTP Settings, make the following entries:
○ URL Access Path: Endpoint maintained in CPI
○ Computer Name of Access URL: Maintain workernode URL without https://
○ Enter the proxy details.
10. Choose Next.
11. Under Reliable Messaging (Asynchr.), select SAP RM as the RM Protocol. Under Message ID
(Synchronous), select SAP Message ID as Message ID Protocol. Under Metering of Service Calls, select
Basic Data Transfer as Data transfer scope, and Transfer via SOAP header as Transfer protocol.
12. Choose Next.
13. No entries are required for Identifiable Business Context. Leave the fields empty, and choose Next.
14. Choose Finish to finalize the creation of the logical port.
17. On the Service Administration tab, select Simplified Web Service Configuration.
18. Search for the object name BusinessPartnerSUITEBulkReplicateConfirmation_In.
19. In the Configure Service Definitions table, select the row that contains your entry, and choose Set
Selected.
 Note
For integration using basic authentication, the checkbox User Name/Password (Basic) needs to be
selected, and for a certificate-based authentication, the checkbox X.509 Client Certificate needs to
be selected.
20.Choose Save.
21. Choose Show Details to view the Access URL and verify that it is similar to the address for the receiver
system in the Iflow.

22. Repeat steps 3p - 3u for the following object names:
Object Name Description
BUSINESSPARTNERSUITEBULKREPLIC Business Partner Data Replication (Request)
BUSINESSPARTNERRELATIONSHIPSU1 Business Partner Relationship Confirmation
BUSINESSPARTNERRELATIONSHIPSUI Business Partner Relationship Data Replication (Re

quest)
4. Define Filter Criteria for Business Objects

1. Define Object Filters
1. Run transaction DRFF to open the Define Filter Criteria screen. In the Query by Replication Model -
All Replication Models table, select the row that contains the replication model you created in step
2j (for example, C4C_BP), and select Change. In the Filter Criteria to Include Business Objects
section, add roles that are relevant for the replication of your Business Partner records to the C4C
system.
For example, add BP Role is FLCU01, BUP002 and BUP001.
2. Define Segment Filters
1. To determine segment filter criteria, select the Show Segment Filters button. Select the Business
Object Business Partner Role. Switch to Edit mode and add filter criteria according to your
requirements.
For example, add BP Role FLCU01, BUP001, BUP002, BUP003. Save your entries.
2. Repeat these steps for the Business Objects Business Partner Address Usage and Business Partner
Identifier.
For example, for Address Usage, add Address Type is XXDEFAULT, POST_TO, SHIP_TO, and for
Identifier, add Identification Type is BUP001, BUP005, CRM002, HCM001).
5. Define Storage Settings for Data Replication
1. Run transaction DRFIMG to open the Data Replication-specific Customizing.
2. Open the Customizing activity Define Technical Settings for Business Systems under Data
Replication Define Custom Settings for Data Replication Define Technical Settings .
3. In the Define Business Systems table, select the row that contains the C4C Business System ID.
4. In the Dialog Structure, double-click Define Bus. Systems, BOs.
5. Choose New Entries, and add BO Type 1376.
6. Select the row that contains BO Type 1376, and double-click Define Bus. Systems, BOs,
Communication Channel in the Dialog Structure.
In the Define Bus. Systems, BOs, Communication Channel table, make the following entries, and save
your settings:
Communi
Sup. Time Create Change
cation Key Harmo Update Key Depend Process Process
Channel nization Mapping Storage ency Template Template Reliable
Replication Not relevant Deselect Not relevant Not defined Not relevant Not relevant Deselect
via Services checkbox checkbox

6. Define Data Replication Framework (DRF) Settings for Key Mapping
1. Run transaction DRFIMG to open the Data Replication Framework Customizing.
2. Open the Customizing activity Define Replication Models under Data Replication Define Custom
Settings for Data Replication .
3. In the Change View Define Replication Model, choose New Entries.
4. In the Define Replication Model table, enter the details for the new replication model.
For example, enter C4C_KEYMAP as the Replication Model, and Keymapping C4C as the Description.
6. In the Define Replication Model table, select the row that contains the replication model you just
created, and double-click on Assign Outbound Implementation in the Dialog Structure on the left.
7. Choose New Entries to define an Outbound Implementation, and enter the following values using the
input help:
○ Outbound Implementation: 1376 Outbound Impl. for Replication via Services
○ Communication Channel: Replication via Services
○ Filter time: Filter After Change Analysis
8. Select the row added and double-click on Assign Target Systems for Repl. Model /Outb.Impl. in the
Dialog Structure.
9. In the Assign Target Systems for Repl. Model/Outb.Impl. table, create a new entry and use the input
help to add the business system name of your C4C system.
10. Select the row that contains the business system you added, and choose Assign Outbound Parameter
in the Dialog Structure. Choose New Entry, and enter the following values:
○ Outb. Parameter: PACK_SIZE_BULK
○ Outb. Parameter Value: 1000 (example value; enter a value to meet your requirements)
12. Return to the Define Replication Model view. Optionally, you can specify an expiration time for the log in
the Log Days column.
13. Save your replication model.
14. Select the newly created replication model, and choose Activate to activate it.
Define Filter Criteria
1. Run transaction DRFF to define filter criteria for the replication.
2. In the Define Filter Criteria table, select your C4C key mapping replication model, and choose Change.
3. In the Filter Criteria to Include Business Objects section, enter the Business Object Types according to
your requirements.
For example, enter 147, 194, 986, 159.
Define Segment Filters
1. Select Show Segment Filters to define the segment filter criteria.
2. In the Segment Filer Objects table, enter filter criteria according to your requirements.
For example, for the Filter Object / Business Object Object Identifier Type, enter Object ID Type is 888,
918, 927, 924, and for the Filter Object / Business Object Business System, enter Object ID Type is
0Lo8BBU, and all relevant MDG and C4C business systems.
7. Configure the SOA Manager for Key Mapping
2. On the Service Administration tab, select Web Service Configuration.
3. Search for the object name KeyMappingBulkReplicateRequest_Out.

4. Select the Internal Name link of the service (CO_KEY_MAP_RPLCTRQ) in the search results.
5. In the Define Logical Ports section, choose Create Manual Configuration .
6. Enter a Logical Port Name (for example, C4C_KEYMAPPING) and a Description (for example, Key
Mapping C4C), select the Logical Port is Default checkbox, and choose Next.
7. Under Authentication Settings, select User ID / Password or X509. SSL Client Certificate depending on
your preference. If you select User ID / Password, enter the logon details you created for your
middleware (PI or CPI) system.
8. Choose Next.
9. Under URL Access Path, select Complete URL, and enter the URL.
10. Choose Next.
11. Under Reliable Messaging (Asynchr.), select SAP RM as the RM Protocol. Under Message ID
(Synchronous), select WS-A Message ID as Message ID Protocol. Under Metering of Service Calls, select
Enhanced Data Transfer as Data transfer scope, and Transfer via SOAP header as Transfer protocol.
12. Choose Next.
13. No entries are required for Identifiable Business Context. Leave the fields empty, and choose Next.
14. Choose Finish to finalize the creation of the logical port.
8. Activate C4C-Specific Processing
1. To set up the integration with C4C, run the Customizing activity Set Up Integration with Special
Consumer Systems under Master Data Governance, Central Governance Master Data Governance
for Customer .
2. In the View for table MDG_BP_SYS_PAR view, select the checkboxes for Filter Reflexive Partner
Functions Active (Flt.Rfl.Pf) and C4C Specific Processing Active (C4C) for your C4C business system.
Parent topic: Integration of MDG-C with SAP Cloud for Customer (C4C) [page 5]

4 Technical Setup in SAP Cloud for
Customer
Business Partner Replication from SAP Master Data Governance with SAP Cloud for Customer [page 13]
This document describes how to set up successful replication of business partners from SAP Master
Data Governance to SAP Cloud for Customer.
Business Partner Replication from SAP Cloud for Customer to SAP Master Data Governance [page 18]
This document describes how to set-up successful replication of business partners from SAP Cloud for
Customer to SAP Master Data Governance.
Key Mapping Replication [page 25]

For successful key mapping replication from SAP Master Data Governance to SAP Cloud for Customer,
complete the following technical setup in the respective systems.
4.1 Business Partner Replication from SAP Master Data

Governance with SAP Cloud for Customer
This document describes how to set up successful replication of business partners from SAP Master Data
Governance to SAP Cloud for Customer.
This integration can be completed in the following phases:
1. Business Partner Replication from SAP Master Data Governance to SAP Cloud for Customer [page 14]
2. Confirmation from SAP Cloud for Customer to SAP Master Data Governance [page 15]
3. Business Partner Relationship Replication from SAP Master Data Governance to SAP Cloud for Customer
[page 17]
Parent topic: Technical Setup in SAP Cloud for Customer [page 13]
Related Information

Technical Setup in SAP Cloud for Customer PUBLIC 13
4.1.1 Business Partner Replication
For successful replication of business partners from SAP Master Data Governance to SAP Cloud for Customer,
Setup in SAP Cloud for Customer
Scoping
Select the following scoping question.
Communication and Information Exchange Integration with External Applications Integration of Master
Data Do you want to replicate business partners from an external application to your cloud solution?
Code List Mapping

● BusinessPartnerRoleCode
Account Group from SAP ERP must be mapped to SAP Cloud for Customer. For example, FLCU01 from
SAP ERP must be mapped to CRM000 in SAP Cloud for Customer.
● PartyRoleCode
Account, Ship-To, Buyer, and Bill-To parties in SAP Cloud for Customer must be mapped to external values
in SAP ERP such as AG, WE, RG, and RE respectively.
Communication Arrangement
Create the following communication arrangement.
Business Partner Replication from SAP Business Suite
Setup in Middleware
For SAP Master Data Governance on SAP S/4HANA

SAP Cloud Platform Integration
Package IFlows
SAP Cloud for Customer Integration with SAP S/4HANA Replicate Business Partner from SAP Business Suite
Process Integration
Sender Interface Operation Mapping
BusinessPartnerSUITEBulkReplicateRequest_Out S4_C4C_BusinessPartnerReplicationIn
For SAP Master Data Governance on SAP ERP


14 PUBLIC Technical Setup in SAP Cloud for Customer
Package IFlows
SAP Hybris Cloud for Customer Integration with SAP ERP Replicate Business Partner from SAP MDG
Process Integration
BusinessPartnerSUITEBulkReplicateRequest_Out ERPBP_C4C_BusinessPartnerReplication
Setup in SAP ERP or SAP S/4HANA
Message Type
Asynchronous via services
Connectivity Report
Run the report RCOD_CREATE_CONNECTIVITY_SIMPL for the following questions:
● In SAP ERP: Do you want to replicate accounts and contacts from SAP MDG via SOAP services to your cloud
solution?
● In SAP S/4HANA: Do you want to replicate accounts and contacts from SAP S/4HANA to your cloud
solution?”
SOA Manager
CO_MDG_BP_RPLCTRQ
4.1.2 Confirmation of Replication
For confirmation of business partners from SAP Cloud for Customer to SAP Master Data Governance,
Scoping
Code List Mapping

Not applicable for this scenario.

Setup in Middleware

Package IFlows
SAP Cloud for Customer Integration with SAP S/4HANA Confirm Business Partner Replication to SAP Business Suite
Process Integration
BusinessPartnerReplicateConfirmationOut S4_C4C_BusinessPartnerReplicationIn

Package IFlows
SAP Hybris Cloud for Customer Integration with SAP ERP Confirm Business Partner Replication to SAP MDG
Process Integration
BusinessPartnerReplicateConfirmationOut S4_C4C_BusinessPartnerReplicationIn
Message Type
Connectivity Report
solution?
solution?

SOA Manager
BUSINESSPARTNERSUITEBULKREPLI1
4.1.3 Business Partner Relationship Replication
For successful replication of business partner relationships from SAP Master Data Governance to SAP Cloud
for Customer, complete the following technical setup in the respective systems.
Scoping
Code List Mapping
Account Group from SAP ERP must be mapped to SAP Cloud for Customer. For example, BUP001 from
Setup in Middleware
Package IFlows
SAP Cloud for Customer Integration with SAP S/4HANA Replicate Business Partner Relationship from SAP Business
Suite
Process Integration

BusinessPartnerRelationshipSUITEBulkReplicateRe S4_C4C_BusinessPartnerRelationshipReplicationIn
quest_Out

Package IFlows
SAP Hybris Cloud for Customer Integration with SAP ERP Replicate Business Partner Relationship from SAP MDG
Process Integration
BusinessPartnerRelationshipSUITEBulkReplicateRe ERPBP_C4C_BusinessPartnerRelationshipReplication
quest_Out
Message Type
Connectivity Report
solution?
solution?
SOA Manager
CO_MDG_BP_RELATIONSHIP_OUT
4.2 Business Partner Replication from SAP Cloud for

Customer to SAP Master Data Governance
This document describes how to set-up successful replication of business partners from SAP Cloud for
Customer to SAP Master Data Governance.
This integration can be completed in the following phases:
1. Business Partner Replication [page 19]

2. Confirmation of Replication [page 21]

3. Business Partner Relationship Replication [page 22]
4. Business Partner Relationship Replication [page 24]
Related Information
4.2.1 Business Partner Replication
For successful replication of business partner from SAP Cloud for Customer to SAP Master Data Governance,
Scoping
Data Do you want to replicate business partners from your cloud solution to an external application?
Code List Mapping
Account Group from SAP ERP must be mapped to SAP Cloud for Customer. For example, FLCU01 from
● PartyRoleCode
Account, Ship-To, Buyer, and Bill-To parties in SAP Cloud for Customer must be mapped to external values
in SAP ERP such as AG, WE, RG, and RE respectively.
Business Partner Replication to SAP Business Suite

Setup in Middleware
Package IFlows
SAP Cloud for Customer Integration with SAP S/4HANA Replicate Business Partner to Business Suite
Process Integration
BusinessPartnerReplicationSelfInitiatedOut C4C_S4_BusinessPartnerReplicationIn
Package IFlows
SAP Hybris Cloud for Customer Integration with SAP ERP Replicate Business Partner to SAP MDG
Process Integration
BusinessPartnerReplicationSelfInitiatedOut C4C_ERPBP_BusinessPartnerReplication
Message Type
Connectivity Report
● In SAP ERP: Do you want to replicate accounts and contacts from your cloud solution via SOAP services to
SAP MDG?
● In SAP S/4HANA: Do you want to replicate accounts and contacts from your cloud solution to SAP S/
4HANA?
SOA Manager
BUSINESSPARTNERSUITBULKREPLIC

4.2.2 Confirmation of Replication
For confirmation of business partners from SAP Master Data Governance to SAP Cloud for Customer,
Scoping
Code List Mapping

Setup in Middleware

Package IFlows
SAP Cloud for Customer Integration with SAP S/4HANA Confirm Business Partner Replication from SAP Business
Suite
Process Integration
BusinessPartnerSUITEBulkReplicateConfirmation_Out BusinessPartnerReplicationConfirmationIn

Package IFlows
SAP Hybris Cloud for Customer Integration with SAP ERP Confirm Business Partner Replication from SAP MDG
Process Integration

BusinessPartnerSUITEBulkReplicateConfirmation_Out BusinessPartnerReplicationConfirmationIn
Message Type
Connectivity Report
SAP MDG?
4HANA?
SOA Manager
CO_MDG_BP_RPLCTCO
4.2.3 Business Partner Relationship Replication
For successful replication of business partner relationships from SAP Cloud for Customer to SAP Master Data
Governance, complete the following technical setup in the respective systems.
Scoping
Code List Mapping

Account Group from SAP ERP must be mapped to SAP Cloud for Customer. For example, BUP001 from

Setup in Middleware
Package IFlows
SAP Cloud for Customer Integration with SAP S/4HANA Replicate Business Partner Relationship to SAP Business
Suite
Process Integration
BusinessPartnerRelationshipReplicationSelfInitiatedOut C4C_S4_BusinessPartnerRelationshipReplicationIn
Package IFlows
SAP Hybris Cloud for Customer Integration with SAP ERP Replicate Business Partner Relationship to SAP MDG
Process Integration
BusinessPartnerRelationshipReplicationSelfInitiatedOut C4C_ERPBP_BusinessPartnerRelationshipReplication
Message Type
Connectivity Report
SAP MDG?
4HANA?
SOA Manager
BUSINESSPARTNERRELATIONSHIPSUI

4.2.4 Confirmation of Business Partner Relationship
Replication
For confirmation of business partner relationships replication from SAP Master Data Governance to SAP Cloud
for Customer, complete the following technical setup in the respective systems.
Scoping
Code List Mapping
Setup in Middleware
Package IFlows
SAP Cloud for Customer Integration with SAP S/4HANA Confirm Business Partner Replication from SAP Business
Suite
Process Integration
BusinessPartnerRelationshipSUITEBulkReplicateConfirma- BusinessPartnerRelationshipReplicationSelfInitiatedIn
tion_Out

Package IFlows
SAP Hybris Cloud for Customer Integration with SAP ERP Confirm Business Partner Replication from SAP MDG
Process Integration
BusinessPartnerRelationshipSUITEBulkReplicateConfirma- BusinessPartnerRelationshipReplicationSelfInitiatedIn
tion_Out
Message Type
Connectivity Report
SAP MDG?
4HANA?
SOA Manager
CO_MDG_BP_RELATIONSHIP_OUT
4.3 Key Mapping Replication
For successful key mapping replication from SAP Master Data Governance to SAP Cloud for Customer,
Scoping
Code List Mapping


ID Mapping Replication from SAP Business Suite
Setup in Middleware

Package IFlows
SAP Cloud for Customer Integration with SAP S/4HANA Replicate Key Mapping from SAP Business Suite
Process Integration
KeyMappingBulkReplicateRequest_Out S4_C4C_KeyMappingReplicationIn

Package IFlows
SAP Hybris Cloud for Customer Integration with SAP ERP Replicate ID Mapping from SAP Business Suite
Process Integration
KeyMappingBulkReplicateRequest_Out ERPBP_C4C_KeyMappingReplication
Message Type
Connectivity Report
● In SAP ERP: Do you want to replicate key mapping from SAP MDG to your cloud solution?
● In SAP S/4HANA: Do you want to replicate Key Mapping from SAP S/4HANA to your cloud solution?
SOA Manager
CO_KEY_MAP_RPLCTRQ

Related Information

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

28 PUBLIC Important Disclaimers and Legal Information
Important Disclaimers and Legal Information PUBLIC 29
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Prepackaged Integration With SAP Master Data Governance: Public 2021-03-09

Uploaded by

Copyright:

Available Formats

Prepackaged Integration With SAP Master Data Governance: Public 2021-03-09

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Prepackaged Integration With SAP Master Data Governance: Public 2021-03-09

Uploaded by

Copyright:

Available Formats

PUBLIC

Prepackaged Integration with SAP Master Data

THE BEST RUN

3 Integration of MDG-C with SAP Cloud for Customer (C4C). . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

4 Technical Setup in SAP Cloud for Customer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Prepackaged Integration with SAP Master Data Governance

Prepackaged Integration with SAP Master Data Governance

Following scenarios are supported:

Prepackaged Integration with SAP Master Data Governance

Overview of MDG/C4C System Communication

For more information about Data Replication, see

Prepackaged Integration with SAP Master Data Governance

The following SAP notes are a prerequisite and need to be implemented:

Prepackaged Integration with SAP Master Data Governance

MDG-specific Customizing is located under SAP Customizing Implementation Guide Cross-Application

1. Define Data Replication Framework (DRF) Settings for Business Partner

Prepackaged Integration with SAP Master Data Governance

You can add

6. Save your entry.

Prepackaged Integration with SAP Master Data Governance

3. Configure the SOA Manager for Business Partner

Prepackaged Integration with SAP Master Data Governance

Object Name Description

BUSINESSPARTNERSUITEBULKREPLIC Business Partner Data Replication (Request)

BUSINESSPARTNERRELATIONSHIPSU1 Business Partner Relationship Confirmation

BUSINESSPARTNERRELATIONSHIPSUI Business Partner Relationship Data Replication (Re­

4. Define Filter Criteria for Business Objects

Prepackaged Integration with SAP Master Data Governance

Prepackaged Integration with SAP Master Data Governance

Prepackaged Integration with SAP Master Data Governance

Key Mapping Replication [page 25]

4.1 Business Partner Replication from SAP Master Data

This integration can be completed in the following phases:

Prepackaged Integration with SAP Master Data Governance

Setup in SAP Cloud for Customer

Code List Mapping

Business Partner Replication from SAP Business Suite

For SAP Master Data Governance on SAP S/4HANA

Sender Interface Operation Mapping

For SAP Master Data Governance on SAP ERP

Prepackaged Integration with SAP Master Data Governance

Sender Interface Operation Mapping

Setup in SAP ERP or SAP S/4HANA

4.1.2 Confirmation of Replication

Setup in SAP Cloud for Customer

Code List Mapping

Prepackaged Integration with SAP Master Data Governance

Business Partner Replication from SAP Business Suite

For SAP Master Data Governance on SAP S/4HANA

Sender Interface Operation Mapping

For SAP Master Data Governance on SAP ERP

Sender Interface Operation Mapping

Setup in SAP ERP or SAP S/4HANA

Prepackaged Integration with SAP Master Data Governance

4.1.3 Business Partner Relationship Replication

Setup in SAP Cloud for Customer

Select the following scoping question.

Code List Mapping

Create the following communication arrangement.

BUSINESSPARTNERRELATIONSHIPSUI Business Partner Relationship Data Replication (Re