Background Information on Conditions
If you use conditions and the query displays an unexpected result, then check the following points:
Usability of conditions
Check if you can use the condition. In the Web item and design item (in the BEx Analyzer) List of Conditions, you can display the existing conditions for the query view or the query. In the status descriptions you can see if the condition is active, inactive, not used, or not applicable .
For more information, seeUsing Conditions.
No Consideration of Local Calculations, Scaling Factors and Currency Translation
The values in a condition always refer to the actual values and not to the values changed for the display. Local calculations (for single values or results), cumulations, normalizations, scaling factors and currencies are not considered during evaluation of conditions.
For example, if you have activated scaling factors in the query properties and have not taken this into account with the condition definition, then it can cause unexpected results when executing the query. This is because it is possible that you have not chosen enough number values in the condition.
With the condition definition, you take the scaling into account or switch off the scaling for the key figures.
Dependency of Drilldown Status
Conditions are dependent on the drilldown. The setting with the definition refers to all drilldown characteristics independently so that the condition is very generally defined and can be used for all drilldown characteristics. However, that does not mean that the conditions are independent of the characteristic distribution for the axes.
The swapping of characteristics for an axis (seeRanked List Condition for All Characteristics in Drilldown Independent: Top 3 Products and Top 3 Sales Channels) also affects a change in the result, as with the swapping of characteristics between the axes.
Conditions for Characteristic Combinations
Usability
Note that the characteristics involved have to be next to one another on the same axes with conditions for characteristic combinations. No characteristic or characteristic combination involved can be removed from the drilldown. Otherwise, the condition cannot be used (seeUsing Conditions). In addition, the axis may not have a hierarchical display (see Query with Hierarchically Displayed Axis and Conditions). If one of the two characteristics has a presentation hierarchy, then conditions are possible for the characteristic combinations. However, it must be a threshold value condition. Ranked list conditions are not possible for characteristics with an active presentation hierarchy (see Query with a Presentation Hierarchy and Conditions).
Results Rows
If you activate a characteristic for characteristic combinations, then the results rows are automatically left out. However, the overall results row for the quantity of characteristics for the condition remains intact.
The reason for this is because the characteristic values merge with a characteristic combination. If you define a condition for a combination of two characteristics (like underRanked-List Condition for Characteristic Combination: Top 10 Combinations from Product and Sales Channel), then the system does not evaluate the separate characteristic rows for each characteristic, but rather the combination of characteristic rows. For this reason, results for the individual characteristics are not useful and are not calculated. With a drilldown according to sales channel and products and the active condition Top 10 Product/Sales Channel Sales, you do not see a results for the inner characteristic (in this case, products).
The overall results for the characteristic combination can then be calculated and is displayed. However, note that the overall result for the characteristic combination is specified without taking the condition into account. This is because conditions have no influence on the display of the results. For more information about conditions and results, seeCondition: Top 5 Products.
Query with Condition and Results Row Suppression
In queries that have a condition that is active for a characteristic, and at the same time, the property Suppress Results Row is active for another characteristic, the result will generally be an incomprehensible output list. In such cases it is necessary that the results row suppression be deactivated to make the output list more comprehensible. For more information, seeQuery with Condition and Results Row Suppression.