Yard Management
Supply Chain Execution
SCM 5.0
©SAP AG 2005
© SAP AG 1
Yard Management: Business Process
[Link]-In and move
TU to parking lot
[Link]-Out [Link] TU from
parking lot to door
[Link] TU from door [Link] TU
to checkpoint
© SAP AG 2005
Yard Movement enables you to move transportation units (TUs) from one yard bin to another inside a
yard. Possible types of yard movement are as follows:
The TU arrives at the checkpoint and is moved to a parking space or to the door.
You move a TU from a parking space to the door, or from the door to a parking space.
You move a TU within the yard, from one parking space to another, or from one door to another.
You map each TU using an empty handling unit (HU) which is described as a HU fort he TU and is
moved during yard movement.
© SAP AG 2
Three Components of Yard Management
1) Yard Location
Management: Door A1
Adopt physical/ Door A2
geographical locations Slot 17 WHS 001
(parking lots and doors) P00A 2) Yard Movements:
and objects (trucks) to
system entities (storage
bins and transport Door An Door Door represent physical
units) B1 Bn movements of trucks by
Checkpoint I “moving” transport units
and vehicles within the
yard locations
Door Door
Yn Y1
Slot 34
3) Yard Stock: Door X1
WHS 00n P00B
report the transport Door X2
units content to
support and control the
Door Xn
loading and unloading Checkpoint II
activities
© SAP AG 2005
This graphic shows a possible setup for a Yard.
Location Management: allows you to move objects (vehicles) to geographical locations (parking lots) and
system entities (storage bins and transport units).
Yard Movements: Vehicles and TU‘s can be moved within the yard structure.
Yard Stock: TU contents are visible in the yard.
© SAP AG 3
Yard Location Management
Whse-Nr 0001 WhType: YARD StoSec: CHPTA
WhType: STAREA WhType: Checkpoint A
DOOR
StoSec: 0003
StoSec: StoSec: 0001
Storage Bin
0001
Storage
StoSec: 000n Section
StoSec: 0002
Storage Type
Whse
StoSec: CHPTB Door
Checkpoint B
© SAP AG 2005
A yard is based on the warehouse structure of Extended Warehouse Management (EWM). This means that
a yard represents a separate storage type in a warehouse. However, you can also configure it as a separate
warehouse number, which must then include a storage type that has the role “Yard“. In both cases, you can
use a yard for multiple warehouses. Conversely, you can define a warehouse with multiple yards.
You map the corresponding storage bins as yard bins, which you can group into yard sections, the same as
for the warehouse. The following are possible types of yard bin:
Parking Spaces
You map parking spaces as standard storage bins with standard storage sections and standard
storage bin types.
Checkpoints
The relationship between the checkpoint and a yard bin is 1:1. The checkpoint represents a supply
chain unit with its own address data.
Doors
The door connects the yard to the warehouse. It is important for stock posting and yard
movement.
You can group yard bins into yard sections.
This graphic shows a yard that has been defined as a separate storage type.
© SAP AG 4
Yard Stock - Visibility
y empty TU-HU for all
Yard Movements
y Stock: the HU-
Product itself
1:1 y Stock
overview on Yard
only via assigned
TU-HU TU
Transport Unit
TU knows its assigned deliveries.
HU-Product Product A
WHS1
HU-Product Posted Stock can be:
a) on TU-Location or
b) on WHS-Location.
Product A Product B
WHS1 Product B WHS2
WHS2
© SAP AG 2005
Each time you want to move a TU in the yard, you have to create a warehouse task (WT) manually. To do
this, you use the standard functions for creating and confirming WTs.
This graphic shows the relationship between a TU and the relevant HU for the TU. This relationship is
1:1.
In yard movements, the HU fort he TU always remains empty, meaning the contents of the TU (deliveries
with HUs and unpacked products) are never packed into an HU for the TU. If you move the HU for the
TU in the yard, the system considers only the packaging material, that is the HU, from a stock point of
view, whereas the relevant stock does not follow every movement.
WTs for yard movements are always HU WTs. The system does not use product WTs because quantities
are not considered in yard movements.
© SAP AG 5
Details of Yard Movements
Allow to handle a transport unit (TU) in Yard movement will utilize the same
the yard by moving its corresponding WT mechanism to store and remove
HU from/to different locations Shipping and
TU into and from the yard bin similar
inside the yard
receiving to standard WHS WT
R
yard movement functionality
(manual transfer order creation)
R R
R
R R (Yard)
LIME TO processing Location Mgmt
For moving TU’s inside the yard Printing Movements import TU data like TU-
the considered TU-HU must be status, business activities assignments
posted goods receipt at check-in to door and vehicle, means of transport
etc. and open transfer order data to get
an overview about the situation in the
yard
© SAP AG 2005
The block diagram shows relation and interaction between the YM functionality and the concerning EWM functionalities like
Shipping and receiving for relevant TU data
Yard location management for relevant location data
LIME for posting
TO processing for moving
Click 1
Requirement: HU-TU must posted goods receipt via CHECK-IN/CHECK-OUT UI
HU-TU is empty - the HU-material is the only physical stock for this HU-TU
real stock is on TU-Lime-location in case the TU content is posted goods receipt
Click 2
There is a one-to-one relationship between the TU and the HU
Directing TU from the yard bin to the warehouse door and from door to yard bin
Moving TU from one bin to another in the yard or when moving the TU from door to door
WT confirmation in fore- or background
Click 3
Movement WTs are exclusively adhoc HU WTs
WR creation is not relevant for this process
Click 4
Business activity: shows the TU activity for example ‘active’ or ‘blocked’ for a special period of time
y Yard moves depend on TU status => WT creation not possible for ‘blocked’ Tus
Assignments to door: With transaction /SCWM/DOOR it is possible to plan a assignment between the TU and door.
In the yard movement UI the assigned door will be displayed as a default value
© SAP AG 6
Yard Location – Customizing Set-up I
Yard = Whse-Type with
Role ‘G’
© SAP AG 2005
© SAP AG 7
Yard Location – Customizing Set-up II
Mark those Warehouses which
have a connection to a yard.
The technical link is done through
the Whse-Door-Settings
© SAP AG 2005
© SAP AG 8
Yard Management Master Data Setup
Link Whse-Door to Yard
© SAP AG 2005
© SAP AG 9
Vehicle + TU creation
Inbound:
Mass creation expected via
Shipment Notification resp.
ASN or manually via
/SCWM/Tu resp. /SCWM/VEH
Outbound:
Manual creation via /SCWM/TU
or SCWM/VEH, automated
through FOM (w/
Transportation Planning)
© SAP AG 2005
FOM = Freight Order Management
© SAP AG 10
Quick Check-in/Check-out (Vehicle/TU)
© SAP AG 2005
© SAP AG 11
Extended Check-in/Check-out for TU
© SAP AG 2005
© SAP AG 12
Yard Movements – Desktop Overview
Simple search
criteria
WT creation
for vehicle
WT creation for
transport unit
WT creation data
Transport unit
master data
Tabstrip for WT
confirmation
Tabstrip with
Created WT‘s
© SAP AG 2005
UI yard movements use the pattern concept
In the OIP the HU-Tus will be displayed with the relevant storage data and data of their corresponding
TU
To search HU-Tus in yard you can use the simple or advanced search
Simple search criteria like TU, Checkpoint, license plate.
With pressing this buttons WTs will be created for all HU-Tus which are related to the vehicle
It‘s also possible to create a WT for a special TU – the TU will be separated from the corresponding
vehicle
Relevant WT data like storage data, process type etc
Tabstrips in the ODP
y 1. tabstrip: internal created WTs
y 2. tabstrip: saved WTs for confirmation
y 3. tabstrip: detailed data of the corresponding TU
© SAP AG 13
UI Yard movements – RF overview
WT creation
WT creation & confirmation
© SAP AG 2005
Start with Transaction /scwm/rfui
Enter warehouse no, resource and presentation device and select the following way
ID is a synonym for HU respectively TU, because Yard movements in RF are reusing the RF adhoc HU
WT creation
© SAP AG 14
Yard Monitoring
© SAP AG 2005
The Yard location monitor is part of the Warehouse Monitor.
© SAP AG 15
Copyright 2005 SAP AG. 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 AG. 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, and Informix are trademarks or registered trademarks of IBM Corporation 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, [Link], 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.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided 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 have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. 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 AG 2005
© SAP AG 16
