PUBLIC

Overview of Functional and Technical Differences

between Extended Warehouse Management in
SAP S/4HANA OP 2021 FPS00 and SAP EWM 9.5

Version: 1.0

Date: October 2021

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 2021 FPS00 in October 2021
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 document is divided into five sections:
1. Differences of EWM in S/4HANA (decentral and embedded) compared to EWM 9.5: this section
lists the differences of EWM in S/4HANA compared to Business Suite EWM.
2. Deployment differences of embedded EWM in S/4HANA and decentral EWM on S/4HANA for
new features in 1909 (these new features are not supported by the business suite releases): this
section lists all new features of the S/4HANA 1909 release where there are differences in the
deployment options (embedded vs. decentral).
3. Deployment differences of embedded EWM in S/4HANA and decentral EWM on S/4HANA for
new features in 2020 (these new features are not supported by the business suite releases): this
section lists all new features of the S/4HANA 2020 release where there are differences in the
deployment options (embedded vs. decentral).
4. Deployment differences of embedded EWM in S/4HANA and decentral EWM on S/4HANA for
new features in 2020 FPS01 (these new features are not supported by the business suite release):
this section lists all new features of the S/4HANA 2020 FPS01 release where there are differences in
the deployment options (embedded vs. decentral).
5. Deployment differences of embedded EWM in S/4HANA and decentral EWM on S/4HANA for
new features in 2021 (these new features are not supported by the business suite release): this
section lists all new features of the S/4HANA 2021 release where there are differences in the
deployment options (embedded vs. decentral).

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 1809 and above are not supported by the business
suite release (e.g. SAP EWM 9.5).

3
1. Differences of EWM in S/4HANA (decentral and embedded) compared to EWM 9.5:

EWM embedded in EWM decentral on

Feature SAP EWM 9.5
S/4HANA S/4HANA

Installation and Deployment

EWM Installation
Integrate with ERP
applications in the same
system instance and client
EWM is part of the SAP EWM is part of the SAP Installation of SAP
S/4HANA installation S/4HANA installation EWM 9.5. See
installation note and
master guide on
http://help.sap.com/ew
m
Supported Not applicable Supported
(SAP EWM as Add-On
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
S/4HANA 1909 FPS11

Planned for non-

harmonized materials
with a future release
(beyond 2020)
Connect to an SAP ERP or an Not applicable Supported with Supported
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 Not supported. Supported.
Cloud, Essentials Edition Planned with a future See scope items2
(former MTE) 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)

4

Feature
Integration with Retail ERP:
Replicate ERP Retail Article
Master to Product Master in
decentral EWM (Retail not
active in EWM)
Implementation / Basic Settings
Basic Settings Guide or ERP-
EWM Integration Guide
EWM Implementation Tools
(for setting up the system
connection with ERP and for
creating a basic warehouse or
the preconfigured warehouse
W001)
Preconfigured Warehouse
(W001)
EWM embedded in EWM decentral on
SAP EWM 9.5
S/4HANA S/4HANA
Not applicable Supported. Supported
See SAP Note
2839077
Basic Settings Guide Integration Guide Integration Guide
available. available. available.
See SAP Note See SAP Note See SAP Note
2782080 2782080 2782080
Implementation tools Implementation tools All implementation
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 Not applicable – Best Supported
Practice content is Practice content is
provided instead provided instead

Best Practice Content Available. Available with RDS (best practice)

See SAP Best Practices S/4HANA 2020. content available with
Explorer. See SAP Best Practices SAP EWM 9.3. and can
Explorer. be referred to by SAP
EWM 9.5 for manual
configuration only
Migration Tools Migration tools to Migration tools to Migration tools to
(from LE-WM to EWM) / upload EWM upload EWM upload EWM
Migration Guide 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

on
http://help.sap.com/ew
m
Migration Tools Not supported S/4HANA Migration Not applicable
(from SAP EWM to EWM in Cockpit supports direct
S/4HANA) transfer for scenario
“SAP EWM to
Decentralized EWM”.

• 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)

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 product
master
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
Not supported via CIF Not supported via CIF Supported
replication but: mass replication but: mass (during CIF replication)
creation possible in creation possible in
Warehouse Monitor Warehouse Monitor
node Product Master node Product Master
Data → Warehouse Data → Warehouse
Attributes Attributes
Or Or
As described in note As described in note
#3081583 #3081583
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 classification No replication needed Replication to data.
data (including characteristics decentralized EWM via Replication via CIF
and classes) standard interfaces
Usage of S/4HANA project Supported Not supported. Not supported.
master data for project stock WBS elements are WBS elements are
replicated automatically replicated automatically
to SCM tables. to SCM tables.
Usage of S/4HANA accounting Supported Usage of SCM tables. Usage of SCM tables.
objects for outbound Replication via Replication via
processing to internal transaction transaction
customers like cost centers /SCWM/ACC_IMP_ERP /SCWM/ACC_IMP_ERP

Usage of PS&S master data for Supported. Supported. Usage of EH&S master
dangerous goods and No replication needed Replication to data.
hazardous substances and decentralized EWM via Replication via standard
phrases standard interfaces interfaces

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

Customizing
Direct access to S/4HANA Supported Supported. Not supported.
customizing for: Replication via standard Usage of SCM
• Catch-weight tolerance 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 Not applicable Supported Supported
control

Customizing for batch Not applicable Batch replication Supported

replication from EWM (table supported by default, no
/SCWM/TBATCHUPD) additional customizing
foreseen.
ERP update always
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 deliveries Inbound delivery Inbound delivery
w/o inbound delivery notifications can be notifications can be
notifications skipped (Customizing) skipped (Customizing)
Re-use of LE-SHP inbound Supported Supported Supported.
delivery number in EWM See SAP Note 2791111
warehouse request number

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

Outbound Processing
Direct creation of warehouse Supported Supported. Supported.
request for outbound delivery Outbound delivery Outbound delivery
orders w/o outbound delivery requests can be skipped requests can be skipped
requests (Customizing) (Customizing)
Re-use of LE-SHP outbound Supported Supported Supported.
delivery number in EWM See SAP Note 2791111
warehouse request number

Direct usage of SD route Supported Not supported.3 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 in Not supported, not strategic; Supported
EWM (also known as EWM but: transportation units are available;
Freight Order Management or Use of SAP TM is recommended for comprehensive
FOM) 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 picking Planned with a future Planned with a future 31.12.2019
processes by smart glasses) release release

3 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.

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

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 4
*1 QIE Standalone Process: Not applicable, feature Not supported, not Supported
Preliminary inbound itself is not supported, strategic
delivery inspections not strategic
(IOT 1)
*2 With ERP QM Not applicable, feature Currently not Not supported.
Integration: Automatic itself is currently not supported, planned with Warehouse tasks for
creation of separate supported, planned with a future release. sample quantities can be
warehouse tasks to a future release. For now, warehouse created manually with
move sample quantity tasks for sample support of BAdI
to an inspection area quantities can be /SCWM/EX_WRKC_PA
created manually CK_QTY_PROPOSE
*3 With ERP QM Not applicable Not supported, not Supported
Integration: QIE strategic; documents are
Document Attachments expected to be attached
(e.g. inspection rule, to the QM objects e.g.
inspection document) inspection lot
*4 With ERP QM Not applicable Not supported, not Supported
Integration: Non-100 % strategic, sample
inspection procedure calculation is expected
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 expected
inspection rule to be set up in QM

4In embedded EWM in S/4HANA, only QM inspection lots are used to 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
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 applicable5 Supported Not supported

Master Data Synchronization
to control QM Processes

Recording an inspection Not supported Supported Supported

decision in RF

Recording and tracking quality Not supported Supported Supported

management workload in labor
management

Integration of Quality Not applicable Supported with 1909 Not supported

Inspection Engine to Multiple FPS1
Enterprise Management
Systems

Node “Inspection” in Supported. Supported. Supported.

Warehouse Management Node “Inspection” Node “Inspection” Node “Inspection”
Monitor displays inspection lots displays QIE inspection displays QIE inspection
documents. documents.
Defect Processing Supported Not Supported Not Supported

Returns Processing and Advanced Returns Management (ARM)

Customer returns processing Not supported. Supported. Supported.
without using ARM but No inspection document Usage decision via Usage decision via
inspection document for stock created but only stock inspection document to inspection document to
posting from blocked to free posting from blocked to post from blocked to post from blocked to
free. free. free.
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

5 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

Internal Warehouse Processes

ABC classification based on Supported Supported Supported with SAP
confirmed warehouse tasks EWM 9.5 SP05.
See SAP note 2809838

Direct creation of warehouse Supported Supported; Supported;

request for posting change w/o posting change requests posting change requests
posting change requests can be skipped can be skipped
(Customizing) (Customizing)

Production Integration
Restriction to VMS and JIT See SAP note 2825796 See SAP note 2825796 See SAP note 2668075
Processes
Repetitive Manufacturing Supported for Supported with Supported with
synchronous goods restrictions, see SAP restrictions, see SAP
movements note 1412318 note 1412318

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

Transit Warehousing Supported Supported. Supported

See SAP note 2808265

UI5 App to support carrier Not supported.6 Not supported.6 Supported

access for maintaining dock
appointments DAS

Usage of Additional SAP Products, Industry Solutions, and Integration with other Applications
SAP HANA Live for EWM and Comparable functions provided with CDS views Supported
SAP Smart Business for EWM (see S/4HANA Analytics under Cross-Topics)

Integration with SAP ME for Supported. Automatic Supported. Automatic Supported

goods receipt from production,
components staging and
consumption
notification of staging notification of staging
confirmation from confirmation from
EWM to SAP ME for EWM to SAP ME for
single order staging and single order staging and
confirmation based on confirmation based on
Production Material Production Material
Request. Available with Request. Available with

6A 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; you can also use Dock
Appointment Scheduling functionality in SAP Logistics Business Network

11
 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 Product See SAP note 2838158
(DIMP) system with active which is required in
long material number EWM system
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 restrictions7 Supported
(Add-On to EWM for
Fashion industry to
integrate with a SAP
ERP-AFS system)

7 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

12
2. Deployment differences of embedded EWM in S/4HANA and decentral EWM on S/4HANA
for new features in 1909 (not supported by the business suite releases):

Feature EWM embedded in S/4HANA EWM decentral on S/4HANA

Harmonized production supply Supported Not supported due to system

area (PSA) and control cycle boundaries
maintenance
Kanban strategy Supported Not supported due to system
“Replenishment with boundaries
warehouse task” in EWM
warehouse
Kanban stock transfer via Supported Not supported due to system
Kanban apps in EWM boundaries
warehouse

Kanban status update from Supported Not supported due to system

warehouse task processing boundaries

Visibility of Kanban ID in Supported Not supported due to system

warehouse tasks processing boundaries
and monitoring

Synchronous goods movement Supported Not supported due to system

postings from EWM to MM- boundaries
IM when no delivery is
involved
QM Activation Without Using Supported Not supported
Inspection Rules

QM: Support Inspection Lot Supported Not supported

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

13
3. Deployment differences of embedded EWM in S/4HANA and decentral EWM on S/4HANA
for new features in 2020 (not supported by the business suite releases):

Feature EWM embedded in S/4HANA EWM decentral on S/4HANA

Integration with “JIT supply to Supported Not supported

production”
Integration to QM defect and Supported Not supported.
QM notification Planned with a future release

Synchronous goods movement Supported Not supported due to system

postings from EWM to MM- boundaries
IM when no delivery is
involved:
• Backflush (GI/GR) for
repetitive, discrete and
process manufacturing
• Transaction PPCGO,
CO11N, CO15, COR6N,
CORK and others
• Batch determination in
EWM for component
backflush (REM & PP)
• Document-neutral and
document-specific
reversals
• UI integration with MIGO
Kanban Board: Supported Not supported due to system
• GR for summarized JIT boundaries
call
• GR for in-house REM
production

14
4. Deployment differences of embedded EWM in S/4HANA and decentral EWM on S/4HANA
for new features in 2020 FPS01 (not supported by the business suite releases):

Feature EWM embedded in S/4HANA EWM decentral on S/4HANA

Advanced Shipping and Supported Not supported.

Receiving / EWM-TM Planned with a future release.
integration without
Transportation Units
Synchronous goods receipts for Supported Not supported due to system
external procurement in boundaries
MIGO

5. Deployment differences of embedded EWM in S/4HANA and decentral EWM on S/4HANA

for new features in 2021 (not supported by the business suite releases):

No new deployment differences of embedded EWM in S/4HANA and decentral EWM on S/4HANA were
introduced with in 2021.

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.