on 11-10-2004 3:28 PM
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.
Pamela,
Any luck with resolving this problem? I am encountering the same one and haven't been able to find a solution to it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
Set the key figures to before aggregation. Then the value will show up right.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.