This document describes the file formats for exporting contract header and terms data from Ariba Contract Management. The contract header file format exports data to a CSV file with columns for attributes like contract ID, title, status, and parties. The contract terms export file format contains similar identifying information as well as contractual details like effective dates, amounts, and types. Notes provide additional context about data types and locales.
This document describes the file formats for exporting contract header and terms data from Ariba Contract Management. The contract header file format exports data to a CSV file with columns for attributes like contract ID, title, status, and parties. The contract terms export file format contains similar identifying information as well as contractual details like effective dates, amounts, and types. Notes provide additional context about data types and locales.
This document describes the file formats for exporting contract header and terms data from Ariba Contract Management. The contract header file format exports data to a CSV file with columns for attributes like contract ID, title, status, and parties. The contract terms export file format contains similar identifying information as well as contractual details like effective dates, amounts, and types. Notes provide additional context about data types and locales.
This document describes the file formats for exporting contract header and terms data from Ariba Contract Management. The contract header file format exports data to a CSV file with columns for attributes like contract ID, title, status, and parties. The contract terms export file format contains similar identifying information as well as contractual details like effective dates, amounts, and types. Notes provide additional context about data types and locales.
• “Contract Header File Format” on page 125 • “Contract Terms Export File Format” on page 126
Contract Header File Format
Ariba Contract Management exports contract header data to CSV files, which consist of rows of data. The first row is the character encoding. For exported files, the character encoding is always set to UTF-8.
The second row is the header row, which lists the column headings. If you have defined custom header fields (flex fields), and you want them exported, verify with your Ariba representative that they are flagged for export on the Advanced tab of the Field Configurator. Any custom fields are added in columns to the end of the export file as String types and are labeled cus_xxx, where xxx is the user interface field label. For example, if a custom field Current Status was added to the Contract Workspace page, then the exported column is labeled cus_CurrentStatus.
The subsequent rows contain the exported data. Each row contains data for one contract, indexed by the Contract Workspace ID.
Notes: • The data in exported CSV files is always in en_US locale format, regardless of user and site default locale settings. • Numerical values in exported CSV files do not include the comma (",") separator.
The following table provides a description of the columns in the contract header CSV data export files:
Column Description Contract ID A unique identifier string for the contract. Last Published The number of the most recently published version of the project. Title The title of the contract. Description The user-specified contract description. Version The most recent contract version. Access Control A list of access controls applied to the contract, delimited by brackets ([ ]). Contract Status The status of the contract: Not Created, Draft, Published, Pending, On Hold, Expired, Closed, Draft Amendment. Owner The user or group who owns this document. Time Updated The last updated time of the contract. Last Modified By The last user who modified the contract.
Ariba Integration Guide for Sourcing, Contract Management, and Supplier Management 125 Contract Terms Export File Format Appendix B Contract Data File Formats
Column Description Test Project Indicates if the contract is a test project (or request). Predecessor The predecessor contract ID. Hierarchical Type Indicates how the contract relates hierarchically to other contracts: as a standalone Agreement, Master Agreement or Sub Agreement. Parent Agreement This depends on the Hierarchical type. If the Hierarchical type is Sub Agreement, then this is applicable to choose the parent or master agreement. This option is not applicable if the Hierarchical type is Standalone or Master agreement. Supplier Name The full name of the contract supplier. Affected Parties A list of names of affected parties, delimited by brackets ([ ]). Affected Parties A list of IDs of affected parties, delimited by brackets ([ ]). Each ID contains a IDs series of domain and value pairs enclosed in parentheses, where the domain and value are separated by a colon (domain:value). For example, [(duns:110011811)(buyersystemid:sid803)(internalsystemid:20003)].
Supplier ID The ID of the contract supplier.
Amount_ Currency The currency specified in the event, when it is different from the project currency. The values in this column are standard ISO currency codes, such as USD or EUO. Amount_Amount The contract's total monetary amount. Contract Type The type of contract chosen. It can be Fixed, Perpetual or Auto-Renew. Effective Date The date when the terms of the contract go into effect. Agreement Date The date when the parties agreed to the contract. Expiration Date The date when the contract will expire and its terms will no longer be in effect, if it is not renewed. InternalId Internal Id of the user. RelatedId This is an optional field. AmendmentReason Reasons entered at the time of choosing the type of Amendment. (Administrative, Renewal, Termination, or Amendment) AmendmentReason Comments entered at the time of creating an Amendment. Comment
IsContractRequest Indicates a contract workspace is required or not.
CreateDate The creation date for the event's contract project. Dates are in the format EEE, d MMM, yyyy. For example, Wed, 18 Feb, 2009. BaseLanguage Base language of the contract.
Contract Terms Export File Format
For information about exported contract terms files, see the Ariba Managing Contract Compliance guide for your procurement or invoicing solution.
126 Ariba Integration Guide for Sourcing, Contract Management, and Supplier Management
