7.2 Shipping Point Determination and Route Determination Mechanics

Shipping Point Determination and Route Determination Mechanics

In SAP S/4HANA Sales, shipping and outbound logistics represent the critical transition where commercial agreements recorded in a sales order materialize into physical fulfillment. Before a warehouse can pick a single box or load a truck, the system must resolve two foundational logistics questions: Where will the shipment originate? and How will the goods travel to the customer?

These questions are answered by Shipping Point Determination and Route Determination. Both mechanisms execute automatically during sales order entry and are re-evaluated during outbound delivery generation. Mastering their underlying customizing rules, data origins, and the delivery split logic they impose is indispensable for configuring Order-to-Cash (O2C) flows.

---

The Shipping Point: The Central Organizational Unit in Shipping

The Shipping Point (VSTEL) is the primary organizational unit of Logistics Execution (LE-SHP). It represents the physical or logical facility from which outbound shipments are dispatched. A shipping point may correspond to a specialized loading ramp, a warehouse packing bay, a rail siding, a tanker pumping station, or a dedicated courier dispatch office.

Architectural Cardinality with Plants

In the SAP Enterprise Structure, the assignment of shipping points to plants obeys a flexible many-to-many (M:N) relationship:

• A single Plant can be assigned to multiple Shipping Points. For example, Plant 1000 might assign Shipping Point 1001 (Bulk Liquids / Tanker Ramp), 1002 (Heavy Freight / Crane Ramp), and 1003 (Standard Package Depot).
• A single Shipping Point can be assigned to multiple Plants, provided those plants are physically contiguous or share the same physical dispatch yard.

  Plant 1000 (Manufacturing Site A) ──────┬─────> Shipping Point 1001 (Express Parcel Ramp)
                                           ├─────> Shipping Point 1002 (Heavy Pallet Dock)
  Plant 1010 (Assembly Site B) ────────────┴─────> Shipping Point 1003 (Hazardous Chemical Bay)

The Inviolable 1:1 Delivery Header Rule

While a plant can host many shipping points, SAP enforces an inviolable architectural rule at the execution level:

$$\mathbf{1\text{ Outbound Delivery Document Header (LIKP)}} \Longleftrightarrow \mathbf{1\text{ Shipping Point (LIKP-VSTEL)}}$$

Every outbound delivery document created in SAP S/4HANA belongs to exactly one shipping point. A single delivery document can never combine line items originating from different shipping points. If a sales order contains five line items and two distinct shipping points are determined, the system strictly mandates at least two independent delivery documents.

Operational Responsibilities of the Shipping Point

The shipping point is far more than an organizational label; it controls essential scheduling and execution parameters:

• Working Hours and Shift Calendars: Specifies the operating hours (e.g., 07:00–16:00) and factory calendar governing warehouse dispatch work.
• Determines Pick/Pack and Loading Times: Establishes the duration required to assemble, stage, and physically load goods onto transport vehicles.
• Address for Departure: Provides the originating country and postal departure zone used in Route Determination.
• Default Storage Location Determination: Serves as a key, together with the delivering plant and the storage condition, for determining the picking storage location with rule MALA.

---

Shipping Point Determination: The 3-Field Rule (Transaction OVL2)

During sales document line item creation (transaction VA01), the system automatically derives the proposed Shipping Point (VBAP-VSTEL) using a standardized 3-field rule evaluated against customizing table TVSTZ (transaction OVL2).

$$\text{Shipping Condition (VSBED)} + \text{Loading Group (LADGR)} + \text{Delivering Plant (WERKS)} \Longrightarrow \text{Proposed Shipping Point} + \text{Allowed Alternatives}$$

[ Sold-to Master / Order Type ]      [ Material Master Sales: Gen/Plant ]     [ CMIR / Ship-to / Material Master ]
       Shipping Condition                       Loading Group                             Delivering Plant
            (VSBED)                                (LADGR)                                    (WERKS)
               │                                      │                                          │
               └──────────────────────────────┬───────┴──────────────────────────────────────────┘
                                              ▼
                                [ Customizing Table TVSTZ (OVL2) ]
                                              │
                                ┌─────────────┴─────────────┐
                                ▼                           ▼
                     Proposed Shipping Point     Allowed Alternative Shipping Points
                          (Default)                  (Manual Selection in VBAP)

1. Shipping Condition (VSBED)

The Shipping Condition reflects the agreed commercial fulfillment urgency or transport method required by the buyer.

• Primary Data Source: Customer Master / Business Partner record of the Sold-to Party under the Sales Area Data $\rightarrow$ Shipping Tab (KNVV-VSBED). Note that even though goods are physically delivered to the Ship-to party, the contractual shipping condition is negotiated with and derived from the Sold-to Party.
• Document Type Override: Customizing for the Sales Document Type (VOV8) contains an optional Shipping Condition field. If maintained at the document type level, it overrides the customer master setting. For example, a rush order type can carry shipping condition 10 (immediately), which then overrides the customer master default.

2. Loading Group (LADGR)

The Loading Group identifies the technical equipment, handling method, or physical facility required to load the material onto transport equipment.

• Data Source: Maintained in the Material Master on the Sales: General/Plant Data view (table MARC-LADGR).
• Typical Values: 0001 (Forklift / Pallet), 0002 (Overhead Crane / Heavy Girder), 0003 (Pumping Station / Liquid Bulk), 0004 (Manual Loading / Hand Parcel).

3. Delivering Plant (WERKS)

The Delivering Plant identifies the manufacturing facility or distribution center from which inventory will be supplied.

• Determination Hierarchy in Sales Orders:
  1. Customer-Material Information Record (CMIR) (KNMT-WERKS): Highest priority; reflects customer-specific sourcing agreements.
  2. Ship-to Party Master (KNVV-VWERK): Sourced from the customer master of the receiving party.
  3. Material Master Sales Org 1 View (MVKE-DWERK): Default delivering plant for the material in the specified sales organization and distribution channel.

Customizing Table TVSTZ (Transaction OVL2)

When all three parameters are resolved, the system searches customizing table TVSTZ for an exact match. If found, it populates the Proposed Shipping Point into VBAP-VSTEL and stores any configured Alternative Shipping Points.

Manual Overrides and Validation

A sales representative can manually change the proposed shipping point at the line item level (VBAP-VSTEL), but only to one of the Allowed Alternative Shipping Points explicitly configured in OVL2 for that specific combination of Shipping Condition, Loading Group, and Plant. If any other shipping point is entered, the system rejects it.

---

Route Determination: The 4-Field Rule (Transaction 0VRF / Table TROLZ)

The Route (ROUTE) in SAP S/4HANA specifies the geographic path, transportation stages, modes of transport (road, rail, sea, air), and transit duration linking the shipping facility to the customer destination. In addition to guiding freight carriers, the route is the core driver of Delivery Scheduling, as it dictates Transit Time and Transportation Lead Time.

The 4-Field Determination Key (Transaction 0VRF / Table TROLZ)

During order entry and delivery processing, the system determines the route based on four parameters:

$$\begin{aligned} \text{Departure Country + Departure Zone (Shipping Point)} & \\ +~\text{Shipping Condition (Sold-to Master / Order Type)} & \\ +~\text{Transportation Group (Material Master)} & \\ +~\text{Destination Country + Transportation Zone (Ship-to Master)} & \Longrightarrow \mathbf{\text{Route}} \end{aligned}$$

[ Shipping Point Customizing ]              [ Sold-to Master / Order Type ]
 Departure Country / Zone                          Shipping Condition
     (ALAND / AZONE)                                    (VSBED)
           │                                               │
           └───────────────────────┬───────────────────────┘
                                   │
                                   ▼
                  [ Customizing Table TROLZ (0VRF) ] <── Weight Group (Optional)
                                   ▲
           ┌───────────────────────┴───────────────────────┐
           │                                               │
[ Material Master: MARC-TRAGR ]              [ Ship-to BP: KNA1-LZONE / ADRC ]
     Transportation Group                        Destination Country / Zone
           (TRAGR)                                     (LAND1 / LZONE)

Deep Breakdown of the 4 Key Elements

1. Departure Country and Departure Zone of the Shipping Point:
   • Derived from the determined Shipping Point (its country and departure zone). Configured under Enterprise Structure definition for Logistics Execution.
2. Shipping Condition (VSBED):
   • Inherited from the sales document header, which originates from the Sold-to Party customer master or the sales document type override.
3. Transportation Group (TRAGR):
   • Maintained in the Material Master record on the Sales: General/Plant Data view (stored at client level, MARA-TRAGR). It classifies materials based on physical transportation demands (e.g., 0001 Standard Dry Box, 0002 Temperature-Controlled Refrigerator, 0003 Liquid Bulk Tanker, 0004 Hazardous Flatbed).
4. Destination Country and Transportation Zone of the Ship-to Party:
   • Sourced from the customer master address of the Ship-to Party (KNA1-LAND1 and KNA1-LZONE / ADRC-ZONE1). While the Shipping Condition comes from the Sold-to, the geographic destination is governed strictly by the Ship-to.

Route Determination Configuration Table (TROLZ)

---

Weight-Dependent Route Determination

In high-volume distribution networks, shipping freight costs vary drastically by payload weight. Sending a 50 kg spare part via a full truckload freight carrier is economically inefficient, while sending a 25,000 kg order via parcel express is prohibitively expensive.

SAP supports Weight-Dependent Route Determination by adding weight groups to route determination (table TROLZ):

1. Weight Groups are defined in customizing with upper weight limits (e.g., Weight Group WG01 up to 500 kg, WG02 up to 5,000 kg, WG03 > 5,000 kg).
2. In route determination (0VRF), records for deliveries can be differentiated by weight group under the same departure zone, shipping condition, transportation group, and destination zone.
3. During sales order entry, the route is determined without a weight group.
4. During outbound delivery creation, the system adds up the gross weight of the delivery items, finds the matching weight group, and can determine a different route for that weight.

---

Delivery Split Criteria: Architecture and Inviolable Boundaries

A Delivery Split occurs when line items from a single sales order (or multiple consolidated orders) cannot be combined into a single outbound delivery document, forcing the creation of multiple distinct deliveries.

An outbound delivery document (LIKP) represents a single operational shipment leaving one dispatch location for one consignee along one transport route at one time. Any divergence in header-level parameters forces an automatic technical split.

                                  Sales Order 1000450
 ┌────────────────────────────────────────┬────────────────────────────────────────┐
 │ Item 10: 100 Units Hardware            │ Item 20: 50 Units Liquid Coolant       │ Item 30: 20 Units Spare Parts          │
 │ Delivering Plant: 1000                 │ Delivering Plant: 1000                 │ Delivering Plant: 2000                 │
 │ Loading Group: 0001 (Forklift)         │ Loading Group: 0003 (Pumping)          │ Loading Group: 0001 (Forklift)         │
 │ Determined Ship Point: 1000 (Dock A)   │ Determined Ship Point: 1003 (Dock C)   │ Determined Ship Point: 2000 (Plant B)  │
 │ Route: R-US-01                         │ Route: R-US-COLD                       │ Route: R-US-02                         │
 └───────────────────┬────────────────────┴───────────────────┬────────────────────┴───────────────────┬────────────────────┘
                     │                                        │                                        │
                     ▼                                        ▼                                        ▼
             Delivery 80000101                        Delivery 80000102                        Delivery 80000103
             Ship Point: 1000                         Ship Point: 1003                         Ship Point: 2000
             Route: R-US-01                           Route: R-US-COLD                         Route: R-US-02

The Mandatory Technical Split Criteria

1. Shipping Point (LIKP-VSTEL): The ultimate architectural split boundary. Because the delivery header holds only one shipping point, items requiring different shipping points can never share a delivery.
2. Ship-to Party (LIKP-KUNNR): Goods traveling to different physical receiving locations require separate transport documentation, bills of lading, and delivery notes.
3. Route (LIKP-ROUTE): Transit time, freight carrier booking, and shipment legs are managed at the delivery header. Different routes dictate separate deliveries.
4. Planned Goods Issue Date / Delivery Date (LIKP-WADAT / LIKP-LFDAT): Items scheduled for dispatch on different calendar dates cannot be staged and issued together.
5. Incoterms (LIKP-INCO1, LIKP-INCO2): Different delivery terms (e.g., FOB Dallas vs. DDP Chicago) normally lead to separate deliveries; according to the official course, Incoterms can be selected or deselected as a split criterion in copying control.

Secondary / Configurable Split Criteria

Some split rules are configurable rather than fixed:

• Combining orders: Items from different sales orders can only share a delivery if order combination is allowed. The Order combination indicator is proposed from the customer master and can be set or removed in the order header and items.
• Copying control: A data transfer routine for the delivery header (field ZUKRL) can turn fields that normally do not split into split criteria, for example the order number or even the item number. Incoterms can be selected or deselected as a split criterion in copying control.
• Warehouse number: A delivery split by warehouse number can be activated in Customizing.

SAP Notes 355404, 399912, and 546668 describe how to analyze why a split occurred.

---

Practical Delivery Split Scenario Analysis

Consider an enterprise order placed by customer CUST-900 containing four distinct line items:

• Item 10: 100 ea Material A | Plant 1000 | Loading Group 0001 | Ship-to CUST-900 | Delivery Date 2026-11-01
  • Derived: Shipping Point 1000, Route R-01.
• Item 20: 50 ea Material B | Plant 1000 | Loading Group 0001 | Ship-to CUST-900 | Delivery Date 2026-11-01
  • Derived: Shipping Point 1000, Route R-01.
• Item 30: 200 ea Material C | Plant 1000 | Loading Group 0002 (Crane) | Ship-to CUST-900 | Delivery Date 2026-11-01
  • Derived: Shipping Point 1002 (Crane Ramp), Route R-01.
• Item 40: 75 ea Material A | Plant 1000 | Loading Group 0001 | Ship-to CUST-900 | Delivery Date 2026-11-15
  • Derived: Shipping Point 1000, Route R-01.

Execution Outcome during Collective Delivery Creation (VL10A):

• Delivery 1 (Items 10 & 20): Combined successfully! Both items share Shipping Point 1000, Ship-to CUST-900, Route R-01, and Goods Issue Date 2026-11-01.
• Delivery 2 (Item 30): Split! Although Plant, Ship-to, Route, and Date match Delivery 1, Item 30 requires Loading Group 0002, which determined Shipping Point 1002. Because LIKP-VSTEL cannot hold both 1000 and 1002, Item 30 splits into an independent delivery.
• Delivery 3 (Item 40): Split! Although Shipping Point 1000, Ship-to, and Route match Delivery 1, Item 40 has a delivery date of 2026-11-15 (two weeks later). Dispatch scheduling enforces an independent delivery.