How to create a WEBI report based on a HANA analytical view that has mandatory PARAMETERS?
Introduction: This short document shares how one can achieve potential performance improvements on large volume analytical views by passing in parameters to the HANA analytical views so the filters can be pushed to the lowest level possible. (Pushing filters to the lowest possible level is one of the best practices so that the aggregation of the data takes place on a smaller subset of data rather than aggregating a large subset of data and then filtering)
At this point this document only shares how to pass a SINGLE PARAMETER and does not cover passing of multiple parameters on multiple dimensions.
Step 1: Create a HANA view that has a Mandatory parameter as shown in the following steps
Finally here is the SQL console statements you can use as reference to test your own HANA views that has parameters.
SELECT * FROM "_SYS_BIC"."sial.bicont-dev.sales.order_flow/AN_ODB_FLOW_U_P"
(PLACEHOLDER."$$P_CUSTOMER$$" => '0049476774' );
Note: This syntax will change a little bit when using in IDT BOBJ layer
At this point we assume you have a HANA view with parameter that has been tested in the HANA studio and ready to start building the Information Design Tool BOBJ artifacts.
Step 2: Create a universe using BOBJ IDT toolset.
SELECT * FROM "_SYS_BIC"."sial.bicont-dev.sales.order_flow/AN_ODB_FLOW_U_P"
('PLACEHOLDER'=('$$P_CUSTOMER$$' ,@Prompt('Enter P_CUSTOMER','A')))
Note: The above syntax is different than used in the HANA studio to test the analytical view.
Also note the @Prompt is a function call and its parameters all of some default value and some meaning
Please ensure you review the documentation on the @Prompt function to understand its parameters
Step 3: Create a WEBI layer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
9 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |