An asterisk (*) indicates that data is from a different partition and is therefore read-only.

Shared users are nonpartitioned users that are shared by Ariba Spend Management applications. Buyer users are partitioned Ariba Buyer users associated with a single shared user. Ariba Buyer users include information specific to Ariba Buyer. You must create a shared user first, before you can create an associated Ariba Buyer user in a particular partition. Shared users only need to have associated Ariba Buyer users if they will be accessing Ariba Buyer. You can only create Ariba Buyer users in your login partition. For more information on shared users and Ariba Buyer users, see the Ariba Buyer Data Load Guide.

Access to create and edit Ariba Buyer users depends on the permissions assigned to you and whether you are in view or edit mode. If you do not have read or edit permission for a particular user, you may still see the user listed in search results and choosers. However, you cannot view details for that user. If you try to view or edit user details without the proper object-level permissions, an error message is displayed.

In the default configuration, the permissions required to access workspaces and tasks are defined in the workspace configuration files; and the access permissions required to view, create, copy, edit, delete, and export Ariba Buyer users are defined in the object manager configuration files. Permissions can be customized, including setting object-level read and edit permission. For more information, see the Ariba Buyer Administrator Customization Guide.

Display Ariba Buyer users. Initially, no users are listed.

• To display all Ariba Buyer users in the database, click List All.
• To display a specific set of Ariba Buyer users, enter search criteria and then click Search or press the Enter key. For example, enter all or part of a user name, or select a partition from the pull-down menu. You can enter one user name at a time. To search all partitions, select No Choice. Search fields are case-insensitive.
• To add or remove search filters, such as supervisor, directly assigned permission, or the name of the associated shared user, click Add/Remove Search Filters. Then select check boxes for the search filters you want to add, or deselect the ones you want to remove. The search filters labeled Permission and Role search on directly assigned permissions and roles only.
• If available, click the Table Options icon, located in the row above the column headers, to display commands that control the display of data in the table. For example, you can hide or show columns of data; group data; or export data to Excel.

View Ariba Buyer user details:

• To view details such as the roles, permissions, and PCards assigned to an Ariba Buyer user, click a user name or a supervisor. User details include information on the associated shared user, including assigned groups, roles, and permissions. When viewing user details, view additional information by clicking links for the Ship To address, default currency, and others.
• To sort search results by user name, partition, email address, or supervisor, click a column header. Click the header again to change the sort order, as indicated by the arrow.

Take other actions:

• To create a new Ariba Buyer user in the database, click Create New. The new user will be created in the same partition as your login partition.
• To create a new Ariba Buyer user in the database based on an existing user, click Copy for an existing user. You can only copy users in the same partition as your login partition. Only one Ariba Buyer user in each partition can be associated with particular shared user.
• To edit or delete one or more Ariba Buyer users in the database, click their check boxes and then click Edit or Delete, as necessary. You are asked to confirm your deletions. You can only edit or delete users in your login partition.
  • Editing Ariba Buyer users includes specifying general information and assigning PCards.
• To export Ariba Buyer users from the database to .csv files, click Export. Users are exported using predefined integration events which do not depend on your login partition or the search filters you specified.