on 07-16-2019 7:36 AM
Dear community,
my planning area is based on SAP6 planning area based on the time profile being shipped by RDS solution with a pre-filled weekweight. The disaggregation from year to month for the key figure DEMANDPLANNINGQTY shows unexpected results.
Key figure definition
Results based on input of 1.200 at yearly level (2020 behaves also differently than 2019 despite having nearly the same weekweight factors)
Does anyone have a hint or can explain why the system disaggregates like shown above?
regards Peter
I found the issue. It was related to the underlying planning levels which have been created upfront. A couple of combinations have had wrong attributes assigned and therefore influenced the disaggreation behaviour in an odd way.
The timely disaggregation works as expected after having deleted the non intended combinations.
Maybe this finding helps others as well in case they face some unexpected behaviour.
regards, Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter,
It may be possible that DEMANDPLANNINGQTY key figure is using STATISTICALFCSTQTY key figure's proportion for disaggregation rather than using weekweight factor. Please pull both these key figures in a planning view and check if this is the case. Further, you can try deleting values in STATISTICALFCSTQTY and DEMANDPLANNINGQTY key figure (make it NULL) and then enter 1200 at year level for DEMANDPLANNINGQTY key figure. It should follow weekweight factor for disaggregation (as per uploaded records in time profile).
Regards,
Piyush
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I found out that calweek 27 (June), 32, 33 and 34 (August) aren't filled during disaggragtion although the starting base was NULL for all key figures which could be somehow related. I have even taken out the weekweight which also did not change the behaviour.
The time series master data does not indicate any strange or even missing values for those weeks. At least I was not able to figure it out.
Peter
Hi Piyush,
thanks for your continuous effort. I already did the way you explained upfront. STATISTICALFCSTQTY key figure is NULL and even DEMANDPLANNINGQTY KF was NULL before I entered 1200 at yearly level.
It's strange to me that the same approach for 2020 even brings up a different pattern also the bucket definitions are more or less the same.
br, Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.