Explaining Integration Scenarios

Potential suppliers are only managed by SAP Supplier Lifecycle Management.

Global supplier master data can be enriched and changed within SAP Supplier Lifecycle Management and transferred to the master data system or vice versa.

Data for other segments are managed and distributed by the master data system.

The preceding figure explains the process to maintain potential suppliers in SLC.

This scenario shows what happens when a new supplier is requested in SAP Ariba Supplier Lifecycle and Performance, and no duplicate for the supplier is found in master data governance.

1. A new supplier is requested in SAP Ariba Supplier Lifecycle and Performance, and the supplier request is approved.
2. The supplier request workflow transfers the data to master data governance for validation as part of the Supplier Governance validation step.
3. In master data governance, a consolidation process is automatically created and started. No duplicates are found,...
4. … and the supplier is created in master data governance. The key mapping between the supplier ID in SAP Ariba Supplier Lifecycle and Performance and the Business Partner ID in master data governance is created.
5. The supplier is replicated from the master data governance hub to SAP Ariba Supplier Lifecycle and Performance and to the operational ERP, and - based on the confirmation - key mapping between the business partner ID in master data governance and the operational ERP is created in master data governance.
6. In SAP Ariba Supplier Lifecycle and Performance, the creation of the supplier is completed upon replication from master data governance. Depending on the SAP Ariba Supplier Lifecycle and Performance configuration, the supplier can be used further to manage the supplier lifecycle, and for transactional purposes depending on the customer's buying policy.

This scenario shows what happens when a new supplier is requested in SAP Ariba Supplier Lifecycle and Performance, a duplicate for the supplier is found in master data governance, and the business partner does not yet exist in SAP Ariba Supplier Lifecycle and Performance.

1. A new supplier is requested in SAP Ariba Supplier Lifecycle and Performance, and the supplier request is approved, and...
2. … the supplier request workflow transfers the data to master data governance for validation as part of the Supplier Governance validation step.
3. In master data governance, a consolidation process is automatically created and started. In the matching step, the supplier replicated from SAP Ariba Supplier Lifecycle and Performance is recognized as a duplicate of a business partner that already exists in master data governance. For example, this can be a customer that is not known in SAP Ariba Supplier Lifecycle and Performance. Master data governance creates a best record by merging the data of both business partners,...
4. … and the existing business partner is updated. The key mapping of the existing business partner in master data governance is enhanced by the SAP Ariba Supplier Lifecycle and Performance supplier ID.
5. The supplier is replicated from the master data governance hub to all connected client systems including SAP Ariba Supplier Lifecycle and Performance.
6. In SAP Ariba Supplier Lifecycle and Performance, the creation of the supplier is completed upon replication from master data governance.

This scenario shows what happens when a new supplier (BP 1002) is requested in SAP Ariba Supplier Lifecycle and Performance that already exists in SAP Ariba Supplier Lifecycle and Performance, SAP ERP, and master data governance. SAP Master Data Governance recognizes the supplier as a duplicate of a business partner in master data governance.

1. A new supplier (BP 1002) is requested in SAP Ariba Supplier Lifecycle and Performance as a duplicate of an already existing SAP Ariba Supplier Lifecycle and Performance supplier (BP 1001), for example, because the user did not search for it or did not find the existing supplier when searching, or because the user ignored the duplicate warning message when creating the supplier request in SAP Ariba Supplier Lifecycle and Performance.
2. In SAP Ariba Supplier Lifecycle and Performance, the supplier request is approved, and the supplier request workflow transfers the data via SOA Service to master data governance for validation as part of the Supplier Governance validation step.
3. In master data governance, a consolidation process is automatically created and started. In the matching step, the supplier replicated from SAP Ariba Supplier Lifecycle and Performance is recognized as a duplicate of a business partner that already exists in master data governance (BP 5001). Master data governance creates a best record by merging the data of both business partners,...
4. … and the existing business partner (BP 5001) is updated. The key mapping of the existing business partner in master data governance is enhanced resulting in two mappings towards SAP Ariba Supplier Lifecycle and Performance suppliers, which means both SAP Ariba Supplier Lifecycle and Performance suppliers will be updated based on the master data governance business partner.
5. The supplier is replicated from the Master Data Governance hub to all connected client systems including SAP Ariba Supplier Lifecycle and Performance.
6. In SAP Ariba Supplier Lifecycle and Performance, the workflow ends when the replication from master data governance is received, and the requestor is asked to use the already existing supplier (BP 1001). The newly created duplicate supplier is updated and deactivated (BP 1002), and the already existing supplier (BP 1001) is updated with the best record data from the Master Data Governance hub.

This scenario shows what happens when a new supplier is requested in SAP Ariba Supplier Lifecycle and Performance, and no duplicate for the supplier record is found in master data governance. Unlike scenario 1a, the supplier record is replicated to master data governance upon registration or qualification of the supplier.

1. A new supplier ABC corp. registers in SAP Ariba Supplier Lifecycle and Performance.
2. The supplier registration workflow transfers the data to master data governance via an SOA service.
3. In master data governance, a consolidation process is automatically created and started. No duplicates are found,...
4. … and the supplier is created in the master data governance hub. A new supplier as well as the Key Mapping was added to the SAP Ariba Supplier Lifecycle and Performance.
5. The supplier is replicated from the master data governance hub to SAP Ariba Supplier Lifecycle and Performance and to the operational ERP, and - based on the confirmation - key mapping between the business partner ID in master data governance and the operational ERP is created in master data governance.
6. The supplier data and master data governance number is stored in SAP Ariba Supplier Lifecycle and Performance.

This scenario shows what happens when a new supplier is requested in SAP Ariba Supplier Lifecycle and Performance, a duplicate for the supplier is found in master data governance, and the business partner does not yet exist in SAP Ariba Supplier Lifecycle and Performance. Unlike scenario 2a, the supplier record is replicated to master data governance upon registration or qualification of the supplier.

1. A new supplier ABC corp. (1001) registers in SAP Ariba Supplier Lifecycle and Performance.
2. The supplier registration workflow transfers the data to master data governance via an SOA service.
3. In master data governance, a consolidation process is automatically created and started. In the matching step, the supplier replicated from SAP Ariba Supplier Lifecycle and Performance is recognized as a duplicate of a business partner ABC corp. (5000) that already exists in master data governance and SAP ERP (2000). Master data governance creates a best record by merging the data of both business partners.
4. The supplier is created in SAP Master Data Governance hub system. The key mapping of the existing business partner in master data governance is added to the SAP Ariba Supplier Lifecycle and Performance.
5. The supplier is replicated from the master data governance hub to all connected client systems including SAP Ariba Supplier Lifecycle and Performance.
6. In SAP Ariba Supplier Lifecycle and Performance, the supplier data as well as the master data governance number is stored.

This scenario shows what happens when a new supplier is requested in SAP Ariba Supplier Lifecycle and Performance that already exists in SAP Ariba Supplier Lifecycle and Performance, and master data governance recognizes the supplier as a duplicate of a business partner in master data governance. Unlike scenario 3a, the supplier record is replicated to master data governance upon registration or qualification of the supplier.

This scenario shows what happens when a supplier is changed in master data governance.

This scenario shows what happens when a supplier is changed in SAP Ariba Supplier Lifecycle and Performance.

1. A supplier updates their existing supplier record in the Ariba Network, and the change is approved in SAP Ariba Supplier Lifecycle and Performance.
2. The changed record is sent to master data governance.
3. In master data governance, the change request process is triggered, and a master data specialist verifies and approves the record.
4. Once the record is activated in master data governance, it is replicated to all connected client systems including SAP Ariba Supplier Lifecycle and Performance.

This scenario shows what happens when a supplier is created in master data governance.

1. The creation of a new supplier is requested in master data governance. The central governance workflow is triggered, the request is processed, and the new supplier record is activated.
2. Master data governance then replicates the data to all client systems including SAP Ariba Supplier Lifecycle and Performance.

This scenario shows what happens when two active suppliers are merged in master data governance.

1. A user scans all business partners in master data governance for duplicates using the Remove Duplicates consolidation strategy. Two business partners are recognized as duplicates, so master data governance merges the data of both business partners and combines the key mapping information to create a best record. This means that from now on, the mapped records in SAP Ariba Supplier Lifecycle and Performance and ERP - two on SAP Ariba Supplier Lifecycle and Performance side, and two on ERP side - will be updated based on the best record.
2. Master data governance then replicates the data to all client systems including ERP and SAP Ariba Supplier Lifecycle and Performance. In ERP, both existing suppliers are kept because transactional data might exist. One of the suppliers can be archived at a later point. In SAP Ariba Supplier Lifecycle and Performance, both suppliers are kept, and both refer to the same business partner in master data governance. The duplicate supplier is deactivated in SAP Ariba Supplier Lifecycle and Performance.

You can find the documentation of the scenarios in the SAP Help Portal for SAP S/4HANA, Master Data Governance, Integration Topics: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/6d52de87aa0d4fb6a90924720a5b0549/da545e576e794bec9475dc1afe798974.html?locale=en-US

The following figure illustrates the process to create a customer as is without SAP Business Partner screening.

The following figure illustrates the process of a decision in master data governance (Screening by Master Data Specialist).

The following figure illustrates the process of a decision in master data governance (Screening by Master Data Specialist, guidance by a screening expert).

Further explanations:

Enrichment

Implemented as Enrichment Spot 'Address Screening' with corresponding adapter in master data governance.

Activate by Change Request Step

For each change request, Type Screening can be activated per the change request step.

Deployment Options

Business Partner Screening can run on a master data governance instance (the same SAP S/4HANA Database, with a different SAP NetWeaver AS) or on a different instance.

The figure illustrates the settings of the compliance check:

• Screening is automatically executed in the process steps being activated.
• A pop-up appears in the case of suspicions; the user can decide if it is a hit or not.
• Hits are logged within Business Partner Screening.
• The user is free to decide how to continue the change request process independent of a decision about a hit or not.

The following figure illustrates the automated screening of a business partner with the consulting of a compliance expert and the decision in Master Data Governance. Once the requested business partner was reviewed by a master data specialist, the workflow triggers the automatic screening in the background. If not hit was found, the purchasing specialist and financial specialist can maintain their attributes and the business partner can be approved. In case of an hit, the Compliance Expert will confirm hits, details the criticality and forward the request to the master data specialist who either rejects the business partner or forward it to purchasing specialist/financial specialist for further maintenance

The following figure illustrates the automated screening of a business partner and the decision in Master Data Governance. Once the requested business partner is reviewed by a master data specialist, the workflow triggers the automatic screening in the background. If no hit was found, the purchasing specialist and financial specialist can maintain their attributes, and the business partner can be approved. In case of a hit, the Compliance Expert will review hits, and defines result (hit or no hit and relevant list). Afterwards, this information is forwarded to the automatic interpretation of business partner screening, which results in a decision about follow-up action. In the next step, the automatic interpretation of business partner screening results rejects the creation of the business partner for business and asks the requestor to cancel the Change Request or rework the data.