MRP Rescheduling Horizon equivalent in APO-SNP?

[former_member1050990]

Hi all,

In (ECC) MRP we currently use the Rescheduling Horizon to limit creation of purchase requisitions when an actual Purchase Order already exists (but is outside the standard lead time).

e.g. Lead Time = 7 days.  Rescheduling Horizon = 50 days

If requirement to reorder exists in 5 days time, and we have actual PO due in 14 days time that can cover it, then no new PurReq is created.

We're now moving to APO-SNP to generate our purchase requisitions.

Is there an equivalent field in APO-SNP we can use to accomplish the same result?

Many thanks,

Greg

[Former Member]

Hi Gerg

Can you check SNP Stock Transfer Horizon field in the APO master data in SNP2 tab in T-code /SAPAPO/MAT1.

Use in SNP:-

Enter the number of days, weeks, or months during which the system is not to plan stock transfers. The time period starts on the system date (or if required, the date specified in the Planning Start Date field of the planning book or in the PDATE user exit for background processing). The system does not generate any planned distribution receipts within this horizon; instead, it moves them to the first day after the SNP stock transfer horizon

Please request you to check the topic and let´s know if it helps.

If this already answer your question follow How to close a discussion and why

Thanks

Amol

[former_member1050990]

Thank you for your response.

Unfortunately, after some testing, I find the SNP Stock Transfer Horizon is not delivering the same result that the Rescheduling Horizon does.

Particularly, it seems to force all purchase requisitions outside of the horizon. And is acting like a Time Fence.

Whereas, we do actually want PurReqs to drop within this horizon if there is no firm incoming order already placed.

It should only be when a firm PO exists within the horizon (to cover the total demand) that the PurReq does not create.

Is there any other field/setting in APO that could deliver this result?

Regards,

Greg

[kenneth_snyder]

No, there is nothing like that for SNP.  PPDS has options but SNP does not.

Using time buckets you can "aggregate" supply into a particular time bucket so any orders in the same time bucket are considered available in beginning of time bucket but I think that is a bad idea.

CTM can peg to existing supply first before creating new supply elements.

Optimizer you can set delay costs so small that it will utilize existing supply before procuring additional supply.

But these are only workarounds.

Ken