The next-gen Authorization Management Service (NAMS) for procurement allows customer administrators to manage user group authorization with a hierarchy for next-gen SAP Ariba applications and shared services.
The User Management Lifecycle
Understanding how user records flow through the system is essential for diagnosing access issues. The lifecycle runs in four stages
- Stage 1 — SCI
- Users are created in SAP Cloud Identity Services. This is the only place where user creation and deactivation happens. You cannot create or deactivate users directly in the SAP Ariba Administration Center..
- Stage 2 — CDM Replication
- SCI replicates the user record to Core Data Management (CDM). CDM receives the basic identity data: name, e-mail, and user ID..
- Stage 3 — CDM Enrichment
- CDM enriches the user record with procurement-specific attributes — including application access configuration, spending limits, and role context relevant to procurement processes.
- Stage 4 — NAMS
- The enriched user record flows to the Authorization Management Service, where group hierarchies and multi-application associations are managed. Custom groups created here are replicated back to SCI, so they are available for user assignment.
If a user exists in SCI but cannot access certain features in next-gen SAP Ariba, the issue is almost always in one of the three downstream stages: CDM replication has not completed, the user has not been assigned to the correct group in NAMS, or the NAMS-to-SCI group replication has not run yet.
Core Data Management Access Roles
Two roles control access to Core Data Management entities. These roles are separate from procurement application roles and are assigned in SCI.
- Viewer
- Grants read-only access to CDM entities. Users with this role can view master data records but cannot upload or modify them. Assign this role to users who need to validate CDM data during implementation without risking changes.
- Manager
- Grants upload access to CDM entities. Users with this role can upload new records and update existing ones using the file upload feature in the Administration Center. Assign this role only to administrators responsible for master data loading during implementation.
Why NAMS?
The next-gen Authorization Management Service extends SAP Cloud Identity Services with capabilities critical for enterprise authorization management:
- Deeper group nesting: Supports group nesting beyond ten levels
- Multi-application associations: Custom groups can be associated with multiple applications and various base groups, expanding utility across different contexts
- Localization and translation: SCI supports English only; NAMS provides localized interfaces for customers requiring multi-language support
Note
This video provides the step-by-step SAP Cloud Identity Services job setup:
Assigning User Groups to Users in SAP Cloud Identity Services
- Sign in to the Administration Console of SAP Cloud Identity Services.
- Navigate to Users and Authorizations→User Management.
- Select a user from the table.
- Choose the Groups tab in the right panel.
- Choose Assign.
- Select the groups you want to assign to the selected user.
- Choose Assign to confirm.
This video explains how to manage users and create user groups in next-gen SAP Ariba:
Why Custom Groups Must Be Created in NAMS, Not in SCI
SAP Cloud Identity Services supports standard group management but has two limitations that matter for procurement: group names are English-only, and groups cannot be associated with multiple applications. NAMS removes both limitations.
Any custom group that needs to appear across more than one next-gen SAP Ariba application — or that needs a name in a language other than English — must be created in NAMS first. It will then replicate to SCI automatically.
To create a custom group, follow these steps:
- Log in to the SAP Ariba Launchpad using your assigned credentials.
- On the left-hand navigation menu, choose Administration Center.
- Under the Authorization Management section, choose User Groups.
- Create a new custom group. Choose Create.
- Enter a Name, for example: Brazil – Nova Retail Group – Catalog Approver.
- Enter a Description, for example: Custom group for Nova Retail Group to establish catalog approvers for Brazil end users.
- Assign groups (optional). Under Assigned Groups, select one or more out-of-the-box groups to nest inside your new custom group.
- Choose Create. Use the search field to find and confirm your new group appears in the list.