How do I import person data?

How You Map Your Source Data to Target Object Attributes

You import Person 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 Person 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.
Ensure that you don't insert duplicate Person while importing, to avoid redundant data.

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: You can pass the PUID when creating Person records. If the PUID isn't passed, it will be auto generated. You can optionally provide the PUID when creating Person records. If you're updating 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 Persons or are updating Persons that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Person 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.

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

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Person record	Updating an Existing Person record
PartyId	The internal ID for the Person type party	When updating the record, this should already exist.	Not required	Conditionally required. To identify a person record, use one of these: Combination of SourceSystem and SourceSystemReferenceValue PartyNumber PartyId
Country	The country code of the postal address	Identify valid country codes using the Setup and Maintenance, Manage Territories task.	Conditionally required A value is required only when you're creating an address for the Person record.	The attribute is neither required nor conditionally required.
AddressNumber	The internal unique identifier that's internally generated when creating an address	No validation	This is a PUID for Address. If a value is passed, it will be imported. Otherwise, it will be auto-generated.	Pass the AddressNumber.
OrganizationPartyNumber	The party number of the organization to which the person is related	This should already exist.	Not required	Not required
DeceasedFlag	The option that indicates whether the person imported is deceased	Y or N The default value is N.	Not required	Not required
PartyNumber	The unique identifier of the party	Know the party number. To obtain a list of all party IDs and party numbers, export the Person object.	This is a PUID for Person. If a value is passed, it will be imported. Otherwise, it will be auto-generated.	Conditionally required To identify a person record, use one of these: Combination of SourceSystem and SourceSystemReferenceValue PartyNumber PartyId
FirstName	The first name of the person	No validation	Required. A value is required for the FirstName, MiddleName, or LastName.	Not required
MiddleName	The middle name of the person	No validation	Required. A value is required for the FirstName, MiddleName, or LastName.	Not required
LastName	The last name of the person	No validation	Required. A value is required for the FirstName, MiddleName, or LastName.	Not required
PartyUsageCode	Specifies the party usage code to which the person is associated	Select one of the following values: EXTERNAL_PAYEE CONTACT PAYMENT_ISSUING_AUTHORITY PARTY_OF_INTEREST VIRTUAL_ASSISTANT FS_TECH You can assign a limited set of unrestricted party usages through the Person import object. To create persons of other types, use the specific import objects created for those purposes.	Required	Not required
SourceSystem	The original source system name	Know the source system. To view source systems, use the Manage Trading Community Source System task.	Conditionally required To identify a person record, use one of these: Combination of SourceSystem and SourceSystemReferenceValue PartyNumber	Conditionally required To identify a person record, use one of these: Combination of SourceSystem and SourceSystemReferenceValue PartyNumber PartyId
SourceSystemReferenceValue	The identifier in the original source system	Know the source system reference value. To view source system reference, use the Manage Trading Community Source System task.	Conditionally required To identify a person record, use one of these: Combination of SourceSystem and SourceSystemReferenceValue PartyNumber	Conditionally required To identify a person record, use one of these: Combination of SourceSystem and SourceSystemReferenceValue PartyNumber PartyId

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the Person 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 CX 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 Person 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 Person 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 Person 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.
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.