Import Your Partner Type Data

You can use the import functionality to create Partner Type records.

You can import Partner Type records using these steps:

1. Map your source data to Oracle Applications Cloud object attributes. This way the import process would know where to insert each of the information bits.

2. Create the source CSV file with the Partner Type data you want to import.

3. Kick off an import activity.

4. Check the import results to know if the import went well.

How You Map Your Source Data to Target Object Attributes

You import Partner Type data into Oracle Applications Cloud from a CSV file containing your source data that's mapped to target Oracle Applications Cloud object attributes.

Before you create the source data file, you should:

• Know how your source data attributes map to the target object attributes in Oracle Applications Cloud. Match each column from the source file to an attribute in the Partner Type import object.

• Finish all prerequisite steps, such as understanding what attributes are required for importing your objects.

• Know how you can uniquely identify the records.

• Check the target object attributes required in the CSV file for a successful import.

• Ensure that you don't insert duplicate Partner Type records while importing, to avoid redundant data.

If you want to import only a few records, then you can create a single CSV file for all Partner Type attributes. However if you want to import a large number of records, then you may decide to create multiple CSV files, one for each of the Partner Type child objects. Note that you must have imported the CSV file for Partner Type object successfully before trying to import the CSV files for the child objects. There are separate help topics describing how to import each of these child objects.

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. 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 a new Partner Type record that has a source system reference data, then provide the source system and source system reference values.

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

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Partner Type record
IntegrationId	This is an internal attribute and should not be used.	No Validation	Not Required
PartnerTypeName	The partner type assigned to the partner.	No Validation	Either the PartnerTypeName or the PartnerTypeCode is required.
PartnerDimMembersId	The primary key of the Partner Type object.	No Validation	Auto-generated
PartnerCompanyNumber	The company number of the partner.	No Validation	Required

Note: The Update operation isn't supported for Partner Type records.

Go to Navigator > Tools > Import Management > Import Objects, to see all the attributes of the Partner Type 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:

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

2. Select the Partner Type 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 Partner Type information. To create an import activity:

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

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 Type from the Object drop-down list.

4. Select the CSV file in the File Name field, and click Next.

5. You would see that the source and target attributes are automatically mapped in the Map Fields page. Review and edit the mappings if required.

6. Check the file for unmapped columns or data format issues by clicking Validate Data. Click Next.

7. Review the import details on the Review and Submit page, and click Submit when you're ready.

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