Extended Warehouse Management - Developer Workshop
Uploaded by
Libreria ERPExtended Warehouse Management - Developer Workshop
Uploaded by
Libreria ERPLibrería ERP — Sample | libreriaerp.com/us | info@libreriaerp.
com
EWM900
Extended Warehouse Management
- Developer Workshop
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 17
Course Duration: 3 Day(s)
Material Number: 50146808
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
SAP Copyrights, Trademarks and
Disclaimers
© 2022 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 https://www.sap.com/corporate/en/legal/copyright.html 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 may have been machine translated and may contain grammatical errors or
inaccuracies.
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.
© Copyright. All rights reserved. iii
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Typographic Conventions
American English is the standard used in this handbook.
The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
Demonstration
Procedure
Warning or Caution
Hint
Related or Additional Information
Facilitated Discussion
User interface control Example text
Window title Example text
iv © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Contents
vii Course Overview
1 Unit 1: SAP EWM System Deployment and Interfaces
3 Lesson: Exploring SAP EWM Deployment Options
9 Lesson: Describing SAP ERP - SAP EWM Interfaces
17 Lesson: Debugging Cross Systems
21 Unit 2: SAP EWM Transaction Handling
23 Lesson: Transaction Handling in SAP EWM
29 Lesson: Program Testing with the /SCWM/TM_WATCH Assertion
31 Unit 3: SAP EWM Master Data
33 Lesson: Exploring SAP ERP and SAP EWM Master Data
37 Lesson: Accessing SAP EWM Master Data (Service Classes and
Function Modules)
41 Lesson: Exploring SAP ERP and SAP EWM Master Data Use Cases
45 Lesson: Debugging the CIF Distribution
47 Unit 4: Warehouse Core
49 Lesson: Describing the SAP EWM Data Model
53 Lesson: Exploring Warehouse Core Technical Components
63 Unit 5: SAP EWM Delivery Model
65 Lesson: Exploring the SAP EWM Delivery Model
75 Unit 6: SAP EWM Shipping & Receiving
77 Lesson: Accessing SAP EWM Shipping & Receiving Data Model
81 Lesson: Exploring Shipping & Receiving BAdIs
83 Unit 7: SAP EWM Mobile Applications
85 Lesson: Enhancing the Radio Frequency Framework
113 Lesson: Pick by Voice Integration With SAP EWM
127 Lesson: SAP EWM Radio Frequency Applications & ITSmobile
131 Unit 8: Additional Techniques
133 Lesson: Using the Post Processing Framework in SAP EWM
153 Lesson: Exception Handling in SAP EWM
159 Lesson: Enhancing Business Object Processing Framework
Applications
© Copyright. All rights reserved. v
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
165 Unit 9: Appendix
167 Lesson: Cheat Sheet
vi © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
● Developer
● Development Consultant
© Copyright. All rights reserved. vii
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
viii © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
UNIT 1 SAP EWM System Deployment
and Interfaces
Lesson 1
Exploring SAP EWM Deployment Options 3
Lesson 2
Describing SAP ERP - SAP EWM Interfaces 9
Lesson 3
Debugging Cross Systems 17
UNIT OBJECTIVES
● Describe SAP EWM deployment options
● Explain the interfaces between SAP ERP and SAP EWM
● Debug the ERP - EWM interface by stopping the RFC queues on both systems
© Copyright. All rights reserved. 1
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Unit 1: SAP EWM System Deployment and Interfaces
2 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Unit 1
Lesson 1
Exploring SAP EWM Deployment Options
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Describe SAP EWM deployment options
SAP Extended Warehouse Management Deployment Options
This course has been developed with the intention to share experiences from SAP Extended
Warehouse Management (EWM) customer implementation projects.
SAP EWM is — as the name implies — an extended and also extensible warehouse
management system (WMS), which comes with a variety of enhancement options and
frameworks. Enhancing SAP EWM requires both profound ABAP development experience,
and also knowledge of the SAP EWM data models and transaction handling.
With a lack of knowledge of SAP EWM functionality and enhancement options, it can happen
that existing standard functionality is unnecessarily re-developed or, due to incorrect
transaction handling in custom code, data has become inconsistent.
This course provides you with the necessary overview and tools for the following tasks:
● To analyze the solution
● To decide whether an enhancement is necessary
● To develop custom enhancements in an SAP EWM implementation project consistently
and with high performance
Solution Overview: SAP EWM
SAP EWM is a comprehensive warehouse management solution that enables you to improve
the efficiency of your warehouse processes, optimize your workflows, and ultimately,
strengthen your position in the market. SAP EWM gives you maximum transparency of your
stock and processes. You benefit from a sophisticated WMS solution that has been on the
market for more than a decade and is being continuously enhanced with new features, from
simple core processes such as picking using an SAP Fiori app, up to extensive options for the
integration of warehouse automation, pick by voice, or monitoring your warehouse processes
using state-of-the-art dashboards.
© Copyright. All rights reserved. 3
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Unit 1: SAP EWM System Deployment and Interfaces
Figure 1: Solution Details of SAP EWM: Core Processes — A Complete Offering Resulting from Solid, Continuous
Investment
Figure 2: Solution Details of SAP EWM: Cross and Supporting Processes
The figures above show an overview on the functional blocks of SAP EWM: Functionalities
within the warehouse core processes like goods receipt and goods issue, cross-processes like
labor management and supporting areas functionalities of EWM like Material Flow System or
Quality Inspection.
The bullet color of a feature indicates with which SAP EWM release it has become available.
You can use this overview as a cheat sheet on SAP EWM functionality at the beginning of an
SAP EWM implementation project.
Review all SAP EWM standard features and their use for your warehouse implementation
project. In this way, you avoid re-developing a functionality as a custom enhancement that is
already part of the SAP EWM standard solution.
For example: In a custom development project, the statuses of the delivery were re-
developed. This custom development caused inconsistencies in SAP EWM standard status
management.
4 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Lesson: Exploring SAP EWM Deployment Options
Available Solution Architecture for SAP EWM
Figure 3: Available Solution Architecture for SAP EWM
Deployment Options for SAP EWM
Several deployment options exist for SAP EWM. It can be deployed in the following ways:
● As a standalone system (hosted on SAP NetWeaver 7.5 Application Server ABAP, since
release EWM 9.0)
● On SAP SCM Server
● As an add-on to SAP ERP Central Component (ECC)
The option to install SAP EWM as an add-on to SAP ERP no longer exists in SAP S/4HANA,
where you have the option of using SAP EWM embedded in SAP S/4HANA. Installing SAP
EWM as an add-on to SAP ERP is not recommended, at least not for a productive
environment.
Connection to ERP Systems
SAP EWM can be connected to SAP ERP systems (SAP ECC, SAP S/4HANA, third-party ERP
systems) in the following ways:
● As decentralized EWM
● As embedded EWM in SAP S/4HANA
Solution Architecture Options
The following are the typical solution architecture options for running SAP EWM:
● Classical peer-to-peer (P2P) network between the SAP EWM and SAP ERP systems
In this option, there is one central SAP ERP system and one decentralized SAP EWM
system, where multiple warehouses are configured in one instance of SAP EWM. This is a
common approach if the warehouses and the EWM application server are located on the
same continent.
© Copyright. All rights reserved. 5
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Unit 1: SAP EWM System Deployment and Interfaces
● Several SAP ERP or SAP S/4HANA systems, interfaced with one decentralized SAP EWM
system
This is a common use case of logistics service providers: stock of different customers is
managed in one SAP EWM system, but the stock data is replicated from the customer's
individual ERP system. Another use case for this deployment option could be a company
merger: an SAP EWM customer acquires a new company that already runs its own ERP
system. In this deployment option, it is important to harmonize the master data of the
different ERP systems, so that the ERP origin of master data in EWM can be distinguished.
SAP EWM offers functionalities for such distinctions, for example the RFC connection of
the ERP system could be added as a suffix to the EWM product number.
● One central SAP ERP system connected to multiple decentralized SAP EWM systems
This is the recommended deployment option for global organizations with warehouses on
different continents. The SAP ERP system is hosted at the company's headquarter
location, while each subsidiary region runs a local SAP EWM server instance. Thus,
response times of the logistics system (SAP EWM) are faster, as with the warehouse and
EWM application servers located on the same continent, network latency times are
shorter. This option should especially be considered for high-volume and/or automated
warehouses that use mobile applications or the SAP EWM material flow system.
● SAP EWM as add-on to SAP ECC
This option has the advantage that all applications needed to run a warehouse are installed
on the same physical hardware. EWM is closely coupled to ECC, that means, in a
maintenance cycle for the ECC system, also the logistics system EWM would be in
downtime - and vice versa. This can be an option for proof of concept or test systems, but
not for warehouses that are running around the clock. This option still requires the
replication of master data via the Core Interface (CIF) and application data via queued RFC
(qRFC). We do not recommend using this deployment option if your roadmap foresees
conversion of an existing SAP ERP system into an SAP S/4HANA on-premise system, as
then SAP EWM has to be uninstalled before the SAP S/4HANA conversion.
● SAP EWM embedded in SAP S/4HANA
As of release 1610, this is a new solution for less complex warehouses, offering
simplification of data exchange between the SAP ERP system and SAP EWM. This solution
replaces the SAP EWM add-on to SAP ERP. As of SAP S/4HANA 1610, embedded EWM is
the default offering, but traditional ECC-WM is still available. However, the life span of
traditional ECC-WM component is limited to 2025. Most of the capability of decentralized
EWM is retained in embedded EWM.
Decentralized EWM (integrated with SAP ERP or SAP S/4HANA on premise) is planned to be
a long-term valid deployment option for SAP EWM for good reasons. These include regional
EWM systems, risk mitigation, specific planned down-times, scale-out for large data centers,
multiple SAP ERP systems connected, different release cycles, proximity to warehouse (MFS,
RF), and so on.
Additional Information
Resource Link
SAP Extended Warehouse https://help.sap.com/viewer/p/SAP_EXTENDED_WARE-
Management <9.x> Mas- HOUSE_MANAGEMENT -> Installation and Upgrade
ter Guide
6 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Lesson: Exploring SAP EWM Deployment Options
Resource Link
SAP Note 1606493 SAP EWM Deployment Options Best Practices
SAP Note 224193 SAP S/4HANA, on-premise edition 1511: Process Integration
with SAP on-premise solutions
SAP Note 2376061 Integration to decentral EWM
SAP EWM on SAP HANA Database
Figure 4: SAP EWM on SAP HANA Database
SAP EWM (and SAP ECC) can run on any database supported by SAP NetWeaver 7.5, or SAP
HANA DB.
To run on SAP HANA, SAP EWM must be upgraded to at least release 9.1 and SAP NetWeaver
to at least release 7.4. For database migration to SAP HANA, we recommend an upgrade to
SAP EWM 9.2 or higher.
The release on the SAP HANA database does not imply any functional changes or functional
enhancement to SAP EWM.
All scenarios and all functions in SAP EWM can be used on SAP HANA in the same way as on
any other supported database.
EWM Labor Demand Planning (LDP) is designed for SAP EWM running on a SAP HANA
database. This is due to the forecast calculation of LDP, which uses an advanced time-series
algorithm from the SAP HANA predictive analysis library (PAL).
SAP EWM Deployment Options for SAP S/4HANA
Figure 5: SAP EWM Deployment Options for SAP S/4HANA
© Copyright. All rights reserved. 7
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Unit 1: SAP EWM System Deployment and Interfaces
SAP EWM Embedded in SAP S/4HANA is the new EWM deployment option as of SAP S/
4HANA 1610 on premise. This the long-term solution to replace SAP WM and is targeted for
small and midsize warehouse, or production warehouses.
SAP WM is part of SAP S/4HANA, but will run out of maintenance and usage rights by 31
December 2025. The same applies for the decentralized SAP LES solution.
Main Advantages of SAP EWM Embedded in SAP S/4HANA
One system
● Simplification of master data
● No more data replication via CIF
● Support for 40–digit material number
Avoid data redundancy
● Direct access to central objects like deliveries and orders
● Skip delivery requests in inbound and outbound processing and posting changes
● No need for transaction /SCWM/EGR (Expected Goods Receipt). Inbound delivery can be
created directly in SAP EWM embedded in SAP S/4HANA.
Additional Information
Resource Link
SAP Maintenance Strategy https://support.sap.com/en/release-upgrade-maintenance/
maintenance-information/maintenance-strategy.html
SAP Product Availability https://apps.support.sap.com/sap/support/pam
Matrix
SAP Note 2269324 Compatibility Scope Matrix for SAP S/4HANA, on-premise edi-
tion
SAP Note 2347770 (1610) Release information and restrictions for SAP EWM in SAP S/
SAP Note 2494704 (1709) 4HANA
● Major differences between embedded EWM and decentral-
ized EWM
● Restrictions in other areas when using EWM
LESSON SUMMARY
You should now be able to:
● Describe SAP EWM deployment options
8 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Unit 1
Lesson 2
Describing SAP ERP - SAP EWM Interfaces
LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain the interfaces between SAP ERP and SAP EWM
Describing SAP ERP - SAP EWM Interfaces
SAP ERP - SAP EWM Integration
Figure 6: SAP ERP - SAP EWM Integration
In SAP EWM embedded in SAP S/4HANA, that is, the “one system” scenario, master data
tables are shared and therefore CIF is no longer needed for master data transfer between the
SAP ERP and SAP EWM systems.
In the standard SAP EWM - SAP ERP integration scenario, there are three techniques for data
replication:
CIF To transfer master data, such as material master (product mas-
ter), batches, customers, vendors (business partners), plants,
and storage locations.
Queued remote function To transfer application data between SAP ERP and SAP EWM,
calls (qRFC) such as deliveries, QIE inspection documents, and goods move-
ments.
© Copyright. All rights reserved. 9
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Unit 1: SAP EWM System Deployment and Interfaces
IDoc interface/Applica- ● To replicate shipments (transportation units) using IDoc
tion Link Enabling (ALE) SHPMNT<xx>
● To connect non-SAP systems with SAP EWM using the inter-
face EWM-WCU (Warehouse Control Unit), for example, to
connect automated warehouse systems with SAP EWM (IDoc
WMTORD, WMTOCO, and so on, for warehouse task (WT)
creation and confirmation)
CIF is in general a single-direction replication, that is, master data is transferred from SAP
ERP to SAP EWM, but updates on SAP EWM are not replicated back to SAP ERP.
However, batches can also be created in SAP EWM first. The batch creation in SAP EWM is
communicated via qRFC to the SAP ERP system. The batch is then created in ERP and
communicated back to EWM via CIF. This has the advantage that a batch can be created in
EWM and warehouse operations would not be impacted in the case of an ERP system
downtime (in a decentralized EWM installation).
Transferring Additional Data between SAP ERP and SAP EWM
Figure 7: Data Containers to Transfer Additional Data between SAP ERP and SAP EWM
In order to transfer additional data between SAP ERP and EWM, you can use structured and
unstructured data containers for customer exit parameters.
The unstructured data container of type BAPIEXTC consists of four generic components,
each of which is 250 characters long. It is recommended that you use this data container to
transfer a large amount of additional data.
Figure 8: Unstructured Data Container to Transfer Additional Data between SAP ERP and SAP EWM
10 © Copyright. All rights reserved.
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Lesson: Describing SAP ERP - SAP EWM Interfaces
Figure 9: Structured Data Container to Transfer Additional Data between SAP ERP and SAP EWM
If only a few short values, like inspection lot numbers or alternative handling unit (HU)
identifiers are to be transferred between SAP EWM and SAP ERP, the structured data
container of type BAPIEXT is the recommended transfer container type, as less data would be
transferred between the systems.
Figure 10: Example for transferring additional data between SAP EWM and SAP ERP
Example:
● A code with a value of 2 characters is transferred using FIELD1 of the unstructured data
container, type BAPIEXTC.
This means that 998 characters out of a total data length of 1000 characters (four fields of
250 characters each) of the structure BAPIEXTC are unused but occupying the
communication channel.
● A free text entered to a delivery is to be transferred to EWM. The text could be split up into
four fields of 250 characters each of unstructured data container type BAPIEXTC in SAP
© Copyright. All rights reserved. 11
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Librería ERP — Sample | libreriaerp.com/us | [email protected]
Unit 1: SAP EWM System Deployment and Interfaces
ERP prior to delivery distribution, and then be transferred using the full capacity of the
extension structure from SAP ERP to SAP EWM.
● For further actions to be executed in SAP ERP, the HU ID and quantity are transferred from
SAP EWM. A table of structured data container type BAPIEXT is used to transfer the data,
including field name and data type, to SAP ERP. This also enables robust programming, as
data type checks on the transferred data are possible.
PARAM HU QTY UOM
ROW 1 2 3
FIELD HUIDENT QTY UOM
VALUE 003300000010000037331 13.000 EA
TYPE CHAR QUAN UNIT
LENGTH 20 6 3
SAP ERP BAdI Methods to Transfer Additional Data from SAP ERP to SAP EWM
Figure 11: SAP ERP BAdI Methods to Transfer Additional Data from SAP ERP to SAP EWM
To change or transfer additional inbound or outbound delivery data during replication from a
central ERP system to a decentralized EWM system using the scenarios SAVE_REPLICA and
CONFIRM_DECENTRAL, use the following BAdI exit in SAP ERP:
BAdI SMOD_V50B0001
Methods Description
EXIT_SAPLV50K_005 BAdI method for replication of inbound deliveries
EXIT_SAPLV50K_007 BAdI method for replication of outbound deliveries
EXIT_SAPLV50K_011 BAdI method for changes to inbound delivery
EXIT_SAPLV50K_012 BAdI method for changes to outbound delivery
Additional Information
Resource Description
SAP Note 351303 Transfer of additional delivery data in decentralized scenario
