This Live Expert Session provides you a detailed overview of innovations delivered by SAP Extended Warehouse Management 9.1.

Transcription

1 This Live Expert Session provides you a detailed overview of innovations delivered by SAP Extended Warehouse Management 9.1. After a short introduction into EWM 9.1 I will go through each single innovation.describe it while presenting screenshots of typical User Interfaces. Let me start first with the introduction into EWM

2 Major focus of EWM release 9.1 has been Reducing total cost of implementation (TCI) and operation ( TCO) Improve User Experience and Leverage innovations by taking advantage of new SAP technologies like mobile SAPUI5 and the super fast in memory database technology SAP HANA. Highlights in terms of new functionalities are The Shipping Cockpit setting a new standard for user experience in EWM Dock Appointment Scheduling with major functional enhancements Labor Demand Planning a HANA based mobile as well as desktop application at the cutting edge of technology and user experience Let me begin with showing and explaining some details for the Shipping Cockpit....The Shipping Cockpit supports the shipping office clerk in his daily activities such as building transportation units, assigning doors, managing the arrival, loading and departure of trucks, printing waybills and posting goods issue. The Shipping Cockpit is a user-centric User Interface designed especially for the shipping office clerk. One major aspect of the cockpit is the user experience for the shipping office clerk, for example reducing navigation by presenting all information needed for one action on one screen, offering personalization options and providing automatisms or mass data processing for tedious manual steps whenever possible in order to meet the expectations on user experience as much as possible our development team went out to out customers, to end users and SAP EWM implementation partners in order to review concepts and mock ups. the result is has been two dedicated user interfaces for a shipping office clerk that gives him all tools and visibility what he needs in order to complete his tasks super efficiently. One desktop based user interface for planning the outbound deliveries from the warehouse and one desktop based User Interface for monitoring the execution of the plan in the warehouse. 2

3 4

4 Let me first show you a screenshot of the planning view. The Planning View contains four major areas The search area for selecting the personal and current planning workload of the shipping office clerk The list of outbound delivery orders (ODO) on the left and its details on the bottom The list of transportation units (TUs) in the middle and its details on the bottom and The Side Panel with context information on the right e.g. as displayed on the screenshot the weight and volume capacity consumption of a transportation unit. Let me explain the shipping cockpit by telling the story of our imaginary shipping office clerk Sarah. Sarah uses the shipping cockpit during her daily work for planning, execution and monitoring. In the morning, Sarah begins with the Outbound Planning. She selects all due outbound delivery orders for the afternoon of the next day. She selects all ODOs of a route and asks the system for a TU proposal based on weight or volume. The selected ODOs are automatically assigned to the new TUs. In case a carrier works regularly on the route, the system automatically proposes the carrier, the time slot and the door for the TU creation. In case there is no regular carrier for the route, Sarah searches for a carrier for the route. She contacts the carrier and communicates the route as well as the total loading weight/volume. She agrees with the carrier on a time slot by checking the free doors on a time axis. She then enters the carrier, the door and the time slot in the TU or as I will show two slides later creates a loading appointment using the integration of the shipping cockpit planning view with Dock Appointment Scheduling). The staging area is determined automatically from the door. Once she has assigned all due ODOs to TUs, either she triggers the creation of a wave for a TU, or waves are created automatically based on wave templates. If a last minute ODO appears in her cockpit, she assigns it manually to the TU created for the appropriate route. The last minute ODO is added automatically to the wave. Before the picking begins in the warehouse, the wave is released automatically. This is the last step of the Outbound Planning. With the wave release, the picking warehouse tasks and warehouse orders are created by the system and the picking can begin in the warehouse. In the afternoon, Sarah switches from the Outbound Planning view to the Outbound Execution view. 6

5 Sarah checks the progress of the warehouse activities like picking, packing and staging in the warehouse for each TU in order to react to delays in a timely manner (for example, contact the warehouse manager or un-assign a delivery if it cannot be staged in time) by the green and red traffic lights the status of the single activities is visualized When a truck arrives, Sarah directs the truck driver to the planned door and sets the TU status to arrival at door. If necessary, she adds information to the TU, for example the tare weight of the truck or the contact information for the truck driver. When the loading is finished, either the loading end is set automatically with the loading of the last HU, or the truck driver parks the truck and comes back to Sarah, who then sets the loading end and departure from door. Sarah prints the delivery and transport documents and hand them over to the truck driver. In case of an export, she additionally triggers the printing of a pro forma invoice in ERP. When the truck driver leaves, Sarah posts the GI and sets the TU status to departure from checkpoint. 7

6 Dock Appointment Scheduling is a collaborative planning tool for loading/unloading appointments at a warehouse between the warehouse operator and its carriers. Let me go shortly back to the planning view and show you how Dock Appointment Scheduling is integrated into the Shipping Cockpit Planning view. Before we have seen the delivery list in the shipping cockpit planning view while our Shipping Office clerk Sarah did the planning. When Sarah is aligning loading appointments with a carrier she uses the capacity list that gives Sarah an overview of free capacity or free time slots for loading appointments at the warehouses loading points (group of doors) With creating a TU also automatically in the background a rough appointment in the Dock Appointment Scheduling application is generated that Sarah will update after aligning the exact loading times with the carrier. Sarah just needs to click on the appointment for the TU in order to navigate to the planning view in Dock Appointment Scheduling. 8

7 9

8 In the upper part of the screen Sarah enters information on the appointment like appointment length, product group, reference documents, carrier etc. There is also a free text field for comments. In the lower part there is the capacity view. The current appointment is displayed as red bar on the horizontal time axis. The vertical bars visualize the already consumed loading capacity. The thin red line on top marks the capacity limit Looking at the capacity overview Sarah can easily detect if there is sufficient loading capacity available for the currently planned appointment time or if she needs to shift the appointment to another date or time Shifting the appointment just works by dragging & dropping the red bar to a time window with sufficient available loading capacity. For those of you who are familiar with the 9.0 version of Dock Appointment Scheduling you probably see that the planning view has been completely changed. The change in the user interfaces goes hand in hand with major enhancements that have been added to Dock Appointment Scheduling compared to the former version like the possibility to maintain appointments with variable length. With variable length of the appointments came the need to change the 9.0 user interface design. A second major improvement is the automatic loading point determination or appointment length calculation based on reference documents or product groups as well as analytic reporting functionalities. 11

9 The current slide shows the monitoring screen for the appointments at a docking location. That is a group of loading points. In the displayed example there are loading points for Beverages Frozen goods and Fruit & vegetables. Please note the variable length of the displayed appointments. A major enhancement compared to the previous version of Dock Appointment Scheduling. Color coded you see the status of each appointment like - Planned appointment - Arrived in yard - Docked at door - Undocked from door - Out of yard 12

10 Let me give you a short glimpse on the added analytic reporting for the appointments. The screenshot shows you a list of appointments grouped by loading point and carrier. The reporting shows visually in green and red color which appointment has been in time and which has been late. The reporting itself can be configured e.g. by defining thresholds for deviation resulting to a red color and so on. Goal of the reporting is to monitor the reliability of carriers and to support during demurrage discussions. 13

11 Labor demand Planning requires EWM running on HANA as a primary database. For deployment options of Labor damand planning see also SAP notes ( and ( 14

12 16

13 Displayed is the Labor Demand planning view Our shift manager let me call him John selects in the morning the date and the view i.e. activities and activity areas he is interested in. The bar chart shows John for each hour today ( see the horizontal time axis ) how many warehouse workers he needs in the selected areas (...see the vertical bar heights ). Below the bar chart John gets further context information The depicted pie chart tells John that the workload is calculated based on 60 % already released warehouse tasks and 40% deliveries in the system that are not yet released to the warehouse this is just one example of context data available. Now you probably ask yourself: Is it difficult to set up Labor Demand Planning? Not at all Just few simple settings are needed. Especially there is no need to set up elaborate Engineered Labor Standards as Labor Demand Planning just uses historical data in the system to learn about durations warehouse tasks. Main message: Labor demand Planning A very intuitive application helping John to efficiently plan his workers to activities. 17

14 Using a self learning algorithm Labor Demand Planning determines the duration of warehouse tasks based on historical data in the system. First already completed warehouse task of the last week or month are selected. Then similar tasks e.g. picking of pallets in a certain activity area or picking of cases in another activity area or packing at packing work center are selected. In the next step the selected historical data of similar warehouse tasks is check for outlier in the duration. The algorithm excludes any outliers. Finally the average duration of the warehouse task is calculated for similar warehouse tasks. The result is then taken in order to calculate the workload of current warehouse tasks in the system. 18

15 A valuable and remarkable feature of Labor Demand Planning is its capability to forecast workload. The forecast again is based on historical data in the system. The historical data gets cleaned from outliers. The forecasting functionality extracts week patterns e.g. in the depiced example the workload on Monday and Friday is lower than on Wednesday or trends into the future e.g. for the next week. The depiced trend examples shows a continuous increasing workload in the next 5 weeks. 19

16 20

17 One of SAPs strategic goals is to deliver the Supply Chain Execution platform a real-time, seamless end-to-end integrated platform for planning, execution and monitoring of physical goods movements. A major milestone in the strategy is the direct end-to-end integration of SAP Transportation Management with EWM. While in the last release 9.0 the integration between TM and EWM has been based on the ERP shipment document and therefore has only been possible via ERP acting as middleware now in release 9.1 having a direct communication channel between the TM Freight Order and the EWM Transportation Unit a tighter master data and configuration integration and simplified system landscape is achieved leading to a lower cost of implementation und due to reduced complexity also lower total cost of operation. Note: the direct TM-EWM integration is done via web services a) Via a Process Integration (PI) system b) Or direct point-to-point integration using Web Service reliable messaging (WS/RM). See SAP note for more details ( 21

18 Let me shortly explain you a typical integrated TM / EWM outbound process: Sales orders or deliveries are created in the ERP system. Based on sales orders or deliveries transportation management plans transportation. The transportation plan is reflected in the Freight Order From the Freight Order a loading plan is transferred to the EWM system In EWM based on the transferred loading plan a transportation unit with assigned corresponding deliveries is created. Picking, packing, staging and loading is executed in the warehouse in EWM. Once goods issue is posted EWM transfers back to SAP TM what has been physically loaded on the TU. Deviations like planned goods that haven t been loaded because they didn t fit anymore on the transportation unit are recognized by TM as deviation and will go back into the transportation planning backlog of the transportation planner. Therefore a real business benefits is achieved by the direct TM / EWM integration as it provides transparency to the transportation planner in realtime about deviations from the loading plan and directly puts the re-planning work back in his personal work list leading to efficiency gains. Also the invoice verifier benefits from the integration as EWM communicates back to TM what has physically been loaded to the TU and therefore what has been indeed transported when leaving the warehouse leading to more accurate Freight settlements. 22

19 Another milestone in reducing total cost of implementation is an enhanced integration of SAP ERP Quality Management with the logistic processes in EWM. The goal is: simply connect EWM to ERP without loosing important functionality of ERP QM. Keep the effort to setup EWM QM as small as possible. This slide shows you as puzzle pieces at which points in the process improvements have been done. Let me start with puzzle No. 1:.. up to now in EWM an inspection document is created for every inbound delivery item... With the enhancement delivered now you are able to collect goods receipt from different inbound deliveries into one inspection document This means you have only one ECC inspection lot when receiving multiple pallets of the same material / batch (SAP note ). The second puzzle: before a usage decision couldn t be done on partial quantities in the integrated ERP QM / EWM process. Now with release 9.1 you are able to navigate to EWM stock and decide partial quantities in EWM (SAP note ). Your are now able to process the decision based on selected handling units and partial quantities. Third puzzle: EWM now considers calculated sample quantities (SAP note ). Fourth piece: Mass creation of inspection for stock in the warehouse (SAP note ) can be now done using the warehouse monitor. The typical use case is:... shelflife will expire in 10 days or next inspection date of batch is reached; manual selection And last not least the fifth puzzle piece: Visibility on EWM stock in inspection for Materials Requirements Planning (MRP)/ ATP runs in SAP ERP (SAP note and ) is achieved. Note: all these ERP QM / EWM enhancements have been down ported to EWM 9.0 and ERPP 6.0 EhP6 via SAP note. Please read SAP note for activating the new EWM QM functional after upgrade to EWM 9.1 or after having installed EWM 9.0 SP6. 23

20 In order to make this process more efficient the monitoring of the interface between SAP ERP and EWM has been simplified and included into the warehouse monitor in order to make it easy for business users to understand and resolve the issue. Key improvements are Enable message selection specific for user roles e.g. grouping error types for specific users Enable filtering by warehouse No. Display meaningful information like document no. You see on the displayed screenshot some examples delivery No., Appointment No. etc Moving the message queue monitoring of the SAP ERP / EWM interface to the warehouse monitor is just one enhancement of the monitor. In EWM 9.1 we did much more enhancements in the monitor 24

21 Further enhancements have been done in the warehouse monitor that improve the usability and productivity for the users. On the current slide you see the complete list of enhancements in the warehouse monitor. I just will explain the first one Create snapshot of monitor query data. In case your query needs to read a lot of data from the data base it might take quite same time until the query displays the results. By the new snapshot functionality your now able to plan your query in as background task e.g. in the evening for the next morning so that when you arrive in the office the next day the query has already been executed. You just need to check the result in the stored snapshot which will be displayed in sub-seconds. The other enhancements are mention on the slides. 25

22 In order to reduce total cost of implementation and operation we also enhanced technical documentation e.g. context help (F1 help), BAdI documentation and cookbooks How to use PPF in EWM How to Add Application Content to the Warehouse Management Monitor Furthermore process descriptions, configuration guides and process test cases will be published in the solution manager content for the new processes Dock Appointment Scheduling Labor Demand Planning and Integrating Warehousing and Transportation (Direct SAP TM-EWM integration) 26

23 You will find the cookbooks ( and the solution manager content links once available on the official SAP EWM SAP Community Network (SCN) page you will find there furthermore Blogs, Discussion and News 27

24 28

25 29

26 30

27 31

28 In January 2013 there has been introduced a new focused business solution SAP Extended Warehouse Management for Fashion ( Furthermore SAP Rapid Deployment System for Retail for EWM has been released ( In EWM 9.1 we added the functionality to automatically add packaging items to the outbound delivery for goods issue. This supports customers to keep track over packaging material stock. For sure the functionality is not an exclusive Retail enhancement but can be used in other industries as well. 32

29 Let me quickly give you an example how the automatic packaging item for goods issue works. An Outbound Delivery Order 4711 with two items 7 Tablet-PCs and 7 Monitors is packed on pallets as following: You pack a carton of 5 tablets together with 2 tablets in another carton on one Euro-Pallet. 7 Monitors are packed onto a second Euro-Pallet. When posting goods issue the packaging materials... 2 Euro-Pallet in our example... are added to the Outbound Delivery Order and resulting Outbound Delivery as additional item.

30 34

31 Now let me summarize the key take away for the EWM 9.1 Live Expert Session. SAP Extended Warehouse Management comes with 9.1 in its 7 th release on the market. With consequently and continuously improving and enhanceing the solution over multiple years and releases we consider EWM as a complete and mature solution Also proven by over 500 customers productively using SAP EWM in their daily operations And still EWM has a strong growing customer base having in 2012 doubled the number of customers encouraging SAP further in developing SAP EWM to a market leading solution. This means our SAP EWM development team has on multi-year development roadmap. With a clear focus on World-Class User Experience New Innovations like Mobile & HANA while Reducing total cost of implementation and ownership EWM 9.1will be another milestone in the success story of SAP EWM. 35

32 SAP AG. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. 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, if any. Nothing herein should be construed as constituting an additional warranty.