Import Your Contract Line Internal Attribute Data

How You Map Your Source Data to Object Attributes

To import your contract line internal attribute 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 option to uniquely identify an object record is through the public unique identifier. 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 internal attribute object, the attribute is LinePUID.

Required Attributes and Validations for the Contract Line Internal Attribute 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 internal attribute records, prerequisite setup tasks for the attributes, and specific validations, if any, for contract line internal attribute import:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Contract Line Internal Attribute Record	Updating an Existing Contract Line Internal Attribute Record
LinePuid	The PUID of the contract line for which the internal attributes are captured.	This must be a valid contract line PUID.	Required	Not required
ExtSource	The external source of the contract line internal attribute information.	This must be a unique combination of external source and key.	Required A combination of external source and external key is required.	Required
ExtKey	The external key of the contract line internal attribute information.	This must be a unique combination of external source and key.	Required A combination of external source and external key is required.	Required
ProviderBusinessUnitId	The provider business unit ID. This is applicable for inter-company contract	This must be a valid business unit ID.	Required if a business unit name isn't passed.	Not required
ProviderBuName	The provider business unit name. This is applicable for inter-company contract.	This must be a valid business unit name.	Required if a business unit ID isn't passed.	Not required
RcvrBusinessUnitId	The receiver business unit ID. This is applicable for inter-company contract.	This must be a valid business unit ID.	Required if a business unit name isn't passed.	Not required
RcvrBuName	The receiver business unit name. This is applicable for inter-company contract.	This must be a valid business unit name.	Required if a business unit ID isn't passed.	Not required
ReceiverProjectId	The receiver project ID. This is applicable for inter-company and inter-project contracts.	This must be a valid project ID.	Required if a project number isn't passed.	Not required
ReceiverProjectNumber	The receiver project number. This is applicable for inter-company and inter-project contracts.	This must be a valid project number.	Required if a project ID isn't passed.	Not required
ReceiverTaskId	The receiver task ID. This is applicable for inter-company and inter-project contracts.	This must be a valid task ID.	Required if a task number isn't passed.	Not required
ReceiverTaskNumber	The receiver task number. This is applicable for inter-company and inter-project contracts.	This must be a valid task number.	Required if a task ID isn't passed.	Not required

You can view the contract line internal attribute 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 Line Internal Attribute 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 Line Internal Attribute 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.