Adding Different Hierarchies to the Same Version

<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 blend hierarchies from two different versions into a new version.

With a blender, you can add unrelated hierarchies from two different versions into a new version. For example, you blend two account hierarchies from version1 with two entity hierarchies from version2 to result in four hierarchies in version3. This type of blender is easy to configure and analyze because the nodes do not overlap between the hierarchies in the source and target versions.

For this type of blender, you configure the following blender wizard tabs in this manner:

Source—Select the hierarchies that you want to combine from the source version with the hierarchies in the target version. If you want to include all hierarchies from both versions, leave the Blend All Hierarchies option enabled.
Style—Enable the Allow Hierarchy Creation and Process Structure options. If you want to include property values from the source version, also enable the Process Properties option.
Filters—Enable the Process Inserts option to allow nodes to be added to the hierarchies that are created by the blender.
Properties—Choose the properties that you want to copy from the source version, if needed.
Target—Configure a new version to contain the hierarchies from the source and target versions.

In this tutorial, you add hierarchies from the Accounts version and the Entities version into a new version Production.

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.

Exploring Source Versions

In this topic, you explore the source versions.

.	Begin in the Browse task group. Use the Browse task group to manage versions and hierarchies.
.	View the hierarchies that you are going to blend. Begin by viewing hierarchies in the 2010 Accounts version. Click 2010 Accounts.
.	Expand the Account hierarchy group. The 2010 Accounts version consists of one hierarchy group (Account) that contains seven hierarchies.
.	View the hierarchies in the 2010 Entities version. Click 2010 Entities.
.	Expand the Entity hierarchy group. The 2010 Entities version consists of one hierarchy group (Entity) that contains three hierarchies. Note: These hierarchies are different than those in the 2010 Accounts hierarchy.

Blending Versions

In this topic, you create a blender that combines the hierarchies in the 2010 Accounts and 2010 Entities versions into a new version called 2010 06 - Production.

.	Navigate to the Blend task group. Use the Blend task group to create, copy, and delete blenders.
.	Click the New Blender button. Use the blender wizard to configure the source, style, filters, properties, and target for your blender. You begin on the Source tab.
.	Use the Source tab to select the source and target versions for the blender. You can blend all hierarchies from both versions or selected hierarchies from the source version. In this example, you blend all hierarchies from both versions. Perform the following actions on the Source tab: In the Source Version drop-down list, select 2010 Accounts. In the Target Version drop-down list, select 2010 Entities. Leave the Blend All Hierarchies option selected.
.	Click the Style tab. Use the Style tab to select structure and property options for your blender.
.	Perform the following actions on the Style tab: Select the Process Structure option to enable all structural actions on the Filters tab. Actions include inserts, removes, moves, activations, and hierarchy validation assignments. Select the Allow Hierarchy Creation option to create hierarchies in the target version that exist only in the source version. If you do not select this option and hierarchies exist in the source version but not in the target version, then an error occurs. Leave the Allow Leaf Promotion option cleared. If a node in the source version has children, but its corresponding node in the target version is a leaf node, then the Allow Leaf Promotion option enables the blender to promote the node to limb status. The child nodes from the source version are then added under the limb node in the target version. Select the Process Properties option to control whether property values are blended on the Properties tab. Leave the Disable Realtime Validations option cleared to display all real-time validations on the target version in the blender results. This feature is useful when you expect many invalid changes to occur and prefer to analyze those changes later on by using batch validations. Leave the Use the Process Version Validation Assignments option cleared. This feature enables the blender to process version-level validation assignments from the source version to the target version.
.	Click the Filters tab. Use the Filters tab to select processing options for the profile default. You can also specify hierarchy overrides, if needed.
.	Perform the following actions on the Filters tab: Leave the Process Inserts option selected to insert any nodes existing only in the source hierarchy into the target hierarchy. If a node being inserted does not exist in the target version, then it will be created by the blender. Clear the Process Removes option that enables the blender to remove nodes that exist only in the target hierarchy. If you select this option, you must select one of the following options for the remove mode: • Remove—removes the node during blending • Mark—marks the node for later removal. You also select a remove indicator property that flags the node for removal. Note: An administrator must create this local Boolean property beforehand. Clear the Process Moves option that enables the blender to move nodes that have a different parent in the source version to that parent in the target version. Clear the Process Activations option that enables the blender to process node activations (inactivate and reactivate) from the target version to the source version. Clear the Process Hierarchy Validation Assignments option that enables the blender to process the hierarchy-level validation assignments from the source version to the target version.
.	Click the Properties tab. Use the Properties tab to configure default properties to be blended for the blender profile. You can also configure hierarchy overrides, if necessary.
.	Perform the following actions on the Properties tab: In the Property Selection drop-down list, select Selected. Use the Property Selection list to specify whether you want to blend specific properties, no properties, or all properties (excluding properties used for node-level validations and for node access group assignments). In the Property Propagate Mode drop-down list, select Defined. Use the Property Propagate Mode field to specify how a property is populated in the target. You can select one of the following options, which are listed from most used to least used: • Defined—overwrites the target property value with the source property value for any node where the property is explicitly defined in the source version. • Difference—overwrites the target property value with the source property value for any node where the source and target property values are different, and regardless of how that property is populated in the target version. • Force—overwrites the target property value with the source property value for every node in the target, regardless if that property is defined for that node, is inherited, or is derived. Leave the Propagate Property Locks option cleared. This feature enables the blender to blend locks for inherited property values in the source version into the target version.
.	Click the Add button to select properties to be propagated.
.	In the Property drop-down list, select Description.
.	In the Action column, click the Update button.
.	Click the Target tab. Use the Target tab to define a new version that stores the blender result, set maximum iterations and maximum error values, and configure blender status properties.
.	Perform the following actions on the Target tab: In the Target Version drop-down list, select Copy to New Version to create a version to store the blended result. In the Name field, enter 2010 06 - Production. Optional. In the Description field, enter a meaningful description of the target version. Leave the Max Iterations field to its default value of 1—The Max Iterations field specifies the maximum number of attempts to reconcile the source and target versions. In this example, one iteration is sufficient because there is no overlap between the blended hierarchies. Conflicts that would require additional iterations are not possible. Leave the Max Errors field to its default value of 10—The Max Errors field sets the maximum number of errors that can occur during processing before the blender stops. Leave the Blender Status Properties to their default values—The Blender Status Properties section tracks node, hierarchy, and version changes during blending. For each action that you want to track, you must select a property to store a status value (True or False). Note: You must configure these properties before running the blender.
.	Click the Save As button.
.	In the Save Blender dialog box, perform the following actions: In the Name field, enter Accounts Entity Blend. Optional. In the Description field, enter a meaningful description of the new blender. In the Object Access Level drop-down list, leave User selected. The Object Access Level field assigns one of the following access levels: • User—Enables only you to run and edit the blender • Standard—Enables all users to run the blender, but only users with the Data Manager role can edit it
.	Click OK. The tab name is displayed as Accounts Entity Blend.
.	Click the Run button to process the blender. The blender completed processing without any errors.

Viewing the Blender Results

In this topic, you verify the target version.

.	Click the Home tab to navigate to the Blend task group. Your blender is listed in the Blend task group. From here, you can open, copy, or delete it.
.	Click Browse to navigate to the Browse task group for viewing the blended results.
.	Click the 2010 06 - Production version to view its hierarchies.
.	Expand the Account hierarchy group.
.	Expand the Entity hierarchy group. A total of ten hierarchies were copied to the 2010 06 - Production version.

Summary

In this tutorial, you have learned how to blend hierachies from two different versions into a new version.

Resources

Oracle EPM System, Fusion Edition 11.1.2.1 Documentation Library
To learn more about Data Relationship Management, refer to additional OBEs in the OLL Web site