If we observe more scenarios will create a version 2. We have penned down general areas where all SAP-MDG projects struggle with Ariba Integration. If you have come across such requirement in the past or have any useful pointers, please share how do we ensure that Duplicate check for External Supplier Request Tax ID considers legacy supplier data migrated from ECC to Ariba as well. Ariba SLP to MDG Integration & replication troubleshoot SeptemSummary: This blog post would help you save time and effort and not reinvent the wheel. However, Custom duplicate checks don't match against mapped data that originates from sources outside of supplier requests, such as data import, ERP integration, or other types of questionnaires as per Default Supplier Request Duplicate Checks and Setting Up Custom Duplicate Checks | SAP Help Portal. Since Tax answer type with default duplicate check is only supported on the Internal Supplier Request, we are planning to use an individual question mapped to tax field to collect Tax ID (ABN) info on External Supplier Request and apply custom duplicate check to it. We have a requirement to perform a Duplicate Check against Tax ID (Australian Business Number - ABN to be specific) that would be entered by suppliers on External (Self-Registration) Supplier Request and this Duplicate Check also needs to match against the supplier data imported/migrated from ERP to SLP.

Ariba slp integration with mdg