Skip to Content

SAP Integration Update Part 8 – Web Intelligence 4.0 and time-dependent hierarchies

This time we will look at how we can use SAP BusinessObjects Web Intelligence 4.0 in combination with time-dependent hierarchies and a feature called “Track Changes” to highlight the impact on our hierarchy.


We are starting by using a BEx Query as the source for our new Web Intelligence report.




In the next step we can select from the list of our configured connections. Our connection is pointing to an InfoProvider and therefore we are shown the complete list of BEx queries.




After we established the connection we are presented with all elements from the underlying BEx Query.



Especially in the BEx Query we are using, we have a characteristic Sales Organization with a time-dependent hierarchy.



The characteristic is presented to us with what is been called a default hierarchy – here Sales Organization and currently selected – as well as the hierarchy Sales_Org.


The default hierarchy is especially helpful when the BEx query contains hierarchy variables and the user then can select the hierarchy at run-time for the report.


As you might notice the list of hierarchies does not indicate that there is a time-dependent hierarchy shown here.


We are going ahead and add the hierarchy to our resultset, together with a keyfigure.



As part of the overall query panel you will be shown the icon shown above on the top left corner in case your BEx query contains a keydate variable.


I added the hierarchy to the resultset and clicked on the icon (shown above) and am now being asked how I would like to resolve the time-dependency.


I can configure a specific data and in addition I can configure the option to prompt the user for each refresh of the report, which is what I am going to use.




In the next step I am opening up the member selector for the hierarchy.




Right now the member selector has one limitation in this scenario, which is tha the member selector is showing inside the query panel (means before we actually executed the report) the default hierarchy for the system date.


We are selecting all the members from the hierarchy…



… and are executing our query. Because we configured the keydate variable to prompt, we are been asked to provide a date for the keydate variable.




Now as soon as we are in the report we are navigating to the tab Analysis and there to the tab Data Tracking.



The option Track allows us to activate the Data Tracking option. On the tab Data we are being asked which dataset we would like to use as reference. In our case we will use the data set we just configured.


The tab Options allows us to configure how changes in the data are being highlighted.



Now we are going to refresh our report and set a different data for our keydate variable.



As a result we are being presented with a hierarchical report showing us very visually highlighed the changes based on our change in the keydate variable for our time-dependent hierarchy.


I hope this short summary helps you to understand how Web Intelligence is able to not only resolve the time-dependency but also to highlight the impact of a change in the keydate variable.

You must be Logged on to comment or reply to a post.