Contract workspaces enable the customer’s contract managers to execute a repeatable contract negotiation, execution, and amendment process. Contract workspaces introduce standardization to the process using project templates set up by administrators. Project templates enable the ability to effectively conduct contract management through the lifecycle.
Business Process Overview
The dashboard of SAP Ariba serves as a point of access for significant, actionable, and relevant user content based on role, such as contract activities. A user that initiates a contract workspace project has to select a project template, besides several project meta-data. This project template serves as a starting point for a project. Templates are usually pre-populated with documents, tasks, and team members.
In SAP Ariba Contracts, there are multiple ways to initiate the creation of a contract:
- Creating a contract request
- Copying an existing contract
- Creating a CW from scratch
- Starting from a sourcing event, for example an RFP, where you create a contract after the event has been awarded

Contract related data is collected through header fields on the following workspace areas:
- Overview - where information such as contract status, commodity, and owner name is collected
- Contract Attributes - where you must enter data such as the supplier name, contract amount, and type of contract (stand-alone, main or sub-agreement)
- Contract Term Attributes - containing contact specific data, for example effective and expiration dates, and whether it is a fixed term or perpetual contract
Commonly after the contract workspace is created, the team members of the contract workspace project are validated in order to guarantee that the correct stakeholders are included for collaboration and visibility purposes. Users can be added to the different project groups and then are assigned tasks per template design.



