Application Guide for Oracle Self-Service E-Billing (Business Edition) > Analytic Reports >

Reporting on the Business Hierarchy

Business hierarchies can have the following properties and relationships:

• One or more levels.
• Only one root node.
• One-to-many group nodes and sub-group nodes.
• One-to-many service agreements for each group node.

The administrator, manager, and subscriber privileges for business hierarchies are the same as those described for billing hierarchies in Reporting on the Billing Hierarchy.

Figure 2 shows the relationships in a business reporting hierarchy:

Figure 2. Relationships in a Business Hierarchy

Virtual Nodes

A virtual node is created when the same user is assigned to two or more group or sub-group nodes for hierarchy display purposes only. For example, if the same user is assigned to both manager positions three and five in Figure 2, then the hierarchy displays a virtual root node and group nodes B and D, which the user can now select for his or her hierarchy report context.

Hierarchy Versioning of Shared Reports

Using the hierarchy example shown in Figure 2, hierarchy versioning of shared reports would behave as follows:

• If group node C is removed, then any reports created from this location would be promoted to group node A where user 1 and 2 would have access to them.
• If group node D is removed, then any reports created from this location would be promoted to group node B where user 1 and 3 would have access to them.
• If group node B is removed, then any reports created from group nodes B, D, and E would be promoted to the root node where only user 1 would have access to them.

Hierarchy Versioning of Private Reports

Using the hierarchy example shown in Figure 2, hierarchy versioning of private reports would behave as follows:

• If group node C is removed, then any reports created from this location would be promoted to group node A, though user 1 and 2 would not have access to them.
• If group node D is removed, then any reports created from this location would be promoted to group node B, though user 1, 2, and 3 would not have access to them.
• If group node B is removed, then any reports created from group nodes D, E, and B would be promoted to the root node but no one would have access to them. If user 5, who created the reports in group node D, were reassigned to group node B, then user 5 would have access to those reports.