Managing Contract Templates Documents

The Main Agreement is the primary contract document used in SAP Ariba Contracts and is a type of assembled document. Within a contract workspace template, administrators define the Main Agreement as the structured document that will serve as the working agreement in all projects created from that template.

The Main Agreement is created as a Microsoft Word document containing the contract text and is organized into structured components called sections and clauses. Sections group related contract content, while clauses represent individual contractual provisions made up of one or more paragraphs treated as a single reusable unit.

When configuring a template, administrators prepare the Word document to support assembly. Paragraph styles in Microsoft Word are mapped to section titles and clause content within SAP Ariba Contracts. This style mapping ensures that sections and clauses are recognized correctly and maintains consistent formatting across generated agreements, supporting organizational standards and compliance.

After preparation, the Main Agreement is uploaded to SAP Ariba Contracts and included in the template. When a new contract workspace is created from that template, a copy of the Main Agreement becomes the working document for that contract. The Outline View displays the document structure, allowing authorized users to view and manage sections and clauses during the authoring process.

Although assembled documents are optional, configuring a Main Agreement as an assembled document enables advanced contract authoring capabilities and promotes reuse of approved legal language. To use these capabilities, Enhanced Contract Authoring or Desktop File Sync must be enabled. Enhanced Contract Authoring is the recommended approach and replaces the legacy Desktop File Sync method.

Styles are created and applied in Microsoft Word to prepare a Main Agreement for use as an assembled document in SAP Ariba Contracts. The document must be saved in Microsoft Word (.docx) format before it is uploaded to the contract workspace template.

When configuring a template, administrators ensure that paragraph styles are applied consistently to section titles and clause content. SAP Ariba Contracts uses these styles to recognize document structure during upload and to correctly identify sections and clauses in the Outline View.

Authors may use standard Word styles or create custom styles to meet organizational standards. Proper style configuration is critical because it determines how the system interprets the document structure and supports clause reuse and contract authoring functionality.

Use consistent paragraph styles for section headings and clause text to ensure proper structure recognition after upload.

Before uploading a Main Agreement to SAP Ariba Contracts, paragraph styles must be configured with the correct outline levels in Microsoft Word.

The outline level assigned to each style determines how SAP Ariba interprets the document hierarchy during assembly. For example, styles assigned higher outline levels are recognized as section headings, while lower levels are interpreted as clause content.

By modifying a style’s paragraph settings, administrators define the document structure that will appear in the Outline View after upload. Correct outline configuration ensures that sections and clauses are properly organized and nested within the contract workspace.

Without properly assigned outline levels, SAP Ariba may not recognize the intended structure of the document, which can impact clause management and authoring functionality.

After preparing and formatting the Main Agreement in Microsoft Word, the document is uploaded to the contract workspace template in SAP Ariba Contracts.

From the Documents area of the template, administrators create a new Main Agreement and upload the prepared Word (.docx) file. During upload, SAP Ariba processes the file as an assembled document and interprets its structure based on the defined styles and outline levels.

The uploaded file becomes a managed document within the template. When a new contract workspace is created from the template, the Main Agreement is automatically included and serves as the working agreement for that contract.

Once processed, SAP Ariba recognizes the document structure and displays the content as sections and clauses in the Outline View, where it can be reviewed and managed during the authoring process.

A Contract Line Items Document (CLID) is a structured document used in procurement contract workspace templates to define the specific goods or services covered by a contract. Each line item represents an individual product or service and includes structured terms such as quantity, price, and other commercial data.

Unlike the Main Agreement, which contains narrative contract language, a CLID captures pricing and item details in a structured, item-based format. This structure supports reporting, compliance tracking, and integration with external systems.

When configuring a contract workspace template, administrators determine whether a CLID is included. CLIDs are available only in procurement contract workspace types and must be enabled at the site level. They are not available with basic SAP Ariba Contracts subscriptions.

A Contract Line Items Document (CLID) can be configured as either a standard-capacity or large-capacity document when added to a contract workspace template. Administrators select the capacity type based on the expected number of line items and contract complexity.

SAP Ariba recommends limiting each line item to a maximum of 50 terms to maintain system performance and usability.

Contract Line Items Documents (CLIDs) enable structured integration across SAP Ariba solutions and external systems.

When included in a contract workspace template:

• Line items from SAP Ariba Sourcing award events can be automatically transferred into the contract workspace when the workspace is created from an award.
• CLID line items can be used to create follow-on sourcing projects, supporting reuse of contract content.

When an External System is configured for integration, such as SAP ERP, published line items from the CLID can be sent to the ERP system to create a corresponding SAP contract (outline agreement). In this integration scenario, there is a one-to-one relationship between a contract workspace and its associated CLID and a single ERP contract.

CLIDs also support document-based tasks such as review, approval, and negotiation. When shared with external reviewers, line items are provided in Microsoft Excel format to allow structured review and comparison.

If your SAP Ariba Contracts solution is integrated with SAP Ariba Procurement solutions, you can create a Contract Terms link document to work with compliance contract requests (and compliance contracts).

Administrators create a contract workspace template containing a Contract Terms document to be used for business use cases where both contract management in SAP Ariba Contracts and operational contracting activities are required.

If you do not want to push pricing terms or other contract data from a contract workspace to a compliance contract request, you do not need to use Contract Terms link documents.

A Contract Terms link document is located in the Documents area of a workspace, however, it is not a document that users can edit or view. Instead of editing or viewing a contract terms link, they:

• Create a Contract Terms link ad-hoc, which creates an associated compliance contract request in the SAP Ariba Buying and Invoicing solution.
• Open a Contract Terms link, which transfers them to the associated compliance contract request (or compliance contract).

• Structured Word documents, like the Main Agreement uploaded to templates serve as working contracts, with sections and clauses recognized by outline levels.
• Consistent paragraph styles and outline levels ensure correct document structure and support clause reuse and advanced authoring capabilities.
• Structured documents, like the Contract Line Items Document capture line item details for pricing, integration, reporting, and support procurement-specific use cases in SAP Ariba Contracts.
• CLIDs facilitate data transfers between SAP Ariba and external systems, enabling seamless contract creation and operational workflows.
• The Contract Terms Document links compliance contracts with SAP Ariba Procurement solutions for managing contract data and operational contracting activities.