Master data plays a crucial role in the procurement process as it provides a foundation for various activities such as sourcing, purchasing, and invoicing. In a multi-ERP environment, where multiple enterprise resource planning (ERP) systems are integrated with SAP Ariba Procurement, it becomes essential to import master data from these systems to ensure accurate and consistent information across the procurement process.
Master Data in a Multi-ERP-Enabled Environment
Master data integration between SAP ERP or SAP S/4HANA (on premise) and the SAP Ariba Procurement solutions supports export of Master Data to the SAP Ariba Procurement solutions in multi-ERP-enabled environments.
Buyers using the SAP Ariba Procurement solutions integrated with SAP ERP or SAP S/4HANA (on premise) can export the master data to multi-ERP-enabled environment and specify the site or realm name of SAP Ariba Procurement solutions to which they want to export the master data.
To export master data for multi-ERP-enabled environment, on the program execution screen in SAP ERP or SAP S/4HANA (on premise), you must select FPC ENABLED option in the window Export All Master Data Required for On-Demand Applications. You can specify the name of the site to which you want to export the master data in the Site field. In a multi-ERP-enabled environment, you can export the same set of master data to multiple sites.
You can export the following types of master data from SAP ERP or SAP S/4HANA (on premise) to multi-ERP-enabled environment of SAP Ariba Procurement solutions:
- Organizational Data
- Accounting Data
- Cross-application Configuration Data
- Supplier Related Data
- User Related Data
The Managed Gateway Add-On’s master data extract program in SAP ERP or SAP S/4HANA (on premise) supports both full load and incremental load export of the master data.
Prerequisites
Before importing master data in a multi-ERP environment, be sure these prerequisites have been met:
Configure required Direct Connectivity or Mediated Connectivity settings.
- Maintain Supplier Locations and Remittance Locations, and User Profiles in SAP ERP or SAP S/4HANA (on premise).
Maintain the parameter CHANGELOG_RETENTION_DAYS before exporting the Master Data for multi-ERP or FPC-Enabled environment.
If you are upgrading from a non-multi-ERP system to Federated Process Control-based system, configure the Maintain Date TimeStamp for Master Data settings in SAP ERP or SAP S/4HANA (on premise).
Limitations
It is important to consider the following limitations when importing master data in a multi-ERP environment:
- The Remittance Location data is linked to the Supplier Location. When you export Remittance Location, even if you choose only the Remittance Location for export, the Managed Gateway Add-On’s master data extract program extracts the corresponding Supplier Location information as well. When you export Supplier Location in the incremental load mode after exporting Remittance Location, the export does not contain those Supplier Location records that you have extracted while exporting Remittance Location master data.
- Remittance Location option is not available for SAP AribaBuying solution users.
- A System ID of your SAP ERP or SAP S/4HANA (on premise) can be associated with only one Realm ID of SAP Ariba Procurement solutions. If you have multiple backend systems and all the backend systems use the same integration method as a part of their connection setup, you can use custom mapping and custom routing utilities to transmit documents from the same Realm ID to the required backend system.
Incremental Export of Master Data to Multi-ERP-Enabled Systems
When you run the incremental export of master data to multi-ERP-Enabled environment, the Managed Gateway Add-On’s master data extract program uses a combination of the following three variables to ensure that the incremental master data is available to all sites to which you want to perform incremental exports:
- Site information
- Date and time stamp
- Retention Period
The Managed Gateway Add-On’s master data extract program tags each of the records that you export with the date and time of the export and the name of the site to which you export the record. It also uses the site information and date and time stamp to identify the records to be exported when a new incremental export is triggered.
You must configure the parameter CHANGELOG_RETENTION_DAYS to specify the number of days you want SAP ERP or SAP S/4HANA (on premise) to retain the change records in the table ARBCIG_CHANGEDOC. When the configured retention period expires, SAP ERP or SAP S/4HANA (on premise) clears the change log.
If you select the FPC ENABLED option, and do not maintain a value for the parameter CHANGELOG_RETENTION_DAYS, the Managed Gateway Add-On’s Master Data extract program returns an error when you attempt to run the program.
Segregation of Supplier and User Master Data Elements for Specific Sites
- You can segregate various elements of the Supplier and User Master Data, and send subsets or supersets based on the specific requirements.
- You can choose to segregate the Supplier Master Data into various Master Data elements based on the specific requirements of the site to which you export the Supplier Master Data. The Supplier Master Data segregation options include Supplier Location, Supplier Purchase Organization, and Remittance Location.
- You can choose to export either the User or the User Group Master Data, or both.
- When you export User Master Data to a parent site, only those master data elements that are relevant for the parent site will be exported. If the realm is not marked as a parent realm, only those master data fields that are relevant for a child site will be exported.
- The parent and child differentiation applies only to User and Supplier Master Data events.
| CSV Filename | Applicable Site |
|---|---|
| UserConsolidated.csv | Parent and child sites |
| SupplierConsolidated.csv | Parent and child sites |
| GroupConsolidated.csv | Child sites |
| PurchaseOrgSupplierCombo.csv | Child sites |
| RemittanceLocationConsolidated.csv | Child sites |
| SupplierLocationConsolidated.csv | Child sites |