Hierarchies in BW can be time-dependent, version-dependent or both. A time-dependent hierarchy is valid only in a specific time range. This range is set by the properties “dateFrom” and “dateTo”. The hierarchy is only valid in that period. As a result, there can be various hierarchies with the same name but different time ranges. Also, it is possible for the entire hierarchy or only the structure of the hierarchy to be time dependent.
A version dependent hierarchy can exist in different versions. These versions are represented by a 3-Character identifier (e.g., 001, AB2) but can also be an empty string. Every version of a hierarchy can have a different hierarchy structure.
If time- and version dependent hierarchies are used, it is not enough to specify the hierarchy by its name. To uniquely identify the hierarchy, a due date and/or a version must be given. The due date specifies the date on which the hierarchy must be valid. The version specifies the version of the hierarchy.
In the past versions of SAP Analytics Cloud (SAC) there is only limited support for time- and version-dependent hierarchies. It is possible to handle values for the due date and version via variables.
Using variables enables the support for times and versions by setting the values from the variable dialog as hierarchy parameters. This is setting the values on a per-story level.
How to setup the variables can be seen here: https://me.sap.com/notes/3081404
With this new feature, time- and version-dependent hierarchies will be supported in the Table and Chart widget (Optimized mode). This addition lets you select the due date and the version for a hierarchy on a per-widget level. Time-dependent hierarchy and hierarchy structure are supported. The given due date will be interpreted by the BW back-end.
It is also possible to select a “default date” which corresponds to the default due date. This default is prioritized like this:
If a new date is selected, or the default checkbox is toggled, the list of available hierarchies will adjust to the selected date. As a result, you will only see hierarchies (and versions) that are valid for your selected date.
The version is shown within the list of hierarchies in brackets after the hierarchy description. If the hierarchy does not have a version or is available in the empty string version, no version is shown.
The display of the due date selection and the version is dependent of the capability of the hierarchy. If the hierarchy does not support one or the other, the corresponding item will not be shown.
Note: An explicit variable submit will reset the information for the hierarchy selection. If a variable for Hierarchy name, Hierarchy due date or Hierarchy version exists, the information will be set when a variable submit is triggered. See also the following SAP Note - https://me.sap.com/notes/3311828/
With the first release of the feature the focus was lying on the Table and Chart widget. There are still some integrations missing which will come as additions in later releases. These are mainly the Geo widget, filter across models and the filter dialog. Also, the scripting API and the Data Analyzer are not support in this release.
You can also see the list of restrictions here: https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/1300cc1becc04f9b8e29d...
The new feature, to modify the hierarchy due date and version on the UI, is planned to be released with SAC Q1.2024. It will be only available for the optimized mode.
To use the feature in SAC, the following BW notes must be installed:
Time, version-dependent hierarchies
Dimension settings for time version dependent hierarchies
A version dependent hierarchy can exist in different versions. These versions are represented by a 3-Character identifier (e.g., 001, AB2) but can also be an empty string. Every version of a hierarchy can have a different hierarchy structure.
If time- and version dependent hierarchies are used, it is not enough to specify the hierarchy by its name. To uniquely identify the hierarchy, a due date and/or a version must be given. The due date specifies the date on which the hierarchy must be valid. The version specifies the version of the hierarchy.
Usage with variables
In the past versions of SAP Analytics Cloud (SAC) there is only limited support for time- and version-dependent hierarchies. It is possible to handle values for the due date and version via variables.
Using variables enables the support for times and versions by setting the values from the variable dialog as hierarchy parameters. This is setting the values on a per-story level.
How to setup the variables can be seen here: https://me.sap.com/notes/3081404
Support of BW time- and version-dependent hierarchies
With this new feature, time- and version-dependent hierarchies will be supported in the Table and Chart widget (Optimized mode). This addition lets you select the due date and the version for a hierarchy on a per-widget level. Time-dependent hierarchy and hierarchy structure are supported. The given due date will be interpreted by the BW back-end.
It is also possible to select a “default date” which corresponds to the default due date. This default is prioritized like this:
- Variable value (if a due date variable exists)
- Due date set for the dimension hierarchy (if available)
- Query key date
Hierarchy due date
Query key date
If a new date is selected, or the default checkbox is toggled, the list of available hierarchies will adjust to the selected date. As a result, you will only see hierarchies (and versions) that are valid for your selected date.
The version is shown within the list of hierarchies in brackets after the hierarchy description. If the hierarchy does not have a version or is available in the empty string version, no version is shown.
Hierarchy versions
The display of the due date selection and the version is dependent of the capability of the hierarchy. If the hierarchy does not support one or the other, the corresponding item will not be shown.
Note: An explicit variable submit will reset the information for the hierarchy selection. If a variable for Hierarchy name, Hierarchy due date or Hierarchy version exists, the information will be set when a variable submit is triggered. See also the following SAP Note - https://me.sap.com/notes/3311828/
Table widget
What is still missing?
With the first release of the feature the focus was lying on the Table and Chart widget. There are still some integrations missing which will come as additions in later releases. These are mainly the Geo widget, filter across models and the filter dialog. Also, the scripting API and the Data Analyzer are not support in this release.
You can also see the list of restrictions here: https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/1300cc1becc04f9b8e29d...
Availability
The new feature, to modify the hierarchy due date and version on the UI, is planned to be released with SAC Q1.2024. It will be only available for the optimized mode.
To use the feature in SAC, the following BW notes must be installed:
- 3316445 - InA: Dimension metadata enhancement (time and version dependent, result alignment and visibility) - https://me.sap.com/notes/3316445
- 3327663 - InA: Metadata of query header not properly updated (description, title, due date) - https://me.sap.com/notes/3327663
- 3335769 - Time Dependent Hierarchy not working as expected when using Key date variable in the BW query - https://me.sap.com/notes/3335769
- 3357445 - InA: Dimension metadata enhancement (enable capability) - https://me.sap.com/notes/3357445
- 3377903 - BW InA: Hierarchy defaults processing (date, version and bindings) - https://me.sap.com/notes/3377903
- SAP Managed Tags:
1 Comment
