Thanks for your response, Jay!
I feel the same that it could be a data grain issue. The BEx query and Lumira visualizations are indeed at different levels.
In our case, Lumira is getting the aggregated values from BEx at a higher level than BEx.
I'll try to explain the situation below. Please note that the fields are modified from our real scenario to simplify the content in this forum.
Hope this provides the details you are looking for.
BEx Query Design
Rows contain Key Figures - Gross Sales and Net Sales
Columns contain a structure.
Structure comprises of Restricted columns Actual and Plan.
Structure also contains a calculated column Actual % Plan.
Free Characteristics contain Company Code, Customer and Month
Data Acquisition in Lumira
Rows contain Measures - Gross Sales and Net Sales
Both have aggregation set to "SUM".
Columns contain the Structure (with values Actual, Plan, "Actual % Plan") and Company Code.
Visualization
This contains a cross tab displaying Dimensions in columns and Measures in Rows.
In our case, we have chosen to display only one Dimension i.e. "Structure" in columns.
The other Dimension "Company Code" is used as a filter only.
This looks somewhat like this:
| Measures | Actual | Plan | Actual % Plan |
|---|---|---|---|
| Gross Sales | xxx (matches BEx) | yyy (matches BEx) | xxx % yyy is not calculated correctly |
| Net Sales | abc (matches BEx) | def (matches BEx) | abc % def is not calculated correctly |
Issue
Aggregation in Lumira is set on Measures (and not columns within the Structure). Hence "Actual % Plan" tries to aggregate and SUM up the values resulting in values that do not match with BEx.