How do I import contract data?

How You Map Your Source Data to Object Attributes

To import your Contract data into Oracle Applications Cloud, you must populate a .csv file with your source data and map that source data to target object attributes in Oracle Applications Cloud.

You need to do the following before creating the CSV file for data import:

Identify how your source data attributes map to the target object attributes in Oracle Applications Cloud.
Ensure prerequisite setups are done, if applicable.
Understand your options for uniquely identifying the records.
Ensure parent records exist before importing child records.
Identify the target object attributes that are required in the CSV file for a successful import.

Before You Start

You must do some basic checks before starting your import. For example:

Complete all the prerequisites for importing each attribute in your source data.
Have all parent records in place before importing child records.

Select a Unique Identifier for Your Records

All records must be unique in the application.

Public unique identifiers: If you're creating records, then you can provide an easily understandable public unique identifier. These are, usually, denoted with 'Number' and visible in the business object's UI. PUID attributes are usually named <object> Number. If you're updating a record with a Number attribute, then use the Number attribute to identify the record. For more information about public unique identifiers, see the topic "How You Use Alternate Keys to Import Records" in Related Topics section.

Note: You can't update or customize a PUID. You can provide a unique value. If left blank, the system will generate a unique identifier.

Required Attributes and Validations for the Contract Object

To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Ensure that you provide valid values for the attributes. The following table lists the required attributes for importing new Contract records, prerequisite setup tasks for the attributes, and specific validations, if any, for Contract import:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Contract Record	Updating an Existing Contract Record
ContractNumber	The alternate unique identifier of the Contract.	No validation	Required	Not required
ContractPuid	The unique PUID that identifies the Contract.	This number identifier must be unique across Contracts of all types.	Required	Required
ContractTypeId	The unique ID of the Contract type. The Contract type sets various properties for the Contract such as the type of permitted Contract lines, party roles, Contract validation checks, and the Contract acceptance and signature requirements.	You can determine and manage Contract types. Navigate to the following in Setup and Maintenance: Offering: Sales Functional Area: Sales Task: Manage Contract Types	Required if ContractTypeName isn't entered.	Not required
ContractTypeName	The name of the Contract type. The Contract type sets various properties for the Contract such as the type of permitted Contract lines, party roles, Contract validation checks, and the Contract acceptance and signature requirements.	You can determine and manage Contract types. Navigate to the following in Setup and Maintenance: Offering: Sales Functional Area: Sales Task: Manage Contract Types	Required if ContractTypeId isn't entered.	Not required
Currency	The name of the currency in which Contract amounts are entered.	This must be a valid currency.	Required if CurrencyCode isn't entered	Not required
CurrencyCode	The code of the currency in which Contract amounts are entered.	This must be a valid currency.	Required if Currency isn't entered	Not required
InvOrganizationId	The unique Id representing the item master organization	This must be a valid ORGANIZATION_ID from the HR_ALL_ORGANIZATION_UNITS_F table.	Required if the InvOrgName isn't entered	Not required
InvOrgName	The name representing the item master organization.	This must be a valid ORGANIZATION_ID from the HR_ALL_ORGANIZATION_UNITS_F table.	Required if the InvOrganizationId isn't entered	Not required
LegalEntityId	The unique Id of the legal entity to which the Contract belongs.	This must be a valid record as per GL_LEDGER_LE_V.	Required if the LegalEntityName isn't entered.	Not required
LegalEntityName	The name of the legal entity to which the Contract belongs.	This must be a valid record as per GL_LEDGER_LE_V.	Required if the LegalEntityId isn't entered.	Not required
OrgId	The unique Id of the business unit to which the Contract belongs.	This must be a valid business unit Id.	Required if the OrgName isn't entered	Not required
OrgName	The name of the business unit to which the Contract belongs.	This must be a valid business unit name.	Required if the OrgId isn't entered	Not required
StartDate	The date on which the Contract comes into effect.	No validation	Required	Not required
StsCode	The code of the Contract status. Examples are ACTIVE, DRAFT, CLOSED, and CANCELED.	Navigate to the following in Setup and Maintenance: Offering: Sales Functional Area: Sales Task: Manage Standard Lookups Search for the Contract Statuses lookup. Activating a draft contract, and one-time import of closed, canceled, and active contracts is supported. You can't update the contract status from active to any other status. Also, you can't update a contract once it is active. You can't import contracts in EXPIRED status directly in the system. You must import the contracts with ACTIVE status and then update contract status to EXPIRED.	Required	Not required

Note: Keep a note of the following:

The attribute GeneratedInvoiceStatus must have one of the following values:
- D for Draft
- S for Submitted for approval
- R for Released
- Ensure to provide one of the values D, S, or R while importing Project contracts.
SupplierId is the party identifier of the supplier and SupplierSiteId is the party site identifier of the vendor.
When you import contracts using the contract type column with the contract numbering method set as Automatic, you can leave the ContractNumber column blank in the CSV file for the application to generate the contract numbers automatically. You can also enter the contract number manually when you don't want the application to assign the contract numbering automatically.
When the contract type has the contract numbering method set as Manual, you can't leave the contract number blank. If the contract number is left blank, then the application generates an error.
To activate a contract while importing, provide the value 'ACTIVE' for the StsCode attribute. This will also activate the lines added to the contract.
To import contracts that are closed, canceled, or on hold, you must first import the contract with all required import files, and then re-import the contract import file with the following information:
- Closed contracts: You must include Status (the status will be Closed), Close reason code, CloseReasonSetCode, Termination Date.
- On-Hold Contracts: You must include Status (the status will be Hold), Hold Reason Code, Hold reason Set Code, Hold Until Date.
- Canceled contracts: You must include Status (the status will be Canceled), Cancel Reason, Cancel reason set code, Cancel date.
- To avoid the modification of the contribution percentage you must include the contribution percentage in the same import file that you're using to activate the contract.
To import data in other languages, use the column attributes "Language and Source Language" in Contract header file and set the preferred language. Then import the parties with the desired values.

You can view the Contract object and attributes in the Manage Import Objects page of the Import Management flow. You can find attribute information like type, length, description, and so on, on this page.

Create the Source CSV File

You include the data that you want to import into Sales and Fusion Service in a source CSV file.

You can use the CSV templates available in the Import Objects UI page to create the source CSV file. To download a CSV template:

Go to Navigator > Tools > Import Management > Import Objects.
Select the Contract object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Note: For help in populating the CSV file and to avoid any issues in entering values, see the topic Potential Issues When Opening CSV Files With Excel in Related Topics section.

Create the Import Activity

After you have the CSV file ready, create an import activity to import the information. To create an import activity:

Go to Navigator > Tools > Import Management > Import Queue.
Click Create Import Activity in the Manage Imports page.
In the Enter Import Options page, provide a name for the import activity, and select Contract from the Object drop-down list.
Select the CSV file in the File Name field, and click Next.
The source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.
Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.
Review the import details on the Review and Submit page, and click Submit when you're ready.

Review the Import Results

Check if your import succeeded on the Manage Imports page. This page shows the status of all active, completed, and unsuccessful imports. To check the status of the import activity:

Go to Navigator > Tools > Import Management > Import Queue.
Click All Imports and search for the import activity that you created earlier.
Check the Status column for the import activity. The import is successful if the status displays as Completed. You can drill down on the import activity to go to the Import Status page which provides the status details of the import activity.