Support for user qualification in contracts
SC-14642
This feature allows you to enable user qualification for contracts. User qualification provides enhanced access restrictions for projects and documents in addition to access control settings, by qualifying users based on contract project header field values. When user qualification is enabled for contracts, the user qualification field values of the current user are validated against the user qualification field values of the contract project. Qualified users are allowed to access the contract project and contract project data.
Currently, contract workspaces can be accessed by users belonging to certain groups, and by a few user driven parameters. This works well for most customers. However, for organizations with complex structures, there is a need to further enhance the access control for contracts and associated information.
With the enhanced user access control, organizations can set access restrictions for projects and documents, thereby providing better control over the contract project and contract project data.
Buyer
https://help.sap.com/docs/SAP_Ariba/978b7e36451a4c2c85321a3ef6f3a7e5/b4632fd131ee46bf9a6beca542e2181d.html?locale=en-US&state=PRODUCTION&version=cloud
Customer Configured
Feature ID: SC-14642
SAP Ariba Sourcing
SAP Ariba Contracts
SAP Ariba Strategic Sourcing Suite
You must enable the following parameters in Manage / Administration / Intelligent Configuration Manager:
- Application.ACM.EnableUserQualification. See Enable user qualification.
- Application.ACM.EnableUserQualificationInContracts. See Enable user qualification in contracts.
Specify user qualification fields and map these fields to contract project header fields in SAP Ariba Contracts. See How to obtain information required for running the Import User Qualification Fields and Import User Qualification Field Mappings tasks and How to specify user qualification fields and map these fields to sourcing project header fields.
You must have a User Qualification API application that sends user qualification field values to SAP Ariba. See How to develop an application to create or change user qualification values and How to check user qualification field values of users.
SAP Ariba checks user qualifications only when both users and sourcing projects have user qualification field values specified. Users without user qualification field values are subject only to the normal access control settings for projects.
User qualification validation does not occur for some of the use cases.
| Scenario | Restrictions |
|---|
| Creating a contract project |
-
User qualification validation does not occur for:
-
Custom fields, users, team members, tasks, documents copied from a template, selected contract workspace, predecessor project, parent agreement, or sourcing project
-
Contract projects created through a webservice
-
User qualification field values of a predecessor project will not be copied to the current project
-
User qualification field values of a parent agreement will not be copied to the current project (subagreement)
-
User qualification field values of a sourcing project will not be copied to the current project (new contract or selected contract)
|
| Editing, amending, publishing, putting on hold, resuming, and closing a contract project |
User qualification validation does not occur for custom fields, users, team members, tasks, documents on edit overview action or edit attributes action.
|
| Adding and editing contract documents | User qualification validation does not occur for:
-
Any reports added to the contract workspace
-
Parallel user scenario are not supported. For example, if two users log in to a site at the same time, one of the user edits and saves the changes, then as long as user is on the project or task page, revalidation does not occur. Once the user navigates out of the project or task page, then the validation occurs.
|
| Adding and editing tasks in contracts |
-
User qualification validation does not occur for a user approving or denying an approval task from an email notification. Unqualified users are allowed to approve or deny the approval task over email.
-
Created tasks will remain in the In Approval or In Review state if the user qualification field values of the contract project are updated and if the user qualification validation is not successful. No error messages will be displayed. Project owner can manually iterate the tasks and retrigger or edit them.
-
User qualification validation does not occur for To Do tasks marked as started or completed directly from the Actions menu directly.
-
The Owner, Original Owner, Reviewer, Observer, Approver, or Signer fields filters the users based on the user qualification field values of the workspace. Filtering will not be done for Project Groups, Groups, Business Contacts and Business Contact Groups, even if unqualified users are included.
|
| Adding users to Teams | User qualification validation does not occur for the groups added in project group of a contract project. |
| Searching for contract types and contract document types | User qualification validation does not occur for:
-
Clause library and contract clause
-
When you search for a contract project, the owner field will not be filtered based on the current user’s user qualification field values.
|
| Delegating responsibilities to another user |
Delegatee to Delegator user filtering is not in scope. If a Delegatee is added first, and then if you search for a Delegator, it's values are not filtered based on the selected Delegatee user qualification field values.
|
Strategic Contracts 2202
Strategic Sourcing 2202
