Name: Working with Approval Tasks in SAP Ariba Contracts
Uploaded: 2024-12-9
Duration: 176 s
Description: See how approval tasks can be created in a contract workspace for documents and the entire workspace in SAP Ariba.

Share feedback

<p><u><strong>Planned maintenance of Practice Systems</strong></u></p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div>See how approval tasks can be created in a contract workspace for documents and the entire workspace in SAP Ariba. </div></div></div></div>

Working with Approval Tasks in SAP Ariba Contracts

In this video, we will first create a simple approval task within a contract workspace project and take a look at the types of approval flows. Then we will look into creating an approval task for the entire contract workspace. We are going to learn how a contract manager can create an ad hoc approval task and add users and groups into an approval flow. In order to see the approval option whenever creating a task, a document or a folder must be selected. Meaning, you will not see it under the Actions menu on the Tasks tab. When a new Approval Task is created within the project, there is an approvers drop-down menu which is a search for users, system groups and project groups. The multi-select search will allow you to choose multiple or one approver to the flow. You can see the type column is helpful to indicate if it is a Project Group which is a group in the team tab, or if it is a system group which is just labeled Group. When we choose multiple approvers, the system creates a graph which we can then select the links in order to edit the flow. We can select the X to take out a group if they were added by mistake, we can add a new group, or we can change the position of the approver if we want to edit the flow. If the graph is set to Parallel, that means that both approvers will need to approve before moving on to the next approver. Custom would be a combination of serial and parallel. A Serial flow is one after the other. Marking the task as required means it can't be canceled by the end users. Also, using the predecessor option, we can set up the sequence in which tasks and phases will be starting in the contract timeline. Once we're happy with the task set up, we can submit the task. An approval task can also be created for the entire contract workspace. This is a common occurrence for contracts with a high value, a strategic commodity or supplier. To create such an approval task, we navigate to the contract overview, then choose Actions and View details. Here on the task area, we can add an Approval Task for the entire workspace. Keep in mind that if an approval is put in place for the entire workspace, The contract can't be published until everyone in the approval flow has approved. Now, approvals are not typically created manually within the project by the end user. Rather, administrators set these at the template level so that company practices can be applied to SAP Ariba projects across the site. If needed, project owners can add additional approvers or reviewers, but they cannot remove anything that is set from the template. This concludes our demo on working with approval tasks in a contract workspace. Thank you for watching.