Import Your Partner Data

How You Map Your Source Data to Target Object Attributes

To import your Partner 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. For the Partner object, this attribute is 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 Partner object, the attribute is CompanyNumber.

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

To update the status of a partner, create an import by providing values for the attributes PartyId, Status,and CompanyNumber in the CSV file.

This table lists the required attributes for importing new Partner records, required attributes for updating Partner records, prerequisite setup tasks for the attributes, and specific validations, if any, for Partner import:

Attribute	Description	Data Type	Data Length	Prerequisite Setup Task/ Import Validations	Creating a Partner Record	Updating an Existing Partner Record
OrganizationName	The name of the organization	Text	360	The value is required if creating a new organization.	Required	Not required
AddressLineOne	The first line of the postal address	Text	240	No validation	Required	Not required
Country	The country code of the postal address	Text	2	If providing a value, the value must exist in the FND_TERRITORIES_B table. You can view valid country codes. Navigate to the following in the Setup and Maintenance work area: Offering: Sales Functional Area: Data Import and Export Task: Manage Territories	Required	Not Required
PartyId	The unique ID for the existing partner organization's party record in the destination table	Number	18	Identify the PARTY_ID for an existing partner party by exporting the Partner Profile object. Navigate to the following in the Setup and Maintenance work area: Offering: Sales Functional Area: Data Import and Export Task: Manage Bulk Data Export, Schedule Export Processes	Not required	A value is required either for PartyId or CompanyNumber.
CompanyNumber	The company number of the partner.	Text	30	If providing a value and importing a new party in the same import batch as this certification, the value must be unique in the ZPM_IMP_PARTNER table. If providing a value for an existing party, the value must exist in the ZPM_PARTNER_PROFILES table, column COMPANY_NUMBER.	Not required	A value is required either for CompanyNumber or PartyId.

You can view the Partner 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 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 Partner object in the table and click Download.

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

You can specify the required role while creating the first partner contact for a partner. Also, once the first partner contact has been created, you can update the role for this partner contact.

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:

In the Navigator, under Tools, click Import Management.
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 Partner from the Object drop-down list.
In File Name, browse and upload the required .CSV file, and click Next.
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.
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:

In the Navigator, under Tools, click Import Management.
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.
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.