Input for IO run-Demand forecast

[former_member696146]

Hello Experts,

Currently IO run takes the "Demand forecast" Key figure as a basis for inventory component calculation.Is there a possibility of running a IO run taking any other demand key figure as a basis other that Demand forecast (KF : IOFORECAST)? Kindly let me know the possibility.

BR,

Praveen

[chris_topf · Accepted solution]

Hello Praveen,

the IO algorithms read the IOFORECAST key figure at the REQUEST level as the input. You could edit the key figure calculation so that it points to another key figure that has a forecast you'd rather use.
For example, say that the key figure containing the forecast you want is the stored key figure OTHERFCST which has a base plan level of WKPRODLOCCUSTGROUP.
You could change the IOFORECAST key figure calculations to be something like this:
IOFORECAST@REQUEST = SUM("IOFORECAST@WKPRODLOCCUSTGROUP")
input is the calculated value of IOFORECAST

IOFORECAST@WKPRODLOCCUSTGROUP = "OTHERFCST@WKPRODLOCCUSTGROUP"
input is the calculated value of OTHERFCST

If the OTHERFCST key figure is not at the same planning level as IOFORECAST (i.e. WKPRODLOCCUSTGROUP), you will have to build a calculation to get it at that level.

Regards,
Chris

[former_member696146 · Accepted solution]

Hi Chris,

Thank you for your input. Modifying IOFORECAST KF calculation will not help, since my requirement is about having two parallel IO runs with varying demand inputs for two different set of materials (due to complicated customer requirement) . If there is no possibility then i need to copy over the demand numbers for the first time and then store the output (with IO run on first set of materials) and then go on to copy over the other demand numbers (different demand number updated in IOFORECAST KF using copy operator) the second time and then get the output again(with IO run on second set of materials). This i wanted to avoid considering the future support situation and looking for other possibilities. Kindly let me know if you need further clarifications on the same.

BR,

Praveen

[piyush_parekh · Accepted solution]

Hi Praveen,

As Chris mentioned, if IOFORECAST input is read at request level, you can maintain flag (say, NVARCHAR attribute) in product master to denote which forecast to be considered and modify IOFORECAST calculation to respect FORECAST1 or FORECAST2 depending on the flag.

Regards,

Piyush

[former_member696146 · Accepted solution]

Hi Piyush,

Thank you very much for your inputs.I will check on your solution proposal and will get back.Thanks once again.

BR,

Praveen