In this lesson, you’ll learn how to require approved supplier requests to be validated in the SAP Master Data Governance for Suppliers (MDG-S) module before SAP Ariba Supplier Management solutions create the new supplier database record.
Requiring SAP MDG-S validation and approval for supplier creation in SAP Ariba Supplier Lifecycle and Performance ensures accurate, compliant, and risk-free supplier data across the enterprise, improving data governance, procurement efficiency, and regulatory compliance. This activity ensures high-quality, validated, and compliant supplier master data before supplier records are created in the ERP system.
The default behavior is that SAP Ariba Supplier Lifecycle and Performance immediately creates a new supplier in SAP ERP when a supplier request is approved. But suppose the "Enable external validation of supplier creation" feature is activated. In that case, the supplier data is sent to SAP MDG-S for validation before creating a record in the SAP ERP.
The Enable external validation of supplier creationin ERP or MDG setting is designed to work with ERP configurations that use SAP MDG-S for Supplier Master Data Management. It does not work with SAP ERP configurations that do not include MDG-S.
Note
Contact SAP Ariba Customer Support to activate the Enable external validation of supplier creation feature.
Enable external validation of supplier creation is an optional feature and can be used only by customers with a standalone SAP MDG-S (installed on a separate box/machine).
The Enable external validation of supplier creation in MDG-S setting is designed for customers who maintain corporate-level business partners (suppliers and customers) in SAP MDG-S and use MDG-S to perform duplicate SAP Business Partner Screening and vendor record enrichment.
This setting allows you to send approved supplier requests to SAP MDG-S, where they are validated against both supplier and customer business partners. Any duplicates are identified, and information such as address and Dun & Bradstreet ID are validated and corrected if necessary, based on the information in SAP MDG-S, which is always the source of truth in this scenario. This validation occurs before the supplier record is created in SAP Ariba Supplier Lifecycle and Performance, which is especially important for preventing the creation of duplicate supplier records in some circumstances.
By default, SAP Ariba Supplier Lifecycle and Performance only checks for duplicate suppliers within the SAP Ariba vendor database. In cases where there is a second approved supplier request for what SAP MDG-S recognizes as an already existing and synchronized supplier, there can be duplicate separate records in SAP Ariba Supplier Lifecycle and Performance that correspond to one supplier record with multiple SM_ID key mappings in SAP MDG-S. There is no way to merge multiple supplier records or SM IDs in SAP Ariba Supplier Lifecycle and Performacne. So, every new supplier created will be validated in the MDG system, and if a duplicate is found, it will be marked as inactive.