How do I create Contract Line Item Document(CLID) from Import Legacy Contracts?

Use the Import Legacy Contracts task to bulk-create multiple legacy contract workspaces(CW). A legacy contract is one that existed in another system before your organization began using Ariba Contract Management Solutions.

To prepare for importing legacy contracts:

1. Create and publish a blank contract workspace template with no documents or default team members. This template will be used to generate each legacy contract workspace, as no default legacy template is provided.

2. Create a ZIP file containing four comma-separated values (CSV) files.

   
   
   • Contracts.csv
   • ContractDocuments.csv
   • ContractTeams.csv
   • ContractContentDocuments.csv
   • ImportProjectsParameters.csv
   • CLID.xlsx(CLID file)
     
     

   You can now include line items in legacy contract loads. You can include pricing terms Excel files in the .Zip file, which will be converted and loaded as line items documents in the Contract Workspace(CW).

   The ImportProjectsParameters.csv file for legacy contract loads should contain a ContractContentDocumentsFileLocation field between the TeamsFileLocation and RootParentId fields.
   
   

   The ContractContentDocuments.csv must contain the following fields:

   • Workspace: Specifies the contract workspace you are adding documents to. The type of identification for this field is specified by the WorkspaceLookupKey parameter in the ImportProjectsParameters.csv file. By default, the WorkspaceLookupKey parameter is set to ContractId, so each entry in the Workspace column must be a valid, unique ContractId.
   • File: Specifies the relative location of the pricing terms Excel document to be converted and loaded as a line items document. The location is relative to the root of the .ZIP file.
   • Title: Specifies the title for the line items document.

   
   Each CSV file contains a specific format that your site uses to create a contract workspace for each legacy contract. The attached ZIP file provides an example of a properly formatted import ZIP file with no contract documents.
   
   All configuration CSV files must appear at the top level of the archive ZIP file, and the only subdirectories within the ZIP file must include the documents referenced by the ContractDocuments.csv file.

Next, run the Import Legacy Contracts task:

1. Go to Project Manager > Import Legacy Contracts
2. Browse for the ZIP file that contains the legacy contracts.
3. Click Import. The Import Legacy Contracts Status page appears.
4. Click Refresh Status to see if the import completes successfully.

Note: You can also specify any other predefined fields for documents in the CW, including, but not limited to: Folder, Status, and Owner.

Along with the 4 CSV files used for Import Legacy Contracts, include ContractContentDocument.csv and PricingTerms.xls file in the .Zip file being uploaded.

A sample Zip file and documentation link is attached to this article for your reference.

Legacy Contract Import ZIP File Contents | SAP Help Portal

To create a pricing terms Excel document for the contents, you can use the information in Excel format for CLID to create an Excel document in the correct format. The document must include a Contract Item Information worksheet. You can omit the Contract Header and Header Attributes worksheets. If you do not need or want to specify terms specific to item master data, you can also omit the Item Attributes worksheet.

For information on Importing Legacy Contracts into CWs, refer to Contract Administration Guide.

Legacy Contract Import ZIP File Contents

How do I create Contract Line Item Document from Import Legacy Contracts?.zip

2.93 KB

Strategic Contracts > Contract Line Items Document (CLID)
Strategic Contracts > Strategic Contracts Import/Export