Safety Stock Requirement category SR

[former_member566355]

Hi,

I would like to understand the use of category SR in SNP.

It will be helpful if an example is given.

Thanks,

Yogesh

[marianoc · Accepted solution]

Hi YR,

I understand that SR are used in PPDS Heuristic: SAP_PP_018 (Create Safety Stock in SAP liveCache  -  Alghoritm: /SAPAPO/HEU_PLAN_SAFETY_STOCK).

This element is used to let the live cache to conside Safety Stock Requirements.

You can read more about SR in the help of the customizing:

In the standard system, it is defined in the Take Safety Stock into

Account field in the planning version that Production Planning and

Detailed Scheduling (PP/DS) should take safety stock into account as

virtual safety stock elements. In this option, the safety stock of a

product is represented by requirement or receipt elements, which PP/DS

only takes into account during the net requirements calculation, but

which do not exist in SAP liveCache as orders. Therefore, dynamic

pegging cannot take the safety stock elements into consideration and

does not create pegging relationships to these elements. All functions

that evaluate dynamic pegging relationships are affected: For example,

because pegging relationships do not exist for receipts that were

created to cover the safety stock, the system creates "incorrect"

overcoverage alerts, or the system is not able to take the requirement

dates/times of the safety stock requirements into account during

optimization of the lateness costs.

In the standard system, you can only implement this option in a

make-to-stock production scenario and for static safety stock methods

To create the safety stock requirements in SAP liveCache, you use a

heuristic that is based on the algorithm /SAPAPO/HEU_PLAN_SAFETY_STOC

If you have selected the option Create and Adjust Safety Stock

Requirements in the heuristic settings, the heuristic creates an orde

in SAP liveCache for the safety stock of a location product. This ord

has the category GC_OM_SAFETY_STOCK, it consists of a requirement

element with standard category SR, and it represents the safety stock

requirement. In the standard system, the safety stock requirement is

equal in amount to the current amount of static safety stock in the

location product master.

I am not sure if you have SR in SNP. Based on what I know SNP does not use SR.

You have different Safety Stock Methods to use in SNP.

Kind Regards,

Mariano

[former_member566355 · Accepted solution]

Thanks Mariano,

Further to this, I have one query.

.

We are generating safety stock requirement using report /SAPAPO/RRP_SR_ATP_GENERATE

which shows up in product view as a requirement element.

By default,the 'APO application' for this element is '2 - PPDS'

Is it possible to set it to initial i.e. '0' and what would be the impact of setting it to '0'. I mean what is the purpose of 'initial'

Yogesh

[marianoc · Accepted solution]

Hi Yogesh,

I don´t think this can be changed. The APO application tells you which was the APO process that has created the order. In this case, it PPDS.

Kind Regards,

Mariano

[sourabh_jain66 · Accepted solution]

Hi YR,

By default any transaction starting with RRP* is the PPDS transaction.

The program /SAPAPO/RRP_SR_ATP_GENERATE is using PPDS as an application at the base, that's why the APO application is 2 in RRP3.

I agree with Mariano that it can't be changed, without putting a lot of efforts.

Rgds

Sourabh