Safety stock requirement generation

[former_member566355]

Hi,

We are using report /SAPAPO/RRP_SR_ATP_GENERATE to generate safety stock requirement.

This report calls up the SAP standard heuristic SAP_PP_018 which has the BADI /SAPAPO/RRP_SFTY_STK (BAdI for Safety Stock Heuristic)

The scenario and requirement is -

1. The safety stock element should be a custom category (SR is standard). No issue here. This is configured and the requirement element gets generated with custom category after running the report.

2. This element is included in relevant GATP scope of checks.

3. The issue is - if some one runs the report with standard ATP category SR in selection this demand element replaces the element with custom category which can be seen in product view. So as I understand at any given point in time there will be only one ATP category which will exist as far as safety stock is concerned.

4. What we want is the Safety Stock requirement element with custom ATP category should be separated out so when someone run the report with SR it will create an additional element.

What is the behavior/use of SR requirement element in other modules like SNP/PPDS.

Thanks in advance,

Yogesh

[tiago_furlanetto · Accepted solution]

Hi Yogesh,

When Method UPDATE_IO_NODES from BAdI /SAPAPO/RRP_SFTY_STK is called, you can see the already existing safety stock requirements in internal table CT_OLD_REQ.

Additionally, you can see the new or changed safety stock requirements in CT_ORDER_METHOD.

Those entries in CT_OLD_REQ which do not contain a corresponding entry in CT_ORDER_METHOD are always deleted in standard are the Safety Stock Requirements that will be deleted.

In order to prevent this, a possibility is to delete the requested entries from CT_OLD_REQ.

Regards,

Tiago