Export Account Hierarchies

When you export one or more companies from DaaS, you can select to include company hierarchies with the export. Hierarchies provide a more complete picture of account opportunities across all related businesses and help you stay up to date with changes in corporate structures.

Topics:

• About Company Hierarchies

• Export Hierarchies for Oracle CX

• Export Generic Hierarchies

• Export Selected Records in a Hierarchy

About Company Hierarchies

When you select the Include Company Hierarchies check box, DaaS exports companies with their hierarchies. DaaS links the company DUNS number with its headquarters, branches, parents, and subsidiaries to create the complete company hierarchy.

Note: Selecting Include Company Hierarchies exports ALL company records in that hierarchy. (Some company hierarchies include hundreds of records.) You cannot choose only certain records in the hierarchy to export. A dialog asks for confirmation that you want to include all companies in that hierarchy.

This Include Company Hierarchies check box is enabled for Oracle Account Enrichment subscribers. It could be disabled for the following reasons:

• You select contacts to export.

• You are using an Oracle Marketing Cloud mapping.

DaaS first identifies the Global DUNS Number for the company record you’re exporting. Then it identifies all other company records with that same Global DUNS Number and the relationships between the companies. Companies in the hierarchy file are sorted by the Global Ultimate Company followed by companies in its hierarchy.

The Subsidiary Indicator and Status Code attributes identify parent node information. The Status Code attribute defines the status of the business, such as Single Location (0), Headquarters (1), or Branch (2). Status Code is used along with Subsidiary Indicator to identify if the business is a subsidiary or a branch.

A subsidiary is a separate legal entity that reports up to a Parent DUNS Number. A subsidiary never has an HQDUNS#. DaaS uses the Domestic Ultimate DUNS Number above the subsidiary as the parent for the subsidiary. If Domestic Ultimate DUNS Number does not exist, then it uses the Global Ultimate DUNS Number as the parent for the subsidiary.

A branch is not a legal entity by itself but part of a legal entity that is the Headquarter DUNS. A branch never has a Parent DUNS Number. DaaS uses the Headquarter DUNS for the branch as the parent for the branch. If Headquarter DUNS does not exist, then it uses Domestic Ultimate DUNS Number as the parent. And if Domestic Ultimate DUNS Number does not exit, then it uses Global Ultimate DUNS Number as the parent.

Note: Hierarchy exports don't include defunct or out-of-business companies. See Set Admin Defaults. Additionally, no hierarchy generates if you exceed your subscription quota. The service doesn't support (or charge for) partial hierarchy creation.

Export Hierarchies for Oracle CX

CX Sales supports exporting HZ_DNB_HIERARCHY type hierarchies, which show all relationships between different companies within a corporate family in the D&B database. (Relationships happen when one business entity "controls" another business entity because it has financial or legal responsibility for it, creating a Headquarters-Branch or Parent-Subsidiary relationship.) When generating this D&B hierarchy, DaaS returns the ultimate parent of the requested company and all related entities (that is, the full family hierarchy). It cannot return only the direct line entities between the company and the global ultimate (upward company hierarchy) or the children entities of the company (downward company hierarchy).

The D&B hierarchy in DaaS updates monthly and reflects mergers, acquisitions, openings, and closings. As companies grow and change, you can use the D&B hierarchy to understand how an organization is structured, view and assess risks across different part of an organization, identify sales opportunities, and negotiate purchase conditions from a better position. You can also understand the changes in the corporate structure, compare them with the account hierarchy structure in CX Sales, and see account opportunities across all related businesses.

When used with a CX Sales mapping, DaaS creates the following mapping files required to import hierarchies into CX Sales.

• Account.csv

  • Address.csv

  • Classification.csv

  • AdditionalIdentifier.csv

  • AdditionalName.csv

• Hierarchy.csv

• HierarchyMembers.csv

For detailed information about these files, see DaaS Files for Import Management in CX Sales.

The data steward then imports these files into CX Sales:

1. Import the accounts (Accounts.cvs file) and then import child files that are part of the account hierarchies. The import process creates the account if it doesn’t already exist in CX Sales.

2. Import the hierarchy definition (Hierarchy.csv file).

3. Import existing companies as company hierarchy members (HierarchyMembers.csv) into the hierarchy defined in #2.

When importing a company hierarchy into CX Sales, you must create an import activity for each file in D&B hierarchy. From the Navigator, click Tools > Import Management > Create Import Activity.

Each import activity also needs a corresponding mapping definition that describes how the DaaS source file attributes map to the corresponding CX Sales target attributes. CX Sales does not provide a predefined map definition for creating a D&B customer hierarchy or for creating a member: a data steward must define the mappings in order to create an import activity for importing a company hierarchy, and also a second import activity for adding the companies to the company hierarchy.

Mappings required by the Manage File Import task:

• Mappings for companies: Use existing mapping definitions for companies, or create a custom mapping for accounts based on the Account object.

• Mapping for the hierarchy definition: Create a mapping in CX Sales based on the Hierarchy object.

• Mapping for hierarchy members: Create a mapping in CX Sales based on the Hierarchy Nodes object.

For example:

1. Create the Customer Hierarchy Mapping.

   • Create new mapping “CreateCustomerHierarchyMapping” on the Manage Imports page.

   • Set Object = Customer hierarchy.

   • Define the source and target attributes for the mapping.

2. Create the Members mapping.

   • Create new mapping “CreateNodeMapping” on the Manage Imports page.

   • Set Object = Customer hierarchy member.

   • Define the source and target attributes for the mapping.

3. Import all hierarchy files.

   • Create a new task using the Manage Imports to import the customer file.

   • Create tasks using the Manage Imports to import all the account files (object name = Account), as well as the hierarchy file (object name = Customer Hierarchy), and the hierarchy members file (object name = Customer Hierarchy Member).

   (The hierarchy created is type HZ_DNB_HIERARCHY.)
4. Verify that the hierarchy imported into CX Sales.

   • Log in to Oracle CX as an administrator, and navigate to Customer Data Management - Parties.

     

   • Search for a customer; for example, Beth Israel.

     

   • In the Party Center tree view, select Hierarchy Memberships.

     

   • Select the tree node for the details in the hierarchy.

     

     

DaaS only supports creation of new company hierarchies and deletion of existing company hierarchies. To update an existing D&B hierarchy imported from DaaS, you must first delete the existing D&B hierarchy in CX Sales, and then import the D&B hierarchy again. The import process imports the hierarchy as a new hierarchy. To delete an existing D&B hierarchy imported from DaaS, set the “Data/ActionCode” to DELETE.

Export Generic Hierarchies

When used with a Generic mapping, DaaS creates two files: the company file (which consists of records selected by user), and the companies hierarchy file (which contains a minimal data set of the all the companies in hierarchy). You’re charged only for records exported without all data elements for company records.

This minimal data set identifies all companies under the same Global Ultimate DUNS Number. Consuming applications can reference information in the hierarchy file to create company hierarchies using the following attributes:

• OrganizationName (column E)

• DunsNumberC (column I)

• GlobalUltimateDunsNumbC (column J)

• GlobalUltimateBusinessName (column EX)

• GlobalUltimateIndicator (column EY)

• Parent/HeadquarterBusinessName (column FD)

The following file formats are supported for generic hierarchy exports: TXT, XLST, JSON, and XML.

Export Selected Records in a Hierarchy

Selecting the Include Company Hierarchies check box in the user interface exports all company records in that hierarchy, and some hierarchies include hundreds of records! To identify the companies in a hierarchy before downloading the records, use the Get Company Hierarchy Tree API.

1. Download the hierarchy tree with /api/v4/search/companies/hierarchy/{daasid}. This returns the hierarchy for a company, including the following attributes: daasid, business name, hierarchy indicator, location type, aggregated revenue, and aggregated employees. (The following facets refine search results within one or more hierarchies: company_hier_indicator, company_gl_du_ids, and company_standalone_id.)

   Note: To get a hierarchy tree, you must provide a DaaS ID (which is created when you export or match a company or contact record).

   See REST API for Oracle Account and Contact Enrichment.

2. Review the downloaded CSV file containing the hierarchy structure, and identify any companies in the hierarchy you want to download.

3. In the user interface, search for that company with company name or any of the other attributes.

4. Export only those records that you want from the hierarchy. You're charged only for those companies exported.

   Note: If you need the full D&B hierarchy created in CX Sales or Customer Data Management, then you must export the complete hierarchy.