The minimum data that is required to import customer hierarchy member information depends on the following:
• The purpose of the import. The data requirements are different when you're creating both the party and the
customer hierarchy member in the same import batch, adding customer hierarchy member to an existing party, or updating a customer hierarchy member record.
• Identifying and associating records. The data requirements are different when you're using source system
information or record IDs to identify and associate records.
Attributes that are available for import in your import file but that aren't listed in the table. For each attribute, the prerequisite setup task before importing that attribute is listed.
Attribute Description Prerequisite
Setup Task Creating Partyand Customer Hierarchy Member Records in the Same Batch Creating Customer Hierarchy Member Record for an Existing Party ActionCode
This attributespecifies to insert or to delete the hierarchy node (tree node). This attribute is typically used only to delete a record.
Use the UPDATE value when updating a record. If deleting an existing record, use the value, DELETE. If inserting a record, use the value INSERT. Conditionally required. A value is required if deleting an existing hierarchy node. Conditionally required. A value is required if deleting an existing hierarchy node. AsOfDate
When ActionCodeis provided as DELETE, No setup task required. Conditionally required. Conditionally required.
Attribute Description Prerequisite
Setup Task Creating Partyand Customer Hierarchy Member Records in the Same Batch Creating Customer Hierarchy Member Record for an Existing Party AsOfDate determines the tree version from which to delete the hierarchy node. Only one version is active on any given date. A value is required if deleting an existing hierarchy node. A value is required if deleting an existing hierarchy node. HierarchyType
Unique Identifierfor a tree structure.
Tree structure can be created and managed using the Setup and Maintenance, Manage Tree Structures task. Required Required HierarchyCode
User-definedidentifier for a tree.
HierarchyCode must exist in the FND_TREE table, column TREE_ CODE or, if the hierarchy is being created in the same batch as this node, then HierarchyCode must exist in HZ_ IMP_ HIERARCHIES_ T table (the interface table for the new hierarchy), column TREE_ CODE (the HierarchyCode attribute for a hierarchy import). [Need the Setup Task for this process]
Required
Required
PartyOrigSystem
The source systemcode that identifies the original source system of the party that you are inserting as a new
Predefine your source system code as enabled for parties, using the Setup and Maintenance,
Conditionally required.
If deleting an existing node, then identify the node
Conditionally required.
If deleting an existing node, then identify the node
Attribute Description Prerequisite
Setup Task Creating Partyand Customer Hierarchy Member Records in the Same Batch Creating Customer Hierarchy Member Record for an Existing Party
node or that exists as the node to be deleted. You provide the source system reference
(PartyOrigSystemReference) and the source
system code (PartyOrigSystem) when the source of your data is your legacy or external system. The import process uses the source system code and source system reference values to: * find the Oracle Sales Cloud internal ID (PartyId) that uniquely identifies an existing party record that was originally imported with the source system reference and source system code values in a prior batch. The party is either being inserted as a new node or is a node to be deleted in this batch. Manage Trading Community Source Systems task. by providing either PartyId or both PartyOrigSystem and PartyOrigSystemReference. by providing either PartyId or both PartyOrigSystem and PartyOrigSystemReference. PartyOrigSystemReference
The ID thatidentifies the party that is the parent node of this node in your legacy or external system. You provide the source system reference
(ParentPartyOrigSystemReference) and the source
system code
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 you will use when importing the party in the same batch
Conditionally required.
If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem Conditionally required. If you're creating a new node, then identify the parent node by providing either ParentPartyId or both
Attribute Description Prerequisite
Setup Task Creating Partyand Customer Hierarchy Member Records in the Same Batch Creating Customer Hierarchy Member Record for an Existing Party (ParentPartyOrigSystem) when the source of your data is your legacy or external system. The import process uses the source system code and source system reference values to: * find the Oracle Sales Cloud internal ID (ParentPartyId) that uniquely identifies the existing parent node (party record) that was originally imported with the source system reference and source system code values in a prior batch. * find the Oracle Sales Cloud internal ID (ParentPartyId) for the new parent node with the source system reference and source system code values that is imported in the same batch as this node. and ParPartyOrigSystemReference. and ParPartyOrigSystemReference. PartyId
The unique internalID of the existing party record that is either being inserted as a new node or is an existing node to be deleted in this batch.
You can obtain the Party ID for an existing party by exporting the Party object using the Setup and Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Conditionally required. If deleting an existing node, then identify the node by providing either PartyId or both PartyOrigSystem and PartyOrigSystemReference. Conditionally required. If deleting an existing node, then identify the node by providing either PartyId or both PartyOrigSystem and
Attribute Description Prerequisite
Setup Task Creating Partyand Customer Hierarchy Member Records in the Same Batch Creating Customer Hierarchy Member Record for an Existing Party ParentPartyId
The unique internalID for the existing party record that is the parent node of this node.
You can obtain the Parent Party ID for an existing party by exporting the Party object using the Setup and Maintenance, Manage Bulk Data Export, Schedule Export Processes task. Conditionally required. If you're creating a new node or deleting an existing node, and the node is not the root node of the hierarchy, then you must identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference. Conditionally required. If you're creating a new node or deleting an existing node, and the node is not the root node of the hierarchy, then you must identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference. ParentPartyOrigSystem
The source systemcode that identifies the original source system of the party that is the parent node of this node. You provide the source system reference
(ParentPartyOrigSystemReference) and the source
system code
(ParentPartyOrigSystem) when the source of your data is your legacy or external system. The import process uses the source system code and source system reference values to: * find the Oracle Sales Cloud internal ID (ParentPartyId) that uniquely identifies the Predefine your source system code as enabled for parent parties, using the Setup and Maintenance, Manage Trading Community Source Systems task. Conditionally required. If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference. Conditionally required. If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference.
Attribute Description Prerequisite
Setup Task Creating Partyand Customer Hierarchy Member Records in the Same Batch Creating Customer Hierarchy Member Record for an Existing Party existing parent node (party record) that was originally imported with the source system reference and source system code values in a prior batch. * find the Oracle Sales Cloud internal ID (ParentPartyId) for the new parent node with the source system reference and source system code values that is imported in the same batch as this node.
ParentPartyOrigSystemReference The ID thatidentifies the
party that is the parent node of this node in your legacy or external system. You provide the source system reference
(ParentPartyOrigSystemReference) and the source
system code
(ParentPartyOrigSystem) when the source of your data is your legacy or external system. The import process uses the source system code and source system reference values to: * find the Oracle Sales Cloud internal ID (ParentPartyId) that uniquely
Identify the reference value from your source system that was used when you imported the parent party in a prior batch, or identify the source system reference you will use when importing the parent party in the same batch. Conditionally required. If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference. Conditionally required. If you're creating a new node, then identify the parent node by providing either ParentPartyId or both ParPartyOrigSystem and ParPartyOrigSystemReference.
Attribute Description Prerequisite
Setup Task Creating Partyand Customer Hierarchy Member Records in the Same Batch Creating Customer Hierarchy Member Record for an Existing Party identifies the existing parent node (party record) that was originally imported with the source system reference and source system code values in a prior batch. * find the Oracle Sales Cloud internal ID (ParentPartyId) for the new parent node with the source system reference and source system code values that is imported in the same batch as this node.
Using Oracle Enterprise Assets to Evaluate Optional Attributes
Information about all available attributes is included in a reference file located in Oracle Enterprise Repository. Review the reference file to explore other customer hierarchy attributes that are available to import and the possible prerequisite steps for those attributes. This reference file includes the following information:
• All customer hierarchy attributes available for import.
• The attribute descriptions. If the attribute is exposed in the user interface, then the corresponding user interface
display name is included with the description.
• The data type, length, and validation logic. The validation information includes the task or work area where you can
view or define valid values before importing data.
• The logic for default values, if values are not provided in your source file.
To access the reference file for customer hierarchy, follow these steps.
1. Using your browser, enter http://fusionappsoer.oracle.com. Sign in as a user or a guest to Oracle Enterprise
Repository.
2. Search for assets, using the following value for your Search String: HZ_IMP_HIERARCHY_NODES_Reference. 3. Navigate to the results, and click the Details tab.
4. Select the HZ_IMP_HIERARCHY_NODES_Reference file.
Additional Tips
Tip: You can explore related topics by entering the following keywords in the Oracle Fusion Help Application search. The Help Application is available from any Oracle Fusion Application page by clicking Help in the top-right corner, and selecting Applications Help.
• Importing customer hierarchies.
• Importing customer hierarchy members.
Tip: If your data is not from a source system, then you can emulate a system by defining a source system and manually generating reference values for your data. For example, if you periodically gather information at sales events or through sales calls, then you might define a source system, using a code of SALES_ACTIVITY. The format of your reference numbers might concatenate the date, salesperson name, and sequence number, such as 01_Jan_2014_Jackson_01.