Import Your Relationship Data

How You Map Your Source Data to Target Object Attributes

To import your Relationship 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 must 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 steps are complete, such as understanding what attributes are required for importing your objects.
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

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 relationships or are updating relationships that have source system reference data, then provide the source system and source system reference values.

Required Attributes and Validations for Relationship 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 relationship records, prerequisite setup tasks and specific validations, if any:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Relationship record	Updating an Existing Relationship record
RelationshipRecId	The unique ID for the existing Relationship record in the destination table.	None	Don't provide a value.	Conditionally required Either the RelationshipRecId or a combination of RelationshipSourceSystem and RelationshipSourceSystemReferenceValue is required.
SubjectPartyId	The primary key identifier of the subject in this relationship.	The party must exist.	Either one of SubjectPartyId, SubjectPartyNumber, and a combination of SubjectSourceSystem and SubjectSourceSystemReferenceValue, is used to identify the subject party of the relationship.	Optional Either one of SubjectPartyId, SubjectPartyNumber, and a combination of SubjectSourceSystem and SubjectSourceSystemReferenceValue, is used to identify the subject party of the relationship.
RelationshipType	The relationship type name. For example, CUSTOMER_SUPPLIER. A list of valid relationship types is defined in the lookup HZ_RELATIONSHIP_TYPE. The unique ID for the existing customer party record in the destination table.	The party must exist.	Required	Not required
RelationshipCode	Indicates whether this is a forward or a backward relationship code.	A list of valid relationship codes is defined in the lookup PARTY_RELATIONS_TYPE.	Required	Not required
StartDate	The date when the relationship was created.	This should be a valid date.	Optional Defaults to current date	Not required
EndDate	The date when the relationship ends.	This should be a valid date.	Optional	Optional
SubjectType	Subject type of the relationship type.	This should be a valid party type.	Optional	Not required
ObjectType	Object type of the relationship type.	This should be a valid party type.	Optional	Not required
ObjectPartyId	The primary key identifier of the object in this relationship.	The party must exist.	Either one of ObjectPartyId, ObjectPartyNumber, and combination of ObjectSourceSystem and ObjectSourceSystemReferenceValue, is used to identify the object party of the relationship.	Optional Either one of ObjectPartyId, ObjectPartyNumber, and combination of ObjectSourceSystem and ObjectSourceSystemReferenceValue, is used to identify the object party of the relationship.
SubjectPartyNumber	Unique identification number for the subject of relationship	No validation	Either the SubjectPartyId or the SubjectPartyNumber is required.	Either the SubjectPartyId or SubjectPartyNumber, or the combination of SubjectSourceSystem and SubjectSourceSystemReferenceValue is required.
ObjectPartyNumber	Unique identification number for the object of the relationship	The party must exist.	Either one of ObjectPartyId, ObjectPartyNumber, and combination of ObjectSourceSystem and ObjectSourceSystemReferenceValue, is used to identify the object party of the relationship.	Optional Either one of ObjectPartyId, ObjectPartyNumber, and combination of ObjectSourceSystem and ObjectSourceSystemReferenceValue, is used to identify the object party of the relationship.
SubjectSourceSystem	Original System ID for the Subject of the Relationship	The source system should exist. You can manage source systems from the Manage Source Systems task.	Conditionally required	Conditionally required
SubjectSourceSystemReferenceValue	Original System Reference for the Subject of the Relationship	No validation	Conditionally Required 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.	Conditionally Required
ObjectSourceSystem	Original System ID for the Object of the Relationship	No validation	Conditionally required	Conditionally required
ObjectSourceSystemReferenceValue	Original System Reference for the Object of the Relationship	No validation	Conditionally required	Conditionally required
RelationshipSourceSystem	Original system of this relationship	The party must exist.	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.	Conditionally required Either the RelationshipRecId or a combination of RelationshipSourceSystem and RelationshipSourceSystemReferenceValue is required.
RelationshipSourceSystemReferenceValue	Original system reference of this relationship	It should be a unique value for a source system.	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.	Conditionally required Either the RelationshipRecId or a combination of RelationshipSourceSystem and RelationshipSourceSystemReferenceValue is required.

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