Within the time frame of 2024 Q1, several new calculation view features have been released in SAP Business Application Studio when connected to SAP HANA Cloud database QRC1. Some of these features are highlighted below. You can find examples that illustrate the individual features here. An overview of features of other releases can be found here.
Open Calculation Views in Read-Only Mode
Calculation views can be opened in read-only mode. The choice of the default opening mode can be persisted for the developer workspace.
When a calculation view is opened in read-only mode the view details can be inspected but no changes are possible. This avoids that unintended changes are tracked in Git due to the frequently used auto-save option. Read-Only mode prevents unintended changes but cannot be used to prevent intended changes by the developers, given that the setting is controlled by the developer.
To open a calculation view in read-only mode, right-click on the calculation view and choose "Open With ..." and option "Read Only":
To persist a choice so that calculation views in the current developer workspace are opened in Read-Only mode per default when double-clicking at them, choose option "Configure default editor for *.hdbcalculationview..." followed by your prefered mode:
Deprecate Views and Block Queries
The option to mark a calculation view as deprecated is enhanced by an option to also block queries to the calculation view. Instead of the query results a configurable information message is shown to the user executing the query.
Use this option to manage the lifecycle of calculation views and to prepare the roll-out of replacement information.
Information about the deprecation status of a view can be found in columns DEPRECATED and DEPRECATION_NOTE of view _SYS_BI.BIMC_CUBES.
The options to deprecate a calculation view are available under View Properties:
Calculation Views that consume deprecated calculation views will show a warning in the design time model:
Flexible Options to Make Column Names Unique
Naming conflicts that arise if a column with the same name as an already existing target column is mapped can now be flexibly resolved.
If name collisions would occur by keeping the source column name, options are offered to pre- or post-fix the name by a fixed string or the source name. Alternatively, and per default, the column names are made unique by adding a number:
This dialog is started automatically, if name collisions arise during mapping in tab Mapping, or when adding a Dimension Calculation View to a Star Join Calculation View.
Support of Analytic Privileges for MDS Cubes
Analytic privilege settings of calculation views are now applied automatically also to MDS Cubes that are defined within the calculation view. If the calculation view is secured by analytic privileges users need also analytic privileges to access data of the respective MDS Cubes. Analytic privileges that are defined on a calculation view automatically apply to the MDS Cube as well. Analytic privileges that are assigned to users who report on the MDS Cube must included only columns that are included in the MDS Cube.
Propagate Adding and Deleting Input Parameters
Similarly to propagating adding or deleting of elements such as columns, adding or deleting also of input parameters can now be propagated to consuming calculation views within the same HDI container.
If in case of adding, name collisions, or in case of deleting, dependencies, would lead to inconsistent models, propagation is blocked and an error message shown.
Define Multiple Window Functions in One Window Function Node
Define multiple window functions in one window function node if the window functions use the same partitioning and ordering. This reduces the effort when modeling several window functions and can lead to improved performance compared to sequential stacking of window function nodes.
- SAP Managed Tags:
2 Comments
