Performance Management Architect exports output hierarchies, nodes, and properties from Data Relationship Management in an import format for Performance Management Architect. The output can be shared with and deployed to multiple EPM applications, such as Oracle Hyperion Financial Management and Oracle Hyperion Planning. Performance Management Architect exports may be run from within Data Relationship Management or from an Performance Management Architect import profile.
For more information on running these exports from Oracle Hyperion EPM Architect import profiles, see the Oracle Hyperion Enterprise Performance Management Architect Administrator's Guide.
To create an EPM Architect export:
On the Source tab, do the following:
Select a version or version variable.
Select a target application type:
Consolidation
Planning
Essbase (ASO)
Essbase (BSO)
Shared Library
Select a dimension property. This is a property with data type Hierarchy Group, used to determine the dimensions and hierarchies being exported.
Select a dimension type property. This is a hierarchy-level lookup property used to determine the dimension type for each dimension being exported.
On the Style tab, select an option:
Include Inactive Nodes — Select to include inactive nodes.
Include Implicitly Shared Nodes — Select to include descendant nodes below shared limb nodes that are explicitly shared. Implicit shared nodes are exported only if not filtered out by another option such as top node selection or a query filter. The structure of implicitly shared nodes below a shared parent node is reflected in the ancestor section of the hierarchy export.
If a query filter is used in the export, the administrator must explicitly include the shared nodes. For example, the filter (#Children=0) must be changed to ((#Children=0 OR (Shared Node Flag = True)).
For the implicitly shared node, the Parent properties reflect the values of the actual node (the primary node). For example, if your export includes the Parent Node property for an implicitly shared node, it will show the parent as the primary node.
In the Batch Validations section, select the type of validations to run.
Note:
Batch validations are performed only for the hierarchies and nodes included in the export. Validations are run before the export. If errors occur, the export stops.
None — No validations run.
Assigned — All validations assigned to the version, hierarchies, and nodes for the export run.
Selected — Click
to select validations to run.
Optional: On the Filter tab, select a query to apply to the export or, to define a query, click
.Note:
The inclusion filter determines the set of nodes from each hierarchy to be compared.
On the Columns tab, select the Parent Key Property and Member Key Property (the Data Relationship Management property for the node when determining duplicates).
To save the export, click
.You are prompted to define a name, description, and an object access group for the export. Select a custom group or one of the following:
User — Personal objects that are only available to an individual user to view and run.
Standard — Public objects that are available to all users to view and run. Only Data Manager users can create and modify standard exports.
System — Restricted objects that are only available to Application Administrator role users to view and run.
To validate the export, click
.You can copy validation errors to the clipboard.
To run the export, click
.If you selected to run validations on the Style tab, clicking
performs the validations. Then, if no errors occur, the export runs. If validation errors occur, then the export stops, and an error is displayed. Click for a list of validation errors.
.