Import Your Contract Party Contact Data

How You Map Your Source Data to Object Attributes

To import your Contract Party Contact 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 Party Contact object, the attributes are Id and Contact 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 Party Contact object, the attribute is Contact PUID.

Required Attributes and Validations for the Contract Party Contact 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 Party Contact records, prerequisite setup tasks for the attributes, and specific validations, if any, for Contract Party Contact import:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Contract Party Contact Record	Updating an Existing Contract Party Contact Record
PartyRolePuid	The unique identifier of the party record.	No validation	Required	Not required
ContactPuid	The unique identifier of the party contact record.	No validation	Required	Required
ContactRoleCode	The role played by the contact in this contract.	OKC_PARTY_CONTACT_SOURCES.CONTACT_ROLE_CODE	Required if the role isn't entered	Required
Role	The name of the role played by the contract in this contract.	No validation	Required if ContactRoleCode isn't entered	Not required
ContactId	The unique identifier of the contract party contact.	HZ_RELATIONSHIPS	Required if PartyContactName isn't entered	Not required
PartyContactName	The name of the contract party contact.	Valid name as per HZ_PARTIES record	Required if ContactId isn't entered	Not required
OwnerYn	Indicates whether the contact is a contract owner	The values must be either YES or NO.	Required	Not required
AccessLevel	The access level of a team member.	This must be one among FULL, READ, or NO_ACCESS.	Required if AccessLevelName isn't entered	Not required
AccessLevelName	The access level of a team member.	This must be one among Full, Read, or No Access.	Required if AccessLevel isn't entered	Not required

You can view the Contract Party Contact 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.

Note: Prior to the 20B release, the logged in user was getting defaulted as the contract owner for a contract automatically. From the 20B release, the logged in user won't get defaulted automatically when you import the contract header. You need to specify the contract owner information in the Contract Party Contact CSV file and import it.

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 Party Contact 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 Party Contact 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.