ATP and calendars

[Former Member]

Does anyone know where a good place to find information on how SAP ATP and calendars (plant, shipping point, customer master) work?

We have our plant & shipping point calendar blocked for certain days and if a product is not in stock ATP takes into account these days, but if the item is in stock it will commit to ship during the timeframe that the shipping calendar (shipping point) is blocked as non-work days.

Thanks for any input.

[eduardo_hinojosa]

Hi Vicki

Please, see these notes:

SAP Note 321803 - Explanatory notes on the ATP Customizing

SAP Note 457787 - Collective SAP note: Advice notes ATP check

SAP Note 835219 - FAQ: ATP composite note

and related notes

Regards

Eduardo

[former_member223981]

I am not sure if there is any standard documentation regarding this but the following may help you.

Scheduling begins with the requested delivery date (Also in the first date field of the item). The system will work backwards from this date to determine the other dates. So lets take the following example:

Backwards scheduling is triggered:

1. System checks the requested delivery date against the route calendar maintained in 0VTC

2. System determines the GI date (Delivery date u2013 transit duration) and checks against the route calendar

3. System checks the GI date against the loading calendar (Maintained in shipping point, tx OVLZ)

4. System determines the loading date (GI Date u2013 Loading time) and checks against the loading calendar (Maintained in shipping point, tx OVLZ)

5. System determines the requested material availability date (Loading date u2013 pick/pack time) and checks against the pick/pack calendar (Maintained in shipping point, tx OVLZ)

If the backwards scheduling determines dates in the past, a forwards scheduling may be triggered:

1. The material availability date = today (SY-DATLO)

2. The material availability date is checked against the pick/pack calendar (Maintained in shipping point, tx OVLZ)

3. System determines the loading date (Material availability date + Pick/Pack time) and checks against the pick / pack calendar (Maintained in shipping point, tx OVLZ)

4. System determines the Goods Issue Date (Loading Date + Loading time) and checks against the loading calendar (Maintained in shipping point, tx OVLZ)

5. GI Date is checked against the route calendar is the route calendar differs to shipping point calendar

6. Delivery Date is determined and system checks it against the route calendar

Note that the above is only true for some if you have loading times, pick/pack times, route transit times maintained. If you donu2019t have these maintained, the system will just automatically take the date value from the preceding step without checking against a calendar. The above example is also only relevant when the availability check finds the confirmed quantity on the requested date. When this does not occur, further scheduling is required which is not discussed in the above example.

Hope this helps.