SD Delivery Processing Part 3: Collective Delivery Creation, Scheduling and Route Determination

📌 KEY POINTS
✅ VL10 (delivery due list) selects due order items by shipping point and date and creates deliveries in the foreground or background.
✅ Split criteria (ship-to, shipping point, route, dates, incoterms…) decide how items are grouped into deliveries.
✅ Complete delivery and partial delivery rules (customer master, info record, order) control whether orders may be split or partially shipped.
✅ Route = departure zone (shipping point) + shipping condition + transportation group (material) + transportation zone (ship-to), determined in 0VRF.
⚠️ Missing transportation zone on the ship-to or transportation group on the material = no route, wrong scheduling.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 2 configured deliveries. Now creating them at scale and scheduling them correctly.

━━━━━━━━━━━━━━━━━━━━
▶ 1. DELIVERY DUE LIST (VL10)

• Variants: by shipping point, route, ship-to, date (material availability or loading date).
• Background jobs for routine creation; log for failures.
• User roles for different warehouses.

━━━━━━━━━━━━━━━━━━━━
▶ 2. SPLIT AND COMBINATION

• Deliveries combine items of several orders if split criteria match (order combination flag in customer/order).
• Additional split via copy control data transfer routines.

━━━━━━━━━━━━━━━━━━━━
▶ 3. COMPLETE AND PARTIAL DELIVERY

• Complete delivery: all items together.
• Partial delivery per item: allowed, one-time, not allowed.
• Maintained in customer master (sales area) or customer-material info record.

━━━━━━━━━━━━━━━━━━━━
▶ 4. SCHEDULING

• Delivery scheduling: pick/pack time (shipping point, route, weight group), loading time.
• Transportation scheduling: transportation lead time, transit time (route).
• Backward from requested date; forward if not feasible.

━━━━━━━━━━━━━━━━━━━━
▶ 5. ROUTE DETERMINATION

• 0VRF: departure country/zone + shipping condition + transportation group + destination country/zone → route.
• Route redetermination in delivery with weight group.
• Routes carry transit times and calendars.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

1. Maintain transportation zone on ship-to and transportation group on material.
2. Define routes and route determination.
3. Create orders and check route and dates.
4. Run VL10 in background and review the log.

✅ CHECKPOINT: orders get the right route, dates follow route transit times, and VL10 creates combined deliveries.

A client complained that all deliveries to a new region were one day late. The ship-to customers had been created without transportation zones, so route determination used a default route with zero transit time and backward scheduling started too late. Maintaining transportation zones (mass change) and a proper route with two transit days fixed scheduling. A validation was added to BP creation requiring a transportation zone for ship-to parties.

• Missing transportation zones or groups.
• Routes without realistic transit times.
• Ignoring complete/partial delivery settings.
• Running VL10 without reviewing the log.
• Unexpected splits due to different shipping points or routes.

• Validate route master data at customer and material creation.
• Maintain realistic scheduling times with logistics.
• Use background VL10 jobs with monitored logs.
• Review split behavior with customers' delivery requirements.
• Document route determination tables.

Questions: "How is the route determined?", "How does delivery scheduling work?", "What does VL10 do?"
Strong answer: 0VRF from departure zone, shipping condition, transportation group, transportation zone; scheduling with pick/pack, loading, transportation lead and transit times; VL10 collective creation by shipping point and date with split criteria and complete/partial rules.