Import Your Classification Data

How You Map Your Source Data to Target Object Attributes

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

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

If you want to import only a few records, then you can create a single CSV file for all classification 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 classification child objects. Note that you must have imported the CSV file for classification 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. For more information, see the related topics section.

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

Required Attributes and Validations for Classification Object

To import data successfully into Oracle Applications Cloud, your CSV file must include the required attributes. Make sure that you provide valid values for these attributes so that they pass import validations inbuilt into the application.

This table lists the required attributes for classification records, prerequisite setup tasks and specific validations, if any:

Attribute	Description	Prerequisite Setup Task/ Import Validations	Creating a Classification Record	Updating an Existing Classification Record
PartySourceSystem	The code representing the source system for the party(account, contact, household, or legal entity) to which the Classification belongs.	Identify the source system code that was used when you imported the party in a prior batch, or identify the source system code that you will use when importing the party in the same batch as this Classification.	Conditionally required Provide one of the following : PartyId (internal ID) PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile.	Optional
PartySourceSystemReferenceValue	The reference number or text representing the source system unique ID for the party (account, contact, household, or legal entity) to which the classification belongs.	Identify the reference value from your source system that was used when you imported the party in a prior batch, or identify the source system reference that you will use when importing the party in the same batch as this classification.	Conditionally Required Provide reference information to identify the existing party. The reference information can be: PartyId ( internal ID) PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile. Party Number (public unique identifier for an organization profile)	Optional
PrimaryFlag	Identifies primary classification for the parent party record.	Only one of the child records can be Primary.	Optional	Optional Pass Y to set Primary and N to reset an existing primary record.
CodeAssignmentId	The unique identifier for the customer classification assignment.	It should be a valid existing value.	Not required	Either the Code assignment Id or a combination of Source System and Source System Reference is required.
ClassCategory	The classification category name	The class category must exist. You can manage class categories from the Manage Class Categories task.	Required A value is required if creating a new classification association record.	Not Required
ClassCode	The classification code, within the classification category, assigned to the party.	The value must be a valid code for the classification category. You can only assign one code if the category definition isn't enabled for multiple code assignments to a party within the same category. The code assignment must not already exist within the same time period. You can obtain classification codes for a classification category.	Conditionally required A value is required if creating a new classification association record.	Not Required
StartDateActive	The date on which the classification becomes valid.	This should be a valid date.	This defaults to the current date.	Not required
PartyId	The internal ID for the party (account, contact, household, or legal entity) to which the address belongs	Identify the party ID value by exporting the relevant Party object such as Account, Contact, and so on.	Conditionally required Provide reference information to identify the existing party. The reference information can be: PartyId (internal ID) PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile. Party Number (public unique identifier for an organization profile)	Not required
PartyNumber	The public unique identifier of the party record to which the classification category and classification code are associated.	The party number must exist.	Conditionally Required Provide reference information to identify the existing party. The reference information can be: PartyId (internal ID) PartySourceSystem and PartySourceSystemReference(source system code and source system reference values) provided when importing the organization profile Party Number (public unique identifier for an organization profile)	Not required
EndDateActive	The date on which the classification code is no longer valid.	This should be a valid date.	Optional	Not required
SourceSystem	Name of external source system of the account, contact or household with which the address is associated.	The source system should exist. You can manage source systems from the Manage Source Systems task.	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.	Not required
SourceSystemReferenceValue	Specifies the identifier in the original source system	The combination of Source System and Source System Reference Value should be unique.	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.	Not required

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