6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations

Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations

When a sales order line item is entered, agreeing on a delivery date involves far more than simply checking if goods exist in a warehouse. Physical products must be picked from storage bins, packed into shipping cartons, staged on loading docks, loaded onto commercial freight vehicles, and transported over highways, railways, or oceans to the buyer's receiving facility. Delivery and Transportation Scheduling in SAP S/4HANA calculates the exact operational milestones required to fulfill customer orders on time.

Delivery scheduling ensures that warehouse and shipping operations operate smoothly. If picking begins too late, shipments miss carrier departures; if picking begins too early, warehouse staging areas become congested with idle inventory.

---

The Four Operational Time Elements

Delivery scheduling calculates schedule dates by evaluating four discrete time duration elements. These elements originate from distinct master data and customizing structures across Sales (SD), Materials Management (MM), and Logistics Execution (LE):

                                OPERATIONAL TIME ELEMENTS
  ┌─────────────────────────────────────┬─────────────────────────────────────┐
  │        Route-Based Durations        │    Shipping Point-Based Durations   │
  ├─────────────────────────────────────┼─────────────────────────────────────┤
  │ 1. Transit Time                     │ 3. Loading Time                     │
  │    (Table TVRO / Route)             │    (Shipping Point + Loading Group) │
  │                                     │                                     │
  │ 2. Transportation Lead Time         │ 4. Pick/Pack Time                   │
  │    (Table TVRO / Route)             │    (Shipping Point + Weight Group)  │
  └─────────────────────────────────────┴─────────────────────────────────────┘

1. Transit Time (Route)

• Definition: The total calendar or working time required for a transport vehicle to carry freight from the delivering shipping point to the customer's ship-to dock.
• Source: Maintained in the Route definition (transaction 0VTC).
• Calendar Used: Evaluated against the Route Transit Calendar (or Customer Receiving Calendar).

2. Transportation Lead Time / Planning Time (Route)

• Definition: The lead time necessary to arrange shipping logistics, book freight carriers, schedule container pickups, and compile commercial export/customs documentation.
• Source: Maintained in the Route definition.
• Calendar Used: Evaluated against the Shipping Point Factory Calendar or Route Planning Calendar.

3. Loading Time (Shipping Point + Loading Group)

• Definition: The operational time needed to physically transfer packed pallets or cartons onto the carrier's truck, railcar, or shipping container.
• Source: Taken from the Shipping Point. Depending on the determination rule in the shipping point, it can be a fixed value or depend on the route and the Loading Group (Material Master Sales: General/Plant view, MARC-LADGR).
• Calendar Used: Evaluated against the Shipping Point Factory Calendar.

4. Pick/Pack Time (Shipping Point + Weight Group)

• Definition: The time required by warehouse staff to retrieve materials from storage racks, verify serial numbers, pack into containers, and affix shipping labels.
• Source: Taken from the Shipping Point. Depending on the determination rule, it can be a fixed value or depend on the route and the weight group.
• Calendar Used: Evaluated against the Shipping Point Factory Calendar.

---

The Backward Scheduling Sequence: Calculating Milestones from the Requested Date

When a sales representative creates an order, the customer specifies a Requested Delivery Date (RDD). SAP automatically initiates Backward Scheduling to determine when warehouse and shipping operations must begin. Backward scheduling operates in reverse chronological order:

Requested Delivery Date (Customer Dock)
       │
       ▼  minus Transit Time (Route)
Goods Issue Date (PGI at Shipping Point)
       │
       ▼  minus Loading Time (Shipping Point + Loading Group)
Loading Date (Staged at Dock)
       ├──► minus Transportation Lead Time (Route)  ──► Transportation Planning Date
       │
       └──► minus Pick/Pack Time (Shipping Point)   ──► Material Availability Date (MAD)

Mathematical Formulation of Backward Scheduling Dates

1. Goods Issue Date (GI Date): $\text{Goods Issue Date} = \text{Requested Delivery Date} - \text{Transit Time}$
   Significance: The date by which physical goods issue (PGI) must be posted and the truck must depart the shipping point.

2. Loading Date: $\text{Loading Date} = \text{Goods Issue Date} - \text{Loading Time}$
   Significance: The date on which loading the carrier vehicle must commence.

3. Transportation Planning Date (TP Date): $\text{Transportation Planning Date} = \text{Loading Date} - \text{Transportation Lead Time}$
   Significance: The date by which transport must be scheduled with freight forwarders.

4. Material Availability Date (MAD): $\text{Material Availability Date} = \text{Loading Date} - \text{Pick/Pack Time}$
   Significance: The date on which goods must be physically assembled, manufactured, or received into stock so picking and packing can begin.

---

Forward Scheduling: Triggers and Calculation Sequence

Backward scheduling represents the ideal path. However, backward scheduling cannot always be fulfilled. SAP triggers Forward Scheduling under either of two specific conditions:

1. The Historical Date Trigger: Backward scheduling calculates a Material Availability Date or a Transportation Planning Date that lies in the past (i.e., earlier than the current order entry date SY-DATUM). Because warehouse staff cannot pick goods yesterday, backward scheduling fails.
2. The Inventory Deficit Trigger: The ATP check executed on the calculated Material Availability Date reveals that inventory is insufficient. The ATP check determines a future date when stock will actually be available (e.g., after an inbound PO arrival or after the Replenishment Lead Time).

Forward Scheduling Sequence

When forward scheduling is triggered, the system abandons the backward timeline and recalculates forward from the earliest feasible starting point:

• Baseline Starting Date: Set to the latest of Current Date (SY-DATUM) and the Confirmed Material Availability Date returned by the ATP check.
• Step 1: Confirmed Material Availability Date (MAD) is locked.
• Step 2: Confirmed Loading Date: $\text{Confirmed Loading Date} = \max(\text{Confirmed MAD} + \text{Pick/Pack Time},\, \text{Current Date} + \text{Transportation Lead Time})$
• Step 3: Confirmed Goods Issue Date: $\text{Confirmed Goods Issue Date} = \text{Confirmed Loading Date} + \text{Loading Time}$
• Step 4: Confirmed Delivery Date: $\text{Confirmed Delivery Date} = \text{Confirmed Goods Issue Date} + \text{Transit Time}$

The Schedule Line Resolution in the Sales Order

When forward scheduling occurs, SAP creates two schedule lines in the sales order item (VBEP):

• Schedule Line 1: Records the customer's original Requested Delivery Date with Confirmed Quantity = 0.
• Schedule Line 2: Records the system's newly calculated Confirmed Delivery Date with Confirmed Quantity = Requested Quantity.

---

The Critical Role of Working Day Factory Calendars

Date arithmetic in delivery scheduling is not simple 24-hour calendar addition; it must respect Factory Calendars. Each operational milestone is governed by a specific organizational calendar:

Worked Scheduling Example Across Factory Calendars

Consider the following real-world scenario:

• Order Entry Date: Monday, October 12, 2026
• Customer Requested Delivery Date: Friday, October 16, 2026
• Customer Receiving Calendar: Standard 5-day work week (Monday–Friday; closed Saturday/Sunday)
• Shipping Point Calendar: Standard 5-day work week (Monday–Friday; closed Saturday/Sunday)
• Route Transit Calendar: 7-day transport calendar (commercial trucking drives over weekends)
• Operational Durations:
  • Transit Time: 2 days
  • Loading Time: 1 day
  • Transportation Lead Time: 1 day
  • Pick/Pack Time: 2 days

Backward Scheduling Execution:

1. Requested Delivery Date: Friday, Oct 16. (Valid customer workday).
2. Goods Issue Date: Oct 16 minus 2 days Transit = Wednesday, Oct 14. (Valid shipping point workday).
3. Loading Date: Oct 14 minus 1 day Loading = Tuesday, Oct 13. (Valid shipping point workday).
4. Transportation Planning Date: Oct 13 minus 1 day Transp Lead Time = Monday, Oct 12. (Valid workday, equals today SY-DATUM $\rightarrow$ OK).
5. Material Availability Date: Oct 13 minus 2 working days of pick/pack time on the shipping point calendar = Friday, October 9 (Monday, October 12 is the first working day back and Friday, October 9 the second, because the weekend is not a working day).
   • Because Friday, October 9 is in the past relative to the order entry date (Monday, October 12), backward scheduling fails.

Forward Scheduling Execution:

1. New Material Availability Date: Set to earliest valid workday: Monday, October 12.
2. Confirmed Loading Date: Oct 12 + 2 workdays Pick/Pack = Wednesday, October 14. (Check Transp Planning: Oct 12 + 1 day = Tuesday, Oct 13 $\le$ Oct 14 $\rightarrow$ OK).
3. Confirmed Goods Issue Date: Oct 14 + 1 workday Loading = Thursday, October 15.
4. Transit Time Addition: Oct 15 + 2 calendar days (7-day carrier calendar) = Saturday, October 17.
5. Customer Calendar Shift: Saturday, Oct 17 is a non-working day on the customer's receiving calendar! The shipment cannot be unloaded until the next customer receiving day: Monday, October 19.

• Result: Order item confirmed for Monday, October 19.

Daily Scheduling, Precise Scheduling, and the Delivery Creation Date

The scheduling logic is chosen per shipping point:

• Daily scheduling calculates with days, hours, and minutes but displays only the resulting dates, and it uses the factory calendar of the shipping point.
• Precise scheduling is active when working times are maintained for the shipping point (a calendar that matches the shipping point's factory calendar plus a shift sequence with start and end times per weekday). The results are calculated and displayed to the minute, and pick/pack and loading times are maintained in hours and minutes.

Both use the route's factory calendar for the days on which the route runs. Precise times do not influence the availability check: ATP compares stock on the material availability date only.

When you create the outbound delivery, forward scheduling can run again if the material availability date in the order has already passed; the delivery type decides whether rescheduling happens. To leave enough time for all shipping activities, create the delivery on the earlier of the material availability date and the transportation planning date. Enter that date as the selection date (single delivery), the delivery creation date (collective processing), or the planned creation date in the Create Outbound Deliveries From Sales Orders app. Routes can also have route schedules, which fix departure times for a route (see SAP Note 146829).