cancel
Showing results for 
Search instead for 
Did you mean: 

Different output between Composite Provider and Calculation View

Hello experts,

I am facing an issue in a Composite Provider on BW 7.5, based on a calculation view. When I extract the data on the BW application either via LISTCUBE, or loading the data into an ADSO, the result is completely different from the data we have on the calculation view.

When I display the result on the calculation view, I have 903 records filtering "CALMONTH" = '201901'

However, when I access the data on the BW side via Composite Provider, it only displays 22 records, and I couldn´t figure out the logic on it. The sum of the key figures are not even the same, and the data on the specific records are completely different. This is the LISTCUBE result:

I tried to load the data into an ADSO and the result is the same 22 records:

The Composite Provider has the same fields and the calculation view, so it is not a aggregation issue:

I also tried to create a query directly on the calculation view, and in that case, the output came out correctly, with the 903 records

I had the correct output also trying to extract from Lumira, so I am guessing the prblem is on the Composite Provider, which has the following settings:

Has anybody ever faced a similar issue? I am stuck with this for a few days now. This solution is working fine and the issue started after a restart on the Hana system.

I tought it could be a problem with database user privileges, but when I access the Hana Studio calculation view with the same usar SAP BW uses, I have the correct output.

Thank you in advance,

Regards,

Rosangela

john_hawk
Active Contributor
0 Kudos

Hi Rosangela,

If appears that there is something in the calculation view which is disaggregating the 22 records into 903.

We need to see the calculation view definition to know why.

John Hawk

0 Kudos

did you get cause/solution for it, I am also facing same issue now.

Accepted Solutions (0)

Answers (1)

Answers (1)

yi
Participant
0 Kudos

Was it the problem with null values?