Study guide
7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM
SAP S/4HANA Sales C_TS462
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure
1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration
2 Chapter 2: The Order-to-Cash Process and Sales Master Data
2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling
3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements
3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries
4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs
4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders
5 Chapter 5: Pricing and the Condition Technique
5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
6 Chapter 6: Availability Check (ATP) and Delivery Scheduling
6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements
7 Chapter 7: Delivery Processing and Embedded EWM
7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries
8 Chapter 8: Billing and Integration with Financial Accounting
8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options
9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output
9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables
10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core
10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels
11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition
11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM
Key Takeaways Explain This Topic AI
A goods receipt or goods issue posting always relates to a delivery, and warehouse activities such as creating and confirming a warehouse order are completed before inventory changes.
Delivery documents are used for sales orders and also for stock transport orders, subcontracting, vendor returns, inbound deliveries for purchase orders, and deliveries from projects.
Each outbound delivery is managed by exactly one shipping point; a shipping point can serve several plants that are close together, and a plant can have several shipping points.
Loading points structure a shipping point; they are assigned manually in the delivery header, and each loading point belongs to only one shipping point.
In EWM, the warehouse number is divided into storage types, storage sections, and storage bins; activity areas group bins for picking, putaway, or physical inventory, and a quant is the stock of a product in a bin.
Last updated: October 2026
Delivery Documents and Organizational Units for Delivery Processing, Including EWM
Shipping starts where sales ends: once a sales order item is confirmed and due, a delivery document takes over. The S46100 course Configuring Delivery Processing in SAP S/4HANA Sales is one of the largest in the learning journey (718 minutes), and it begins with two foundations covered here: what a delivery document does, and which organizational units shipping and warehouse management use.
Deliveries in Logistics Execution
Logistics Execution covers both directions of goods movement: goods receipt and goods issue . The official course makes two points that shape everything in this chapter:
SAP Extended Warehouse Management (EWM) is also available inside SAP S/4HANA as embedded EWM . Legacy Warehouse Management (WM) remains available, but future development takes place only in EWM, which will replace legacy WM entirely. A lean version of legacy WM continues as Stock Room Management .
When you work with deliveries, warehouse activities such as creating and confirming a warehouse order are completed before the stock level changes in inventory management. A goods receipt or goods issue posting always relates to a delivery . The warehouse order is the document used to execute all material movements in the warehouse.
More Than Sales Orders
Delivery documents model many processes through different delivery types. Besides the outbound delivery for a sales order, the course names:
Replenishment deliveries for stock transport orders : the ordering plant creates a purchase order on the supplying plant, and the supplying plant creates a delivery with reference to it as the basis for picking, output, and goods issue.
Deliveries for subcontract orders .
Vendor returns .
Inbound deliveries for purchase orders : one inbound delivery can cover a complete purchase order, partial quantities, or several purchase orders, and serves as the basis for packing, putaway, the warehouse order, and the goods receipt posting.
Deliveries from projects .
What Shipping Processing Includes
The course lists the activities of shipping:
- Monitoring the deadlines of reference documents due for shipping
- Creating and processing outbound deliveries
- Monitoring the capacity situation in the warehouse
- Supporting picking
- Packing
- Printing and distributing shipping documents
- Processing the goods issue
- Controlling through overviews of deliveries in progress, open activities, and bottlenecks
The delivery document is the basis for all of them, and its status values show how far each step has progressed. After goods issue, the delivery is added to the billing due list.
Structure of a Delivery Document
A delivery consists of a header and items . The header contains data for the whole document, so the ship-to party , the shipping point , and the route are clearly displayed in the header of every outbound delivery. The items contain the materials to be delivered. The overview screen shows selected header and item data grouped on tabs by activity. Detail screens at header level group information into tabs for processing, picking, loading, shipment, foreign trade/customs, texts, partners, output, package monitoring, and conditions , and item details offer similar tabs.
Delivery versus Shipment or Freight Order
A delivery describes what leaves one shipping point for one ship-to party . Transportation is planned in a separate document: a shipment in classic Logistics Execution transportation, or a freight order in SAP S/4HANA Transportation Management. One shipment or freight order can group several deliveries that travel together on one truck, so delivery processing (picking, packing, goods issue) and transportation planning (carrier, stages, freight costs) remain separate.
Organizational Units for Inventory Management
You model the inventory structure of a corporate group with clients, company codes, plants, and storage locations . A client represents the corporate group and a company code an independent accounting unit. The plant plays the central role: it is a physical location where inventory is stored, such as a manufacturing site or distribution center, and production, procurement, maintenance, and materials planning are managed at plant level. Each plant has one or many storage locations , which differentiate the stocks of a material within the plant; stock is managed at storage location level. A plant can be assigned to only one company code , so stocks and stock values are managed independently per company.
- Organizational Units for Shipping and Goods Receipt
- Shipping Point
A shipping point is an independent organizational unit at a fixed location that processes and monitors outbound deliveries and goods issues. The official rules:
Each outbound delivery is managed by a single shipping point. The responsible shipping point is determined in the sales order at item level (section 7.2).
A shipping point can process the deliveries of several plants , but this is only useful if the plants are located close to each other.
Several shipping points can be assigned to one plant , for example for different loading equipment, processing times, or modes of transport.
The allowed combinations of shipping points and plants are defined in Customizing.
A shipping point can also be set as a goods receiving point , so it can manage inbound deliveries too.
Loading Point
A loading point structures a shipping point, for example into individual loading ramps. Loading points are defined in Customizing for Logistics Execution and are assigned manually in the delivery header ; they can be printed in the delivery output. Any number of loading points can belong to a shipping point, but each loading point belongs to only one shipping point .
Organizational Units in SAP EWM
When a warehouse is managed with EWM, a more detailed structure describes the building:
Unit Description
Warehouse number The whole warehouse complex, with attributes such as weight, volume, and time units and the determination procedures for palletization data and packaging specifications. SAP recommends one warehouse number for each group of storage areas or buildings in the same geographical area, and separate warehouse numbers for complexes in different cities. To identify the owner of the stock, the warehouse number is assigned to a supply chain unit (SCU) .
Storage type A physical or logical subdivision of the warehouse, characterized by warehouse technology, the nature of the products, space required, and organizational function. It has a four-character key and a storage type role that defines its use.
Storage section A subdivision of a storage type that groups bins with similar attributes (heavy parts, bulky parts, hazardous materials, fast-moving or slow-moving items), used during putaway.
Storage bin The smallest addressable unit of space in the warehouse: the exact location where a product is stored.
Activity area A logical grouping of bins, independent of storage type, per activity: picking, putaway, or physical inventory . Activity areas define bin sorting when warehouse orders are created, and one bin can belong to several activity areas.
Quant The record of the stock of a product in a storage bin.
The link between inventory management and EWM is made by assigning combinations of plant and storage location to a warehouse number . When the picking storage location of a delivery item belongs to a warehouse number, picking must be done in the warehouse management system (section 7.5).
Worked Example: Designing the Structure
A company has plant 1010 (production) and plant 1020 (distribution center) on the same site, with one warehouse building.
One shipping point serves both plants because they are close together; a second shipping point in plant 1010 handles crane loading for heavy machines, because it needs different loading equipment and times.
The first shipping point has three loading points for three ramps, assigned in the delivery header by the shipping clerk.
Plant 1020, storage location 101S, is assigned to EWM warehouse number 1710. The warehouse is divided into a high-rack storage type, a fixed-bin picking storage type, and a goods receipt area; activity areas sort the picking bins along the picker's route.
A sales order item from plant 1020 is delivered from the shared shipping point. Because its picking storage location belongs to warehouse number 1710, EWM creates the warehouse tasks for picking.
Tip
Remember the cardinalities: one delivery has one shipping point; one shipping point can serve several nearby plants; one plant can have several shipping points; one loading point belongs to one shipping point.