Describing the SAP Ariba Contracts Lifecycle

Objectives

After completing this lesson, you will be able to:
  • Describe contract workspaces.
  • Explain the role of contract workspace templates.
  • Explain the contract workspace lifecycle within the SAP Ariba Contracts application.

Contract Workspace Description and Overview

SAP Ariba Contracts is an application that offers customers tools for the management of contracts. It leverages workspace functionality and templates designed by administrators to ensure contract creators respect legal and business requirements.

A contract workspace (CW) is an SAP Ariba project that stores contracts online and includes information about the contract, contract documents, project team members, and tasks. Essentially, a contract workspace is a container for your agreements and the workflow behind them.

SAP Ariba Contracts supports the following contract workspace types:

  • Contract Workspace (Procurement) - used for contracts with a supplier
  • Contract Workspace (Sales) - used for contracts with a customer or buyer
  • Contract Workspace (Internal) - used for contracts within companies or organizations

In SAP Ariba, contract workspaces serve as containers for all aspects of contract lifecycle management, from drafting the written legal documents to engaging the right stakeholders. Different components inside a workspace facilitate the smooth management of a contract.

Workspace ComponentDefinition
OverviewContains information about the contract, including workspace ID, owner, status, version, commodity, regions, departments, term attributes, and other searchable and reportable data.
Contract AttributesAttributes such as supplier or customer name, contract value, and hierarchical type. These can be out-of-the-box or custom fields.
Contract Term AttributesAttributes such as term type, effective and expiration dates, and other terms that relate to the notification of the expiration date. You can search for contracts using the Contract Terms option in the Search menu.
DocumentsPlace to manage all contract-related documents, such as the main agreement, addenda, or contract terms. They are files that can be shared by users working together to create the contract. Documents can be linked to tasks and have version control to track the document's change history.
TasksMaps out an organization's standardized process for contract creation and provides auditable and repeatable processes that can be delegated to other team members and tracked through reporting.
TeamAllows users to assign others to specific roles that map to different tasks in the creation process, providing for efficient collaboration and letting multiple stakeholders (such as legal, tax, and risk management) participate in the process.
Message BoardA collection of messages for a workspace. Users can create messages, reply to messages, label messages for filtering, and message external recipients via e-mail through the message board.
HistoryA detailed record of changes to information in the workspace, such as the creation date and field changes.
View of a Contract Workspace (Procurement) in SAP Ariba, displaying each of the components discussed in this unit.

A contract workspace can be displayed in full view, as illustrated above, or in compact view. To change the project view, choose Actions in the Overview section, then select Full View or Compact View. The compact view turns the full view's tabs into sections, as illustrated below.

The compact view of a contract workspace, which has the components displayed in sections instead of tabs.

Contract Workspace Templates

As with any type of project in SAP Ariba (sourcing and contract requests, sourcing projects, sourcing events), contract workspaces are created from a template. Templates can contain documents and tasks that define standard business processes your company uses to buy and sell goods and services.

Templates can include questions and conditions that determine the documents, tasks, and phases created according to the project attributes. When used with conditions, questions are designed to make defining project conditions for a specific project more user-friendly. Answers are predefined responses to questions in templates. Answers can trigger conditions; whether an answer is visible is controlled by its visibility condition.

Templates are used to:

  • Standardize the creation of projects.
  • Model an organization’s contract lifecycle. They may have unique processes for different commodity categories or contract amounts.
  • Pre-populate projects with team members, documents, tasks, and other project items.

The templates that are available depend on the following:

  • Project information you have entered and the user groups you belong to.
  • Header field data that you enter when creating the contract workspace.

Contract Workspace Lifecycle

SAP Ariba Contracts allows you to manage the entire contract lifecycle in a centralized location. Here are the main steps:

Graph displaying the steps in the lifecycle of a contract workspace in SAP Ariba.
  1. Contract request: Initiates the contract process by creating and sending a request to a contract manager to create a contract workspace (CW). This step is typically performed by users who do not have system permissions to create a CW.

    Note

    Creating a contract request is optional for users with the appropriate system permissions for creating workspaces. They can bypass this step and create a CW from an awarded sourcing event or the SAP Ariba dashboard.
  2. Prepare a workspace and author a main agreement: In this step, a contract manager creates a contract workspace in SAP Ariba and begins drafting (also known as authoring) the main agreement and other contract documents in preparation for review and negotiation.
  3. Review and negotiate: In this step, contract documents go through an internal review process, then are sent out to other parties, such as the supplier or customer, for further redlines and negotiation.
  4. Approve and finalize: In this step, contract documents go through final approvals, and signatures are obtained. The workspace is then published, and the contract is executed.
  5. Amend and manage: Finally, a contract may be amended and further managed through dashboard tools, access controls, and reporting. Depending on the amendment type, new approvals might be required.

Log in to track your progress & complete quizzes