Study guide

7.5 Picking and Goods Issue with Embedded 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.5 Picking and Goods Issue with Embedded EWM

Key Takeaways Explain This Topic AI

If the picking storage location of a delivery item is assigned to a warehouse number, picking must be performed in the warehouse management system (EWM).

The LE outbound delivery type LF is mapped to the EWM document type OUTB (outbound delivery order), and item categories are mapped as well.

Warehouse tasks control the physical movement; they find quants using the storage type search sequence and the stock removal rule (for example FIFO), and warehouse orders group warehouse tasks for execution.

Goods issue can be triggered manually from the outbound delivery order or automatically when goods reach the staging area or the truck leaves; it creates an EWM outbound delivery that reports back to the LE delivery.

A goods issue on an LE outbound delivery must cover the full quantity; for a partial goods issue, the EWM outbound delivery triggers a split of the LE delivery.

Last updated: October 2026

Picking and Goods Issue with Embedded EWM

In a warehouse managed with SAP Extended Warehouse Management, the sales order and the outbound delivery are still created in SAP S/4HANA Sales, but picking, packing, staging, and goods issue happen in EWM. The S46100 unit Integrating Delivery Processing with Embedded EWM shows how the two sides connect. Understanding the hand-over matters because an outbound delivery that does not move forward is often waiting for an EWM step.

  • From the Sales Document to EWM
  • Determining the Warehouse Number

When the outbound delivery is created, the picking storage location is determined (section 7.4). If the combination of plant and storage location is assigned to a warehouse number , picking must be performed with SAP WM or SAP EWM. In the course system, plant 1010 works with two EWM-managed storage locations: 101D ( EWM Received on Dock ) and 101S ( EWM Available for Sale ); stock becomes available for sale only after putaway into the final storage type.

Document Mapping

For goods issue in an EWM-managed warehouse, the documents depend on the business process. For a sales order, there is a Logistics Execution (LE) outbound delivery and corresponding documents in EWM. In EWM Customizing ( SCM Extended Warehouse Management → Extended Warehouse Management → Interfaces → ERP Integration → Delivery Processing → Map Document Types from ERP System to EWM ), the LE delivery type LF is linked to the EWM document type OUTB , the outbound delivery order ; item categories are mapped as well. For supplying manufacturing, LE outbound deliveries can be used, or a production material request can be created directly in EWM to reduce the number of documents.

Picking Output for an External Subsystem

If picking is done in a subsystem, the picking request is sent with output type WSOR , an output at delivery header level. Sending it does not set the picking status to C . When the subsystem reports the picking results, the logical output type WHSCON sends the picked quantity to the delivery, which sets the picking status to C .

Warehouse Tasks and Warehouse Orders

The physical movement of materials is controlled with warehouse tasks . For picking, warehouse tasks try to find the most appropriate quants to satisfy the outbound delivery order. A quant is created when material is put into an empty bin and deleted when the quantity is removed. To find the right stock, the system considers:

The storage type search sequence : the storage types in which the system looks for bins with the material, checked one after the other. For picking, the sequence can contain a storage type group to consider quants from several storage types at the same time.

The stock removal rule (picking strategy): assigned to a storage type or determined together with the search sequence. Examples are FIFO (first in, first out: the oldest quant in the defined storage type sequence) and stringent FIFO , which uses a storage type group to find the oldest quant across storage types.

Warehouse tasks are grouped into warehouse orders , the work packages that warehouse workers execute and confirm, typically with mobile devices.

The Warehouse Management Monitor

The EWM Warehouse Management Monitor informs warehouse managers about the current situation and the demands on resources so they can act. Its features:

Alert monitoring highlights actual and potential problems and offers exception handling.

With the right authorization, you can execute functions directly : create or confirm warehouse tasks and warehouse orders, change or block bins, and trigger wave processing.

It is highly customizable: hide nodes, create variant nodes based on standard nodes with specific selections or layouts, or build your own monitor in Customizing.

Objects are shown in an ALV list view with sorting, filtering, and printing, and you can switch to a more detailed form view .

Posting the Goods Issue

When the materials are picked and ready, the goods issue is posted. It can be triggered:

Manually from the outbound delivery order, or

Automatically , when the materials reach the staging area or when the truck leaves the warehouse.

For the goods issue, EWM creates another document, the EWM outbound delivery . It sends the goods issue information back to the LE outbound delivery , from which the inventory management document and the financial documents are created.

Why the Additional Document?

The course explains the reason. A goods issue against an LE outbound delivery must be posted for the full quantity of the delivery; a partial goods issue is not possible . Partial goods issue can nevertheless be necessary: there may be less stock physically in the warehouse than the system shows, or not enough transport capacity. In such cases, the LE outbound delivery must be split , and the split is triggered through the EWM outbound delivery.

End-to-End Flow

  • Step System Document
  • 1. Create sales order SAP S/4HANA Sales Sales order
  • 2. Create outbound delivery Logistics Execution LE outbound delivery ( LF ) with picking storage location 101S
  • 3. Distribute to EWM EWM Outbound delivery order ( OUTB )
  • 4. Create warehouse tasks for picking EWM Warehouse tasks grouped in a warehouse order
  • 5. Confirm the warehouse order EWM Picked quantity reported to the delivery
  • 6. Post goods issue EWM → LE EWM outbound delivery; material and accounting documents in SAP S/4HANA
  • 7. Bill SAP S/4HANA Sales Invoice with reference to the LE delivery

The course exercise follows exactly this sequence: create a sales order and an outbound delivery, create a warehouse task and confirm the warehouse order, then post the goods issue.

Worked Example: Short Stock at Picking

A delivery for 100 pieces is distributed to EWM. The warehouse task finds only 80 pieces in the bins (the system showed 100), because 20 pieces were damaged and not yet posted.

The picker confirms 80 pieces in the warehouse order and reports the difference.

Because the LE delivery cannot receive a partial goods issue, the EWM outbound delivery is created for the 80 pieces and triggers a split of the LE delivery: one part with 80 pieces, one part with 20 pieces.

Goods issue is posted for the 80-piece part, which is then billed. The 20-piece part stays open for later processing, and the stock difference is cleared in EWM.

Tip

If a delivery in an EWM warehouse has picking status C but no goods issue, check whether goods issue is triggered automatically (staging area, truck departure) or must be posted manually from the outbound delivery order.