Import Your Partner Contact Data

Use this topic to import Partner Contact data into Oracle Applications Cloud. You can use the Import Management to create or update Partner Contact records.

To import Partner Contact 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 Partner Contact 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 Contact 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 Contact object, the attribute is PartyNumber.

Required Attributes and Validations for Partner Contact 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 Partner Contact records, required attributes for updating Partner Contact records, prerequisite setup tasks for the attributes, and specific validations, if any, for Partner Contact import:

Attribute	Description	Data Type	Data Length	Prerequisite Setup Task/ Import Validations	Creating a Partner Contact record	Updating an Existing Partner Contact record
FirstName	The first name of the person	Text	150	A value is required if creating a new person party.	Required	Not required
LastName	The last name of the person	Text	150	A value is required if creating a new person party.	Required	Not required
EmailAddress	The Email address of the partner contact	Text	320	While importing the partner contacts which have the createUserAccountFlag attribute set to 'Y', the username value must be unique. If the username attribute isn't set, then the email address value should be unique.	Required	Not Required
CompanyNumber	The company number of the partner	Text	30	The value must exist in the column COMPANY_MUMBER of the ZPM_PARTNER_PROFILES table. Identify the COMPANY_NUMBER for an existing partner 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	A value is required either for CompanyNumber or PartnerPartyId.	Not Required
PartyNumber	The party number of the contact	Text	30	The PartyNumber must be unique when you're creating a new record and the value needs to be the same as that of a valid partner contact, when you're updating an existing record.	A value is optionally required when creating a record.	A value is required either for PartyNumber or PartyId when updating a record.
PartnerPartyId	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	A value is required either for CompanyNumber or PartnerPartyID when creating a record.	Not required
PrimaryFlag	Indicates if the partner contact is a primary contact	String	1	Set this attribute for a partner contact, if the corresponding partner doesn't have a primary contact. This can be either Y or N.	Required	Not required

Note: When importing partner contacts, use the CompanyNumber attribute. Don't use the PartnerCompanyNumber attribute.

You can view the Partner Contact 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:

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

2. Select the Partner Contact 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

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 Partner Contact 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.

Note: To access and submit the import activities for Partner Contact, the user must be assigned the job roles of the Channel operations manager.

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:

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

2. Click All Imports and search for the import activity that you created earlier.

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