How do I import contract line data?
You can use Import Management to create or update Contract Line records.
To import Contract Line records, perform the following tasks:
-
Map your source data to Oracle Applications Cloud object attributes.
-
Create source Comma Separated Values (CSV) file for import.
-
Create the import activity.
-
Review the import results.
How You Map Your Source Data to Object Attributes
To import your Contract Line 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
To import data into Oracle Applications Cloud, your CSV file must include some specific attributes that enable the import process to uniquely identify the records. The file import process uses the attribute values to automatically map your source data to the target object attributes in Oracle Applications Cloud.
The preferred options to uniquely identify an object record are as follows:
-
Internal ID: If you're identifying a record that already exists in Oracle Applications Cloud, then you can use the internal ID of the record, a system-generated unique identifier attributes with "ID" in the attribute name are typically internal IDs. You can determine the internal ID of a record by exporting Oracle Applications Cloud object data, or by doing a transactional database query. Using an internal ID typically provides better performance and reduces the import duration. For the Contract Line object, the attributes are Line Id and Id.
-
Public unique identifiers: If you're creating new records, then you can provide a user-friendly public unique identifier (attributes denoted with 'Number' and usually visible in the business object's UI). If you update a record for which you have previously provided a Number attribute, or for which a Number attribute is visible in the object's UI, you can use the Number attribute to identify the record. For the Contract Line object, the attribute is Line PUID.
Required Attributes and Validations for the Contract Line 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 Line records, prerequisite setup tasks for the attributes, and specific validations, if any, for Contract Line import:
Attribute |
Description |
Prerequisite Setup Task/ Import Validations |
Creating a Contract Line Record |
Updating an Existing Contract Line Record |
---|---|---|---|---|
ContractPuid |
The unique PUID that identifies the contract |
No validation |
Required |
Not required |
ItemName |
The item name for an item type of line |
This must be a valid inventory item. |
Required for an item type of line |
Not required |
ItemNameTxt |
The item name for a free form type of line |
No validation |
Required for a free form type of line |
Not required |
ItemQuantity |
The line quantity. |
No validation |
Required for an item type of line |
Not required |
LineAmount |
The line amount. |
No validation |
Required for a free form type of line |
Not required |
LineNumber |
The number of the contract line. |
This must be a unique number within a contract. |
Required |
Not required |
LinePuid |
The unique PUID that identifies the contract line. |
This must be a unique PUID across all contract line records. |
Required |
Required |
LineStatus |
The line status |
This must be one of Active, Draft, Closed, or Canceled. |
Required if StsCode isn't entered |
Not required |
LineTypeId |
The Id that represents the line type. |
This must be valid as per OKC_CONTRACT_TYPE_LINES. |
Required if LineTypeName isn't entered |
Not required |
LineTypeName |
The name of the line type. |
This must be valid as per OKC_CONTRACT_TYPE_LINES. |
Required if LineTypeId isn't entered |
Not required |
StartDate |
The date from which the contract line becomes effective. |
No validation |
Required |
Not required |
StsCode |
The code that represents the line status |
This must be one of ACTIVE, DRAFT, CLOSED, or CANCELED |
Required if LineStatus isn't entered |
Not required |
UnitOfMeasure |
The unit of measure of the contract line. |
This must be a valid unit of measure in INV_UNITS_OF_MEASURE_TL.UNIT_OF_MEASURE. |
Required if the UOMCode isn't entered |
Not required |
UnitPrice |
The unit price of the line. |
No validation |
Required for an item type of line |
Not required |
UOMCode |
The UOM code of the contract line. |
This must be a valid unit of measure in INV_UNITS_OF_MEASURE_B.UOM_CODE. |
Required if the UnitOfMeasure isn't entered |
Not required |
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
. -
Select the Contract Line object in the table and click Download.
You can now edit the downloaded file and provide valid values for the required attributes.
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
. -
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 Line 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
. -
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.