Import Your Additional Name Data

Use this topic to import Additional Name data into Oracle Applications Cloud. You can use the import functionality to create, update, or delete Additional Name records.

To import Additional Name records, perform the following tasks:

1. Map your source data to Oracle Applications Cloud object attributes.

2. Create source Comma Separated Values (CSV) file for import.

3. Create the import activity.

4. Review the import results.

How You Map Your Source Data to Object Attributes

To import your Additional Name 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 need to set certain options for some attributes in the application before you can populate them. When importing a child record, ensure that its parent record exists in the database.

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 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 Additional Name object, the attributes are NameID and RegistryID.

Required Attributes and Validations

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

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating an Additional Name Record	Updating an Existing Additional Name Record
NameId	Unique identifier of the address record as the primary key	No Validation	Not required	Optional Either the NameId or a combination of Source System and Source System Reference can be passed.
StatusFlag	The status of the additional name	Defaults to Y during creation.	Not required	To inactivate an existing active Additional Name record, provide the value as "N".
NameType	Additional Name Type	This must be a valid name type. The name types can be managed in Manage Name Types.	Required	If you don't provide the primary key, provide the existing additional name type.
PartyNumber	The public unique identifier of the party record to which the Additional Name 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
PartySourceSystem	The code representing the source system for the party (account, contact, household, or legal entity) to which the Additional name 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 Name.	Conditionally required Provide one of the following : 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 Name 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 Name.	Conditionally required Provide one of the following : 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 name is associated.	Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on.	Conditionally required Provide one of the following : 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 address 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	No validation	Provide a valid value.	Not required

You can view the Additional Name 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

The CSV file is provided as input to the file-based data import process. You must populate the CSV file with the data you want to import into Oracle Applications Cloud.

You can either create a CSV file on your own or use templates available in preexisting mappings. To download a template, do the following:

1. In the Navigator, under Tools, click Import Management.

2. Click Import Objects tab to open the Import Object Details page.

3. Select the object you're interested in the Import Object Details page and click the Download icon next to that object name.

4. Save the template CSV file to a location on your desktop.

You must edit the template CSV file and provide valid values for the required attributes. You can attach different types of files, giving each file a specific description.

PartyNumber	NameType	AdditionalName
RN_PTY_06_MAR_19_A1	LEGAL	Test_Addname_A1
RN_PTY_06_MAR_19_A2	LEGAL	Test_Addname_A2
RN_PTY_06_MAR_19_A3	LEGAL	Test_Addname_A3
RN_PTY_06_MAR_19_A4	LEGAL	Test_Addname_A4
RN_PTY_06_MAR_19_A5	LEGAL	Test_Addname_A5

Create the Import Activity

To import data into Oracle Applications Cloud, you need to create an import activity and provide the CSV file as an input to the activity.

To create an import activity, do the following:

1. In the Navigator, under Tools, click Import Management.

2. On the Manage Imports page, click Create Import Activity.

3. In the Create Import Activity: Enter Import Options page, provide a name for the import activity, and select Additional Name from the Object drop-down list.

4. In File Name, browse and upload the required .CSV file, and click Next.

5. In the Create Import Activity: Map Fields page edit the attribute mappings if required, and click Next.

   Note: Click Validate Data to validate the mapping of the source file for unmapped columns and to check for data format issues.

6. In the Create Import Activity: Review and Submit page, click Submit.

Review the Import Results

You can review the import results by checking for the import activity in the Manage Import Activity page. A file import activity is said to be successful when its status displays as Completed. To check the status of the import activity, do as follows:

1. In the Navigator, under Tools, click Import Management.

2. On the Manage Imports page, search for the import activity that you created using one of the search criteria, such as status, name, object, and so on.

3. Check the Status column for the import activity. The import is successful if the status displays as Completed. The other valid values for the import activity status are Queued for import, Preparing data for import, Importing data, Completed with errors, and Unsuccessful.

Note: On this page you can also quickly view the number and status of all active imports, completed imports, and unsuccessful imports that have been submitted.