Direct Tm Ewm Integration 1o702j

Speed Demo Short-Script Demo Scenario: Direct TM / EWM Integration Last Updated: February 4, 2014 External Speed Demo URL: http://demo.tdc.sap.com/SpeedDemo/214243b017394703 One paragraph story-line Summary: Learn how transportation planner John manually plans a transport in the operations office. At the warehouse shipping clerk Sarah gets John’s transportation plan displayed in the shipping cockpit as a planned outbound delivery on a transportation unit from the warehouse. Sarah releases the work to the warehouse that is then executed by warehouse worker Mark. At arrival truck driver Mike gets checked into the warehouse and instructed at the trucker desk. Once docked on the warehouse door the truck gets loaded by fork lift driver Mark. The demo shows how the exception of one planned pallet not fitting on the truck is handled and how the transportation planner John in real-time gets informed about the exception and the action to take.

What are the key messages your audience needs to take from this demo? The direct SAP Transportation Management (SAP TM) integration with SAP Extended Warehouse Management (SAP EWM) helps customers to: 1. Reduce cost by optimizing and automating transportation and warehouse processes 2. Achieve high transparency on the execution of transportation plans 3. Align in real-time transportation planning and warehouse execution 4. Reduce costs and improve operational productivity by more accurate freight settlements

Chapter Overviews: Sales Order / Delivery (ERP) Learn how sales orders are entered in an SAP ERP system and consolidated into outbound deliveries. Sales orders and deliveries serve as basic for transportation planning as well as planning the workload in the In the given example a customer CUST032 orders one pallet of product PROD-S01 and one pallet of product PROD-S02.

Transportation Planning (TM) Learn how transportation planner John Smith’s work list and how he does a simple manual transportation planning step Transportation requirements either based on sales orders or on deliveries are displayed in John’s work list. He selects one or more requirements and enters the transportation cockpit. Note: in the demo John selects Original Delivery No. 80000079 with Customer PO No. MK20140122A containing a transportation reuqest for 2 pallets (2 PAL). In the cockpit John assigns manually Freight Units i.e. goods shipped together from one source to one destination location to transportation resources. In this simple example a one stage transport from source to destination location using a truck is planned. The transportation plan is reflected in the resulting Freight Order 6100003155. In the next step John selects a carrier and assigns the carrier to the

Freight order. Once the freight order is ready to be executed John set the Freight Order Item Status to Ready for Loading. By doing so the connected SAP EWM run warehouse will be informed automatically about the transportation plan.

Shipping Planning in Warehouse (EWM) Learn how shipping clerk Sarah uses the Shipping Cockpit for planning the workload in the warehouse Sarah is planning todays shipping workload in the Shipping Cockpit. Transportation planned by SAP TM show up automatically as transportation unit with already assigned deliveries in her planning view. Note that the transportation unit No. 6100003155 matches the corresponding Freight Order No. 6100003155 in the SAP TM system. In order to plan the workload in the warehouse Sarah just creates a wave for the transportation unit. The wave takes care by considering cutoff times that the goods are picked, packed, staged and loaded right in time so that the truck leaves the warehouse on schedule. Sarah is able to navigate from the shipping cockpit to other tools like the warehouse monitor in order to get further detailed information. In the given example she is looking for warehouse orders created by the wave after it has been released.

Picking & Staging Learn how fork lift driver Mark Miller uses his mobile RF based barcode scanning device to pick and stage pallets Mark logs himself on to the mobile device mounted on his fork lift truck. In the given example he manually selects the warehouse order. He picks a pallet with a unique barcode identifier 800000090. Mark confirms that he picked one pallet. He brings the pallet to the staging area and confirms the step by scanning the pallet barcode. Note: The mobile screens are configurable in SAP EWM by the RF framework tool. Customer have flexibility about screen layout and formatting, displayed fields, validations and even screen flow on the mobile device. For more information see the How-to Guides on RF here. The last screenshot shows again Sarah’s desktop computer screen in the shipping office. Displayed is the execution view of the shipping cockpit. The execution view serves to monitor the execution of the planned shipping workload and its status. Visualized by simple traffic lights Sarah can observe the status of the different activities in the warehouse. In the given example after having staged all pallets for delivery 80000079 the Pick and Stage traffic light switches to green.

Warehouse Execution Learn how shipping office clerk Sarah checks in a truck and monitors the loading and checks it out again The truck to pick up the shipment arrives in the warehouse. Truck driver Mike Green first walks to the trucker desk at the shipping office. There he gets from Sarah a warehouse door assigned where to dock on to. Sarah selects the door in the shipping cockpit and assigns it to the transportation unit representing the truck in the system. Mike goes back to his truck, drives to the door and docks his truck to the door. In the meantime fork lift driver Mark got on his mobile device the loading tasks. Mark scans the door ID that uniquely identifies the truck as it is docked to the door. Next Mark scans the label on the pallets (Handling Unit No.) and brings the pallets on the truck. Unfortunately one of the two planned pallets doesn’t fit any more on the truck. Mark is forced to finish loading before having loaded all planned pallets on the truck. This deviation from the plan is depicted in Sarah’s shipping cockpit as yellow triangle that tells her that there is a deviation. When loading is finished Mike goes to the trucker desks to pick up his truck manifest. Sarah closes the TU (transportation unit) which triggers goods issue posting and printing of the truck manifest. She hands the truck papers over to truck driver Mike and checks out the transportation unit. Mike goes to his truck and leaves the warehouse.

Wait…what happens to the pallet that didn’t fit on the truck? See in the next scene how the direct TM / EWM integration handles such an exception situation in real-time.

Update TM Learn how SAP TM gets updated from EWM about the execution in the warehouse Once posting goods issue SAP EWM sends the message to SAP TM what actually has been loaded to the truck and updates the status of the freight Order in TM. In the current case one pallet has been left in the warehouse. You see in the Freight Order 6100003155 that only one of the two planned pallets has been loaded. Please note also the status events with time stamps for Ready for Loading, Arrival, Loading Begin… Now going back into the work list of transportation planner John Smith you see that the original delivery for Customer PO No MK20140122A has been split into two Deliveries. One delivery (No. 80000079) in execution (see Life Cycle Status) that represents the loaded pallet on the truck and another delivery (No. 100000000) with life cycle status “New” that represents the pallet left back in the warehouse and needs to be planned again on a truck by John. You see one of the major business benefits of the direct TM / EWM integration is real-time update of TM after warehouse execution. Status as well as the transportation planners work list gets updated instantly. Another major business benefit (not shown in the demo) derives from real-time updates of what has actually loaded to the transportation unit. TM gets accurate information on transportation unit loads and therefore is able to do precise transportation charge calculation and performs correct invoice verification with the truck carrier based on actual transportation execution.

Copyright 2015 SAP SE. All rights reserved © No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are ed trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or ed trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or ed trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a ed trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are ed trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or ed trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or ed trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a ed trademark of Sun Microsystems, Inc. JavaScript is a ed trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or ed trademarks of SAP AG in and in several other countries all over the world. 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 d 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. These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver “How-to” Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or , please refer to SAP Consulting. Any software coding and/or code lines / strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Services and may not be modified or altered in any way.