Blenders in DRM

You can blend elements of two versions. You can blend structural elements, such as hierarchies and nodes, and properties.

With Blenders, you can perform these actions:
l    Process adds, moves, or deletes to an existing hierarchy
l    Process activations and promotions (leaf to limb)
l    Act upon any combination of hierarchies
l    Create new hierarchies
l    Map top nodes from a source hierarchy to nodes in a target hierarch.

Blenders can be customized and saved by users with the roles: Application Administrator, Data Manager, and Data Creator.
Creating Blenders
When you create or open a blender, it is displayed on a named tab.
The blender wizard is used to define the parameters and criteria for the blender. The wizard content is organized across Source, Style, Filters, Properties, and Target tabs to guide input. Although the wizard tabs are ordered to gather input in a sequence, you can navigate between any tabs.
ä    To create a blender: 1    From the Data Relationship Management navigation bar, select Blend.
2    Click . 3    On the Source tab, select source and target versions for the blender. 4    Perform an action:
l
Select Blend all Hierarchies to blend all hierarchies in the selected versions.
Creating Blenders    91
5
6
Note:    If you select this option, the Use Profile Defaults For All Hierarchy Sets option is required.
l    Deselect Blend all Hierarchies, click New and select hierarchy and top node mappings to select hierarchy/top node pairs to blend.
These are mappings from the source to the target indicating which hierarchy top nodes in the target are to receive values from the source. Top nodes in the target can be created or mapped to existing top nodes, depending on the Blender settings.
Note:    You can select Use Profile Defaults For All Hierarchy Sets to use default values for all hierarchy/top node sets. You set the profile defaults for properties on the Properties tab. If you deselect this option, you have the option of choosing which hierarchies should use the defaults and which should not when you select hierarchy/top node pairs.
On the Style tab, do the following: l    Select from the following structure options:
m    Process Structure — To blend structural elements, such as hierarchies and nodes. m    Allow Hierarchy Creation — To create hierarchies in the target version that exist
only in the source version.
Note:    If this option is not selected and there are hierarchies that exist in the source but not in the target, then an error occurs.
m    Allow Leaf Promotion — to promote a node with children in the source to a limb in the target.
Note:    If a node in the source has children, but its corresponding node in the target is a leaf node (an outermost node with no children allowed), then this option enables the Blender to promote the node to limb status. The child nodes from the source are then added to the limb node in the target.
l    Select from the following property options:
m    Process Properties — To blend property values
m    Disable Realtime Validations — To turn off the real-time validations on the target version prior to blending.
m    Process Version Validation Assignments — To process version-level validation assignments from the source to the target
On the Filter tab, select from these options on the Profile Defaults tab or the Hierarchy Overrides tab.
Note:    If you selected Use Profile Defaults for All Hierarchy Sets in step 3, make selections on the Profile Defaults tab. If any hierarchy sets exist and any are set to NOT use defaults, then the Hierarchy Overrides tab is enabled. Provide overrides for each hierarchy set on this tab.
92
Blending Versions
l    Process Inserts - To insert any nodes existing only in the source hierarchy to the target hierarchy.
l    Process Removes - To remove any nodes existing only in the target hierarchy according to the setting in the Remove Mode list and the Remove Indicator list.
If you selected Process Removes, select one of the following Remove Modes: m    Remove - Node is immediately removed during blending m    Mark - Node is marked for later removal
When the Remove Mode is set to Mark, the Remove Indicator option designates which property contains the value showing that the node is flagged to be removed. The remove indicator property must be created as a local, Boolean property. For information on creating properties, see the Oracle Hyperion Data Relationship Management Administrator's Guide.
l    Process Moves - To move any node which has a different parent in the source to that parent in the target.
l    Process Activations - To process node activations (inactivate and reactivate) from the target to the source.
l    Process Hierarchy Validation Assignments - To process the hierarchy level validation assignments from the source to the target.
7    On the Properties tab, from Property Selection, select one of the following ways to blend properties: l    All Excluding Val/Access - All properties are blended; excludes properties used for node-
level validations and for node access group leaf and limb-level settings. l    None - No properties are blended. l    Selected - The selected properties are blended.
8    From Property Propagate Mode, select one of the following modes to determine how the property is populated in the target.
Note:    If you selected Use Profile Defaults for All Hierarchy Sets in step 3, make selections on the Profile Defaults tab. If you did not select to use profile defaults, make selections on the Hierarchy Overrides tab.
l    Force - The property is assigned for every node in the target, whether that property is defined at that node, is inherited, or derived.
l    Difference - Populates the property for any node where the value is different, regardless of how that property is populated in the target.
l    Defined - The property is blended only when it is specifically defined for the node in the source.
9    Optional: Select Propagate Property Locks if you want inheritance locks in the source to be blended to the target.
10 On the Target tab, select the Target version:
Creating Blenders    93
l    Use Selected Target - To blend changes into the selected target version. l    Copy to New Version - To blend changes into a copy of the selected target version.
Note:    If you select this option, you must specify a name and description for the new version.
11 Enter a value for Max Iterations.
Note:    This value determines the maximum number of attempts the Blender performs in reconciling the Source and Target versions. This prevents the Blender from running indefinitely in the case of irresolvable conflicts. The recommended value is 3.
12 Enter a value for Max Errors. Note:    This value sets the maximum number of errors that can occur during processing
before the Blender stops without completion.
13 Make selections for the following blender status properties options:
l    Clear Values - to set all Blender Status Property values to False during processing.
l    Populate Values - to set each Blender Status Property to True during processing.
l    Version Blended - The name of the property that will be set to TRUE if the version has been blended {Version Level Boolean Defined Property}
l    Node Moved - The name of the property that will be set to TRUE if the node was moved by the blend {Local Node Level Boolean Defined Property}
l    Node Created - The name of the property that will be set to TRUE if the node was created by the blend {Global Node Level Boolean Defined Property}
l    Local Node Changed - The name of the property that will be set to TRUE if the node had local properties changed by the blend {Local Node Level Boolean Defined Property}
l    Hierarchy Blended - The name of the property that will be set to TRUE if the hierarchy has been blended {Hierarchy Level Boolean Defined Property}
l    Global Node Changed - The name of the property that will be set to TRUE if the node had global properties changed by the blend {Global Node Level Boolean Defined Property}
l    Node Inserted - The name of the property that will be set to TRUE if the node was inserted by the blend {Local Node Level Boolean Defined Property}
l    Leaf Promoted - The name of the property that will be set to TRUE if the node was promoted from a leaf to a limb by the blend {Global Node Level Boolean Defined Property}
14 Do either or both of the following:
l
l
Click    to save the blender. Click    to run the blender.
94    Blending Versions
Running, Copying, and Deleting Blenders
You can run copy, and delete saved blenders. You must open a blender before you can run it. ä    To run a blender:
1    From the Data Relationship Management navigation bar, select Blend.
2    Select a blender and click.
3    Click the tabs to modify the blender parameters, and then click    to run the blender.

To copy a blender:
1    From the Data Relationship Management navigation bar, select Blend.
2    Select a blender.
3    From Blenders, select Copy.
4    Enter a new name and description for the blender.
5    From Object Access Level, select User, Standard, or System (depending on the role of the user) and click OK.

To delete a blender:
1    From the Data Relationship Management navigation bar, select Blend.
2    Select a blender.
3    From Blenders, select Delete.