Monique Dupont is a new employee, and part of her responsibilities will include working in SAP Ariba as a Sourcing Agent. She needs to be created as a new Enterprise User, and needs help from her administrators.
Jenny has been tasked with adding Monique as a user in the system. She consults Marco, to ensure she has all of the correct data.
User accounts provide individuals access to SAP Ariba products. Before creating a user, there are implications on the type of realm the user is being added to, and what user information will be required.
Suite Integrated or Not Suite Integrated?
- Suite integrated Realms
In suite integrated realms, both solutions share the same common user, linked by the common user ID. The common user object contains information such as name, email address, default currency and locale.
On the Procurement side, the user must also have a partitioned user. This object contains data such as shipping address and accounting information.
Groups will be synchronized.
- Non Suite integrated Realms
In non suite integrated realms, common users exist as two separate common users in each application.
On the Procurement side, the partitioned user data is still necessary.
Groups are not synchronized.
It is recommended for customers to have their user administrators agree on a uniformed process when adding and maintaining user data as early as possible.
If a customer is deploying SAP Ariba Procurement solutions in tandem with SAP Ariba Strategic Sourcing, it is recommended for both teams to work together on user creation and have a process in place for Strategic Sourcing group assignments.
