Exploring Multi-ERP Configurations


After completing this lesson, you will be able to Explore multi-ERP structures.

Multi-ERP Configurations

"Why do we need multi-ERP configurations?"

"Multi-ERP configurations give organizations the ability to integrate multiple SAP Ariba sites in a way that allows enterprise-wide data to be shared throughout the organization, while site-specific and transactional data remain separate."

A realm can be integrated with a single accounting system (or a single middleware if multiple ERPs have to be considered) to exchange transactional data.

All realms will share the same Buyer Account that is inherited from the parent realm.

By default, all child sites will have the same procurement or invoicing features which are inherited from the parent realm.

SAP Ariba realms are created to map to the accounting system they are integrated with, using different data models to manage ERP-specific data such as suppliers, accounting data.

An SAP Ariba realm's data model is based on its variant. A variant is a type of ERP system. There are three variants to choose from when defining a realm:

  • SAP
  • PeopleSoft
  • Generic

For instance, an SAP Ariba realm having an SAP variant will have its data model adapted to handle:

  • SAP specific organizational data: Company code, purchasing organization, and more.
  • SAP specific supplier data model
  • SAP specific accounting dimensions: General Ledger, Cost Center, WBS, and others.

For an understanding of the data flow in multi-ERP hierarchy configurations, watch this video.

To further understand multi-ERP configuration, let's look at the configuration options available for multi-ERP child sites.


Data does not flow between the parent site and child sites. It Is the only configuration supported for turning existing sites with transactions into child sites.

If Disconnected is chosen for one child site, it must be chosen for all other child sites under the same parent site.


Is available only if the child site is the same variant as the parent site.

Single-variant child sites receive fully rationalized cross-variant and variant-specific master data from the parent site. Additional data can be loaded into the child sties. Variant-specific user data can either be replicated or not. If it is not replicated, it is loaded directly into child sites.


The replication for the user data class can be disabled. All other data classes are replicated.


Multi-variant child sites receive cross-variant master data from the parent site. Variant-specific master data is loaded directly into child sites. The associated ERP systems are either different variants or have a significant amount of site-specific data.

Multi-variant and single-variant configurations can coexist in a multi-ERP configuration.

The image below summarizes the multi-ERP features supported by each configuration type.

Log in to track your progress & complete quizzes