 |
| ||||||||
When signing into Ariba, the user receives the authentication error message, User is not defined in any partition.
The user does not have a Partitioned User.
This can be resolved by loading the Partitioned User into Ariba through the Import Users task in Ariba (User.csv file) or the Import User Data (Consolidated File) (UserConsolidated.csv).
To load the Partitioned User:
- Sign in to Ariba.
- Click Manage > Core Administration.
- Click Site Manager > Data Import/Export.
- Click the Import tab.
- Search for the Import Users task or the Import User Data (Consolidated File) task.
- Click Import for the desired task.
- Browse and select the updated files which include the specific users:
Import Users: User.csv and the PCardMap.csv
Import User Data (Consolidated File): UserConsolidated.csv - Select the Create or Load option when prompted.
- Click the Run button.
Once the task completes, the Partitioned User will be created/activated and the user will have access to log in to Ariba procurement applications.
If the Import User Data (Consolidated File) was uploaded and it did not resolve the issue, then try with Import Users. Specific error messages may not appear in the user interface as a result of the consolidated task being a collective one; however, Import Users is the standalone partition user data task and will display errors when the consolidated will not.
- In Ariba procurement applications, a Partitioned User is required. This is different from the Shared User or Enterprise User.
- The Enterprise User provides the user access to the application for sourcing applications and is needed for procurement users as well. However, the Partitioned User is an additional requirement for procurement users.
- In an FPC configuration, only the Enterprise User (Shared User) gets replicated from parent realm to child realm. The Partitioned User (Import Users User.csv) should be uploaded directly to the child realm as needed.
Core Procurement > Core Administration > Core Administration User Management