Merging Changes Across Versions

<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 merge changes across versions.

With a blender, you can merge changes across versions. This type of blender is useful when you want to process incremental changes from an imported version into an existing production version. For example, you maintain a BalanceSheet hierarchy outside Data Relationship Management. The hierarchy is periodically imported into a new version in Data Relationship Management and then blended into the same hierarchy in an existing version to apply any updates since it was last imported.

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 merge changes across versions.

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.

Reviewing Source Hierarchies

In this topic, you review the hierarchies that you are going to blend.

.	Begin in the Browse task group. Use the Browse task group to manage versions and hierarchies.
.	Click the BalanceSheet - 2010 04 - Production tab to review the BalanceSheet hierarchy in the Production version. Some nodes were expanded for you.
.	Click the BalanceSheet - 2010 04 - External tab to review the BalanceSheet hierarchy in the 2010 04 - External version, which was imported from an external source. Some nodes were expanded for you. The nodes are similar in both BalanceSheet hierarchies, although their children and properties may have slight differences.

Begin in the Browse task group. Use the Browse task group to manage versions and hierarchies.

Click the BalanceSheet - 2010 04 - Production tab to review the BalanceSheet hierarchy in the Production version. Some nodes were expanded for you.

Click the BalanceSheet - 2010 04 - External tab to review the BalanceSheet hierarchy in the 2010 04 - External version, which was imported from an external source. Some nodes were expanded for you. The nodes are similar in both BalanceSheet hierarchies, although their children and properties may have slight differences.

Merging Changes

In this topic, you create a blender that processes changes from the imported BalanceSheet hierarchy into the production BalanceSheet hierarchy.

.	Right-click the Home tab.
.	Click Blend from the drop-down menu to 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 source and target versions for the blender. The target hierarchy receives values from the source. In this example, you later configure the Target tab to create a version for storing the blended result. Perform the following actions on the Source tab: In the Source Version drop-down list, select 2010 04 - External In the Target Version drop-down list, select 2010 04 - Production Clear the Blend All Hierarchies field because you want to define a hierarchy/top node set for the BalanceSheet hierarchies. Note: If you select the Blend All Hierarchies field, the Use Profile Defaults For All Hierarchy Sets field is automatically selected. Leave the Use Profile Defaults For All Hierarchy Sets field selected. Use this field to apply the profile default (filters and properties) to all hierarchy/top node sets. If you clear this field, you can later configure it for each hierarchy/top node set.
.	Click the New... button to add a hierarchy/top node set. Use the Add Blender Hier-Set dialog box to map a hierarchy/top node in the source to a hierarchy/top node in the target.
.	Perform the following actions on the Source tab: In the Hierarchy drop-down list, select BalanceSheet. Leave the BalanceSheet node selected as the source top node.
.	Click the Target tab.
.	Perform the following actions on the Target tab: In the Method drop-down list, select Selected. Use this list to indicate whether you want to specify or select a hierarchy and target top node. In the Hierarchy drop-down list, select BalanceSheet. In the Nodes section, select BalanceSheet as the target top node.
.	Click OK. The Source and Target columns display the hierarchy/top node set that you just configured.
.	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. Leave the Allow Hierarchy Creation option cleared. 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. This option enables the blender to promote a leaf node in the target version to a limb node. If a node in the source version has children, but its corresponding node in the target version is a leaf node, then this feature 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 Process Version Validation Assignments option cleared. This option 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 Profile Defaults sub-tab of 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. Leave the Process Removes option selected to enable the blender to remove nodes that exist only in the target hierarchy. In the Remove Mode drop-down list, leave the Remove option selected. Leave the Process Moves option selected to enable the blender to move nodes that have a different parent in the source version to that parent in the target version. Leave the Process Activations option selected to enable 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 Profile Defaults sub-tab of the Properties tab: In the Property Selection drop-down list, select All Excluding Val/Access. 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, leave Defined selected. 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 option enables the blender to blend locks for inherited property values in the source version into the target version.
.	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 04 - Production v2. Optional. In the Description field, enter a meaningful description of the target version. In the Max Iterations field enter 3—The Max Iterations field specifies the maximum number of attempts to reconcile the source and target versions. In this example, you specify three iterations because you are processing moves and removes. 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 BalanceSheet 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 BalanceSheet Blend.
.	Click the Run button to process the blender. The blender completed processing without any errors.

Verifying the Blender Results

In this topic, you verify the blender results.

.	Right-click the Home tab.
.	Click Browse to navigate to the Browse task group for viewing the blended results.
.	Click the 2010 04 - Production v2 version to view its hierarchies, which was created by the blender.
.	In the Hierarchies tab, double-click BalanceSheet to open the hierarchy. The hierarchy was expanded for you. The 211209 node originated from the 2010 04 - External version. The blender inserted it under the 211200 node. Target property values are overwritten with source property values for properties that are explicitly defined in the source version.

Summary

In this tutorial, you have learned how to merge changes across versions.

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