SAP Knowledge Base Article

2221849 - Customizing and process flow of SD scheduling

Component: LE-SHP-GF-DS (Delivery and transport scheduling), Version: 6, Released On: 30.03.2021

Symptom
This Knowledge Base Article explains the relevant customizing and the process flow of SD scheduling.

Environment
Sales And Distribution (SD)
Logistics Execution (LE)
SAP ERP SD scheduling (LE-SHP-GF-DS)
SAP R/3
SAP R/3 Enterprise 4.7
SAP ERP Central Component
SAP ERP
SAP Enhancement package for SAP ERP
SAP Enhancement package for SAP ERP, version for SAP HANA
SAP S/4 HANA

Resolution
The aim of the scheduling is to determine the goods issue date, loading date, material availability date, the transportation
planning date and when necessary a new delivery date.
Customizing:

Sales documents:
The delivery and transportation scheduling can be activated in transaction OVLY.
Customizing path: Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation
Scheduling -> Define Scheduling By Sales Document Type
It is controlled by the document type.

Deliveries:
For deliveries you have to consider the setting in transaction 0VLK. Field 'Rescheduling' controls whether a new
scheduling is carried out.

Stock transport documents:

In stock transport documents you also have the possibility to use the SD scheduling functionality. If you do not
activate it then an MM scheduling is carried out.
Customizing path: Materials Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -
> Configure Delivery Type & Availability Check Procedure by Plant
or when using the functionality of Stock transport orders between storage location:
Materials Management -> Purchasing -> Purchase Order -> Set up Stock Transport Order -> Set Up Stock Transfer
Between Storage Locations -> Configure Delivery Type & Availability Check Procedure by Storage Location

Replenishment deliveries:
Regarding replenishment deliveries please have a look at SAP Note 215664.
 Calendar
During SD scheduling the system can take into account three different calendars:

Calendar at the shipping point: The calendar for the shipping point you can maintain under the following
customizing path: Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation Scheduling
-> Maintain Duration
This calendar is used for the calculation of the transportation planning date, material availability date, loading date
and goods issue date.

Calendar at the route: This calendar is used for the calculation of the transportation. You can maintain this under:
Customizing path: Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation
Scheduling -> Maintain Duration
If no calendar is maintained at the route then the calendar at the shipping point is used.

In the customer master you can define Unloading Points. The unloading point determines when your customer is
able to receive the goods. You have the possibility to assign a factory calendar and working hours to your receiving
point.
The requested delivery date is checked against the factory calendar at the unloading point. If no calendar is
maintained then the requested delivery date can lie on non-working days due to your calendar assigned to the
shipping point. Please check SAP Knowledge Base Article 1579665.
The check happens in function module SD_DELIVERY_DATE_CHECK.
The calendars must be maintained at least three years into the future!

Working times:
SD scheduling can be carried out exact to days or exact to seconds. This depends on whether you are working with
working times. In the customizing you have to define working times for your shipping point.
Customizing path: Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation
Scheduling -> Maintain Working Hours
These working times you have to assign to the shipping point under:
Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation Scheduling -> Maintain
Duration

Determined dates:

Goods issue date

In case of backwards scheduling: goods issue date = delivery date – transit time
In case of forwards scheduling: goods issue date = loading date + loading time

The transit time is the time that is required to deliver the goods from your site to your customer. The transit time is
defined in the route.
Customizing path: Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation
Scheduling -> Maintain Duration

The loading time is the time that is required for loading the shipment. It can be maintained as default for the
shipping point, for the combination of shipping point and route or for the combination shipping point, route and
loading group.
Customizing path: Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation
Scheduling -> Maintain Duration

Loading date
In case of backwards scheduling: loading date = goods issue date – loading time
In case of forwards scheduling: loading date = transportation planning date + transportation planning time

The loading time is the time that is required for loading the shipment. It can be maintained as default for the
shipping point, for the combination of shipping point and route or for the combination shipping point, route and
loading group.
Customizing path: Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation
 Scheduling -> Maintain Duration

Material Availability date

In case of backwards scheduling: material availability date = loading date – pick pack time
In case of forwards scheduling: material availability date = loading date – pick pack time or current date

The pick/pack time is the time that is required for allocating goods to a delivery as well as the time that is required
for picking and packing.
The pick/pack time can be maintained as default for the shipping point. Furthermore for the combination of
shipping point and route or the combination of the shipping point route and weight group.
Customizing path: Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation
Scheduling -> Maintain Duration

Transportation Planning date

In case of backwards scheduling: transportation planning date = loading date – transportation planning time
In case of forwards scheduling: current date or transportation planning date = loading date – transportation
planning time

Delivery date
If the requested delivery cannot be kept a forwards scheduling will calculate a new delivery date:
Delivery date = goods issue date + transit time

Process logic of the scheduling:

Usually the system starts with a backwards scheduling starting from the requested delivery date.

Exception: Transaction Co06 always carries out ONLY a forwards scheduling.

The requested delivery date will be checked against the factory calendar of the unloading point, and the arrival time will
be set according to the beginning of the receiving hours, in other words, to the opening time of the unloading point.
From coding point of view this happens in subroutine function module SD_DELIVERY_DATE_CHECK. Please also
consider SAP Knowledge Base Article 1579665.
All other dates and times will be determined in backwards scheduling. If one of the dates or times lies in the past the
system automatically switches to forwards scheduling. In transaction OVLY (Customizing path: Sales and Distribution -
> Basic Functions -> Delivery Scheduling and Transportation Scheduling -> Define Scheduling By Sales Document
Type) you can control that the system does not switch to a forwards scheduling when the material availability lies in the
past. Please also check the related debugging guide (SAP Knowledge Base Article 2220102) for further information. If
the system has to switch to forwards scheduling then the transportation planning date or the material availability date
will be set to the current date. Starting from this the other dates will be calculated considering the maintained times. The
newly calculated delivery date will be checked against the factory calendar at the unloading point and also against the
working times. It can happen that the delivery date and time has to be shifted further into the future. In other words, to
the next working day and time of the unloading point. In this case a new backwards scheduling is carried out from that
date and time.

These dates and times can still be changed by the route schedule scheduling which is called right after SD scheduling.
Regarding route schedule determination please check SAP Knowledge Base Articles 1750978, 2150219.
Please consider the document for route schedule scheduling.

The final result of the scheduling, or better to say, the determined material availability date will be passed over to the
ATP check. The ATP check is carried out for this date. If the date can be confirmed everything is fine. If the ATP check
can only confirm on a later date then the new material availability date will be passed again to the scheduling and a
forwards scheduling is carried out starting from this date.
 Time stream:
Scheduling uses time streams. The time streams are stored in table TTSTR. Please consider SAP Note 169885 and SAP
Knowledge Base Article 2140434.

Troubleshooting Guide:

Delivery Date or another date falls on a non-working date

Please check the customizing and the time stream according to SAP Knowledge Base Article 1579665.

Changes in the factory calendar are not considered while scheduling

The system works with streams during the scheduling. When you e.g. change the factory calendar in your test
system then the time stream will be deleted and will be newly generated when needed. But when you move the
changes of the factory calendar to another system (e.g. productive system) via a Transport then the time stream will
not be updated. You have to delete the time streams manually. Please consider SAP Note 169885. Whenever you
carry out such changes it is recommended to delete the streams via the report mentioned in the SAP Note. The
reports run only a few seconds and you will not get any success information when the report has finished. The
report can be used safely at any time. The time streams will be automatically generated when needed.

Unexplainable dates are determined while scheduling

There are several cases where the time stream cannot be built up correctly or where you receive not explainable
dates. Usually this is caused by wrong customizing:
Factory calendar validation is not sufficient. Please make sure that the factory calendar is maintained at least
three years into the future.
Factory calendars (shipping point, route, unloading point) are not harmonized. The same is valid for the
working times and the factory calendar at the unloading point. It makes no sense to maintain e.g. working
times for Monday whereas it is a non-working day due to the factory calendar.
Shift definitions for the shipping point are not valid any more. Please make sure that the shifts are valid
(Customizing path: Sales and Distribution -> Basic Functions -> Delivery Scheduling and Transportation
Scheduling –> Maintain Working Hours).
Inconsistencies in the time stream -> See SAP Note 169885

Confirmed delivery date lies before requested delivery date

This can happen when you are using rout schedules and the specific transit time of the route schedule is not the
same as the transit time in the route. Please consider SAP Note 146829.

Issues regarding route schedule scheduling

Please check SAP Knowledge Based Article 1880353 and SAP Note 146829.

Delivery date is earlier then the Goods Issue Date

This can happen when you are working with time zones. The delivery date is displayed in the time zone of the ship-
to-party. All other dates will be displayed in the time zone of the shipping point. Please consider SAP Knowledge
Based Article 1890212.

Keywords
Versandterminierung, Transportterminierung, Vorwärtsterminierung, Rückwärtsterminierung, Verfügbarkeitsprüfung,
Materialbereitstellungsdatum, Transportdispositionsdatum, Ladedatum, Warenausgangsdatum, Einteilungsdatum,
Verkaufsbeleg, Lieferbeleg, Einkaufsbeleg, Nachschublieferung, Fabrikkalender, Versandstelle, Arbeitszeiten,
Wunschlieferdatum, Richtzeit, Ladezeit, Transitzeit, Teitstrahl, Vorwärtsterminierung, Rückwärtsterminierung,
Verfügbarkeitsprüfung, Auftragsart, Zeitzone, 311, EWM,
 Attributes
Key Value

Other Components MM-PUR-GF-STO (Stock Transfer)

Other Components SD-BF-AC (Availability Check)

Other Components CA-ATP-SCH (ATP: Scheduling)

Products
Products

SAP ERP Central Component all versions

SAP ERP all versions

SAP R/3 Enterprise all versions

SAP R/3 all versions

SAP S/4HANA all versions

SAP enhancement package for SAP ERP all versions

SAP enhancement package for SAP ERP, version for SAP HANA all versions

This document refers to

SAP Note/KBA Component Title

2220102 LE-SHP-GF-DS Debugging guide for SD scheduling

2150219 LE-SHP-GF-RS Troubleshooting guide for route schedules (ERP)

2140434 LE-SHP-GF-DS Troubleshooting guide for ERP SD scheduling

1890212 LE-SHP-GF-DS Delivery date / goods issue date seems to be incorrect

1880353 LE-SHP-GF-RS Delivery date shifted into the future with route schedules

1750978 LE-SHP-GF-RS Route Schedule does not populate on sales order

1579665 LE-SHP-GF-DS Scheduling - Date lies on a non-working day

This document is referenced by

SAP Note/KBA Component Title

2215897 Incorrect dates in the first schedule line of sales documents

2196410 SD-BF-AC Everything about ERP ATP check and SD scheduling