Skip to Content

Different aggregation between Hana Studio and Composite Provider

Oct 16, 2017 at 07:53 PM


avatar image

Hello Experts,

We are facing an issue with a query on a composite provider that presents a different value from the result we get on Hana Studio calculation view.

We created a Calculation View on Hana and we are using this calculation View on a Composite Provider (Union type).

The Composite Provider contains only the calculation view:

We are facing a problem on the output of the query created on this Composite Provider (Bex Query Designer), that the result on this output is different from the result we have on the Hana Studio output (using data preview or raw data) When we run the result on Hana, the outputs we have for the measure ZPUR_GROVAL and NET_PO_VAL are this:

However, when we either run a query developed on this Composite Provider the output we get is different from what we are getting on Hana Studio.

Both values are a calculation where I actually apportion the value when the same purchase document item has several cost centers or wbs elements.

We use this formula to calculate both measures:

ZZWPROZ being the percentage in the apportioning for each costcenter of wbs element. All the measures were created with data type DOUBLE (including ZZWPROZ) to get as accurate as we could on the decimal rounding.

We tried different things but none of them seemed to work.

We tried different data types on the fields (FLOAT, DECIMAL), andwe also tried to associate those fields to standard InfoObjects (0PUR_GROVAL and 0NET_PO_VAL) but none of them worked.

What SAP BW seems to be doing is rounding the values to only three decimals (we found that out by trying it on excel).

Has anyone found an issue with this decimal loss in values from SAP Hana to SAP BW?

How did you solve it?

Thanks in Advance

Alexandre Spissoto

hana1.jpg (18.5 kB)
hana2.jpg (234.6 kB)
hana3.jpg (244.5 kB)
hana4.jpg (79.3 kB)
10 |10000 characters needed characters left characters exceeded

I'd probably check the data type definition for the calculated column and compare it to the ABAP data type. Conversions like this could occur by mapping to a different numeric data type.


I created the calculated columns as DOUBLE in the calculation view, but they are created in ABAP as FLTP 16,16


Generally, working with floating point data types comes with compromises on precision and that's even more relevant when trying to do that across systems (here SAP ABAP and SAP HANA).

See @Horst Keller's blog as an example for that.

Other than that, it might be worthwhile to open a support issue for that, so that the colleagues can have a deeper look into what's happening with the data where.


Thanks Lars,

We did open an incident with SAP support and they are analyzing the problem to find a solution


Hi there,

We are facing exactly same issue with the wrong numbers on the Key Figure (FLTP type) in Composite provider, while in Calculation view Preview everything shown correctly.

We have found that our issue is only limited to few particular calculation views, while for others it's working properly. The ones, which are affected has Input Parameters... We are still investigating...

Do you have any update from SAP regarding this issue? He have also raised message to them..

Thanks, Alex


Sorry for the delay Alexey, we are still nvestiganting the issue too. We ran some tests and what we think happens is that when BW read the calculation view, it only coniders three decimals, instead of the seven we are using on the calculation view.

So, try to see if the cases you say are working properly are cases where you use no more than three decimals on the calculation view. In our case, we need seven decimals for accuracy.

* Please Login or Register to Answer, Follow or Comment.

0 Answers