Hi experts,
repeatedly I came in touch with the following scenario and didn't find a satisfying solution for that yet.
Maybe you can give the crucial hint.
I've got a query from the production-business-area (PP):
It shows production-notifcations including the produced material and the used input-components.
The InfoProvider looks (extremly simplified) like this:
Material Component ProducedQty InputQty
A X 10 10
A Y 10 10
B X 20 20
B Z 20 20
For the imagination: Let's say "A" is a knife, with the input-components X "blade" and Y "knife-handle".
B" is a scissors, as well with (partially different) input-compentens X "blade" and Y "scissors-handle".
Using standard-aggregation, a report would show the following result-rows:
Material Component ProducedQty InputQty
A X 10 10
A Y 10 10
Result 20 20
B X 20 20
B Z 20 20
Result 40 40
That is technically correct, but for the reporting very miss-leading, since it looks like material A had been produced 20 times, but in real it was only 10 times. The reason for this miss-leading result-row is the 1:n-relationship between the material an the components.
Now I'm looking for a way out of this.
In the end, I'd like to see the following reporting-result:
Material Component ProducedQty InputQty
A X 10 10
A Y 10 10
Result 10 20
B X 20 20
B Z 20 20
Result 20 40
I am aware, that this can be reached using exception-aggregation (Last/max/min for ProducedQty with reference-characteristic component).
The disadvantage of exception-aggregation is the fact, that (in this case) the characteristics material and components always need do be part of the OLAP-result-set, and this might become extremly big if you imagine that there might be 50.000 different materials, each having a components list of 10+. It becomes even worse if a 3rd characteristic (e.g. the workcenter, since the articel passes n of them in its production-process) joins the game.
In the end I've to struggle with very disturbing runtimes (2 Minutes+ for each navigation-step).
So, is there any way out of this, maybe some kind of preperation in the data-staging, usage of multiproviders, etc.?
(The problem with multiproviders: If you use a "header"-level InfoProvider (e.g. for the ProducedQty) and an "item"-level provider for the "InputQty", you'll get a 0 result, as soon as you restrict your report to any concrete compontent <> #).
In the end note http://service.sap.com/sap/support/notes/1257455 addresses the same topic, but unfortunately without any real solution.
Best regards, Marco