1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments

Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments

While Sales Organizations, Distribution Channels, and Divisions establish the commercial architecture of an enterprise, physical fulfillment requires seamless integration with internal sales departments and logistics execution facilities. In SAP S/4HANA Sales, internal units like Sales Offices and Sales Groups manage sales territory performance, while logistics units—specifically Delivering Plants, Storage Locations, and Shipping Points—govern where stock is sourced and how shipments depart.

---

Internal Sales Units: Sales Office and Sales Group

To manage commercial operations across diverse territories, companies structure their sales representatives into internal departmental units. In SAP, these units are optional from a technical document perspective, but standard practice in corporate implementations.

The Sales Office

A Sales Office represents a physical branch office, regional sales division, or geographic territory (e.g., "Mid-Atlantic Sales Office", "Northern California Branch").

• Assignment: A Sales Office is assigned to one or more Sales Areas in customizing (SPRO $\rightarrow$ Enterprise Structure $\rightarrow$ Assignment $\rightarrow$ Sales and Distribution $\rightarrow$ Assign sales office to sales area).
• Document Role: When an order is created, the Sales Office is captured in the sales order header (VBAK-VKBUR). It can be defaulted from the customer master record (BP role FLCU01 Sales Area data) or entered manually.
• Reporting Utility: Acts as the primary organizational dimension for regional revenue tracking, sales quota management, and territory profitability analysis.

The Sales Group

A Sales Group represents an operational team, group of sales representatives, or departmental squad within a Sales Office (e.g., "Key Accounts Team", "Commercial Fleet Reps").

• Assignment: A Sales Group is assigned directly to a Sales Office (SPRO $\rightarrow$ Enterprise Structure $\rightarrow$ Assignment $\rightarrow$ Sales and Distribution $\rightarrow$ Assign sales group to sales office).
• Personnel Integration: The individual sales representative appears in sales documents as a partner (the sales employee partner function, German key VE), which refers to a personnel number. The sales group itself is only an organizational grouping maintained in customizing.
• Document Role: Stored in the sales order header (VBAK-VKGRP), driving commission calculations and sales team performance reporting.

Sales Area 1000 / 10 / 01
    └── Sales Office 110 (Northeast Branch)
            ├── Sales Group 11A (Major Accounts)
            └── Sales Group 11B (Mid-Market Team)

---

Logistics Execution Units: Delivering Plant and Storage Location

Sales orders do not hold physical inventory; physical stock resides in logistical facilities defined in Materials Management (MM) and Logistics Execution (LE).

Delivering Plant Architecture

A Plant is an operational facility where goods are manufactured, stored, or distributed. In SAP enterprise architecture:

• Every plant is defined centrally and assigned to exactly one Company Code (OX18).
• To utilize a plant for sales fulfillment, it must be assigned to an SD commercial channel via:
  SPRO $\rightarrow$ Enterprise Structure $\rightarrow$ Assignment $\rightarrow$ Sales and Distribution $\rightarrow$ Assign sales organization - distribution channel - plant.

Delivering Plant Determination Priority in Sales Orders

When a sales order line item is created, the system determines the Delivering Plant using a strict three-tier priority hierarchy:

1. Customer-Material Information Record (CMIR): If a specific delivering plant is defined for the customer and material combination (transaction VD51 / VD52), this plant takes absolute precedence.
2. Ship-to Party Master Record: If no CMIR entry exists, the system checks the Delivering Plant field (KNVV-VWERK) in the Sales Area data of the Ship-to Party customer master.
3. Material Master Record: If neither the CMIR nor the Ship-to Party specifies a plant, the system reads the Delivering Plant field (MVKE-DWERK) maintained on the Sales: Sales Org. 1 view of the material master.

Delivering Plant Search Sequence:
1. CMIR (Customer-Material Info Record)  ──[Found?]──> Use Plant
                     │ No
                     ▼
2. Ship-to Party Master (Shipping Tab)  ──[Found?]──> Use Plant
                     │ No
                     ▼
3. Material Master (Sales: Sales Org 1) ──[Found?]──> Use Plant

Storage Location Architecture

A Storage Location is an organizational subdivision of a plant where inventory is physically held (e.g., Raw Materials 0001, Finished Goods 0002, Quarantine 0003).

• Storage locations are defined under a specific plant.
• In standard sales orders, the storage location is often left blank and determined automatically upon outbound delivery creation using Picking Location Determination (rules based on Shipping Point + Delivering Plant + Storage Condition from the material master, or SAP Extended Warehouse Management integration).

---

The Shipping Point: The Logistics Anchor for Deliveries

The Shipping Point is the highest organizational unit in shipping and outbound delivery logistics. It represents the physical loading bay, crane terminal, rail depot, or parcel staging dock from which shipments are picked, packed, and dispatched.

The Inviolable Delivery Split Rule

In SAP S/4HANA, the shipping point governs the delivery header (LIKP-VSTEL):

• Every Outbound Delivery document can have exactly ONE Shipping Point.
• If a sales order contains multiple line items that resolve to different shipping points, the system forces an automatic delivery split.
• Line items requiring different shipping points can never be combined into the same outbound delivery document.

Multi-Plant Cardinality

• A single Shipping Point can serve multiple Plants (e.g., a shared bulk loading gantry servicing two adjacent plants).
• A single Plant can be assigned multiple Shipping Points (e.g., Plant 1010 has Bay 101A for standard pallet trucks, Dock 101B for heavy cranes, and Ramp 101C for hazardous chemicals).

---

Automatic Shipping Point Determination (Transaction OVL2)

During sales order entry, the system evaluates the line item material and customer parameters to automatically determine the proposed shipping point. This is executed using the classic three-key determination rule:

$$\text{Shipping Point} = \text{Shipping Condition} + \text{Loading Group} + \text{Delivering Plant}$$

The Three Determining Factors

1. Shipping Condition (2 characters): Reflects customer delivery requirements or transaction urgency (e.g., 01 Standard, 02 Customer Pickup, 10 Express Overnight).
   • Default Source: Sourced from the Sold-to Party customer master record (Shipping tab of Sales Area data).
   • Customizing Override: Can be overridden directly by the Sales Document Type header (transaction VOV8), such as defaulting Express 10 for Rush Orders (SO) regardless of customer master defaults.
2. Loading Group (4 characters): Reflects the mechanical equipment or handling gear needed to load the product (e.g., 0001 Forklift, 0002 Overhead Crane, 0003 Manual/Liquid Pump).
   • Source: Sourced from the Material Master record on the Sales: General/Plant view (MARC-LADGR).
3. Delivering Plant (4 characters): Determined from the sales order item via the CMIR $\rightarrow$ Ship-to $\rightarrow$ Material master priority sequence.

Customizing Mechanics in Transaction OVL2

In transaction OVL2, entries are configured combining the three inputs:

• Proposed (Default) Shipping Point: The primary shipping point inserted automatically into the sales order item.
• Manual / Alternative Shipping Points: Up to several permitted alternative shipping points that a user or logistics planner can manually select if the default dock is congested or closed.

---

Worked Determination Example: Dual-Item Order Split

Consider an industrial manufacturer fulfilling an order for Customer 400500 (Sold-to Party with Shipping Condition 01 Standard):

• Item 10: 5 Industrial Compressors (Material COMP-500).
  • Loading Group: CRAN (Heavy Crane required).
  • Delivering Plant: 1010 (Main Plant).
  • System lookup in OVL2 for [01 + CRAN + 1010] $\rightarrow$ Proposed Shipping Point: 101C.
• Item 20: 50 Pallet Boxes of Replacement Valves (Material VALV-100).
  • Loading Group: FORK (Forklift required).
  • Delivering Plant: 1010 (Main Plant).
  • System lookup in OVL2 for [01 + FORK + 1010] $\rightarrow$ Proposed Shipping Point: 101F.

Execution Outcome at Outbound Delivery

Both items successfully confirm stock from Plant 1010. However, when the shipping specialist runs collective delivery creation (VL10A / VL01N):

• Item 10 requires Shipping Point 101C.
• Item 20 requires Shipping Point 101F.
• Because a delivery document can contain only one shipping point in its header, the system creates two separate outbound deliveries:
  • Delivery 80000301 for Item 10 (dispatched from 101C).
  • Delivery 80000302 for Item 20 (dispatched from 101F).