on 07-11-2018 11:55 AM
Hello Experts,
I have a specific forecast requirement in IBP. I want forecast algorithm to populate values for specific periods only. It should not be Rolling forecast. e.g. If my current month is July 18 and I want Forecast values till December 18 only. When I move to August 18, Forecast value should not get generated for January 19. In short, I want forecast till December month only for some specific Product Location combinations. Any idea how to maintain it?
Regards,
Prasad
Hello Prasad,
Forecast operator in IBP exhibits rolling behavior by-default. However we can address your requirement with some custom development.
1. To distinguish selective location-products, configure custom attribute('CUSTOM1') and add it to LOCATIONPRODUCT master data and include that attribute in all relevant planning levels so that we can use this in KF calculation.
2. Using HCI task, populate value '1' in KF1 for this financial year and '0' for next financial year i.e. from Jan 19 on wards. You will run this job yearly once.
3. As we cannot restrict rolling behavior of statistical forecast, let it generate forecast for FY19 and store in KF1. Have another KF let say KF2, where in we put calculation as below
KF2@MTHPRODLOC = IF ( ''CUSTOM1'' = ''X'' AND KF1@MTHPRODLOC = 0, NULL, KF1@MTHPRODLOC)
4. With this design, you may have to consider KF2 as baseline forecast Key figure
Regards
Sai Samrat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, You can have your time profile valid only till Dec and run Stat forecast for the next months - forecast won't go beyond Dec then 🙂
Thanks,
Uthaman
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Prasad -
You may create a normal all editable custom key-figure, say "FCSTMNTH" that takes the input as either 1 or 0. And then update the values for this key-figure manually in the planning view or via data integration. In your case, it will be 1 till Dec'18 and then on 0. Allow the StatFcst to run as how it usually runs (rolling) and then as part of calc logic, multiply the StatFcst with this new custom key-figure so as to have the fcst values only where you need - you will see the StatFcst till Dec'18 because of the multiplication with 1 and then on 0 / NULL based on how you write your calc logic.
Just so to not disturb the system generated StatFcst volumes, I suggest to create a new key-figure for your fcst requirements and then write the calc logic for this newly created Fcst key-figure instead of directly operating on standard StatFcst key-figure.
Hope it helps,
Regards - Guru
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.