

This opens up the expression editor for editing. We do this because Input Parameters can only be added as filter via the expression editor. Every time you need a filter (even a static one) you would have to add a small bit of code here. This means that no more rights click + apply filter functionalities will work in this node. HANA throws us a warning that from now on, filters for this projection can only be maintained as an expression code.

But with curious developers like us, we have to explore the options that lie ahead! Press the Edit button marked below. Notice that it is greyed out because there was no manual coding of filters yet. We created it by simply right clicking the VBTYP field and assigning a filter value = ‘C’ there but due to that the system auto-creates the corresponding filter expression code in here. You can see here that the static filter that we applied earlier also appears here. Now, double click on the “Expression” under filters. Notice that an input parameter has been created and appears in the folder as shown below. Provide a datatype and length of this input parameter. Picture them as a value that can be used anywhere and this value being dynamic, can be entered at run-time by the user.

Input parameters can be created independent of fields unlike variables. Notice that there is no attribute to bind this value to here. The below window appears which is similar to our variable creation screen. Right click on it and select “New” to create a new one. Now, single click on the VBAK node if you already haven’t and then on the right side, you would see a folder for Input Parameters as shown below.

In this case variable can’t be used as we need to apply this dynamic filter at a lower node level and not at the top level.įirst things first- Let’s add one more field GRUPP to the view by propagating it to semantics and then activating the view again. When the user selects a value during data preview, this filter should be applied to Projection_1 and thus only the reduced data set should undergo further calculations. Let’s say we need to add a filter on field GRUPP from VBAK table. Input Parameters explained with an example Input parameters are of great importance and have multiple applications but here we learn how to use it as a dynamic filter at the lowest node. They are somewhat similar to variables but are available at every node in the view. Input parameters are the magical underappreciated providers of flexibility in SAP HANA. Filters:Type 3- SAP HANA Input Parameters
