Skip to Main Content

Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Master vs Alternate DRM hierarchy Relationship

RAM1123Jul 19 2018 — edited Aug 14 2018

Hello all,

We are having a Hierarchy 'A' (existing) which is considered as a Master hierarchy and we are planning to create a hierarchy 'B' as a alternate based on the master hierarchy 'A' plus few additional nodes in hierarchy B.

pastedImage_1.png

CURRENT STATE: When we add leafs like highlighted in hierarchy B, it automatically adds those leafs in hierarchy A also which we do not wanted to happen. For example, the leaf nodes (leaf_33333333A, ***B and ****C) should be present ONLY in hierarchy B and NOT be flown into hierarchy A.

EXPECTATION / TARGET STATE:

> We want to keep the hierarchies A and B as it is displayed in the above diagram.

> Any new limb or leaf added by users in Hierarchy B (alternate) should stay in Hierarchy B ONLY.

> But, Any new limb or leaf added by users in Hierarchy A (Master) should reflect in Hierarchy B also.

NOTE: To create the same nodes in hierarchy B, 'Insert' option was used. Also note, the new leafs to be added in hier B (but not to reflect in hier A) can be added at any level.

QUESTIONS / HELP REQUIRED:

> How can we break the "backward flow" relationship from hierarchy B to hierarchy A ?

> However, we want to retain the "forward flow" relationship from hierarchy A to B so that any nodes added in hierarchy A gets reflected in hierarchy B also.

Thank you in advance.

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Sep 11 2018
Added on Jul 19 2018
3 comments
996 views