PUBLIC

Overview of Functional and Technical Differences

between Extended Warehouse Management in
SAP S/4HANA OP 1909 FPS1 and SAP EWM 9.5

Version: 1.8

Date: April 2020

DISCLAIMER: This presentation outlines our general product direction and should not be relied
upon in making a purchase decision. This presentation is not subject to your license agreement or
any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in
this presentation or to develop or release any functionality mentioned in this presentation. This
presentation and SAP’s strategy and possible future developments are subject to change and may
be changed by SAP at any time for any reason without notice. This document is provided without a
warranty of any kind, either express or implied, including, but not limited to, the implied warranties of
merchantability, fitness for a particular purpose, or noninfringement. SAP assumes no responsibility
for errors or omissions in this document, except if such damages were caused by SAP intentionally
or grossly negligent.

SAFE HARBOR STATEMENT

This document is intended to outline future product direction, and is not a commitment by SAP to
deliver any given code or functionality. Any statements contained in this document that are not
historical facts are forward-looking statements. SAP undertakes no obligation to publicly update or
revise any forward-looking statements. All forward-looking statements are subject to various risks
and uncertainties that could cause actual results to differ materially from expectations. The timing or
release of any product described in this document remains at the sole discretion of SAP. This
document is for informational purposes and may not be incorporated into a contract. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be
relied upon in making purchasing decisions.

2
INTRODUCTION OBJECTIVE OF THIS DOCUMENT

The following document contains functional and technical differences between the different EWM
deployment options. The information is based on the release of SAP S/4HANA 1909 FPS1 in February 2020
and the latest EWM business suite release SAP EWM 9.5.

The intention of the overview is to provide customers, partners, and consultants a guidance to select
the right deployment option for the customer projects. In addition SAP recommends to check the SAP
Note 1606493 „SAP EWM Deployment Options Best Practices“. In general SAP recommends starting new
projects only on the SAP S/4HANA stack as this is the future platform for Extended Warehouse Management
and is planned to receive innovations with future releases.

The table below contains only entries with known differences. Features which are identical between the
deployment options are not listed.

The overview does not include differences between EWM and LE-WM. The overview does not include a
delta comparison between different SAP S/4HANA releases or between different business suite releases. In
general, new functions developed with SAP S/4HANA 1909 and above are not supported by the business
suite release (e.g., SAP EWM 9.5).

3
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA

Installation and Deployment

EWM Installation EWM is part of the EWM is part of the Installation of SAP
SAP S/4HANA SAP S/4HANA EWM 9.5. See
installation installation installation note and
master guide on
http://help.sap.com/ewm
Integrate with ERP Supported Not applicable Supported
applications in the same (SAP EWM as Add-On
system instance and client to SAP ERP)

Integrate with Transportation Supported Supported with Supported

Management in the same S/4HANA 1809 FPS2
system instance and client See SAP Note
2812981
Connect the EWM client to Not applicable Supported for Supported
multiple SAP ERP or SAP harmonized materials
S/4HANA systems with ERP (and non-harmonized
system role customer/vendor) with
1909 FPS11

Planned for non-

harmonized materials
with a future release
(beyond 2020)
Connect to an SAP ERP or Not applicable Supported with Supported
an SAP S/4HANA as ERP SAP ERP 6.0 EhP 3 or
higher
SAP S/4HANA 1610 or
higher as ERP
IDOC based integration Not supported Not supported Supported
(transactional data) with SAP
ERP lower than ERP 6.0

Connect to SAP S/4HANA Not applicable Currently not Supported,

Cloud Edition supported, planned see scope items2
with a future release

1
Pre-requisite for integrating with several ERPs with non-harmonized customer/vendor keys across the ERP
systems: The master data distribution has to use the Data Replication Framework (DRF) and replicate the
Business Partners (BP) of the ERP systems. This is only possible for ERP systems which fulfill the following
requirements:
1. Active CVI: Only with CVI the ERP systems have BPs assigned to the customer/vendor master
2. DRF based BP distribution is available only in EHP5 or higher
2
The supported functionality is described in the following scope items in SAP Best Practices Explorer for
SAP S/4HANA Cloud:
• SAP EWM Integration – Batch Management (2VN)
• SAP EWM Integration – Customer Returns (2VO)
• SAP EWM Integration – Delivery-Based Production Integration (2VM)
• SAP EWM Integration – Inbound Processing from Supplier (2VJ)
• SAP EWM Integration – Outbound Processing for Customer (2VK)
• SAP EWM Integration – Stock Transport Orders (2VL)
• SAP EWM Integration – Warehouse Stock Handling (2YL)

4
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA
Integration with Retail ERP: Not applicable Supported with SAP Supported
Replicate ERP Retail Article Note 2839077
Master to Product Master in
decentral EWM (Retail not
active in EWM)
Implementation / Basic Settings
Basic Settings Guide or Basic Settings Guide Integration Guide Integration Guide
ERP-EWM Integration Guide available. available. available.
See SAP Note See SAP Note See SAP Note
2782080 2782080 2782080

EWM Implementation Tools Implementation tools Implementation tools All implementation

(for setting up the system
connection with ERP and for
creating a basic warehouse
or the preconfigured
warehouse W001)
Preconfigured Warehouse
(W001)
for system connection for system connection tools are available
and for creating a and for creating a
warehouse with basic warehouse with basic
settings are available settings are available
Not applicable – Best Currently not Supported
Practice content is supported, planned
provided instead with a future release

Best Practice Content Supported Currently not RDS (best practice)

Migration Tools
(from LE-WM to EWM) /
Migration Guide
supported, planned content available with
with a future release. SAP EWM 9.3. and
Customizing from can be referred to by
client 000 is used SAP EWM 9.5 for
instead. manual configuration
only
Migration tools to Migration tools to Migration tools to
upload EWM upload EWM upload EWM
warehouse structures, warehouse structures, warehouse structures,
configuration and configuration and configuration and
stock from CSV file stock from CSV file stock from CSV file.

See migration guide

Migration Tools
(from SAP EWM to EWM in
S/4HANA)
on
http://help.sap.com/ewm
Not supported S/4HANA Migration Not applicable
Cockpit supports direct
transfer for scenario
“SAP EWM to
Decentralized EWM”
Migration Objects:
• Storage Bin
• Storage Bin Sorting
• Warehouse Product
• Fixed Bin
Assignment
• Warehouse Stock

5
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA

Master Data
Usage of S/4HANA business
partner master data for
customers and vendors
(including carriers)
Usage of S/4HANA material
master
Maintenance of EWM
warehouse attributes in the
central Fiori app “Manage
Product Master Data”
Automatic creation of
warehouse product master
data when new products are
created
Usage of S/4HANA material
master for valuation data (for
value tolerance checks and
split valuation)
Supported; Supported; Usage of business
no replication needed replication to partner master data;
decentralized EWM via replication via CIF
standard interfaces
Supported; Supported; Usage of SCM master
no replication needed replication to data;
decentralized EWM via replication via CIF
standard interfaces
Supported Supported Not supported;
automatic creation of
warehouse product
master data during
CIF is possible
Not supported; Not supported; Supported
but: mass creation but: mass creation (during CIF replication)
possible in Warehouse possible in Warehouse
Monitor node Product Monitor node Product
Master Data à Master Data à
Warehouse Attributes Warehouse Attributes
Supported; Usage of SCM tables; Usage of SCM tables;
no replication needed replication via replication via
transaction transaction
/SCWM/VALUATION_SET /SCWM/VALUATION_SET

Usage of S/4HANA batch Supported; Supported; Usage of SCM master

master and batch no replication needed replication to data;
classification data (including decentralized EWM via replication via CIF
characteristics and classes) standard interfaces
Batch master maintenance in Supported Supported via creation Supported
EWM of new batches in
EWM inbound delivery
transactions/apps 3
Usage of S/4HANA project Supported Not supported; Not supported;
master data for project stock WBS elements are WBS elements are
replicated replicated
automatically to SCM automatically to SCM
tables. tables.
Usage of S/4HANA Supported Usage of SCM tables; Usage of SCM tables;
accounting objects for replication via replication via
outbound processing to transaction transaction
internal customers like cost /SCWM/ACC_IMP_ERP /SCWM/ACC_IMP_ERP
centers
Usage of PS&S master data Supported; Supported; Usage of EH&S master
for dangerous goods and no replication needed replication to data;
hazardous substances and decentralized EWM via replication via
phrases standard interfaces standard interfaces

3
The creation of local batches by using the batch master transaction/Apps is not supported as the batches
are not replicated to the connected ERP system. If you create the batch in EWM inbound delivery
transaction/Apps, the batches will be replicated back to the connected ERP system.

6
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA
Tracking of changes via Supported Supported Not supported
change documents for:
• storage bin
• fixed bin assignments
• quality inspection rules
• (EWM) control cycles
Customizing
Direct access to S/4HANA Supported Supported; Not supported;
customizing for: replication via usage of SCM
• Catch-weight tolerance standard customizing customizing tables
group synchronization
• CW profile for CW
quantities
• Delivery priority
• Handling indicator
• Handling unit type
• Incoterms
• Packing group
• Quality inspection group
• Serial number profile
• Shipping conditions
• Transportation group
• Warehouse product
group
• Warehouse storage
condition
Customizing for ERP version n.a. Supported Supported
control

Transparency of storage Supported Supported Not supported

location assignment in EWM
stock type and availability
group
Customizing for batch n.a. Not supported; Supported
replication from EWM (table ERP update always
/SCWM/TBATCHUPD) asynchronous
(equivalent to value 3
in SAP EWM 9.5)
Inbound Processing
Direct access to purchasing Supported Not supported; Not supported;
documents or manufacturing EGR documents are EGR documents are
orders to create inbound used used
deliveries in EWM (without
expected goods receipt
documents)
Direct creation of warehouse Supported Supported; Supported;
request for inbound inbound delivery inbound delivery
deliveries w/o inbound notifications can be notifications can be
delivery notifications skipped (Customizing) skipped (Customizing)

7
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA
Re-use of LE-SHP inbound Supported Supported Supported with SAP
delivery number in EWM Note 2791111
warehouse request number

Enhancements to Fiori app Supported Supported Not supported

“Change Inbound Deliveries”

Fiori app “Process Supported Supported Not supported

Warehouse Tasks -
Putaway”

Setting to forbid putaway WT Supported Supported Not supported

before goods receipt

Delivery-related Supported Supported Not supported

authorizations based on
warehouse number

Storage Behavior: Supported Supported Not supported

‘Flexible Bin’

Outbound Processing
Direct creation of warehouse Supported Supported; Supported;
request for outbound outbound delivery outbound delivery
delivery orders w/o requests can be requests can be
outbound delivery requests skipped (Customizing) skipped (Customizing)
Enhancements to Fiori app Supported Supported Not supported
“Run Outbound Process –
Deliveries”

Fiori app “Run Outbound Supported Supported Not supported

Process– Transportation
Units”

Fiori app “Pack Outbound Supported Supported Not supported

Deliveries”

Fiori app “Process Supported Supported Not supported

Warehouse Tasks - Picking”

Re-use of LE-SHP outbound Supported Supported Supported with SAP

delivery number in EWM Note 2791111
warehouse request number

8
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA
Direct usage of SD route Supported Not supported4; Not supported;
master in EWM warehouse SCM route is used SCM route is used
requests (e.g. determination
of transit countries for
dangerous goods functions)
Transportation Management Not supported, not strategic; Supported
in EWM (also known as EWM but: transportation units are available;
Freight Order Management Use of SAP TM is recommended for
or FOM) comprehensive transportation functionality
EWM Routing Guide and all Not supported Supported Supported
the related EWM functions,
with below examples:
• Simulation tool on route
determination
• Transportation Cross
Docking
• Delivery scheduling
using EWM routing guide
• Automatic delivery splits
in case of different
routes
SAP AR Warehouse Picker Not supported; Not supported; Supported until
(supporting hands free Planned with a future Planned with a future 31.12.2019
picking processes by smart release with lower release with lower
glasses) priority priority
Delivery-related Supported Supported Not supported
authorizations based on
warehouse number

Quality Management
Quality Inspection Engine Not applicable Supported Supported
(QIE) for quality management (with restriction *1, *2,
processes with ERP QM *3, *4, *5)
integration, as well as
standalone quality inspection
processes without ERP QM
integration 5
*1 QIE Standalone Not applicable, feature Not supported, not Supported
Process: Preliminary itself is not supported, strategic
inbound delivery not strategic
inspections (IOT 1)

4
This restriction is only for the usage of master data of SD route because in SAP standard there is no
replication of SD route master available to the decentralized EWM on S/4HANA system. The SD route key is
available in the EWM warehouse request with the distribution of the LE-SHP delivery.
5
In embedded EWM in S/4HANA, only QM inspection lots are used the run the quality management
processes. Inspection rules are used for triggering quality inspection and detailed planning. They contain
both the inspection setup and the inspection relevance checks.
For more information about QIE and the supported quality management processes, please access the SAP
EWM Help Portal for EWM 9.5 or S/4HANA: http://help.sap.com/S4HANA: select in section Product
Assistance English. Navigate to Enterprise Business Applications à Supply Chain à Extended Warehouse
Management (EWM)à Quality Management

9
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA
*2 With ERP QM Not applicable, feature Currently not Not supported.
Integration: Automatic itself is currently not supported, planned Warehouse tasks for
creation of separate supported, planned with a future release. sample quantities can
warehouse tasks to with a future release. For now, warehouse be created manually
move sample quantity tasks for sample with support of BAdI
to an inspection area quantities can be /SCWM/EX_WRKC_P
created manually ACK_QTY_PROPOSE
*3 With ERP QM Not applicable Not supported, not Supported
Integration: QIE strategic; documents
Document are expected to be
Attachments (e.g. attached to the QM
inspection rule, objects e.g. inspection
inspection document) lot
*4 With ERP QM Not applicable Not supported, not Supported
Integration: Non-100 strategic, sample
% inspection calculation is expected
procedure to be done in QM
*5 With ERP QM Not applicable Not supported, not Supported
Integration: Dynamic strategic, dynamic
Modification in the QIE modification is
inspection rule expected to be set up
in QM
Counting inbound delivery Not supported Supported Supported
(inspection object type (IOT)
2)

Preliminary inspection Not supported Supported Supported

handling unit (inspection
object type (IOT) 6)

With ERP QM Integration: Not applicable6 Supported Not supported

Master Data Synchronization
to control QM Processes

QM Activation Without Using Supported Not supported Not supported

Inspection Rules

QM: Support Inspection Lot Supported Not supported Not supported

Types “01” and “04” with
Inspection Origin “17”

Recording an inspection Not supported Supported Supported

decision in RF

Recording and tracking Not supported Supported Supported

quality management
workload in labor
management

6
Master data synchronization not necessary as QM and EWM run in same system

10
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA
Integration of Quality Not applicable Supported with 1909 Not supported
Inspection Engine to Multiple FPS1
Enterprise Management
Systems

Returns Processing and Advanced Returns Management (ARM)

Customer returns processing Not supported, Supported Supported
without using ARM planned with a future
release
Quality Inspection with Not supported Not Supported Supported
Returns in the Distribution
Network
Fiori App E-Commerce Not supported, Supported Supported
Returns (planned and planned with a future
unplanned customer returns) release

ARM: processing of Not supported Supported Supported

replacement material from
supplier

Inspection lot in the material Not supported; Not supported; Not supported;
inspection in ARM integrated see SAP notes see SAP notes see SAP notes
with QM 2259775 and 2481845 2259775 and 2481845 2259775 and 2481845

Visibility of assigned serial Not supported Not supported Not supported

numbers on the ARM
material inspection

Internal Warehouse Processes

Fiori app “Count Physical Supported Supported Not supported
Inventory”

ABC classification based on Supported Supported Supported with SAP

confirmed warehouse tasks EWM 9.5 SP05 (see
SAP note 2809838)

Enhancements to Supported Supported Not supported

Warehouse Management
Monitor: Node “Inspection” Node “Inspection”
• Methods for monitor displays inspection displays inspection
nodes “Physical Stock” lots documents as in SAP
and “Posting Change EWM 9.5
Items”
• Node “Storage Bin
Sorting“
• Navigation to bin change
documents
• Node “Inspection“
Direct creation of warehouse Supported Supported; Supported;
request for posting change posting change posting change
w/o posting change requests requests can be requests can be
skipped (Customizing) skipped (Customizing)

11
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA
Enhancements to stock Supported Supported Not supported
consolidation

Enhancements to physical Supported Supported Not supported

inventory (queue, RF)

Production Integration
Harmonized production Supported Not supported Not supported
supply area (PSA) and due to system
control cycle maintenance boundaries

Kanban strategy Supported Not supported Not supported

“Replenishment with due to system
warehouse task” in EWM boundaries
warehouse
Kanban stock transfer via Supported Not supported Not supported
Kanban apps in EWM due to system
warehouse boundaries

Kanban status update from Supported Not supported Not supported

warehouse task processing due to system
boundaries

Visibility of Kanban ID in Supported Not supported Not supported

warehouse tasks processing due to system
and monitoring boundaries

Multi-step staging and Supported Supported Not supported

production supply using
distribution equipment

Synchronous goods Supported Not supported Not supported

movements from PP: due to system
• REM backflush (GI/GR) boundaries
• Transaction PPCGO
• Kanban Board: GR for
summarized JIT call
• Kanban Board: GR for
in-house REM
production
Restriction to VMS and JIT See SAP note See SAP note See SAP note
Processes 2825796 2825796 2668075

Cross Topics
Additional Warehouse Supported Supported Not supported
Management Monitor
methods for monitor nodes
“Warehouse Task”

12
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA
Synchronous goods Supported Not supported Not supported
movement postings from due to system due to system
EWM to MM-IM when no boundaries boundaries
delivery is involved
Fiori app “Pack Warehouse Supported Supported Not supported
Stock”

Labor Demand Planning Currently not supported, planned with a future Supported
release after conversion to Fiori App and (with HANA DB)
technical backend change

Transit Warehousing Supported Supported; Supported

see SAP note 2808265

UI5 App to support carrier Not supported7, Not supported6, Supported

access for maintaining dock planned to offer a planned to offer a
appointments DAS native Fiori app in a native Fiori app in a
future release future release
IUID (Item Unique Supported Supported Not supported
Identification) to handle
products that have serial
numbers and UII
S/4HANA Analytics / Supported Supported Not supported
operational monitoring based
on CDS views for:
• Outbound delivery
orders
• Warehouse orders and
warehouse tasks
Enterprise Search for EWM Supported Supported Not supported
objects:
• Warehouse products
• Storage bins

Usage of Additional SAP Products, Industry Solutions, and Integration with other Applications
SAP HANA Live for EWM
and
SAP Smart Business for
EWM
Integration with SAP ME for
goods receipt from
production, components
staging and consumption
Comparable functions provided with CDS views Supported
(see S/4HANA Analytics under Cross-Topics)
Supported. Automatic Supported. Automatic Supported
notification of staging notification of staging
confirmation from confirmation from
EWM to SAP ME for EWM to SAP ME for
single order staging single order staging
and confirmation and confirmation
based on Production based on Production
Material Request. Material Request.
Available with Available with

7
A Webdynpro application with the same functionality is available and can also be enabled for external
access outside of the firewall by special system setups to secure the access control

13
 EWM embedded in EWM decentral on
Feature SAP EWM 9.5
S/4HANA S/4HANA
S/4HANA OP 1909 S/4HANA OP 1909
FPS1 & SAP ME 15.4 FPS1 & SAP ME 15.4
SP00 SP00

Integration with SAP ERP Not applicable Supported; Supported

Discrete Industry Mill See SAP note
Product (DIMP) system with 2838158 which is
active long material number required in EWM
system
Integration with decentral Supported; Supported; Supported
GTS but: integration with but: integration with
embedded GTS in embedded GTS in
S/4HANA not S/4HANA not
supported supported
Integration with SAP CRM to Not applicable Not supported Supported
receive business partner
master data for customer
and vendor as used in the
Spare Parts Management
(SPM) solution landscape
Fashion Management Supported, with restrictions8 Supported
(Add-On to EWM for
Fashion industry to
integrate with a SAP
ERP-AFS system)

8
Restrictions related to order allocation run (ARun) and stock segmentation of EWM-managed stock:
• ARun: In case the complete stock is allocated to outbound deliveries, an EWM stock difference (e.g.
during physical inventory counting) creates a hanging queue as the stock is fully allocated. In this
case the customer is forced to de-allocate part of the stock from deliveries, reprocess the hanging
queue to post the stock difference and allocate the stock again
• ARun: In case the stock is allocated to outbound deliveries and the warehouse performs an “over-
pick” (picking more than requested) the update to the LE outbound delivery during goods issue fails
as only the original quantity is allocated by A-Run. In this case the customer is forced to de-allocate
part of the stock from other deliveries, reprocess the hanging queue to update the LE outbound
delivery and allocate the stock again
• Stock Segmentation: currently, EWM does not provide information related to the stock segment
attribute in the available EWM stock reports
• Stock Segmentation: There is currently no visibility of segmentation strategy to EWM warehouse
users during the warehouse task processing. Hence if a batch is changed or replaced by a
warehouse worker during warehouse task processing and this batch does not match the delivery
batch that was determined based on segmentation value in the mapping rule of the segmentation
strategy, the goods issue posting will fail, resulting in hanging queues. To avoid this, it is
recommended to select the “Ignore Segmentation rule“ in Customizing node in Delivery type for
Segmentation Rule to allow alternate batches selected by warehouse worker in EWM to be
accepted while goods issue posting

14
www.sap.com/contactsap

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/copyright for additional trademark information and notices.