Speed Demo Short-Script

Demo Scenario:
Shipping Cockpit and Dock Appointment Scheduling
Last Updated: January 23, 2014
External Speed Demo URL: http://demo.tdc.sap.com/SpeedDemo/b61eb86471fb45bb

One paragraph story-line Summary:

Learn how shipping office clerk Sarah plans the shipping workload in the warehouse and plans appointments
in collaboration with carriers for loading trucks at the warehouse

What are the key messages your audience needs to take from this demo?
SAP Extended Warehouse Management helps customers to:

1. Reduce cost by optimizing and automating warehouse processes

2. Achieve high transparency and ease of use to plan and monitor outbound activities

3. Use embedded analytics to make quick decisions and executive in a single user experience

4. Efficient schedule dock doors and staging areas with easy-to-use graphics

Chapter Overviews:

Shipping Cockpit planning

Learn how to plan your workload to transportation units (TU) e.g. trucks using the shipping cockpit

After having selected the planning workload for today Sarah plans the workload represented as deliveries in the system to
transportation units (TU). Sarah selects the route, customer or deliveries to be planned and if not already available creates TU
representing e.g. a truck to be loaded. Note: Sarah could also plan the deliveries to an existing appropriate TU, if available, just
by dragging and dropping the deliveries to the TU. Remark: For regular routes TUs are created and deliveries are assigned
automatically by scheduling report /SCWM/R_TUDLV_AUTOPLAN_DLV as background job (for more information check here
in the application help).

Dock Appointment Scheduling

Learn how to plan an appointment for loading a transportation unit (TU) in collaboration with your carrier.

When creating a TU the system creates automatically a provisional appointment number. Sarah navigates to the dock
appointment planning form just by clicking on the appointment number. She calls the selected carrier and aligns with him an
appropriate time for loading at the warehouse. The appointment planning screen supports Sarah by displaying graphically the
available capacity at the selected loading point i.e. group of warehouse doors. It helps Sarah to find quickly and reliable the
appropriate time slot for the loading activity.

Staging Area Planning

Learn how to plan and assign a staging area to the transportation unit
Having planned the transportation unit and the appointment for loading now it is time to plan the staging area for staging the
goods. Sarah navigates to the Staging Area Planning tab. Sarah gets graphically displayed the staging areas of the selected
Staging Area Group. The planned loading window aligned during the appointment planning step with the carrier is visually
highlighted in green. Sarah realizes that for staging area STAGE-O02 sufficient capacity is available so she selects the TU and
assigns staging area STAGE-O02 to the TU. At this instant the status traffic light for staging area switches from red to green
meaning the staging area has now been planned.

Side Panel
Learn how to find more context information to support shipping planning in the side panel

Select a transportation unit and click on the Side Panel link in the top right corner of the shipping cockpit. The side panel
opens displaying context information on the selected TU. In the given example the total, open and already consumed i.e.
loaded capacity in weight or volume for the selected transportation unit is displayed in a bar chart. The side panel is a very
valuable visual support for our shipping office clerk Sarah in order to judge if a delivery still fits on the TU or not.

She gets also support for selecting an appropriate carrier. The side panel shows information which carriers operated for the
warehouse in the past on the route and what has been the share. In order to quickly get in touch with the carriers also
telephone No. of the carriers are shown.

Furthermore you get context information again visually on the share of workload already planned versus to be planned
workload (ODOs planned vs. to be planned - in the given example we are fine 100% of workload is planned).

Wave Creation and Warehouse Execution

Learn how to release the planned workload to the warehouse workers in the warehouse for execution.

Sarah selects the TUs (in the given example she selects all TUs displayed in the shipping cockpit), clicks on "create Waves" and
selects automatic wave creation determined by TU. For each TU a wave will be created that takes care that the work packages
are assigned to warehouse workers right in time in order to complete loading before the TU is scheduled to depart.

Furthermore by example a forward navigation from the shipping cockpit to the warehouse monitor is shown

Shipping Cockpit Execution

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 additionally Sarah can
retrieve context information via the side panel e.g. visual representation of the workload as bar charts for each route, or a
second example is monitoring completed goods issue vs. pending goods issues visualized in a pie chart as well as having a bar
chart of the history available. These are just examples of context information to be displayed in the side panel. These
examples are intended to serve as a template for customers to extent the side panel information tailored to their specific
needs. (Learn more in the How-To Guide: How-To Enhance the Shipping Cockpit)

When a truck arrives, Sarah directs the truck driver to the planned door and sets the TU status to arrival at door. 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. By setting departure from checkpoint
automatically also goods issues is posted and the delivery and transport document are printed.

Finally Sarah hands over the documents to the truck driver and the truck leaves the warehouse.
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
registered 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 registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader
are either trademarks or registered trademarks of Adobe
Systems Incorporated in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered
trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame,
WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or
registered trademarks of W3C, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered 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 registered trademarks of SAP AG in
Germany 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 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.
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
support, 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 SAPs Support Services and may not be
modified or altered in any way.