Alternate Viewpoints Using Different Parent-Child Relationships

You can create an alternate viewpoint in which nodes' parent-child relationships differ from the relationships defined in the primary viewpoint. For example, you would use this type of hierarchy to analyze the impact of a reorganization that combines multiple business units into one unit.

Tip:

Use this type of alternate viewpoint for what-if and future scenario planning.

Note:

For Oracle Financials Cloud General Ledger applications, each tree (tree code/tree version name) must have a separate hierarchy set.

To define a hierarchy in which parent-child relationships differ from those of the primary viewpoint, you create new instances of the following data chain objects:

• Hierarchy set

  Note:

  A new hierarchy set is needed because you would not be changing the primary viewpoint's parent-child relationships
• Node set
• Viewpoint

The following steps describe how to create a hierarchy with parent-child relationships that differ from those of the primary viewpoint. For more information, see, Defining Alternate Views and Viewpoints.

1. Create a new hierarchy set that uses the same node types as those used in the primary viewpoint.
2. Create a new node set using the same hierarchy set you just created.
3. Create the alternate viewpoint using the node set you just created.

Example 19-2 Evaluating a Reorganization

Suppose a company needs to evaluate the impact of reorganizing the Sales department. Currently the Sales organization has top nodes for continents, and the continent nodes have child nodes for countries. The following example shows the Europe branch of the hierarchy:

In the alternate viewpoint that models the reorganization, the branches for continents have child nodes for regions, and the regional nodes have child nodes for countries. The following example shows that the Europe node in the alternate viewpoint has child nodes for the Eastern Europe and Western Europe regions, with the regional nodes containing nodes for countries: