How do I import hierarchy data?

You can use the import management to create Hierarchy data.

The hierarchies supported are:

• Customer hierarchy

• Dun and Bradstreet hierarchy

• Trading Community Party hierarchy

To import Hierarchy 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 Hierarchy 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 option to uniquely identifying an object record is the 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. Use this option only if you're updating Hierarchies. 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 Hierarchy object, the attributes are TreeStructureCode, TreeCode, TreeName, and TreeVersionName.

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

The following table lists the required attributes for importing new Hierarchy records, prerequisite setup tasks for the attributes, and specific validations, if any, for Hierarchy import:

Attribute	Description	Data Type	Data Length	Prerequisite Setup Task/ Import Validations	Creating a Hierarchy Record
TreeStructureCode	Unique identifier for a tree structure.	Varchar2	30	Seeded data needs to be present.	Required
TreeCode	User defined Identifier for the tree code.	Varchar2	30	No validation	Required
TreeName	Name of the tree	Varchar2	80	No validation	Required
TreeVersionName	Version Name of the tree	Varchar2	80	No validation	Required
LangCode	Indicates the code of the language into which the contents of the translatable columns are translated.	Varchar2	4	No validation	Required
AsofDate	The date that's used to determine the tree version when you're updating a tree version.	Date		No validation	Optional

You can view the Hierarchy 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

The .CSV file is provided as input to the file-based data import process. You must populate the .CSV file with the data you want to import into Oracle Applications Cloud.

You can either create a CSV file on your own or use templates available in preexisting mappings. To download a template, do the following:

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

2. Select the Hierarchy 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. In 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 Hierarchy 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: Initiate the Tree Flattening Service manually. Do one of the following:

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:

1. In the Navigator, under Tools, click Import Management.

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

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