PUBLIC

Document Version: 2311 – 2023-11

Multi-ERP Configuration Guide

SAP Ariba Buying and Invoicing, multi-ERP edition
SAP Ariba Buying, multi-ERP edition
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

Multi-ERP Configuration Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Overview of Multi-ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Terminology Specific to Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Introduction to Parent and Child Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Replication Configuration Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Data Flow in Single- and Multi-Variant Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Shared Customer Catalog Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Interaction Between SAP Business Network and multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . 11
Cross-Site Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Suite Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Migration of Existing Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Purchasing Units Vs. Multi-ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Deployment Process Overview for Multi-ERP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Deployment Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Disconnected Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Data Considerations for Deploying Disconnected Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . 17
Migration of Multiple Existing Sites to a Disconnected Multi-ERP Configuration. . . . . . . . . . . . . . . . . 17
Migration of a Single Existing Site to a Disconnected Multi-ERP Configuration. . . . . . . . . . . . . . . . . . 18
Deployment of New, Disconnected Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Single- and Multi-Variant Multi-ERP Deployments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Data Replication in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

General Information About Enterprise-Wide Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
User and Group Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Supplier Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Accounting Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Customer Catalog Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Strings and Enumerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Approval Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Inherited Parameter Values in Child Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Flex Fields, Field Properties, EForm Templates, and AML Customizations. . . . . . . . . . . . . . . . . . . . . 27
Customization Replication Failures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
The Replication Setup User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Master Data Rationalization in Multi-ERP Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Multi-ERP Configuration Guide

2 PUBLIC Content
 Data Rationalization for Multi-ERP Using Consolidated CSV Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Data Rationalization for Multi-ERP Using Legacy (Non-Consolidated) Files. . . . . . . . . . . . . . . . . . . . . . . 32
User and Group Data Rationalization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
User Data in Single-Variant Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Rationalizing User Data for Multi-Variant Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Supplier Data Rationalization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Understanding the Supplier Data Import Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Rationalizing Supplier Data for Single-Variant Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Supplier Data in Multi-Variant Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Rationalizing Application Configuration Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Rationalization of Invoice Exception Types and Invoice Exception Type Overrides. . . . . . . . . . . . . . . . . . 43

Deploying Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Setting Up the Parent Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Setting Up Child Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Setting Up the Reporting Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Setting Up Communication with SAP Business Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Configuring an Existing SAP Business Network Buyer Account for Multi-ERP Support. . . . . . . . . . . . 46
Configuring Business Application System IDs in SAP Business Network Accounts. . . . . . . . . . . . . . . 46
Configuring SAP Business Network End Points for Child Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Setting the Business Application System ID in a Child Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Loading Data into the Parent Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Configuring Replication for Child Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Setting the Data Replication Configuration Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Checking Replication Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Replication Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Subscribing to Customer Catalog Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Child Site Customizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Loading Site-Specific Data into Child Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Multi-ERP Configuration Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Push Multi-ERP Configurations from Test to Production. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Maintaining Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Pushing Transactional Data to External ERP Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Performing Incremental Data Loads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Modifying Replicated Data in Child Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Switching Supplier Organizations from Site-Specific to Enterprise-Wide. . . . . . . . . . . . . . . . . . . . . . . . 56
Supplier ID Conflicts in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Editing Supplier Organization Data, and Removing Links Between Suppliers and Automatically
Generated Supplier Organizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Removing Incorrect Data from a Child Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Replicating the Correct Supplier Organizations from the Parent Site and Establishing Links to
Suppliers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Multi-ERP Configuration Guide

Content PUBLIC 3
 Remote Authentication in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Overriding an Inherited Approval Process in a Child Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Child Site Customizations in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Overriding Inherited Parameter Values in Child Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Modifying Flex Fields and Standard AML Customizations in Child Sites. . . . . . . . . . . . . . . . . . . . . . . 61

Multi-ERP Features for Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Switching Between Sites in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
User Profile Information in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Cross-Site Reporting in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Reassigning Invoices in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Making a Contract Available to All Child Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Integration with SAP Ariba Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Approval Delegation in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Data Replication Reference for Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

Cross-Variant Data Classes and CSV Files in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . .67
Variant-Specific Data Classes and CSV Files in Multi-ERP Configurations. . . . . . . . . . . . . . . . . . . . . . . . 69
Variant-Specific Data Classes: PeopleSoft Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Variant-Specific Data Classes: SAP Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Variant-Specific Data Classes: Generic Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
CSV File Replication Reference for PeopleSoft Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
CSV File Replication Reference for SAP Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
CSV File Replication Reference for Generic Variants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Multi-ERP Configuration Guide

4 PUBLIC Content
Multi-ERP Configuration Guide

This guide is for SAP Ariba administrators who need to know how SAP Ariba multi-ERP configurations work and
how to set up parent and child sites with the help of SAP Ariba.

Buyer organizations can integrate multiple SAP Ariba sites in a way that allows enterprise-wide data to be shared
between sites while site-specific and transactional data remain separate.

This guide applies to:

• SAP Ariba Buying

• SAP Ariba Buying and Invoicing
• SAP Ariba Invoice Management

Multi-ERP Configuration Guide

Multi-ERP Configuration Guide PUBLIC 5
Overview of Multi-ERP

With multi-ERP support, organizations can 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 remains separate.

Each site can be associated with a separate enterprise resource planning (ERP) system. The level of integration
between sites varies depending on the type of configuration implemented. The most basic level of integration
provides cross-site reporting. More complex levels of integration also involve partial or full data sharing between
sites.

Highly integrated multi-ERP configurations offer the following benefits:

• Cost-effective administration across ERP systems

• Shared data, configuration settings, approval rules, and customization settings
• Shared contracts
• Cross-site reporting (available for all multi-ERP configurations)
• Invoice reassignment capability on invoices from SAP Business Network (available for all multi-ERP
configurations)
• Shared customer catalog content
• Suite integration, including contract management integration

This guide explains how to set up customers with multiple, integrated procurement and invoicing solution sites
from SAP Ariba to support the various ERP systems that they have. It focuses on the aspects of deployment that
pertain specifically to consolidating multiple sites. It assumes an understanding of ERP integration, data import,
and service administration.

SAP Ariba representatives can refer to the SAP Ariba Procurement solutions service administration guide for general
information about deploying sites.

Terminology Specific to Multi-ERP Configurations [page 7]

Introduction to Parent and Child Sites [page 7]

Replication Configuration Types [page 8]

Data Flow in Single- and Multi-Variant Configurations [page 9]

Shared Customer Catalog Content [page 11]

Interaction Between SAP Business Network and multi-ERP Configurations [page 11]

Cross-Site Reports [page 13]

Suite Integration [page 13]

Migration of Existing Sites [page 14]

Purchasing Units Vs. Multi-ERP [page 15]

Related Information

Multi-ERP Configuration Guide

6 PUBLIC Overview of Multi-ERP
Tax and Charge Configuration
Integrating SAP Ariba cloud solutions procurement and invoicing data with SAP ERP and SAP S/4HANA
Common Data Import and Administration for SAP Ariba Procurement Solutions
Procurement Data Import and Administration Guide
SAP Ariba integration toolkit guide
SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network Configuration Guide

Terminology Specific to Multi-ERP Configurations

The following table lists multi-ERP terminology.

Term Description

Master data Non-transactional data such as users, groups, and commodity codes.

Enterprise-wide data Master data that is shared by multiple sites.

Site-specific data Master data specific to a site, for example, accounting data. Also, all transactional data.

Variant Type of ERP system. SAP, PeopleSoft, and Generic are variants.

Cross-variant Common to all ERP variants. Cross-variant fields are fields common to all types of ERP systems.

Variant-specific Specific to one ERP variant. Variant-specific fields are fields used by one variant but not others.

Cross-site Across multiple sites. For example, cross-site reporting pulls data from multiple sites.

Configuration Determines the level of integration between sites. There are three configuration types: disconnected
(the most basic level of integration), multi-variant, and single-variant. For information, see About
Replication Configuration Types [page 8].

Introduction to Parent and Child Sites

To implement multi-ERP configurations, SAP Ariba uses a parent site – child site model. One parent site groups all
the child sites together. There is no limit to the number of child sites associated with a parent site.

Figure 1: Parent and Child Sites

Multi-ERP Configuration Guide

Overview of Multi-ERP PUBLIC 7
Each child site can be associated with one ERP system. The ERP systems the child sites are associated with can be
of the same variant or different variants. ERP systems of the same variant do not need to be of the same version.

In single- and multi-variant configurations, the parent site holds enterprise-wide master data and configuration
settings that it pushes to the child sites. The flow of data between sites is covered in more detail in the section
About Data Flow in Single- and Multi-Variant Configurations [page 9].

Figure 2: Data Flow in multi-ERP Configurations

All child sites have the same procurement or invoicing solution feature set, which they inherit from the parent site.
(A feature set, which SAP Ariba configures for you in the site profile, is the set of SAP Ariba solutions available
on a site. Examples are SAP Ariba Buying and Invoicing, SAP Ariba Invoice Management, and SAP Ariba mobile
app capabilities .) If a child site does not use an inherited feature, it can be hidden from users through group
membership.

Replication Configuration Types

There are three configuration options for multi-ERP child sites: disconnected, single-variant, and multi-variant.

The configuration of a child site determines which data is replicated from the parent site to the child site—no data
at all, cross-variant master data only, or cross-variant and variant-specific master data. Configurations are set by
an SAP Ariba representative.

 Note

The configuration options available depend on the ERP system variants. In the case of SAP Ariba Invoice
Management, the options also depend on whether you are deploying a new system or migrating an existing
standalone system.

The following table describes the configuration types.

Multi-ERP Configuration Guide

8 PUBLIC Overview of Multi-ERP
 Configuration Type Description

Disconnected In the Disconnected configuration, data does not flow between the parent site and child sites. This
configuration supports cross-site reporting, site switching, and invoice reassignment only. 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.

Single-variant 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 sites. Variant-specific user data can either be replicated or not. If it is not
replicated, you load it directly into child sites.

 Note
The User data class is the only data class for which replication can be disabled. All other data
classes are replicated.

Multi-variant Multi-variant child sites receive cross-variant master data from the parent site. You load variant-spe-
cific master data directly into child sites. The associated ERP systems either are of 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 following table shows the multi-ERP features supported by each configuration type.

Feature Disconnected Single-Variant Multi-Variant

Cross-site reporting Yes Yes Yes

Invoice reassignment between sites Yes Yes Yes

Site switching Yes Yes Yes

Cross-site global contracts No Yes Yes

Shared customer catalog content No Yes Yes

SAP Ariba Contracts integration No Yes Yes

Common data server (CDS) integration No Yes, with parent site Yes, with parent site

Site-specific procurement solution feature No No No

sets

Data Flow in Single- and Multi-Variant Configurations

In single- and multi-variant multi-ERP configurations, some processes are centralized, and others might be site-
specific. Enterprise-wide master data is shared between sites, but sites can have site-specific master data, too.
Transactional data resides in the child sites.

The following figure shows the flow of ERP master data through a multi-ERP system.

Multi-ERP Configuration Guide

Overview of Multi-ERP PUBLIC 9
 Figure 3: Flow of ERP Master Data

In single- and multi-variant configurations, the parent site receives enterprise-wide, cross-variant master data from
the data transfer tool. The master data then flows to the child sites. Each child site can also receive site-specific
data from the data transfer tool. Inherited approval rules, customizations, and parameter values can be overridden
at the child site level.

The common data server (CDS) pushes system data such as global currencies to the parent site. The parent site
pushes this data to the child sites automatically during replication.

Multi-ERP Configuration Guide

10 PUBLIC Overview of Multi-ERP
Shared Customer Catalog Content
In single- and multi-variant configurations, child sites subscribe to customer catalog content, which resides in the
parent site. Child sites can subscribe to either all content or specific portions. From each child site, you can access
only the customer catalog content to which that child site subscribes.

In disconnected configurations, each child site contains its own customer catalog content, which is not shared
between sites.

All customer catalog types are supported with multi-ERP: CIF, PunchOut, and Level 2 PunchOut.

If SAP Ariba changes the configuration type of a child site from disconnected to single- or multi-variant, they also
reload customer catalog types to ensure accuracy of customer catalog data.

Interaction Between SAP Business Network and

multi-ERP Configurations
All related child sites interact with SAP Business Network through one buyer account configured to support
multi-ERP.

 Note

The SAP Business Network capabilities discussed in this section are covered in more detail in the SAP Business
Network Buyer Administration Guide.

To maintain separation of communication among child sites, buyer account administrators create a unique
business application system ID for each child site. The business application system ID, together with the ANID
(which is inherited from the parent site), are included in all communications between child sites and suppliers.

Each business application system ID is associated with at least one billing address, which the supplier sees.
(Suppliers must choose a billing address when creating a non-PO invoice.)

All sites use the same account configuration settings such as transaction rules and customer catalog validation
preferences.

The following figure shows an example of the routing of communication between a child site and a supplier using
ANID and business application system ID routing information.

Multi-ERP Configuration Guide

Overview of Multi-ERP PUBLIC 11
 Figure 4: Communication Flow Between a Child Site and a Supplier

Sites with multi-ERP configurations support supplier punch-in from SAP Business Network for creating and viewing
invoices.

Multi-ERP Configuration Guide

12 PUBLIC Overview of Multi-ERP
Cross-Site Reports
For cross-site reporting, one reporting site is linked with the parent site. The reporting site pulls data directly from
the child sites.

Figure 5: Data Flow in Cross-Site Reporting

Each child site must have a business application system ID specified in its site profile. The business application
system ID is mapped to the Source System reporting field, which is used to separate reporting data.

For more information about cross-site reporting, see About Cross-Site Reporting [page 63].

Suite Integration
Single- and multi-variant configurations support suite integration (that is, integration between procurement or
invoicing solutions from SAP Ariba Procurement solutions and other solutions such as SAP Ariba Contracts or SAP
Ariba Sourcing). Suite integration occurs through the parent site.

The following table lists suite integration features and the configuration types that support them.

Feature Description Disconnected Single-Variant Multi-Variant

Suite-integrated re- Reports pull data from all SAP Ariba solu- Yes Yes Yes
porting tions.

Master data syn- Data is synchronized between all SAP Ariba No Yes Yes
chronization solutions.

Application single Users log in to one SAP Ariba solution and Reporting only Yes Yes
sign-on have access to other solutions without hav-
ing to log in separately.

Multi-ERP Configuration Guide

Overview of Multi-ERP PUBLIC 13
Feature Description Disconnected Single-Variant Multi-Variant

Suite-integrated The home dashboard includes procurement Reporting only Yes Yes
home dashboard and invoicing information from the current
site along with tasks from other solutions
such as SAP Ariba Contracts or SAP Ariba
Sourcing.

Suite-integrated All SAP Ariba solutions can access relevant Reporting only Yes Yes
flex fields flex field data.

SAP Ariba Con- Generate contract requests from contract No Yes Yes
tracts workflow workspaces created in SAP Ariba Con-
tracts.

Migration of Existing Sites

Support for migrating an existing site to a multi-ERP configuration depends on whether the site is a procurement
solution site (SAP Ariba Buying and Invoicing or SAP Ariba Buying) or an SAP Ariba Invoice Management site.

You can migrate existing SAP Ariba Buying and Invoicing or SAP Ariba Buying sites to any multi-ERP configuration
—disconnected, single-variant, or multi-variant.

Existing SAP Ariba Invoice Management sites with transactional data that were not initially enabled for multi-ERP
can be migrated to the disconnected configuration only. They can't be migrated to a single- or multi-variant
configuration.

Regardless of the configuration you're migrating to, migration to multi-ERP is supported for SAP Ariba
Procurement solutions that consist of one of the following:

• A single procurement or invoicing solution site

• Multiple procurement or invoicing solution sites that have business application system IDs and are using a
single SAP Business Network account

Migration is not supported for multiple sites using different SAP Business Network accounts.

For information about migrating to a disconnected configuration, see About Migrating Multiple Existing Sites to a
Disconnected Configuration [page 17] and About Migrating a Single Existing Site to a Disconnected Configuration
[page 18].

 Note

This guide covers migration to a disconnected configuration only. For information on migrating to a single-
variant or multi-variant configuration, customers can contact their Customer Engagement Executive or
Account Manager. The system administrator works with SAP Ariba to plan the migration process.

Multi-ERP Configuration Guide

14 PUBLIC Overview of Multi-ERP
Purchasing Units Vs. Multi-ERP
A table lists advantages of a multi-ERP configuration over a single site with purchasing units for companies that
want to implement spend management by business unit.

For information about purchasing units, see Purchasing Unit Administration Guide.

Question Purchasing Units Multi-ERP Configuration

Where is the master data and transac- All data is stored in the same site. Enterprise-wide master data is stored in
tional data stored? the parent site. Transactional data and
site-specific master data is stored in
child sites.

Are there any chart of account (COA) re- Yes. The entire organization shares the No. Each business unit can have its own
strictions? same COA. COA.

Can master data be filtered by business No, only some master data is filtered. Yes, master data specific to one business
unit? unit is completely filtered because it ex-
ists in its own site.

Is it possible for users to have access to Yes, but the administrative cost can be Yes, a user can have access to multiple
data across multiple business units? high because each purchasing unit must sites and switch between them easily.
be included in the Purchasing Unit field. Users can also be associated with differ-
ent accounting entities in each site.

Can searches by purchasing managers Yes, purchasing managers can be re- Yes, purchasing managers can see only
be restricted to their own business unit? stricted to seeing data for purchasing the data in sites they have access to.
units where they are included as a re-
sponsible user only.

Can purchasing units be used in a multi- Not applicable. Yes, purchasing units provide a way to
ERP configuration? filter data within a site.

Can the solution handle more than one No. A purchasing unit solution is limited Yes.
ERP system? to companies with a single ERP system.

Multi-ERP Configuration Guide

Overview of Multi-ERP PUBLIC 15
Deployment Process Overview for Multi-ERP

The deployment process for multi-ERP configurations involves multiple points of coordination between SAP Ariba
and the customer.

The deployment steps are first done on test sites. Each production site has a corresponding test site. When testing
is complete, SAP Ariba pushes the implementation to the production sites.

Deployment Requirements [page 16]

Disconnected Multi-ERP Configurations [page 16]

Single- and Multi-Variant Multi-ERP Deployments [page 20]

Deployment Requirements
There are three specific deployment requirement sites must meet in a multi-ERP configuration.

• All child sites must use the same SAP Business Network buyer account. (This means that all sites use the same
account configuration settings such as transaction rules and customer catalog validation preferences.)
• Each child site must have its own business application system ID defined in the SAP Business Network buyer
account.
• Each site must have its own web address and site name.

Disconnected Multi-ERP Configurations

Deploying disconnected configurations is about linking multiple sites so users can run reports that draw data from
all the sites they have access to.

Data Considerations for Deploying Disconnected Multi-ERP Configurations [page 17]

Migration of Multiple Existing Sites to a Disconnected Multi-ERP Configuration [page 17]

Migration of a Single Existing Site to a Disconnected Multi-ERP Configuration [page 18]

Deployment of New, Disconnected Multi-ERP Configurations [page 19]

Multi-ERP Configuration Guide

16 PUBLIC Deployment Process Overview for Multi-ERP
Data Considerations for Deploying Disconnected Multi-ERP
Configurations
There are several consideration to keep in mind regarding disconnected configurations.

• There is no data sharing between sites. The customer administrator loads the appropriate ERP data into each
child site.
• Users who need access to multiple sites must have separate user accounts on each site (with the same unique
name in each site).
• A user’s reporting access depends on group membership. For more information, see About Cross-Site Reports
[page 13].
• Customizations made in the parent site are not replicated to the child sites.
• For flex fields to be available for reporting, they must exist in the parent site. In disconnected configurations, an
SAP representative must create flex fields in the parent site that are identical to those in the child sites.
• In disconnected configurations only, strings and enumerations can be uploaded into child sites.

Parent topic: Disconnected Multi-ERP Configurations [page 16]

Related Information

Migration of Multiple Existing Sites to a Disconnected Multi-ERP Configuration [page 17]

Migration of a Single Existing Site to a Disconnected Multi-ERP Configuration [page 18]
Deployment of New, Disconnected Multi-ERP Configurations [page 19]

Migration of Multiple Existing Sites to a Disconnected

Multi-ERP Configuration
A table lists the basic steps for migrating an existing system with multiple sites to a disconnected configuration.

Table 1: Steps for Migrating Multiple Sites to a Disconnected Configuration

Deployment Step Person Responsible For More Information, See

Verify that the SAP Business Network SAP Ariba Support representative Configuring an Existing Ariba Network
buyer account is enabled to support Buyer Account for Federated Process
multi-ERP. Control [page 46]

Multi-ERP Configuration Guide

Deployment Process Overview for Multi-ERP PUBLIC 17
Deployment Step Person Responsible For More Information, See

Verify that all existing sites are linked to SAP Business Network buyer administrator Setting Up Communication with Ariba
the same SAP Business Network buyer Network [page 45]
account. Each site must have a business
application system ID created in the SAP
Business Network buyer account, and
the business application system ID must
be specified in the corresponding site
profile.

 Note
You can't change an existing ANID or
business application system ID.

Set up and enable a new parent site. SAP Ariba Commerce Services representa- About Setting Up the Parent Site [page
tive 44]

Establish the parent-child relationship in SAP Ariba Commerce Services representa- About Setting Up Child Sites [page
site profiles of the existing sites (the sites tive 45]
you're migrating).

Set up the reporting site, linking it to the SAP Ariba Commerce Services representa- About Setting Up the Reporting Site
parent site. tive [page 45]

Import user data for parent site users Customer administrator Common Data Import and Administra-
into parent site. tion for SAP Ariba Procurement Solu-
tions

Parent topic: Disconnected Multi-ERP Configurations [page 16]

Related Information

Data Considerations for Deploying Disconnected Multi-ERP Configurations [page 17]

Migration of a Single Existing Site to a Disconnected Multi-ERP Configuration [page 18]
Deployment of New, Disconnected Multi-ERP Configurations [page 19]

Migration of a Single Existing Site to a Disconnected Multi-

ERP Configuration

Customers with just one site can take advantage of multi-ERP functionality if they plan to expand their deployment.

The following table lists the basic steps for migrating a single existing site to a disconnected parent–child
configuration.

Multi-ERP Configuration Guide

18 PUBLIC Deployment Process Overview for Multi-ERP
Table 2: Steps for Migrating a Single Site to a Disconnected Configuration
Deployment Step Person Responsible For More Information, See...

Configure the SAP Business Network SAP Ariba Support representative Configuring an Existing Ariba Network
buyer account to support multi-ERP. Buyer Account for Federated Process
Control [page 46]

In the SAP Business Network buyer ac- SAP Business Network buyer administrator About Configuring Business Applica-
count, create a business application sys- tion System IDs in Ariba Network Ac-
tem ID for the existing site. counts [page 46]

Set up and enable a new parent site. SAP Ariba Commerce Services representa- About Setting Up the Parent Site [page
tive 44]

Establish the parent-child relationship in SAP Ariba Commerce Services representa- About Setting Up Child Sites [page
the site profile of the existing site (the tive 45]
site you're migrating).

Set up a reporting site, linking it to the SAP Ariba Commerce Services representa- About Setting Up the Reporting Site
parent site. tive [page 45]

Import user data for parent site users Customer administrator Common Data Import and Administra-
into parent site. tion for SAP Ariba Procurement Solu-
tions

Parent topic: Disconnected Multi-ERP Configurations [page 16]

Related Information

Data Considerations for Deploying Disconnected Multi-ERP Configurations [page 17]

Migration of Multiple Existing Sites to a Disconnected Multi-ERP Configuration [page 17]
Deployment of New, Disconnected Multi-ERP Configurations [page 19]

Deployment of New, Disconnected Multi-ERP

Configurations

A table lists the basic steps for deploying a disconnected multi-ERP configuration for new sites.

Table 3: Steps for Deploying New Sites in a Disconnected Configuration

Deployment Step Person Responsible For More Information, See...

Configure the SAP Business Network SAP Ariba Support representative Configuring an Existing Ariba Network
buyer account to support multi-ERP. Buyer Account for Federated Process
Control [page 46]

Create business application system IDs SAP Business Network buyer administrator About Configuring Business Applica-
for each child site in the buyer account. tion System IDs in Ariba Network Ac-
counts [page 46]

Multi-ERP Configuration Guide

Deployment Process Overview for Multi-ERP PUBLIC 19
Deployment Step Person Responsible For More Information, See...

Set up and enable the parent site. SAP Ariba Commerce Services representa- About Setting Up the Parent Site [page
tive 44]

Set up and enable the child sites, mak- SAP Ariba Commerce Services representa- About Setting Up Child Sites [page
ing sure to specify a business application tive 45]
system ID in each site profile.

Establish the parent-child relationship in SAP Ariba Commerce Services representa- About Setting Up Child Sites [page
the child site profiles. tive 45]

Set up a reporting site, linking it to the SAP Ariba Commerce Services representa- About Setting Up the Reporting Site
parent site. tive [page 45]

Import user data for parent site users Customer administrator Common Data Import and Administra-
into parent site. tion for SAP Ariba Procurement Solu-
tions

Parent topic: Disconnected Multi-ERP Configurations [page 16]

Related Information

Data Considerations for Deploying Disconnected Multi-ERP Configurations [page 17]

Migration of Multiple Existing Sites to a Disconnected Multi-ERP Configuration [page 17]
Migration of a Single Existing Site to a Disconnected Multi-ERP Configuration [page 18]

Single- and Multi-Variant Multi-ERP Deployments

SAP Ariba representatives must work closely with customer administrators to deploy single- and multi-variant
configurations.

The following table lists the basic steps required for integrating multiple sites into single- and multi-variant
configuration.

Table 4: Steps for Deploying Single- and Multi-Variant Configurations (continued)

Deployment Step Person Responsible For More Information, See...

Export data from each ERP system. Customer administrator ERP system documentation

Multi-ERP Configuration Guide

20 PUBLIC Deployment Process Overview for Multi-ERP
Deployment Step Person Responsible For More Information, See...

Analyze and rationalize the data (that is, Customer administrator Master Data Rationalization in Multi-
decide which data to load into the parent ERP Configurations [page 31]
site and which data to load into child
sites).

 Note
Rationalizing the data from the ERP
systems for import into procurement
solution sites is the most time-con-
suming and involved task in multi-
ERP deployment. The success of
the deployment process depends on
customers following the data ration-
alization guidelines presented in the
next chapter.

For each child site and the parent site, Customer administrator Common Data Import and Administra-
create a set of CSV files to import. tion for SAP Ariba Procurement Solu-
tions
Optionally, if you plan to run a batch im-
port task, create ZIP files containing the
CSV files you created—one ZIP file per
site. You can use the same SAP Ariba in-
tegration toolkit for all sites.

Configure the SAP Business Network SAP Business Network Customer Support Configuring an Existing Ariba Network
buyer account to support multi-ERP. representative Buyer Account for Federated Process
Control [page 46]

In the SAP Business Network buyer ac- SAP Business Network buyer administrator About Configuring Business Applica-
count, create business application sys- tion System IDs in Ariba Network Ac-
tem IDs for the child sites. You can't counts [page 46]
change an existing ANID or business ap-
plication system ID.

Set up and enable the parent site. SAP Ariba Commerce Services representa- About Setting Up the Parent Site [page
tive 44]

Set up and enable each child site, mak- SAP Ariba Commerce Services representa- About Setting Up Child Sites [page
ing sure to establish the parent-child rela- tive 45]
tionship.

Set up a reporting site, linking it to the SAP Ariba Commerce Services representa- About Setting Up the Reporting Site
parent site. tive [page 45]

 Note
This step is required for cross-site
reporting.

Import enterprise-wide master data into Customer administrator Loading Data into the Parent Site [page
the parent site. 48]

Multi-ERP Configuration Guide

Deployment Process Overview for Multi-ERP PUBLIC 21
Deployment Step Person Responsible For More Information, See...

Import parent site-specific data into the Customer administrator Loading Data into the Parent Site [page
parent site (multi-variant configurations 48]
only).

Select a configuration for each child site SAP Ariba Commerce Services representa- Configuring Replication for Child Sites
(single-variant or multi-variant). At this tive [page 49]
point, the parent site pushes master data
to the child sites.

Subscribe to customer catalog content SAP Ariba Commerce Services representa- Subscribing to Catalog Content [page
on behalf of each child site. tive 51]

Import site-specific master data into the Customer administrator Loading Site-Specific Data into Child
child sites. Sites [page 52]

Test the deployed system. SAP Ariba Commerce Services representa- Testing Integration [page 53]
tive and customer administrator

Push the system to production. SAP Ariba Commerce Services representa- Pushing from Test to Production [page
tive 53]

Multi-ERP Configuration Guide

22 PUBLIC Deployment Process Overview for Multi-ERP
Data Replication in Multi-ERP Configurations

For single- and multi-variant configurations, it is important to understand how data replication works—what data is
replicated, what is not replicated, and what can be overridden.

Subsequent topics provide information about the replication of various types of data and the user interface for
configuring and verifying data replication. The replication user interface is available to SAP Ariba representatives
only.

For information about data rationalization, see Master Data Rationalization in Multi-ERP Configurations [page
31]. Data Replication Reference for Multi-ERP Configurations [page 67] provides a reference of CSV files and
replication information.

General Information About Enterprise-Wide Master

Data
Data is replicated by type of object rather than by individual object. For example, all cross-variant user data in the
parent site (for example, SharedUser.csv data) is replicated to child sites. You cannot specifically exclude data
about individual users.

In multi-variant configurations, only data that belongs to cross-variant data classes—that is, data classes that are
not specific to one ERP variant—is replicated from the parent site to the child sites. This includes, for example,
cross-variant supplier organization data and cross-variant user data. Variant-specific data classes have a specific
ERP shape and are loaded only into child sites.

In single-variant configurations, cross-variant and variant-specific data is replicated.

User and Group Data

Cross-variant user data (for example, the data in SharedUser.csv) is replicated from the parent site to all single-
and multi-variant child sites.

In single-variant configurations, cross-variant user data (for example, the data in SharedUser.csv) is replicated
from the parent site to the child site. Variant-specific user data (for example, the data in User.csv, which holds
user accounting data) can either be replicated or not. Child sites can either subscribe to or unsubscribe from this
data. By default, single-variant child sites don't subscribe to variant-specific user data, and you load the data into
each child site. This allows you to associate different accounting entities to cross-site users in each child site. If you
prefer to have all variant-specific user data replicated in a single-variant configuration, make sure your SAP Ariba
representative sets the replication settings accordingly.

In multi-variant configurations, cross-variant user data is replicated. After replication, you load variant-specific data
into the child site. For details, see About Rationalizing User and Group Data [page 32].

Multi-ERP Configuration Guide

Data Replication in Multi-ERP Configurations PUBLIC 23
In both single- and multi-variant configurations, group data loaded into the parent site is replicated to the child
sites. You can modify group membership in each child site. Group membership and child group changes made in a
child site don't affect other child sites or the parent site. Approval queues are replicated from the parent site and
cannot be deactivated in child sites.

If you import user-related data using the simplified Import User Data (Consolidated File) data import task, then
both cross-variant and variant-specific data is available in the UserConsolidated.csv file. The ImportCtrl field
in the CSV files enables you to specify which data to load into the parent site and which data to load into child sites.
For more information, see About Rationalizing Data Using Consolidated CSV Files [page 31].

Exclude Supplier Users

Make sure your user data loads exclude supplier users. Suppliers create and maintain supplier users on SAP
Business Network. If you update them through a data load, the users might not be able to punch in to your site for
collaboration requests or collaborative contract invoicing.

To avoid loading and updating supplier users in your site, when you export users, filter out records with a
PasswordAdapter value of AribaSupplierNetworkUser. Don't sync supplier users to your ERP system or
modify supplier user data from an external source.

Supplier Data
Cross-variant supplier data is the data in the SupplierOrganizations.csv and SupplierIDs.csv files.
Variant-specific supplier data is the data in the Supplier.csv and SupplierLocation.csv files.

However, if you import supplier-related data using the simplified Import Supplier Data (Consolidated File) data
import task, then both cross-variant and variant-specific data is available in the SupplierConsolidated.csv file.
The ImportCtrl field in the CSV files enables you to specify which data to load into the parent site and which data
to load into child sites.

For general information about supplier data, see Supplier Organizations, Suppliers, and Supplier Locations.

In single-variant configurations, both cross-variant and variant-specific supplier data is replicated to child sites.

In multi-variant configurations, cross-variant supplier data loaded into the parent site is replicated to child sites.
After replication, you load variant-specific supplier data into the multi-variant child sites.

Accounting Data
Accounting data is variant-specific. In single-variant configurations, it can be loaded into the parent site and
replicated. In multi-variant configurations, it must be loaded into the child sites.

The set of accounting files to import depends on the variant of each child site. For information about which CSV
files must be included for SAP and PeopleSoft data, see the Common Data Import and Administration for SAP
Ariba Procurement Solutions.

Multi-ERP Configuration Guide

24 PUBLIC Data Replication in Multi-ERP Configurations
You can associate cross-site users with different accounting units in each child site, even in single-variant
configurations. For information, see About Single-Variant Configurations [page 33].

Customer Catalog Content

In single- and multi-variant configurations, customer catalog content (items, kits, supplemental attribute
definitions, and customer catalog hierarchy) resides in the parent site. It is not replicated to the child sites. Instead,
the child sites subscribe to the customer catalog data in the parent site.

Child sites can subscribe to customer catalogs that are active and searchable.

Child sites inherit the system commodity code set and unit of measure from the parent site. You can load additional
commodity codes and units of measure into the child sites.

You cannot load customer catalog content into child sites.

If partitioned supplier data does not exist in the parent site, then the catalog kits for these suppliers must be
created in each of the appropriate child sites.

 Note

Customer catalog views reside in child sites.

Customer catalog content depends on the following data in order to function properly:

• Type
• CatalogHierarchy
• CommonSupplier (SupplierOrganizations.csv, SupplierIDs.csv)
• CommodityCode
• CommodityCodeMap
• UnitOfMeasure
• UnitOfMeasureMap
• Currency
• CurrencyMap

Multi-ERP Configuration Guide

Data Replication in Multi-ERP Configurations PUBLIC 25
Strings and Enumerations
Strings and enumerations are periodically replicated from the parent site to all child sites. You cannot upload
strings or enumerations to child sites except in the disconnected configuration.

Approval Processes
A list describes replication behavior for approval processes.

For general information about approval processes, see the Approval Process Management Guide.

• Child sites inherit approval processes and their activation settings from the parent site. In multi-variant
configurations, child sites do not inherit approval processes that include variant-specific approval rules.
• In child sites, the names of inherited approval processes have the prefix Inherited.
• Changes made to approval processes in the parent site are replicated to child sites, with the exception of
changes to activation settings.
• Approval processes in Draft state in the parent site are not replicated to child sites.
• You cannot modify or move an approval rule in an inherited approval process from within the child site. You can,
however, add approval rules to an inherited approval process.
• You can disable inherited edit rules and filter rules. You can also copy them and edit the copies.
• If you make changes to an inherited approval process in the child site, those changes are not overwritten by
subsequent changes in the parent site. Instead, changes to the approval process in the parent site are merged
into the approval process in the child site.
• You can create approval processes in child sites. If you activate an approval process created in the child site, the
corresponding inherited approval process is deactivated.
• The CSV supporting files for approval processes (such as approver lookup tables) are replicated only if they are
referenced by an approval process in the parent site.

Customizations
This section discusses replication issues pertaining to parameters, approval rules, flex fields, field properties,
and standard Ariba markup language (AML) customization changes. SAP representatives have access to these
customizations.

For more details about modifying parameters, approval rules, and other customizations, see About Modifying Child
Site Customizations [page 60].

Multi-ERP Configuration Guide

26 PUBLIC Data Replication in Multi-ERP Configurations
Inherited Parameter Values in Child Sites

Inherited parameter values can be overridden in the child site. SAP representatives can edit the parameter values.

Parameters are loaded into child sites in the following order:

1. System-level parameters (loaded by replication)

2. Inherited site-level parameters (loaded by replication)
3. Site-level parameters for the child sites (loaded directly into child sites)

Subsequent loads override previous loads.

Modifications to parent site parameters are replicated to child sites unless those parameters were modified directly
in the child sites.

For more information, see Overriding Inherited Parameter Values in Child Sites [page 60].

Flex Fields, Field Properties, EForm Templates, and AML

Customizations

In single- and multi-variant configurations, customizations in the parent site—for example, eForm templates and
standard Ariba markup language (AML) customizations—are replicated from the parent site to the child sites. If the
parent site is a different variant from the child site, variant-specific customizations are not replicated.

When an SAP representative publishes customizations in the parent site, the SAP Ariba solution validates the
customizations against each child site. If validation reveals any conflicts (for example, duplicate flex fields), the
customizations are not applied to any site, including the parent site.

Private AML customizations are permitted in child sites only. Private AML customizations cannot be uploaded to a
parent site.

Flex Fields

SAP representatives must be aware of flex field behavior when working with flex fields and eForm templates in a
multi-ERP configuration.

Behaviors to be aware of include:

• For flex fields to be available for reporting, they must be created in the parent site and replicated to child sites.
You can't modify the reporting availability of flex fields in child sites. This is true regardless of whether the field
was created in the parent or child site.
• If there are duplicate flex fields in parent and child sites, you can't configure the child site as a single-variant or
multi-variant site. These configuration options aren't available in this situation.
• In multi-variant configurations, variant-specific field definitions aren't replicated. If there are references to
those field definitions in objects that would normally be replicated, the broken reference causes replication to
fail.
• If a child site has flex fields that aren't in the parent site, the fields remain in the child site.

Multi-ERP Configuration Guide

Data Replication in Multi-ERP Configurations PUBLIC 27
EForm Templates

SAP representatives must be aware of eForm template behaviors when working with eForm templates in a multi-
ERP system.

Behaviors to be aware of include:

• eForm templates replicated from the parent site can't be revised in the child site.
• As with flex fields, for eForm templates to be available for reporting, they must be created in the parent site and
replicated to child sites. You can't modify the reporting availability of eForm templates in child sites. This is true
regardless of whether the eForm template was created in the parent or child site.
• If a child site has eForm templates that aren't in the parent site, they remain in the child site.

Customization Replication Failures

If an error occurs during data replication and causes replication to fail, and the procurement solution doesn't retry
the failed records, an SAP representative can set a site parameter on the child site to resolve the issue.
Application.Base.RetryFailedReplication
In multi-ERP configurations, This parameter can solve replication issues occurring with
any type of customization, including replication of approval rules, parameters, and other
customizations.

The Replication Setup User Interface

SAP Ariba representatives configure data replication settings, verify replication status, and view the replication log
on the Replication Setup page in SAP Ariba Service Manager.

To open the Replication Setup page:

1. Log in to SAP Ariba Service Manager.

2. Choose Site Manager Customer Sites . The Customer Sites page opens. On the Customer Sites page:
• In the Realm column, site names followed by a superscript P are parent sites. You can hold the pointer over
a superscript P to see a list of associated child sites.
• The ANID column indicates business application system IDs for child sites in addition to the SAP Business
Network.
3. Administer a parent or child site.

 Tip

Administering the parent site also gives you access to replication configuration for all related child sites.

4. Choose FPC Manager Replication Setup .

If you open the Replication Setup page while administering a parent site, the page contains two tabs—Overview
and Configuration (described next). If you open the Replication Setup page while administering a child site, there
are no tabs, and the page you see is equivalent to the Configuration tab for that child site.

Multi-ERP Configuration Guide

28 PUBLIC Data Replication in Multi-ERP Configurations
• The Overview tab shows replication status throughout the entire multi-ERP configuration. Child sites are
distinguished by business application system ID.
• The Configuration tab (or the Replication Setup page for a child site) lets you select a child site and configure
replication, view replication status, and subscribe to customer catalog content.

The Status column displays the status of replication for each class. Status is indicated by colored boxes.

Status Indicator Status Description

Green Replication was successful and free of warnings.

Purple Replication is in progress in child sites when the parent site is replicating data.

Yellow Replication finished but that there are warnings.

Red A fatal error occurred.

Orange Replication finished, but there were errors that prevented some data from being repli-
cated.

Replication stopped for this group of data. Replication stops when there are five consecu-
Red with exclamation point tive fatal errors.

Blank (no color) For customer catalog content, indicates unsubscribed content.

For other data, indicates data that is not replicated but could be if a different configuration
were chosen. For example, this status appears for variant-specific data if a child site is the
same variant as the parent site but is configured as multi-variant.

Appears for variant-specific data if the child site is a different variant from the parent site.
It indicates that these classes cannot be replicated, regardless of configuration.

To filter the information displayed on the page, use the Show menu in the top right corner.

Command on the Show Menu Description

All Shows the entire list.

Selected Shows only the data classes, customizations, and customer catalog content the child is
currently subscribing to.

Selectable Shows the customer catalog content and data classes for which you can modify the
subscription setting.

The Actions menu lets you perform actions related to replication.

• To perform an action on an individual catalog or data class, use the Actions menu for that customer catalog or
class. To perform an action on an entire group of data at once, use the Actions menu for that group of data.
• The commands available on the Actions menu vary depending on the type of data you are acting on.

Actions Menu Command Description

View log Opens the replication log. To view the log for all data, use the Actions menu in the All row.

Subscribe/Unsubscribe Subscribes to or unsubscribes from the data.

Retry failed records Performs the replication operation on all records that failed the last time replication ran. This
command has no effect on customer catalog content, which is not replicated.

Re-replicate all Performs the replication operation on all records in the class or group of classes. This
command has no effect on catalog content, which is not replicated.

Multi-ERP Configuration Guide

Data Replication in Multi-ERP Configurations PUBLIC 29
Actions Menu Command Description

Clear status
Clears the error status. You must clear status indicators before choosing Retry failed
records.

Multi-ERP Configuration Guide

30 PUBLIC Data Replication in Multi-ERP Configurations
Master Data Rationalization in Multi-ERP
Configurations

Customer administrators prepare ERP data for import into the parent and child sites of a single- or multi-variant
configuration.

Before loading data into a single- or multi-variant configuration, you must separate it into two sets of data:
cross-variant, enterprise-wide master data destined for the parent site, and variant-specific, site-specific master
data destined for the child site.

The process of analyzing and separating the data is called rationalization. The data rationalization process differs
depending on the following factors:

• Whether you're implementing a single- or multi-variant configuration

• How you plan to import user and supplier data:
• Using consolidated files with the tasks Import User Data (Consolidated File) and Import Supplier Data
(Consolidated File)
• Using the legacy, non-consolidated files and tasks (for example, the files SharedUser.csv,
SupplierOrganizations.csv, and SupplierIDs.csv)

 Note

When you export data from ERP systems, export data for the parent site and child sites at the same time to
ensure that the data is consistent with itself.

Before rationalizing data, be sure to read About Data Replication [page 31]. Data Replication Reference [page 31]
provides a reference of CSV files and replication information.

Data Rationalization for Multi-ERP Using Consolidated CSV Files [page 31]

Data Rationalization for Multi-ERP Using Legacy (Non-Consolidated) Files [page 32]

User and Group Data Rationalization [page 32]

Supplier Data Rationalization [page 39]

Rationalizing Application Configuration Data [page 43]

Rationalization of Invoice Exception Types and Invoice Exception Type Overrides [page 43]

Data Rationalization for Multi-ERP Using

Consolidated CSV Files
When you load user and supplier data using the simplified master data import tasks Import User Data
(Consolidated File) and Import Supplier Data (Consolidated File), you use the ImportCtrl field in the CSV
files to specify which data to load into the parent site and which data to load into child sites.

Valid values of this field are: Both, Shared, and Partition.

Multi-ERP Configuration Guide

Master Data Rationalization in Multi-ERP Configurations PUBLIC 31
The following table lists the type of data that is imported depending on the ImportCtrl field value and whether
the site is a parent or a child site:

ImportCtrl Field Value Type of Site Type of Data Imported

Both Parent Creates/Updates both the cross-variant and variant-specific data

Child Creates/Updates both the cross-variant and variant-specific data

Shared Parent Creates/Updates only the cross-variant data

Child Creates/Updates only the cross-variant data

Partition Parent No data is imported

Child Creates/Updates only the variant-specific data

“ blank ” Parent Creates/Updates only the cross-variant data

Child Creates/Updates only the variant-specific data

Data Rationalization for Multi-ERP Using Legacy

(Non-Consolidated) Files
If you use the legacy, non-consolidated data import tasks to load user and supplier data, rationalize the data by
creating different sets of CSV files to be loaded into the parent and child sites.

For more information, see:

• User and Group Data Rationalization [page 32]

• Supplier Data Rationalization [page 39]

User and Group Data Rationalization

The first step in rationalizing user data is to decide which users need access to the parent site and which users
need access to child sites.

 Note

You must load all enterprise-wide user data (for example, the data in SharedUser.csv and
SharedUserSupervisor.csv or the UserConsolidated.csv) into the parent site, regardless of whether
the system configuration type is single-variant or multi-variant. Failure to do so can result in problems with
accessing reports and viewing content on the dashboard. Also, do not create new users though the user
interface in a child site, because doing so does not create a SharedUser entry in the parent site.

Keep the following in mind regarding user data:

• Users can access all sites in which they have a user account (that is, an entry in Users.csv or the
UserConsolidated.csv). For cross-site users, a unique user name must identify the user across all sites.

Multi-ERP Configuration Guide

32 PUBLIC Master Data Rationalization in Multi-ERP Configurations
• A parent site user cannot have a supervisor that was loaded directly into a child site. Supervisors of parent site
users must be imported into the parent site.
• A user’s access to reporting depends on group membership. (There are reporting groups specific to child
sites.) For more information, see About Cross-Site Reports [page 13].

User Data in Single-Variant Configurations [page 33]

Rationalizing User Data for Multi-Variant Configurations [page 37]

User Data in Single-Variant Configurations

In single-variant configurations, cross-variant user data loaded into the parent site is replicated to single-variant
child sites.

By default, replication of variant-specific user data is disabled; that is, child sites don't subscribe to this data
by default. This allows you to associate users with different accounting units in each site. Alternatively, an Ariba
representative can configure child sites to subscribe to variant-specific user data.

When child sites subscribe to variant-specific user data on the parent site, users with a User.csv entry in the
parent site automatically have access to all single-variant child sites.

You can import User.csv data for site-specific users directly into the child sites. These site-specific users don't
have access to the parent site.

Rationalizing User Data for Single-Variant Configurations Where Cross-Site Users Have the Same Accounting
Unit in All Sites [page 33]

Rationalizing User Data for Single-Variant Configurations Where Cross-Site Users Have Different Accounting
Units in Each Site [page 35]

Rationalizing User Data for Single-Variant Configurations Where

Cross-Site Users Have the Same Accounting Unit in All Sites

Procedure

1. Group users depending on which sites they need access to:

• Parent and child sites

• One or more child sites only
2. Using the following tables as a reference, include entries for the indicated users in the CSV files listed for that
row.

• Reference Tables for Consolidated and Legacy (Non-Consolidated) CSV Files [page 34]

Multi-ERP Configuration Guide

Master Data Rationalization in Multi-ERP Configurations PUBLIC 33
Reference Tables for Consolidated and Legacy (Non-Consolidated) CSV Files

Use the following tables if you are using the consolidated and legacy (non-consolidated) CSV files.

Table 5: Table of Consolidated CSV Files to Create for Importing User Data into Sites in a Single-Variant Configuration
Cross-Variant and Variant-Specific
Master Data for the Parent Site (Repli- Variant-Specific (Site-Specific) Master
User Access Requirements cated) Data for Each Child Site

Users requiring access to parent and • UserConsolidated* None

child sites
• UserGroupConsolidated*
• Address
• Any other required user data files
* Set the ImportCtrl value to
Both .

Users requiring access to one or more • UserConsolidated* • UserConsolidated*

child sites only (but not to the parent
site)
• UserGroupConsolidated* • UserGroupConsolidated*
* Set the ImportCtrl value to • Address
Shared or leave it blank. • Any other required user data files
* Set the ImportCtrl value to
Partition or leave it blank.

Table 6: Table of Legacy (Non-Consolidated) CSV Files to Create for Importing User Data into Sites in a Single-Variant
Configuration
Cross-Variant and Variant-Specific
Master Data for the Parent Site (Repli- Variant-Specific (Site-Specific) Master
User Access Requirements cated) Data for Each Child Site

Users requiring access to parent and • SharedUser None

child sites
• SharedUserSupervisor
• UserParentGroup
• SharedUserShipToAddressM
ap
• GroupSharedUserMap
• User
• Address
• UserPCardMap
• Any other required user data files

Users requiring access to one or more • SharedUser • User

child sites only (but not to the parent
site)
• SharedUserSupervisor • Address
• UserParentGroup • SharedUserShipToAddressM
• GroupSharedUserMap ap
• UserPCardMap
• Any other required user data files

Multi-ERP Configuration Guide

34 PUBLIC Master Data Rationalization in Multi-ERP Configurations
Rationalizing User Data for Single-Variant Configurations Where
Cross-Site Users Have Different Accounting Units in Each Site

The process for rationalizing data in this scenario is the same as the process in multi-variant configurations.

Context

If you are working with single-variant child sites, and you want to give cross-site users different accounting units in
each child site, make sure an SAP Ariba representative has configured the child site so that it does not subscribe to
variant-specific user data.

Procedure

1. Divide users depending on which sites they need access to:

• Parent and child sites

• One ore more child sites
2. Using the following tables as a reference, include entries for the indicated users in the CSV files listed for that
row. You will have a different set of CSV files to import into each site.

• Reference Tables for Legacy (Non-Consolidated) and Consolidated CSV Files [page 36]

Multi-ERP Configuration Guide

Master Data Rationalization in Multi-ERP Configurations PUBLIC 35
Reference Tables for Legacy (Non-Consolidated) and Consolidated CSV Files

Use the following tables if you are using legacy non-consolidated and the consolidated CSV files:

Table 7: Table of Legacy (Non-Consolidated) User Data CSV Files to Create for Importing into Sites in a Multi-Variant
Configuration
Cross-Variant Master Data
User Access Re- for Parent Site (Repli- Site-Specific Data for the Parent Variant-Specific Master Data for
quirements cated) Site (Not Replicated) Each Child Site

Users requiring ac- • SharedUser • User* • User

cess to parent and
child sites
• SharedUserSuperv • Address • Address
isor • SharedUserShipToAddre • SharedUserShipToAddre
• UserParentGroup ssMap ssMap
• GroupSharedUserM • UserPCardMap** • UserPCardMap
ap • Any other required user data • Any other required user data
files files
* User.csv for the parent site
does not need to contain ac-
counting data.
** UserPCardMap.csv
needs to contain headings even
if it does not contain data.

Users requiring ac- • SharedUser None • User

cess to one or more
child sites (but not
• SharedUserSuperv • Address
to the parent site)
isor • SharedUserShipToAddre
• UserParentGroup ssMap
• GroupSharedUserM • UserPCardMap
ap • Any other required user data
files

Table 8: Table of Consolidated User Data CSV Files to Create for Importing into Sites in a Multi-Variant Configuration
Cross-Variant Master Data Site-Specific Data for the Pa- Variant-Specific Master Data
User Access Requirements for Parent Site (Replicated) rent Site (Not Replicated) for Each Child Site

Users requiring access to pa- • UserConsolidated* • UserConsolidated*

rent and child sites
• UserGroupConsolidated* • UserGroupConsolid
• Address ated*
• Any other required user data files • Address
* Set the ImportCtrl value to Both . • Any other required user
data files
* Set the ImportCtrl
value to Both ,
Partition, or leave it
blank.

Multi-ERP Configuration Guide

36 PUBLIC Master Data Rationalization in Multi-ERP Configurations
 Cross-Variant Master Data Site-Specific Data for the Pa- Variant-Specific Master Data
User Access Requirements for Parent Site (Replicated) rent Site (Not Replicated) for Each Child Site

Users requiring access to one • UserConsolidated* • UserConsolidated*

or more child sites (but not to
the parent site)
• UserGroupConsolidated* • UserGroupConsolid
* Set the ImportCtrl value to Shared or leave it ated*
blank. • Address
• Any other required user
data files
* Set the ImportCtrl
value to Partition or
leave it blank.

Rationalizing User Data for Multi-Variant Configurations

In multi-variant configurations, cross-variant user data loaded into the parent site (for example, SharedUser.csv)
is replicated to multi-variant child sites. You then load variant-specific user data into each multi-variant child site.

Context

Users have access to sites in which they have a site-specific user account (that is, a Users.csv entry).

Procedure

1. Divide users depending on which sites they need access to:

• Parent and child sites

• One or more child sites
2. Using the following tables as a reference, include entries for the indicated users in the CSV files listed for
that row. You will have a different set of CSV files to import into each site.Reference Tables for Legacy (Non-
Consolidated) and Consolidated CSV Files [page 36]

Multi-ERP Configuration Guide

Master Data Rationalization in Multi-ERP Configurations PUBLIC 37
Reference Tables for Legacy (Non-Consolidated) and Consolidated
CSV Files

Use the following tables if you are using legacy non-consolidated and the consolidated CSV files:

Table 9: Table of Legacy (Non-Consolidated) User Data CSV Files to Create for Importing into Sites in a Multi-Variant
Configuration
Cross-Variant Master Data Site-Specific Data for the Parent
User Access Re- for Parent Site (Repli- Site Variant-Specific Master Data for
quirements cated) (not Replicated) Each Child Site

Users requiring ac- • SharedUser • User* • User

cess to parent and
child sites
• SharedUserSuperv • Address • Address
isor • SharedUserShipToAddre • SharedUserShipToAddre
• UserParentGroup ssMap ssMap
• GroupSharedUserM • UserPCardMap** • UserPCardMap
ap • Any other required user data • Any other required user data
files files
* User.csv for the parent site
does not need to contain ac-
counting data.
** UserPCardMap.csv
needs to contain headings even
if it does not contain data.

Users requiring ac- • SharedUser None • User

cess to one or more
child sites (but not
• SharedUserSuperv • Address
to the parent site)
isor • SharedUserShipToAddre
• UserParentGroup ssMap
• GroupSharedUserM • UserPCardMap
ap • Any other required user data
files

Table 10: Table of Consolidated User Data CSV Files to Create for Importing into Sites in a Multi-Variant Configuration
Cross-Variant Master Data Site-Specific Data for the Pa- Variant-Specific Master Data
User Access Requirements for Parent Site (Replicated) rent Site (Not Replicated) for Each Child Site

Users requiring access to pa- • UserConsolidated* • UserConsolidated*

rent and child sites
• UserGroupConsolidated* • UserGroupConsolid
• Address ated*
• Any other required user data files • Address
* Set the ImportCtrl value to Both . • Any other required user
data files
* Set the ImportCtrl
value to Both ,
Partition, or leave it
blank.

Multi-ERP Configuration Guide

38 PUBLIC Master Data Rationalization in Multi-ERP Configurations
 Cross-Variant Master Data Site-Specific Data for the Pa- Variant-Specific Master Data
User Access Requirements for Parent Site (Replicated) rent Site (Not Replicated) for Each Child Site

Users requiring access to one • UserConsolidated* • UserConsolidated*

or more child sites (but not to
the parent site)
• UserGroupConsolidated* • UserGroupConsolid
* Set the ImportCtrl value to Shared or leave it ated*
blank. • Address
• Any other required user
data files
* Set the ImportCtrl
value to Partition or
leave it blank.

Supplier Data Rationalization

How you rationalize supplier data depends on the configuration type (multi-variant or single-variant).

For every supplier you want to import into a site, it’s a good idea to verify that a corresponding supplier
organization already exists in the site. To verify that the supplier organizations already exist, match the IDs
listed in the SupplierIDs.csv file to the IDs and domains listed in the corresponding Supplier.csv files.
When you prepare supplier data for import, make sure SupplierIDs.csv includes entries for every supplier
listed in the Supplier.csv files. For general information about suppliers and supplier organizations, see Supplier
Organizations, Suppliers, and Supplier Locations.

 Note

Each supplier organization can have only one supplier mapped to it. You can map multiple supplier locations to
one supplier.

Customer catalog content resides in the parent site and depends on supplier organization data (the data
in SupplierOrganizations.csv and SupplierIDs.csv). For all content to be viewable, relevant supplier
organization data must be loaded into the parent site and replicated. The customer catalog cannot reference
supplier organization data loaded at the child site level.

Understanding the Supplier Data Import Process

When you import suppliers into a site, the SAP Ariba system verifies that a supplier organization already exists
in that site for each supplier. Each supplier organization can have only one supplier mapped to it. (You can map
multiple supplier locations to one supplier.)

• If an associated supplier organization exists in the site and is active, the supplier is imported and is linked to the
supplier organization.
• If an associated supplier organization is not found in the site, one is created automatically. This process
generates a system ID for the supplier organization. The supplier and supplier organization are linked.

Multi-ERP Configuration Guide

Master Data Rationalization in Multi-ERP Configurations PUBLIC 39
  Note

The automatic creation of supplier organizations impedes replication of the supplier organization from
the parent site. To fix the problem and reinstate the replication, you must unlink the supplier from the
automatically created supplier organization. Then you must deactivate the automatically created supplier
organization. For more information, see Correcting Supplier ID Conflicts [page 57].

• If an associated supplier organization exists in the site but is inactive, the supplier is removed from the supplier
organization. That is, the supplier and supplier organization are no longer linked.

Rationalizing Supplier Data for Single-Variant

Configurations

You can prepare supplier data for import from legacy, non-consolidated supplier files or from simplified,
consolidated files. In single-variant configurations, all supplier data that you load into the parent site—including
cross-variant and variant-specific data—is replicated to the single-variant child sites.

Context

You can load additional site-specific supplier data into child sites.

Procedure

1. Create one of the following sets of CSV files.

• If you are importing data using the legacy (non-consolidated) supplier files, create the following CSV files:
• SupplierOrganizations.csv
• SupplierIDs.csv
• Supplier.csv
• SupplierLocation.csv
• Other supplier data files
• If you are importing data using the simplified, consolidated supplier files, create the following consolidated
CSV files:
• SupplierConsolidated.csv
• SupplierLocationConsolidated.csv
2. Populate the files with information about all supplier organizations and suppliers.

Multi-ERP Configuration Guide

40 PUBLIC Master Data Rationalization in Multi-ERP Configurations
Supplier Data in Multi-Variant Configurations
In multi-variant configurations, cross-variant supplier data loaded into the parent site is replicated to the child sites.
You then load variant-specific supplier data into each multi-variant child site.

You can load additional site-specific supplier data into child sites.

Make sure you rationalize supplier data carefully before importing it and creating orders and invoices. You should
not attempt to modify the relationship of suppliers to supplier organizations once transactional data exists.

Rationalizing Supplier Data for Multi-Variant Configurations Using

Legacy (Non-Consolidated) CSV Files

You can rationalize supplier data for a multi-variant configuration using legacy CSV files. These files are not
consolidated.

Procedure

1. Identify enterprise-wide and site-specific supplier organizations. All supplier organizations referenced by the
customer catalog are considered enterprise-wide suppliers.

 Tip

Use supplier name and location to do the matching. This information is likely to be identical across all ERP
systems, whereas supplier IDs tend to be variant-specific.

2. For the parent site, create SupplierOrganizations.csv and populate it with data for enterprise-wide
supplier organizations.
3. For the parent site, create SupplierIDs.csv. Populate it with supplier IDs for all suppliers across the entire
system that are linked to enterprise-wide supplier organizations.

 Note

Supplier organization data (SupplierOrganizations.csv and SupplierIDs.csv) replicated from the

parent site cannot be modified from within child sites. This means you cannot add a site-specific supplier
to a replicated supplier organization.

4. For each child site, create SupplierOrganizations.csv and populate it with data for site-specific supplier
organizations. This file should contain only non-customer catalog supplier organizations.
5. For each child site, create SupplierIDs.csv and populate it with supplier IDs for the suppliers linked to the
site-specific supplier organizations. Keep the following in mind regarding site-specific supplier organizations:
• When you import site-specific supplier organizations into a child site, if the site-specific
SupplierIDs.csv file has supplier IDs identical to the IDs replicated from the parent site, the import
operation is rolled back.
• For SupplierID entries for which no domain is specified, site-specific IntegrationMappings.aml
includes a default value for PeopleSoft and SAP variants. For generic variants, the domain is left blank.

Multi-ERP Configuration Guide

Master Data Rationalization in Multi-ERP Configurations PUBLIC 41
 • Each supplier organization can have only one supplier mapped to it.
6. For each child site, create the following files, populating them with data about the suppliers used in that site:
• Supplier.csv
• SupplierLocation.csv
• Other supplier files as needed

Rationalizing Supplier Data for a Multi-Variant Configuration Using

Consolidated CSV Files

You can rationalize supplier data for a multi-variant configuration using simplified, (consolidated) CSV files.

Procedure

1. Create the following CSV files and populate them with both cross-variant and variant-specific data:
• SupplierConsolidated.csv
• SupplierLocationConsolidated.csv
2. Populate the ImportCtrl field in the SupplierConsolidated.csv file depending on the type of data that
you want to load into the parent and child sites.

The following table lists the type of data that is imported depending on the ImportCtrl field value and
whether the site is a parent or a child site:

ImportCtrl Field Value Type of Site Type of Data Imported

Both Parent Creates/Updates both the cross-variant and variant-specific supplier

data

Child Creates/Updates both the cross-variant and variant-specific supplier

data

Shared Parent Creates/Updates only the cross-variant supplier data

Child Creates/Updates only the cross-variant supplier data

Partition Parent No data is imported

Child Creates/Updates only the variant-specific supplier data

“ blank ” Parent Creates/Updates only the cross-variant supplier data

Child Creates/Updates only the variant-specific supplier data

You import the SupplierLocationConsolidated.csv and any other required supplier data files only to the
respective child sites.

Multi-ERP Configuration Guide

42 PUBLIC Master Data Rationalization in Multi-ERP Configurations
Rationalizing Application Configuration Data
You rationalize application configuration data for applications such as SAP Ariba Buying and Invoicing and SAP
Ariba Invoice Management.

Context

Application configuration data might include the following information:

• Invoice exception type

• Charge exception type
• Payment type
• Expense policy type
• Currency conversion rate

How you rationalize this data depends on your business requirements.

Procedure

1. Create a set of CSV files that contain enterprise-wide, cross-variant data to import into the parent site.
2. Create sets of CSV files that contain variant-specific and site-specific data to import into child sites.

Rationalization of Invoice Exception Types and

Invoice Exception Type Overrides
Invoice exception types are replicated to child sites in single-variant and multi-variant configurations.

Invoice exception type overrides for line-level invoice exception types are replicated to child sites in single-variant
configurations.

In multi-variant configurations, if you want invoice exception type overrides in child sites, you must import the
invoice exception types into the child site rather than the parent site. This is the only way to make the invoice
exception types editable in the child site, which is required for configuring overrides.

Override validation data (InvoiceExceptionTypeOverrideValidation.csv) is replicated in both single- and

multi-variant configurations.

Multi-ERP Configuration Guide

Master Data Rationalization in Multi-ERP Configurations PUBLIC 43
Deploying Multi-ERP Configurations

An SAP representative leads the deployment effort for multi-ERP configurations, working closely with the
customer.

Setting Up the Parent Site [page 44]

Setting Up Child Sites [page 45]

Setting Up the Reporting Site [page 45]

Setting Up Communication with SAP Business Network [page 45]

Loading Data into the Parent Site [page 48]

Configuring Replication for Child Sites [page 49]

Child Site Customizations [page 51]

Loading Site-Specific Data into Child Sites [page 52]

Multi-ERP Configuration Testing [page 53]

Push Multi-ERP Configurations from Test to Production [page 53]

Setting Up the Parent Site

An SAP representative performs this task.

To set up the parent site, follow the general site setup procedures in the SAP Ariba Procurement solutions service
administration guide (available to SAP representatives only). In addition, make sure to adhere to the following
guidelines:

• Parent sites should be new, fresh sites. Do not turn a production site into a parent site.
• Specify a feature set that includes the features required by all sites in the system.
• When prompted to choose an ERP type:
• If you are setting up a disconnected configuration, or if no ERP type is dominant among your ERP systems,
choose Generic.
• If you are setting up single- or multi-variant configurations, and there is a dominant type among your ERP
systems, choose that type.
• In the site profile, to define the site as a parent site, select the Is Parent Realm check box.
• Specify the SAP Business Network account ID. Do not assign a business application system ID to the parent
site.

Multi-ERP Configuration Guide

44 PUBLIC Deploying Multi-ERP Configurations
Setting Up Child Sites
An SAP representative performs this task.

To set up child sites, follow the general site setup procedures in the SAP Ariba Procurement solutions service
administration guide (available to SAP representatives only). In addition, make sure to adhere to the following
guidelines:

• In site profile for each child site, to establish the parent–child relationship, specify the parent site in the Parent
Realm ID field.
When you establish the parent–child relationship, the child site inherits the parent site SAP Business Network
account ID and shared secret. These are not editable in the child sites.
• Enter the remaining information as usual.
• Each site in a multi-ERP configuration can have a different set of languages enabled.
• You'll enter a business application system ID after it is created in SAP Business Network. See Setting Up
Communication with SAP Business Network [page 45].

Setting Up the Reporting Site

An SAP representative performs this task.

 Note

For cross-site reporting, business application system IDs are required for each child site. The business
application system ID is specified in the site profile.

Set up the reporting site, following these guidelines:

• Specify the parent site in the Customer Site Name field.

• Provide the SAP Business Network account ID and the shared secret of the parent site.

Setting Up Communication with SAP Business

Network
Setting up communication between a multi-ERP system and SAP Business Network involves four steps.

1. An SAP Ariba Customer Support representative configures the SAP Business Network buyer account to
support multi-ERP [page 46].
2. The SAP Business Network buyer administrator creates a business application system ID for each child site
and optionally maps business application system IDs to supplier private IDs. [page 46]
3. The SAP Business Network buyer administrator configures end points for each system ID. [page 47]
4. An SAP Ariba representative adds the business application system IDs to the child site profiles. [page 47]

Multi-ERP Configuration Guide

Deploying Multi-ERP Configurations PUBLIC 45
Configuring an Existing SAP Business Network Buyer
Account for Multi-ERP Support
SAP Ariba Customer Support performs this task.

Procedure

1. Log in to the SAP Business Network administration application for the appropriate SAP Business Network
stack.
2. Click the Buyers tab and search for the customer’s SAP Business Network account.
3. Click the user ID of the account, then click User Details. The User Detail -Buyer Information page opens.
4. Scroll down and select one of the following options. The option you select depends on the parent site’s feature
set:

• To configure SAP Ariba Invoice Management to support multi-ERP, click the Convert to Ariba Open
Network check box and click Update. Select this option only if the parent site’s feature set is SAP Ariba
Invoice Management.
• To configure SAP Ariba Buying and Invoicing or SAP Ariba Buying to support multi-ERP, click the
Designate this buyer as an SSP buyer check box and click Update SPP Info.
5. Click Update.
6. In the Multi ERP section, click the Enable multiple ERP support check box and click Update.
7. Log out.

Configuring Business Application System IDs in SAP

Business Network Accounts
After an SAP Ariba Customer Support representative configures the SAP Business Network buyer account to
support multi-ERP, the SAP Business Network buyer administrator creates business application system IDs for
each child site.

The system IDs are used in child site communications with SAP Business Network and the reporting site.

You can map business application system IDs to a supplier identifier called a private ID. Private IDs are mapped to
the supplier’s Ariba Network ID to ensure correct document routing.

For more information about creating business application system IDs and mapping them to supplier private IDs,
see Link Multiple Business Applications and Multiple Unique Supplier IDs for One Supplier.

Multi-ERP Configuration Guide

46 PUBLIC Deploying Multi-ERP Configurations
Configuring SAP Business Network End Points for Child
Sites

The SAP Business Network buyer administrator configures end points for each child site to manage and control
the flow of data between SAP Business Network and the multi-ERP configuration. The end points ensure that SAP
Business Network sends cXML documents to the correct destination.

End point URLs for child sites are in the following format:

https://s1-integration.ariba.com/Buyer/cxmlchannel/ANID-SystemID

In the preceding URL:

• ANID is the Ariba Network ID of the site, which is the ID of the SAP Business Network account.
• SystemID is the business application system ID specific to the child site.

For example:

https://s1-integration.ariba.com/Buyer/cxmlchannel/AN02002355307-CHILD1

For information about setting up end points for child sites, see Configuring End Points When You Have Multiple ERP
Systems.

Setting the Business Application System ID in a Child Site

An SAP Ariba representative enters the system ID in the child site profile so that all communications from a child
site include the site's system ID.

Prerequisites

The SAP Business Network buyer administrator creates a business application system ID for each child site.

Procedure

1. In SAP Ariba Procurement Service Manager, administer the customer site for which you want to set the
business application system ID.
2. In the Ariba Network Settings section, enter the site's business application system ID in the Network
Business Application System ID field. This value must match the value created in the SAP Business Network
buyer account.
3. Click OK.
4. For sites with SAP Ariba Invoice Management, in the top section of the page, fill in the ERP Network ID (SSI)
field in the following format:

SystemID-NetworkID

Multi-ERP Configuration Guide

Deploying Multi-ERP Configurations PUBLIC 47
  Note

The ERP network ID must be configured in this way so that copy orders and subsequent messages from
SAP Business Network are posted to SAP Ariba Invoice Management.

Results

Communications between the buyer and suppliers will now include the appropriate routing information.

Loading Data into the Parent Site

The customer administrators loads data into the parent site.

Prerequisites

Rationalize master data as described in Master Data Rationalization in Multi-ERP Configurations [page 31].

Context

For general information about importing data into sites, including the order in which you should perform import
tasks on a given site, see the Common Data Import and Administration for SAP Ariba Procurement Solutions.

You can use the same SAP Ariba integration toolkit for all sites in the deployment.

Procedure

1. In the upper right corner of the dashboard, click Site, and select the parent site from the pull-down menu.

2. On the dashboard, click Manage Core Administration .

3. Select Site Manager Data Import/Export .

4. Use the data import tasks to import the CSV files prepared for the parent site with data that will be replicated to
the child sites.
5. For multi-variant configurations, import data specific to the parent site (such as Users.csv).
6. Import customer catalog content.

Multi-ERP Configuration Guide

48 PUBLIC Deploying Multi-ERP Configurations
Configuring Replication for Child Sites
For each child site, an SAP Ariba representative specifies a data replication configuration.

For information about available configurations, see About Replication Configuration Types [page 8].

As soon as you choose a configuration, replication begins.

 Note

Do not set the replication configuration for more than two child sites at once. After setting the configuration for
the first two child sites, wait for the data replication operation to finish, and then set the configuration for the
next two child sites.

Setting the Data Replication Configuration Type

An SAP Ariba representative sets the data replication configuration for single-variant and multi-variant child sites.

Procedure

1. In SAP Ariba Procurement Service Manager, administer the parent site for which you want to configure
replication.

2. Select FPC Manager Replication Setup .

3. Click the Configuration tab.
4. Select a child site from the Site pull-down menu.
5. Click Select, click a configuration type, and click OK.

Replication starts as soon as you select a configuration type. To check whether replication is finished, refresh
the page and refer to the Update Time column.
6. For single-variant configurations, if you want variant-specific user data to be replicated, make sure to subscribe
to it. By default, it is not replicated.
7. Check replication status to see whether replication was successful for all data. For information, see “ Checking
Replication Status” [page 50].
8. Set the configuration type for the next child site.
9. If there are more than two child sites, wait for replication to finish on the first two child sites, then set the
configuration type for the next child site.

During initial configuration, it's a good idea to avoid replicating data to more than two child sites at one time.

Multi-ERP Configuration Guide

Deploying Multi-ERP Configurations PUBLIC 49
Checking Replication Status

SAP Ariba monitors replication status and takes corrective action if errors occur.

Procedure

1. In SAP Ariba Procurement Service Manager, administer the parent site for which you want to configure
replication.

2. Select FPC Manager Replication Setup .

3. Click the Configuration tab.
4. Select a child site from the Site pull-down menu.
5. Check the Status column to see the status of each data class.

For information about status indicators, see About the Replication Setup User Interface [page 28].
6. To view the replication log, click the Actions menu for a class or group of classes, and choose View log.

To view the replication log for all data at once, use the Actions menu for the All group.

Next Steps

After you investigate and correct replication errors, you can use the Actions menu on the Replication Setup page
to initiate replication again.

Replication Log

The replication log, accessible to SAP Ariba representatives only, provides information about the most recent
replication event.

In the replication log, the Duration column displays the number of miliseconds spent on the last replication. The
Replication Failed column dislpays the number of records for which replication has never succeeded, whereas the
Failed column shows the number of records that failed in the last replication.

The following table describes the possible values in the Status String column.

Status String Description

Info Replication was successful. No records failed.

Error An unexpected exception has occurred, affecting individual records. Replication failed for the affected
records.

Multi-ERP Configuration Guide

50 PUBLIC Deploying Multi-ERP Configurations
Status String Description

Fatal An exception has occurred in the framework, potentially affecting all records being replicated. Replica-
tion was stopped.

An example of when this can occur is if a node dies during a replication run. This type of error resolves
itself with the next successful run.

Stopped Replication has stopped completely. Fatal errors occurred in subsequent replication runs, and the
replication operation itself might have negative effects on the system. Engineering investigation is
required before replication can continue.

Subscribing to Customer Catalog Content

When configuring Multi-ERP replication, SAP Ariba Commerce Services can subscribe or unsubscribe to specific
customer catalogs on behalf of a child site. Customer catalog content resides in the parent site.

Procedure

1. In SAP Ariba Procurement Service Manager, administer the parent site for which you want to configure
replication.

2. Select FPC Manager Replication Setup .

3. Click the Configuration tab.
4. Select a child site from the Site dropdown.
5. In the Content section, find the customer catalog to subscribe to or unsubscribe from.
6. Click Actions and choose Subscribe or Unsubscribe.

Child Site Customizations

Child sites inherit customizations from the parent site. SAP Ariba representatives can override inherited parameter
values, approval rule settings, and other customizations in the child sites.

For information about modifying customizations in child sites, see Child Site Customizations in Multi-ERP
Configurations [page 60].

For information about how approval rules, and parameters, and other customizations are replicated in multi-ERP
systems, see About Customizations [page 26].

Multi-ERP Configuration Guide

Deploying Multi-ERP Configurations PUBLIC 51
Loading Site-Specific Data into Child Sites
The customer administrator performs this task after notification from the SAP Ariba representative that data
replication is complete.

Prerequisites

Load data into child sites after replication from the parent site is complete.

Have the rationalized CSV files for the child sites ready for importing.

Context

When working with single- and multi-variant configurations, the customer administrator must rationalize the
data before importing it into parent and child sites. For information about data rationalization, see Master Data
Rationalization in Multi-ERP Configurations [page 31].

For general information about importing data into sites, including the order in which to perform the import tasks on
a given site, see the Common Data Import and Administration for SAP Ariba Procurement Solutions.

Procedure

1. In the upper right corner of the dashboard, click Site, and select the a child site from the pull-down menu.

2. On the dashboard, click Manage Core Administration .

3. Select Site Manager Data Import/Export .

4. Use the data import tasks to import the CSV files prepared for the child site you are working with.

Next Steps

If you encounter supplier ID conflicts when you import site-specific supplier organizations, see Correcting Supplier
ID Conflicts [page 57].

Multi-ERP Configuration Guide

52 PUBLIC Deploying Multi-ERP Configurations
Multi-ERP Configuration Testing
A table lists workflows to test before the SAP representative pushes a multi-ERP deployment to production.

Task Disconnected Multi-Variant Single-Variant

Switch between sites Yes Yes Yes

Create reports that pull data from all sites. Yes Yes Yes

Reassign an invoice from one child site to another (applies to Yes Yes Yes
invoices from SAP Business Network only).

Test the availability of customer catalog content on each child No Yes Yes
site.

Create a global contract in a child site and create a release No Yes Yes
against it from another site.

Create a no-release global contract in a child site and invoice No Yes Yes
against it from another site.

Create a purchase requisition and push it through to the pay- No Yes Yes
ment stage.

Create users in the parent site and make sure they are repli- No Yes Yes
cated to child sites.

Make user profile modifications in a child site and make sure No Yes Yes
the changes are applied to other related sites.

Verify that flex fields are replicated. No Yes Yes

Test parameter and approval rule overrides. No Yes Yes

Export transactional data for import into ERP systems. No Yes Yes

Push Multi-ERP Configurations from Test to

Production
An SAP representative pushes a multi-ERP test system to production.

Context

When pushing single-variant and multi-variant configurations from the test environment to a production
environment, be sure to follow the steps in the recommended order.

In single- and multi-variant configurations, if you modify parameters or standard AML customizations in a test site
and then push the configuration to a production parent site, the changes are immediately replicated to the child
sites.

Multi-ERP Configuration Guide

Deploying Multi-ERP Configurations PUBLIC 53
Procedure

1. Establish the parent–child relationships between sites in the production environment.

2. Push the test parent site configuration to the production parent site.
3. Push each test child site configuration to the corresponding production child site.
4. For single- and multi-variant configurations, load the appropriate master data into the production parent site.
5. For disconnected and multi-variant configurations, and for single-variant configurations in which user
replication is disabled in the test site, load data for parent site users into the parent site.
6. For each production child site, set the data replication configuration as appropriate.
7. Wait for replication to finish in single- and multi-variant configurations.
8. Load the appropriate site-specific master data into each production child site.
9. Push the test reporting site to the production reporting site.

Multi-ERP Configuration Guide

54 PUBLIC Deploying Multi-ERP Configurations
Maintaining Multi-ERP Configurations

Routine tasks for maintaining a multi-ERP configuration include pushing transactional data to ERP systems,
performing incremental data loads, modifying replicated data in child sites, switching supplier organizations from
site-specific to enterprise wide, correcting supplier ID conflicts, setting up remote authentication, and modifying
child-site approval processes.

Additional tasks performed by SAP Ariba Commerce Services include modifying child site customizations, and
modifying flex fields and standard AML customizations.

Pushing Transactional Data to External ERP Systems

To push transactional data to an external ERP system, export the data from the corresponding child site and import
it into the ERP system. You can use the SAP Ariba integration toolkit to do this.

For information, refer to SAP Ariba integration toolkit guide and Integrating SAP Ariba cloud solutions procurement
and invoicing data with SAP ERP and SAP S/4HANA.

Performing Incremental Data Loads

You can perform incremental data loads in a multi-ERP configuration.

 Note

Before loading new data into a multi-ERP system, be sure to review About Data Replication [page 55] and
About Rationalizing Data [page 55].

Keep the following guidelines in mind:

• New data in the parent site overwrites corresponding data in child sites.
• It’s important to pay attention to data dependency. If child site data depends on parent site data, parent site
data must be loaded first. Make sure the new parent site data is fully replicated before loading data into the
child sites.
• When you export data from ERP systems, export data for the parent site and child sites at the same time to
ensure that the data is consistent with itself.
• Provide sufficient time for replication to occur before loading site-specific data into child sites. For large
amounts of data, allow at least two hours for data replication to complete before loading site-specific data into
the child sites.

Multi-ERP Configuration Guide

Maintaining Multi-ERP Configurations PUBLIC 55
Modifying Replicated Data in Child Sites
You cannot modify replicated data in the child sites except in a few cases.

You can:

• add users and child groups to groups

• modify users' shipping and billing addresses
• add suppliers to supplier organizations
• modify user profiles (see About Modifying User Profiles [page 62])

You can view these modifications only from the child site in which you made them.

Subsequent modifications in the parent site are replicated to child sites, but do not override additions made in the
child sites.

Removing the relationship between a parent site and a child site makes replicated data externally maintainable
(modifiable) in the child site. (This does not apply to system objects, such as default groups.) Similarly,
deactivating an object in the parent site makes the object deactivated and externally maintainable in child sites.
Reestablishing the parent–child relationship or reactivating an object in the parent site causes data to be replicated
from the parent site again.

Switching Supplier Organizations from Site-Specific

to Enterprise-Wide
To convert a site-specific supplier organization into an enterprise-wide supplier organization, the customer
administrator creates the supplier organization in the parent site.

 Note

Do not make this change if there is transactional data that refers to the supplier organizations involved.

If the supplier organization you want to move is one that was autogenerated when you loaded supplier data, you
must find out its supplier ID so you can include it in the supplier organization CSV files to be loaded into parent
site. Because autogenerated supplier IDs are not visible in the user interface, to see them, you must export supplier
organization data from the child site and view the export file. The supplier ID should be in the buyersystemid
domain.

When the supplier organization is replicated to the child sites, if the child sites include autogenerated supplier
IDs, supplier ID conflicts might arise. You can resolve supplier ID conflicts by following the instructions in the next
section.

For information about autogenerated supplier IDs, see Understanding the Supplier Data Import Process [page 39].

Multi-ERP Configuration Guide

56 PUBLIC Maintaining Multi-ERP Configurations
Supplier ID Conflicts in Multi-ERP Configurations
When you import supplier data in multi-ERP configurations, if your CSV files map supplier organizations to
organization IDs incorrectly, supplier ID conflicts arise. You must correct these conflicts.

Correcting supplier ID conflicts consists of the following procedures:

• Editing Supplier Organization Data, and Removing Links Between Suppliers and Automatically Generated
Supplier Organizations [page 57] the supplier organization information in CSV files.
• Removing Incorrect Data from a Child Site [page 58] incorrect data from the child site.
• Replicating the Correct Supplier Organizations from the Parent Site and Establishing Links to Suppliers [page
58] the correct data (replicate supplier organizations from the parent site and reimport the suppliers).

 Tip

The process for correcting supplier ID conflicts is complex. Consider correcting one conflict at a time until
you are comfortable with the steps.

For general information about the supplier import process, see Understanding the Supplier Data Import Process
[page 39].

Editing Supplier Organization Data, and Removing Links

Between Suppliers and Automatically Generated Supplier
Organizations
You can edit supplier organization data and remove links between supplier and automatically generated supplier
organizations to correct supplier ID conflicts in multi-ERP configurations.

Procedure

1. In the child site, export the supplier organization data using the Export Supplier Organizations task. When
prompted for an adapter source, select External.

The export operation creates a ZIP file containing the files SupplierOrganization_Export.csv and
SupplierOrganizationOrganizationIDs_Export.csv. Using these files, you can see which supplier
organizations were automatically generated. The following steps guide you through correcting the data to
remove these automatically generated supplier organizations.
2. Create new SupplierOrganizations.csv and SupplierIDs.csv files to contain the corrections to make
to the data.
3. Populate the SupplierOrganizations.csv file you created in step 2 with the automatically generated
supplier organizations from SupplierOrganization_Export.csv.
4. In the SupplierIDs.csv file you created in step 2, add one entry for each of the entries in
SupplierOrganizations.csv. In the Domain and Value columns, create fictional, unique domain-value
pairs, one pair for each entry. These domain-value pairs will replace the existing domain-value pairs that are

Multi-ERP Configuration Guide

Maintaining Multi-ERP Configurations PUBLIC 57
 linked to the automatically generated supplier organizations, allowing you to remove the supplier organizations
later.

 Tip

When you create the fictional domain-value pairs, use values that are outside the range of any existing
domain-value pairs in the system to avoid affecting functioning suppliers in the system.

Removing Incorrect Data from a Child Site

You can remove incorrect data from a child site using the Import Supplier Organization task.

Procedure

1. In the child site, use the Import Supplier Organizations task to import the data in the
SupplierOrganizations.csv and SupplierIDs.csv files you created in the previous procedure. Choose
the Update Only import option.
2. Verify that the import task in step 1 was completed and that the number of updated records matches the
number of entries in the SupplierIDs.csv file that you imported. The suppliers are no longer linked to the
automatically generated supplier organizations.
3. Deactivate the automatically generated supplier organizations. To do so, run the Import Supplier
Organizations task again, this time choosing the Delete option.
4. Verify that the import task in step 3 was completed and that the number of deleted records matches the
number of entries in the SupplierIDs.csv file that you imported.

Replicating the Correct Supplier Organizations from the

Parent Site and Establishing Links to Suppliers
In concert with an SAP representative, customer administrators can replicate correct supplier organizations from a
parent site and establish links to suppliers.

Procedure

1. An SAP representative performs the following actions.

a. On the Replication Setup page for the child site, find the listing for Common Supplier data.
b. In that row, choose Actions Retry failed records .
c. Verify that the supplier organizations were replicated to the child site without errors.
2. The customer administrator performs the following steps to reimport the suppliers and establish the correct
links between suppliers and supplier organizations.

Multi-ERP Configuration Guide

58 PUBLIC Maintaining Multi-ERP Configurations
 a. In the child site, use the Import Suppliers task to import Supplier.csv and SupplierLocation.csv.

Choose the Load option.

b. Verify that the suppliers are correctly linked to the replicated supplier organizations.

Remote Authentication in Multi-ERP Configurations

Multi-ERP configurations can be set up for remote authentication through child sites. An SAP Ariba representative
performs this task.

It’s possible to configure different remote authentication settings for each child site. However, successful
authentication in one child site applies to all sites the user has access to.

Overriding an Inherited Approval Process in a Child

Site
For each type of approvable, you can override the inherited approval process by activating a different approval
process in the child site.

Context

Activation settings set manually in the child sites remain in place even when other changes to the inherited
approval process are replicated from the parent site.

You can also modify inherited approval processes in the following ways:

• Add approval rules

• Disable edit and filter rules
• Copy edit and filter rules, and edit the copies

Changes to the approval process in the parent site are merged into the approval process in the child site.

Procedure

1. In the upper right corner of the dashboard, click Site, and select the parent site from the pull-down menu.

2. On the dashboard, click Manage Approval Processes .

3. Find and open the approval process you want to use.
4. Click Activate.

Multi-ERP Configuration Guide

Maintaining Multi-ERP Configurations PUBLIC 59
Results

The approval process in the child site is activated, and the inherited approval process is deactivated.

For information about the replication of approval processes, see About Approval Processes [page 26]. For details
about working with approval processes, see the Approval Process Management Guide.

Child Site Customizations in Multi-ERP

Configurations
Child sites inherit customizations from the parent site. SAP Ariba representatives can override inherited parameter
and approval rule settings in child sites.

For details about how approval rules, and parameters, and other customizations are treated in multi-ERP
configurations, see About Customizations [page 26].

Overriding Inherited Parameter Values in Child Sites

SAP Ariba representatives with the appropriate group membership can override an inherited parameter value on a
child site.

Context

In a child site, resetting a parameter that was modified in the child site causes the parameter value to be inherited
from the parent site again.

In SAP Ariba Procurement Service Manager, the Parameters page for a child site includes an Inherited Value
column. This column contains a value only if the parameter value in the parent site is something other than the
default value. The presence of a value in this column indicates that the child site is inheriting a value other than the
default value.

Procedure

1. In SAP Ariba Procurement Service Manager, administer the child site for which you want to change a
parameter value.
2. Click Advanced.

3. Select Customization Manager Parameters .

4. Find the parameter to change.

Multi-ERP Configuration Guide

60 PUBLIC Maintaining Multi-ERP Configurations
5. Edit the parameter value and click Save.

Modifying Flex Fields and Standard AML Customizations in

Child Sites
In child sites, customization changes inherited from the parent site are stored in the extension
ariba.variants.vrealm_n.runtimemodifications.extension.inherit.Modifications.

An SAP Ariba representative can download inherited extensions via the Customization Manager AML
Upload task.

You can override the inherited modifications with standard AML customizations made in
the child sites. Standard, non-inherited AML customizations are stored in the extension
ariba.variants.vrealm_n.runtimemodifications.extension.safecustomize.Modifications.

You can hide replicated flex fields in child sites, but you cannot remove them. You cannot upload or modify inherited
extensions directly in the child site. For example, you cannot add fields to an inherited eForm template class (or to a
flex master data template) by uploading standard AML extensions directly to the child site. Trying to do so triggers
an error.

 Note

Private AML customizations are permitted in child sites only. You cannot upload private AML customizations to
a parent site. Also, you cannot edit the reportability of an inherited flex field in the child site.

Multi-ERP Configuration Guide

Maintaining Multi-ERP Configurations PUBLIC 61
Multi-ERP Features for Users

End-user features in multi-ERP configurations include switching between sites, modifying user profiles, cross-site
reporting, reassigning invoices, creating global contracts, and using contract management integration.

Switching Between Sites in Multi-ERP Configurations

In a multi-ERP configuration, user authentication information applies to all related sites the user has access to.
After logging in to a site, cross-site users can switch to related sites without having to log in again.

Context

In suite-integrated systems, the dashboard shows procurement solution content from the current site along with
tasks from other SAP Ariba solutions (such as SAP Ariba Sourcing and SAP Ariba Contracts) from all sites.

Procedure

1. In the upper right corner of the dashboard, click Site.

2. Select the site to switch to.

User Profile Information in Multi-ERP Configurations

In multi-ERP configurations, users whose user profile information was replicated from the parent site can make
changes to their user profiles from any site they have access to.

Modifications to replicated user profile information affect other sites as follows:

• When a user modifies cross-variant user profile data (name, supervisor, email address) from a child site, the
change takes effect in all sites, including the parent site.
• In single-variant configurations, when a user modifies replicated variant-specific user data in a child site, the
change takes effect in all single-variant configurations in the system, including the parent site.
• Changes to notification preferences, dashboard preferences, default currency, and language settings in a child
site do not affect that information in other sites.
Each site in a multi-ERP configuration can have different languages enabled. For example, the parent site might
have only English enabled, and a child site might have English plus ten other languages enabled. Users can
choose from all the languages enabled for the site they are in when they change their locale.

Multi-ERP Configuration Guide

62 PUBLIC Multi-ERP Features for Users
 • Changes to group membership in a child site do not affect other child sites or the parent site, and they are not
overridden by subsequent data replication from the parent site.

Cross-Site Reporting in Multi-ERP Configurations

In multi-ERP configurations, users can create reports that query multiple sites.

The Source System field in reports indicates which site the data comes from. Users can filter reports based on this
field.

Because one child site can include fields that another child site lacks, fields in cross-site reports might be blank for
some records.

Users can report on data from multiple sites if their group membership includes one of the following:

• Membership in the ReportManager group in any site grants reporting access to all sites on which the user has
a user account.
• On sites that are not suite-integrated, membership in a ReportManager- SiteName group, where SiteName
represents the name of a site, grants reporting access to the corresponding site. (This functionality does not
work in suite-integrated environments.)

On sites that are not suite-integrated, a user’s permission set in the reporting site consists of the user’s
permissions from all child sites and the parent site, combined.

 Note

Supervisors can report on a subordinate’s data regardless of the supervisor’s group membership. If the
Visibility Control feature is enabled, reporting capabilities are limited by purchasing unit. For multi-ERP
environments that have the Visibility Control feature enabled, site administrators must assign purchasing unit
responsibilities to report users on the parent site in addition to the child site. For information about the Visibility
Control feature, see the Common Data Import and Administration for SAP Ariba Procurement Solutions.)

Reporting Access in Suite-Integrated Sites

In suite-integrated sites, an SAP Ariba representative must set a site configuration option if the buyer wants to
prevent certain report users (users belonging to groups with a QueryAll permission) from being able to access
data on all sites in the multi-ERP configuration. (The QueryAll permission, included in management-related
groups such as Purchasing Manager, enables a user to see data in all approvables that pertain to the group rather
than only the approvables created by the user.)
Application.Analysis.FPCReportingEnabled
In suite-integrated sites configured to support multi-ERP and reporting, this parameter
determines whether reporting visibility is restricted to the sites on which users have a user
account. The parameter takes a Boolean value:

• If this parameter is set to Yes (true), all reporting users can see only the data on the
sites where they have user accounts.

Multi-ERP Configuration Guide

Multi-ERP Features for Users PUBLIC 63
 • If this parameter is set to No (false), reporting visibility behaves in the same way as
before. Users in groups with a QueryAll permission can see data from all child sites.

This parameter does not affect users who belong to the SV Senior Analyst group, which
includes the SVAuthorized permission. These users can see all data in invoice and
purchase order line items regardless of the parameter setting.

By default, this parameter is set to No.

Cross-Site Reporting Limitations

The fields available for reporting include only the fields applicable to the variant of the parent site.

For example, suppose the parent site is configured as a PeopleSoft variant. In that case, even if there are child sites
configured as SAP or Generic variants, the only fields you see in reporting are the fields available for PeopleSoft
variants. Fields specific to SAP and Generic variants are not available in cross-site reporting.

The Company Code dimension for reporting supports one company code description for each company code
unique ID across all sites in multi-ERP configurations. Differences in company code descriptions from one site to
another aren't reflected in reports.

Reassigning Invoices in Multi-ERP Configurations

In multi-ERP configurations, users who belong to the Invoice Manager group can reassign invoices to a different
site for reconciliation.

Context

Reassigning an invoice recreates the it in the new site and removes it from the original site. Any changes made in
the original site are lost.

Invoice reassignment applies to invoices that meet the following conditions:

• The invoice was received from SAP Business Network.

• The status is Reconciling.

Procedure

1. Open the invoice reconciliation and go to the Exceptions tab.

2. Click Edit.
3. Click Change Site.

Multi-ERP Configuration Guide

64 PUBLIC Multi-ERP Features for Users
 4. Select the site to which you want to assign the invoice.

Making a Contract Available to All Child Sites

In single- and multi-variant configurations, you can make a contract available to all child sites. Such contracts are
called global contracts.

Context

Global contracts offer the following benefits:

• Users in all sites can create purchase orders against the contract.
• Cross-site contract searching allows users to find the best deal on all sites.
• When you view a contract, the Contract Orders tab lists all purchase orders released against the contract.
• Global contracts support contract-based invoicing.

 Note

In global contracts, accounting information is not displayed for pricing terms for line items. This is because
accounting information is not necessarily the same in all child sites.

 Note

When searching for contracts or contract requests, do not use variant-specific fields (such as, Company Code
or purchase organization) as search filters.

To be eligible for global release access, a contract:

• can be any type: item level, supplier level, commodity level, or customer catalog level
• cannot be a blanket purchase order
• can be a standalone agreement, master agreement, or subagreement

If your contract is a global master agreement, you can create separate subagreements for each partition, or the
subagreements themselves can also be global.

The following additional points apply to global contracts:

• You can modify, print, and export global contracts only in the site in which they were created.
• You can change or cancel a release only from the site in which it was created.
• Global contracts with non-catalog items add the items to the customer catalog view in the child site. Other
child sites using the contract can see those items.
• You can perform reconciliation between an invoice, receipt, and contract only if all three objects reside in the
same site.
• You cannot associate purchasing units with global contracts, even if purchasing unit filtering is enabled on the
site in which you are creating the contract.

Multi-ERP Configuration Guide

Multi-ERP Features for Users PUBLIC 65
Procedure

1. In the Contract wizard, go to the Definitions page.

2. In the Release Access From field, click All Sites (Global Contract).

Maintain global contracts in the site in which they were created. You can change or cancel a release only from
the site in which it was created.

Integration with SAP Ariba Contracts

In SAP Ariba Contracts, there is no concept of parent and child sites. The concept of multi-ERP is specific to SAP
Ariba Procurement solutions.

In SAP Ariba Contracts, when you create contract pricing terms for use in a procurement contract, you must
designate a child site to receive the data and generate the contract request in SAP Ariba Procurement solutions.

The following procedure is a high-level overview of the workflow. For details about working with contract
workspaces, see Managing Projects, Teams, Documents, and Tasks.

1. Create a contract workspace (procurement).

2. (Optional) Upload a document to the contract workspace, setting Use As to Contract Content.
3. Create the contract terms, specifying the procurement child site to which you want to send this contract
information.
The Site field is a required field. You must select a child site.
4. When you click OK after filling out the mandatory data for the contract terms, a contract request opens in the
procurement child site that you specified. If you uploaded contract pricing terms in SAP Ariba Contracts, they
are included in the contract request.

The rest of the workflow is the same as it is when SAP Ariba Contracts is integrated with standalone procurement
sites.

Approval Delegation in Multi-ERP Configurations

In multi-ERP configurations, authority delegation is site-specific.

When a user delegates approval authority to another user for a specific amount of time, the delegation is applicable
only in the site the user was in when creating the delegation.

For example, suppose user Martha Hughes has access to child sites 1 and 2. While accessing child site 1, she
creates a delegation, delegating authority to user Danielle Howard. This delegation will apply to approval requests
routed to Martha in child site 1 but not child site 2. Martha can create a separate delegation on child site 2.

Multi-ERP Configuration Guide

66 PUBLIC Multi-ERP Features for Users
Data Replication Reference for Multi-ERP
Configurations

Data replication makes uses of CSV files. Reference tables lists these files and indicate whether they are used for
single- or multi-variant configuration.

Additional tables list cross-variant data classes and their corresponding CSV files.

For general information about CSV files that can be imported into sites, see the Common Data Import and
Administration for SAP Ariba Procurement Solutions and the Procurement Data Import and Administration Guide.

Related Information

Data Replication in Multi-ERP Configurations [page 23]

Master Data Rationalization in Multi-ERP Configurations [page 31]

Cross-Variant Data Classes and CSV Files in Multi-

ERP Configurations
When CSV files are loaded into a parent site, cross-variant data is replicated to child sites in both single- and
multi-variant configurations. This topic lists cross-variant data classes and the corresponding CSV files.

SAP Ariba representatives can view this data on the Replication Setup page in SAP Ariba Procurement Service
Manager. Cross-variant data is listed in the Data section under the heading Common. For more information, see
About the Replication Setup User Interface [page 28].

Table 11: Data Replicated in Single- and Multi-Variant Configurations When Loaded into the Parent Site (continued)
Data Class CSV Files

Account Type AccountType.csv

AllowableHierarchyChioce AllowableHierarchyChoice.csv

Approval Queue ApprovalQueue.csv

Attendee Company Not applicable

BankAccountIDType BankAccountIDType.csv

BankAccountType BankAccountType.csv

BankIDType BankIDType.csv

BatchAuditPolicyType BatchAuditPolicyType.csv

Multi-ERP Configuration Guide

Data Replication Reference for Multi-ERP Configurations PUBLIC 67
Data Class CSV Files

BuyerImportTracker Not applicable

BuyerSubscriptionInfo Not applicable

BuyerSubscriptionVersion Not applicable

Catalog Supplier Data Not applicable

Category Driver CategoryDriver.csv

ChargeExceptionType ChargeExceptionType.csv

ClassificationCodeDomainMet ClassificationCodeDomainMeta.csv
a

ClassificationCodeMap ClassificationCodeMap.csv

CommodityCode CommodityCode.csv, EClassCommodityCode.csv,

NAICSCommodityCode.csv, and other system commodity code files

Common Supplier SupplierOrganizations.csv, SupplierIDs.csv

CurrencyConversionRate CurrencyConversionRate.csv

Expense Policy Type ExpensePolicyType.csv

ExpenseTypeToGroupMap ExpenseTypeToGroupMap.csv

Flex Master Data Not applicable

GenericRelationEntry RelationEntry.csv

GenericRelationType RelationType.csv

Group CustomGroup.csv, GroupChildGroupMap.csv,

GroupParentGroup.csv, GroupSharedUserMap.csv,
UserParentGroup.csv

Invoice Exception Rule InvoiceExceptionType.csv,

InvoiceExceptionTypeValidation.csv,
InvoiceExceptionTypeOverrideValidation.csv

Kit Not applicable

Labor Laws Not applicable

Labor Pay Code LaborPayCode.csv

NonCatRef Not applicable

Password Not applicable

Payment Bank Location BuyerPaymentBankLocation.csv,

SupplierPaymentBankLocation.csv

Payment Location Not applicable

PaymentMethodType PaymentMethodType.csv

PaymentProvider Not applicable

PaymentType ExpensePayment.csv

Multi-ERP Configuration Guide

68 PUBLIC Data Replication Reference for Multi-ERP Configurations
Data Class CSV Files

PCard PCard.csv

Permission Not applicable

Print Configuration Not applicable

Procure Line Type ProcureLineType.csv

ProcurementUnit PurchasingUnit.csv

RealTimeAuditPolicyType RealTimeAuditPolicyType.csv

ReceiptByCommodityCode ReceiptByCommodityCode.csv

ReceiptByPartNumber ReceiptByPartNumber.csv

RemittanceLocation RemittanceLocation.csv

Shared Addresses Not applicable

Shared Users SharedUser.csv, SharedUserSupervisor.csv

ShippingCarrier Not applicable

String Maps Not applicable

Subscription Not applicable

SubscriptionVersion Not applicable

Tax Type Map TaxTypeMap.csv

TaxCodeMapping ChargeTaxCodes.csv

UnitOfMeasure UnitOfMeasure.csv

Variant-Specific Data Classes and CSV Files in Multi-

ERP Configurations
When these CSV files are loaded into a parent site, variant-specific data is replicated to child sites in single-variant
configurations. This topic lists variant-specific data classes and the corresponding CSV files. On the Replication
Setup page in SAP Ariba Procurement Service Manager.

SAP Ariba representatives can view this data on the Replication Setup page in SAP Ariba Procurement Service
Manager. Variant-specific data is listed in the Data section under the heading ERP-specific. For more information,
see About the Replication Setup User Interface [page 28].

Tables are provides for PeopleSoft, SAP, and Generic variants. which list the variant-specific data classes and the
corresponding CSV files.

Multi-ERP Configuration Guide

Data Replication Reference for Multi-ERP Configurations PUBLIC 69
Variant-Specific Data Classes: PeopleSoft Variants
The following table lists the data classes and the corresponding CSV files specific to the PeopleSoft variant. This
data is replicated to child sites in single-variant configurations.

Table 12: PeopleSoft variant-specific data replicated in single-variant configurations when loaded into the parent site (continued)
Data Class CSV Files

Account Account.csv

AccountingCombination AccountingCombination.csv

AccountingCombinationGroup AccountingCombinationGroup.csv

Address Address.csv

AutoType AutoType.csv

BusinessUnit BusinessUnit.csv

CommodityExportMapEntry ERPCommodityCodeMap.csv

Department Department.csv

Expense Code Mapping ExpenseCodeMapping.csv

Expense Type ExpenseType.csv

ExpenseHeaderCategoryMap ExpenseHeaderCategoryMap.csv

ExpenseTaxCodeLookup ExpenseTaxCodeLookup.csv

ExpenseTaxRateLookup_TaxCod ExpenseTaxRateLookupByTaxCode.csv
e

GLBusinessUnit GLBusinessUnit.csv

Invoice Exception Override InvoiceExceptionTypeCCCOverride.csv (commodity code),

InvoiceExceptionTypeSupplierOverride.csv

Level 2 Adjustment Type Charge.csv

Location Type LocationType.csv

Partitioned Commodity Code ERPCommodityCode.csv

Payment Terms PaymentTerms.csv, PaymentTermSteps.csv,

PaymentTermStepDetails.csv

Product Product.csv

Project Project.csv

ReceiptImagingConfiguration Not applicable

SetId SetId.csv

StatisticsCode Statistics.csv

Supplier Supplier.csv, SupplierSupplement.csv

Multi-ERP Configuration Guide

70 PUBLIC Data Replication Reference for Multi-ERP Configurations
Data Class CSV Files

Supplier Location SupplierLocation.csv, SupplierLocationSupplement.csv,

SLRemittanceInformation.csv,
SLRemittanceInformationDetails.csv

Tax Code TaxCode.csv

Tax Code Lookup Table TaxCodeLookup.csv

Tax Rate Lookup By Tax Code TaxRateLookupByTaxCode.csv

User User.csv, UserPCardMap.csv,

ResponsibleUser.csv, SharedUserShipToAddressMap.csv,
 Note SharedUserBillingAddressMap.csv,
Child sites can subscribe to and un- SharedUserSingleShipToAddressMap.csv,
subscribe from this data. For infor- UserApprovalLimit.csv
mation, see User and Group Data
[page 23].

VAT Defaults VATDefaults.csv

Variant-Specific Data Classes: SAP Variants

The following table lists the data classes and the corresponding CSV files specific to the SAP variant. This data is
replicated to child sites in single-variant configurations.

Table 13: SAP Variant-Specific Data Replicated in Single-Variant Configurations When Loaded into the Parent Site (continued)
Data Class CSV Files

AccCategoryFieldStatusCombo AccCategoryFieldStatusCombo.csv

Account Account.csv

AccountCategory AccountCategory.csv

Address Address.csv

AdjustmentType AdjustmentType.csv

Asset Asset.csv

AutoType AutoType.csv

CommodityExportMapEntry ERPCommodityCodeMap.csv

CompanyCode CompanyCode.csv

CompanyCodeIOCombo CompanyCodeIOCombo.csv

CompanyCodeWBSCombo CompanyCodeWBSCombo.csv

CostCenter CostCenter.csv

Expense Code Mapping ExpenseCodeMapping.csv

Expense Type ExpenseType.csv

Multi-ERP Configuration Guide

Data Replication Reference for Multi-ERP Configurations PUBLIC 71
Data Class CSV Files

ExpenseHeaderCategoryMap ExpenseHeaderCategoryMap.csv

ExpenseTaxCodeLookup ExpenseTaxCodeLookup.csv

ExpenseTaxRateLookup_TaxCode ExpenseTaxRateLookupByTaxCode.csv

FieldStatusToAccountingFieldNa FieldStatusToAccountingFieldNameMap.csv
meMap

GeneralLedger GeneralLedger.csv

InternalOrder InternalOrder.csv

ItemCategory ItemCategory.csv

Invoice Exception Override InvoiceExceptionTypeCCCOverride.csv (commodity code),

InvoiceExceptionTypeSupplierOverride.csv

Level 2 Adjustment Type AdjustmentType.csv

Location Type LocationType.csv

Partitioned Commodity Code ERPCommodityCode.csv

Payment Terms PaymentTerms.csv, PaymentTermSteps.csv,

PaymentTermStepDetails.csv

PlantPurchaseOrgCombo PlantPurchaseOrgCombo.csv

PorgSupplierCombo PurchasOrgSupplierCombo.csv

PurchaseGroup PurchaseGroup.csv

PurchaseOrg PurchaseOrg.csv

Supplier Supplier.csv, SupplierSupplement.csv, MinorityVendor.csv

Supplier Location SupplierLocation.csv, SupplierLocationSupplement.csv,

SLRemittanceInformation.csv,
SLRemittanceInformationDetails.csv

Tax Code TaxCode.csv

Tax Code Lookup Table TaxCodeLookup.csv

Tax Rate Lookup By Tax Code TaxRateLookupByTaxCode.csv

TaxRateLookup Not applicable

User User.csv, UserPCardMap.csv,

ResponsibleUser.csv, SharedUserShipToAddressMap.csv,
 Note SharedUserBillingAddressMap.csv,
Child sites can subscribe to and unsub- SharedUserSingleShipToAddressMap.csv,
scribe from this data. For information, UserApprovalLimit.csv
see User and Group Data [page 23].

VAT Code VATCode.csv

VAT Defaults VATDefaults.csv

VAT Rate Lookup VATRateLookup.csv

Multi-ERP Configuration Guide

72 PUBLIC Data Replication Reference for Multi-ERP Configurations
Data Class CSV Files

WBSElement WEBElement.csv

Variant-Specific Data Classes: Generic Variants

The following table lists the data classes and the corresponding CSV files specific to the Generic variant. This data
is replicated to child sites in single-variant configurations.

Table 14: PeopleSoft Variant-Specific Data Replicated in Single-Variant Configurations When Loaded into the Parent
Site (continued)
Data Class CSV Files

Account Account.csv

AccountingCombination AccountingCombination.csv

AccountingCombinationGroup AccountingCombinationGroup.csv

Address Address.csv

AdjustmentType AdjustmentType.csv

AutoType AutoType.csv

BusinessUnit BusinessUnit.csv

CommodityExportMapEntry ERPCommodityCodeMap.csv

Company Company.csv

CostCenter CostCenter.csv

Expense Code Mapping ExpenseCodeMapping.csv

Expense Type ExpenseType.csv

ExpenseHeaderCategoryMap ExpenseHeaderCategoryMap.csv

ExpenseTaxCodeLookup ExpenseTaxCodeLookup.csv

ExpenseTaxRateLookup_TaxCod ExpenseTaxRateLookupByTaxCode.csv
e

Invoice Exception Override InvoiceExceptionTypeCCCOverride.csv (commodity code),

InvoiceExceptionTypeSupplierOverride.csv

Level 2 Adjustment Type AdjustmentType.csv

Location Type LocationType.csv

Partitioned Commodity Code ERPCommodityCode.csv

Payment Terms PaymentTerms.csv, PaymentTermSteps.csv,

PaymentTermStepDetails.csv

Product Product.csv

Project Project.csv

Multi-ERP Configuration Guide

Data Replication Reference for Multi-ERP Configurations PUBLIC 73
Data Class CSV Files

Region Region.csv

SubAccount SubAccount.csv

Supplier Supplier.csv, SupplierSupplement.csv

Supplier Location SupplierLocation.csv, SupplierLocationSupplement.csv,

SLRemittanceInformation.csv,
SLRemittanceInformationDetails.csv

Tax Code TaxCode.csv

Tax Code Lookup Table TaxCodeLookup.csv

Tax Rate Lookup By Tax Code TaxRateLookupByTaxCode.csv

TaxRateLookup Not applicable

User User.csv, UserPCardMap.csv,

ResponsibleUser.csv, SharedUserShipToAddressMap.csv,
 Note SharedUserBillingAddressMap.csv,
Child sites can subscribe to and un- SharedUserSingleShipToAddressMap.csv
subscribe from this data. For infor-
mation, see User and Group Data
[page 23].

VAT Code VATCode.csv

VAT Defaults VATDefaults.csv

VAT Rate Lookup VATRateLookup.csv

CSV File Replication Reference for PeopleSoft

Variants
The following table lists the CSV files that contain data for PeopleSoft variants and specifies whether the data is
replicated to child sites when imported into the parent site of a multi-ERP configuration.

Table 15: Data Replication Reference for PeopleSoft Variants (continued)

Replicated in Single-Variant Con- Replicated in Multi-Variant Con-
File figurations figurations

Account.csv Yes No

AccountType.csv Yes Yes

AccountingCombination.csv Yes No

AccountingCombinationGroup.csv Yes No

Address.csv Yes No

Multi-ERP Configuration Guide

74 PUBLIC Data Replication Reference for Multi-ERP Configurations
 Replicated in Single-Variant Con- Replicated in Multi-Variant Con-
File figurations figurations

AutoType.csv Yes No

BusinessUnit.csv Yes No

CurrencyConversionRate.csv Yes Yes

CustomGroup.csv Yes Yes

Department.csv Yes No

ERPCommodityCode.csv Yes No

ERPCommodityCodeMap.csv Yes No

ExpenseCodeMapping.csv Yes No

ExpenseHeaderCategoryMap.csv Yes No

ExpenseTaxCodeLookup.csv Yes No

ExpenseTaxRateLookupByTaxCode.csv Yes No

ExpenseType.csv Yes No

GLBusinessUnit.csv Yes No

GroupChildGroupMap.csv Yes Yes

GroupParentGroup.csv Yes Yes

GroupSharedUserMap.csv Yes Yes

InvoiceExceptionType.csv Yes Yes

InvoiceExceptionTypeCCCOverride.csv Yes No

InvoiceExceptionTypeOverrideValidati Yes Yes

on.csv

InvoiceExceptionTypeSupplierOverride Yes No
.csv

PaymentTerms.csv Yes No

PaymentTermStepDetails.csv Yes No

PaymentTermSteps.csv Yes No

Product.csv Yes No

Project.csv Yes No

PurchasingUnit.csv Yes Yes

RelationEntry.csv Yes Yes

RelationType.csv Yes Yes

ResponsibleUser.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

Multi-ERP Configuration Guide

Data Replication Reference for Multi-ERP Configurations PUBLIC 75
 Replicated in Single-Variant Con- Replicated in Multi-Variant Con-
File figurations figurations

SetId.csv Yes No

SharedUser.csv Yes Yes

SharedUserBillingAddressMap.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

SharedUserShipToAddressMap.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

SharedUserSingleShipToAddressMap.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

SharedUserSupervisor.csv Yes Yes

SLRemittanceInformation.csv Yes No

SLRemittanceInformationDetails.csv Yes No

Statistics.csv Yes No

Supplier.csv Yes No

SupplierConsolidated.csv Yes Yes

The data that is imported into the parent site depends on the
ImportCtrl field value in the CSV file. For details, see About Ration-
alizing Data Using Consolidated CSV Files [page 31].

SupplierIDs.csv Yes Yes

SupplierLocation.csv Yes No

SupplierLocationSupplement.csv Yes No

SupplierOrganizations.csv Yes Yes

SupplierSupplement.csv Yes No

TaxCode.csv Yes No

TaxCodeLookup.csv Yes No

TaxRateLookupByTaxCode.csv Yes No

User.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

UserApprovalLimit.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

Multi-ERP Configuration Guide

76 PUBLIC Data Replication Reference for Multi-ERP Configurations
 Replicated in Single-Variant Con- Replicated in Multi-Variant Con-
File figurations figurations

UserConsolidated.csv Yes Yes

The data that is imported into the parent site depends on the
ImportCtrl field value in the CSV file. For details, see About Ration-
alizing Data Using Consolidated CSV Files [page 31].

UserParentGroup.csv Yes Yes

UserPCardMap.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

VATDefaults.csv Yes No

CSV File Replication Reference for SAP Variants

The following table lists the CSV files that contain data for SAP variants and specifies whether the data is replicated
to child sites when imported into the parent site of a multi-ERP configuration.

Table 16: Data Replication Reference for SAP Variants (continued)

Replicated in Single-Variant Con- Replicated in Multi-Variant Config-
File figurations urations

AccCategoryFieldStatusCombo.csv Yes No

AccountCategory.csv Yes No

AccountType.csv Yes Yes

AdjustmentType.csv Yes No

Asset.csv Yes No

AutoType.csv Yes No

CompanyCode.csv Yes No

CompanyCodeIOCombo.csv Yes No

CompanyCodeWBSCombo.csv Yes No

CostCenter.csv Yes No

CurrencyConversionRate.csv Yes Yes

CustomGroup.csv Yes Yes

ERPCommodityCode.csv Yes No

ERPCommodityCodeMap.csv Yes No

GeneralLedger.csv Yes No

GroupChildGroupMap.csv Yes Yes

Multi-ERP Configuration Guide

Data Replication Reference for Multi-ERP Configurations PUBLIC 77
 Replicated in Single-Variant Con- Replicated in Multi-Variant Config-
File figurations urations

GroupParentGroup.csv Yes Yes

GroupSharedUserMap.csv Yes Yes

InternalOrder.csv Yes No

ItemCategory.csv Yes No

InvoiceExceptionType.csv Yes Yes

InvoiceExceptionTypeCCCOverride.csv Yes No

InvoiceExceptionTypeOverrideValidat Yes Yes

ion.csv

InvoiceExceptionTypeSupplierOverrid Yes No
e.csv

MinorityVendor.csv Yes No

PaymentTerms.csv Yes No

PaymentTermStepDetails.csv Yes No

PaymentTermSteps.csv Yes No

Plant.csv Yes No

PlantPurchaseOrgCombo.csv Yes No

PurchaseGroup.csv Yes No

PurchaseOrg.csv Yes No

PurchaseOrgSupplierCombo.csv Yes No

PurchasingUnit.csv Yes Yes

RelationEntry.csv Yes Yes

RelationType.csv Yes Yes

ResponsibleUser.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

SharedUser.csv Yes Yes

SharedUserBillingAddressMap.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

SharedUserShipToAddressMap.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

Multi-ERP Configuration Guide

78 PUBLIC Data Replication Reference for Multi-ERP Configurations
 Replicated in Single-Variant Con- Replicated in Multi-Variant Config-
File figurations urations

SharedUserSingleShipToAddressMap.cs File is part of variant-specific user No

v data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

SharedUserSupervisor.csv Yes Yes

SLRemittanceInformation.csv Yes No

SLRemittanceInformationDetails.csv Yes No

Supplier.csv Yes No

SupplierConsolidated.csv Yes Yes

The data that is imported into the parent site depends on the
ImportCtrl field value in the CSV file. For details, see About Rationaliz-
ing Data Using Consolidated CSV Files [page 31].

SupplierIDs.csv Yes Yes

SupplierLocation.csv Yes No

SupplierLocationSupplement.csv Yes No

SupplierOrganizations.csv Yes Yes

SupplierSupplement.csv Yes No

TaxCode.csv Yes No

TaxCodeLookup.csv Yes No

TaxRateLookupByTaxCode.csv Yes No

User.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

UserApprovalLimit.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

UserConsolidated.csv Yes Yes

The data that is imported into the parent site depends on the
ImportCtrl field value in the CSV file. For details, see About Rationaliz-
ing Data Using Consolidated CSV Files [page 31].

UserParentGroup.csv Yes Yes

UserPCardMap.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

VATCode.csv Yes No

VATDefaults.csv Yes No

Multi-ERP Configuration Guide

Data Replication Reference for Multi-ERP Configurations PUBLIC 79
 Replicated in Single-Variant Con- Replicated in Multi-Variant Config-
File figurations urations

VATRateLookup.csv Yes No

WBSElement.csv Yes No

CSV File Replication Reference for Generic Variants

The following table lists the CSV files that contain data for Generic variants and specifies whether the data is
replicated to child sites when imported into the parent site of a multi-ERP configuration.

Table 17: Data Replication Reference for Generic Variants (continued)

Replicated in Single-Variant Con- Replicated in Multi-Variant Config-
File figurations urations

Account.csv Yes No

AccountType.csv Yes Yes

AccountingCombination.csv Yes No

AccountingCombinationGroup.csv Yes No

Address.csv Yes No

AdjustmentType.csv Yes No

AutoType.csv Yes No

BusinessUnit.csv Yes No

Company.csv Yes No

CostCenter.csv Yes No

CurrencyConversionRate.csv Yes Yes

CustomGroup.csv Yes Yes

ERPCommodityCode.csv Yes No

ERPCommodityCodeMap.csv Yes No

GroupChildGroupMap.csv Yes Yes

GroupParentGroup.csv Yes Yes

GroupSharedUserMap.csv Yes Yes

InvoiceExceptionType.csv Yes Yes

InvoiceExceptionTypeCCCOverride.csv Yes No

InvoiceExceptionTypeOverrideValidat Yes Yes

ion.csv

Multi-ERP Configuration Guide

80 PUBLIC Data Replication Reference for Multi-ERP Configurations
 Replicated in Single-Variant Con- Replicated in Multi-Variant Config-
File figurations urations

InvoiceExceptionTypeSupplierOverrid Yes No
e.csv

PaymentTerms.csv Yes No

PaymentTermStepDetails.csv Yes No

PaymentTermSteps.csv Yes No

Product.csv Yes No

Project.csv Yes No

PurchasingUnit.csv Yes Yes

Region.csv Yes No

RelationEntry.csv Yes Yes

RelationType.csv Yes Yes

ResponsibleUser.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

SharedUser.csv Yes Yes

SharedUserBillingAddressMap.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

SharedUserShipToAddressMap.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

SharedUserSingleShipToAddressMap.cs File is part of variant-specific user No

v data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

SharedUserSupervisor.csv Yes Yes

SLRemittanceInformation.csv Yes No

SLRemittanceInformationDetails.csv Yes No

SubAccount.csv Yes No

Supplier.csv Yes No

SupplierConsolidated.csv Yes Yes

The data that is imported into the parent site depends on the
ImportCtrl field value in the CSV file. For details, see About Rationaliz-
ing Data Using Consolidated CSV Files [page 31].

SupplierIDs.csv Yes Yes

Multi-ERP Configuration Guide

Data Replication Reference for Multi-ERP Configurations PUBLIC 81
 Replicated in Single-Variant Con- Replicated in Multi-Variant Config-
File figurations urations

SupplierLocation.csv Yes No

SupplierLocationSupplement.csv Yes No

SupplierOrganizations.csv Yes Yes

SupplierSupplement.csv Yes No

TaxCode.csv Yes No

TaxCodeLookup.csv Yes No

TaxRateLookupByTaxCode.csv Yes No

User.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

UserConsolidated.csv Yes Yes

The data that is imported into the parent site depends on the
ImportCtrl field value in the CSV file. For details, see About Rationaliz-
ing Data Using Consolidated CSV Files [page 31].

UserParentGroup.csv Yes Yes

UserPCardMap.csv File is part of variant-specific user No

data, so replication can be enabled
or disabled. For details, see User
and Group Data [page 23].

VATCode.csv Yes No

VATDefaults.csv Yes No

VATRateLookup.csv Yes No

Multi-ERP Configuration Guide

82 PUBLIC Data Replication Reference for Multi-ERP Configurations
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

Multi-ERP Configuration Guide

Important Disclaimers and Legal Information PUBLIC 83
www.ariba.com

Copyright © 2023 Ariba, Inc. All rights reserved.

This documentation, as well as the Ariba solutions, software and/or

services described in it, contain proprietary information. They are
provided under a license or other agreement containing restrictions on
use and disclosure and are also protected by copyright, patent and/or
other intellectual property laws. Except as permitted by such agreement,
no part of the document may be reproduced or transmitted in any form
by any means, electronic, mechanical or otherwise, without the prior
written permission of Ariba, Inc.

Ariba, Inc. assumes no responsibility or liability for any errors or

inaccuracies that may appear in the documentation. The information
contained in the documentation is subject to change without notice.

Ariba and Ariba products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of
Ariba, Inc. in the United States and other countries. Please see http://
www.ariba.com/legal/trademarks for additional trademark information
and notices.

Ariba Sourcing solutions (On Demand and software) are protected

by one or more of the following patents, including without limitation:
U.S. Patent Nos. 6,199,050; 6,216,114; 6,223,167; 6,230,146; 6,230,147;
6,285,989; 6,408,283; 6,499,018; 6,564,192; 6,871,191; 6,952,682;
7,010,511; 7,072,061; 7,130,815; 7,146,331; 7,152,043;7,225,152; 7,277,878;
7,249,085; 7,283,979; 7,283,980; 7,296,001; 7,346,574; 7,383,206;
7,395,238; 7,401,035; 7,407,035; 7,444,299; 7,483,852; 7,499,876;
7,536,362; 7,558,746; 7,558,752; 7,571,137; 7,599,878; 7,634,439;
7,657,461; 7,693,747; 8,364,577; and 8,392,317. Patents pending.

Other Ariba product solutions are protected by one or more of the

following patents:

U.S. Patent Nos. 6,199,050, 6,216,114, 6,223,167, 6,230,146, 6,230,147,

6,285,989, 6,408,283, 6,499,018, 6,564,192, 6,584,451, 6,606,603,
6,714,939, 6,871,191, 6,952,682, 7,010,511, 7,047,318, 7,072,061,
7,084,998; 7,117,165; 7,225,145; 7,324,936; 7,536,362; 8,364,577; and
8,392,317. Patents pending.

Certain Ariba products may include third party software or other

intellectual property licensed from a third party. For information
regarding software or other intellectual property licensed from a third
party, go to http://www.ariba.com/copyrights.cfm.

THE BEST RUN