A node is a point within a hierarchy. Every point in a hierarchy is a node. For example, within a hierarchy that represents an organizational structure, a node might represent a department or a cost center.
Within a version, a node may be a part of more than one hierarchy. A node can have many user- defined properties that store information about the node and control the use of the node within the information systems of an organization.
Caution!
Using commas in node names can cause difficulties when working with certain properties that are comma-delimited, such as Ancestor List, Child List and client- created node lists. In addition, using the characters defined in the system preferences for the shared node separator and the hierarchy separator can cause unpredictable behavior and should be avoided. If the query wildcard characters asterisk ( * ) and underscore ( _ ) are used in a node name they cannot be easily searched for unless a derived formula is used to search for them using the Pos function.
The following terms are used to define the position of a node and behavior of the node within a hierarchy:
About Nodes 13
Table 1
Node Terminology
l
l
Create a new node Insert an existing node not currently in the hierarchy - See
Term
Leaf
Limb
Child
Parent
Descendant
Ancestor
Sibling
Orphan
Definition
A node that cannot have children
A node that can have children
A node directly below another node (if B is directly below A, B is a child of A)
The node directly above another node (in the previous example, A is the parent of B)
A node below a specified node (including children and children of children)
All nodes between a node and the top of the hierarchy (including the parent, the parent of the parent, and so on)
All nodes that share a parent node in a hierarchy
A node not assigned to a hierarchy
Adding and Inserting Nodes
You can include a node in a hierarchy in two ways:
Caution!
Using commas in node names can cause difficulties when working with certain properties that are comma-delimited, such as Ancestor List, Child List and client- created node lists. In addition, using the characters defined in the system preferences for the shared node separator and the hierarchy separator can cause unpredictable behavior and should be avoided. If the query wildcard characters asterisk ( * ) and underscore ( _ ) are used in a node name they cannot be easily searched for unless a derived formula is used to search for them using the Pos function.
ä To create a node and add it to a hierarchy: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select New. 6 Optional: Select Leaf Node if the node is a leaf. 7 Enter a name and description for the node.
14 Working with Nodes
Note: If you are adding a node to a part of the hierarchy tree that has repeated node names, you can click ID to automatically generate a node name. See ID Function.
8 Select whether to add the node as a child or sibling of the selected node. 9 Click OK.
ä To insert an existing node into a hierarchy: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select Insert. 6 Select the location of the node:
l
l
Existing Hierarchy
Orphan Node List
7 Do one of the following:
l
If you selected Existing Hierarchy in step 6, do the following: a. Select a hierarchy. b. Select the node to insert by doing one of the following:
m
m
Enter text in Find and click to locate the node.
Note: You can use the asterisk ( * ) as a wildcard character.
Expanding the Nodes tree to locate the node.
8 Select whether to insert the node as a child or sibling of the selected node. 9 Click OK.
ID Function
The ID function enables you to automatically generate node names using sequential numerical IDs and node prefixes. For example, a set of nodes can be created where each of them have a name like Org000xxx, where:
l
l
Org is the node prefix and can be any desired character string. 000xxx is the sequential ID and increments by 1 starting at 1.
These system preferences must be enabled for the ID function to work:
l
l
AllowNextIDGeneration must be set to True. AllowNextIDKeyCreation determines the level of user that can create new ID keys.
Adding and Inserting Nodes 15
To use the Next ID function, type a prefix in the node name field and click ID.
l If the prefix already exists in the system, then an ID value is returned that is one greater than the last ID previously generated.
l If the prefix has not been used before, then an ID value of 1 (with the appropriate number of leading zeros) is returned.
The total length of the ID (excluding the prefix and including any leading zeros as necessary) is determined as follows:
l The hierarchy properties IDLengthLimbProp and IDLengthLeafProp can be set to point to node-level properties that specify the desired ID length for the specified node.
l If the IDLengthLimbProp and IDLengthLeafProp properties are not set, then the length of the next sequential ID is used without leading zeros.
Modeling a Node
You can create a node by modeling an existing node.
ä To create a node by modeling a node: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node to model. 5 On the Shortcuts menu, select Script and then select Model After.
The Source tab is populated with information from the node you selected.
6 On the Properties tab, from Copy Properties, select the properties to be copied from the node. l None - No properties are copied. l Defined - Only defined property values are copied. l Selected - Only the properties you select are copied.
Note: For Selected, click to display a property selector from which to select properties.
l All - all properties are copied. 7 Do the following:
l
Select the Global Properties tab to view the Global property values that will be included in the Action Script based on your selection in Step 4.
16 Working with Nodes
l
Select the Local Properties tab and select a hierarchy to view the local property values that will be included from each hierarchy based on your selection in Step 4. Make changes as necessary.
8 On the Target tab, do the following: l Select the target version for the new node. l Enter a name for the new node. l Enter a description for the new node.
9 Click Load. 10 When the load completes, review the script actions and parameter values. You can:
l Click to modify a row. l Select Script, then Substitute Versions to change a version. Select the version to be
replaced and the version to replace it with and click OK. l Double-click a column header to sort rows alphabetically.
l Click to filter one or more columns. 11 Select the check box in the Process column next to each row to be run.
Note: From the Script menu, use Select All to process all actions. You can select a subset of actions from a script and only process those actions.
12 Click to run the Action Script. The results of each script action are displayed in the Status and Result Value columns. The
script and the results can be saved to a file using the Download option on the Script menu.
Moving and Ordering Nodes
You can move a node within a hierarchy or to a different hierarchy:
l Moving a node within a hierarchy removes the node from its original parent and places it under the new parent.
l Moving a node to a different hierarchy is treated like a copy. The node is left unchanged in its original hierarchy. This function is identical to inserting an existing node.
ä To move a node: 1 Select the node to move. 2 Drag and drop the selected node to the new location. 3 If you moved the node under a different top node, select an action:
l
l
Put as Child - To insert the node as a child of the node. Put as Sibling or Reorder - To insert the node as a sibling.
Moving and Ordering Nodes 17
Relaxed Move Option
To facilitate a move that requires a node to be removed from an alternate hierarchy, you can use the Relaxed Move option. If the System Preference AllowRelaxedMove is set to True, the Relaxed Move is allowed. If the system preference is set to False or does not exist, then the normal integrity constraints are enforced.
When moving a node, the Relaxed Move enables the new parent in the main hierarchy to take precedence over any conflicting parental relationships for this node in other hierarchies.
Sorting Nodes
In Data Relationship Management, nodes are sorted according to the following default rules:
1. Limb nodes are sorted before leaf nodes. (This is optional and controlled by the SortLimbsFirst system preference.)
2. Nodes are sorted by name in ascending order.
Custom Sort Order
Nodes can also be sorted in any explicit custom sort order. The sort order can be defined by any property that has a property data type of Sort.
To sort a hierarchy according to the value of a node-level sort order property, the hierarchy- level property StandardHierSort must be set to point to the appropriate node-level property that contains the sort order.
A custom sort order can also be used that applies only to a specific Data Relationship Management user ID, enabling users to customize their display of Data Relationship Management data without impacting other users of the same hierarchy. This is controlled by the hierarchy-level property UserHierSort. If this property has been set to point to a node-level property that has a data type of Sort Order, then this sort order takes precedence over both the StandardHierSort property and the default sort order.
If there is no value assigned to the hierarchy-level property StandardHierSort nor to UserHierSort, then default sorting rules are used.
The value of a custom sort order property can be set in any of the following ways:
l Sort order values can be loaded into a node-level sort order property when data is initially imported into Data Relationship Management (see following for details.)
l Explicit values can be defined for the sort order property for any node.
l If a sort order property has been selected for a hierarchy’s StandardHierSort or UserHierSort properties, use the Take/Put options or drag and drop to custom order nodes within a hierarchy.
l A node-level sort order property might be defined as Derived, and so might be automatically populated with a sort order.
18 Working with Nodes
Node Deletion Methods
There are four methods of deleting nodes described in decreasing order of severity in the following table.
Table 2 Node Deletion Methods
Action
Delete
Remove
Annul
Inactivate
Result
Removes the node from all hierarchies and deletes the node from the version
Removes the node from the current hierarchy and any other hierarchies where it has the same parent. However, the node is not deleted from the version and is available for re-insertion.
Performs a Remove on the node in all hierarchies where it has the same parent, and also Deletes the node if it is then an orphan:
Note:
If the UseMerge system preference is enabled, you can select Delete & Merge, then select a node to use in place of the deleted node. If the ReqMerge system preference is enabled, then you must specify a merge node. If ReqMerge is not enabled, then a merge node is optional unless the node approved property is TRUE. The node approved property is set to TRUE when a version is finalized or when it is specifically set to TRUE by a user with appropriate access.
l
l
For example, if a node has the same parent in all hierarchies in which it exists, then an Annul will remove the node from all hierarchies and then delete it because it is an orphan.
If the node does not have the same parent in all hierarchies, Annul produces the same result as Remove.
Flags the node as inactive so that it can be filtered from an export.
Deleting Nodes Note: Only nodes without descendents can be deleted.
To delete multiple nodes from a hierarchy, use the Annul All Below command.
ä To delete a node: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select Delete.
Node Deletion Methods 19
6 Select Delete Node to confirm node deletion. When the version tree refreshes, the node is no longer displayed. Deleting a node removes it from all hierarchies and parents in the selected version.
Merging Nodes
When you delete or inactivate nodes, you can specify nodes for Data Relationship Management to use in place of the deleted or inactivated nodes. External transaction systems supported by Data Relationship Management may have transactions that refer to a deleted node. By keeping a merge list, Data Relationship Management is able to provide appropriate node mappings that allow data to a rolled to a valid node.
Note: The merge options (Delete & Merge and Inactivate & Merge) are available only if the UseMerge system preference is enabled.
Removing Nodes
Removing a node removes it only from the current parent. If the node has other parents, those relationships are not affected. If the node has no other parents, it becomes an orphan node.
ä To remove a node: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select Remove. 6 Select Remove Node to confirm node removal.
When the version tree refreshes, the node is no longer displayed. If the node had no other parents, it becomes an orphan node.
Annulling Nodes
When you annul a node, the node is removed from the parent, and, if it becomes an orphan, the orphan node is deleted. For example, if a node has only one parent, then Annul results in the node being deleted.
You can use the Annul All Below command to annul multiple nodes.
ä
1
To annul a node:
From Browse, select a version.
20
Working with Nodes
2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select an action:
l
l
Annul - To annul the selected node Annul All Below - To annul all nodes below the selected node
Note: This option is available only if you select a limb node. 6 Select Annul Node.
When the version tree refreshes, the node is no longer displayed. You can use the Annul All Below command to annul multiple nodes.
Inactivating Nodes
You can inactivate leaf nodes or limb nodes that have no active children.
The Inactivate and InactiveChanges system preferences control which users can inactivate a node and make changes to inactive nodes.
ä To inactivate a node: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select Inactivate.
Note: If the UseMerge system preference is enabled, you can select Inactivate & Merge, then select a node to use in place of the inactivated node.
When the version tree refreshes, the node is grayed out and displays an inactive status icon.
Reactivating Nodes
ä To reactivate a node: 1 From Browse, select a version.
Node Deletion Methods 21
2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select an inactive node. 5 From Nodes, select Reactivate.
When the version tree refreshes, the node is displayed.
Orphan Nodes
An orphan node is defined as a node that exists in a version but is not assigned to a hierarchy within the version. Orphans may exist pending a cleanup to completely remove them, or they may be awaiting re-allocation to hierarchies in the version.
It is possible for an orphan node to have descendants that are not orphans. To avoid this, review the list of orphan nodes regularly.
Viewing Orphan Nodes
ä To view orphan nodes: 1 Select the Orphans tab.
For each orphan node, the number of descendants is displayed.
2 Select a node. 3 Perform an action:
l Select Related and then Descendants or Children to view a node's relationships. l Select Node and then Properties to view a node's properties.
l Click to search for an orphan node by name, description, or number of descendants.
l Select Node and then Take/Copy to copy the selected node to the clipboard.
l Select Download and then choose a format in which to download the list of orphan nodes.
Deleting Orphan Nodes
You can delete or destroy orphan nodes. If you select destroy, the node is deleted immediately regardless of any merge requirements.
Note: Nodes with children can only be removed, not deleted.
22 Working with Nodes
ä To delete orphan nodes: 1 Select the Orphans tab. 2 Select one or more nodes. 3 From Node, select Delete or Destroy.
Note: If the UseMerge system preference is enabled, you can select Delete & Merge, then select a node to use in place of the deleted node.
4 Confirm the Delete or Destroy command. When the orphan list refreshes, the node is no longer displayed.
Finding Nodes
You can search for nodes within a hierarchy or a version.
ä To find a node in a version: 1 From Browse, select a version. 2 Select Find Nodes.
3 Click and select By Name or By Description. 4 Enter text for which to search.
Note: You can use the asterisk ( * ) as a wildcard character.
ä To find a node in a hierarchy: 1 From Browse, select a version. 2 Select a hierarchy, then select Hierarchies, then Open. 3 Select Find Nodes.
4 Click and select By Name or By Description. 5 Enter text for which to search.
Note: You can use the asterisk ( * ) as a wildcard character.
Node Security
You can be assigned different levels of access to nodes within and across hierarchies. The Limb and Leaf Access properties for a node indicate your level of access. Node security settings can only be assigned by a Data Relationship Management user with administrative privileges.
Finding Nodes 23
Using Shared Nodes
Shared nodes are multiple instances of a node within the same hierarchy. Explicitly shared nodes, created during manual maintenance and import processes, share global property values with the primary node. The global properties for shared nodes automatically reference the values of the primary node and can only be changed at the primary node. Local properties can be specific to each shared node.
You can: l Automate the alternate naming of the shared nodes
l Create system-level properties that map shared nodes l Display the structure below a shared node l Move between shared nodes and the primary node l Remove and delete primary shared nodes
l Rename the primary shared node (thus renaming all the shared nodes) l Find and display a shared node list to be used for navigation and analysis purposes
Shared Node Properties
The following read-only, node properties are created automatically when a node is shared and provide information about primary and shared nodes
Note: The Shared Info property category must be manually assigned to users in order to see the shared node properties.
Property
Primary Node
Shared Node
Primary Node
Primary Node
Primary Node
Primary Node
Shared Map
Name
Has Descendants
Descendants
Ancestors
Description
Indicates whether a node has shared nodes that point to it
Indicates whether the node is a shared node
The primary name portion of the shared node name. For non-shared nodes, this property returns the node name in its entirety.
Indicates whether the primary node has structure below it. Only populated on shared nodes.
List of descendants of the primary node. Only populated on shared nodes where the primary node has structure below it.
List of ancestors of the primary node. Only populated on shared nodes.
Associated nodes property that maps the shared and primary nodes. This property is populated for shared and primary nodes.
Indicates whether the shared node points to a primary node that does not exist
Indicates whether the primary node is not in the same hierarchy
Missing Primary Node
Primary Not in Hierarchy
24 Working with Nodes
Enabling Shared Nodes
To use shared nodes in an application, you must enable the SharedNodeMaintenanceEnabled system preference. For any hierarchy in which you want to share nodes, you must enable the EnableSharedNodes hierarchy property. These settings are disabled by default.
Note: If shared nodes are enabled, the default shared node system preferences (delimiter, unique string, zero-pad length) should not be changed.
For information on configuring system preferences, see the Oracle Hyperion Data Relationship Management Administrator's Guide.
Adding and Inserting Shared Nodes
You can use the add or insert menu options to create a shared node. You can create a Shared Node by doing a Take/Put across Hierarchies, when the Node already exists in the target Hierarchy. You can accomplish the same thing by performing a drag/drop across two Hierarchies in a side-by-side Compare result.
Note: Before creating a shared node, make sure you have completed Enabling Shared Nodes.
ä To add a shared node: 1 Select the node where you want to insert a shared node. 2 From Nodes, select Add. 3 If the shared node is a leaf, select Leaf Node. 4 Enter the name of the existing node that you want to add. 5 Select If Node already exists, Insert the Node. 6 For Add As, select Child or Sibling. 7 Click OK.
ä To insert a shared node: 1 Select the node where you want to insert a shared node. 2 From Nodes, select Insert. 3 For Insert From, make sure that Existing Hierarchy is selected. 4 Select a hierarchy. 5 From the Nodes list, select the node to share. 6 For Insert As, select Child or Sibling. 7 Click OK.
Using Shared Nodes 25
In this example, node ABC is a primary node under Node1 and a shared node under Node2.
Removing and Deleting Shared Nodes
When you remove a shared node, the system removes the shared node only and the primary node remains. If the primary node is removed and a shared node also exists, the shared node is removed and the primary is moved to the parent of the shared node that was removed. If multiple shared nodes exist, one of the shared nodes becomes the primary node.
When you delete a shared node, the system deletes the shared node and all of its shared nodes.
ä To remove or delete a shared node: 1 Select a shared node. 2 From Nodes select Delete or Remove. 3 Select Delete Node or Remove Node.
When the hierarchy tree refreshes, the shared nodes are no longer displayed.
Renaming Shared Nodes
When you rename a primary node, the system renames the primary node and the shared nodes. Only the primary node can be renamed. The secondary shared nodes cannot be renamed.
ä To rename a shared node: 1 Select the primary node. 2 In the property editor, select the Name value field. 3 Change the name and click Save.
When the hierarchy refreshes, the primary node name and the shared node names are updated with the new name.
Converting a Shared Node into a Primary Node
ä To convert a shared node to a primary node: 1 Select the shared node. 2 From Nodes, select Convert to Primary.
26 Working with Nodes
ä
1 2
To display shared nodes:
Select a node. From Related, select Shared Nodes. Primary and shared nodes are displayed on the Relationships tab.
Within a version, a node may be a part of more than one hierarchy. A node can have many user- defined properties that store information about the node and control the use of the node within the information systems of an organization.
Caution!
Using commas in node names can cause difficulties when working with certain properties that are comma-delimited, such as Ancestor List, Child List and client- created node lists. In addition, using the characters defined in the system preferences for the shared node separator and the hierarchy separator can cause unpredictable behavior and should be avoided. If the query wildcard characters asterisk ( * ) and underscore ( _ ) are used in a node name they cannot be easily searched for unless a derived formula is used to search for them using the Pos function.
The following terms are used to define the position of a node and behavior of the node within a hierarchy:
About Nodes 13
Table 1
Node Terminology
l
l
Create a new node Insert an existing node not currently in the hierarchy - See
Term
Leaf
Limb
Child
Parent
Descendant
Ancestor
Sibling
Orphan
Definition
A node that cannot have children
A node that can have children
A node directly below another node (if B is directly below A, B is a child of A)
The node directly above another node (in the previous example, A is the parent of B)
A node below a specified node (including children and children of children)
All nodes between a node and the top of the hierarchy (including the parent, the parent of the parent, and so on)
All nodes that share a parent node in a hierarchy
A node not assigned to a hierarchy
Adding and Inserting Nodes
You can include a node in a hierarchy in two ways:
Caution!
Using commas in node names can cause difficulties when working with certain properties that are comma-delimited, such as Ancestor List, Child List and client- created node lists. In addition, using the characters defined in the system preferences for the shared node separator and the hierarchy separator can cause unpredictable behavior and should be avoided. If the query wildcard characters asterisk ( * ) and underscore ( _ ) are used in a node name they cannot be easily searched for unless a derived formula is used to search for them using the Pos function.
ä To create a node and add it to a hierarchy: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select New. 6 Optional: Select Leaf Node if the node is a leaf. 7 Enter a name and description for the node.
14 Working with Nodes
Note: If you are adding a node to a part of the hierarchy tree that has repeated node names, you can click ID to automatically generate a node name. See ID Function.
8 Select whether to add the node as a child or sibling of the selected node. 9 Click OK.
ä To insert an existing node into a hierarchy: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select Insert. 6 Select the location of the node:
l
l
Existing Hierarchy
Orphan Node List
7 Do one of the following:
l
If you selected Existing Hierarchy in step 6, do the following: a. Select a hierarchy. b. Select the node to insert by doing one of the following:
m
m
Enter text in Find and click to locate the node.
Note: You can use the asterisk ( * ) as a wildcard character.
Expanding the Nodes tree to locate the node.
8 Select whether to insert the node as a child or sibling of the selected node. 9 Click OK.
ID Function
The ID function enables you to automatically generate node names using sequential numerical IDs and node prefixes. For example, a set of nodes can be created where each of them have a name like Org000xxx, where:
l
l
Org is the node prefix and can be any desired character string. 000xxx is the sequential ID and increments by 1 starting at 1.
These system preferences must be enabled for the ID function to work:
l
l
AllowNextIDGeneration must be set to True. AllowNextIDKeyCreation determines the level of user that can create new ID keys.
Adding and Inserting Nodes 15
To use the Next ID function, type a prefix in the node name field and click ID.
l If the prefix already exists in the system, then an ID value is returned that is one greater than the last ID previously generated.
l If the prefix has not been used before, then an ID value of 1 (with the appropriate number of leading zeros) is returned.
The total length of the ID (excluding the prefix and including any leading zeros as necessary) is determined as follows:
l The hierarchy properties IDLengthLimbProp and IDLengthLeafProp can be set to point to node-level properties that specify the desired ID length for the specified node.
l If the IDLengthLimbProp and IDLengthLeafProp properties are not set, then the length of the next sequential ID is used without leading zeros.
Modeling a Node
You can create a node by modeling an existing node.
ä To create a node by modeling a node: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node to model. 5 On the Shortcuts menu, select Script and then select Model After.
The Source tab is populated with information from the node you selected.
6 On the Properties tab, from Copy Properties, select the properties to be copied from the node. l None - No properties are copied. l Defined - Only defined property values are copied. l Selected - Only the properties you select are copied.
Note: For Selected, click to display a property selector from which to select properties.
l All - all properties are copied. 7 Do the following:
l
Select the Global Properties tab to view the Global property values that will be included in the Action Script based on your selection in Step 4.
16 Working with Nodes
l
Select the Local Properties tab and select a hierarchy to view the local property values that will be included from each hierarchy based on your selection in Step 4. Make changes as necessary.
8 On the Target tab, do the following: l Select the target version for the new node. l Enter a name for the new node. l Enter a description for the new node.
9 Click Load. 10 When the load completes, review the script actions and parameter values. You can:
l Click to modify a row. l Select Script, then Substitute Versions to change a version. Select the version to be
replaced and the version to replace it with and click OK. l Double-click a column header to sort rows alphabetically.
l Click to filter one or more columns. 11 Select the check box in the Process column next to each row to be run.
Note: From the Script menu, use Select All to process all actions. You can select a subset of actions from a script and only process those actions.
12 Click to run the Action Script. The results of each script action are displayed in the Status and Result Value columns. The
script and the results can be saved to a file using the Download option on the Script menu.
Moving and Ordering Nodes
You can move a node within a hierarchy or to a different hierarchy:
l Moving a node within a hierarchy removes the node from its original parent and places it under the new parent.
l Moving a node to a different hierarchy is treated like a copy. The node is left unchanged in its original hierarchy. This function is identical to inserting an existing node.
ä To move a node: 1 Select the node to move. 2 Drag and drop the selected node to the new location. 3 If you moved the node under a different top node, select an action:
l
l
Put as Child - To insert the node as a child of the node. Put as Sibling or Reorder - To insert the node as a sibling.
Moving and Ordering Nodes 17
Relaxed Move Option
To facilitate a move that requires a node to be removed from an alternate hierarchy, you can use the Relaxed Move option. If the System Preference AllowRelaxedMove is set to True, the Relaxed Move is allowed. If the system preference is set to False or does not exist, then the normal integrity constraints are enforced.
When moving a node, the Relaxed Move enables the new parent in the main hierarchy to take precedence over any conflicting parental relationships for this node in other hierarchies.
Sorting Nodes
In Data Relationship Management, nodes are sorted according to the following default rules:
1. Limb nodes are sorted before leaf nodes. (This is optional and controlled by the SortLimbsFirst system preference.)
2. Nodes are sorted by name in ascending order.
Custom Sort Order
Nodes can also be sorted in any explicit custom sort order. The sort order can be defined by any property that has a property data type of Sort.
To sort a hierarchy according to the value of a node-level sort order property, the hierarchy- level property StandardHierSort must be set to point to the appropriate node-level property that contains the sort order.
A custom sort order can also be used that applies only to a specific Data Relationship Management user ID, enabling users to customize their display of Data Relationship Management data without impacting other users of the same hierarchy. This is controlled by the hierarchy-level property UserHierSort. If this property has been set to point to a node-level property that has a data type of Sort Order, then this sort order takes precedence over both the StandardHierSort property and the default sort order.
If there is no value assigned to the hierarchy-level property StandardHierSort nor to UserHierSort, then default sorting rules are used.
The value of a custom sort order property can be set in any of the following ways:
l Sort order values can be loaded into a node-level sort order property when data is initially imported into Data Relationship Management (see following for details.)
l Explicit values can be defined for the sort order property for any node.
l If a sort order property has been selected for a hierarchy’s StandardHierSort or UserHierSort properties, use the Take/Put options or drag and drop to custom order nodes within a hierarchy.
l A node-level sort order property might be defined as Derived, and so might be automatically populated with a sort order.
18 Working with Nodes
Node Deletion Methods
There are four methods of deleting nodes described in decreasing order of severity in the following table.
Table 2 Node Deletion Methods
Action
Delete
Remove
Annul
Inactivate
Result
Removes the node from all hierarchies and deletes the node from the version
Removes the node from the current hierarchy and any other hierarchies where it has the same parent. However, the node is not deleted from the version and is available for re-insertion.
Performs a Remove on the node in all hierarchies where it has the same parent, and also Deletes the node if it is then an orphan:
Note:
If the UseMerge system preference is enabled, you can select Delete & Merge, then select a node to use in place of the deleted node. If the ReqMerge system preference is enabled, then you must specify a merge node. If ReqMerge is not enabled, then a merge node is optional unless the node approved property is TRUE. The node approved property is set to TRUE when a version is finalized or when it is specifically set to TRUE by a user with appropriate access.
l
l
For example, if a node has the same parent in all hierarchies in which it exists, then an Annul will remove the node from all hierarchies and then delete it because it is an orphan.
If the node does not have the same parent in all hierarchies, Annul produces the same result as Remove.
Flags the node as inactive so that it can be filtered from an export.
Deleting Nodes Note: Only nodes without descendents can be deleted.
To delete multiple nodes from a hierarchy, use the Annul All Below command.
ä To delete a node: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select Delete.
Node Deletion Methods 19
6 Select Delete Node to confirm node deletion. When the version tree refreshes, the node is no longer displayed. Deleting a node removes it from all hierarchies and parents in the selected version.
Merging Nodes
When you delete or inactivate nodes, you can specify nodes for Data Relationship Management to use in place of the deleted or inactivated nodes. External transaction systems supported by Data Relationship Management may have transactions that refer to a deleted node. By keeping a merge list, Data Relationship Management is able to provide appropriate node mappings that allow data to a rolled to a valid node.
Note: The merge options (Delete & Merge and Inactivate & Merge) are available only if the UseMerge system preference is enabled.
Removing Nodes
Removing a node removes it only from the current parent. If the node has other parents, those relationships are not affected. If the node has no other parents, it becomes an orphan node.
ä To remove a node: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select Remove. 6 Select Remove Node to confirm node removal.
When the version tree refreshes, the node is no longer displayed. If the node had no other parents, it becomes an orphan node.
Annulling Nodes
When you annul a node, the node is removed from the parent, and, if it becomes an orphan, the orphan node is deleted. For example, if a node has only one parent, then Annul results in the node being deleted.
You can use the Annul All Below command to annul multiple nodes.
ä
1
To annul a node:
From Browse, select a version.
20
Working with Nodes
2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select an action:
l
l
Annul - To annul the selected node Annul All Below - To annul all nodes below the selected node
Note: This option is available only if you select a limb node. 6 Select Annul Node.
When the version tree refreshes, the node is no longer displayed. You can use the Annul All Below command to annul multiple nodes.
Inactivating Nodes
You can inactivate leaf nodes or limb nodes that have no active children.
The Inactivate and InactiveChanges system preferences control which users can inactivate a node and make changes to inactive nodes.
ä To inactivate a node: 1 From Browse, select a version. 2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select a node. 5 From Nodes, select Inactivate.
Note: If the UseMerge system preference is enabled, you can select Inactivate & Merge, then select a node to use in place of the inactivated node.
When the version tree refreshes, the node is grayed out and displays an inactive status icon.
Reactivating Nodes
ä To reactivate a node: 1 From Browse, select a version.
Node Deletion Methods 21
2 Select a hierarchy. 3 From Hierarchies, select Open.
The top node of the hierarchy is displayed in a node tree.
4 Select an inactive node. 5 From Nodes, select Reactivate.
When the version tree refreshes, the node is displayed.
Orphan Nodes
An orphan node is defined as a node that exists in a version but is not assigned to a hierarchy within the version. Orphans may exist pending a cleanup to completely remove them, or they may be awaiting re-allocation to hierarchies in the version.
It is possible for an orphan node to have descendants that are not orphans. To avoid this, review the list of orphan nodes regularly.
Viewing Orphan Nodes
ä To view orphan nodes: 1 Select the Orphans tab.
For each orphan node, the number of descendants is displayed.
2 Select a node. 3 Perform an action:
l Select Related and then Descendants or Children to view a node's relationships. l Select Node and then Properties to view a node's properties.
l Click to search for an orphan node by name, description, or number of descendants.
l Select Node and then Take/Copy to copy the selected node to the clipboard.
l Select Download and then choose a format in which to download the list of orphan nodes.
Deleting Orphan Nodes
You can delete or destroy orphan nodes. If you select destroy, the node is deleted immediately regardless of any merge requirements.
Note: Nodes with children can only be removed, not deleted.
22 Working with Nodes
ä To delete orphan nodes: 1 Select the Orphans tab. 2 Select one or more nodes. 3 From Node, select Delete or Destroy.
Note: If the UseMerge system preference is enabled, you can select Delete & Merge, then select a node to use in place of the deleted node.
4 Confirm the Delete or Destroy command. When the orphan list refreshes, the node is no longer displayed.
Finding Nodes
You can search for nodes within a hierarchy or a version.
ä To find a node in a version: 1 From Browse, select a version. 2 Select Find Nodes.
3 Click and select By Name or By Description. 4 Enter text for which to search.
Note: You can use the asterisk ( * ) as a wildcard character.
ä To find a node in a hierarchy: 1 From Browse, select a version. 2 Select a hierarchy, then select Hierarchies, then Open. 3 Select Find Nodes.
4 Click and select By Name or By Description. 5 Enter text for which to search.
Note: You can use the asterisk ( * ) as a wildcard character.
Node Security
You can be assigned different levels of access to nodes within and across hierarchies. The Limb and Leaf Access properties for a node indicate your level of access. Node security settings can only be assigned by a Data Relationship Management user with administrative privileges.
Finding Nodes 23
Using Shared Nodes
Shared nodes are multiple instances of a node within the same hierarchy. Explicitly shared nodes, created during manual maintenance and import processes, share global property values with the primary node. The global properties for shared nodes automatically reference the values of the primary node and can only be changed at the primary node. Local properties can be specific to each shared node.
You can: l Automate the alternate naming of the shared nodes
l Create system-level properties that map shared nodes l Display the structure below a shared node l Move between shared nodes and the primary node l Remove and delete primary shared nodes
l Rename the primary shared node (thus renaming all the shared nodes) l Find and display a shared node list to be used for navigation and analysis purposes
Shared Node Properties
The following read-only, node properties are created automatically when a node is shared and provide information about primary and shared nodes
Note: The Shared Info property category must be manually assigned to users in order to see the shared node properties.
Property
Primary Node
Shared Node
Primary Node
Primary Node
Primary Node
Primary Node
Shared Map
Name
Has Descendants
Descendants
Ancestors
Description
Indicates whether a node has shared nodes that point to it
Indicates whether the node is a shared node
The primary name portion of the shared node name. For non-shared nodes, this property returns the node name in its entirety.
Indicates whether the primary node has structure below it. Only populated on shared nodes.
List of descendants of the primary node. Only populated on shared nodes where the primary node has structure below it.
List of ancestors of the primary node. Only populated on shared nodes.
Associated nodes property that maps the shared and primary nodes. This property is populated for shared and primary nodes.
Indicates whether the shared node points to a primary node that does not exist
Indicates whether the primary node is not in the same hierarchy
Missing Primary Node
Primary Not in Hierarchy
24 Working with Nodes
Enabling Shared Nodes
To use shared nodes in an application, you must enable the SharedNodeMaintenanceEnabled system preference. For any hierarchy in which you want to share nodes, you must enable the EnableSharedNodes hierarchy property. These settings are disabled by default.
Note: If shared nodes are enabled, the default shared node system preferences (delimiter, unique string, zero-pad length) should not be changed.
For information on configuring system preferences, see the Oracle Hyperion Data Relationship Management Administrator's Guide.
Adding and Inserting Shared Nodes
You can use the add or insert menu options to create a shared node. You can create a Shared Node by doing a Take/Put across Hierarchies, when the Node already exists in the target Hierarchy. You can accomplish the same thing by performing a drag/drop across two Hierarchies in a side-by-side Compare result.
Note: Before creating a shared node, make sure you have completed Enabling Shared Nodes.
ä To add a shared node: 1 Select the node where you want to insert a shared node. 2 From Nodes, select Add. 3 If the shared node is a leaf, select Leaf Node. 4 Enter the name of the existing node that you want to add. 5 Select If Node already exists, Insert the Node. 6 For Add As, select Child or Sibling. 7 Click OK.
ä To insert a shared node: 1 Select the node where you want to insert a shared node. 2 From Nodes, select Insert. 3 For Insert From, make sure that Existing Hierarchy is selected. 4 Select a hierarchy. 5 From the Nodes list, select the node to share. 6 For Insert As, select Child or Sibling. 7 Click OK.
Using Shared Nodes 25
In this example, node ABC is a primary node under Node1 and a shared node under Node2.
Removing and Deleting Shared Nodes
When you remove a shared node, the system removes the shared node only and the primary node remains. If the primary node is removed and a shared node also exists, the shared node is removed and the primary is moved to the parent of the shared node that was removed. If multiple shared nodes exist, one of the shared nodes becomes the primary node.
When you delete a shared node, the system deletes the shared node and all of its shared nodes.
ä To remove or delete a shared node: 1 Select a shared node. 2 From Nodes select Delete or Remove. 3 Select Delete Node or Remove Node.
When the hierarchy tree refreshes, the shared nodes are no longer displayed.
Renaming Shared Nodes
When you rename a primary node, the system renames the primary node and the shared nodes. Only the primary node can be renamed. The secondary shared nodes cannot be renamed.
ä To rename a shared node: 1 Select the primary node. 2 In the property editor, select the Name value field. 3 Change the name and click Save.
When the hierarchy refreshes, the primary node name and the shared node names are updated with the new name.
Converting a Shared Node into a Primary Node
ä To convert a shared node to a primary node: 1 Select the shared node. 2 From Nodes, select Convert to Primary.
26 Working with Nodes
ä
1 2
To display shared nodes:
Select a node. From Related, select Shared Nodes. Primary and shared nodes are displayed on the Relationships tab.
No comments:
Post a Comment