You are on page 1of 113

Authors: see list of

authors in section 1

SAP EWM 7.00: High-Performance
Warehouse Management for Retailers

Version: 1.0 History
Version Date Status (Comments)
rd
1.0 3 August 2010 First Publication

Table of Contents
1 About This Document .................................................................................................. 3
2 Disclaimers and Legal Information ............................................................................. 4
3 Introduction .................................................................................................................. 7
4 Technical Landscape ................................................................................................. 13
4.1 Targeted Production Landscape ............................................................................................ 13
4.2 Test Environment .................................................................................................................... 14
4.2.1 Load Driver and System under Test .......................................................................................... 14
4.2.2 System under Test - Hardware/Software Layout ........................................................................ 15
4.2.3 EWM Backend – Storage Configuration..................................................................................... 16
4.2.4 EWM Backend – Important Periodic Batch Jobs ........................................................................ 17
4.2.5 Database Filling Level ............................................................................................................... 18
4.3 System Tuning and Important SAP Notes ............................................................................. 19
4.3.1 Parameterization of the Enqueue Table..................................................................................... 19
4.3.2 Parameterization of the ICM ...................................................................................................... 19
4.3.3 Configuration of the Update Task System.................................................................................. 19
4.3.4 DB2 Parameters ....................................................................................................................... 19
4.3.5 Missing Indexes ........................................................................................................................ 20
5 Setup of EWM Scenarios ........................................................................................... 21
5.1 Master Data and Warehouse Layout ...................................................................................... 21
5.2 Inbound ................................................................................................................................... 22
5.3 Outbound................................................................................................................................. 23
5.4 Flow-Through .......................................................................................................................... 23
5.5 Cross-Docking ........................................................................................................................ 23
5.6 Material Flow System .............................................................................................................. 24
5.7 Application Tuning .................................................................................................................. 24
6 Performance Results .................................................................................................. 26
6.1 Methodology............................................................................................................................ 26
6.2 Inbound Scenario .................................................................................................................... 28
6.2.1 Processing of Incoming Inbound Deliveries ............................................................................... 28

High Performance Warehouse Management
for Retailers

6.2.2 Dialog Performance .................................................................................................................. 29
6.2.3 Dialog Throughput and Resource Consumption......................................................................... 31
6.2.4 Scalability Test for Unloading Process....................................................................................... 33
6.3 Outbound Scenario ................................................................................................................. 34
6.3.1 Processing of Incoming Outbound Delivery Orders and Wave Creation ..................................... 34
6.3.2 Dialog Performance .................................................................................................................. 36
6.3.3 Dialog Throughput and Resource Consumption......................................................................... 42
6.3.4 Guaranteed Picking Response Time ......................................................................................... 46
6.3.5 Picking and Staging Scalability Test .......................................................................................... 47
6.4 Flow-Through Scenario .......................................................................................................... 49
6.4.1 Processing of Incoming Inbound and Outbound Deliveries ........................................................ 49
6.4.2 Dialog Performance .................................................................................................................. 49
6.4.3 Dialog Throughput and Resource Consumption......................................................................... 54
6.5 Cross-Docking Scenario ......................................................................................................... 55
6.5.1 Processing of Incoming Deliveries ............................................................................................. 55
6.5.2 Dialog Performance .................................................................................................................. 55
6.5.3 Dialog Throughput and Resource Consumption......................................................................... 58
6.6 Simultaneous Inbound/Outbound Scenarios......................................................................... 59
7 Conclusions and Outlook .......................................................................................... 63
8 APPENDIX ................................................................................................................... 64
8.1 Detailed Customizing Settings ............................................................................................... 64
8.1.1 Basics ....................................................................................................................................... 64
8.1.2 Master data and Warehouse Layout .......................................................................................... 66
8.1.3 Inbound..................................................................................................................................... 70
8.1.4 Outbound .................................................................................................................................. 71
8.1.5 Flow-Through ............................................................................................................................ 76
8.1.6 Cross-Docking .......................................................................................................................... 77
8.1.7 MFS .......................................................................................................................................... 78
8.2 Scenario Specifications .......................................................................................................... 83
8.2.1 Inbound Scenario ...................................................................................................................... 84
8.2.2 Outbound Scenario ................................................................................................................... 88
8.2.3 Cross-Docking ........................................................................................................................ 101
8.2.4 Flow Through .......................................................................................................................... 105

© 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page
Dietmar-Hopp- Retailers 2 of 113
Allee 16 Version: 1.0
D-69190 Walldorf Document Date: August 2010

High Performance Warehouse Management
for Retailers

1 About This Document
Many leading retail companies create value by using their most efficient, high-performance retail
warehouse logistics as the backbone of their commercial success. SAP understands the importance of a
comprehensive proof of technology and performance for the latest versions of mission-critical SAP
Extended Warehouse Management (EWM) in Retail.
Therefore SAP has used intensive performance tests to prove the reliability and scalability of SAP EWM
and hence its capacity to provide essential and comprehensive up-to-date performance and configuration
information to optimize retailers’ investments.
This document supplements the higher level white paper (see http://service.sap.com/scm -> Warehousing -
> Information on Extended Warehouse Management in SAP SCM -> White Papers), which is assumed to
have been read prior to this document. The document at hand is intended to guide and facilitate SAP EWM
implementation projects by means of detailed technical insights about the chosen EWM process
configuration setup and applied technical optimizations. Furthermore, this document shall enable
successor test projects to conduct analogous application test scenarios.
The target audience of this document is SAP EWM consultants and other SAP EWM-skilled members of
EWM implementation projects or test projects, as well as technical staff who are in charge of system tuning
and configuration.
At first, the document describes the technical landscape which was used in the test, and then the
application scenario setup details (e.g. Customizing) are described. Then the test methodology and results
are presented for each scenario, as well as the results of simultaneously processed scenarios which
simulate a real-life ‘peak hour in the life of warehouse processing’. Some focus tests on scalability and
‘extreme transaction rate’ for essential warehouse process steps complement the results of the scenario
tests, which remain within the technical domain of the scenario specification.
This document was created by the following contributors and authors, grouped by department and
alphabetical order therein:
o Andreas Gnacke, SAP Value Prototyping / Center of Excellence (CoE) - EWM Prototyping Lab,
SAP AG, Walldorf, Germany.
o Peter Jaeger, SAP Value Prototyping / Center of Excellence (CoE) - High Performance Lab, SAP
AG, Walldorf, Germany.
o Dr. Nikolai Sauerwald, SAP Performance and Scalability, SAP AG, Walldorf.
o Werner Schwarz, SAP Performance and Scalability, SAP AG, Walldorf.
o Tobias Adler, SAP EWM Development, SAP AG, Walldorf, Germany.
o Dr. Andreas Daum, SAP EWM Development, SAP AG, Walldorf, Germany.
o Wolfgang Neufing, SAP EWM Development, SAP AG, Walldorf, Germany.
o Dietmar Schuetze, SAP Business Unit Retail Supply Chain, SAP AG, Walldorf, Germany.

This document is published at http://service.sap.com/scm -> Warehousing -> Information on Extended
Warehouse Management in SAP SCM -> SAP EWM 7.0.

© 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page
Dietmar-Hopp- Retailers 3 of 113
Allee 16 Version: 1.0
D-69190 Walldorf Document Date: August 2010

always use your own proprietary design style when creating and producing a marketing piece. legality. copyright compliance. In the absence of a response. or other third party. downloaded. or decency of material contained in sites listed in the directory or in the Materials. and we ask our users to do the same. High Performance Warehouse Management for Retailers 2 Disclaimers and Legal Information General Disclaimer SAP does not represent or endorse the accuracy or reliability of any of the information. INCIDENTAL. SAP – Guidelines for Using SAP Trademarks Throughout the world. nor would they be able to readily identify the superior quality that SAP trademarks represent. Guidelines for Using SAP-Copyrighted Material © 2006 SAP AG SAP EWM 7. information. INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. the Guidelines for Using SAP Trademarks shall govern any and all uses. to make improvements to. You hereby acknowledge that any reliance upon any Materials shall be at your sole risk. THE SERVICE AND THE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS. the "Materials") contained on. PUNITIVE. based on volume of requests you should allow several weeks for a response. nor the quality of any products. partner. Therefore. in appropriate circumstances and in its sole discretion. INDIRECT. However. WITH RESPECT TO THE SERVICE OR ANY MATERIALS AND PRODUCTS. EXPRESS OR IMPLIED. or linked. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT. or obtained by you as a result of an advertisement or any other information or offer in or in connection with the Service (the "Products"). or correct any error or omissions in any portion of the Service or the Materials. terminate the accounts of users that infringe or otherwise violate such rights of others. OR CONSEQUENTIAL DAMAGES OF ANY KIND WHATSOEVER WITH RESPECT TO THE SERVICE.0 D-69190 Walldorf Document Date: August 2010 . SAP will make reasonable efforts to respond to your request. please direct your inquiry to trademarks@sap.00: High Performance Warehouse Management for Page Dietmar-Hopp. Designing Marketing Material If you are a developer. distributed through. If you believe that your work has been copied in a way that constitutes copyright infringement. customer. and so SAP isn't responsible for the accuracy. SAP encourages you to exercise discretion while browsing the Internet using this site. If after reviewing the Guidelines for Using SAP Trademarks you still have a question about use. You must not copy the SAP design style or borrow any SAP design elements. content. SAP respects the rights (including the intellectual property rights) of others. AND THE PRODUCTS. SAP may. consumers would not be able to distinguish SAP solutions from those of other companies. please follow the instructions at the top of this page. please see the following information: SAP trademarks and SAP offering names Proper use of trademarks Additional trademark usage information for third parties Trademark usage information for all print and online media. in its sole discretion and without any obligation. thousands of customers recognize and select SAP solutions on the basis of the company's trademarks and service marks. THE MATERIALS. Without these trademarks and service marks (collectively referred to as "trademarks"). or advertisements (collectively. AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES. SAP reserves the right. it is critically important that trademarks of SAP and its subsidiaries are protected. SAP makes no representations concerning any endeavor to review the content of sites linked to this site or any of the Materials. For guidelines on trademark usage. which signify high-quality computer software products and services.com. Retailers 4 of 113 Allee 16 Version: 1. or accessed from any of the services contained on this Web site (the "Service"). purchased. or other materials displayed.

Windows. Redbooks. All other product and service names mentioned are the trademarks of their respective companies. Inc. Inc.. POWER5+. The information contained herein may be changed without prior notice. All rights reserved. XML. System p. Linux is the registered trademark of Linus Torvalds in the U. and Motif are registered trademarks of the Open Group. S/390 Parallel Enterprise Server. MetaFrame. eServer. Power Architecture. MVS/ESA. Crystal Decisions. OS/400. you must include a copyright notice – either in an adjacent area or as a footnote – to indicate SAP's copyright. Oracle is a registered trademark of Oracle Corporation. System x.S. and other countries. z10. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. iSeries. System z10. Retailers 5 of 113 Allee 16 Version: 1. JavaScript is a registered trademark of Sun Microsystems. WebSphere. IBM. SAP. In addition.00: High Performance Warehouse Management for Page Dietmar-Hopp. and other materials from SAP sources must be approved by SAP. in the United States and in other countries. National product specifications may vary. WinFrame. pSeries. Business Objects and the Business Objects logo. Netfinity. Program Neighborhood. RACF. xSeries. ByDesign. OS/2. PowerVM. OS/390. System p5. Duet. BusinessObjects. PostScript. All rights reserved. Excel. POWER6+. Web Intelligence. © 2006 SAP AG SAP EWM 7. POWER. AIX.A. System i5. System i. AS/400. X/Open. images. PowerPC. Data contained in this document serves informational purposes only. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. VideoFrame.0 D-69190 Walldorf Document Date: August 2010 . OSF/1. SAP NetWeaver. and MultiWin are trademarks or registered trademarks of Citrix Systems. Intelligent Miner. PartnerEdge. Inc. R/3. BladeCenter. Microsoft. Business Objects is an SAP company. ICA." Please note that SAP photography is only licensed for SAP use and must not be used by third parties in their communications. used under license for technology invented and implemented by Netscape. z/VM. System z. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. HACMP. POWER5. The copyright should read as follows: "© SAP AG <year>. i5/OS. System z9. OpenPower. S/390. SAP – Copyrights and Trademarks ENGLISH – German version below © Copyright 2010 SAP AG. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Citrix. BatchPipes. Java is a registered trademark of Sun Microsystems. SAP Business ByDesign. RETAIN. graphics. Crystal Reports. XHTML and W3C are trademarks or registered trademarks of W3C®. DB2 Universal Database. when using such materials. and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S. POWER6. z/OS. Outlook. UNIX. the Adobe logo. HTML. and PowerPoint are registered trademarks of Microsoft Corporation. Acrobat. screen shots. GPFS. Xcelsius. Adobe. zSeries. z9. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. System Storage. Massachusetts Institute of Technology. DB2. DB2 Connect. Parallel Sysplex. World Wide Web Consortium. High Performance Warehouse Management for Retailers The use of original texts.

Java ist eine eingetragene Marke von Sun Microsystems. System p. HACMP. z/OS. Alle Rechte vorbehalten. GERMAN © Copyright 2010 SAP AG. Aus den in dieser Publikation enthaltenen Informationen ergibt sich keine weiterführende Haftung. Citrix. XHTML und W3C sind Marken oder eingetragene Marken des W3C®. RACF. ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. ByDesign. Crystal Decisions. High Performance Warehouse Management for Retailers These materials are subject to change without notice. System i5. POWER5+. z9. Retailers 6 of 113 Allee 16 Version: 1. Die vorliegenden Angaben werden von SAP AG und ihren Konzernunternehmen ("SAP-Konzern") bereitgestellt und dienen ausschließlich Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. BusinessObjects. if any. POWER6. Adobe. Tivoli und Informix sind Marken oder eingetragene Marken der IBM Corporation. © 2006 SAP AG SAP EWM 7. Web Intelligence. PowerVM. WinFrame. Massachusetts Institute of Technology. eServer. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services. xSeries. OS/400. XML. OS/2. System i. DB2 Connect. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. System z10. S/390. ICA. X/Open. Netfinity. die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MetaFrame. POWER5. in den USA und anderen Ländern. Microsoft. A.0 D-69190 Walldorf Document Date: August 2010 . Acrobat. zSeries. Nothing herein should be construed as constituting an additional warranty. Der SAP-Konzern steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein. Excel. OS/390. Redbooks. zu welchem Zweck und in welcher Form auch immer. Business Objects und das Business-Objects-Logo. System Storage. in den USA und/oder anderen Ländern. Crystal Reports..00: High Performance Warehouse Management for Page Dietmar-Hopp. Business Objects ist ein Unternehmen der SAP. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Program Neighborhood. DB2 Universal Database. AIX. Duet. without representation or warranty of any kind. Oracle ist eine eingetragene Marke der Oracle Corporation. SAP Business ByDesign und weitere im Text erwähnte SAP-Produkte und - Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern. GPFS. S/390 Parallel Enterprise Server. R/3. AS/400. Xcelsius und andere im Text erwähnte Business-Objects-Produkte und -Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der Business Objects S. Der SAP-Konzern übernimmt keinerlei Haftung oder Garantie für Fehler oder Unvollständigkeiten in dieser Publikation. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind. Inc. Windows. PartnerEdge. System z. MVS/ESA. Outlook und PowerPoint sind eingetragene Marken der Microsoft Corporation. z10. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only. PowerPC. System p5. PostScript und Reader sind Marken oder eingetragene Marken von Adobe Systems Inc. WebSphere. System z9. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. POWER. Intelligent Miner. BatchPipes. IBM. BladeCenter. DB2. POWER6+. Power Architecture. OSF/1 und Motif sind eingetragene Marken der Open Group. World Wide Web Consortium. Inc. Inc. i5/OS. Parallel Sysplex. UNIX. iSeries. pSeries. and SAP Group shall not be liable for errors or omissions with respect to the materials. z/VM. OpenPower. VideoFrame und MultiWin sind Marken oder eingetragene Marken von Citrix Systems. HTML. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. RETAIN. Linux ist eine eingetragene Marke von Linus Torvalds in den USA und anderen Ländern. SAP NetWeaver. JavaScript ist eine eingetragene Marke der Sun Microsystems. das Adobe Logo. System x. SAP.

The throughput numbers are normalized to a frequency of unit ‘per hour’. several standard correction notes were created.g. which is the most frequent and thus most important RF-based system interaction done in parallel by many users.0 as a component of SAP SCM 7. Most of these KPIs are derived from the following requirements: Being able to ship 420.0 SP04). so that such an attempt could produce misleading results. The response time overview table shows only the major dialog steps which run very complex or mass functions in the system. The KPIs are related to the three different areas of system throughput.000 product items) and the highest required throughput numbers.6) show only minor deviations.1. and some additional performance optimizations have to be applied by means of changing configuration settings. dialog response time and general business requirements. With all these tuning a set of target KPIs (Key Performance Indicators). For details about the test methodology please see section 6. Thus it is highly recommended that at least SP06 is deployed to the EWM/SCM system in order to benefit from this test and achieve comparable system performance. Please note that this SAP SCM 7.0 release is the so-called stable core release.5. were investigated with this experimental test. In the course of the test. The exploration of these technical limits was not a test goal. many of which are independent of SAP EWM application architecture. which are contained in SP05 and SP06 of SAP EWM. with an assumed large adoption by many SAP customers.0 D-69190 Walldorf Document Date: August 2010 . Retailers 7 of 113 Allee 16 Version: 1.000 delivery items by means of 10 picking waves within a time frame of around 10 hours Being able to reserve only a minor part of the night-time period for EWM delivery creation based on received ERP deliveries Warehouse workers experiencing almost imperceptible system response times from their mobile devices so as not to hinder their high volume of frequent consecutive execution steps The tables provide an overview of the results which were measured with the most challenging parameter set called ‘Scale B’ which comprises the largest single objects (e. All these additional notes and performance optimization settings are described in this document.0. See section 6. thus providing a real-time system interaction user experience. several additional notes of other software components are needed. Besides these major dialog steps. as derived from business process needs.00: High Performance Warehouse Management for Page Dietmar-Hopp. In the case of picking and staging. For the raw measurement data please see section 6. there also exist minor dialog steps in process with much shorter response times (usually shorter than 50ms). Transactions could either run automatically in the system without user interaction (referred to as ‘background processing’). it was only experimentally confirmed that the required throughput KPIs were fulfilled. Besides deployment of SP06 for SCM software components. could be run by office clerks (referred to as ‘desktop’). The listed throughput numbers do not approach the technical limitations of SAP EWM. which often depend heavily on many factors. a further investigation was conducted to show that the system throughput capabilities are far beyond the required KPI. The listed response times are the results of the single scenario tests. delivery with 1. Thus the test focused on the validation of a well-defined business scenario rather than investigating technical limits. High Performance Warehouse Management for Retailers 3 Introduction The test was conducted with SAP EWM 7.3. or could be run by warehouse workers with mobile devices (referred to as ‘RF’). The test system was installed on SP04 level of all SCM software components (including EWM 7. The response times of the simultaneous scenario test (see section 6. The measured throughput numbers are based on the test procedure which was derived from the required KPIs. © 2006 SAP AG SAP EWM 7. although in several cases the measurement time span was shorter than 1 hour.

After Measurement data: saving the Outbound Delivery Order a PPF action is processed 420. Picking (RF) and Staging (RF) 42. Outbound Delivery Creation with 420. < 1 hour 1.000 items. High Performance Warehouse Management for Retailers Throughput related KPIs Goal Throughput as measured by Test Procedure Inbound Delivery Creation Some few thousand items per Extrapolated rate: (received via ERP Interface.615 delivery items and wave Delivery Request (ODR) is items / hour (Scale A) created and activated. ( 370.000 item picks in 17 min 1680 HU staging in 17 min Tests proofed linear scalability of picking and staging up to a picking rate of 180.680 HUs and staged in < 1 148.929 ship HU staging / hour Measurement data (Scale B): 42. The Outbound 486. Retailers 8 of 113 Allee 16 Version: 1.000 Delivery Items and wave Extrapolated rate: picking wave planning and items created in < 2 hours 296. Advanced Shipping Notifications This activation creates the Inbound Delivery (ID).000 delivery items / hour background processing).000 picks per hour.588 packed items / hour ) © 2006 SAP AG SAP EWM 7.824 ship HU / hour loaded within < 10 min. The Outbound Delivery Request (ODR) is created and activated.000 items in 20 min.000 HUs / hour (IDN) is created and activated. Delivery creation is either 80. Loading (RF) 1.000 items.235 picks / hour hour 5.0 D-69190 Walldorf Document Date: August 2010 .000 HUs in 45 seconds Outbound Delivery Creation 420. 85 min (Scale B) for the ODO which assigns the 420.000 items in 45 seconds 2. 420.680 ship HUs (containing Extrapolated rate (Scale B): 42.471 delivery items and wave assignment (received via ERP items / hour (Scale B) interface.260.000 delivery items picked into Extrapolated rate (Scale B): 1. 52 min (Scale A) ODO items to wave items. The based on ERP purchase order Inbound Delivery Notification data or based on suppliers 160. Measurement data: This activation creates the Outbound Delivery Order (ODO). hour.000 delivery items / hour background processing).000 Delivery Items created in Extrapolated rate: (received via ERP interface. This activation creates the Outbound Delivery Order (ODO).00: High Performance Warehouse Management for Page Dietmar-Hopp. Measurement data: 1.000 packed delivery items) 14. background processing).

6 min.000 items) in 16.6 min. Delivery Note Creation 42. The goods 1000 items < 5 min.8 Sec. Goods Issue of Truck Load and 42 Trucks with 42. picking Warehouse Order (WO) 20 min Last picking WO after 20 min.7 min. High Performance Warehouse Management for Retailers Measurement data (Scale B): 1. Major step 2. Major step 0. Staging (RF) All steps < 0.000 delivery items in 10.9 Sec. Delivery Note creation for a Delivery Note(s) creation for truck Major step 1. creation (Desktop) Picking (RF) All steps < 0.3 Sec. Major step 0.8 min.000 items Extrapolated rate (Scale B): Truck Departure (Desktop).680 HUs (42.1 min.9 Sec. Extrapolated rate (Scale B): (Desktop). Loading per truck (RF) All ‘once per truck steps’ < 5 Sec.514 delivery items / hour Delivery is created based on the related ODO(s) of a Transportation Unit. Major steps ‘start loading’ and ‘loading finished’ 2.000 delivery items in < 15 min. The Outbound 235. for a Transportation Unit. and the Outbound Delivery is printed.000 delivery/wave items in < First picking WO after 15 min. Major step 0.0 D-69190 Walldorf Document Date: August 2010 . (Scale A) single truck load (Desktop). (Scale B) issue posting is done for a © 2006 SAP AG SAP EWM 7. Loading per HU (RF) All HU-related steps < 0. packed in 1. (Scale A) truck load (Desktop).000 packed items) loaded to 42 TUs in < 7 min.680 shipping HUs in 152 Trucks / hour These functions are processed < 20 min. Goods Issue Posting for a single Goods Issue for truck load of Major step 2.9 Sec. Measurement data (Scale B): 42. Table 1: Throughput-related KPIs Response Time KPIs Goal Response Time Measured by Test Procedure Picking Wave Release and 42. (Scale B) Outbound Delivery is created for a Transportation Unit.00: High Performance Warehouse Management for Page Dietmar-Hopp. The load of 1000 items < 5 min. Major step 1.807 delivery items / hour ) Measurement data (Scale B): 42 trucks (with 42.0 Sec. (151.3 Sec.5 min. Retailers 9 of 113 Allee 16 Version: 1.

000 SAPS. Major step 0.0 D-69190 Walldorf Document Date: August 2010 .9 Sec.200 SAPS with max.00: High Performance Warehouse Management for Page Dietmar-Hopp.5 Sec.9 Sec.000 SAPS outbound process and wave release for follow-up outbound wave was possible with a system which has in total 111. Putaway (RF) All steps < 0. i. Major step 0. < 5 min. Major step 0. Linear scalability of the software Hardware resource consumption Linear increasing CPU utilization when increasing throughput / increases linearly with the load of and constant response times in number of users the system.8 Sec.5 min. Unloading Preparation (Desktop). 90% CPU utilization. distribution/picking (RF) Merchandise Cross-Docking / All steps < 0. (Scale B) an Inbound Delivery in the and 400 HU < 2 min. in the unloading desktop UI for all (Scale B) HUs of an Inbound Delivery. inbound simultaneous process test script reliably and without any process and release of follow-up showed no performance malfunction due to concurrency wave shall run reliably without bottlenecks or other malfunctions effects bottlenecks Table 3: System sizing and process implementation KPIs © 2006 SAP AG SAP EWM 7.3 Sec.e. Unloading (RF) All steps < 0. Merchandise Flow-Through All steps < 0. unloading desktop UI. in the range of inbound process. response time picking and staging with up to remains (almost) stable 410 parallel users and a CPU utilization of 82% Process Configuration in SAP Process setup and execution Processes as required by retail EWM shall be possible within SAP business blueprint were EWM standard without any implemented within SAP modification and/or additional standard development All required system activities for a Simultaneous large scale Repeated runs of the large retail warehouse shall run outbound process.3 min.9 Sec. Retailers 10 of 113 Allee 16 Version: 1.9 Sec. 400 unloading tasks created in Major step ‘unloading and The unloading tasks are created putaway task creation’ 3. Goods Receipt (Desktop). Major step 0. picking wave 100. The Goods receipt for truck load with Major step ‘goods receipt’ goods receipt posting is done for inbound delivery of 200 items 0.7 Sec. Picking (RF) Table 2: Response time-related KPIs Business KPIs Goal Result of Test Procedure Absolute Hardware Sizing Lower or equal to Retail Industry Simultaneous processing of typical range. High Performance Warehouse Management for Retailers Transportation Unit. When assuming linear utilization/SAPs relation this would mean a utilization of 100.

Transportation TU Smallest loadable unit of a vehicle that is used to transport goods. Notification © 2006 SAP AG SAP EWM 7. The inbound delivery notification is used to create an inbound delivery. This process starts with the receipt of the goods in the yard and ends with the handing over of the goods for final put-away. The following list provides an explanation of the SAP terms referred to: Term Abbreviation Definition Handling Unit HU Physical unit consisting of packaging materials and the products they contain.00: High Performance Warehouse Management for Page Dietmar-Hopp. The outbound delivery request is used to create an outbound delivery order. Outbound ODO Document that contains all the relevant data required for triggering and Delivery Order monitoring the complete outbound delivery process.sap. Retailers 11 of 113 Allee 16 Version: 1. scan-enabled identification number. which was written without using SAP-specific terminology. A handling unit (HU) has a single. High Performance Warehouse Management for Retailers In contrast to the higher level white paper (see http://service. Advanced ASN Notification by the vendor to the recipient regarding the pending arrival Shipping of goods shipped or about to be shipped. production. Warehouse WT Document used to execute goods movements. The warehouse order is composed of warehouse tasks or physical inventory items. or outbound delivery. Outbound OD Document that records the goods that are delivered to a goods Delivery recipient. Inbound ID Document that contains all data necessary for triggering and Delivery monitoring the complete inbound delivery process. Outbound ODR Document in the outbound delivery process containing all relevant Delivery logistics data from the initiator of the outbound delivery process (such Request as the sales order). The outbound delivery order is either used as a preview for planning upcoming warehouse activities or to create the outbound delivery. The Unit transportation unit (TU) can be a fixed part of the vehicle. Warehouse WO Document that represents an executable work package that a Order warehouse worker is to execute at a specific time. Wave Pick Wave Work package for controlling picking in the warehouse. A warehouse task can Task be based on logical or physical goods movements or changes to stocks.0 D-69190 Walldorf Document Date: August 2010 . Inbound IDN Document in the inbound delivery process containing all relevant Delivery logistics data from the initiator of the inbound delivery process (such as Notification the shipping notification. This process starts with the first planning activities for the outbound delivery and extends to the loading and shipping of the goods. delivery note or purchase order). this document uses SAP EWM terminology in order to assist the readers in finding the technical entities in the SAP EWM system.com/scm -> Warehousing -> Information on Extended Warehouse Management in SAP SCM -> White Papers).

Retailers 12 of 113 Allee 16 Version: 1. the faxing of order confirmations.00: High Performance Warehouse Management for Page Dietmar-Hopp. for Frequency example an EWM system. Radio RF Mobile device could be connected via RF with a SAP system.0 D-69190 Walldorf Document Date: August 2010 . The system System is often controlled by software which runs in a PLC. known as RF transactions. the Framework printing of delivery notes. Material Flow MFS Hardware system which automates material movements. or the triggering of approval procedures). EWM provides tailored transactions for the small UI of typical mobile devices. High Performance Warehouse Management for Retailers Post PPF Component that provides SAP applications with a standard interface Processing for the condition-dependent generation of actions (for example. Programmable PLC Underlying controller that controls the physical transportation in Logic Controller conveyor technology. Table 4: Glossary © 2006 SAP AG SAP EWM 7.

© 2006 SAP AG SAP EWM 7. The EWM backend exchanges business documents such as delivery notifications with an SAP ERP system.sap.0. These devices are usually equipped with a scanner so that bar codes on the handling units can be scanned and the related data be sent to the backend.00: High Performance Warehouse Management for Page Dietmar-Hopp.2.sap. section 4. The PCO must be run in a Microsoft Windows environment (see SAP Product Availability Matrix). The devices are connected via SAP ITS Mobile technology over the http protocol.3 focuses on system tuning and important SAP Notes that must be considered in the course of an implementation project. material handling trucks etc.com/instguides SAP Business Suite Applications SAP SCM SAP EWM Using SAP EWM 7. Finally.com/instguides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP SCM 7.) with mobile devices that are wirelessly connected to the backend. Retailers 13 of 113 Allee 16 Version: 1.sap.0 and the Application Operations Guide for EWM 7. The PLC is connected to the backend via SAP Plant Connectivity (SAP PCO).0.0 can be downloaded from http://service.1 Targeted Production Landscape The principle layout of a typical EWM production landscape is shown in Figure 1.com/instguides SAP Business Suite Applications SAP Manufacturing SAP Manufacturing Integration and Intelligence Plant Connectivity 2.2. The operations guide is especially important with regard to periodic batch jobs that need to be scheduled in the production environment (see section 4.4). The documents are transferred via qRFCs. The installation of the backend is described in http://service. The setup captures the crucial performance aspects of the EWM backend and can be seen as an abstraction of a typical productive landscape which is described in section 4.1. Although EWM can be deployed on top of an SAP ERP system. In addition the EWM backend exchanges telegrams with the Programmable Logic Controller (PLC) for control of the automated high rack storage. The technical details (load generation and hardware/software layout) are provided in section 4. High Performance Warehouse Management for Retailers 4 Technical Landscape This chapter is dedicated to the technical setup of the test landscape.0 Server Installation Guides. Guides related to the PCO release employed in this test can be found under http://service. EWM-related guides such as the Master Guide for SAP EWM 7. End users can be broadly grouped into two classes: those who work in the office with the SAP Frontend (SAPGUI) running on desktop PCs and those who work at the handling units (pallets. 4.0 D-69190 Walldorf Document Date: August 2010 . In the center stands the EWM backend. which is technically an SAP SCM system. we do not recommend this option for a high-performance environment.

004 as the underlying RDBMS.2. The http and SAPGUI load is generated with HP LoadRunner 9.1 running on a MS Windows 2003 server. The test landscape does not contain an ERP system. The EWM backend is installed as an SCM 7. This method is sufficient © 2006 SAP AG SAP EWM 7. the EWM backend installed on an IBM pSeries P595 server with a DS8000 storage system attached and secondly the PLC emulation system. The LPAR has an equivalent of ca. Retailers 14 of 113 Allee 16 Version: 1.0 GHz CPUs and SMT (simultaneous multithreading) enabled.5.2 Test Environment This section presents the technical details of the test environment. The EWM telegrams are exchanged via RFC. 117000 SAPS.1). the storage layout. Therefore the ingoing qRFCs (which are usually sent by an SAP ERP system) are created in the EWM system with an ABAP program.0 SP04 system with DB2 9.1 Load Driver and System under Test The high-level layout of the test environment is shown in Figure 2. The PCO converts these into TCP/IP based PLC messages. For the emulation of a PLC a tool is provided by the SAP Center of Excellence / Value Prototyping. periodic batch jobs and the database filling level.00: High Performance Warehouse Management for Page Dietmar-Hopp. The system under test consists of two servers: firstly. High Performance Warehouse Management for Retailers Figure 1: Targeted production landscape 4. The setup of the system under test is described in the subsequent sections including the crucial hardware/software parameters. This Java-based PLC emulation is deployed on a MS Windows 2003 VMWare server and connected via SAP PCO (Plant Connectivity) to the SCM system. 4. A high-level description comprising the load generators and the system under test is given in the first section (4.2.0 D-69190 Walldorf Document Date: August 2010 . It is highly recommended to deploy at least SP06 to the EWM/SCM system in order to benefit from this test and meet comparable system performance. The SCM as well as the RDBMS software is running on a single LPAR with up to 21 dual core POWER 6 5.

the storage system which hosts the file systems used by the EWM system and the Windows server which runs the PCO and PLC emulation. Retailers 15 of 113 Allee 16 Version: 1. High Performance Warehouse Management for Retailers for simulating the ERP interface and for measuring the performance of the EWM programs that process the incoming ERP documents. Figure 2: Test environment 4. In the course of the processing of deliveries the EWM system creates qRFC queues that are to be sent to the connected ERP system. The outgoing queues. hence need not be in the scope of the test.Hardware/Software Layout Figure 3 provides more details on important hardware and software parameters. The EWM system as part of the SCM 7. which has 42 dedicated cores (21 dual core processors) and 220 GB RAM. It shows three building blocks of the landscape: the LPAR that hosts the EWM backend.00: High Performance Warehouse Management for Page Dietmar-Hopp. As with the incoming qRFC queues. © 2006 SAP AG SAP EWM 7. which the system keeps in sysfail status. For ease of administration all three components are running on the same LPAR. are therefore deleted after the tests. Note that the mere transfer of qRFCs does not pose a performance challenge compared to the processing on EWM side. because no receiver is found.2. this transfer is not tested. The AIX operating system is configured according to SAP Note 973227.0 server consists of two ABAP instances and the DB2 system.2 System under Test .0 D-69190 Walldorf Document Date: August 2010 .

The EWM backend uses three file systems. one for the database logs and one for the data files (for the database filling level see section 4. The configuration of the RAID arrays is not dedicated to this particular test but is a general layout chosen for the storage as part of the SAP Center of Excellence data center. Here the DS8000 is configured into two extend pools. Memory configuration of the software components is very simple: the DB2 system runs with self-tuning memory manager (STMM=on) and the ABAP instances are configured for high memory usage (see SAP Note 789477). From the pool logical disks of 100 GB size are created which are grouped into volume groups. Retailers 16 of 113 Allee 16 Version: 1.0 D-69190 Walldorf Document Date: August 2010 .2.2. Each rank contains one RAID5 array with 8 146 GB disks exporting 1 GB storage extents to the related pool. one for software and test data.2. one for the DB2 log files and one for the DB2 data files (coedata2vg). Four volume groups are assigned to the LPAR (Figure 4). one for paging. High Performance Warehouse Management for Retailers The central instance (DVEBMGS00) runs the batch and user load. The storage configuration is detailed in section 4.5).30. © 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page Dietmar-Hopp. and the additional instance (D10) is dedicated to qRFC processing. The memory values in the figure show the high-water marks during the tests. The PLC emulator runs on a Windows 2003 VMWare along with the SAP PCO which runs as a Windows service.3 EWM Backend – Storage Configuration The storage configuration of the DS8000 is intended for high I/O throughput and flexibility in storage provisioning. The DS8000 is connected to the LPAR via two fiber channel adapters and two fabrics. Every extend pool has its own controller and consists of 8 ranks. one for software and test data (coedata1vg). Figure 3: EWM system hardware/software layout 4. Note that the software components only used a fraction of the available RAM.

4 EWM Backend – Important Periodic Batch Jobs As part of the operation of an EWM system a couple of periodic batch jobs have to be scheduled. Retailers 17 of 113 Allee 16 Version: 1.2. In the test landscape only those jobs were run which were applicable to the test scenarios: Job Function /LIME/BACKGROUND_DELETE_EXEC Inventory: Deletes DB entries for zero stock quantities and on request index entries without stock /LIME/COLLECTION_DELETE Warehouse Logistics Processing: Deletes the dispatch message log for goods movements between EWM and ERP /SCMB/ALEN_ALERT_DELETE Deletes alerts older than X days /SCWM/R_REORG_HU_WO_PRINT Warehouse Logistic Processing: Deletes EWM- specific PPF action data Table 5: List of periodic batch jobs These jobs were run before the start of a new test cycle.00: High Performance Warehouse Management for Page Dietmar-Hopp. The complete list is given in section 4. High Performance Warehouse Management for Retailers Figure 4: Storage configuration 4.6.0 D-69190 Walldorf Document Date: August 2010 .1 of the EWM Operations Guide. © 2006 SAP AG SAP EWM 7.

Note that the number of ODO items outweighs the number of GI items because only for a fraction of ODOs created in the system the full scenario has been processed until GI. The numbers of records in the relevant tables are given in the following table. The data was introduced by running the single test scenarios.533 /SCWM/TU_SR_ACT Transportation Unit Activities 2.5 Database Filling Level The simultaneous scenarios were running on a system with a filled database.240.385 /SCWM/WAVEHDR Wave Header 1.089.799 /SCDL/DB_DLVH_O Outbound Delivery Header 5.779 /SCWM/ORDIM_C Confirmed Warehouse Tasks 6.016 /SCDL/DB_PROCI_O Outbound Delivery Order Item 6.470 Table 6: Number of records in important EWM tables © 2006 SAP AG SAP EWM 7.672 /SCDL/DB_PROCH_I Inbound Delivery Header 3.850 /SCDL/DB_REQI Inbound Delivery Notification Item 109.279.764 /SCDL/DB_DLVI_O Outbound Delivery Item 1.946 /SCDL/DB_REQH Outbound Delivery Request Header 27.0 D-69190 Walldorf Document Date: August 2010 .614 /SCWM/HUREF Handling Unit Reference 65.706 /SCDL/DB_REQI Outbound Delivery Request Item 6.843.998 /SCWM/ORDIM_O Open/Inactive Warehouse Task 84. Retailers 18 of 113 Allee 16 Version: 1.786 (select distinct TANUM where TRART='5') /SCWM/ORDIM_C (TRART='5') Material Documents GR Items 92.699.246 /SCWM/WAVEITM Wave Positions 5. High Performance Warehouse Management for Retailers 4.784 (select distinct TANUM where TRART='6') /SCWM/ORDIM_C (TRART='6') Material Documents GI Items 108.692 /SCWM/ORDIM_C Material Documents GR Headers 4.231 /SCWM/DOOR_SRACT S & R Activities of a Door 2.00: High Performance Warehouse Management for Page Dietmar-Hopp. The database filling level roughly corresponds to two weeks of full productive usage of the system (according to the volume requirements). Table Stored Entity Number of Records /SCDL/DB_REQH Inbound Delivery Notification Header 3.395 /SCWM/HUHDR Handling Unit Header 512.577 /SCDL/DB_PROCH_O Outbound Delivery Order Header 25.904 /SCWM/ORDIM_C Material Documents GI Headers 1.218 /SCWM/QUAN Quant Attributes/Logical Stock 168.2.399 /SCWM/WHO Warehouse Orders 262.583 /SCDL/DB_PROCI_I Inbound Delivery Item 101.

0 D-69190 Walldorf Document Date: August 2010 .0 icm/max_timeout_wp = 2000 icm/min_timeout_mpi = 30000 icm/max_threads = 500 icm/max_conn = 500 mpi/total_size_mb = 200 We recommend setting the parameters icm/max_conn and icm/max_thread to the number of parallel RF users. In the test we used the following parameterization: icm/backend_wait_time_mult = 1.3 System Tuning and Important SAP Notes This section describes system tuning activities and related SAP Notes that were employed in order to achieve the performance results reported in this document. during the creation of ODOs with wave assignments we measured a high water mark of more than 196000 lock entries. A good single-thread performance (in terms of good server response times) is a prerequisite for a good single-user performance (in a single-user environment as well as in a multi-user environment). For example. 4. In general we recommend upgrading the EWM system to the highest available support package. It includes EWM system tuning as well as application tuning measures. Retailers 19 of 113 Allee 16 Version: 1. 4. 4.00: High Performance Warehouse Management for Page Dietmar-Hopp.3. The reason for its importance is that in the course of certain EWM processes many lock entries are written. The reason is that the EWM application is mainly CPU-bound.2 Parameterization of the ICM Another very important tuning measure is the configuration of the ICM (internet communication manager) as described in SAP Notes 1422086 and 1307291. This table is part of the Update Task System. For application tuning we refer to the next chapter.1 Parameterization of the Enqueue Table One of the most crucial system parameters for the EWM backend is the size of the enqueue table (parameter enque/table_size).4 DB2 Parameters The recommended standard parameterization of DB2 is described in SAP Note 1086130 and has to be applied in the context of a given system landscape. These problems have been solved with the application of SAP Note 1430621. The parameter was set to 409600. High Performance Warehouse Management for Retailers 4. In the EWM system under test we set the following parameters: STMM=on UTIL_HEAP_SZ=50000 KEEPFENCED=YES DFT_EXTENT_SZ=16 © 2006 SAP AG SAP EWM 7.3. Another general recommendation is the employment of fast server CPUs. For more details regarding the enqueue table see SAP Note 552289. For the sake of a better comparison of our performance results and the results achieved in a similar customer performance test we also include the single user response times in chapter 5.3 Configuration of the Update Task System In certain high-load situations we faced technical issues with update functions that could be traced back to the processing of the VBDATA table in DB2.3. 4. In addition SAP Note 1423066 should be consulted.3.

0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers MAX_QUERYDEGREE=1 Because of the activated self-tuning management. some parameters have been set to AUTOMATIC: DATABASE_MEMORY. © 2006 SAP AG SAP EWM 7. PCKCACHESZ. Retailers 20 of 113 Allee 16 Version: 1. SHEAPTHRES_SHR.00: High Performance Warehouse Management for Page Dietmar-Hopp. 4. Note also that the database statistics are automatically collected as described in SAP Note 860724 so that no RUNSTATS should be scheduled in the DBA planning calendar. MAXLOCKS.5 Missing Indexes Two sets of indexes needed activation: LIME collector indexes (SAP Note 1039436) and an additional index for the /SCWM/WHO table (SAP Note 1358890). LOCKLIST. SORTHEAP Further file system caching was deactivated according to SAP Note 1353421: DB2_LOGGER_NON_BUFFERED_IO=ON.3.

5. The number of doors. Flow-through partly uses the existing doors and staging areas used by the inbound and outbound processes. (Capacity checks on storage bins are not activated to achieve a smooth process flow. It can be found in your Solution Manager. The following chapters describe the necessary settings in verbal form. The master data setup supports the intended throughput described in the following sections.00: High Performance Warehouse Management for Page Dietmar-Hopp. is dictated by the intended parallelization of the unloading and loading process. © 2006 SAP AG SAP EWM 7. As a prerequisite the configuration guide “Integration of SAP ERP and SAP EWM” must be applied. there are 20 mobile users unloading the 40 deliveries.) Staging areas and doors for outbound complete this. Retailers 21 of 113 Allee 16 Version: 1. Cross-docking partly uses the existing doors and staging areas of the inbound and outbound processes.1 Master Data and Warehouse Layout After creating a warehouse number. High Performance Warehouse Management for Retailers 5 Setup of EWM Scenarios In this chapter the necessary customizing and application settings for the performance-relevant processes are described. for example. Additionally. In the Inbound scenario. In scale A of the Inbound scenario.0 D-69190 Walldorf Document Date: August 2010 . The same holds for the resources to be defined in the implementation: as mobile users have to log in to unique EWM resources. products and stores reflect the quantity structure of inbound deliveries and outbound deliveries respectively. these exactly mirror the parallelization of the related mobile-based processes. a work center for distribution is needed. scale A. More detailed settings can be found in the appendix in chapter 8. 1000 items – 1 product each – are delivered in 40 deliveries. The number of vendors.1 in tabular form. in contrast. for instance. doors and staging areas for the inbound process it is necessary to create a put-away target in high rack storage. On the other side this is the source of the internal replenishment for the picking area in the outbound process.

- (MFS) Resources (RF) Unloading 20 .in 20 .2 Inbound In order to model the inbound process with an unloading and put-away step a new process-oriented storage control is created.600 . 420 24 3 Staging . 4 . 42 40 23 Table 7: Master data quantities 5. .0 D-69190 Walldorf Document Date: August 2010 .600 3. door determination criteria are maintained in the product master based on where the products should be unloaded. The automatic high rack storage type should be determined as the final destination for inbound warehouse tasks.600 399. Therefore. To define the storage process a new warehouse process type for the inbound process is introduced. - bins High rack storage 4 I-points 4 P-points . 1 - Picking . an appropriate storage type search sequence is used. High Performance Warehouse Management for Retailers Master Data Inbound Outbound Flow-through Cross-docking Vendors 40 . 1 1 Replenishment . For the unloading process 20 inbound doors are used.out . - Putaway 4 . which are linked to their corresponding staging areas and staging bays. which will © 2006 SAP AG SAP EWM 7. - High rack storage 399.00: High Performance Warehouse Management for Page Dietmar-Hopp. which will be linked to the warehouse process type specified before.600 .000 24 24 Doors . 42 40 23 Work center . 1 - Fixed storage bins 3. During warehouse task creation for inbound deliveries this warehouse process type will be found based on a new warehouse process type control indicator. Additionally. 1 1 Doors .000 1. 1 1 Stores . 40 - Loading . Retailers 22 of 113 Allee 16 Version: 1. 420 400 230 Products 1. This storage process consists of these both steps.

During picking the warehouse clerk should not pick individual pieces but instead pick cartons. © 2006 SAP AG SAP EWM 7. Moreover. Unloading and put-away was adapted accordingly from similar processes in the Inbound scenario.g. printing and departure were adapted from outbound processes. Therefore wave template determination using condition technique is set up. the distribution of pre-packed pallets. 5. staging.00: High Performance Warehouse Management for Page Dietmar-Hopp. The loading step loads goods on transportation units. The latter is connected to a storage type search sequence to determine the automated high rack storage type. which is also assigned to the relevant products. The necessary Customizing was delivered by a Business Configuration Set. staging and loading. which are the operative unit of measure and consist of 6 pieces. The proper warehouse order creation rule is defined based on a new warehouse process type for picking. For fix bin usage individual fix bins are assigned to the products used with a given maximum quantity.) Wave template options are introduced on an hourly basis. In EWM. posting GI.5 Cross-Docking Here. picking.3 Outbound Automatic wave assignment of outbound delivery order items is used to organize the daily picking workload. (This ERP planned PGI date and time can be calculated with ERP SD Transport and Shipping Scheduling. which consists of the steps picking. For this purpose packaging specifications are set up and a proper determination is maintained. warehouse order creation should take care of pick HU creation.4 Flow-Through FT is in this instance a planned distribution of products from vendor pallets to store material handling trucks in the distribution center – so-called “Product-Driven Flow-Through”. Wave releasing. 5. In the outbound process warehouse order creation is used for two purposes: On the one hand. The objective is the grouping of the outbound deliveries according to their planned goods issue date & time. it should create warehouse orders with a maximum of 50 items all belonging to the same consolidation group (in this case goods recipient). In particular. On the other hand. optionally including the ERP retail route schedule. this storage type search sequence will be found. we consider a distribution of complete pallets from vendor to stores in the distribution center. High Performance Warehouse Management for Retailers be maintained in the product master of all affected products. Based on a new putaway control indicator. out-of- yard planned date can be derived from this planned PGI date which is retrieved from ERP. which picks goods from the fix bin storage type. A storage type search sequence for picking is determined based on the warehouse process type. loading on TUs. e. For this purpose a special warehouse order creation rule and warehouse process type are used. This warehouse process type is also linked to a process-oriented storage control process. and is further complemented by a new warehouse process Customizing and a Customizing of a special FT picking wave. To prevent the fix bins from becoming empty replenishment from the automated high rack is set up. no transportation units or yard management are used in the inbound process. the delivery items are assigned to a wave according to their planned departure from yard and route. This includes the Customizing for creating the pick HUs and the deconsolidation station. Based on this. the alternative unit of measure for cartons is maintained in every affected product. 2 pick HUs per warehouse order with a maximum of 25 items each should be created. which was already set in product master for the inbound process. In general. 5.0 D-69190 Walldorf Document Date: August 2010 . The warehouse process type is determined based on a special warehouse process type determination indicator. Retailers 23 of 113 Allee 16 Version: 1.

Additionally. delivery grouping must be set up to guarantee that for a given wave there is only one delivery for a given combination of route and goods recipient. the following application tuning measures were carried out. communication channels (including IP address and port). the system is enabled to decide that warehouse tasks have to be sent to the PLCs. For easier and faster selection the warehouse management monitor should be used to release waves. It must be ensured on the organizational level that TU creation and wave release for the same delivery items do not happen in parallel. This new status profile has to be used by all affected inbound delivery document types. the telegram structures and action function modules to be used are introduced. 5. loading on TUs. In addition. Picking. In all inbound processes the status “In Transit” for inbound deliveries is not used. Based on new queues. For this purpose a special application server group should be introduced. 5. Updating of start dates of the loading or unloading process in the outbound delivery order or the inbound delivery is prevented. posting GI. Checks for different routes and date/time of departure between outbound delivery order and transportation unit are deactivated. This is applicable for all queues used for loading and the queue used in cross-docking for picking. they should be prevented. Therefore.00: High Performance Warehouse Management for Page Dietmar-Hopp. For more information. storage bins and storage groups are made. © 2006 SAP AG SAP EWM 7. the logon group of the users releasing waves should be directed to the same application servers as for parallel wave release. High Performance Warehouse Management for Retailers The necessary Customizing was delivered by a Business Configuration Set. To operate MFS the necessary settings regarding activity area. see SAP Note 1423066. From a technical communication point of view the PLCs. the consolidation group should be determined based on route and goods recipient. Retailers 24 of 113 Allee 16 Version: 1. Based on these settings the layout-oriented storage control for the routing through the automatic warehouse is specified. Because cross-delivery pick HUs could lead to increased processing time. complemented by new warehouse process Customizing and some changes in the warehouse product master of the products involved. printing and departure were adapted from outbound processes.0 D-69190 Walldorf Document Date: August 2010 . the goods receipt mode is set to send only full goods receipt messages at the end of the putaway process. which are found according to the involved activity areas and bin access types. resources and communication points are created.6 Material Flow System For using the material flow system two storage types are introduced – one for the automatic high rack and one for the communication points.7 Application Tuning To improve performance during processing in the different processes mentioned. As the wave release is a critical step in the outbound process it is set up to run in parallel processes. On the ERP side. For certain processes the delivery update is set as asynchronous to ensure lower response times. This could be achieved by using a status profile with the deactivated status “In Transit”. the warehouse creation rule used should not allow more than one consolidation group per warehouse order. Unloading and putaway was adapted accordingly from similar processes in the Inbound scenario. To minimize data exchange between application servers. Communication with the ERP system due to partial goods receipts should be prevented. The update of waves with TU numbers during TU creation and OD creation is deactivated. Therefore.

Retailers 25 of 113 Allee 16 Version: 1. In the Transaction TU. the system is set up to print the delivery note only at its creation time. the flag ‘Not read delivery data’ in the transaction settings is set to avoid reading delivery data.00: High Performance Warehouse Management for Page Dietmar-Hopp. © 2006 SAP AG SAP EWM 7. High Performance Warehouse Management for Retailers Adaption of the route of outbound delivery orders into TU activities is disabled. The VAS relevance check for inbound and outbound deliveries is turned off. To prevent additional system load due to delivery note printing. In the flow-through process the packaging material type of the HUs used is set up to be deleted automatically as soon as the HUs are empty.0 D-69190 Walldorf Document Date: August 2010 .

Please note that in the latter case the frontend runtimes would be higher than the total response time of all other system components. the SAPGUI load was generated. The ‘think-time’ is defined as the time period between the screen presentation by the system and a dialog action initiated by the user (e. In the case of desktop transactions.15 sec can be achieved. In the case of desktop transactions.1 Methodology The user interaction with the EWM system was simulated in the test by using a technical tool.1 sec with modern PC hardware. spool requests become visible in transaction SP01). while for the other ‘multiple data input’ dialog picking steps there was no think-time used. This simulates the data input of multiple screen fields in sequence by means of a scanner-enabled mobile device. This tool generated the network load on the SAP system which would come from the user’s terminals or mobile devices in productive system landscapes. which means that a queue is created on the ERP side. The test procedure also used some simplified Application Interface procedures: Printing: printing was configured such that spool entries were created in the EWM system (i.g.e. but with longer system response times (especially for the major functional steps). these local frontend runtimes are < 0. the http protocol was used. HP LoadRunner 9. the so-called ‘think time’ is another important parameter. in the picking a think- time of 8 sec on average was chosen for the dialog step which presents the next bin to be picked from while the system is waiting for the pick bin scanning by the user (thus simulating a fast picking as in pick- by-light/voice). In the case of high-performing OS and hardware. pressing a button). ERP Outbound Interface: Outbound qRFCs were configured to make use of ‘Inbound Queue’. ERP Inbound Interface: incoming ERP deliveries were simulated by a report which created the qRFC entries in the EWM system as they would be created in the case of ERP delivery creation (e. For simplification of the test.1. In the simulation of the user interaction. the think time is not as important. This approximation holds true because the throughput and system load is dominated by the major functional steps which have response times >5 sec (which would be the typical user think time in desktop transactions). In the case of desktop transactions. there are fewer parallel users who do less frequent system interactions. Within the LoadRunner emulation this ‘think-time’ was always randomly calculated according to a uniform distribution with a well-defined average and max/min values. frontend runtimes of < 0. For example. these frontend runtimes typically comprise rendering runtimes for transferring the network protocol data into UI screen elements. Spool requests were deleted on a regular basis between the test runs. The average think-time was chosen per business step in order to reflect the real circumstances of high throughput warehouses. No real output devices were configured and no real output was performed for these spool requests. This means that these response times include network latency time and all backend system runtimes like SAP EWM application runtimes and SAP ITS for mobile. via SAP ERP transaction VL10 or VL10B) and configuring the qRFC connection ERP->EWM to make use of ‘Inbound Queue’. The random distribution is needed in order to prevent possible artificial pile-up effects during the recurring cycles of the automated test procedure. For SAP EWM desktop transactions. the frontend runtime depends strongly on the operating system and hardware used.00: High Performance Warehouse Management for Page Dietmar-Hopp. while in other worse cases about 1 sec frontend runtime is possible. a think time of 0 was used in desktop transactions.0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers 6 Performance Results 6. The qRFC infrastructure always creates an © 2006 SAP AG SAP EWM 7. For SAP EWM mobile device transactions (RF). Among others. Retailers 26 of 113 Allee 16 Version: 1. In the case of mobile devices. but exclude any runtime which would be needed for real presentation frontend software (like SAPGUI Front End). All response times which are given in this document are based in the LoadRunner measurements on protocol level. compared to the RF transactions which have relatively short system runtimes.g. Thus we highly recommend improving these frontend runtimes of mobile devices by means of a hardware evaluation phase for the mobile devices within an EWM implementation project.

Many of them have a response time much shorter than 1 second. and some are optional (e. technically implemented by means of LoadRunner test scripts. Inbound Scale B: Few supplier shipments with a large number of products each: A time window of max 6 warehouse working hours for the Inbound scenario is considered. The extrapolated throughput is calculated by number of processed items (or HUs) in the test divided by the test’s runtime. 5 inbound deliveries with 200 products each are considered. Example: Inbound scenario = IN Each scenario is split into several independent process phases. The measurements and the below presented results follow a general scheme: Each scenario has an abbreviation. © 2006 SAP AG SAP EWM 7. High Performance Warehouse Management for Retailers outbound queue (visible in transaction SMQ1) before starting the RFC which creates the (optional) inbound queue in the ERP system. Besides the throughput numbers of a process phase (i. IN2 represents the work which is done by the office clerk prior to unloading execution. The result overview tables of the following sections contain only the response times of the major functional steps. and the steps with very fast response time were not treated as important measurement results (instead they were combined into a single technical measurement via so-called ‘defined transactions’ within the HP LoadRunner). Typically all these steps are performed by the same group of parallel users. resulting in 50 pallets per delivery. so the outbound queues on the EWM side failed to process their RFC to the ERP system. the user optionally inspects data by toggling between tab strips or scrolling within tables). The raw data includes the information about the test run duration. The related screenshots of the steps are presented in the scenario specification in the appendix. In the test procedure there was no ERP system in place. Retailers 27 of 113 Allee 16 Version: 1. IN1).e. in order to span an experimental test space with edges of extreme occurrences of the characteristics. For example. Every product is delivered being packed onto 2 pallets. Each script consists of a well-defined business process step or multiple steps which belong to the same process phase. In that sense. resulting in 400 packages per delivery. The test procedure focuses on the resource-intensive dialog steps only. but still within the borders of expected real-life business processes. the system resource consumption of the EWM backend was also measured and is listed for system sizing estimation purposes. called dialog steps (one request of the UI to the server and the server’s reply). The comparison of both could provide insights into the concurrency management capabilities of the technical EWM implementation. The response time results are provided for multi-user test runs (several concurrent users) and single-user test runs. The following value sets for Performance Relevant Characteristics were used for the several scenarios: Inbound Scale A: Many supplier shipments with a small number of products each: A time window of max 6 warehouse working hours for the Inbound scenario is considered. the optional interactions were omitted. These failed outbound queues were deleted on a regular basis between the test runs. ‘Scale B’ is the more challenging scale in terms of throughput requirements and response time challenges due to larger objects or documents. like goods receipt posting and unloading warehouse task creation. 5 unload workers and 4 putaway workers are working simultaneously.00: High Performance Warehouse Management for Page Dietmar-Hopp. 40 inbound deliveries with 25 products each are considered. Ideal concurrency management retains system data consistency while having a zero impact on response times. Every product is delivered packed into 2 packages. This is why the multi-user results of ‘Scale B’ can be seen as ‘worst case scenario’ results.0 D-69190 Walldorf Document Date: August 2010 .g. Throughput results are given in terms of measured and extrapolated throughput. which were handled by LoadRunner as ‘defined transactions’ whose average response time is measured individually. 20 unload workers and 4 putaway workers are working simultaneously. Measurements were conducted for the Inbound and Outbound scenarios with two different value sets of performance-relevant characteristics. called ‘Scale A’ and ‘Scale B’. the response times as measured in the multi-user test are always at the upper limit of the response times obtained with a smaller number of concurrent users. In the test procedure/LoadRunner script. often within a single transaction code. Each process phase/test script consists of multiple user actions.

As outlined in section 4. The load consists of 40 material handling trucks.000 products. vendors and stores.g. packed in boxes of 6 pieces.400 pieces is considered. the planned delivery date. 4 inbound delivery documents are to be created (resulting in 4 qRFC queues) with 25 items and 50 HUs per delivery. Each product is packed into one or several small boxes. with each having 24 different products in 3 palettes. Each Inbound Delivery consists of 3 palettes which each contain 8 products. The store deliveries are done by 40 trucks. each containing 25 different products. The goods are delivered by 230 deliveries to 230 stores. The transport to the stores is done by 23 trucks. each containing 25 different products. Merchandise Flow-Through: A single supplier shipment with few products is used for 400 separate store deliveries. Outbound Scale B: Supply to large sized stores: 420 outbound trucks per day within a time window of about 10 warehouse working hours are considered. Thus. and 23 loaders are working simultaneously. 3 boxes of 6 pieces of a product. According to the parameters. 6. Further parameters control the naming of related materials. each wave having a size of 30. Each inbound delivery is packed into a qRFC queue on the EWM system. Each product is on a single inbound pallet. which are related to 400 store deliveries. 1 putaway worker. A time window of max 4 warehouse working hours for the Cross-Docking scenario is considered. Each item will contain 2520 pieces of one dedicated material. 3 pickers. 420 pickers and 42 loaders are working simultaneously.000 items and being dedicated for 30 truck loads. Each store is being delivered 200 products in 8 material handling trucks.2. Retailers 28 of 113 Allee 16 Version: 1.000 items and being dedicated for 42 truck loads. the number of delivery items per document. 24 pickers.100 stores is done per day.1 Processing of Incoming Inbound Deliveries The first step in the Inbound scenario is the reception of inbound deliveries sent by the connected ERP system (process IN1). The load consists of 40 material handling trucks. Each product is packed into 2 HUs. Each truck has a load for a single large sized store of 1. and thus containing 30 palettes. The main parameters of this program are: the number of documents (deliveries) to be created. Each truck contains 10 material handling trucks with each containing the boxes of 24 different products. so the processing of these qRFC queues is tested by calling a program that directly creates them in the EWM system.000 delivery product items in total. e.2 Inbound Scenario 6. which automatically determines the number of HUs to be created. 40 workers for staging. 300 pickers and 30 loaders are working simultaneously. each having the load of 10 deliveries for 10 stores. Each truck has a load for 5 medium sized stores. each wave having a size of 42. These boxes are picked by means of 14 picking waves throughout the day. The screenshot in Figure 5 provides an example. The load of each truck is 5 deliveries with 1. The 24 inbound pallets are distributed to 400 outbound material handling trucks. a distribution to 2. which were received by the several Inbound Deliveries. These boxes are picked by means of 10 picking waves throughout the day.g.00: High Performance Warehouse Management for Page Dietmar-Hopp. 1 unload worker.2. 3 boxes of 6 pieces of a product. Merchandise Cross-Docking: Many supplier shipments are cross-docked to many separate store deliveries. On the inbound pallet there are 400 boxes. 1 worker for providing the empty pick material handling trucks.0 D-69190 Walldorf Document Date: August 2010 . 1 unload worker. A time window of max 4 warehouse working hours for the Flow-Through scenario is considered. High Performance Warehouse Management for Retailers Outbound Scale A: Supply to a high number of medium sized stores: 420 outbound trucks per day within a time window of about 16 warehouse working hours are considered. © 2006 SAP AG SAP EWM 7. 230 Inbound Deliveries with each having 24 products are considered. 1 inbound delivery with 24 products with each having a quantity of 2. . e.1 the ERP system is not part of the system under test. and 40 loaders are working simultaneously. item quantity and quantity of the HUs. Each product is packed into one or several small boxes. each containing the deliveries for 10 stores.

High Performance Warehouse Management for Retailers Figure 5: Creation of inbound deliveries in the EWM system The first item contains material A-P0001. In scale A.2 Dialog Performance This section reports the inbound process dialog performance in terms of average response time measured with HP LoadRunner.00: High Performance Warehouse Management for Page Dietmar-Hopp. In scale B.0 D-69190 Walldorf Document Date: August 2010 . As shown in Figure 6 the Inbound scenario consists of three processes: creation of unloading warehouse tasks and posting of goods receipt (IN2). 5 parallel batch jobs created 5 deliveries with 200 items each. Retailers 29 of 113 Allee 16 Version: 1. IN2 is processed by one © 2006 SAP AG SAP EWM 7. Selected dialog steps are handled by LoadRunner as defined transactions whose average response time is measured individually (nevertheless we refer to dialog steps).2. The first delivery document is assigned to vendor VR0001. 6. The processing of the qRFC queues ended after 32 seconds (32 ms/item). The processing took 45 seconds (45 ms/item). the last item material A-P0025. Note that the performance is independent of item quantities. unloading (IN3) and put-away (IN4). The report includes single-user as well as multi-user response times. 10 parallel batch jobs created 40 deliveries with 25 items each. hence these have been treated as scale-invariant. Testing was done on a 5-core LPAR. the last to VR0004.

however. IN3 is processed by 20 users in scale A and 5 users in scale B. say. The leftmost column shows the processes along with the technical transaction code and the steps. The response times of the measured steps are given in Table 8. (/SCWM/RFUI is the general transaction code for all RF transactions. In this document. as these steps are usually in the range of below 50ms. starts transaction /SCWM/PRDI and searches for the delivery document by entering the related ERP number and clicking the Execute button (step IN2_Search_Items). The related screenshots of the steps are presented in the scenario specification in the appendix. IN4 is processed by 4 users. © 2006 SAP AG SAP EWM 7. High Performance Warehouse Management for Retailers user only (hence there are no multi user results). The middle column lists the single-user response times differentiated by scale. For further details regarding the runtime and processed quantities of the various tests. refer to the next section. In the IN2 process the user logs into SAPGUI. Retailers 30 of 113 Allee 16 Version: 1. Figure 6: Inbound processes Each process consists of a series of dialog steps (one request of the UI to the server and the server’s reply). the document/item distinction does not play any role. navigation steps in the ITS mobile menu. hence indicates that the related process is carried out on mobile devices).0 D-69190 Walldorf Document Date: August 2010 . This means that we do not report the performance of. Afterwards he saves (step IN2_Save) and presses the Goods Receipt button (step IN2_Goods_Receipt). Then he switches to the unload view (step IN2_Menu_Unload) and presses the Unload WTs button (step IN2_Unload_WTs).00: High Performance Warehouse Management for Page Dietmar-Hopp. we focus on the resource-intensive dialog steps only. Note that IN4 is scale-invariant because there are only HUs to be put away i.e.

As with IN3. it is rather a function of the system response and user think times. i.08 0.5 /SCWM/RFUI Scale-invariant Scale-invariant HU_RSC_Enter_2 0. respectively) in the test divided by the test’s runtime. the I-point of the high rack storage (step IN4_IP_PUT_2). He confirms the HU to be put away (step IN4_HU_RSC_Enter_2) and then the destination bin.00: High Performance Warehouse Management for Page Dietmar-Hopp. which does not affect the response time of the user but creates additional load in the system. The throughput is calculated by number of processed items (or HUs. Retailers 31 of 113 Allee 16 Version: 1. but then navigates to Putaway by HU.2.5 0. It is important to note that the measured throughput is not the maximum that can be achieved.3 IN4 IP_PUT_2 0. Usually the first step is very fast (< 30ms) and will not be included here. for the process IN4 the user logs into the RFUI. The latter are derived by the KPIs of the test. He then confirms the ASN number (step IN3_ASN_Enter_2)1. Single-User Test Multi-User Test Average Response Time Average Response Time (sec) (sec) Scale A Scale B Scale A Scale B Search_Items 1.3 TCODE: Unload_WTs 12.4 0.1 3.8 No multi-user test IN2 Menu_Unload 1.0 Goods_Receipt 3.7 IN3 HU_RSC_Enter_2 0.05 0.2 0.2 TCODE: /SCWM/RFUI Table 8: Inbound scenario-related response times of the most complex and resource-intensive dialog steps 6. After confirmation there is an automatic putaway from the I- point to the final bin via MFS and PCO.7 0.05 0. High Performance Warehouse Management for Retailers In the IN3 process the user logs into the RFUI via ITS Mobile and navigates to Unloading by ASN.5 4.05 TCODE: DestBin_Enter_2 0.0 5.e. © 2006 SAP AG SAP EWM 7.3 0.5 197.0 ASN_Enter_2 0.6 0.3 Dialog Throughput and Resource Consumption The following table 2 presents the measured and extrapolated throughput and system resource consumption of the EWM backend.3 0.7 0.0 D-69190 Walldorf Document Date: August 2010 . He then confirms the related HU numbers (step IN3_HU_Enter_2) and the destination bins (step IN3_DestBin_Enter_2).8 30. here simulated as entering the ASN number and pressing enter (step IN3_ASN_Enter_1) second the confirmation of the number scanned in.5 /SCWM/PRDI Save 1. 1 As with many RF screens there are two steps: the first is the scan-in of the bar-code.

3 DB2 10% (items/min) Extrapolated 4.463 RAM 7% throughput (items/hour) Scale invariant Number of users 4 Cores in LPAR 5 IN4 Runtime (min) 47 RAM in LPAR 40 GB TCODE: Processed HUs 2.000 RAM 20%2 throughput (items/hour) Scale A Scale B Scale B Number of users 20 5 Cores in LPAR 423 IN3 Runtime (min) 10 41 RAM in LPAR 252 GB TCODE: Processed items 1. the user requires up to 90MB extended memory. 3 This resource consumption of this process was measured when the LPAR had the large configuration.6 DB2 13% (HUs/min) Extrapolated 2. This is required to interpret the CPU and RAM utilization.000 CPU utilization 30% /SCWM/RFUI Think time (sec) 5 ABAP 87% Actual throughput 42. we also differentiate how much CPU was consumed by the EWM kernel (“ABAP”) and how much by the database (“DB2”). For the former.4 DB2 14% (items/min) Extrapolated 6.5 30 RAM in LPAR 40 GB TCODE: Processed items 1. Retailers 32 of 113 Allee 16 Version: 1.1 33.00: High Performance Warehouse Management for Page Dietmar-Hopp. the table includes the number of cores and the amount of RAM assigned to the LPAR during the test.553 RAM 22% throughput (items/hour) Table 9: Throughput and resource consumption in the Inbound scenario 2 IN2 is a RAM-intensive process. High Performance Warehouse Management for Retailers Because the CPU and RAM configuration of the LPAR varies between tests of the isolated scenarios. © 2006 SAP AG SAP EWM 7. Throughput Resource Consumption Scale A Scale B Scale B Number of users 1 1 Cores in LPAR 5 IN2 Runtime (min) 13.000 1.0 D-69190 Walldorf Document Date: August 2010 .000 CPU utilization 5% /SCWM/RFUI Think time (sec) 5 5 ABAP 86% Actual throughput 100 24.000 1. we provide the utilization of RAM by system and processes as well as the total utilization.444 2.000 CPU utilization 20% /SCWM/PRDI Think time (sec) 0 0 ABAP 90% Actual throughput 74. including file system cache (the number in brackets). For the latter.000 1.

In the test 100 deliveries (scale A type) have been unloaded in 40 minutes starting with 5 users and adding 5 users every 10 minutes. it is worthwhile to investigate the scalability of this process (IN3). Retailers 33 of 113 Allee 16 Version: 1.4 Scalability Test for Unloading Process Because the number of users doing the unloading from trucks can considerably vary. The response times are plotted in Figure 7 and the CPU consumption in Figure 8. The CPU utilization increases from 25% to 85%.0 D-69190 Walldorf Document Date: August 2010 . Figure 7: Response times in IN3 scalability test © 2006 SAP AG SAP EWM 7. Only a slight increase in response time over number of users can be observed. High Performance Warehouse Management for Retailers 6.00: High Performance Warehouse Management for Page Dietmar-Hopp.2. Each user processed 2 deliveries in 10 minutes. The LPAR is configured for 5 dedicated cores.

3 Outbound Scenario 6. Retailers 34 of 113 Allee 16 Version: 1.0 D-69190 Walldorf Document Date: August 2010 . in which 420 ODOs (420 qRFC queues) with 1000 items each will be created. provided that automatic wave creation is configured. the processing of outbound delivery orders (ODOs) received from the ERP system (process OB1) is simulated by an ABAP program which creates corresponding qRFC queues (see section Processing of Incoming Inbound Deliveries 6. the next 42 will have an out-of-yard of 10:10 am etc.3. © 2006 SAP AG SAP EWM 7. Here. High Performance Warehouse Management for Retailers Figure 8: CPU utilization in IN3 scalability test 6. The date is derived from the date of execution of the program plus 1 day (out of yard day offset). The out-of-yard time. The program uses the material prefix and the store prefix to create documents with different materials distributed over n stores.00: High Performance Warehouse Management for Page Dietmar-Hopp. the second set of 42 ODOs to the second wave and so on.1 Processing of Incoming Outbound Delivery Orders and Wave Creation Similarly to the Inbound scenario.2. only one ODO will be assigned to one route (hence one transport unit (TU)). Figure 9 shows a screenshot of the program parameterized for scale B. In the example the first 42 ODOs will have an out-of-yard time of 9:10 am. the increment and the ODOs-per-wave parameters control the creation of waves.1). In addition the number of documents per route can be specified. In the EWM system the wave templates are created in such a way that the first 42 ODOs are assigned to the first wave.

0 D-69190 Walldorf Document Date: August 2010 .000 RAM in LPAR 252 GB Create ODOs Actual throughput 21.471 RAM 7% throughput (ODOs/hour) Table 10: Throughput and resource consumption in outbound scenario © 2006 SAP AG SAP EWM 7. High Performance Warehouse Management for Retailers Figure 9: Creation of ODOs in the EWM system We tested the creation of ODOs with and without simultaneous creation of waves. Throughput Resource Consumption Scale A Scale B Scale A Runtime (min) 20 not tested Cores in LPAR 42 OB1 Created ODO items 420. Retailers 35 of 113 Allee 16 Version: 1.615 296. The results are presented in the following table.077 4.000 RAM in LPAR 252 GB Create Number of waves 14 10 ABAP 91% ODOs and waves Actual throughput 8.0000 DB2 4% throughput (ODOs/hour) RAM 6% Scale B Runtime (min) 52 85 Cores in LPAR 42 OB1 Created ODO items 420.941 DB2 9% (ODOs/min) Extrapolated 484.000 ABAP 96% without (ODOs/min) waves Extrapolated 126.000 420.00: High Performance Warehouse Management for Page Dietmar-Hopp.

For general remarks please see also section 6.2 Dialog Performance This section summarizes the dialog performance of the important dialog steps within the Outbound scenario. The process OB2A creates replenishment warehouse tasks (WTs). Figure 10: CPU utilization in OB1 with wave creation (scale B) Figure 11: Disk I/O in OB1 with wave creation (scale B) 6. High Performance Warehouse Management for Retailers The ODO creation tests were conducted on an LPAR with 42 cores. Processing of an outbound wave starts with the release of the wave (OB3A). followed by the picking © 2006 SAP AG SAP EWM 7. The next two figures plot the CPU utilization and the disk I/O utilization. In the I/O plot the left Y-axis has a scale of 1000 kb/sec (for reads/writes) and the right Y-axis displays I/Os/sec. respectively. which are then processed by OB2B.3. Generally there are two groups of processes.0 D-69190 Walldorf Document Date: August 2010 . during the scale B ODO and wave creation. those that can be seen as pre-steps to the processing of a wave (OB2A-C) and those that make up the outbound wave processing (OB3A-F).2. Figure 12 shows the related processes. Retailers 36 of 113 Allee 16 Version: 1.00: High Performance Warehouse Management for Page Dietmar-Hopp.2. In the process OB2C the transport units (TUs) are created and the ODOs assigned.

In the OB3E process the outbound deliveries (ODs) are created for the current wave and in OB3F the TUs are undocked and leave the yard. The generated warehouse tasks are processed in process OB2B in which the user first confirms the pick of the source HU (OB2B_Conf_Src_HU) and then the drop to the destination bin (OB2B_Conf_Dest_Bin).6) the release of the next wave is run in parallel to the picking of the current wave. There will be one warehouse task per product.00: High Performance Warehouse Management for Page Dietmar-Hopp. OB2B was also conducted in single-user mode only. Loading is identified by process OB3D. Figure 12: Outbound processes In the replenishment transaction (OB2A) the user creates warehouse tasks for the replenishment of goods required for a series of waves. which accounts for a more realistic scenario. Note that in the simultaneous scenario (section 6. enters parameters of the TU and executes (OB2C_Press_Create). Afterwards he assigns the planned door to the TU (OB2C_Save_3). © 2006 SAP AG SAP EWM 7. this means 1000 in total. He then saves (OB2C_Save_1). In the first SAPGUI screen the user confirms the selection (OB2A_Execute_1) and in the second screen he confirms the planned replenishment items by selecting them and pressing the Execute button (OB2A_Execute_2). Retailers 37 of 113 Allee 16 Version: 1. In the multi-user test OB2C is run with 3 users.0 D-69190 Walldorf Document Date: August 2010 . enters transaction /SCWM/TU presses the Create button. The TUs belonging to the current wave are checked in and docked to door in process OB3C. The steps of OB2C (creation of TUs) are as follows: the user logs in with SAPGUI. The dialog performance is shown in the next table. OB2A was tested in single-user mode only because the replenishment planning is done once per wave by a single desktop user. High Performance Warehouse Management for Retailers processes (OB3B). assigns the related ODOs (OB2C_Assign_ODOs_TU) and saves again (OB2C_Save_2). because the single-user measurement shows response times which are by far shorter than the defined KPI.

0 Assign_TU_Door 19. In the multi-user test we tested with 300 users (scale A) and 420 users (scale B).3 2.8 59. After the release wave dialog returns with a success message.2 9. The reason for this is that in the multi-user test we deactivated the update of waves with TUs (see also chapter 4). High Performance Warehouse Management for Retailers Single-User Test Multi-User Test Average Response Average Response Time (sec) Time (sec) Execute_1 480 (8 min) No multi-user test OB2A Execute_2 120 (2 min) TCODE: /SCWM/REPL Press_F4 0. The degree of internal technical parallel processing in the EWM system. One iteration in the picking process (OB3B) consists of three steps: after the user logs in via ITS Mobile and navigates to system-guided selection where he is presented a list of open WTs. For the processing of one wave each user does two iterations. Wave release (OB3A) is done via the EWM monitor (/SCWM/MON). can be controlled by the EWM Customizing.5 0. This is repeated one more time. because there are 2 pick HUs per user. The former is much higher than the latter.4 measured 0.7 0. As there is only one user releasing the outbound wave there is no multi-user test. however.2 Table 11: Outbound scenario-related response times of the most complex and resource-intensive dialog steps (OB2A-C) With OB2C_Assign_ODOs_TU.2 /SCWM/RFUI Scale A Scale B Scale A Scale B Press_Create 0.3 22.1 OB2B Conf_Src_HU 0. The results listed in the next table have been achieved with a 10-fold parallelization. Then he confirms picking of one item (OB3B_Src_HU_2). This step is called staging.6 Save_3 2.4 14.4 TCODE: Assign_ODOs_TU 87. he presses F4 (OB3B_Src_HU_1).2 2.00: High Performance Warehouse Management for Page Dietmar-Hopp. further processing is done in UPDATE tasks. © 2006 SAP AG SAP EWM 7. He then transports the 2 HUs to the staging area and drops them into the destination bin. Because the first pickers can already start working on the first WTs after the success message is displayed. there is an apparent mismatch of the single-user response time compared to the multi-user response time. which is done 25 times.6 Not 0.6 OB2C Save_1 0. respectively.9 67. Retailers 38 of 113 Allee 16 Version: 1. it is worth reporting the response times with and without update processing. which needs to be confirmed (OB3B_DestBin_Confirm).3 /SCWM/TU Save_2 9.0 D-69190 Walldorf Document Date: August 2010 .0 19.2 TCODE: Conf_Dest_Bin 0.

3 1. UPD (10min) (15min) /SCWM/MON Src_HU_1 0. © 2006 SAP AG SAP EWM 7.6 8. The tables are followed by Figure 13 which shows the response times of the important picking and staging process.0 D-69190 Walldorf Document Date: August 2010 .3 /SCWM/RFUI TU_Search -4 Not 5. In OB3E the user presses the Check button (OB3E_Check).3 0.8 TCODE: DestBin_Confirm 0.2 0.00: High Performance Warehouse Management for Page Dietmar-Hopp. In the OB3D process (loading) each user processes one TU. In OB3F the user presses the Goods Issue button (OB3F_GoodsIssue). Finally he saves the transaction (OB3C_Save).6 0.4 TCODE: Door_Arrival_Door 20. He then confirms each loaded HU (OB3D_HU_2) and the corresponding destination bin (OB3D_Conf_Dest_Bin_2). hence there was no search step.6 measured 6.9 11.06 0.3 0.200 No multi-user test OB3A incl. In both OB3E and OB3F the user logs in via SAPGUI and searches for the given TU (OB3E/F_Search_TU).3 4 During the single-user test OB3C and OB2C were in one test script.8 OB3D HU_2 (enter HU) 0. The following tables summarize the dialog performance results.3 0. UPD (14min) (20min) TCODE: Release_Wave 600 840 excl. After all HUs are loaded he confirms that the loading is finished (OB3D_Conf_TU_Loaded). After having logged into the system via ITS Mobile the user navigates to Loading by Transport Unit and enters the given TU (OB3D_TU_3).3 0.4 TU_3 (enter TU) 1.1 OB3C CheckPoint_Arrival_Save 3. Retailers 39 of 113 Allee 16 Version: 1. He then chooses Departure from Door (OB3F_DepartureFromDoor) and Departure and Save (OB3F_DepartureAndSave) from the menu.2 6. enters the transaction SCWM/TU and searches for a given TU (OB3C_TU_Search).7 Not 2. The graph covers a run with 420 users in scale B.3 0.2 OB3B Src_HU_2 0.4 35.3 0.06 TCODE: 5 Conf_Dest_Bin_2 0. He then selects Checkpoint Arrival (OB3C_CheckPoint_Arrival_Save) and Door Arrival (OB3C_Door_Arrival_Door) from the menu. Single-User Test Multi-User Test Average Response Average Response Time (sec) Time (sec) Scale A Scale B Scale A Scale B Release_Wave 840 1.6 0.6 /SCWM/TU Save 2. generates the ODs (OB3E_Generate_OD) and saves (OB3E_Save). High Performance Warehouse Management for Retailers In the OB3C process the user logs in to the system via SAPGUI.06 measured 0.7 0.3 47.5 0.5 11.

1 2. High Performance Warehouse Management for Retailers /SCWM/RFUI Conf_TU_Loaded 0.8 2.8 /SCWM/TU Save_2 9. Retailers 40 of 113 Allee 16 Version: 1.2 8.9 86.6 /SCWM/TU Save_1 22. © 2006 SAP AG SAP EWM 7.1 27.3 Table 13: Outbound scenario-related response times of the most complex and resource-intensive dialog steps (OB3E-F) 5 Here the single-user test result is worse than in the multi-user test.00: High Performance Warehouse Management for Page Dietmar-Hopp.9 94.0 27.0 Table 12: Outbound scenario-related response times of the most complex and resource-intensive dialog steps (OB3A-D) Single-User Test Multi-User Test Average Response Average Response Time (sec) Time (sec) Scale A Scale B Scale A Scale B TU_Search Not measured 7.9 OB3E Check 37.0 D-69190 Walldorf Document Date: August 2010 .2 12.0 Save_3 11.4 OB3F GoodsIssue 152.2 TU_Search Not measured 9.5 TCODE: DepartureFromDoor 17.8 47.2 169.0 TCODE: Generate_OD 65.7 15.0 16.2 DepartureAndSave 62. because of code changes between the two test series.

High Performance Warehouse Management
for Retailers

Figure 13: Response times of the major dialog steps in outbound picking and
staging

© 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page
Dietmar-Hopp- Retailers 41 of 113
Allee 16 Version: 1.0
D-69190 Walldorf Document Date: August 2010

High Performance Warehouse Management
for Retailers

6.3.3 Dialog Throughput and Resource Consumption
The throughput requirements and the related resource consumption of the Outbound scenario determine
the sizing of the EWM backend to a large extent. This is because the requirements in terms of delivery
items to be processed per time unit is much higher than in the other scenarios (e.g. 42,000 items
processed in less than 1 hour) which leads to very resource-intensive processes, such as ODO and wave
creation (420,000 items in a certain batch window, usually less than 2 hours), picking and staging with a
relatively high number of users, or goods issue and OD creation. This section therefore treats the aspects
of throughput and resource consumption more thoroughly than is done for the other scenarios.

We start with the OB2x processes that have to be completed before the processing of an outbound wave.
The replenishment processes can be disregarded because throughput and resource consumption are
functions of the number of products to be replenished, rather than the number of delivery items. The
replenishment WTs for 1000 products can be created by one user in less than 15 minutes (running in one
dialog work process at a time), no matter how many pieces of the products are to be handled. The same
holds for the actual replenishment, which is very lean compared to the other outbound processes.
The creation of TUs in the system, however, requires more power: in the scale B test, 3 users continually
create 42 TUs in 28 minutes, keeping 3 cores completely busy. After the end of the online transactions
there is a further backlog of qRFC queues to be processed which takes another 37 minutes. This backlog
has been removed later on by application tuning (no update of waves with TU numbers). The next table
summarizes the measurements for both scales.

Throughput Resource Consumption
Scale A Scale B Scale B
Number of users 3 3 Cores in LPAR 30
OB2C Runtime (min) 16 28 RAM in LPAR 217GB
TCODE:
13 qRFC 37 qRFC
/SCWM/TU backlog backlog
Processed TUs 30 42 CPU utilization 10%
Think time (sec) 0 0 ABAP 98%
Actual throughput 1.9 1.5 DB2 2%
(TUs/min)
Extrapolated 112.5 90 RAM 18%
throughput
(TUs/hour)
Table 14: Throughput and resource consumption in the Outbound scenario (OB2C)

The throughputs of the first three outbound wave-related processes together with the resource
consumption are presented in the next table.

© 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page
Dietmar-Hopp- Retailers 42 of 113
Allee 16 Version: 1.0
D-69190 Walldorf Document Date: August 2010

High Performance Warehouse Management
for Retailers

Throughput Resource Consumption
Scale A Scale B Scale B
Number of users 1 1 Cores in LPAR 30
OB3A (10-fold) (10-fold)
TCODE: Runtime (min) 10 15 RAM in 217GB
(excl. (excl. LPAR
/SCWM/MON
UPD) UPD)
Processed items 30,000 42,000 CPU utilization Up to 34%
(see
Figure 14)
Think time (sec) - - ABAP 96%
Actual throughput 3,000 2,800 DB2 4%
(items/min)
Extrapolated 180,000 168,000 RAM 20%
throughput
(items/hour)
Scale A Scale B Scale B
Number of users 300 420 Cores in LPAR 30
OB3B Runtime (min) 17 17 RAM in 217GB
TCODE: LPAR
/SCWM/RFUI Processed items 30,000 42,000 CPU utilization 85%
Think time (sec) 8 8 ABAP 94%
Actual throughput 1,764.7 2,470.6 DB2 6%
(items/min)
Extrapolated 105,882 148,235 RAM 21%
throughput
(items/hour)
Scale A Scale B Scale B
Number of users 3 3 Cores in LPAR 30
OB3C Runtime (min) 9 21 RAM in 217GB
TCODE: LPAR
/SCWM/TU Processed items 30 42 CPU utilization 10%
Think time (sec) 0 0 ABAP 92%
Actual throughput 3.3 2 DB2 8%
(items/min)
Extrapolated 200 120 RAM 18%
throughput
(items/hour)
Table 15: Throughput and resource consumption in the Outbound scenario (OB3A-
C)

© 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page
Dietmar-Hopp- Retailers 43 of 113
Allee 16 Version: 1.0
D-69190 Walldorf Document Date: August 2010

It shows that the whole process is divided into four segments. Note that the think time of 8 seconds between two picks is relatively short and ramp up is very fast in the test. Retailers 44 of 113 Allee 16 Version: 1. which amounts roughly to an equivalent of 26 cores being fully utilized6. which runs for another 5 minutes. After ca 5 minutes there is one work process running for another 5 minutes followed by a second parallel run. We return to the picking and staging process in section 6. Figure 14 shows the CPU utilization during wave release (scale B). The remaining warehouse tasks are generated in the course of update processing.000 items/h. In order to further increase the throughput we tested the process in scale A with half the think time (4 sec). 6 Note that if simultaneous multi-threading (SMT) is used there is no linear correlation between utilization and the percentage of the maximal possible throughput. The throughput of OB3C (check-in TU and dock) in scale B is around 2 TUs/min. The degree of parallelization can be controlled in Customizing. Apart from ramp-up and down the utilization is around 85%. so that the whole picking of 42000 items only takes 17 minutes. consuming 1/3 of the 30 available cores. This resulted in an extrapolated throughput of 180. otherwise the degree of parallelization is determined by the number of free work processes. It is important to note.4 which addresses its scalability. In the test 3 users are continuously performing this process so that 3 cores are fully utilized during this time. Figure 14: CPU utilization during scale B outbound wave release The next figure shows the continuous utilization of CPU during the picking process in scale B. yielding an extrapolated throughput of 148. however.00: High Performance Warehouse Management for Page Dietmar-Hopp. that at the time of the release there must be a sufficient number of dialog work processes available in the instance in which the user starts the transaction.3. © 2006 SAP AG SAP EWM 7. which means that 10 cores are fully busy.0 D-69190 Walldorf Document Date: August 2010 . At first the work processes are running in parallel. After 15 minutes the first warehouse tasks are already created so that the picking process can start. With a utilization of 85% less than 26 cores are fully utilized. High Performance Warehouse Management for Retailers The wave release was tested with 10-fold parallelization.000 items/h.

CPU utilization was around 45% with some spikes up to 75%. CPU utilization is around 50% with some peaks up to 72%. At the end of the online processing there is a backlog of qRFC queues to be processed.000 42.8 RAM in LPAR 217GB TCODE: Processed TUs 30 42 CPU utilization 32% /SCWM/RFUI Processed Items 30.5 4. Retailers 45 of 113 Allee 16 Version: 1.176 DB2 6% © 2006 SAP AG SAP EWM 7. High Performance Warehouse Management for Retailers Figure 15: CPU utilization during outbound picking and staging The throughput figures and resource consumption of the remaining three outbound wave related processes are summarized in the table below. This test anticipated a scenario in which 4 office users work with multiple SAPGUI sessions (each session is simulated by one vuser) and work continuously on the creation of ODs.5 6.000 6. Throughput Resource Consumption Scale A Scale B Scale B Number of users 30 42 Cores in LPAR 30 OB3D Runtime (min) 7. These qRFCs could be tuned away by deactivating the wave update with TU numbers (see SAP note 1439613). the goods issue and departure of TUs was performed with 14 vusers achieving a runtime of less than 17 minutes. taking some further 50 minutes.5 sec) to simulate a fast loading in less than 7 minutes achieving a throughput of 6176 items/min.0 D-69190 Walldorf Document Date: August 2010 .5 ABAP 94% Actual throughput 4. The CPU utilization was 32%. The loading process (OB3D) was tested with a relatively low think time (only 4. Similarly to OB3E.000 Processed HUs 1.200 1. Likewise the creation of ODs (OB3E) for 42000 delivery items was performed in less than 11 minutes using 14 vusers (LoadRunner virtual users) and 0 seconds think time.680 Think time (sec) 4.00: High Performance Warehouse Management for Page Dietmar-Hopp.

3.000 Think time (sec) 0 0 ABAP 98% Actual throughput 3.9 2.514 RAM 18% throughput (items/hour) Table 16: Throughput and resource consumption in Outbound scenario (OB3D-E) Throughput Resource Consumption Scale A Scale B Scale B Number of users 10 14 Cores in LPAR 30 OB3F Runtime (min) 13.867 235.205.000 Think time (sec) 0 0 ABAP 95% Actual throughput 2.807 RAM 21% throughput (items/hour) Table 17: Throughput and resource consumption in Outbound scenario (OB3F) 6.0 D-69190 Walldorf Document Date: August 2010 .6 RAM in 217GB TCODE: LPAR /SCWM/TU Processed TUs 30 42 CPU utilization 45% Processed items 30.7 RAM in LPAR 217GB TCODE: Processed TUs 30 42 CPU utilization 50% /SCWM/TU Processed items 30. Retailers 46 of 113 Allee 16 Version: 1.614 3.530.000 42.4 Guaranteed Picking Response Time It is common that service level agreements have to guarantee a certain response time.000 42.6 16.000 370. which means that the overwhelming majority of users are expected to experience a good response time.588 RAM 19% throughput (items/hour) 9.00: High Performance Warehouse Management for Page Dietmar-Hopp.353 151. The stipulation of a © 2006 SAP AG SAP EWM 7.600 14.1 DB2 5% (items/min) Extrapolated 132.3 10. High Performance Warehouse Management for Retailers (items/min) Extrapolated 240.925 DB2 2% (items/min) Extrapolated 216.824 Extrapolated throughput (HUs/hour) Scale A Scale B Scale B Number of users 10 14 Cores in LPAR 30 OB3E Runtime (min) 8.

whereas the average is still “good”. for example.9.5 . Each test took 7.7ms and the median was 844. the slight increase in duration stemming from increased ramp-up/ramp-down time when more users were added.1 minutes. RT>900ms The average response time in the test was 843. High Performance Warehouse Management for Retailers threshold for an average response time is often not enough because it could happen that. In this test the number of users varied from 1 up to 410. The average response time of the picking dialog step (OB3B_Src_HU_2) increased from 705ms to 876ms (see Figure 18).5 Picking and Staging Scalability Test In addition to the isolated single-user and multi-user tests a scalability test on the outbound picking and staging process (OB3B. 6. The results are depicted in the figures below. The average think time was 8 seconds as in the tests reported earlier. 90% of users have a very low response time and 10% of users suffer from an unacceptable response time. scale B) was performed.0 indicating a very small statistical spread. The throughput increased linearly as shown in Figure 16. © 2006 SAP AG SAP EWM 7. For this reason we briefly discuss the response time distribution of the crucial picking step.3. The following table shows that only few users have a response time greater than 1 sec: Response Time Percentage of Dialog Steps > 900ms 16% > 1000ms 3% > 1100ms 2% > 1200ms 1% Table 18: Response time distribution. The same holds for the CPU utilization (Figure 17). Retailers 47 of 113 Allee 16 Version: 1. Each user processed one iteration with 50 items.0 D-69190 Walldorf Document Date: August 2010 .00: High Performance Warehouse Management for Page Dietmar-Hopp. The distribution reported here stems from a scale-B run with 420 users and 8 sec think time.

0 D-69190 Walldorf Document Date: August 2010 .00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 48 of 113 Allee 16 Version: 1. High Performance Warehouse Management for Retailers Figure 16: Throughput in picking and staging over users Figure 17: CPU utilization of picking and staging over users © 2006 SAP AG SAP EWM 7.

The scenario combines inbound and outbound processes with the main difference that goods are not put away to a high rack storage.4 Flow-Through Scenario 6.600 items) were created in 18 minutes without wave assignment and in 20 minutes including the assignment to the FT wave.(See section 6. In this test the system reached a throughput of 180. Because the processes.2.000 items/h (3000 items/min).4.3. respectively).2 for general remarks). only requires a few seconds so it will not be further reported. 6. apart from the provisioning of HUs at the destination area and apart from picking.1 and 6.2. however. The 400 ODOs (9.4. are identical to the related processes of the Inbound and © 2006 SAP AG SAP EWM 7.1 Processing of Incoming Inbound and Outbound Deliveries The processing of the deliveries coming through the qRFC interface is tested very much as in the related Inbound and Outbound scenarios (see sections 6. From the material flow perspective the inbound part of the scenario ends with the putaway to the distribution area and the outbound part starts with the picking within the distribution area.1.00: High Performance Warehouse Management for Page Dietmar-Hopp. closing the HUs and staging.0 D-69190 Walldorf Document Date: August 2010 . Retailers 49 of 113 Allee 16 Version: 1. High Performance Warehouse Management for Retailers Figure 18: Picking response time over users In an additional scale A-based test with 300 users the think time was halved to 4 seconds. The single processes are displayed in Figure 19. 6. The one inbound delivery to be processed in this scenario. but rather transported to a distribution area (also called a deconsolidation station) where they are re-packed.2 Dialog Performance This section reports on the dialog performance of important dialog steps within the Flow-Through scenario.

This means that the workers will remove them whenever appropriate but without notifying the EWM system. the destination bin and the consolidation group for the HU and saves (FT4_Save_HU). The confirmation is done by pressing Enter again (FT9_HU_2). In the next screen he confirms the source bin and HU (FT9_Conf_Src_Bin_1 for the scan simulation and FT9_Conf_Src_Bin_2 for the actual confirmation). This is repeated until all 400 destination HUs have been picked into. navigates to Creation of single HU and specifies the work center (the identifier for the distribution area). loading (FT10) and finally creation of ODs. FT9_HU_1). The user therefore logs in to the system with a mobile device. For the mapping to the related processes in the other scenarios we refer to the scenario specification in the appendix. will be restricted to the picking and staging (see next section). In the © 2006 SAP AG SAP EWM 7. For the picking processes each user logs into the system via mobile device. the picked quantity and the HU identifier for each destination HU (FT8_Target_HU). the FT scenario can be very briefly explained: the inbound part comprises the creation of unloading warehouse tasks and goods receipt (FT2). but separated in the test. The steps of the processes already described. closing the HUs (FT8b). Every user is responsible for one source HU (which contains a single product) and will distribute the 400 delivery items to the 400 destination HUs. as configured in Customizing. resulting in more measurement points in the space of potential volume structures. For closing a HU the user navigates to HU Maintenance and enters the work center. unloading (FT5) and putaway (FT6). The user enters the source HU with “his” product and presses Enter. a process which is usually included with picking. For the staging process the user logs in via mobile device and navigates to Selection by HU. staging (FT9). navigates to Pick Point and specifies the work center. picking (FT8). The steps of the processes unique to FT are as follows: as a prerequisite for the picking process 400 empty destination HUs have to be set up in the distribution area and created in the EWM system (FT4). High Performance Warehouse Management for Retailers Outbound scenarios. He then enters the HU to be staged and presses Enter (again the scan simulation.0 D-69190 Walldorf Document Date: August 2010 . Then for each HU to be closed he specifies the HU and presses Enter (FT8B_Close_HU_1. the performance of all processes is measured. wave release (FT7). provisioning of destination HUs (FT4). which simulates the scan) and then confirms the HU by pressing Enter again (FT8B_Close_HU_2). because of technical reasons. The reporting of the throughput figures. Figure 19: Flow-through processes Despite the overlap of processes with the other scenarios. which simulates the scan of the HU (FT8_SRC_HU_1) and then confirms this HU (FT8_SRC_HU_2). goods issue and departure (FT11). He then enters the packing material number. In the test scenario one user is closing the destination HUs (FT8B). He then specifies the product. Note that the empty source HUs are automatically deleted by the system. such as unloading.00: High Performance Warehouse Management for Page Dietmar-Hopp. need not be reiterated here. Retailers 50 of 113 Allee 16 Version: 1. This step is repeated until all 400 HUs have been set up. however. The outbound part includes the creation of TUs including ODO assignment (FT3).

3 /SCWM/TU Save_2 2. Dialog steps not included have an average response time below 50ms.4 TCODE: Assign_ODOs_TU 10. Single-User Test Average Response Time (sec) Search_Items 1.2 Press_Create 1.0 D-69190 Walldorf Document Date: August 2010 .4 /SCWM/RFUI HU_Enter_2 0.4 TCODE: Unload_WTs 3.00: High Performance Warehouse Management for Page Dietmar-Hopp.4 FT5 HU_Enter_2 0.5 Checkpoint_Arrival_Save 1.05 TCODE: DestBin_Enter_2 0.03 FT4 TCODE: /SCWM/RFUI ASN_Enter_2 0. High Performance Warehouse Management for Retailers subsequent screen he confirms the destination bin (FT_Conf_Dest_Bin_1 and FT_Conf_Dest_Bin_2.3 FT6 IP_PUT_2 0.4 Goods_Receipt 5.6 FT2 Menu_Unload 1. respectively).0 /SCWM/PRDI Save 2.0 Door_Arrival_Door 4. The response times of the processes that were tested in single-user mode are summarized in the next table followed by the table with the single-user/multi user-results of the remaining processes.3 Save_4 0.9 TCODE: /SCWM/RFUI © 2006 SAP AG SAP EWM 7.8 Save_HU 0.5 FT3 Save_1 0.4 Save_3 3. Retailers 51 of 113 Allee 16 Version: 1.4 Assign_TU_Door 4.

7 Table 20: Flow-through scenario-related response times of the most complex and resource-intensive dialog steps (FT7.4 TCODE: Generate_ODs 12. High Performance Warehouse Management for Retailers Table 19: Flow-through scenario-related response times of the most complex and resource-intensive dialog steps (FT2-6) Single-User Test Average Response Time (sec) Release_Wave 360 FT7 incl.6 DepartureFromDoor 4.03 TCODE: /SCWM/RFUI Search 1.1 Save_2 2.9 Goods_Issue 38.4 Save_3 2.0 D-69190 Walldorf Document Date: August 2010 . Retailers 52 of 113 Allee 16 Version: 1.8 FT11 Check 10.4 /SCWM/TU Save_1 5.00: High Performance Warehouse Management for Page Dietmar-Hopp. UPD (4 min) /SCWM/RFUI Close_HU_1 0. UPD (6 min) TCODE: Release_Wave 240 excl. 8b. 11) © 2006 SAP AG SAP EWM 7.1 FT8b Close_HU_2 0.4 Departure_Save 13.

2 0.2 FT9 Conf_Dest_Bin_2 0. Retailers 53 of 113 Allee 16 Version: 1.4 Table 21: Flow-through scenario-related response times of the most complex and resource-intensive dialog steps (FT8-10) © 2006 SAP AG SAP EWM 7.2 /SCWM/RFUI Conf_TU_Loaded 0.2 0. High Performance Warehouse Management for Retailers Single-User Test Multi-User Test Average Response Average Response Time (sec) Time (sec) Src_HU 0.6 FT10 HU_2 0.9 TCODE: /SCWM/RFUI Conf_Src_Bin_2 0.00: High Performance Warehouse Management for Page Dietmar-Hopp.8 0.7 0.2 0.2 0.1 /SCWM/RFUI TU_3 0.3 0.0 D-69190 Walldorf Document Date: August 2010 .1 0.032 FT8 Target_HU 0.2 TCODE: HU_2 0.3 TCODE: Conf_Dest_Bin_2 0.032 0.

743 DB2 13% (items/min) Extrapolated throughput 164.4. Throughput Resource Consumption Number of users 24 Cores in LPAR 30 FT8 Runtime (min) 27. HUs/hour) Number of users 40 Cores in LPAR 30 FT9 Runtime (min) 3.5 RAM in LPAR 217GB TCODE: Processed Items 9. High Performance Warehouse Management for Retailers 6.1 RAM in LPAR 217GB TCODE: Processed Items 9.00: High Performance Warehouse Management for Page Dietmar-Hopp.3 Dialog Throughput and Resource Consumption This section summarizes the dialog throughputs and resource consumptions of the steps tested in multi- user mode.600 CPU utilization 6% /SCWM/RFUI Processed HUs 400 Think time (sec) 5 ABAP 87% Actual throughput 2. Retailers 54 of 113 Allee 16 Version: 1.600 CPU utilization 15% /SCWM/RFUI Processed dest.5% (items/hour) Extrapolated throughput 6857 (HUs/hour) Table 22: Throughput and resource consumption in the Outbound scenario (FT8-9) © 2006 SAP AG SAP EWM 7.571 RAM 20. HUs 400 Think time (sec) 3 ABAP 85% Actual throughput 354 DB2 15% (items/min) Extrapolated throughput 21.0 D-69190 Walldorf Document Date: August 2010 .255 RAM 22% (items/hour) Extrapolated throughput 886 (Dest.

0 D-69190 Walldorf Document Date: August 2010 . In this scenario 230 inbound and 230 outbound deliveries with 24 items each were processed in around one minute on a 5-core LPAR. Note that unlike the FT scenario no wave assignment takes place. loading (CD6) and finally OD creation. creation of TUs and assignment of ODOs and doors (CD3). picking (CD5).7 RAM in LPAR 217GB TCODE: Processed TUs 40 CPU utilization Up to 25% /SCWM/RFUI Processed Items 9. goods issue and departure (CD6). The scenario consists of these processes: goods receipt and creation of unload WTs (CD2).5. 6.5% (items/hour) Extrapolated throughput 1.600 Processed HUs 400 Think time (sec) 5 ABAP 93% Actual throughput 701 DB2 7% (items/min) Extrapolated throughput 42.2 Dialog Performance The Cross-Docking (CD) scenario is the simplest of the four scenarios.044 RAM 20.5. Similarly to FT it combines inbound with outbound processes as shown in Figure 20. © 2006 SAP AG SAP EWM 7.752 (HUs/hour) Table 23: Throughput and resource consumption in the Outbound scenario (FT10) 6. High Performance Warehouse Management for Retailers Throughput Resource Consumption Number of users 40 Cores in LPAR 30 FT10 Runtime (min) 13.5 Cross-Docking Scenario 6. unloading (CD4). Picking in this scenario is just the transport from the inbound staging area to the outbound staging area.1 Processing of Incoming Deliveries The processing of the incoming inbound and outbound delivery documents have been tested with the same method as in the other scenarios.00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 55 of 113 Allee 16 Version: 1.

0 Door_Arrival_Door 0.1 TCODE: Unload_WTs 0.9 CD3 Save_1 0.3 Assign_TU_Door 4.4 TCODE: Assign_ODOs_TU 9.04 TCODE: DestBin_Enter_2 0.5 Goods_Receipt 2.1 /SCWM/TU Save_2 2. Single-User Test Average Response Time (sec) Search_Items 1. High Performance Warehouse Management for Retailers During picking (CD5) the user scans and confirms the source HU (CD5_Src_HU_Enter1/2) and then the destination bin and destination HU which is equal to the source HU (CD5_Dest_HU_Enter1/2).1 CD4 HU_Enter_2 0.1 CD2 Menu_Unload 1.8 ASN_Enter_2 0.0 D-69190 Walldorf Document Date: August 2010 .00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 56 of 113 Allee 16 Version: 1.5 Press_Create 0.8 Checkpoint_Arrival_Save 1.9 /SCWM/PRDI Save 0.7 /SCWM/RFUI © 2006 SAP AG SAP EWM 7. Figure 20: Cross-Docking processes The next two tables summarize the average response times.

6 CD5 Dest_HU_Enter2 0.3 TCODE: /SCWM/RFUI TU_3 0.00: High Performance Warehouse Management for Page Dietmar-Hopp.6 0. Retailers 57 of 113 Allee 16 Version: 1.4 Table 25: Cross-docking scenario-related response times of the most complex and resource-intensive dialog steps (CD5-6) © 2006 SAP AG SAP EWM 7.2 TCODE: Conf_Dest_Bin_2 0.7 CD7 Check 3. High Performance Warehouse Management for Retailers Search 1.2 0.0 /SCWM/TU Save_1 5.5 Departure_Save 13.9 TCODE: Generate_ODs 13.6 CD6 HU_2 0.2 0.5 Save_3 2.7 Table 24: Cross-docking scenario-related response times of the most complex and resource-intensive dialog steps (CD2-4.2 /SCWM/RFUI Conf_TU_Loaded 0.2 0.2 Save_2 2.6 0. 7) Single-User Test Multi-User Test Average Response Average Response Time (sec) Time (sec) Src_HU_Enter2 0.3 0.0 D-69190 Walldorf Document Date: August 2010 .6 Goods_Issue 39.4 DepartureFromDoor 4.

High Performance Warehouse Management for Retailers 6. Retailers 58 of 113 Allee 16 Version: 1.5.0 D-69190 Walldorf Document Date: August 2010 .553 Extrapolated throughput (HUs/hour) Number of users 23 Cores in LPAR 30 CD6 Runtime (min) 5.7 RAM in LPAR 217GB TCODE: Processed Items 5.5% /SCWM/RFUI Processed HUs 690 Think time (sec) 8 ABAP 91% Actual throughput 968 DB2 9% (items/min) Extrapolated 58.520 CPU utilization 9. Throughput Resource Consumption Number of users 3 Cores in LPAR 30 CD5 Runtime (min) 26.7 RAM in LPAR 217GB TCODE: Processed Items 5.420 RAM 15% throughput (items/hour) 1.105 RAM 15% throughput (items/hour) 7263 Extrapolated throughput (HUs/hour) Table 26: Throughput and resource consumption in Outbound scenario (CD5-6) © 2006 SAP AG SAP EWM 7.520 CPU utilization 6% /SCWM/RFUI Processed dest. 690 HUs Think time (sec) 3 ABAP 83% Actual throughput 207 DB2 17% (items/min) Extrapolated 12.3 Dialog Throughput and Resource Consumption The next table documents the dialog throughputs and resource consumptions of the steps tested in multi- user mode.00: High Performance Warehouse Management for Page Dietmar-Hopp.

66GB) was used by processes and operating system. The red marked processes are the most CPU intensive ones.00: High Performance Warehouse Management for Page Dietmar-Hopp. Figure 22 shows the CPU utilization during the first hour of the test run along with the progress of the single processes involved. The overlap of the two scenarios is motivated by the possible shift plan shown in Figure 21. the HUs to be put away are given as input of the script. The LoadRunner scripts have been extended in order to account for the interdependencies of the processes. © 2006 SAP AG SAP EWM 7. During this test the LPAR was configured with 40 dedicated cores and 212 GB RAM. the test here achieves realism by overlapping the processes and the two major scenarios “inbound” and “outbound”. in the simultaneous scenario the HUs that are ready to be put away are determined by the script itself so that unloading and put away can be safely run in parallel. for example. Here the Inbound scenario happens in the morning in parallel to the processing of outbound waves. Figure 21: Possible Warehouse Shift Plan The simultaneous scenario simulates a one-hour time window in which one outbound wave is fully processed in parallel to the Inbound scenario.6 Simultaneous Inbound/Outbound Scenarios The simultaneous inbound/outbound test approaches a realistic simulation of a productive EWM system. excluding file system cache. Up to 31% RAM (ca. the outbound wave after approximately 1 hour. High Performance Warehouse Management for Retailers 6. Retailers 59 of 113 Allee 16 Version: 1. While in the isolated Inbound scenario. Whereas in the previously reported tests the processes have been tested in isolation.0 D-69190 Walldorf Document Date: August 2010 . Moreover we simulated a possible worst-case scenario in which wave release runs fully parallel with picking and staging. The inbound processes are finished after 1 hour 45 min.

0 D-69190 Walldorf Document Date: August 2010 . such as picking confirmation. Retailers 60 of 113 Allee 16 Version: 1. Apart from two dialog steps. The exceptions are the specification of the TU to be loaded (not in the figure) and the confirmation of the loaded TU. Up to 511 vusers are working in parallel. the average response times are well below one second. Both take around 2 seconds which is acceptable because these steps only happen once per TU.3 min). High Performance Warehouse Management for Retailers Figure 22: CPU utilization in simultaneous scenario The number of virtual users (vusers) over the time is shown in Figure 23.00: High Performance Warehouse Management for Page Dietmar-Hopp. Wave release takes around 1340 seconds (22. Figure 24 plots selected RF dialog steps. © 2006 SAP AG SAP EWM 7.

0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers Figure 23: Running vusers © 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 61 of 113 Allee 16 Version: 1.

0 D-69190 Walldorf Document Date: August 2010 . bin Put-away (IN4) Confirm HU Figure 24: Response times of selected RF dialog steps © 2006 SAP AG SAP EWM 7. bin Loading (OB3D) Confirm dest. Retailers 62 of 113 Allee 16 Version: 1.00: High Performance Warehouse Management for Page Dietmar-Hopp. High Performance Warehouse Management for Retailers Loading (OB3D) Confirm TU loaded Picking and Staging (OB3B) Confirm source HU Unloading (IN3) Confirm destination bin Picking and Staging (OB3B) Confirm dest.

but carrying out such analysis by means of system prototyping is much more important. We recommend that this kind of performance-related prototyping analysis shall be a project phase for every high throughput warehouse implementation. including integration of automated material flow systems. and in order to foster the projects with SAP’s expertise. Besides those processes which were set up and tested within this test project. is feasible (i. © 2006 SAP AG SAP EWM 7. Thus risk mitigation and analysis is possible based on a first business blueprint phase. and in a parallel user environment. High Performance Warehouse Management for Retailers 7 Conclusions and Outlook The test results above show: the capabilities of SAP EWM to handle real-life warehouse business processes without any modification or AddOn development the capabilities of SAP EWM for daily mass transaction volumes. the SAP Center of Excellence (CoE) provides Value Prototyping services which enable these performance analysis and validations to be carried out in a very early project phase. there are short dialogue response times in all mobile device execution steps like picking and staging) that processing of complex and simultaneous warehouse scenarios without process issues is possible in SAP EWM The scenario descriptions provided shall offer guidance for SAP EWM implementation projects in the food and hard goods retailer industry segments by providing well-optimized standard implementations for that industry. within and beyond the required performance KPIs that time-critical daily processing of information on the level of a single stock keeping unit (SKU). In order to facilitate this project phase for SAP customers.e.0 D-69190 Walldorf Document Date: August 2010 . Retailers 63 of 113 Allee 16 Version: 1. and mobile devices/UIs. SAP EWM supports a large portfolio of additional processes and process variants.00: High Performance Warehouse Management for Page Dietmar-Hopp. A generic risk for any standard software implementation project is based on the fact that potential performance issues are often related to the specific details of the system implementation.

1 Basics Step What to do Switch off logs Set application log for wave release. High Performance Warehouse Management for Retailers 8 APPENDIX Here is the list of support package levels of the various software components of the SCM test system: Software Component SWC Description Release SP Level SAP_ABA Cross-Application Component 701 0005 SAP_BASIS SAP Basis Component 701 0005 PI_BASIS Basis Plug-In 701 0005 ST-PI SAP Solution Tools Plug-In 2005_1_700 0006 SAP_BS_FND SAP Business Suite Foundation 701 0004 SAP_BW SAP Business Warehouse 701 0005 SAP_AP 700 0017 EA-IPPE SAP iPPE (EA-IPPE) 400 400 0016 SCEMSRV SCEMSRV 7. SAP menu: EWM Settings Activate Application Log © 2006 SAP AG SAP EWM 7. Please note: All warehouse dependant entries mentioned later on have to be created for warehouse number EWM1.1.1 Detailed Customizing Settings This chapter shows detailed customizing settings per process.0 700 0004 SCM_BASIS SCM Basis 7.0 D-69190 Walldorf Document Date: August 2010 . warehouse order log and warehouse task to activation level “very important”.0 700 0004 BI_CONT Business Intelligence Content 704 0003 QIE Quality Inspection Engine 2.00 200 0006 ST-A/PI Application Servicetools for SCM 500-700 01L_SCM570 0000 Table 27: Installed Software Components 8. 8.0 700 0004 SCM Supply Chain Management 7.0 700 0004 SCMEWM Extended Warehouse Management 7. Retailers 64 of 113 Allee 16 Version: 1.0 700 0004 SCMBPLUS SCM Basis PLUS 7. Other logs should not be switched on.0 700 0004 SCMSNC SCMSNC 7.00: High Performance Warehouse Management for Page Dietmar-Hopp.

to inactive for application /SCTM/FOM. Set all PPF actions. action definition /SCDL/ODR_TRANSFER Action profile /SCDL/PRD_CMMN. action definition /SCWM/SR_TU_HU_TO_CREATE and TRIG_TO_CREATION Transaction SPPFCADM © 2006 SAP AG SAP EWM 7. Set all PPF actions. action definition /SCDL/IDR_TRANSFER Action profile /SCDL/ODR. action definition /SCWM/PRD_OUT_PRINT and /SCWM/PRD_OUT_WAVE_NEW Action profile /SCDL/PRD_OUT_ODIS. action definition /SCWM/MSG_PRD_SEND_ODIS and /SCWM/PRD_OUT_POST_GI_ODIS Set all PPF actions. action definitions /SCWM/FD_OUT_PRINT. to inactive for application /SCDL/DELIVERY except: Action profile /SCDL/DR_CMMN. action definition /SCWM/MSG_DR_RESPONSE Action profile /SCDL/FD_OUT.00: High Performance Warehouse Management for Page Dietmar-Hopp. which are not needed. which are not needed. to inactive for application /SCWM/SHP_RCV except: Action profile /SCWM/TU. which are not needed. Switch off change documents for all document types in outbound delivery process using check box change docs. action definition /SCWM/MSG_PRD_SEND Action profile /SCDL/PRD_IN_IDIS. /SCWM/MSG_DTN_FD_OUT_SEND and /SCWM/MSG_FD_OUT_SEND Action profile /SCDL/IDR. Retailers 65 of 113 Allee 16 Version: 1. IMG: EWM Goods Receipt Process Inbound Delivery Manual Settings Define Document Types for Inbound Delivery Process IMG: EWM Goods Issue Process Outbound Delivery Manual Settings Define Document Types for Outbound Delivery Process Deactivate PPF actions Set all PPF actions. action definition /SCWM/MSG_PRD_SEND_IDIS and /SCWM/PRD_IN_POST_GR_IDIS Action profile /SCDL/PRD_OUT. to inactive for application /SCWM/WME.0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers Switch of PPF log for printing SAP menu: EWM Work Scheduling Print Settings Activate Application Log Switch off change documents Switch off change documents for all document types in inbound delivery process using check box change docs. which are not needed.

Retailers 66 of 113 Allee 16 Version: 1. storage section 0001. Create 42 staging area storage bins for goods issue (OI-GI- ZONE01 – OI-GI-ZONE42) in storage type 9020. SAP menu: EWM Master Data Storage Bin Create Storage Bin Create storage bins for work Create storage bins FTPD-INB-001 and FTPD-OUTB-001 © 2006 SAP AG SAP EWM 7. SAP menu: EWM Master Data Storage Bin Generate Storage Bin Create storage bins manually Create 10 staging area storage bins for goods receipt (IR-GR- Zone01 – IR-GR-ZONE10) in storage type 9010. IMG: EWM Master Data Define Storage Type Create storage sections Create sections SO01 to SO42 for storage type 9020.0 D-69190 Walldorf Document Date: August 2010 . Create 42 outbound door storage bins (OR_DOOR_01 – OR_DOOR42) in storage type 9040.600 bins) and 0050 (3. IMG: EWM Cross-Process-Settings Copy Warehouse Number Customizing Create storage type Copy storage type 0020 to storage type 0290. storage section SO01 – SO42 with bin access type OL01 to OL42. Create start bin START_BIN_0050 in storage type 0050. IMG: EWM Master Data Activity Area Generate Activity Area from Storage Type Create storage bins based on Create storage bins according to storage bin structures for structures storage types 0290 (399.00: High Performance Warehouse Management for Page Dietmar-Hopp. storage section 0001. storage section 0001. issue IMG: EWM Master Data Staging Areas Define Staging Areas Define storage bin structure Define a storage bin structure for storage types 0290 and 0050. Generate activity area for storage type FTPD with activity PICK and PTWY. storage section 0001. Create 20 inbound door storage bins (IR_DOOR_01 – IR_DOOR20) in storage type 9030. IMG: EWM Master Data Storage Bins Define Storage Bin Structure Create activity area Generate activity areas for storage types 0290 and 0050. Define storage type FTPD.1. IMG: EWM Master Data Define Storage Section Define staging areas for goods Create staging areas SO01 to SO42 for storage type 9020.2 Master data and Warehouse Layout Step What to do Create warehouse number Copy warehouse number 0001 to warehouse number EWM1. High Performance Warehouse Management for Retailers Table 28: Basic Customizing Settings 8.600 bins).

e. area SAP menu: EWM Master Data Storage Bin Assign Start/End Storage Bin for Activity Area Sort storage bins Sort storage bins for all affected activity areas (in particular 0290 and 0050) and all activities.00: High Performance Warehouse Management for Page Dietmar-Hopp. IMG: EWM Master Date Warehouse Door Assign Staging Area to Warehouse Door Assign staging area and door Assign staging area and door determination group to door.0 D-69190 Walldorf Document Date: August 2010 . determination group to door EWM1 / IR01 to IR01 (repeat this for all IB doors. IMG: EWM Master Date Warehouse Door Define Warehouse Door Create staging area and door Create staging area/door determination group IR01 to IR20. Create 42 outbound warehouse doors (OR01 – OR42) with default staging area group 9020 and default staging area 0001. which should be used for CD) Assign door IR01 to staging area/door determination group IR01 and so on. High Performance Warehouse Management for Retailers center SAP menu: EWM Master Data Storage bins Create storage Bin Create storage bin sorting Create Bin Sorting for Activity Area/Activity: FTPD/PICK SAP menu: EWM Master Data Storage bins Sort storage bins Define work center Define work center FTPD SAP IMG: EWM Master Data Work center Define Master Data attributes Define work center determination Define work center determination SAP menu: EWM Master Data Work center Determine work center for cross-docking Assign start storage bin to activity Assign start bin START_BIN_0050 to activity area 0050. Assign warehouse door IR01 – IR20 to staging area group/staging area 9010/0001. Retailers 67 of 113 Allee 16 Version: 1.g. staging bays IR-GR- ZONE01 to IR-GR-ZONE10 (staging bays are shared by two © 2006 SAP AG SAP EWM 7. determination groups IMG: EWM Master Data Staging Areas Define Staging Area and Door Determination Groups Assign staging area to Assign warehouse door OR01 to staging area 9020/SD01 and so warehouse doors on. SAP menu: EWM Master Data Storage Bin Sort Storage Bins Create warehouse doors Create 20 inbound warehouse doors (IR01 – IR20) with default staging area group 9010 and default staging area 0001. IMG: EWM Master Data->Warehouse Door -> Assign Staging Area/Door Determination Group to Door Set door / staging area Create entries for warehouse process type 1F11 with staging determination inbound area/door determination group IR01 to IR20 with constant staging area group 9010 and staging area 0001.

Create two entries to find queue IB_PUTAWAY based on either destination activity area 0290 or 0291.0 D-69190 Walldorf Document Date: August 2010 . Create an entry to find queues OB_PICK_01 to OB_PICK_42 based on activity area 9020 and bin access type of the different staging bins. High Performance Warehouse Management for Retailers doors) and warehouse doors IR01 to IR20. Create an entry to find queue OB_LOAD based on warehouse process type 3A70. Create an entry to find queue OB_REPL based on warehouse process type 3A10. Determine Queues FTPD_IN and FTPD_OUT FT_UNLOAD FT_INTMOVE FT_PICK FT_STAGE FT_LOAD IMG: EWM Cross-Process Settings-> Resource Management-> Define Queues -> Define Queue Determination Criteria Maintain resource Group Maintain resource Group PTWY. SAP Menu: -> EWM -> Settings -> Shipping and Receiving-> Staging Area and Door Determination (Inbound) Set door / staging area Create entries for routes SR0001 to SR0420 with staging area determination outbound SO01 to SO42 and staging bay OI-GI-ZONE01 to OI-GI-ZONE42.00: High Performance Warehouse Management for Page Dietmar-Hopp. Create an entry to find queue IB_UNLOAD based on source activity area 9010. SAP Menu: -> EWM -> Settings -> Shipping and Receiving-> Staging Area and Door Determination (Outbound) Define Queues Define queues: IB_UNLOAD IB_PUTAWAY OB_PICK_01 to OB_PICK_42 OB_LOAD OB_REPL FT_UNLOAD FT_INTMOVE FT_PICK FT_STAGE FT_LOAD CD_UNLOAD CD_PICK CD_LOAD IMG: EWM Cross-Process Settings-> Resource Management-> Define Queues -> Define Queues Define Queue determination Create an entry to find queue IB_PUTAWAY based on criteria warehouse process type 1F11. Maintain resource Group FTPD Maintain resource Group UNLO © 2006 SAP AG SAP EWM 7. Retailers 68 of 113 Allee 16 Version: 1.

CD_LOAD_023 SAP menu: EWM Master Data Resource Management -> Maintain resource Table 29: Master Data and Warehouse Layout © 2006 SAP AG SAP EWM 7. Create resource IB_UNLOAD_001 to IB_UNLOAD_020 with resource type RT01.FT_LOAD_040 CD_UNLOAD_001 CD_PICK_001 .CD_PICK_003 CD_LOAD_001 . default presentation device PRES and queue IB_UNLOAD. Create resources OB_PICK_001 to OB_PICK_ 420 with resource type RT01 and queues OB_PICK_01 to OB_PICK_42 (each with 10 resources). Create resources OB_LOAD_001 to OB_LOAD_ 042 with resource type RT01 and queue OB_LOAD. High Performance Warehouse Management for Retailers SAP menu: EWM Master Data Resource Management -> Maintain Resource Group Maintain Queue Sequence for Enter queue IB_PUTAWAY for resource group PTWY and queue Resource Group INBOUND for resource group UNLO. UNLO SAP menu: EWM Master Data Resource Management -> Maintain Queue Sequence for Resource Group Maintain resource Maintain resource Create resource IB_PUTAWAY_001 to IB_PUTAWAY_004 with resource type RT01. Maintain Queue Sequence for Resource Group FTPD. default presentation device PRES and queue IB_PUTAWAY. Retailers 69 of 113 Allee 16 Version: 1. Create resources OB_REPL_001 to OB_REPL_ 004 with resource type RT01 and queue OB_REPL.FT_STAGE_040 FT_LOAD_001 . resource group PTWY.00: High Performance Warehouse Management for Page Dietmar-Hopp.FT_PICK_024 FT_STAGE_001 . resource group UNLO. FT_UNLOAD_001 FT_INTMOVE_001 FT_PICK_001 .0 D-69190 Walldorf Document Date: August 2010 .

IMG: EWM Cross-Process-Settings Warehouse Task Determine Warehouse Process Type Create storage type search Create storage type search sequence 0290.1. sequence IMG: EWM Goods Receipt Process Strategies Storage Type Search Define Storage Type Search Sequence for Putaway © 2006 SAP AG SAP EWM 7. the status 'in transit (DTR)' should be deactivated. Retailers 70 of 113 Allee 16 Version: 1. process type determination ZL and warehouse process type 1F11. CD. IMG: EWM Cross-Process-Settings Warehouse Task Define Process-oriented Storage Control – Storage Process – Definition Create warehouse process type Copy warehouse process type 1011 to 1F11. IMG: EWM Cross-Process Settings Delivery Processing Status Management Define Status Profiles The Z-profile has to be assigned to the document type used for inbound delivery process. control indicator IMG: EWM Cross-Process-Settings Warehouse Task Define Control Indicators for Determining Warehouse Process Type Create warehouse process type Create warehouse process type determination entry with determination document type INB. Therefore.00: High Performance Warehouse Management for Page Dietmar-Hopp. Specify ZIN6 as storage process and 001 as availability group. FT Set no status “In Transit” in all Inbound Processes In the status profile for the inbound delivery type INB. CD and Inbound scenario.3 Inbound Step What to do Only if you do not use yard Management IB. a Z-status profile has to be created. IMG: EWM Goods Receipt Process Inbound Delivery Manual Settings Define Document Types for Inbound Delivery Process Set Parameter 'Goods Receipt Mode' to Value '1 Only Send Full Set “No partly goods receipt” in GR at End of Put away Process' all Inbound Processes SAP Menu -> EWM -> Interfaces -> ERP Integration -> General Settings -> Set Control Parameters for ERP Version Control Create process-oriented storage Create storage process ZIN6 with direction putaway. High Performance Warehouse Management for Retailers 8. IMG: EWM Cross-Process-Settings Warehouse Task Define Warehouse Process Type Create warehouse process type Create process type determination ZL. Enter step IB03 as 2nd step with no check box checked and duration of 30 minutes. control IMG: EWM Cross-Process-Settings Warehouse Task Define Process-oriented Storage Control – Storage Process – Definition Assign storage process steps Enter step IB01 as 1st step with both check boxes checked and duration of 5 minutes. used in FT.0 D-69190 Walldorf Document Date: August 2010 .

SAP menu: EWM Delivery Processing Actions Maintain Condition Records for PPF Schedule Conditions © 2006 SAP AG SAP EWM 7. FT_LOAD. High Performance Warehouse Management for Retailers Assign storage type to storage Create an entry for storage type search sequence 0290 with type search sequence storage type 0290. IMG: EWM Goods Receipt Process Strategies Storage Type Search Define Putaway Control Indicator Maintain master data for products Enter transaction with the affected products.00: High Performance Warehouse Management for Page Dietmar-Hopp. OB_LOAD SAP menu: EWM Settings Activate Asynchronous Delivery Update Use no multiple delivery note Create condition record for application DPP and maintenance group printing in all outbound processes 0_RPMA with the following attributes: condition type = 0RMA. On the warehouse data tab enter process type determination indicator ZL.0 D-69190 Walldorf Document Date: August 2010 . SAP menu: EWM Master Data Product Maintain Warehouse Product Table 30: Customizing for Inbound Scenario 8. Data' to limit the data amount. using flag “NoWvUpd”. CD_PICK. IMG: EWM Cross-Process-Settings Define General Settings for Parallel Processing Adapt transportation unit handling Set flag 'Do Not Read Del. warehouse number EWM1 and the default entitled to dispose. IMG: EWM Goods Receipt Process Strategies Storage Type Search Specify Storage Type Search Sequence for Putaway Create putaway control indicator Create an entry for putaway control indicator 0290 with storage type search sequence 0290. Retailers 71 of 113 Allee 16 Version: 1. which would be executed number during TU creation and OD creation. SAP menu: EWM Shipping and Receiving -> Process Transportation Unit -> Icon Maintain Default Values Use asynchronous delivery update Set Queues CD_LOAD.4 Outbound Step What to do Deactivate wave update with TU Deactivate wave update with TU number. IMG: EWM Goods Receipt Process Strategies Storage Type Search Assign Storage Types to Storage Type Search Sequence Specify storage type search Create an entry for warehouse process type 1F11 with search sequence sequence 0290 and no putaway rule. document type = OUTB and change mode = I.1. On the storage type data tab create an entry for storage types 0050 and 0290 and adopt data. document category = FDO. putaway control indication 0290 and staging area/door determination group one of IR01 to IR20 (depending on where the product should be unloaded).

maximum number of HUs set to 2 and maximum number of WTs per HU set to 25. High Performance Warehouse Management for Retailers Use monitor instead of wave SAP menu: EWM Monitoring -> SAP Warehouse Management management for releasing of Monitor waves Turn off VAS relevance check Delete entries to check VAS relevance for inbound and outbound deliveries IMG: EWM Cross-Process Settings Value-Added Services (VAS) Define Relevance for VAS Disable adaption of the route Disable warning or error message in case of different routes or departure dates between outbound delivery order and TU activity.0 D-69190 Walldorf Document Date: August 2010 . IMG: EWM Cross-Process-Settings Warehouse Order Define Packing Profile for Warehouse Order Creation Create warehouse order creation Create rule OUPT with creation category consolidation group. IMG: EWM Cross-Process-Settings Warehouse Order Define © 2006 SAP AG SAP EWM 7. IMG: EWM Cross-Process-Settings Warehouse Order Define Limit Values for the Size of a Warehouse Order Create packing profile for Create packing profile OBP1 with pack mode simple algorithm and warehouse order creation rule checkboxes create HUs and assign WTs to HUs set. packing profile OBP1 and storage process OU_1. maximum consolidation group per WO set to 1. IMG: EWM Cross-Process Settings Shipping and Receiving General Settings General Settings for Shipping and Receiving Do not create cross delivery pick Determine consolidation group based on route and goods recipient HUs IMG: EWM Goods Issue Process Define Consolidation Group Do not allow more than one consolidation group per warehouse order using limit values (see also below). Do not run TU creation and wave Schedule creation and releasing accordingly releasing in parallel Wave releasing: SAP menu: EWM -> Monitoring -> SAP Warehouse Management Monitor TU creation SAP Menu: EWM -> Shipping and Receiving -> Process Transportation Unit Create limit for warehouse order Create limit LIPT with limit type warehouse task and maximum item creation rule per WO set to 50. Retailers 72 of 113 Allee 16 Version: 1. Prevent update of start dates of the loading or unloading process in the outbound delivery order or the inbound delivery.00: High Performance Warehouse Management for Page Dietmar-Hopp. limit rule LIPT. IMG: EWM Cross-Process-Settings Warehouse Order Define Limit Values for the Size of a Warehouse Order On ERP side delivery grouping has to be set up to guarantee that for a wave there is only one delivery for a given combination of route and goods recipient. Disable copying the route of the outbound delivery order to the TU activity during loading.

Retailers 73 of 113 Allee 16 Version: 1.0 D-69190 Walldorf Document Date: August 2010 .Definition Assign storage process steps Enter step OB01 as 1st step with the first check box checked. Enter step OB03 as 2nd step with the first check box checked. IMG: EWM Cross-Process-Settings Warehouse Task Define Warehouse Process Type Create external storage process Copy storage process step OB04 to OB4P. rough bin determination and automatic wave creation set.Definition Assign warehouse process type to Assign warehouse process type 3A70 to external step OB4P. Enter step OB4P as 3rd step with no check box checked. process type determination ZL and warehouse process type 2I10. rule IMG: EWM Cross-Process-Settings Warehouse Order Define Creation Rule for Warehouse Order © 2006 SAP AG SAP EWM 7. IMG: EWM Cross-Process-Settings Warehouse Task Determine Warehouse Process Type Create storage type search Create storage type search sequence PIPT and assign storage type sequence 0050 to it. warehouse order creation rule OUPT. IMG: EWM Cross-Process-Settings Warehouse Task Define Process-oriented Storage Control – Storage Process . High Performance Warehouse Management for Retailers Creation Rule for Warehouse Order Create warehouse process type Create warehouse process type 2I10 with warehouse process category 2. SI control C. step IMG: EWM Cross-Process-Settings Warehouse Task Define Process-oriented Storage Control – External Storage Process Step Create process-oriented storage Create storage process OU_1 with direction stock removal. IMG: EWM Goods Issue Strategies Specify Storage Type Search Sequence Create storage type search Create an entry to find storage type search sequence PIPT with sequence determination removal rule FIFO based on warehouse process type 2I10.00: High Performance Warehouse Management for Page Dietmar-Hopp. IMG: EWM Goods Issue Strategies Determine Storage Type Search Sequence for Stock Removal Create limit for warehouse order Create limit REPT with limit type warehouse task and maximum item creation rule per WO set to 1. activity PICK. control IMG: EWM Cross-Process-Settings Warehouse Task Define Process-oriented Storage Control – Storage Process . storage process step IMG: EWM Cross-Process-Settings Warehouse Task Define Process-oriented Storage Control – Process-Oriented Storage Control Create warehouse process type Create warehouse process type determination entry with document determination type OUTB. IMG: EWM Cross-Process-Settings Warehouse Order Define Limit Values for the Size of a Warehouse Order Create warehouse order creation Create rule REPT with limit REPT. Create warehouse process type 3A70 with warehouse process category 2 and activity PICK.

warehouse process type IMG: EWM Goods Issue Process Wave Management General Settings Set Automatic Wave Generation for Warehouse Process Type Set Wave Template determination 1) Define Condition Table ZPT_OUTB with condition field WME_LGNUM 2) Define Access Sequence PT_O and add table ZPT_OUTB 3) Define Condition Type PT_O with access sequence PT_O 4) Define Determination Procedure ZFT1 with condition types ZFT1 and PT_O © 2006 SAP AG SAP EWM 7. IMG: EWM Goods Issue Strategies Specify Storage Type Search Sequence Create storage type search Create an entry to find storage type search sequence PETE with sequence determination removal rule FIFO based on warehouse process type 3A10. IMG: EWM Goods Issue Strategies Determine Storage Type Search Sequence for Stock Removal Assign storage bin type to storage Create an entry. physical quantity as quantity type used and checkbox WT immediately set.0 D-69190 Walldorf Document Date: August 2010 . IMG: EWM Internal Warehouse Processes Replenishment Control Activate Replenishment Strategies in Storage Types Change storage type 0050 Change entry of storage type 0050 and set checkbox for use for rough bin determination. which assigns storage bin type P002 to storage type type 0050. warehouse process type 3A10. High Performance Warehouse Management for Retailers Create warehouse process type Create warehouse process type 3A10 based on 3010 and set WO rule to REPT. IMG: EWM Goods Receipt Process Strategies Storage Bin Determination Assign Storage Bin Type to Storage Type Maintain fixed storage bins Assign an individual fix bin to products A-P0001 to A-P1025 in storage type 0050 and set maximum quantity to 100.000.00: High Performance Warehouse Management for Page Dietmar-Hopp. SAP menu: EWM Master Data Storage Bin Maintain Fixed Storage Bin Set automatic wave creation for Check checkbox AutoWave for warehouse process type 2I10. IMG: EWM Master Data Define Storage Type Create storage type search Create storage type search sequence PETE and assign storage type sequence 0290 to it. Retailers 74 of 113 Allee 16 Version: 1. IMG: EWM Cross-Process-Settings Warehouse Task Define Warehouse Process Type Maintain document/item categories Create an entry for warehouse process type 3A10 with document for replenishment type SRPL and item type SRPL IMG: EWM Internal Warehouse Processes Replenishment Control Maintain Document/Item Categories for Replenishment Warehouse Request Activate replenishment for storage Create an entry for storage type 0050 with replenishment strategy type order-related replenishment.

SAP menu: EWM Work Scheduling Wave Management Maintain Wave Templates Create condition for the Create a condition record to find condition type PT_2. High Performance Warehouse Management for Retailers 5) Assign procedure ZFT1 to document type OUTB and document category PDO 6) Define Condition Maintenance Group WME and add condition table ZPT_OUTB and condition type PT_O IMG: EWM Goods Issue Process -> Wave Management-> Wave template determination Define Condition Tables Define Access Sequences Define Condition Types Define Determination Procedure Assign procedure to document type Define Condition Maintenance Groups Create wave templates Create a wave template release method manual and with a one hour time slot per option starting with wave completion at 9am to 10pm. SAP menu: EWM Master Data Packaging Specifications Set determination of packaging 1) Define Condition Table CUSWHTPT with condition fields specification for alternative unit of PAK_PROCT and PAK_LOCID measure 2) Define Access Sequence ZWHP and add table CUSWHTPT 3) Define Condition Type ZHWP with access sequence ZWHP 4) Define Determination Procedure ZWHP with condition type ZWHP 5) Define Condition Maintenance Group PAK and add condition table CUSWHTPT and condition type ZWHP IMG: EWM Master Data Packaging Specification Determination of Packaging Specifications Define Condition Table Define Access Sequences Define Condition Types © 2006 SAP AG SAP EWM 7. Retailers 75 of 113 Allee 16 Version: 1.0 D-69190 Walldorf Document Date: August 2010 . which leads to 14 options. IMG: EWM Goods Issue Process Wave Management General Settings Edit Parallel Processing for Waves Create packaging specification Create packaging specification for pick HU determination during WO creation with a valid packaging material and specify a determination for condition type 0BDL. supply chain unit of the warehouse and packing profile OBP1.00: High Performance Warehouse Management for Page Dietmar-Hopp. determination of wave template SAP menu: EWM Work Scheduling Wave Management Maintain Conditions for Determining Wave Templates Enable parallel wave processing Enable parallel wave processing and allow 10 parallel processes.

SAP menu: EWM Master Data Packaging Specifications Table 31: Customizing for Outbound Scenario 8. supply chain unit of the warehouse and warehouse process type 2I10. for Warehouse Process Type IMG: EWM Goods Issue Process -> Wave Management-> General Settings ->Set Automatic Wave Generation for warehouse Process Type Set Wave Template 1) Define Condition Table ZMEDIFT1 determination 2) Define Access Sequence ZFT1 3) Define Condition Type ZFT1 4) Define Determination Procedure ZFT1 © 2006 SAP AG SAP EWM 7.0 D-69190 Walldorf Document Date: August 2010 . IMG: EWM Cross-Process Settings Handling Unit Basics Define Packaging Material Types Activation of FT Business Activate BC Set /SCWM/MEDI_FT_PRODUCT Configuration Set Please find more documentation in Transaction SCPR3. IMG: EWM Master Data Define Warehouse Number Control Maintain master data for products Enter transaction with the affected products.5 Flow-Through Step What to do Automatic deletion of FT inbound Configure packaging material type to delete HUs as soon as they HU when empty get empty using flag “Delete”. High Performance Warehouse Management for Retailers Define Determination Procedure Define Condition Maintenance Groups Maintain determination procedure Set determination procedure ZWHP for the determination procedure for warehouse number for warehouse-internal processes. On the units of measure tab specify the alternative unit of measure CAR (1 CAR = 6 EA). SAP menu: Tools Customizing Business Configuration Sets Activation of BC Sets Define Merchandise Distribution Set Merchandise Distribution Process 002 for Warehouse Process for Warehouse Process Process Types FTPD and OFTP Type IMG: EWM Cross-Process Settings -> Cross-Docking (CD) -> Planned Cross-Docking -> Merchandise Distribution -> Define Merchandise Distribution Process for Warehouse Process Type Set Automatic Wave Generation Set the Auto Wave flag for Warehouse Process Type OFTP. SAP menu: EWM Master Data Product Maintain Warehouse Product Create packaging specification Create packaging specification for alternative unit of measures with operative unit of measure CAR on the warehouse tab of the main level and target quantity 6. Retailers 76 of 113 Allee 16 Version: 1.00: High Performance Warehouse Management for Page Dietmar-Hopp.1. Specify a determination for condition type ZWHP. warehouse number EWM1 and the default entitled to dispose.

Retailers 77 of 113 Allee 16 Version: 1. (Control of Creation of WT’s) IMG: EWM Cross-Process Settings -> Warehouse Task -> Define process oriented Storage control -> Assign Storage © 2006 SAP AG SAP EWM 7. IMG: EWM Cross-Process Settings -> Warehouse Task -> Determine Warehouse Process Type Change Storage Process Change Storage Process Definition MDCD Definition IB03: set checkmark for Prod/HU WT.1. SAP menu: ->Tools -> Customizing -> Business Configuration Sets -> Activation of BC Sets Define Warehouse Process Type Define Warehouse Process Type Control Indicator ZM Control Indicator IMG: EWM Cross-Process Settings -> Warehouse Task -> Define Control Indicators for Determining Warehouse Process Types Determine Warehouse Process Determine Warehouse Process Type MDCD via Process Type Type Control Indicator ZM and Document Type IND.6 Cross-Docking Step What to do Activation of Business Activate the following business configuration sets Configuration Sets /SCWM/DLV_MEDI_PO /SCWM/DLV_MEDI_SO /SCWM/MEDI_CD /SCWM/MEDI_FT_PRODUCT /SCWM/MEDI_FT_RECIPIENT Please find more documentation in Transaction SCPR3. High Performance Warehouse Management for Retailers 5) Assign procedure to document type ZFT1 6) Define Condition Maintenance Group WME IMG: EWM Goods Issue Process -> Wave Management-> Wave template determination- -> Define Condition Table -> Define Access Sequences -> Define Condition Types -> Define Determination Procedure -> Assign procedure to document type -> Define Condition Maintenance Groups Define Process-Oriented Storage Check settings of Storage Processes FTPD and OFTP Control IMG: EWM Cross-Process Settings -> Warehouse Task-> Define Process-Oriented Storage Control Table 32: Customizing for Flow-Through Scenario 8.00: High Performance Warehouse Management for Page Dietmar-Hopp.0 D-69190 Walldorf Document Date: August 2010 .

Grp to IR01 SAP menu: EWM Master Data->Product -> Maintain Warehouse Product. High Performance Warehouse Management for Retailers process step Set Storage Type Search Set Storage Type Search Sequence OMDX Sequence IMG: EWM Goods Issue Process -> Strategies -> Specify Storage Type Search Sequence Define Print Profile for Delivery Define Print Profile for Delivery Processing OB_DEL Processing IMG: EWM Goods Issue Process -> Outbound Delivery -> Print -> Define Print Profile for Delivery Processing Define Print Profile Determination Define Print Profile Determination for Goods Issue Process for Goods Issue Process IMG: EWM Goods Issue Process -> Outbound Delivery >> Print -> Define Print Profile Determination for Goods Issue Process Determine Form Determination Determine Form Determination for Delivery Note Printing for SHP for Delivery Note Printing office SP20 IMG: EWM Goods Issue Process -> Outbound Delivery >> Print -> Define Print Profile Determination for Goods Issue Process Change warehouse product Change warehouse product for relevant products: Set Proc. Type Det.00: High Performance Warehouse Management for Page Dietmar-Hopp.0 D-69190 Walldorf Document Date: August 2010 . Retailers 78 of 113 Allee 16 Version: 1. putaway = X Storage control/putaway completed = X Putaway rules = 5 © 2006 SAP AG SAP EWM 7.1. Ind. to ZM Stk Rmvl Ctrl Indicator to OMDX StagArea/DoorDet. Whse Tab Set Up Printer and Form Set Up Printer and Form Determination for outbound delivery Determination note SAP Menu: EWM -> Settings -> Shipping and Receiving -> Set Up Printer and Form Determination Table 33: Customizing for Cross-Docking Scenario 8.7 MFS Step What to do Activation of Business Activate the following business configuration sets Configuration Sets /SCWM/MFS_EXCEPTION_CODES SAP menu: ->Tools -> Customizing -> Business Configuration Sets -> Activation of BC Sets Create storage type Create storage type 0290 with the following attributes: Storage type role = J HU requirement = X Conf.

High Performance Warehouse Management for Retailers Addition stock forbidden = X Putaway storage control = 1 Mixed storage = 3 ID point active = X Delete stock identification = X Confirm removal = X Use rough bin determination = X Availability group = 002 Non-dependent stock type = FF Mandatory = X No GI = X Stock type role = N Create storage type 0291 with the following attributes: Storage type role = H HU requirement = X Conf. Retailers 79 of 113 Allee 16 Version: 1. IMG: EWM Master Data Storage Bins Define Bin Access Type Define storage bin structure Define a storage bin structure for storage type 0291. IMG: EWM Master Data Activity Area Activities Create activity area Create activity areas for storage types 0290 and 0291. Take the different aisles into account.0 D-69190 Walldorf Document Date: August 2010 . For storage type 0290 create activity areas RK1 to RK4 for the different aisles/rack feeders. © 2006 SAP AG SAP EWM 7. IMG: EWM Master Data Storage Bins Define Storage Bin Strucure Create activity Create activity MFSI with process category 3.00: High Performance Warehouse Management for Page Dietmar-Hopp. putaway = X Putaway rules = 4 Putaway storage control = 1 Capacity check = 4 Confirm removal = X Availability group = 002 No GI = X IMG: EWM Master Data Define Storage Type Create storage sections Create section 0001 for storage type 0290 and 0291. IMG: EWM Master Data Define Storage Section Create bin access types Create bin access types RCK1 to RCK4 for the different aisles.

PLC and Create two PLC interface types – one for conveyor technique and communication channel one for the rack feeders. activity MFSI and warehouse order creation rule MFS1. activity MFSI. High Performance Warehouse Management for Retailers IMG: EWM Master Data Activity Area Define Activity Area Assign storage bins to activity Assign storage bins of storage types 0290 and 0291 to their area activity areas. IMG: EWM Material Flow System (MFS) Master Data © 2006 SAP AG SAP EWM 7. manual WT forbidden checked. Take activity areas RK1 to RK4 for storage type 0290 into account. Retailers 80 of 113 Allee 16 Version: 1. IMG: EWM Master Data Activity Area Define Sort Sequence for Activity Area / Define Sort Sequence for Cross-Line Stock Putaway Assign storage bin type to Assign storage bin type P001 to storage types 0290 and 0291. Create communication channels for PLCs – two for the conveyor technique and one per rack feeder. warehouse order creation rule MFS1 and storage control relevance 3. Create PLCs based on PLC interface types – one for conveyor technique and one per aisle of the high rack. IMG: EWM Master Data Activity Area Assign Storage Bins to Activity Areas Create sort sequence for activity Create an appropriate storage bin sorting in the activity areas for area storage type 0290 and 0291. storage type IMG: EWM Goods Receipt Process Strategies Storage Bin Determination Assign Storage Bin Types to Storage Types Create storage groups Create storage groups for layout-oriented storage control: For every communication point in storage type 0291 For the different aisles/rack feeders in storage type 0290 IMG: EWM Cross-Process Settings Warehouse Task Define Storage Groups for Layout-Oriented Storage Control Create layout-oriented storage Create layout-oriented storage control according to the control warehouse layout. Create warehouse process type 3091 with warehouse process category 3.00: High Performance Warehouse Management for Page Dietmar-Hopp.0 D-69190 Walldorf Document Date: August 2010 . confirm immediately checked. source storage type 9030. warehouse order creation rule activity area 1. Create warehouse process type 3092 with warehouse process category 3. IMG: EWM Cross-Process-Settings Warehouse Task Define Warehouse Process Type Create PLC interface. Make use of the storage groups. IMG: EWM Cross-Process Settings Warehouse Task Define Layout-Oriented Storage Process Control Create warehouse process type Create warehouse process type 3090 with warehouse process category 1. source storage bin DOOR_01 and select HU w/o storage process checked. activity PTWY.

IMG: EWM Cross-Process Settings Resource Management Define Queues – Define Queue Determination Criteria Create MFS resource type Create MFS resource type for rack feeders with max. resource management active IMG: EWM Material Flow System (MFS) Master Data Define MFS Queue Create queue determination Create queue determination criteria to find queue RPT_CONVQ criteria for movements between communication points and queues RPT_RCK1Q to RPT_RCK4Q for movements in and out of the different aisles of the high rack. IMG: EWM Material Flow System (MFS) Telegram Processing Define MFS Actions Find MFS Actions Create telegram structure Create telegram structures per PLC interface type for communication to PLCs and assign DDIC structures representing the telegram format.0 D-69190 Walldorf Document Date: August 2010 . 1 telegram and one-step confirmation IMG: EWM Material Flow System (MFS) Master Data Define MFS Resource Type Create MFS action Create MFS action for warehouse task confirmation and use action function /SCWM/MFSACT_WT_CONFIRM. no resource management RPT_RCK1Q to RPT_RCK4Q for rack feeders with operation environment MFS.00: High Performance Warehouse Management for Page Dietmar-Hopp. IMG: EWM Material Flow System (MFS) Master Data Define Communication Point Types Create communication point Create necessary communication points according to the warehouse layout IMG: EWM Material Flow System (MFS) Master Data Define Communication Point Create MFS queues Create MFS queues and assign them to PLCs: RPT_CONVQ for conveyor technique with operation environment MFS. © 2006 SAP AG SAP EWM 7.g. Assign this action to the telegram type for warehouse task confirmation. Retailers 81 of 113 Allee 16 Version: 1. storage bin errors occupied) for both PLC interface types. High Performance Warehouse Management for Retailers Define PLC Interface Category Define Programmable Logic Controller (PLC) Communication Channel Define Communication Channel Create communication point type Create communication points types CP for ordinary communication points and SP for scanner points. IMG: EWM Material Flow System (MFS) Telegram Processing Define Telegram Structure Define Telegram Structure for PLC Interface Type Assign EWM exceptions to PLC Assign EWM exception codes to PLC errors (e.

SAP menu: EWM Master Data Material Flow System (MFS) Generate Application Data Create mapping for PLC objects Map EWM storage bins to PLC objects (naming convention of PLC). incorrect start errors sequence) for both PLC interface types. IMG: EWM Material Flow System (MFS) Exception Handling EWM Exceptions Define EWM Exceptions for Communication Errors Assign telegram errors to PLC Assign error codes to telegram errors (e. SAP menu: EWM Master Data Material Flow System (MFS) Map EWM Objects to PLC Objects Maintain MFS resource Maintain attributes for MFS resources used for the high rack aisles by specifying MFS queues and error bins. SAP menu: EWM Master Data Material Flow System (MFS) Maintain Programmable Logic Controller Maintain Communication Channel Generate MFS application data Automatically generate application data for MFS. communication errors sequence error) for both PLC interface types. IMG: EWM Material Flow System (MFS) Exception Handling EWM Exceptions Assign Telegram Errors to PLC Errors Create storage bins for Create storage bins for all communication points according to the communication points manually warehouse layout. Make sure to maintain the storage group correctly. Make sure to maintain the storage group correctly. SAP menu: EWM Master Data Storage Bin Generate Storage Bin Sort storage bins Sort storage bins for activity areas 0290 and 0291 and all activities. High Performance Warehouse Management for Retailers IMG: EWM Material Flow System (MFS) Exception Handling EWM Exceptions Define EWM Exception for PLC Errors Assign EWM exceptions to PLC Assign EWM exception codes to PLC communication errors (e. SAP menu: EWM Master Data Storage Bin Sort Storage Bins Assign storage bins to Assign storage bins to communication points. SAP menu: EWM Master Data Storage Bin Create Storage Bin Create storage bins based on Create storage bins according to storage bin structures for structures storage type 0290 (per aisle).0 D-69190 Walldorf Document Date: August 2010 .g.00: High Performance Warehouse Management for Page Dietmar-Hopp. © 2006 SAP AG SAP EWM 7. communication points SAP menu: EWM Master Data Material Flow System (MFS) Maintain Communication Points Maintain communication to PLCs Maintain communication layer per PLC and specify IP and port to be used per communication channel. Retailers 82 of 113 Allee 16 Version: 1.g.

© 2006 SAP AG SAP EWM 7.2 Scenario Specifications This section is dedicated to the specification of the online scenarios. By means of the LoadRunner transaction. if defined.0 D-69190 Walldorf Document Date: August 2010 . For each process we specify the scenario to which it belongs.00: High Performance Warehouse Management for Page Dietmar-Hopp. Every dialog step is described by a screen shot. and the sequence of dialog steps. excluding the logon to and the logoff from the system (and logon to the resource in case it is an RF transaction). the response times of actions can be exactly traced back to the scenario specification. the input of the script (except user IDs). Retailers 83 of 113 Allee 16 Version: 1. a short description of the action and a LoadRunner transaction (LR-TID). High Performance Warehouse Management for Retailers Table 34: Customizing for MFS Integration 8.

Retailers 84 of 113 Allee 16 Version: 1.0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers 8.1 Inbound Scenario Scenario: Process: INBOUND Create Unload WT and Goods Receipt (IN2) Script Input: ERP document number 1 Action: enter transaction /SCWM/PRDI LR-TID: - 2 Action: select “ERP document”.00: High Performance Warehouse Management for Page Dietmar-Hopp. WTs button LR-TID: IN2_Unload_WTs 5 Action: save LR-TID: IN2_Save 6 Action: press Goods Receipt button LR-TID: IN2_Goods_Receipt 7 In the simultaneous scenario we switched the order for the sake of script simplification: first goods receipt.2. © 2006 SAP AG SAP EWM 7. put in ERP document number and execute LR-TID: IN2_Search_Items 3 Action: select Unload from the menu7 LR-TID: IN2_Menu_Unload 4 Action: press Unload. then creation of unload WTs.

Retailers 85 of 113 Allee 16 Version: 1.00: High Performance Warehouse Management for Page Dietmar-Hopp.0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers Scenario: Process: INBOUND Unloading (IN3) Script Input: ASN (Advanced Shipping Notification) ID related HU numbers 1 Action: select 03 in the menu LR-TID: - 2 Action: select 01 in the menu LR-TID: - 3 Action: select 04 in the menu LR-TID: - 4 Action: enter ASN ID and press <ENTER> twice LR-TID: IN3_ASN_Enter_1 LR-TID: IN3_ASN_Enter_2 5 Action: enter HU number and press <ENTER> twice LR-TID: IN3_HU_Enter_1 LR-TID: IN3_HU_Enter_2 © 2006 SAP AG SAP EWM 7.

0 D-69190 Walldorf Document Date: August 2010 .00: High Performance Warehouse Management for Page Dietmar-Hopp. High Performance Warehouse Management for Retailers 6 Action: copy destination bin and press <ENTER> twice LR-TID: IN3_DestBin_Enter_1 LR-TID: IN3_DestBin_Enter_2 7 If there are more HUs to enter go to previous screen else: 8 Action: press the Yes button LR-TID: IN3_Unloading_Completed Scenario: Process: INBOUND Put away (IN4) Script Input: HU numbers 1 Action: select 03 in the menu LR-TID: - 2 Action: select 01 in the menu LR-TID: - © 2006 SAP AG SAP EWM 7. Retailers 86 of 113 Allee 16 Version: 1.

High Performance Warehouse Management for Retailers 3 Action: select 01 in the menu LR-TID: - 4 Action: enter HU number and press <ENTER> twice LR-TID: IN4_HU_RSC_Enter_1 LR-TID: IN4_HU_RSC_Enter_2 5 Action: copy HU. Retailers 87 of 113 Allee 16 Version: 1.0 D-69190 Walldorf Document Date: August 2010 . HU and press <ENTER> twice LR-TID: IN4_IP_PUT_1 LR-TID: IN4_IP_PUT_2 if there are more HUs then go to previous screen (5) © 2006 SAP AG SAP EWM 7. dest.00: High Performance Warehouse Management for Page Dietmar-Hopp. bin and dest.

0 D-69190 Walldorf Document Date: August 2010 .2. High Performance Warehouse Management for Retailers 8.00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 88 of 113 Allee 16 Version: 1. put in wave interval and wave template (91) and press execute LR-TID: OB2A_Execute_1 © 2006 SAP AG SAP EWM 7.2 Outbound Scenario Scenario: Process: OUTBOUND Create Replenishment WTs (OB2A) Script Input: Wave interval 1 Action: enter transaction /SCWM/REPL. choose “Order- Rel. Replenishment”.

0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers 2 Action: select all and press execute LR-TID: OB2A_Execute_2 Scenario: Process: OUTBOUND Replenish (OB2B) Script Input: None because process is system-guided 1 Action: select 01 in the menu LR-TID: - 2 Action: select 01 in the menu LR-TID: - 3 Action: press F4 button LR-TID: OB2B_Press_F4 © 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 89 of 113 Allee 16 Version: 1.

High Performance Warehouse Management for Retailers 4 Action: copy data and <enter> LR-TID: OB2B_Conf_Src_HU 5 Action: copy data and <enter> LR-TID: OB2B_Conf_Dest_Bin repeat 4-5 until all WTs are processed © 2006 SAP AG SAP EWM 7.0 D-69190 Walldorf Document Date: August 2010 .00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 90 of 113 Allee 16 Version: 1.

High Performance Warehouse Management for Retailers Scenario: Process: OUTBOUND Create TU (OB2C) Script Input: TU names ODOs per TU doors per TU 1 Action: enter transaction /SCWM/TU and press the create button LR-TID: - 2 Action: enter TU details and confirm LR-TID: OB2C_Press_Create 3 Action: save LR-TID: OB2C_Save_1 4 Action: press “Assign Del.00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 91 of 113 Allee 16 Version: 1.” LR-TID: - 5 Action: assign ODOs and execute LR-TID: OB2C_Assign_ODOs_TU © 2006 SAP AG SAP EWM 7. Immed.0 D-69190 Walldorf Document Date: August 2010 .

0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers 6 Action: save LR-TID: OB2C_Save_2 7 Action: press “Assigned Doors” tab LR-TID: - 8 Action: enter door details and confirm LR-TID: OB2C_Assign_TU_Door 9 Action: save LR-TID: OB2C_Save_3 © 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 92 of 113 Allee 16 Version: 1.

Retailers 93 of 113 Allee 16 Version: 1. High Performance Warehouse Management for Retailers Scenario: Process: OUTBOUND Release Wave (OB3A) Script Input: - 1 Action: enter transaction /SCWM/MON and select Outbound Documents Wave LR-TID: - 2 Action: enter current date and status=I (initial) and execute LR-TID: - 3 Action: select first wave of the list and choose release wave LR-TID: - 4 Action: confirm pop-up LR-TID: OB3A_Release_Wave 5 Action: confirm success message LR-TID: - © 2006 SAP AG SAP EWM 7.0 D-69190 Walldorf Document Date: August 2010 .00: High Performance Warehouse Management for Page Dietmar-Hopp.

i.0 D-69190 Walldorf Document Date: August 2010 . Retailers 94 of 113 Allee 16 Version: 1. HUs with 25 items each © 2006 SAP AG SAP EWM 7.e. High Performance Warehouse Management for Retailers Scenario: Process: OUTBOUND Picking and Staging (OB3B) Script Input: None because process is system-guided 1 Action: select 01 in the menu LR-TID: - 2 Action: select 01 in the menu LR-TID: - 3 Action: choose F4 LR-TID: OB_Srce_HU_1 4 Action: copy data into text fields (= scan simulation) and press <enter> LR-TID: OB_Srce_HU_2 Repeat last step (4) as long as there are source Hus. fill 2 dest.00: High Performance Warehouse Management for Page Dietmar-Hopp.

High Performance Warehouse Management for Retailers 5 Action: copy data into text fields (= scan simulation) and press <enter> LR-TID: OB_Dest_Bin Action: press <enter> again LR-TID: OB_DestBin_Confirm Repeat last step (5) as long as there are dest. Retailers 95 of 113 Allee 16 Version: 1.00: High Performance Warehouse Management for Page Dietmar-Hopp.0 D-69190 Walldorf Document Date: August 2010 . otherwise: 6 Action: log out LR-TID: - © 2006 SAP AG SAP EWM 7. HUs The system will jump back to 3 if there are still WOs left for the resource.

High Performance Warehouse Management
for Retailers

Scenario: Process:
OUTBOUND Check-in TU and Dock to
Door (OB3C)
Script Input:
- TU names
- doors per TU
1 Action: enter transaction
/SCWM/TU and search for TU
LR-TID: OB3C_TU_Search

2 Action: select
Action Checkpoint
Arrival+Save from the menu
LR-TID:
OB3C_CheckPoint_Arrival_Save

3 Action: select Action Door
Arrival at Door from the menu
LR-TID:
OB3C_Door_Arrival_Door

4 Action: save
LR-TID: OB3C_Save_4

© 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page
Dietmar-Hopp- Retailers 96 of 113
Allee 16 Version: 1.0
D-69190 Walldorf Document Date: August 2010

High Performance Warehouse Management
for Retailers

Scenario: Process:
OUTBOUND Loading (OB3D)
Script Input:
- TU names
- HUs per TU
1 Action: select 04 from the menu
LR-TID: -

2 Action: select 03 from the menu
LR-TID: -

3 Action: select 03 from the menu
LR-TID: -

4 Action: enter TU (= scan
simulation) and press <enter>
LR-TID: OB3D_TU_1
Action: press <enter> again
LR-TID: OB3D_TU_2
Action: press <enter> again
LR-TID: OB3D_TU_3
5 Action: enter HU (= scan
simulation) and press <enter>
LR-TID: OB3D_HU_1
Action: press <enter> again
LR-TID: OB3D_HU_2

© 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page
Dietmar-Hopp- Retailers 97 of 113
Allee 16 Version: 1.0
D-69190 Walldorf Document Date: August 2010

High Performance Warehouse Management
for Retailers

6 Action: copy DstBin (= scan
simulation) and press <enter>
LR-TID:
OB3D_Conf_Dest_Bin_1
Action: press <enter> again
LR-TID:
OB3D_Conf_Dest_Bin_2

If there are more HUs, go to 5
7 Action: press <yes>
LR-TID: OB3D_Conf_TU_loaded

© 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page
Dietmar-Hopp- Retailers 98 of 113
Allee 16 Version: 1.0
D-69190 Walldorf Document Date: August 2010

High Performance Warehouse Management for Retailers Scenario: Process: OUTBOUND Create ODs (OB3E) Script Input: .00: High Performance Warehouse Management for Page Dietmar-Hopp. TU names 1 Action: enter transaction /SCWM/TU and search TU LR-TID: OB3E_TU_Search 2 Action: press <check> button LR-TID: OB3E_Check 3 Action: select Transportation Unit Generate Outbound Delivery for TU LR-TID: OB3E_Generate_OD 4 Action: save LR-TID: OB3E_Save_1 © 2006 SAP AG SAP EWM 7. Retailers 99 of 113 Allee 16 Version: 1.0 D-69190 Walldorf Document Date: August 2010 .

TU names 1 Action: enter transaction /SCWM/TU and search TU LR-TID: OB3F_TU_Search 2 Action: press the <Goods Issue> button LR-TID: OB3F_GoodsIssue 3 Action: choose Action Door Departure from Door LR-TID: OB3F_DepartureFromDoor 4 Action: save LR-TID: OB3F_Save_1 5 Action: choose Action Checkpoint Departure +Save LR-TID: OB3F_DepartureAndSave 6 Action: save LR-TID: OB3F_Save_2 © 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 100 of 113 Allee 16 Version: 1. High Performance Warehouse Management for Retailers Scenario: Process: OUTBOUND Goods Issue and Departure (OB3F) Script Input: .0 D-69190 Walldorf Document Date: August 2010 .

Check-in TU and Dock to Door (CD3) Script Input: .00: High Performance Warehouse Management for Page Dietmar-Hopp.2. Retailers 101 of 113 Allee 16 Version: 1. doors per TU 1 Action: enter transaction /SCWM/TU and press the create button 2 CD3_Press_Create = OB2C_Press_Create 3 CD3_Save_1 = OB2C_Save_1 4 CD3_Assign_ODOs_TU = OB2C_Assign_ODOs_TU 5 CD3_Save_2 = OB2C_Save_2 6 CD3_Assign_TU_Door = OB2C_Assign_TU_Door 7 CD3_Save_3 = OB2C_Save_3 8 CD3_CheckPoint_Arrival_Save = OB3C_CheckPoint_Arrival_Save © 2006 SAP AG SAP EWM 7.0 D-69190 Walldorf Document Date: August 2010 . TU names . High Performance Warehouse Management for Retailers 8.3 Cross-Docking Scenario: Process: CROSS DOCKING Create Unload WT and Goods Receipt (CD2) Script Input: ERP document number 1 Action: enter transaction /SCWM/PRDI LR-TID: - 2 CD2_Search_Items = IN2_Search_Items 3 CD2_Menu_Unload = IN2_Menu_Unload 4 CD2_Unload_WTs = IN2_Unload_WTs 5 CD2_Save = IN2_Save 6 CD2_Goods_Receipt = IN2_Goods_Receipt Scenario: Process: CROSS DOCKING Create TU.

0 D-69190 Walldorf Document Date: August 2010 . scenario IN3) - 3 4 CD4_ASN_Enter_1 = IN3_ASN_Enter_1 CD4_ASN_Enter_2 = IN3_ASN_Enter_2 5 CD4_HU_Enter_1 = IN3_HU_Enter_1 CD4_HU_Enter_2 = IN3_HU_Enter_2 6 CD4_DestBin_Enter_1 = IN3_DestBin_Enter_1 CD4_DestBin_Enter_2 = IN3_DestBin_Enter_2 7 Confirm if unloading is complete Scenario: Process: CROSS DOCKING Picking (CD5) Script Input: None (because process is system-guided) 1 Action: select 01 from the menu LR-TID: - © 2006 SAP AG SAP EWM 7. Retailers 102 of 113 Allee 16 Version: 1. High Performance Warehouse Management for Retailers 9 CD3_Door_Arrival_Door = OB3C_Door_Arrival_Door Scenario: Process: CROSS DOCKING Unloading (CD4) Script Input: ASN (Advanced Shipping Notification) ID related HU numbers 1 In RF menu navigate to “Unloading by ASN” (cf.00: High Performance Warehouse Management for Page Dietmar-Hopp.

00: High Performance Warehouse Management for Page Dietmar-Hopp. scenario OB3D) - 3 4 CD6_TU_1 = OB3D_TU_1 CD6_TU_2 = OB3D_TU_2 CD6_TU_3 = OB3D_TU_3 5 CD6_HU_1 = OB3D_HU_1 CD6_HU_2 = OB3D_HU_2 6 CD6_Conf_Dest_Bin_1 = OB3D_Conf_Dest_Bin_1 © 2006 SAP AG SAP EWM 7. Retailers 103 of 113 Allee 16 Version: 1. High Performance Warehouse Management for Retailers 2 Action: select 02 from the menu LR-TID: - 3 Action: enter queue and confirm (<enter>) LR-TID: - 4 Action: copy source HU (= scan simulation) and press <enter> LR-TID: CD5_Src_HU_Enter1 Action: press <enter> again LR-TID: CD5_Src_HU_Enter2 5 Action: copy dest. bin and HU (= scan simulation) and press <enter> LR-TID: CD5_Dest_HU_Enter1 Action: press <enter> again LR-TID: CD5_Dest_HU_Enter2 Repeat 5 until all HUs are picked Scenario: Process: CROSS DOCKING Loading (CD6) Script Input: .0 D-69190 Walldorf Document Date: August 2010 . TU names . HUs per TU 1 Navigate to “Loading by Transport Unit” (cf.

High Performance Warehouse Management for Retailers CD6_Conf_Dest_Bin_2 = OB3D_Conf_Dest_Bin_2 If there are more HUs. Retailers 104 of 113 Allee 16 Version: 1. go to 5 7 CD6_Conf_TU_loaded = OB3D_Conf_TU_loaded © 2006 SAP AG SAP EWM 7.0 D-69190 Walldorf Document Date: August 2010 .00: High Performance Warehouse Management for Page Dietmar-Hopp.

2. Goods Issue. Departure (CD7) Script Input: . High Performance Warehouse Management for Retailers Scenario: Process: CROSS DOCKING Create ODs. TU names 1 CD7_TU_Search = OB3E_TU_Search 2 CD7_Check = OB3E_Check 3 CD7_Generate_OD = OB3E_Generate_OD 4 CD7_Save_1 = OB3E_Save_1 5 CD7_GoodsIssue = OB3F_GoodsIssue 6 CD7_DepartureFromDoor = OB3F_DepartureFromDoor 7 CD7_Save_2 7 CD7_DepartureAndSave = OB3F_DepartureAndSave 8 CD7_Save_3 8.00: High Performance Warehouse Management for Page Dietmar-Hopp.4 Flow Through Scenario: Process: FLOW THROUGH Create Unload WT and Goods Receipt (FT2) Script Input: ERP document number 1 Action: enter transaction /SCWM/PRDI LR-TID: - 2 FT2_Search_Items = IN2_Search_Items 3 FT2_Menu_Unload = IN2_Menu_Unload 4 FT2_Unload_WTs = IN2_Unload_WTs 5 FT2_Save = IN2_Save 6 FT2_Goods_Receipt = IN2_Goods_Receipt © 2006 SAP AG SAP EWM 7.0 D-69190 Walldorf Document Date: August 2010 . Retailers 105 of 113 Allee 16 Version: 1.

TU names . List of 400 consolidation groups (1 per HU to be created) 1 Action: select 04 from the menu LR-TID: - © 2006 SAP AG SAP EWM 7. Check-in TU and Dock to Door (FT3) Script Input: . High Performance Warehouse Management for Retailers Scenario: Process: FLOW THROUGH Create TU.0 D-69190 Walldorf Document Date: August 2010 . doors per TU 1 Action: enter transaction /SCWM/TU and press the create button LR-TID: - 2 FT3_Press_Create = OB2C_Press_Create 3 FT3_Save_1 = OB2C_Save_1 4 FT3_Assign_ODOs_TU = OB2C_Assign_ODOs_TU 5 FT3_Save_2 = OB2C_Save_2 6 FT3_Assign_TU_Door = OB2C_Assign_TU_Door 7 FT3_Save_3 = OB2C_Save_3 8 FT3_CheckPoint_Arrival_Save = OB3C_CheckPoint_Arrival_Save 9 FT3_Door_Arrival_Door = OB3C_Door_Arrival_Door Scenario: Process: FLOW THOUGH Create Destination HUs (CD4) Script Input: . Retailers 106 of 113 Allee 16 Version: 1.00: High Performance Warehouse Management for Page Dietmar-Hopp.

Retailers 107 of 113 Allee 16 Version: 1.00: High Performance Warehouse Management for Page Dietmar-Hopp. High Performance Warehouse Management for Retailers 2 Action: select 04 from the menu LR-TID: - 3 Action: select 02 from the menu LR-TID: - 4 Action: put in work center (FTPD) and press <enter> LR-TID: - 5 Action: put in packing material (122). then save LR-TID: FT4_Save_HU 6 Goto 3 if there are still HUs to be created © 2006 SAP AG SAP EWM 7. the destination bin (FTPD- OUTB-001) and the consolidation group.0 D-69190 Walldorf Document Date: August 2010 .

scenario IN3) - 3 4 FT5_ASN_Enter_1 = IN3_ASN_Enter_1 FT5_ASN_Enter_2 = IN3_ASN_Enter_2 5 FT5_HU_Enter_1 = IN3_HU_Enter_1 FT5_HU_Enter_2 = IN3_HU_Enter_2 6 FT5_DestBin_Enter_1 = IN3_DestBin_Enter_1 FT5_DestBin_Enter_2 = IN3_DestBin_Enter_2 7 Confirm if unloading is complete Scenario: Process: FLOW THOUGH Put away to DECONS station (FT6) Script Input: HU numbers 1 Navigate to “Putaway by HU” (cf. IN4) - 3 4 FT6_HU_Enter_1 = IN4_HU_RSC_Enter_1 FT6_HU_Enter_2 = IN4_HU_RSC_Enter_2 5 FT6_IP_PUT_1 = IN4_IP_PUT_1 FT6_IP_PUT_2 = IN4_IP_PUT_2 if there are more HUs then go to previous screen (5) © 2006 SAP AG SAP EWM 7.00: High Performance Warehouse Management for Page Dietmar-Hopp. Retailers 108 of 113 Allee 16 Version: 1.0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers Scenario: Process: FLOW THROUGH Unloading (FT5) Script Input: ASN (Advanced Shipping Notification) ID related HU numbers 1 In RF menu navigate to “Unloading by ASN” (cf.

00: High Performance Warehouse Management for Page Dietmar-Hopp. High Performance Warehouse Management for Retailers Scenario: Process: FLOW THOUGH Release Wave (FT7) Script Input: Wave number 1 Navigate to “Putaway by HU” (cf. Retailers 109 of 113 Allee 16 Version: 1. IN4) Action: enter transaction /SCWM/MON and select wave LR-TID: - 2 FT7_Release_Wave = OB3A_Release_Wave 3 Confirm success message Scenario: Process: FLOW THOUGH Picking (FT8) Script Input: HU numbers 1 Action: select 04 from the menu LR-TID: - 2 Action: select 04 from the menu LR-TID: - 3 Action: select 03 from the menu LR-TID: - © 2006 SAP AG SAP EWM 7.0 D-69190 Walldorf Document Date: August 2010 .

High Performance Warehouse Management for Retailers 4 Action: put in work center (FTPD) and press <enter> twice LR-TID: - 5 Action: put in source HU (= scan simulation) and press <enter> LR-TID: FT8_SRC_HU_1 Action: press <enter> again LR-TID: FT8_SRC_HU_2 6 Action: copy data (= scan simulation) and press <enter> LR-TID: FT8_Target_HU 7 Goto 5 if there are still HUs to be picked Scenario: Process: FLOW THOUGH Picking (FT8b) Script Input: HU numbers 1 Action: select 04 from the menu LR-TID: - 2 Action: select 04 from the menu LR-TID: - © 2006 SAP AG SAP EWM 7.0 D-69190 Walldorf Document Date: August 2010 . Retailers 110 of 113 Allee 16 Version: 1.00: High Performance Warehouse Management for Page Dietmar-Hopp.

0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers 3 Action: select 04 from the menu LR-TID: - 4 Action: put in work center (FTPD) and press <enter> twice LR-TID: - 5 Action: put in HU (= scan simulation) and press <enter> LR-TID: FT8b_Close_HU_1 Action: press <enter> again LR-TID: FT8b_Close_HU_2 6 Goto 5 if there are still HUs to be closed Scenario: Process: FLOW THOUGH Staging (FT9) Script Input: HU numbers 1 Action: select 02 from the menu LR-TID: - 2 Action: select 02 from the menu LR-TID: - © 2006 SAP AG SAP EWM 7. Retailers 111 of 113 Allee 16 Version: 1.00: High Performance Warehouse Management for Page Dietmar-Hopp.

go to 5 7 FT10_Conf_TU_loaded = OB3D_Conf_TU_loaded © 2006 SAP AG SAP EWM 7. Retailers 112 of 113 Allee 16 Version: 1. High Performance Warehouse Management for Retailers 3 Action: put in HU and press <enter> LR-TID: FT9_HU_1 Action: press <enter> LR-TID: FT9_HU_2 4 Action: copy data (= scan simulation) and press <enter> LR-TID: FT9_Conf_Src_Bin_1 Action: press <enter> LR-TID: FT9_Conf_Src_Bin_2 5 Action: copy data (= scan simulation) and press <enter> LR-TID: FT_Conf_Dest_Bin_1 Action: press <enter> LR-TID: FT_Conf_Dest_Bin_2 6 Goto 3 if there are still HUs to be staged Scenario: Process: FLOW THROUGH Loading (FT10) Script Input: .00: High Performance Warehouse Management for Page Dietmar-Hopp. HUs per TU 1 Navigate to “Loading by Transport Unit” (cf.0 D-69190 Walldorf Document Date: August 2010 . TU names . scenario OB3D) - 3 4 FT10_TU_1 = OB3D_TU_1 FT10_TU_2 = OB3D_TU_2 FT10_TU_3 = OB3D_TU_3 5 FT10_HU_1 = OB3D_HU_1 FT10_HU_2 = OB3D_HU_2 6 FT10_Conf_Dest_Bin_1 = OB3D_Conf_Dest_Bin_1 FT10_Conf_Dest_Bin_2 = OB3D_Conf_Dest_Bin_2 If there are more HUs.

TU names 1 FT11_TU_Search = OB3E_TU_Search 2 FT11_Check = OB3E_Check 3 FT11_Generate_OD = OB3E_Generate_OD 4 FT11_Save_1 = OB3E_Save_1 5 FT11_GoodsIssue = OB3F_GoodsIssue 6 FT11_DepartureFromDoor = OB3F_DepartureFromDoor 7 FT11_Save_2 7 FT11_DepartureAndSave = OB3F_DepartureAndSave 8 FT11_Save_3 © 2006 SAP AG SAP EWM 7.0 D-69190 Walldorf Document Date: August 2010 . High Performance Warehouse Management for Retailers Scenario: Process: FLOW THROUGH Create ODs. Retailers 113 of 113 Allee 16 Version: 1. Departure (FT11) Script Input: .00: High Performance Warehouse Management for Page Dietmar-Hopp. Goods Issue.