Financial Management Blogs by SAP
Get financial management insights from blog posts by SAP experts. Find and share tips on how to increase efficiency, reduce risk, and optimize working capital.
cancel
Showing results for 
Search instead for 
Did you mean: 
alex_marasigan
Product and Topic Expert
Product and Topic Expert
1,230

Dear readers, if you are reading this after getting familiar with SAP Profitability and Performance Management Cloud Universal Model, I presume you are eager for more details about its features. You are fortunate, because SAP PaPM Cloud has recently launched the Hierarchy functionality in Model View function, and is what will be explained here.According to the dictionary, "Hierarchy" is a system where items are ranked based on their importance, allowing users to query data consistently and structurally regardless of the source data layout.

Parent-child and leveled hierarchies are the most frequently encountered types. Each record in

parent-child hierarchies refers to a parent record to define the structure while in hierarchies with levels, every record includes full path details for tiering.

For other Hierarchy terminologies that may interest you, see Hierarchy Terminology.

Since we now have a little background of hierarchy’s  definition, here are the available types of Hierarchy incorporated in the UM Model View function:

In addition to Hierarchy types, optional value help tags are utilized to offer valuable data. Listed below are the value help tags and their definition.

Value Help Tags

Definition

Parent ID

Given to categories that originate from the input and are viewed as the predecessors.

Node ID

Designated to areas that originate from the input and are seen as the heirs.

Hierarchy Rank

The position indicates how many nodes in the tree contain key values lower than the node's key. This also acts as the main identifier for the hierarchy node.

Hierarchy Parent Rank

The location indicates the position of the parent node. The parent node's value is 0 for the highest ancestor.

Hierarchy Root Rank

The location where the root node is displayed.

Hierarchy Level

The position of the node on the level.

Hierarchy Tree Size

The count of nodes located underneath the current node.  Please be aware that the counting begins at the current node.

Hierarchy is Cycle

This tells us if we can reach a particular node more than once.

Hierarchy is Orphan

An indication of whether the child has parental figures.

Hierarchy Distance

The distance from one node to another.

Hierarchy Start Rank

This offers the identical features as Hierarchy Rank.

Start ID

The starting condition.

To know more about the configuration steps of  the Model View in the system, refer to the Model View section of the PaPM Cloud Universal Model Application Help.

To give you even a more detailed explanation of each value help tags, let me now explain how each type of “Hierarchy” functions works and how the value help tags impact its result.

This model view type creates a hierarchical structure by linking a parent-child sources, no matter the form of the original data source, which includes an ordered list of nodes that always follow the same structure. 

So, how does the value help tag affects the result? The value help tag dictates how the system should process input data to deliver a meaningful result.  Now, let's take an example on how each value tag prepares the input. Each row in the example below signifies a relationship between a parent and child.

Let us begin with Hierarchy Rank, where this Value Tag tallies the input entries and allocates a number based on their hierarchy level. The system assigns numbers ranging from 1 to 15 to each entry based on our input.

alex_marasigan_0-1723453655807.png

In the diagram below, the yellow number indicates the Hierarchy Rank for each entry.

alex_marasigan_1-1723454057421.png

The Hierarchy Parent Rank is derived from the Hierarchy Rank. The hierarchy is determined by the Parent ID column in this instance. The Hierarchy Parent Rank takes on the Hierarchy Rank of a node after becoming a parent.

Now you must be wondering why the blank Parent IDs have hierarchy parent rank as 0 instead of 1. This is because they symbolize the highest level of hierarchy or the original source.

alex_marasigan_2-1723454103496.png

Just like in the above example, the illustration below depicts the input, with red number which  shows the Hierarchy Parent Rank for each entry.

alex_marasigan_3-1723454263484.png

Hierarchy Root Rank assigns values according to parent grouping; all entries marked A1 and A2 have values of 1 and 13 respectively, as they come from the same parent.

alex_marasigan_0-1723454404222.png

Just like in the example above, the diagram displayed below visually represents the result.

alex_marasigan_1-1723454525678.png

Hierarchy Level assigns values according to the position of the node, so each line or row on the figure corresponds to a hierarchy level in the example.

alex_marasigan_2-1723454592272.png

Here is a visual representation of the result.

alex_marasigan_3-1723454716890.png

Hierarchy Tree Size indicates the quantity of nodes located beneath the current node. The calculation involves the present node, which in our scenario is A1 and A2.

alex_marasigan_4-1723454746019.png

In the diagram below, this shows a visual representation of the size in a hierarchy tree.

alex_marasigan_5-1723454869821.png

Hierarchy is Cycle tells us if we can get to some node apart from the top-down relation because there are many paths that it can be reached.

alex_marasigan_6-1723454909117.png

Hierarchy is Cycle as illustrated.

alex_marasigan_7-1723455151409.png

Hierarchy Spantree

Just like Hierarchy, it employs the identical source data format to determine the quickest route to a specified node. Because of the shortest path policy, it is not possible  to have multiple parents or cycles; and orphans are always excluded.

At first, all nodes at the current depth are examined before moving on to the nodes at the next depth level. In cases where there are various routes from the root to a specific node, only the initial and shortest route is shown on the tree while the rest are disregarded.

This instance establishes a relationship between a parent and child in the resulting table, with the exclusion of entries accessed through longer routes.

alex_marasigan_8-1723455194891.png

alex_marasigan_9-1723455338110.png

Furthermore, in our example there is an entry that lacks a parent, making it classified as an orphan. Nonetheless, if there is an orphan record in the data, it will be disregarded. For a field labeled with a value tag of "Hierarchy is Orphan", the result will be zero (0) and the orphaned entry will be excluded from the final output.

alex_marasigan_10-1723455379844.png

alex_marasigan_12-1723455509161.png

Hierarchy Ancestors

This technique provides the ancestral lineage of a given set of initial nodes. Ancestors are the same as Predecessors.

Hierarchy Start Rank functions similarly to Hierarchy Rank by tallying the input entries and allocating a hierarchy number accordingly.

The value help tag field Start ID produces the identical outcome as "Hierarchy Start Rank". The sole variation is that it shows the "Parent ID” precisely as the value in the final outcome.

alex_marasigan_13-1723455547588.png

The Hierarchy Distance is the outcome of the process that shows the distance between an ancestor and its descendants. Only “0” and negative numbers are permitted for Hierarchy Ancestors. Even though  not required,but users can choose to input values in the Hierarchy Distance From and Hierarchy Distance To fields in the header, indicating the extent to which the system should process the data. Ancestors in a hierarchy must be either negative numbers or ”0”.

alex_marasigan_14-1723455851146.png

Hierarchy Descendants

This produces a structure of offspring from a starting point. Descendants are the same as successors.

Hierarchy Distance is the outcome of the process that shows the relative distance between a descendant/child and its ancestor/parent.

alex_marasigan_16-1723455928010.png

Similarly, to Hierarchy Ancestors, the user can specify Hierarchy Distance From and Hierarchy Distance To fields to indicate the boundaries for data processing in the system. Descendants in a hierarchy are only allowed to be positive numbers or ”0”.

Spoiler
NOTE:  

Hierarchy and Ancestors is a type of model view that integrates the features of both Hierarchy and Hierarchy Ancestors. This model view type helps users avoid creating a Hierarchy Ancestor over a Hierarchy model view, thus saving effort in making several model views. This is also the case for Hierarchy and Descendants.

Hierarchy Ancestors Aggregate

Performs groups in a hierarchical structure starting from the highest level. An analysis is conducted from the top down using a hierarchical method.

Average (AVG) - Calculates the mean of the data sets.

Sum (SUMMATION) - Combines all the given information to find the total.

Maximum (MAX) - Shows the highest value for every group.

Minimum (MIN) - Shows the lowest value for every group.

Product (PRODUCT) - The outcome of multiplying two or more factors.

alex_marasigan_0-1723456235006.png

The focus will be on the (A1) (A1-B1-C3) family and  the process used to achieve the results will be further elaborated. The outcome is calculated from the clusters using their aggregation capabilities. The data was organized in rows to display the results in segments, illustrating the process of obtaining them.

alex_marasigan_1-1723456298277.png

String Aggregation (STRING AGGREGATION) - Produces a string by combining the given expression. The slash is configured on the Separator field from the header.

alex_marasigan_2-1723456357352.png

Hierarchy Descendants Aggregate

Employs a method starting from the base to effectively compute totals at different levels of a structure.

Average (AVG) - Calculates the mean of the data sets.

Sum (SUMMATION) - Combines all the given information to find the total.

Maximum (MAX) - Shows the highest value for every group.

Minimum (MIN) - Shows the lowest value for every group.

Product (PRODUCT) - The outcome of multiplying two or more factors.

alex_marasigan_3-1723456429284.png

In the same way as it has been discussed in the Hierarchy Ancestors Aggregate,the concentration will be on the (A1) (A1-B1-C3) family and  the process of obtaining the results will be further elaborated. The results are calculated from the groupings using their aggregation capabilities. The data was organized in rows to display the results in sections that illustrate the process of obtaining them.

alex_marasigan_4-1723456457428.png

That's all for now. Thank you for taking the time to read this blog entry.  I hope I have managed to address any lingering questions on your mind concerning Hierarchy.

Also, I am excited to share blog updates on What's New  in PaPM Cloud and Universal Model and other PaPM Cloud Universal Model Technical blogposts. .

Until the next blog post

If you have any questions or need further clarification on this topic, please click on this link.

 

1 Comment