We have been using IBP 5.0 since the last 15 months.The systems are now upgraded to 6.0 too. Now I have a peculiar problem in one of our Planning areas.

Can any of you please tell me why the formula with title 'Working' feeds PCAPAUSAGE and the one titled 'Not working' does not feed into PCAPAUSAGE at all? I have also attached Excel front end screenshots too.

If you look at both the graphs you will see that PCAPACONSUMPTION is at PERPRODLOCRESSRC in both the calculations. PCAPACONSUMPTION gets calculated for both graphs but PCAPAUSAGE is calculated only for one of them.

My understanding is Supply Planning Key Figures have to be fed by a KF which is saved at the same planning level. From my graphs you will see that HISCAPACONS2 which feed PCAPACONSUMPTION is the correct level in both the graphs. PCAPACONSUMPTION is calculated for both but PCAPAUSAGE can be seen for only one.

This might be a show stopper....any guidance will be appreciated highly.

Related questions

5 Answers

In one of the screenshot(not working), the value of PCAPACONSUMPTION is calculated from a key figure which is stored at PERRES.

For supply planning to work, all key figures involved in the calculation chain should be on same planning level which is PERPRODLOCRESSRC. Due to this PACAPAUSAGE is calculated only in the first case where key figures are on same planning level.

Add comment

In one of the screenshot(not working), the value of PCAPACONSUMPTION is calculated from a key figure which is stored at PERRES.

For supply planning to work, all key figures involved in the calculation chain should be on same planning level which is PERPRODLOCRESSRC. Due to this PACAPAUSAGE is calculated only in the first case where key figures are on same planning level.

Add comment

Thanks a lot Rohit and this is what the going back and forth between me and SAP. Unfortunately this limitation would take away a very critical business functionality. This limitation calls for us to maintain 'global' level Resource attributes at PEPPRODLOCRESSRC level. Just imagine a Resource with 8 extruders(BUSHING in our scenario) and 5 Source IDs. When you load the Resource it will show up as 40 Extruders which is wrong. My users also will not like to maintain the same data multiple times, which also may lead to inconsistencies.