Import Your Additional Identifier Data

How You Map Your Source Data to Object Attributes

To import your Additional Identifier 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, 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

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. Use this option only if you're updating Additional Identifiers. 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 Additional Identifier object, the attributes are PartyIdentifierID and PartyID.
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 Additional Identifier object, the attribute is PartyNumber.

Required Attributes and Validations for the Additional Identifier 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 Additional Identifier records, required attributes for updating Additional Identifier records, prerequisite setup tasks for the attributes, and specific validations, if any, for Additional Identifier import:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Additional Identifier Record	Updating an Existing Additional Identifier Record
PartySourceSystem	The code representing the source system for the party (account, contact, household, or legal entity) to which the Additional identifier belongs	Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this Additional identifier.	Conditionally required Provide reference information to identify the existing party. The reference information can be: PartyId (internal ID) PartySourceSystem and PartySourceSystemReference (source system code and source system reference values) provided when importing the organization profile Party Number (public unique identifier for an organization profile)	Not required
PartySourceSystemReferenceValue	The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the Additional identifier belongs.	Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this Additional identifier.	Conditionally required Provide reference information to identify the existing party. The reference information can be: PartyId ( internal ID) PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile Party Number (public unique identifier for an organization profile)	Not required
PartyIdentifierID	Unique identifier of the additional identifier of the party	No validation	Not required	Required
StatusCode	The status of the additional identifier	Not required This defaults to Y during creation.	Not required	To inactivate existing active Additional Name record, provide the value as N.
PartyIdentifierType	The type of the Additional Identifier import	The Identifier Type must exist. You can manage additional types using the Manage Additional Name Types task.	Required	Not required
PartyIdentifierValue	Value to be imported for the Identifier Type	Mandatory field	Required	Not required
PartyNumber	The public unique identifier of the party record to which the Additional identifier is associated.	The party number should exist.	Conditionally required Provide reference information to identify the existing party. The reference information can be: PartyId (internal ID) PartySourceSystem and PartySourceSystemReference (source system code and source system reference values) provided when importing the organization profile Party Number (public unique identifier for an organization profile)	Not required
PartyID	The unique identifier as primary key of the party record to which the additional identifier is associated.	Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on.	Conditionally required Provide reference information to identify the existing party. The reference information can be: PartyId (internal ID) PartySourceSystem and PartySourceSystemReference (source system code and source system reference values) provided when importing the organization profile Party Number (public unique identifier for an organization profile)	Not required
SourceSystem	Name of external source system of the account, contact or household with which the Additional identifier is associated.	The source system should exist. You can manage source systems from the Manage Source Systems task.	Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values.	Not required
SourceSystemReferenceValue	Specifies the identifier in the original source system.	The combination of Source System and Source System Reference Value should be unique.	Optional If the source of your data is a third party or external system, and you intend to import updates to previously imported records from the same system, provide the original source system and source system reference values.	Not required

You can view the Additional Identifier 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 templates available in the Import Objects UI page to create the source CSV file. To download a template:

Go to Navigator > Tools > Import Management > Import Objects.
Select the Additional Identifier 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 Additional Identifier 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.