Import Your Contract Line Translation Data

You can use the import functionality to create, update, or delete your contract line translation data.

You can import contract line translation records using these steps:

Map your source data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.
Create the source CSV file with the contract line translation data you want to import.
Kick off an import activity.
Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

You import contract line translation data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.

Before you create the source data file, you should:

Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the contract line translation import object.
Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.
Know how you can uniquely identify the records.
Check the target object attributes required in the CSV file for a successful import.

If you want to import only a few records, then you can create a single CSV file for all contract line translation attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the contract line translation child objects.

Before You Start

You must do some basic checks before starting your import. For example, make sure that:

You have completed all the prerequisites for importing each attribute in your source data.
You 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. You can use one of these to identify records:

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.
Source system and source system reference: Source system is an identifier for the external system, and source system reference is a unique identifier within the external system. If you're importing new contract line translation or are updating contract line translation that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Contract Line Translation Object

To import data successfully into Oracle Applications Cloud, your .csv file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.

This table lists the required attributes for contract line translation records, prerequisite setup tasks and specific validations, if any:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Contract Line Translation record	Updating an Existing Contract Line Translation record
LinePuid	The PUID of the contract line for which the translation information is captured.	Must be a valid contract PUID.	Required	Required
Lang	The language in which the translation is captured.	Must be a valid language.	Required	Required

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the contract line translation object. The page also lists attribute information like type, length, description, and so on.

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 Translation 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 contract line translation information. To create an import activity:

Go to Navigator > Tools > Import Management > Import Queue.
On the Manage Imports page, click Create Import Activity.
In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Contract Line Translation from the Object drop-down list.
Select the CSV file in the File Name field, and click Next.
You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues.
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.