IBP_CAGGR - Correct aggregation from techn. week to any aggreg. time period

[peter_casper]

Dear community,

we are currently working on the implementation of a custom projected stock calculation. For that reason we created 3 helper key figures which accumulate the respective input key figures, i.e. stock, receipts and demand. We applied MAX functionality for aggregation which ensures that always the highest value from technical week level will be taken for the display at e.g. monthly level. This function is fine due to the fact that the accumulated figures won't decrease across the time horizon.

Finally all three helper key figures get summed within their target key figure projected stock. This logic works well in case we stay at technical week level. But in case we choose a higher aggreted one, the calculation is simply wrong in either this or that way (irrespective if we use SUM, MAX or MIN).

Example

From my pov we would need to take the value of the last technical week period which belongs to the aggreation level in order to have a correct calculation also for this level in place. However I am not sure if and how this can be achieved. Maybe someone has an idea.

Thanks in advance, Peter

[Former Member · Accepted solution]

Hi Peter,

Using Last Period Aggregation method in IBP your issue will get resolved. What is does is it displays the value in Last period of the aggregation period. So in case your aggregation is at Calendar weekly then the value aggregated will be always Tech Week B.

Please refer below link to understand more about them

https://blogs.sap.com/2019/02/24/sap-ibp-last-period-aggregation-with-example/

Also same aggregation method is used in Standard Projected Stock Key figure.

Note: With 1908 Upgrage SAP will be providing a new config fuction "IBP_LPA" using which it will become easier to model the aggregation method as required.

https://help.sap.com/viewer/bf99e931b8d44aafb4e306ec3602cbdd/1908/en-US/8280eea63c914d8e95eecd322e5a...

Hope this helps

Regards,

Manoj

[peter_casper · Accepted solution]

Hi Manoj,

let me try to get it implemented although it seems to be quite cumbersome. The upcoming new function "IBP_LPA" would make life much easier. For the time being I would need to stick to various calculations for getting it done. Hopefully I can work it out.

Thanks so far.

Best regards, Peter

[peter_casper]

Hi all,

a brief update in case someone bases his LPA for any PRODLOC related inventory/receipt aggregation on the standard SAP6 planning area.

As said, the implemenation is quite cumbersome and it needs some time to understand the different necessary planning levels, aggregations and transformations. But, in essence it works and can be adjusted more or less easily to ones need.

Starting situation

LPA is needed to aggregate receipts and inventory on LOCPROD level correctly across the different time dimensions. In my case the lowest level of granularity is based on technical weeks.

How to implement LPA

Follow instructions from OSS note 2286684: https://launchpad.support.sap.com/#/notes/2286684

However planning area SAP6 from IBP version 1905 has already got an LPA functionality incorporated which is on LOCPRODCUST level. Therefore all related calculations need to be removed for the standard key figures CUSTDCSTOCKQTY and CUSTSTORESTOCKQTY incl the helper key figures w/ prefix H.

From that point onwards new planning levels at PERPRODLOC level can be defined. Ideally one uses the standard levels PERLOCPRODCUST1 and 2 as copy template followed by a removal of all customer related attributes.

Additionally I created an own helper key figure HKFPER2 similar to the standard one HKFPER but on LOCPRODWEEKLY level instead of LOCPRODCUSTWEEKLYLPA.

Last but not least the transformation key figure PERIODID needs to be changed where HKFPER2 serves as input instead of HKFPER.

The rest is according to the OSS note.

regards, Peter