on 2022 Oct 31 8:51 AM
Hi everyone,
Please consider (in SAP IBP) a calendar week that covers two different technical weeks and an editable key figure (base planning level on technical week). Further assume that the technical week A has key figure value 0, technical week B has key figure value NULL and the calendar week has key figure value 0. If (in the SAP IBP Excel-AddIn), I type in the key figure value 0 again on this calendar week and save the change, technical week B has still value NULL. Now, this is an issue if a user wants to set to 0 a (big) range of calendar weeks and this key figure is used to manually oversteer another. In this case, later, this key figure may still pull some other values than 0 in technical week B from other key figures. Does anyone know a possibility how to avoid that, i.e. make sure (e.g. by changing the configuration somehow) that in this case technical week will be set to 0?
I already tried to fix it by using a period weight factor, but the behaviour is still the same. If you have any questions or the need of clarification of the question, please let me know.
Thanks a lot for any hint!
Best wishes,
Alain
Technical details:
Version Excel Add-In 2111.6.0
Key figure configuration details: see attachment technical-configuration-details.jpg
Update:
I changed the proportionality of the diasaggregation to Same Key Figure - Stored Values, but the described situation above didn't change. In the attachment you'll find now also a screenshot of the applied disaggregation expression and a screenshot of the configuration details of the key figure used in it. Does anyone has an idea, how to solve this issue?configuration-details-of-disaggregation-key-figure.jpg disaggregation-expression.jpg
Request clarification before answering.
Hi alainibp,
I see you have used Proportionality: "disaggregation expression". Could you change that to "Same Key figure - Stored Values" and try. If that does not work, please share the screenshot of Disagg expression from KF calculation.
BR,
Praveen Jadhav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Alain
This type of behaviour typically happens when underlying TWb time period is not initialised for certain planning objects.
Please find the difference in 2 scenarios in screenshots when putting a value at cw when twb is initialised and not initialised.
Solution: Please run extend time periods operator to initialse twb and after initialisation it can still be null. Now when you put some value in cwk dependingon disagg expression/other proportion, it should respect for both weeks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
5 | |
4 | |
1 | |
1 | |
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.