Skip to main content

Delivery Scheduling functionality in SAP SD





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 -> Assign Delivery Type and Checking Rule
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 -> Assign Delivery Type and Checking Rule According to 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


Referred from "SAP Note  : 2221849 - Customizing and process flow of ERP SD scheduling"

Comments

  1. Thanks for sharing article about Delivery Scheduling functionality in SAP SD as i got for more information about detaIed explaation Delivery Scheduling functionality in Sales and Distribution.Visit now SAP SD Online Training in Hyderabad if you are looking to learn SAP SD skills.

    ReplyDelete
  2. hi, your posts about sd are nice, am following you. today's blog about delivery scheduling functionality in SAP SD is explained well, thanks for sharing.

    ReplyDelete
  3. This comment has been removed by the author.

    ReplyDelete
  4. wow... what a great blog, this writter who wrote this article it's realy a great blogger, this article so inspiring me to be a better person
    Definition of SAP

    ReplyDelete
  5. TBH this is the only link i got all the info about customization i needed, Thanks :)

    ReplyDelete
  6. Great blog Lots of information to Read...Great Man Keep Posting and update to People. Thanks Kevin Costner Yellowstone Season 03 Vest

    ReplyDelete

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...