Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

"All" value in prompts based on BEx variables in SAP BO WEBI


Environment: BW, BEx Queries with BEx Variables for the prompts, WEBI 4.0 SP6, NO Universes

(all new reports are developed on top of bw)

What is the best practice to include an "ALL" value option in the LOV prompt for a BEx variable?

With universes, it is certainly possible to include an "All" value in the prompt, but what about BEx prompts?

Option 1:

When the BEx variable is defined as optional and no value is selected, it acts as no restriction and thus all the values of the characteristic are considered.

Disadvantage: Users are used to select something - they are used to an "All values" option which means I will get all values. Not selecting anything is unusual for the user. Furthermore, some reports are based on universes, and some on bw/bics, the design of the reports looks the same, but in the "universes-based" reports they can select "All" because it is possible to implement it there but in the "bw-based" reports if they would have to select nothing - this would be confusing for the users.

Option 2:

When the BEx variable is defined as "allows multiple values to be selected", the user can select all values.

Disadvantage: We are showing in the report area an overview of what values have been selected for the prompts. If a user selects all values from several prompts, the amount of information gets very long and crammed not clean and clear.

Option 3:

If a hierarchy is defined with one text node on top called "All" and all the values of the characteristic placed under it, then a prompt is created on this hierarchy, the user can select the top node of the hierarchy to have All values. With this option/solution the user would finally have the possibility to select an "ALL" value in the LOV.

Disadvantage: Creating hierarchies for all prompts - is this best practice? What about maintenance and performance?

Option 4:

Creating Input Controls in WEBI adds "All values" automatically as the first value in the input control.

Disadvantage: All the required data has to be in the report.

What other options exist and which one do you use or recommend and why?

Also if there are other known disadvantages of the options I described, feel free to mention that too, much appreciated.

Thank you!

Kind regards,


Former Member
Not what you were looking for? View more on this topic or Ask a question