cancel
Showing results for 
Search instead for 
Did you mean: 

Incorrect Results Row

Former Member
0 Kudos

Keyfigures are set where A * B = C. In the overall results row, the total for column C is correct at a detail level (ex: material number) - it sums the values in column C. When the drilldown for the detail level is removed and the totals are rolled up (ex: plant), the total for column C is incorrect - it uses the original calculation of A * B = C.

The key figures have been set to Calculate Results as Summation and the options under Formula Collusion have been changed to see if that would make a difference. It hasn't so far. Does anyone have any suggestions on how to work around this issue?

Thanks.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Pamela,

Any luck with resolving this problem? I am encountering the same one and haven't been able to find a solution to it.

Former Member
0 Kudos

When creating Calculated Key Figures, the complexity of the formula depicts if the enhance option is avaiable.

http://help.sap.com/saphelp_bw33/helpdata/en/6f/56853c08c7aa11e10000000a11405a/content.htm

Hope this helps.

Jeff

Former Member
0 Kudos

Set the key figures to before aggregation. Then the value will show up right.

Former Member
0 Kudos

I see this option for the calculated key figure, but it's grayed out. It's not available for the restricted key figures.

Former Member
0 Kudos

Could you tell me the full scenario. From the above mail it looks like you are doing calculated key figure. Correct me on that.

Former Member
0 Kudos

Column A and Column B are restricted key figures (the key figures used are restricted by a specific calendar year/week) and Column C is a calculated key figure that's the product of Column A and Column B.

The key figure used in Column C was originally created as a formula and I thought that might be part of reason for the incorrect results. I did see an OSS note that referenced key figures and before aggregation, so I thought I would change it from a formula to a calculated key figure to see if that would resolve the problem.

Former Member
0 Kudos

in the calculated key figure set the property to before aggregation.

Default:

after aggregation:

ex:

A B C

10 2 20

2 5 10

Result: 12*7=84

if changed to before aggregation means:

result=30.

so thats why that needs to be changed.

Former Member
0 Kudos

Amit,

Thanks for the explanation. The issue now is that I can't change the properties - the option to select before or after aggregation is grayed out.

Former Member
0 Kudos

I had run into similar issue in the past. My solution was to generate the report with the details so that all calculations are correct then I hide all details rows. It was done using coding in web API.

Former Member
0 Kudos

You could use a virtual key figure to calculate the multiplication. There you can set the detail as you like.

Best regards

Dirk

Former Member
0 Kudos

Joe,

How are you? I have encountered a similar problem where I need to generate a report with the details to make my formula calculate correctly. I would like to know the details on how you were able to hide the columns.

Thanks,

-Tim

Former Member
0 Kudos

Tim,

This was done for my client's web report. There is SAP document on hiding columns in web reports. You will need to understand Web API "table interface" concept and ABAP-OO to attempt this. It will open up a lot of new possibilities for what you can do with web reports.

Former Member
0 Kudos

Hi Pamela,

Were you able to fix your problem? What was the fix?I am having a similar situation with incorrect values and the option to select Before aggregation is grayed out.

Former Member
0 Kudos

We had a similar issue. It was because on the data aide of the world, the 2 fields we were using in the calculated key figure were not of the same aggregation type. One was based on a summation/numeric field, the other was a price that was tied to a date field. The Data people ended up doing the calculation for us and storing the result in a field/object that we could then pull into our query. It took a little bit of space as out InfoProvider is large, but we got the result that we wanted.

Former Member
0 Kudos

No, I have not been able to fix the problem. I'm still reading the replies to the post with the hopes that something will work for us.