Skip to Content
Technical Articles
Author's profile photo Xavier Polo

SAP DWC Input Parameters & Story Filters

In the latest DWC update (2021.11.7) some new features have been added, such as Input Parameters.

We can use Input Parameters to filter views in a similar way as we do with Story Filters. But what are the differences? First let’s review the Story Filters.


Story Filters


Defining Story Filters from View Editor

In an analytical view we can identify any attribute as a Story Filter, so that in SAP Analytics Cloud the user will see a window to filter values.


Creating a Story Filter from Attribute


In the configuration we can set:

  • If it is a range of values, or if it is an independent value or values.
  • If it has a default value
  • If it accepts multiple entries (ranges or values).
  • If it is mandatory for the user to fill it in



Configuring Story Filter as Range


Configuring Story Filter as Single


Opening a SAC Story with a view with Story Filters

If a view has Story Filters and/or Input Parameters, the user will be prompted to fill them using the variables window.



Variable window


The NameCountry is the Story Filter set previously.

Story Filters have helpers to fill them, like clipboard icon to allow us to paste values


Managing values from clipboard


Or a member selector:


Member selector


After making the selection, we will be able to see that the data in our Story is filtered. We can configure these filters to be applied in the same way in the whole story or leave some graphs to have their own values in the variables (customized with {} button)



Chart with Story Filter (left), Chart with custom Story Filter values (right) in the same SAC Story



Input Parameters (IP)

In the analytical view (SQL and Graphical) we can create Input Parameters, which like the Story Filters will also be requested to the user in SAC, but the difference is that we can use the IPs not only to filter data, but also to perform operations with them.

Creating an IP

From View Properties there are a new section called “Input Parameters”, from where we can manage them.


Input Parameters in View Properties



From here we can create, modify or delete the IPs:


Creating an Input Parameter


Using IPs

After creating the IPs, we can use them in our view:


Using the IP for filtering



Using the IP in a calculated field


Another difference between IPs and Story Filter is that when we use a view with IPs inside another view we can map the IPs to a fixed value or to an IPs from the “caller” view (this is not possible with “Story Filters”)

In the case of graphical views, when we drag and drop a view with IPs it asks us if we want to associate an IP from “caller” view or if we want to assign it a fixed value.


Map IPs window

This option allows us to pass values from view to view as we would pass parameters from method to method if we were programming

In the case of SQL views, when dragging the view with IPs, the name and IPs will appear in HANA SQL notation.


Using a view with “BP_CAT” IP in another SQL view and setting a fixed value “2”



Using a view with “BP_CAT” IP in another SQL view and setting “PARAM_1” IP from caller view


IPs – Business Builder

Input Parameters has also support at Business Builder, and they are referenced in several places.

First at Entity and Fact Models, we can decide whether to expose IPs to users in the Business layer. If the dimension or analytical dataset is based on a view with IPs, we can indicate which ones we want to expose and which ones we do not.


IPs at Business Layer Entity


After that in Consumption Models and Perspectives, allowing us to set a default values for each IP and Perspective:


Set default value at Perspective



IPs in SAC Story

Unlike the Story Filters, the IPs are shown to the user as a text box to be filled in, without any help.

Business Partner Category is the IP


Variable window


Some SAC charts using IPs in calculated fields:


Sample of calculated field using IP



We have been looking forward to this IPs feature, so enjoy it!


Best regards,

Xavier Polo


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Sebastian Gesiarz
      Sebastian Gesiarz

      Hi Xavier Polo ,

      Is my understanding correct that only single value input parameters are supported in DWC?
      That would mean that all different variable types have to be moved to SAC and more complex ones handled through AnalyticalApp/JS.


      Author's profile photo Xavier Polo
      Xavier Polo
      Blog Post Author

      Hi Sebastian Gesiarz,

      Yes, Input parameters are single value.

      But if you want to filter data, the view is Analytical, and it's exposed, you can create Story Filters instead of Input Parameters,


      Author's profile photo Sebastian Gesiarz
      Sebastian Gesiarz

      Indeed, so no place for push down to the lowest level.

      & no place for user exits apart from writing custom app in JS.

      Author's profile photo Gaurav Kumar
      Gaurav Kumar

      Hi Sebastian,


      Did you find a way to push down to the lowest level with multiple value select?




      Author's profile photo Sachin DJ
      Sachin DJ

      Hi Xavier Polo,

      Is there a way we can map any field to DWC input parameter to get input help? or there is no way?


      Author's profile photo Xavier Polo
      Xavier Polo
      Blog Post Author

      Now it is not possible, but iit's in roadmap for Q3 2022;INNO=000D3ABE796A1EEBB6DEB145CBFA0B74