1. Understanding Import and Export Management for Sales and Fusion Service
  2. Import Your Linked Party Data

Import Your Linked Party Data

You can use the import management to create or delete your Linked Party records.

To import Linked Party 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 Target Object Attributes

To import your Linked Party data into Oracle Applications Cloud, you need to 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 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

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.

  • 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.

Required Attributes and Validations for Linked Party 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 importing new Linked Party records, required attributes for deleting Linked Party records, prerequisite setup tasks for the attributes, and specific validations, if any, for Linked Party import:

Attribute

Description

Prerequisite Setup Task/ Import Validations

Creating a Linked Party Record

Deleting a Linked Party Record

LinkType

Indicates the type of Link Sets such as B2F_EQUIV.

None

Required

 Required

RelatedPartyId

Fusion identifier of the Party which is related to the Link Set.

None

Conditionally Required. Either RelatedPartyId or RelatedPartyNumber must be provided. It should be party of the Customer party usage.

 Not Required

RelatedPartyNumber

 Public unique identifier of the Party which is related the the Link Set.

None

Conditionally Required. Either RelatedPartyId or RelatedPartyNumber must be provided. It should be party of the Customer party usage.

 Required

PartyId

Fusion unique identifier of the party.

 None

Conditionally Required. Either PartyId or PartyNumber must be provided. It should be a party of Sales such as Sales Prospect or Sales Account party usage.

 Not Required

PartyNumber

The public unique identifier of the party.

None

Conditionally Required. Either PartyId or PartyNumber must be provided. It should be a party of Sales such as Sales Prospect or Sales Account party usage.

 Required

You can view the Linked Party object along with all its child objects 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 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:

  1. Go to Navigator > Tools > Import Management > Import Objects.

  2. Select the Linked Party object in the table and click Download.

You can now edit the downloaded file and provide valid values for the required attributes.

Here is a recommended format for the CSV file:
LinkType RelatedPartyNumber PartyNumber MainLink
B2F_EQUIV FinancialParty-2 SalesParty-1 Y
B2F_EQUIV FinancialParty-3 SalesParty-1 Y
B2F_EQUIV SalesParty-1 FinancialParty-2 N
B2F_EQUIV SalesParty-1 FinancialParty-3 N
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

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

Related Topics