SAP

EWM & SAP S/4HANA – EXTERNAL FAQ

FAQ
V4

SAP EWM and SAP S/4HANA

Frequently Asked Questions
May, 2017, V4

SAP EWM & SAP S/4HANA – EXTERNAL FAQ


SAP EWM & SAP S/4HANA – EXTERNAL FAQ

The purpose of this document is to provide an external audience with a

selection of frequently asked questions and answers about SAP EWM in
combination with SAP S/4HANA.

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

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

1 Table of Contents
1 SAP EWM and SAP S/4HANA Enterprise Mangement ..................................... 5
1.1 General Information ....................................................................................................... 5
1.1.1 What is the current status for SAP EWM in combination with SAP
S/4HANA? ................................................................................................................................................... 5
1.1.2 After the embedded EWM was released, will the de-central EWM option still
exist in a long run? .................................................................................................................................. 7
1.1.3 Are different functions provided in the de-central-EWM and the embedded
EWM? 7
1.1.4 “Simplified Integration” was mentioned here earlier with for the embedded
EWM within SAP S/4HANA. What does this mean? ................................................................. 8
1.1.5 There are two editions of the SAP S/4HANA: on-premise and cloud. Does
the information indicated above hold for both? ........................................................................ 8
1.2 Impact on LE-WM module ............................................................................................. 8
1.2.1 Once the embedded EWM is in place, will the LE-WM module be retired at
once? 8
1.2.2 Is LE-WM module in S/4HANA only applicable for customers migrating
from ERP WM to S/4HANA WM? ...................................................................................................... 8
1.2.3 De-central LE-WM has been deployed with my SAP ERP. If I migrate SAP
ERP to SAP S/4HANA, will the de-central LE-WM still be supported? ............................ 9
1.2.4 Does LE-WM in S/4HANA have the same structure and functions as SAP
ERP? Which funtions of LE-WM are not available in S/4HANA? ........................................ 9
1.2.5 Lean WM is part of LE-WM. As LE-WM is planned to phased out after 2025,
what will SAP offer for this function? ............................................................................................. 9
1.3 Migration ............................................................................................................................ 9
1.3.1 What do I need to consider if I run SAP ERP+WM and would like to migrate
to SAP EWM with SAP S/4HANA? .................................................................................................... 9
1.4 Deployment Options .................................................................................................... 10
1.4.1 Customer is using LE-WM already and plans to implement embedded EWM
for new warehouses. Is it possible to run both solutions in parallel on the same
S/4HANA system? ................................................................................................................................ 10
1.4.2 Could we use an embedded EWM warehouse and a de-central EWM
warehouse running in parallel with S/4HANA ? ..................................................................... 10
1.4.3 Do we need to migrate our existing de-central EWM to embedded EWM if
we convert our ERP to S/4HANA ? ............................................................................................... 11
1.4.4 Do we need to upgrade our existing de-central EWM if we convert our ERP
to S/4HANA ? .......................................................................................................................................... 11
1.4.5 How do I decide the best suitable deployment option in my specific case? 11
1.5 License ............................................................................................................................. 11
1.5.1 If I want to connect SAP EWM to SAP S/4HANA, is the licensing different
from SAP EWM connecting to SAP ERP? .................................................................................... 11
1.5.2 Do my customers who want to run on embedded EWM in SAP S/4HANA
need to pay separately? ..................................................................................................................... 12
1.5.3 What kind of user licenses are required for embedded EWM in SAP
S/4HANA? ................................................................................................................................................ 12
1.5.4 How to convert old licenses sold before Q2 2014 or between Q2 2014 and
Q4 2016 if customers want to implement embedded EWM in SAP S/4HANA? ........ 12
1.5.5 How will SAP audit if customers start with basic warehouse management
and wants to activate advanced warehouse management functionalities? ................ 13

3

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

1.6 Outlook – Roadmap on SAP EWM ............................................................................ 13

2 SAP S/4HANA Supply Chain for EWM – on-premise edition 1610 .......... 14
2.1 Functions ......................................................................................................................... 14
2.1.1 Are the Fiori apps shipped with EWM 9.4 also available in the embedded
EWM in S/4HANA 1610? ................................................................................................................... 14
2.1.2 Is Merchandise Distribution available in the embedded EWM in S/4HANA
1610? 14
2.1.3 We’re using LE-TRA to group deliveries into shipments. Is it possible to use
it together with the embedded EWM in S/4HANA? .............................................................. 14
2.1.4 Customers like the new Belize and Fiori LaunchPad. Can it also be applied
to the de-central EWM systems? .................................................................................................... 14
2.1.5 Where do I find the list of different features & functions of embedded EWM
in S/4HANA1610 compared with EWM 9.4? ............................................................................ 14
2.1.6 Can we activate the S/4HANA long material number when de-central EWM
system is integrating with this S/4HANA system? ................................................................ 15
2.1.7 Is the ERP Handling Unit Management (HUM) and the EWM HUM combined
to a single HUM solution ? ................................................................................................................ 15
2.2 Mobile Strategy ............................................................................................................. 15
2.2.1 Which technology is available to run mobile warehouse transactions in the
embedded EWM? Is ITS Mobile still supported in S/4HANA? .......................................... 15
2.2.2 Are there FIORI apps available for mobile warehouse processes? ................. 16
2.3 System Conversion and Landscape ........................................................................ 16
2.3.1 Is it possible to convert from EWM on top of ERP to embedded EWM in
S/4HANA? ................................................................................................................................................ 16
2.3.2 Is it possible to convert (upgrade) from de-central EWM to embedded EWM
in S/4HANA? ........................................................................................................................................... 16
2.3.3 Does SAP offer a migration service to migrate a EWM warehouse from one
system to another, e.g. from de-central EWM to embedded EWM in S/4HANA ? .... 16
2.3.4 The customer likes embedded EWM in S/4HANA but has still legacy ERP or
SAP ERP systems running. Is it possible to connect embedded EWM in S/4HANA
against another ERP system? .......................................................................................................... 16
2.3.5 Is there a Best Practice for System Landscape, including development and
test systems for custom development, in case that both de-central and embedded
EWM are used ? ..................................................................................................................................... 17
2.4 SAP Best Practices ........................................................................................................ 17
2.4.1 What is SAP S/4HANA Best Practices content for the embedded EWM and
what do I get out of it? ........................................................................................................................ 17
2.4.2 Is the best practice content covering basic or advanced warehouse
management features? ....................................................................................................................... 18
2.4.3 Where can I find SAP Best Practices for EWM? ........................................................ 18
2.4.4 How to activate the best practice content for embedded EWM in S/4HANA
1610? 19
3 Where can I learn more about SAP S/4HANA? .............................................. 20

4

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

1 SAP EWM and SAP S/4HANA Enterprise Mangement

1.1 General Information
1.1.1 What is the current status for SAP EWM in combination with SAP S/4HANA?

SAP S/4 HANA, the Digital Core, is the next generation of ERP to modernize
for Digital Business. The SAP lines of business solutions continue to be
consumed as standalone solutions or as part of the SAP S/4HANA Lines of
Business solutions giving more choice to customers, allowing true hybrid
scenarios and incremental deployments.

The graphic below shows how we plan to deliver SAP EWM, one of the key
SAP Lines of Business Solutions, in combination with the on-premise edition
of SAP S/4HANA to two separate customer options for product integration on
the SAP HANA platform.

5

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

SAP Extended Warehouse Management

Product road map overview - key themes and capabilities

Recent innovations 2017 – Planned innovations 2018 – Product direction 2019 – Product vision

SAP EWM embedded in SAP SAP EWM embedded in SAP SAP Extended Warehouse SAP Extended Warehouse
S/4HANA* 1 S/4HANA* Management (embedded in SAP Management (embedded in
• One System requirements • Additional processes between S/4HANA* + core) SAP S/4HANA* + core)
– No Core Interface S/4HANA Quality Management and • Automotive industry enhancements such • Simulation and forecasting
– SAP Fiori UX enablement embedded EWM as JIT, Supply to line, Additional Kanban • Industry-specific enhancements
– Direct read of Actual data scenarios
• Product Master Enhancements – Retail & E-commerce
– Support Material field Length • Expanded Warehouse Automation-
Enhancement • Warehouse Analytics using core – Pharmaceutical
data services (CDS) Physical inventory at HU level, Putaway
• Reduced Data Redundancy – Utilities
strategies, sequencing
– Skip Delivery Request objects • Supporting changes of outbound – Mill
• Extended integration with SAP S/4HANA
– Eliminate QIE from quality deliveries handed over to EWM
– Further QM scenarios
management processes
– Further Production scenarios
– Replacement of EGR document
• Simplifications SAP EWM (core) • Additional IoT scenarios like exchanging
• Advanced Labor Management warehouse events with IoT applications
• Best practice content
• Advanced e-commerce functionality
SAP EWM 9.4 2 (core) • Additional SAP Fiori apps like:
• Advanced warehouse optimization
• Warehouse Automation (MFS) – Work Center apps such as packing,
• Supply Chain Execution platform • TCI/TCO topics repacking
• Traceability / Batch Management – Mobile task confirmation
• Industry related topics – Warehouse planning
• Usability • Enhanced analytics for SAP Extended
Warehouse Management
1
SAP S/4HANA 1610 release
2
SAP Extended Warehouse Management 9.4 *SAP S/4HANA Supply Chain for extended warehouse management This is the current state of planning and may be changed by SAP at any time.

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.
© 2017 SAP SE or an SAP affiliate company. All rights reserved. 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 non-infringement
Customer 11

Since Q4/2015, SAP EWM has been able to be connected to SAP S/4HANA
(on-premise edition 1511, as indicated in the SAP Note 2241931) using a
sidecar approach based on the same technology employed for
communication with SAP ERP — that is, asynchronous data transfer by qRFC
(queued Remote Function Calls) via the CIF (Core Interface) integration layer.

SAP EWM is de-centralized deployed on a separate server platform.

The sidecar approach as an option for integration with SAP S/4HANA
supports business scenarios and processes of complex and automated
warehouse and distribution centers. The two deployment options are SAP

6

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

EWM as part of SCM Server or deployed on SAP NetWeaver. We’ll refer to the
sidecar approach as “de-central EWM” in this document.

In Q4/2016, SAP EWM became an embedded application component
within SAP S/4HANA (on-premise edition 1610), known as S/4HANA
Supply Chain Management for extended warehouse management. To
make it simple, we’ll call it “embedded EWM” in this document.

With the release of it, both basic warehousing and extended warehouse
management are running on a common code base embedded in SAP
S/4HANA.

The embedded approach as a deployment option within SAP S/4HANA
supports less complex or non-high throughput warehouses with a simplified
integration to S/4HANA business processes.

As a long term plan, the de-central EWM and the embedded EWM are being
developed based on a common core of warehouse management funtions.

1.1.2 After the embedded EWM was released, will the de-central EWM option
still exist in a long run?

Our plan is to make available to you the option of SAP EWM sidecar to SAP
S/4HANA as a long-term solution for sound business reasons, among which:
• A de-centralized deployment solution provides proven customer value,
such as high volume data processing, risk mitigation, and scalability for
large distribution centers.
• This solution safeguards SAP EWM data when existing SAP ERP+EWM
customers decide to migrate their ERP system to SAP S/4HANA.
• This deployment also allows for connection to multiple ERP or S/4
systems.

1.1.3 Are different functions provided in the de-central-EWM and the embedded
EWM?

Our goal is to provide the same functions when using either option. In other
words, they’ll share a common core of warehouse functions, which is planned
to evolve overtime with new features for both.

With the common core, both options will cover the same business scenarios
and processes, while at the same time exceptions exist.

For example, the embedded EWM and the de-central EWM will integrate with
SAP S/4HANA core processes by different technical features.

7

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

1.1.4 “Simplified Integration” was mentioned here earlier for the embedded
EWM within SAP S/4HANA. What does this mean?

Technically, the simplified integration of the embedded EWM within the on-
premise edition of S/4HANA is reached by adoption of a unified data model
(that is, new product code line). The goal is to simplify the data model as
much as possible. The major simplifications are as follows:

• Core Interface is not used any more for master data including businesss
partner, material master and batch.
• Redundant customizing tables are eliminated.
• Direct read of actual data in SAP S/4HANA is realized instead of
replication, for example, material values, accounting objects, purchase
orders, production orders, etc..

1.1.5 There are two editions of the SAP S/4HANA: on-premise and cloud. Does
the information indicated above hold for both?

No. The plan described in this document applies to the on-premise edition
of innovation products in SAP S/4HANA, only.

1.2 Impact on LE-WM module

1.2.1 Once the embedded EWM is in place, will the LE-WM module be retired at
once?

In the business interests of existing customers, the LE-WM module is planned
initially remain available in SAP S/4HANA as one of the “Compatibility
Package” solutions, the details of which were stated in the SAP Note
2269324.

As mentioned in the note, SAP provides customers a limited use right to
run certain classic SAP solutions on S/4HANA installations (including LE-
WM), provided customers have licensed the applicable solutions as set forth
in their license Agreements. This use right expires on Dec 31, 2025.

1.2.2 Is LE-WM module in S/4HANA only applicable for customers migrating from
ERP WM to S/4HANA WM?

As stated in 1.2.1, LE-WM remains available until the end of 2025, and this is
also applicable to customers who didn’t run WM before. However,
considering the use right and businesss needs, we sincerely suggest
customers evaluate the necessity before they decide to go with LE-WM, as
EWM has been the strategic warehouse solution of SAP with all the
innovations developed all along.

8

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

1.2.3 De-central LE-WM has been deployed with my SAP ERP. If I migrate SAP ERP
to SAP S/4HANA, will the de-central LE-WM still be supported?

The key interface component to support de-central LE-WM is LE-IDW, and
this is still available in SAP S/4 Hana as of today. Therefore you can
definitely keep working with your de-central LE-WM deployment after the
SAP S/4HANA migration.

Please be noted that the maintenance of SAP ERP will end at the end of
2025*. Until then, as long as SAP S/4HANA continues supporting the LE-IDW
interface, the de-central LE-WM will be possible.

*Note: please always refer to the Product Availability Matrix for the SAP ERP
maintenance end year, in case of any changes.

1.2.4 Does LE-WM in S/4HANA have the same structure and functions as SAP
ERP? Which funtions of LE-WM are not available in S/4HANA?

There are limitations for the enterprise extensions (including TRM, VAS,
Yard Management). Customers cannot activate the enterprise extensions in
an S/4HANA system. If those extensions have been activated in SAP ERP,
they will be available after the system is converted from ERP to S/4HANA.

1.2.5 Lean WM is part of LE-WM. As LE-WM is planned to phased out after 2025,
what will SAP offer for this function?

SAP doesn’t plan to provide this function by using a lean version of EWM.
Instead, SAP plans to provide functions to replace Lean WM in a future
release.

1.3 Migration
1.3.1 What do I need to consider if I run SAP ERP+WM and would like to migrate
to SAP EWM with SAP S/4HANA?

You’ll have to decide which option to go with – de-central EWM or embedded
EWM, and your business needs shall be considered with priority, e.g.,
warehouse scalability, data volume, budget, and roll out plan, etc..

SAP provides tools to facilitate with migration from LE-WM to EWM as
follows:

9

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

For Master Data migration:

o Migrate warehouse product (Transaction /SCWM/MIG_PRODUCT)
o Migrate storage bins (Transaction /SCWM/MIG_BIN)
o Migrate Stock (Transaction /SCWM/MIG_STOCK)
o Migrate Physical Inventory completeness (Transaction
/SCWM/MIG_PI_COMPL)

For Warehouse Layout migration:
o Storage type migration
o Bin types/Storage Unit types migration
o Storage section migration
o Picking area migration
o Door/Staging area migration

Other migration tools:
o Migrate LE-WM queues to EWM queues
o Migrate LE-WM movement types to EWM warehouse process
types
o Migrate put-away, picking and replenishment strategies

In addition, a migration guide is available here in the service market place. In
case you can’t get to the document directly by clicking the link, please copy
the link and open it in an internet browser.

1.4 Deployment Options

1.4.1 Customer is using LE-WM already and plans to implement embedded EWM
for new warehouses. Is it possible to run both solutions in parallel on the
same S/4HANA system?

EWM and WM can be run in parallel on a single S/4HANA client. The
warehouses must be linked to different storage locations. It is not possible to
run a single warehouse (single storage location) with a mixture of WM and
EWM processes.

1.4.2 Could we use an embedded EWM warehouse and a de-central EWM
warehouse running in parallel with S/4HANA ?

Yes, on the same S/4HANA client, it is allowed to have some warehouses
implemented with embedded EWM, some warehouses implemented with de-
central EWM, some warehouses implemented with LE-WM, and some
warehouses implemented with de-central LE-WM. All 4 scenarios are allowed
to be used at the same time on the same ERP client, in this case, S/4HANA
client.

10

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

1.4.3 Do we need to migrate our existing de-central EWM to embedded EWM if

we convert our ERP to S/4HANA ?

No. You can continue running de-central EWM and no changes are expected
on the EWM side. There’re good reasons to run de-central warehouse
applications (see 1.1.2) and SAP will always support this in the future.

1.4.4 Do we need to upgrade our existing de-central EWM if we convert our ERP
to S/4HANA ?

No, if your de-central EWM has a version of EWM 7.0 SP13 and above. From
this version onwards the de-central EWM has been released to be integrated
with S/4HANA. See release notes 2241931 and 2376061.

1.4.5 How do I decide the best suitable deployment option in my specific case?

SAP Note 1606493 ‘SAP EWM Deployment Options Best Practices’ provides
some hints on the various different decision criteria. The embedded EWM in
S/4HANA is similar to EWM-on-ERP. One of the important decision criteria is
the system sizing. SAP offers a Quicksizer tool which also provides a ‘HANA
version’ of Quick Sizing. Within the HANA Version of the Quick Sizer Tool you
find the embedded EWM sizing tool in ‘SAP S/4HANA->EWM Inbound’ and
‘SAP S/4HANA->EWM Outbound’.

In case of large rollout plans SAP recommends an SAP DBS service to evaluate
the specific requirements and boundary conditions and to create a
recommended proposal for EWM deployment strategy. SAP already has
experience in such a service including the new option of the embedded EWM
in S/4HANA.

1.5 License
1.5.1 If I want to connect SAP EWM to SAP S/4HANA, is the licensing different
from SAP EWM connecting to SAP ERP?

If SAP EWM is connecting to SAP S/4HANA system as sidecar (de-centralized
deployment), and running on a non-HANA database, the license material
number is the same as SAP EWM connecting to SAP ERP.

If SAP EWM is connecting to SAP S/4HANA system as sidecar (de-centralized
deployment), and running on a HANA database, the license material number
is different.

Please contact your local pricing contacts for details.

11

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

1.5.2 Do my customers who want to run on embedded EWM in SAP S/4HANA

need to pay separately?

Basic warehousing functions of embedded SAP EWM are included in the SAP
S/4HANA Enterprise Management license. Advanced functions will require
the ‘classic’ SAP EWM engine license. The Advanced and Basic funtions are as
follows:

Warehouse Management with SAP S/4HANA

Supporting all levels of warehouse complexity
Advanced Warehouse Management
•  Inventory Management Optimization (e.g. Slotting) Optimize
•  Inbound Process Optimization (e.g. Deconsolidation) warehouse
•  Outbound Process Optimization (e.g. Waves) operations
SAP S/4HANA SUPPLY CHAIN
•  Material Flow Control
•  Yard Management (e.g. TU handling, DAS)
•  Labor Management
•  Value Added Services
Suite
•  Kitting
•  Cross Docking
Products •  Extended Warehouse Management •  Warehouse Billing

Digital Core •  Basic warehouse management Stock

Basic Warehouse Management transparency
•  Inventory Management and control
•  Inbound Processing
•  Outbound Processing
Enterprise Management
•  Internal Warehouse Movements
•  Physical Inventory
•  Reporting

©  2016 SAP SE or an SAP affiliate company. All rights reserved. Internal

Internal & Partner 17


The de-central EWM always requires the ‘classic’ SAP EWM engine license no
matter using advanced or basic features or not.


1.5.3 What kind of user licenses are required for embedded EWM in SAP
S/4HANA?

Warehouse transactions affect inventory management, production and
shipping/receiving functions which are all core S/4HANA business events.
SAP S/4HANA users can be used also for EWM. Most warehouse workers use
a limited transaction set very intensively. These are typically operators on
forklifts or with manual picking equipment and generally account for 80% of
warehouse personnel. For these workers, the S/4HANA Productivity User
may be employed.

1.5.4 How to convert old licenses sold before Q2 2014 or between Q2 2014 and
Q4 2016 if customers want to implement embedded EWM in SAP
S/4HANA?

The conversion is the same as any SAP Business Suite conversion. A full
credit for the licenses paid is applied to embedded EWM in SAP S/4HANA.

12

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

The pricing method does not change for embedded EWM in S/4HANA,
although there are new license material codes. Please contact your local
pricing contacts for details.

1.5.5 How will SAP audit if customers start with basic warehouse management
and wants to activate advanced warehouse management functionalities?

Customers are able to switch on the advanced feathure usage on warehouse
number level. An audit report can be run to check whether system usage
complies with the actual settings.

1.6 Outlook – Roadmap on SAP EWM

Please visit SAP Road Maps, and navigate to Browse All Roadmaps -> Line
of Business -> Products -> Supply Chain Management -> SAP Extended
Warehouse Management, from which you are able to get the up-to-date
SAP EWM Roadmap information.

13

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

2 SAP S/4HANA Supply Chain for EWM – on-premise edition

1610

2.1 Functions
2.1.1 Are the Fiori apps shipped with EWM 9.4 also available in the embedded
EWM in S/4HANA 1610?

The Lean Warehouse Clerk app is available with the same functions.

The E-Commerce Return app is not available as Quality Management is not
able to process customer returns inspection yet. It is planned to close this gap
in a future release.
2.1.2 Is Merchandise Distribution available in the embedded EWM in S/4HANA
1610?

In S/4HANA 1610 most of the IS-Retail Business Functions are always active,
so the functionality behind it is available by default. However, the business
function ISR_RET_CD/FT_EWM ‘Retail, Merchandise Distribution-SAP EWM
Integration’ is not always on but switchable by customers like in the former
IS-Retail ERP system.

In S/4HANA Merchandising the functionality of Cross docking and Flow
Through is active and functional useable.

2.1.3 We’re using LE-TRA to group deliveries into shipments. Is it possible to use
it together with the embedded EWM in S/4HANA?

EWM can be used together with LE-TRA in S/4HANA 1610 to communicate
shipment information.

2.1.4 Customers like the new Belize and Fiori LaunchPad. Can it also be applied to
the de-central EWM systems?

No, Belize Theme is only available in S/4HANA 1610 and not available in the
latest classic Suite versions like EWM 9.4 (de-central EWM). See public
information chapter 3 of:
https://experience.sap.com/documents/sap-fiori-2-0-welcome-pack-master-
document.pdf .

2.1.5 Where do I find the list of different features & functions of embedded EWM
in S/4HANA1610 compared with EWM 9.4?


SAP EWM & SAP S/4HANA – EXTERNAL FAQ

This list is published in SAP Note 2347770. In addition, you can access the
S/4HANA system to check the content of DB-table SBLM_BLACKLIST which
contains those ABAP artifacts monitored by the ABAP kernel to not being
executed in an S/4HANA system. Also all custom Z-code that calls these ABAP
Artifacts will be stopped with a dump.

2.1.6 Can we activate the S/4HANA long material number when de-central EWM
system is integrating with this S/4HANA system?

Starting from EWM 9.4 SP04, the long material number is supported.

For EWM9.4 with a lower SP version than SP04, the SAP Note 2405257 is
available for customers to manually implement corrections to support long
material number. However, it’s highly recommended to upgrade to SP04, as
the code corrections are very large.

For EWM version lower than 9.4, the S/4HANA long material number is not
yet supported, as stated in the restriction note 2232396. So from EWM
integration aspect the ‘long material number’ of S/4HANA shall not be
activated. In case the long material number is urgently needed for other
S/4HANA processes (which do not integrate with de-central EWM), note
2287625 is required to be implemented in S/4HANA system. In this scenario,
operational measures are required to prevent materials from being used in
the EWM integration which has an actual key length longer than 18.

2.1.7 Is the ERP Handling Unit Management (HUM) and the EWM HUM combined
to a single HUM solution ?

No, there are still two separate technical HUM for the ERP applications and
EWM. For de-central EWM, both HUM are integrated via delivery interfaces
between EWM Deliveries and LE Deliveries. An example of this integration is
stock transfer process which has planned inbound deliveries based on the
EWM HUM data of shipping HUs in the outbound delivery. The UI integration
of both HUM solutions has been included in the development backlog, e.g.
showing EWM HUs in ERP Handling Unit Monitor (Trasaction HUMO), but
this is plan only and no timeline is in place yet for the availability of it.

2.2 Mobile Strategy

2.2.1 Which technology is available to run mobile warehouse transactions in the
embedded EWM? Is ITS Mobile still supported in S/4HANA?

Customers want to execute the warehouse processes on mobile devices to
confirm picking, putaway, replenishment, counting etc. In de-central EWM
the technology is ITS mobile to render an ABAP based screen into HTML, so it

15

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

can be executed on mobile devices. In S/4HAHA ITS Mobile is still supported.

There’s no change compared with EWM 9.4.

2.2.2 Are there FIORI apps available for mobile warehouse processes?

FIORI simplifies the system interaction and requires less training. In
S/4HANA 1610, one Fiori apps is available for the embedded EWM: The Lean
Warehouse Clerk app deals with simple and quick goods receipt and goods
issue; and in the de-central EWM 9.4, one additional Fiori app Customer
Returns is available to help to receive and put away/scrap returns with high
efficiency.

2.3 System Conversion and Landscape

2.3.1 Is it possible to convert from EWM on top of ERP to embedded EWM in

S/4HANA?

This is not possible because the EWM Add-ON on ERP is not released for
S/4HANA onPremise edition. SAP will provide a de-installation tool very
soon which allows to de-install EWM-on-ERP as a pre-requisite step before
this system can be converted to an S/4HANA system.

2.3.2 Is it possible to convert (upgrade) from de-central EWM to embedded EWM
in S/4HANA?

This is not provided. It is not possible to upgrade a de-central EWM-on-SCM
or EWM-on-NW to an S/4HANA system. There is no technical upgrade path
either.

2.3.3 Does SAP offer a migration service to migrate a EWM warehouse from one
system to another, e.g. from de-central EWM to embedded EWM in
S/4HANA ?

No, SAP is not (yet) providing such a standard service. In general SAP DBS
offers these kind of services for other application areas if there is a business
case for SAP (i.e. many customers requesting and paying for it).

2.3.4 The customer likes embedded EWM in S/4HANA but has still legacy ERP or
SAP ERP systems running. Is it possible to connect embedded EWM in
S/4HANA against another ERP system?

This deployment is currently not considered as a standard deployment. To
run embedded EWM in S/4HANA you need local S/4HANA master data and
local S/4HANA delivery documents. See note 2347770 (release restrictions of

16

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

EWM in 1610): there it is explicitly stated that the embedded EWM can be
integrated only with the local client in the local system.

2.3.5 Is there a Best Practice for System Landscape, including development and
test systems for custom development, in case that both de-central and
embedded EWM are used ?

Yes, but this
1. Depends on the type of custom development: whether it is in ‘Common
Core EWM’ only or also in the S/4HANA Adapter Layer:
a. If it is foreseeable that only development in the ‘common core
EWM’ is required, then the dev & test systems for this custom
development can be based on a de-central EWM system. After
successful test the new features can be transported to the test
landscape of S/4HANA for the functional validation with
embedded EWM.
b. If custom development in the EWM S/4HANA Adapter Layer is also
required (e.g. static usage of ERP ABAP artifacts in the custom
code), then an S/4HANA system has to be the basis for the custom
development. When using an S/4HANA system as the basis for
custom development it is recommended to use a separate ABAP
transport layer for ‘Common Core EWM’ developments and
developments in the EWM S/4HANA Adapter Layer. With the
separate transport layer the developments in ‘Common Core EWM’
can be transported to a de-central EWM test system to validate
there the syntactical and functional correctness of the
development in a system w/o ERP applications like SD and LE.
2. Depends on the upgrade strategy of S/4HANA productive system
compared to the de-central EWM productive system: if it is not feasible to
keep the EWM software versions of embedded EWM and de-central EWM
in sync (only a few days or weeks until all system are upgraded to the
next same version), then it is recommended to have separate dedicated
landscapes (DEV, Test, QAP, PROD) for supporting the different versions.
This is the same procedure like it had to be used in case of using several
ERP instances with non-aligned upgrade cycles or using several de-
central EWM systems with non-aligned upgrade cycles.

2.4 SAP Best Practices

2.4.1 What is SAP S/4HANA Best Practices content for the embedded EWM and
what do I get out of it?

17

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

SAP S/4HANA Best Practices content is the recommended content delivery

for SAP S/4HANA product. With the SAP S/4HANA Best Practices content for
EWM, customers get a new warehouse XX10 (XX = Country Code) with its
pre-defined warehouse structure, related customizing, sample master data
and business processes based on this setup. The key features and benefits are
as follows:
§ Quickly enable pre-configured basic warehouse management processes
using a clearly defined scope and explicit guidance
§ Comprehensive configuration settings, Test Scripts, Process Diagrams and
other valuable assets, which can be used as accelerators in
implementation projects
§ Fully compliant to one system requirements and simplifications such as
No CIF, use of S/4HANA Business Partner, Central Master Data, direct
usage of S/4 Customizing (e.g. HU Types) and direct read of purchase
order (no EGR).
§ Predefined warehouse structure and sample master data
§ SAP Fiori Launchpad Enabling - unified user experience across all UI
technologies
§ Support of Germany and USA Localization

2.4.2 Is the best practice content covering basic or advanced warehouse

management features?

The S/4HANA 1610 content is showcasing ‘basic warehousing’ and none of
the advanced features which would require an extra license is used.

2.4.3 Where can I find SAP Best Practices for EWM?

The SAP Best Practices Explorer is the new and simplified web channel to
search, browse and consume SAP Best Practices. The SAP S/4HANA EWM
Best Practices are part of the SAP Best Practices for SAP S/4HANA (on
premise) solution package.

SAP Best Practices Explorer
§ Link: https://rapid.sap.com/bp
§ Navigate to SAP S/4HANA -> On-Premise -> SAP Best Practices for SAP
S/4HANA (on-premise) -> Scope Item Group “Supply Chain”

You’ll find the materials of the six pre-configured basic warehouse
management processes offered in S/4HANA 1610 release as follows:

§ Basic Inbound Processing from Supplier
§ Basic Outbound Processing to Customer
§ Physical Inventory
§ Replenishment

18

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

§ Scrapping
§ Initial Stock Upload

The materials include process description and test scripts which provide the
details on master data & customizing setup as well as business end user
transactions.

Additional information about the SAP Best Practices for EWM are provided
via SAP Note:
§ Link: https://launchpad.support.sap.com/#/notes/2351332

2.4.4 How to activate the best practice content for embedded EWM in S/4HANA
1610?

With the SAP S/4HANA 1610 OP (on premise) edition, the EWM content is
documentation only, which means it has to be implemented manually after
the Best Practices solution package is implemented. The automated
activation of the EWM content using the Solution Builder is planned to be
available with the next SAP S/4HANA on-premise release.

19

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

3 Where can I learn more about SAP S/4HANA?

Visit us on sap.com/s4hana.

SAP EWM & SAP S/4HANA – EXTERNAL FAQ

© 2017 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.
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. Please see
http://global12.sap.com/corporate-en/legal/copyright/index.epx for
additional trademark information and notices.
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 SE or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP SE 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, which
speak only as of their dates, and they should not be relied upon in making
purchasing decisions.

21