Please note: All discussions regarding shared master data elements are pa

Any shared master data discussions do not represent the sole topic of Data

Impacted Solutions

Suite Integrated Realms All Solutions

Commodity Codes All solutions

Commodity Code Mappings All solutions

Units of Measure Sourcing

Currency Conversion Rates All solutions

External Commodity Map All solutions

UserConsolidated All solutions

Custom Groups All solutions

Group All solutions

Group Child Group Map All solutions

User Group Mapping Consolidated All solutions

Suppliers All solutions

Supplier Contacts Strategic Sourcing Suite

Primary Supplier Manager Strategic Sourcing Suite

User Matrix Strategic Sourcing Suite

Display Mappings Strategic Sourcing Suite

Supplier Qualification Strategic Sourcing Suite

Preferred Supplier Level Strategic Sourcing Suite

Preferred Suppliers Strategic Sourcing Suite

Purchasing Organizations Strategic Sourcing Suite

Factories Strategic Sourcing Suite

ns regarding shared master data elements are part of a series of data strategy discussions.
scussions do not represent the sole topic of Data Strategy and it should be understood that additional discussions will be conducted to focu

Suggested Path if How to update it (if not

Permission needed
Automated automated)

N/A N/A N/A

Customer Administrator
Customer Users with appropriate
Ariba or
permission
Commodity Code Manager

Customer Administrator
Customer Users with appropriate
ERP > Procurement or
permission
Commodity Code Manager

Customer Users with appropriate

ERP > Procurement Customer Administrator
permission

ERP (tie to existing Customer Administrator

Customer Users with appropriate
update process where or
permission
possible) > Procurement Currency Manager

Customer Users with appropriate

ERP > Procurement Customer Administrator
permission
 Customer Users with appropriate
ERP > Procurement Customer Administrator
permission

Customer Users with appropriate

ERP > Procurement Customer Administrator
permission

Customer Users with appropriate

ERP > Procurement Customer Administrator
permission

Customer Users with appropriate

ERP > Procurement Customer Administrator
permission

Customer Users with appropriate

ERP > Procurement Customer Administrator
permission

Customer Users with appropriate

ERP > Procurement Customer Administrator
permission

Customer Users with Customer Users with appropriate

Customer Administrator
appropriate permission permission

Customer Users with appropriate

ERP > SLP Customer Administrator
permission
 Customer Users with appropriate
ERP > SLP Customer Administrator
permission

Customer Users with appropriate

ERP > SLP Customer Administrator
permission

Customer Users with appropriate

ERP > SLP Customer Administrator
permission

Customer Users with appropriate

ERP > SLP Customer Administrator
permission

Customer Users with appropriate

ERP > SLP Customer Administrator
permission

Customer Users with appropriate

ERP > SLP Customer Administrator
permission

Customer Users with appropriate

ERP > SLP Customer Administrator
permission
will be conducted to focus on the specific Data Requirements unique to the specific solutions in scope.

Where to load it Manually

N/A

Manage > Core Administration > Data

Import/Export > Import Commodity
Codes

Manage > Core Administration > Data

Import/Export > Import Commodity
Codes

Manage > Administration > Data

Import/Export > Import Units of
Measure

Manage > Core Administration > Data

Import/Export > Import Currency
Conversion Rates

Manage > Core Administration >Data

Import/Export > Import External
Organization Commodity Codes
 Manage > Core Administration >Data
Import/Export > Import User Data
(Consolidated file)

Manage > Core Administration >Data

Import/Export > Import Custom Groups

Manage > Core Administration >Data

Import/Export > Import Group To Child
Group Mapping

Manage > Core Administration >Data

Import/Export > Import Group To Child
Group Mapping

Manage >Core Administration >Data

Import/Export > ImportUser to Group
Mapping Data (Consolidated File)

Manage > SM Administration > Data

Import or Export > File Type: Suppliers
> Import Supplier.csv

Manage > SM Administration > Data

Import or Export > File Type: Supplier
Contacts > Import SupplierContacts.csv

Manage > SM Administration > Data

Import or Export > File Type: Primary
Supplier Manager > Import
PrimarySupplierManager.csv
 Manage > SM Administration > Data
Import or Export > File Type: User
Matrix > Import UserMatrix.csv

Manage > SM Administration > Data

Import or Export > File Type: Custom
Display Names > Import
DisplayMappings.csv

Manage > SM Administration > Data

Import or Export > File Type: Supplier
Qualification Data > Import
SupplierQualifications.csv

Manage > Administration > Data

Import/Export > Import Preferred
Supplier Level

Manage > SM Administration > Data

Import or Export > File Type: Preferred
Supplier list Data > Import
PreferredSupplier.csv

Manage > SM Administration > Data

Import or Export > File Type: Supplier
Purchasing Organization Data > Import
SupplierPurchasingOrg.csv

Manage > SM Administration > Data

Import or Export > File Type: Supplier
Factory Data > Import
SupplierFactory.csv
ements unique to the specific solutions in scope.

Data Descriptions

This is for reference only and describes in detail how data is shared across solutions in a suite integrated environment.

You can classify your projects, lots, items, and suppliers into a commodity code. We have already loaded the full UNSPSC V9.
Ariba On-Demand site. You can use this list as it is, make changes, or delete the list and create your own (custom) classificatio
UNSPSC codes and example of custom commodity tree.

If you create your own custom commodity tree, you will have to map your custom codes to a code in the UNSPSC classificatio
UNSPSC commodity tree available in your Ariba On-Demand site to find codes that correspond to your custom list.

While creating your items and lots, you will need to assign each of them a Unit of Measure. The list on this determines the val
in the UOM field. We have an extensive list of Units of Measure prepared for you on this . Please review the information and c
anything that doesn't apply to your business or adding anything that might be missing. You are also welcome to use the entire

Within report settings, you will choose a base currency for your site. In order to run projects in any currency other than that ba
currency conversion rate mapping from the specified currency to the base currency of your site (both ways).

For example: The base currency of your site is the European Euro (EUR). In order to run a project in Singapore Dollar (SGD)
currency conversion rate mapping from SGD to EUR and from EUR to SGD.

If you do not load a conversion rate mapping for a specific currency, your buyers will receive an error message if they choose a
project.

This is an OPTIONAL load. Use this to map your suppliers and customers against the commodity code structure. This enables
on commodities they supply. You can find more details about required information by hovering over the column headings.
Through this action, common user profiles are created which will exist both in SIPM/Contracts/Sourcing and P2X.

Groups that are specific for a business will be created. You can maintain the naming convention your organization is used to. T
mapped with Ariba standard roles to grant users various permission to use the tool.

Use the Group sheet to add all customer and standard group IDs that will be needed for the mapping. This file will be requeste
Group

Through this file, custom groups will be mapped to Ariba standard system groups. Without this mapping, the custom group wo
users would not be able to take any action (if assign no other permissions at all).

Users will be mapped to groups (either custom or standard system). Without assigning users permissions, they will not be able
system.

This is a REQUIRED load. Use this to import your suppliers from outside SAP Ariba.

This is a REQUIRED load. Use this to import your supplier contacts (supplier users). To specify multiple contacts for the same
contact.

This is a REQUIRED load. Use this to specify a primary and optional alternate contact within your company who either interfac
questions about it. Primary and alternate supplier managers do not have any role in supplier projects; they are for information
registration invitations, in which case they are required.
This is a REQUIRED load. Use this to specify user assignments for categories and regions.
Example: You can assign John Smith to Computer Equipment in North America as a project owner. He is a member of the Cat
supplier registration questionnaire template adds the Category Manager to the approval flow. When a supplier submits a regist
they supply computer equipment in North America, John Smith automatically becomes an approver for that questionnaire.
You may assign only one approver to each category/region combination.

This is an OPTIONAL load. Use this to specify custom display names for registration and qualification statuses.

This is an OPTIONAL load. Use this to designate supplier qualification status for suppliers that were created outside of SAP Ar
Performance. To specify the same supplier as qualified in multiple categories or regions, add a unique row for each combinatio

This is a REQUIRED load if you plan to designate preferred suppliers for specific categories or regions. Use this to define the
which your organization prefers one supplier over another. Examples of preferred supplier levels include number ranges (such
Medium, Low).

This is an OPTIONAL load. Use this to designate preferred suppliers that were created outside of SAP Ariba Supplier Lifecycle
specify the same supplier as preferred for multiple categories, add a unique row for each combination of category and supplier

This is an OPTIONAL load and is typically used if integration with SAP Ariba Procurement or ERP is involved. Use this to defin
associated with your suppliers.

This is an OPTIONAL load and is used with Direct Material Sourcing. Use this to define the factory data associated with your s
Suite Integration connects SAP Ariba Procurement a
environment.
Benefits:
Single log-in location for individuals who are users of both systems
Simplified Master Data management
Unified view of all relevant content, aggregated across Ariba applications
Truly seamless cross-application workflows (e.g. Contracts visibility, Reporting)

When deploying also an SAP Ariba Procurement solu

following master data will be synchronized:
Currency Conversion Rates

Locale

Commodity codes
The same domains have to be used
The selected values will be used in all transactions
If UNSPSC Commodity Code structure is not used, all Custom Commodities must be mapped back to UN

Units of Measure (UoM)

It is highly recommended for customers to use the default list of UoM available in Ariba (to enable transac
Carefully review the list of UoM and select the values which are relevant for the business

Common Users & Common Suppliers

all users and suppliers have a common part that will be shared but for P2X, also their partitioned data nee
for more more details please see below

User and Supplier Management

Enterprise Users are always loaded through Core Administration and their common part will be synchron
partitioned data.

In Suite Integrated sites, Groups are always synchronized and licenses may be required for certain action
Certain Groups grant permissions both to P2X and Sourcing/SIPM/Contract Mgmt and these cannot be se
Contract Administrator
Contract Agent
Contract Manager
Customer Administrator
CustomerDashboardAdmin
CustomerUserAdmin
Procurement Agent
Senior Analyst
Supplier Manager

Supplier Organizations
"Common supplier" data are always synchronized; "partitioned supplier" data (e.g. location, remittance de
new Sourcing/SIPM/Contract suppliers will be needed for transactions
Suppliers created via the Sourcing process will have an auto-generated ID and the ACM prefix.
Suppliers created in Downstream through the UI have the Buyer_ prefix and auto-generated ID.
Procurement Agent
Senior Analyst
Supplier Manager

Supplier Organizations
"Common supplier" data are always synchronized; "partitioned supplier" data (e.g. location, remittance de
new Sourcing/SIPM/Contract suppliers will be needed for transactions
Suppliers created via the Sourcing process will have an auto-generated ID and the ACM prefix.
Suppliers created in Downstream through the UI have the Buyer_ prefix and auto-generated ID.
ocurement and Sourcing/SIPM/Contracts into 1

rement solution, please bear in mind that the

ed:

be mapped back to UNSPSC to facilitate transactional supplier workflow

riba (to enable transactions with Network suppliers)

siness

eir partitioned data need to be added

n part will be synchronized. Additional information specific to P2X (Ship to address, accounting) is called

quired for certain actions.

and these cannot be segregated:

ocation, remittance details) are not synchronized - these data will have to be loaded additionally in case the

ACM prefix.
enerated ID.
ocation, remittance details) are not synchronized - these data will have to be loaded additionally in case the

ACM prefix.
enerated ID.
Master Data Planning Questions: After reviewing master data requirements at a high

If you maintain similar master data today, can you describe the process?
Where possible, we should leverage existing processes to ensure compliance and avoid duplicate data maintenance efforts.

Do you have members of the project team that have access to similar master data?
We want to be sure we have the right people on the project team to avoid delays around access.

Knowing the data is shared, do all to-be Ariba users utilize the same set of master data?
We will need to have a single list for all master data elements that will work for all teams using Ariba. It is never too early to sta

Have you identified who will own and/or support master data maintenance going forward?
Client administrators will be responsible for data maintenance after the deployment concludes. Administrators should be a part
uirements at a high level, please complete the following quesitons.

data maintenance efforts.

. It is never too early to start internal discussions on this topic.

ministrators should be a part of the project from day 1 with proper understanding of their role.
It is important to understand what permissions can be assigned to a user w

In your Sourcing dashborad, click on Help > Help Center > Learning

The relevant documents you will want to check are the 'Strategic sourcing and s
e assigned to a user within Ariba for him to view/edit/create and also which permission co

> Learning

trategic sourcing and supplier management group description table' and the 'Group licensing refe
which permission consume a user license.

e 'Group licensing reference':