Exporting Hierarchy Nodes

<Do not delete this text because it is a placeholder for the generated list of "main" topics when run in a browser>

Purpose

This tutorial covers how to export hierarchy nodes.

Time to Complete

Approximately 20 min.

Overview

Hierarchy exports are useful when you want to output nodes from selected hierarchies in a flat list or a parent-child relationship format. Examples of hierarchy exports include an outline for a financial report or a list of cost centers by geographic region.

For this type of export, configure the export wizard tabs as follows:

In this tutorial, you export hierarchy nodes.

Prerequisites

Before starting this tutorial, you should have access to or have installed Oracle Hyperion Enterprise Performance Management 11.1.2.1.0 and Oracle Hyperion Data Relationship Management, Fusion Edition 11.1.2.1.0.

Exporting Hierarchy Nodes

In this topic, you create an export and view the export results.

.

Begin by navigating to the Export task group. Use the Export task group to create and manage exports.

 

.

Double-click Planning - Detail to open the Planning - Export hierarchy export.

Use the export wizard to edit the source, style, filter, columns, and target for the Planning - Detail export. You begin on the Source tab.


.

Use the Source tab to specify the source of data that you want to export. For a hierarchy node export, you select a version and one or more hierarchy/top node sets. You can select a normal, baseline, or as-of version. The Planning - Detail export is already configured to use the [Default Current Version] - 2010 03 - Production normal version and the TotalGeography/TotalGeography hierarchy/export top node set. In this example, you add the Function/Function hierarchy/top node set.

Click the Add... button.

 

.

Use the Select Node dialog box to select a hierarchy and export top node. You can also search for a node. Perform the following actions in the Select Node dialog box:

  • In the Hierarchy drop-down list, select Function.
  • Leave the Function node selected as the export top node.

 

.

Click OK.

 

.

Click the Style tab.

Use the Style tab to specify the type of nodes to be included in the export and to specify whether to include implicitly shared nodes. In this example, you export all nodes, recurse from the top node, include inactive nodes, and remove duplicate nodes based on primary key columns.

 

.

Perform the following actions on the Style tab:

  • In the Node Selection field, leave the All Nodes option selected to specify that you want to export all nodes.
  • Leave the Recurse from Top Node option selected to include descendant nodes below the top node. If cleared, only the top node is included.
  • Leave the Include Inactive Nodes option selected to export inactive nodes with the other nodes.
  • Leave the Include Implicitly Shared Nodes option cleared. This option enables you to include descendant nodes below shared limb nodes that are explicitly shared. Implicit shared nodes are exported only if they are not filtered out by another option. If you use a query filter in the export, you must explicitly include the shared nodes.
  • Select the Remove Duplicates Based on Key option to suppress the export of duplicate records based on the primary key columns that you specified on the Column Options tab of the Columns tab.

 

.

Click the Filter tab.

Use the Filter tab to define the filter criteria for the exported data by using a validation, query, or text file. Only nodes that fail the validation or that meet the query criteria are included in the export results. The text file must contain a list of node names (one per line) to be included or excluded from the export.

 

.

In this example, you create a new private query filter to find nodes that have parents defined as budget planning points in the hierarchy branch. Click the (...) button. .

Use the Query: New Query* dialog box to specify the query type and to enter filter parameters.

 

.

Click Add.

 

.

Perform the following actions:

  • In the Property drop-down list, select Plan Point?.
  • In the Operator drop-down list, select Above.
  • In the Value field, enter True.

 

.

In the Actions column, click the Update (...) button.

 

.

Click OK.

The filter criteria is displayed in the Description field.

 

.

Click the Columns tab.

Use the Columns tab to select properties for output columns and to configure column options. In this example, you leave the selected properties as is.

 

.

Click the Column Options tab.

Use the Columns Options tab to configure pivot, defaults, and primary keys for the exported columns. In this example, you configure the Name and Parent Node properties as primary keys.

 

.

In the [Core] Name row in the Actions column, click the Edit button.

 

.

In the [Core] Name row, select the Primary Key option.

 

.

In the [Core] Name row, click the Update button.

 

.

In the [Core] Parent Node row in the Actions column, click the Edit button.

 

.

In the [Core] Parent Node row, select the Primary Key option.

 

.

In the [Core] Parent Node row, click the Update button.

 

.

Click the Target tab.

Use the Target tab to configure where the data is to be exported and the format of the exported results. In this example, you export data to a server file named PlanningDetail.txt, which uses the DRM_Demo connection.


.

In the Device drop-down list, leave Server File selected to export data to a server file. Click the Test Connection... button to test the DRM_Demo connection to the server.

The connection succeeded; therefore, you can finish configuring the target.


.

In the Confirmation dialog box, click OK.


.

In the File Name field, enter a server file name for storing the export results. For example, enter PlanningDetail.txt.


.

Click the Run () button to process the export.

The export is successfully processed.


.

Open the PlanningDetail.txt server file in Notepad to view the export results .


Summary

In this tutorial, you have learned how to export hierarchy nodes.

Resources