How do I import account data?

How You Map Your Source Data to Target Object Attributes

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

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

Note: You can enable automatic territory-based assignment after sales accounts are imported. You can enable this feature by turning the profile option ZCA_BATCH_ASSIGN_ON_BULK_IMPORT ON. If the profile option is disabled, then you must manually run a batch assignment or assign each sales account individually.

To better manage your account information, the account object has the following child objects:

Address
Classification
Relationship
Sales Team Member

Note: You can't set an attribute value to NULL in high-volume import (import management with the option Enable High-Volume Import selected). However, when updating a record, you can change an attribute value from NOT NULL to NULL

If you're importing account records with attributes specific to the parent account object or along with single child record details (like phone, email, address, and so on), then you can include the child record details in the same .csv file for account object. However, if you're importing multiple records of any child object, then you must create multiple .csv files to import- one for each child which has multiple records that you're importing. For example, if you're importing 5 emails, 5 phones, and 5 addresses for an account, then you must create three import files - one for Account object, one for Contact Point object (phone and email), and one for Address object. There are separate help topics describing how to import each of these child objects. For more information, see the related topics section.

Note: High-volume import for accounts now supports hierarchy management and generation.

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. For example, when using source system reference information to identify your account records, the source system of the account object should be enabled for parties using the Manage Trading Community Source Systems task.
You have all parent records in place before importing child records. For example, when importing the address of an account, ensure the account exists.

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 account object, the attribute is PartyNumber and shows up in the UI as Party 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 new accounts or are updating accounts that have source system reference data, then provide the source system and source system reference values. For account object, these are SourceSystem and SourceSystemReferenceValue and show up as Party Source System and Party Source System Reference Value in the UI.

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

Attribute	Description	Prerequisite Setup Tasks or Import Validations	Creating an Account Record	Updating an Existing Account Record	Deleting an Existing Account Record
SourceSystem	The source system for the sales account.	Know the source system. To view source systems, use the Manage Trading Community Source System task.	Conditionally Required To identify an account record, use one of these: SourceSystem and SourceSystemReferenceValue PartyNumber	Conditionally Required To identify an account record, use one of these: SourceSystem and SourceSystemReferenceValue PartyNumber	Conditionally Required To identify an account record, use one of these: SourceSystem and SourceSystemReferenceValue PartyNumber
SourceSystemReferenceValue	The reference number or text representing the source system unique ID for the party (account or contact) to which the sales profile belongs.	Know the source system reference value. To view the source systems reference, use the Manage Trading Community Source System task.	Conditionally Required To identify an account record, use one of these: SourceSystem and SourceSystemReferenceValue PartyNumber	Conditionally Required To identify an account record, use one of these: SourceSystem and SourceSystemReferenceValue PartyNumber	Conditionally Required To identify an account record, use one of these: SourceSystem and SourceSystemReferenceValue PartyNumber
PartyNumber	The public unique identifier of the party.	The party must exist. You get a list of all party IDs and party numbers by exporting the Party object.	Conditionally Required	Conditionally Required	Conditionally Required
OrganizationName	The name of the party of the Organization party type.	Organization names are listed in the Resource Directory.	Required	Conditionally Required	Conditionally Required
OwnerPartyId	The identifier of the account owner.	This attribute is required only in import management, but optional in high-volume import.	Required	Not Required	Not Required

Note: When deleting or updating accounts, you must ensure that the account related to the party number provided has the Sales Account usage. If you provide the party number of an account that doesn't have the Sales Account usage, then the relationships for that account are also deleted. For example, if you provide the party number ORA17292 that doesn't have a Sales Account usage, then the related partners, contacts, and so on are also deleted.

For the extension child objects of account, RecordName field isn't unique. Hence you can't update the records only by passing RecordName.

You can use the profile option ORA_HZ_IMPORT_MULTI_ADDRESS_TYPE to control how address types are entered. By default this profile option is set to Yes, so you can enter multiple address types, during high-volume import of Account, Contact, and Household objects . You can disable this profile option to improve the import performance. When you set this profile option to No, you can enter only a single address type.

Note: When importing accounts or legal entities, you can retrieve duplicates using the Customer Data Management Duplicates LOV only if you have licensed the data quality functionality. Once licensed, you must rebuild the keys for your matching configuration using the Manage Enterprise Data Quality Matching Configurations task. After the keys are rebuilt, the matching functionality uses the settings in the match configuration to identify duplicates.

Go to Navigator > Tools > Import Management > Import Objects to see all the attributes of the account 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 CX 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 Account object in the table and click Download.

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

Providing the ZIP and Country Code values in the import CSV file won't automatically populate the State/County/City fields. Values for these fields should be separately provided in the import file.

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

Note: After importing your data successfully, you need to run a couple of post processing jobs for duplicate identification, duplicate resolution, and account assignment. For more information on import management post processing jobs, see the topic: Import Management Post Processing for Accounts and Contacts.

When importing accounts using high-volume import, you can now load the account hierarchy data. Use the following attributes to import accounts using high-volume import:

ParentAccountPartyId
ParentAccountPartyNumber
ParentAccountSourceSystem
ParentAccountSourceSystemReferenceValue

Note: This is available only for low volume data and should not be used for high volume data.

You can load account hierarchy data. To load the account hierarchy data:

Load the account data without providing values for the parent attributes mentioned above.
Load the account hierarchy using the Hierarchy and Hierarchy Member import objects.