SD Scheduling
SD Scheduling
Symptom
This Knowledge Base Article explains the relevant customizing and the process flow of SD scheduling in the
ERP system.
Environment
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.
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 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
Usually the system starts with a backwards scheduling starting from the requested delivery date.
The requested delivery date will be checked against the factory calendar of the unloading point, and the
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.
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:
Keywords
Products
Other Components
Component Description
1880353 Delivery date shifted into the future with route schedules