dbNavigate Hierarchy Relationship Management

dbNavigate Hierarchy Relationship Management

Table of Contents

I.Launching DRM Application21.Login to DRM Application22.View Alternate Hierarchies5II.Process of Defining the Alternate Hierarchies in DRM71.Definitions and guidelines72.Building Alternate Hierarchies9III.FAQs23

I. Launching DRM Application1. Login to DRM Application

a. Launch the DRM Client from All Programs-> Oracle EPM System-> Data Relationship Management-> Data Relationship Management

b. You would receive the login popup as below.

c. Click on the button circled in Blue above, to open below popup box

d. Enter your username and DRM server details as above. You may click on Test button to verify the access, as shown below

e. Enter the password to get into DRM as below

f. You would be able to see the DRM Versions of dbNavigate as shown below.

2. View Alternate Hierarchies a. Open the Alternate Hierarchy that you are trying to add/edit the nodes in it as shown below

b. Below is how Alternate Hierarchy looks like once it is opened.

c. You can change the view as shown below to see the node, along with its description.

II. Process of Defining the Alternate Hierarchies in DRM

1. Definitions and guidelines

Alternate Hierarchy should contain the Alternate nodes (User defined Nodes) suffixed with _A, having children either Alternate nodes, or Standard hierarchy Nodes.We use below operations in DRM while working on Alternate Hierarchies.Add: This operation is used to Add a new Node to Alternate Hierarchy which never exists either in Standard or in Alternate Hierarchies Delete: Delete Operation should be used in conjunction with Add Operation. If user is Added an node, and later wanted to delete it, then Delete operation should be used. To delete any node, first we need to either delete or remove all of its descendents. Delete operation would delete the node present across all hierarchies within the Alternate Version.Strictly use for alternate nodesInsert: Insert Operation should be used for the nodes which are already exists part of Standard Hierarchy, and now being added to Alternate Hierarchy to achieve different rollup. Remove: Remove operation on a node would remove the node from the current hierarchy. Remove operation should be used in conjunction with Insert operation, to revert the insert operation. Remove would remove the node from the Alternate Hierarchy.

When to Use Add Operation:As Alternate nodes are user defined, they would not exist in Standard Hierarchies, thus we should perform Add operation for adding the node to the alternate hierarchy. When to use Delete OperationIf an alternate node added earlier, no longer required now, can be deleted. When to use Insert OperationA Standard Node exists in Standard Hierarchy, which is going to be part of Alternate Hierarchy, need to inserted. DRM throws a warning as shown below, if user tries to Add instead of Insert for Standard Nodes

When to User Remove Operation

Remove operation should be used for inserted node in Alternate Hierarchy to be deleted. When not to Use Delete OperationDelete Operation should not be used for removing the standard nodes in Alternate Hierarchies. DRM throws below warning saying, delete a node from alternate hierarchy will delete from Standard Hierarchy also.

2. Building Alternate Hierarchies

A. Add an Alternate Node in Alternate Hierarchy 1. Locate the node to which you want to add the new Alternate node, as child. You can either locate manually by drilling down the Hierarchy, or use Find as show below

If you want to add the new Alternate node at top level, right click on top node (root node) Ex: Accounts Alternate in top node in Accounts Alternate Hierarchy You can Use Edit Button on Menu Bar to Add an Alternate node, or right click on located node, as shown below.

2. Enter the Name of the Alternate Node, Description. Select whether its a leaf or limb node, and Click on Add Button.

It would be as below after adding the node in Alternate Hierarchy.

B. Nodes

1. Right Click on the Alternate node for which you need to place a standard node as child, and click on Insert as shown below

2. Enter the name of the node to be inserted and enable the check box Create Shared Node as shown below

You can also browse for Standard Node instead of type, using button as highlighted above in red. You would see below popup box to navigate between hierarchies, and then to select the node from Standard hierarchy

3. Once Insert Button clicked in Insert Node dialog box, the node would be inserted as shown below.

4. Repeat the steps from 1-3 to insert more shared nodes under alternate hierarchy5. Edit Properties for Standard Nodes (Shared nodes) NAV_CHILD_AGG_ATTRIB: The default value of this property is +. The value can be changed to -ve (negative) to redefine the rollup of the node.

No other property should be changed for inserted Standard Nodes in alternate Hierarchies, except NAV_CHILD_AGG_ATTRIB

C. Drag and Drop Option:You can even use drag and drop option for inserting/ moving or sharing the nodes among the hierarchies/within the hierarchies Within Hierarchy move operationTo move a node from location to other, hold the node and drag to the parent to which you want to make the node being dragged, as child

Hold and Drag as below

Release the control on parent where you want to move as child

Within Hierarchy Insert Operation

Select the node you want to share at different parent within the alternate hierarchy, hold th Ctrl key while selecting the node, and then move the control to the parent to which you want to make this node as child, as below

Release the control, once the parent to which the current node is being shared under (parent would become bold as shown above), then release the control to get it inserted shared node

Among the hierarchy - To insert a node from Standard Hierarchy to Alternate hierarchy, Open the Standard and Alternate hierarchy as below, and select the node you want to insert from Standard to Alternate hierarchy.

Hold and Drag the control on to the parent to which you want to insert this node as child and release the control

Once you release the control, the node would be inserted as below

III. FAQs

Q1. What if I use delete instead of remove operation for removing the standard node from Alternate Hierarchy?Delete would delete that particular node from Standard Hierarchy. This is not advised to do it.Q2. What if I use remove instead of Delete for deleting a Alternate NodeUse Insert operation to insert it back, and then use delete operation to delete it permanently. Q3. What if I use insert instead of add for adding Alternate node.No issues. DRM will prompt the user to Add as below

Q4. What if I use add instead of insert for adding a standard node in Alternate HierarchyDRM would prompt the user as the node already exists. You can click on Yes button

Q6. What if I insert a node in wrong location (place) in Alternate Hierarchy?Use Remove operation to remove it , and locate the parent for which you want to make this node as a child, and use insert operation

Q7.

This is because, the node F1510000000 is already exists in Hierarchy, and you tried to insert the parent of this node later, as shown below.

In this case, you have remove the child/descendants of FPL wherever they are present in the total hierarchy, then only insert FPL. Once FPL is inserted, you can again place all the removed child/descendants back into their location from where they were removed.Q11. Unable to share a node as sibling of primary node You cannot have primary and shared nodes as siblingsAlternate Hierarchies User Manual24