Name: Reviewing Task Types in SAP Ariba Guided Sourcing Full Projects
Uploaded: 2024-12-4
Duration: 233 s
Description: See which task types are available within SAP Ariba full projects in guided sourcing. Find out how tasks can be executed and completed by their task owners. All task types that a project owner can create within a full project will be covered in this video including To Do, Approval, Review, Notification, and how documents can be associated.

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><div>See which task types are available within SAP Ariba full projects in guided sourcing.  Find out how tasks can be executed and completed by their task owners.  All task types that a project owner can create within a full project will be covered in this video including To Do, Approval, Review, Notification, and how documents can be associated.</div></div></div></div></div>

Reviewing Task Types in SAP Ariba Guided Sourcing Full Projects

This video will demonstrate common task types within an SAP Ariba-guided sourcing full project and how to take action from a task owner's perspective. Tasks can either be steps that are taken offline and tracked like a to-do list, or they can be more involved and require online document completion. Tasks are actions that need to be done by a particular person at a specific time. In most cases, you will see various to-do tasks within a full sourcing project, including lists of activities outside the system and incorporating events and other supporting documents. Let's create a new guided sourcing full project. We see that the project creator is automatically identified as the owner, which automatically assigns them to the project owner group, who is responsible for many of the tasks and documents within the project. After the full project is drafted, the Tasks panel displays a table of activities detailing the workflow, consisting of the task and phase names, descriptions, types, status, owners, due dates, approvers or reviewers, documents, and actions. The project owner is responsible for completing most of the tasks in our example. Tasks can be grouped into phases, which appear in both the Tasks panel and the Process panel. The Process panel in Guided Sourcing Full Projects includes a color-coded snapshot of the phase's progression. Project owners view the tasks within each section and identify the owners who will take the necessary action. Tasks with red asterisks are required tasks that must be completed before the project's end. The necessary action depends on the type of task and whether a document that requires attention is associated with it. In our first task, we are instructed to check the default team, as indicated by the to-do task description. To-do tasks without associated documents often include instructions in their descriptions to perform activities online or outside of the tool, and they are set to started or set to complete to keep track of progress. The next task is a to-do task associated with a non-SAP Ariba formatted file. Non-executable files can be downloaded by selecting the file name. They must then be edited and re-uploaded to the project before the task can be marked as complete. The data on these files is unavailable in analytical reports, as they are not SAP Ariba formatted documents. SAP Ariba formatted documents, like forms, savings forms, content documents, and events, can also be associated with to-do tasks. Traditionally, the full sourcing project templates contain a placeholder for the event with an associated required to-do task. The project owner must complete the required fields or proceed to create the event. The project owner must select the event type and template and choose Create. The project owner will then proceed to run the event by adding content, rules, and participants. When a document is associated with a task, the task type can be review, approval, notification, or to-do. Review tasks ask other system users to edit or comment on a project document. Approval types are used to request a document's actual approval or denial. They are traditionally inherited from the template selected to create the project instead of being created manually. Notification types send one time or repeating email reminders. For additional information on tasks within full sourcing projects, please consult our help menus and product documentation.