SAP Yard Logistics Day-to-Day Guide, TZYL20 Col02

Get a practical overview of SAP Yard Logistics 2.0 from the perspective of day-to-day yard operations. This ebook explains the system environment, the master data and organizational elements you need, and how to work with the graphical Yard Layout to process tasks efficiently. You’ll also learn how check-in and check-out are handled for transportation units and how documents flow through typical yard scenarios.

Beyond core execution, the text walks through monitoring tools and shows how yard activities connect with adjacent systems. It highlights integration touchpoints to SAP Transportation Management, SAP Extended Warehouse Management, and SAP ERP (ECC), plus innovations from the SAP Leonardo portfolio that enhance visibility and automation across the yard.

1. TZYL20
Yard Logistics
.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 02
Course Duration: 3 Day(s)
e-book Duration: 4 Hours 10 Minutes
Material Number: 50145760Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

2. Librería ERP https://libreriaerp.com/us [email protected] Librería ERP https://libreriaerp.com/us [email protected]

3. SAP Copyrights and Trademarks
©
2018 SAP SE or an SAP affiliate company. 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 or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please seehttp://global12.sap.com/corporate-en/legal/copyright/index.epxfor additional
trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any
reason without notice. The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking statements are subject to
various risks and uncertainties that could cause actual results to diff er materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.
©Copyright. All rights reserved. iiiLibrer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

4. Typographic Conventions
American English is the standard used in this handbook.
The following typographic conventions are also used.
This information is displayed in the instructor’s presentation
Demonstration
Procedure
Warning or Caution
Hint
Related or Additional Information
Facilitated Discussion
User interface control Example text
Window title Example text
©Copyright. All rights reserved. ivLibrer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

5. Contents
vi Course Overview
1 Unit 1: SAP Yard Logistics (YL), Overview
2 Lesson: Describing SAP Yard Logistics
10 Unit 2: SAP Yard Logistics, Introduction
11 Lesson: Introducing SAP Yard Logistics
29 Unit 3: Graphical Yard Layout
30 Lesson: Explaining the Graphical Yard Layout
32 Lesson: Using the Yard Cockpit
37 Unit 4: Check In and Check Out of Transportation Units
38 Lesson: Planning in SAP Yard Logistics
44 Lesson: Checking Transportation Units In and Out
46 Lesson: Handling the Arrival and Departure of Transportation Units
at the Yard
51 Unit 5: Yard Activities
53 Lesson: Understanding Yard Tasks
58 Lesson: Explaining Queue Management
60 Lesson: Explaining Communication
63 Lesson: Handling Dangerous Goods
65 Lesson: Performing Location Determination
70 Lesson: Executing Measurements
72 Lesson: Performing Pick-Up Planning
76 Lesson: Explaining Cross Docking
78 Unit 6: Yard Monitoring
79 Lesson: Using the Diff erent Tools of Yard Monitoring
86 Unit 7: Cross Processes
87 Lesson: Explaining Dock Appointment Scheduling (DAS)
92 Lesson: Explaining Billing
97 Lesson: Uploading Transportation Units
99 Unit 8: Integration Capabilities
100 Lesson: Explaining the Integration to ERP, EWM and SAP TM
108 Lesson: Explaining the IoT integration
116 Lesson: Exploring the Required Set Up
©Copyright. All rights reserved. vLibrer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

6. Course Overview
TARGET AUDIENCE
This course is intended for the following audiences:
●Application Consultant
●Business Process Architect
●Business Process Owner/Team Lead/Power User
©Copyright. All rights reserved. viLibrer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

7. UNIT 1SAP Yard Logistics (YL),
Overview
Lesson 1
Describing SAP Yard Logistics 2
UNIT OBJECTIVES
●Describe SAP Yard Logistics
©Copyright. All rights reserved. 1Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

8. Unit 1
Lesson 1
Describing SAP Yard Logistics
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Describe SAP Yard Logistics
Overview of Yard Logistics
Figure 1: SAP Yard Logistics Overview
SAP Yard Logistics (SAP YL) simplifies and streamlines truck, container, and rail yard
management. A graphical yard layout enables monitoring and visualization of the yard's
actual situation.
Intuitive user interfaces ease decision making and the support for mobile users cuts down on
paper-based processes.
It allows you to:
●Decrease duration of yard processes
●Monitor all processes in the yard
●Enable the digitalization of the yard
●Scale the solution to diff erent user needs
●Create an integrated business network with SAP Transportation Management and SAP
Extended Warehouse Management
●Fit the solution to your system landscape
©Copyright. All rights reserved. 2Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

9. SAP Yard Logistics 2.0 — Industries
Figure 2: SAP Yard Logistics 2.0 — Industries
The figure gives an overview of the various industries, which can use SAP Yard Logistics 2.0.
Rail Yard
Figure 3: Yard Logistics Overview — Rail Yard
Rail Yards are facing diff erent challenges and have specific characteristics.
The following will give you a rough overview about the main challenges and the specific
characteristics.
Main Challenges
●Many diff erent kinds of products can be stored, sorted, loaded, and unloaded
●Planning of complex movements of trains and railcars, shunting
Lesson: Describing SAP Yard Logistics
©Copyright. All rights reserved. 3Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

10. ●Strictly predefined transport lines (rails) within the yard
●Threat of potential bottlenecks
●Use staging tracks to provide off-layout destinations
●Exploit limited space
Characteristics
Yard Layout:
●Difficult to change yard layout because of expensive infrastructure (rails, and so on)
●Typically only few loading points
●Typically many tracks in parallel
●Different processes depending on loading point and goods to be loaded or unloaded
Yard Processes:
●Complex series of diff erent processes depending on business requirements
-Storing, sorting, loading, and unloading
●Railroad cars are typically moved by yard switcher (a kind of locomotive)
●DG handling
Others:
●Railway yards are recognized as playing a key role in smooth freight transportation
Automotive
Figure 4: Yard Logistics Overview — Automotive
Automotive Yards are facing diff erent challenges and have specific characteristics.
The following will give you a rough overview about the main challenges and the specific
characteristics:
Main Challenges
Unit 1: SAP Yard Logistics (YL), Overview
©Copyright. All rights reserved. 4Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

11. ●All logistics processes have to ensure on-time delivery to the end-customers
●Thereby, vehicle yard management is key to optimizing distribution
●Allocating resources efficiently to ensure reasonable logistics prices
●Optimized planning of limited storage and technical space
●Using advanced information about vehicle arrivals and shipments
Characteristics
Yard Layout:
●Thousands of parking spaces
●Large parking sites
●Ensure that all means of transportation can be combined
Yard Processes:
●Each car has its own specifications with respect to size, delivery date, priority date, and
destination
●Intelligent coordination of large numbers of vehicles
●Vehicle loading and unloading
●Automated processes
●Use of real-time information of free parking slots, vehicles, and movement activities
Others: ●Always determine the optimal parking space for each car
Retail, Consumer Products
Figure 5: Yard Logistics Overview — Retail, Consumer Products
Retail/Consumer Product Yards are facing diff erent challenges and have specific
characteristics.
Lesson: Describing SAP Yard Logistics
©Copyright. All rights reserved. 5Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

12. The following will give you a rough overview about the main challenges and the specific
characteristics:
Main Challenges
●Minimizing time spent loading unloading products
●Extremely competitive market
●Defining enough capacity for very high loading cycles
●Ensuring efficient and timely trailer movements
●Proactive planning requires a high degree of visibility
Characteristics
Yard Layout:
●Huge number of loading docks
●Huge number of parking spaces
Yard Processes:
●Use of RFID tags and GPS tacking
●Potentially smaller packaging sizes
-Consolidation and deconsolidation efforts
●Sometimes movements of very sensitive goods (for example, perishable food) -Prevent contamination
-Prevent disruptions in cold chains
●Continuously receiving real-time dock loading updates
Others:
●Dedicated equipment often required
Unit 1: SAP Yard Logistics (YL), Overview
©Copyright. All rights reserved. 6Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

13. Oil and Gas, Chemicals
Figure 6: Yard Logistics Overview — Oil and Gas, Chemicals
Oil and Gas or Chemical Yards are facing diff erent challenges and have specific
characteristics.
The following will give you a rough overview about the main challenges and the specific
characteristics:
Main Challenges
●Complex Site Layouts
●Many diff erent Process variants
●Bulk Products (weighing, capturing filled qty)
●Equipment provisioning & handling
Characteristics
Yard Layout:
●Typically many loading points
●Different processes depending on loading point
Yard Processes:
●Typically many diff erent Modes of Transports and Means of Transport (from groupage to
parcel tanker)
●Different process types depending on products and order type:
-For example, bulk versus package goods
-Different activities: cleaning of equipment, pre-loaded equipment, weighing, and so on
●DG Handling
Others:
Lesson: Describing SAP Yard Logistics
©Copyright. All rights reserved. 7Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

14. ●Dedicated equipment, for example, specific railcar or container resources
Container Terminal
Figure 7: Yard Logistics Overview — Container Terminal
Container Terminals are facing diff erent challenges and have specific characteristics.
The following will give you a rough overview about the main challenges and the specific
characteristics:
Main Challenges
●Complex site layouts
●Intermodal processes with small time windows
●Container storage and removal with minimum amount of movements
●Demurrage and other fees
●Sequence of movements
Characteristics
Yard Layout:
●Typically many piles of containers
●Cranes are used for moving containers
●Rail connections are often available
Yard Processes:
● -Loading, unloading, and storage of containers
-Heating and inspection activities
-Intermodal processes
-Stacking of containers
Others
●
Dedicated equipment, for example, specific railcar or container resources
Unit 1: SAP Yard Logistics (YL), Overview
©Copyright. All rights reserved. 8Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

15. LESSON SUMMARY
You should now be able to:
●Describe SAP Yard Logistics
Lesson: Describing SAP Yard Logistics
©Copyright. All rights reserved. 9Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

16. UNIT 2SAP Yard Logistics,
Introduction
Lesson 1
Introducing SAP Yard Logistics 11
UNIT OBJECTIVES
●Get an introduction to SAP Yard Logistics
©Copyright. All rights reserved. 10Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

17. Unit 2
Lesson 1
Introducing SAP Yard Logistics
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Get an introduction to SAP Yard Logistics
Reasons to Use Yard Management Software
Figure 8: Introduction — Why use Yard Management?
The figure shows examples of diff erent yards: a container yard, chemical yard, and rail yard.
When it comes to efficient logistics and order fulfillment,, a yard is the link between the
distribution and transportation of goods and the warehouse. With the rising importance of e-
commerce and supply chains focusing on customer centricity, speed of fulfillment is the big
ask for logistics. Only with a seamlessly integrated flow of goods through the entire stages of
logistics can this demand be addressed and lead times be significantly reduced. The yard is
an important part of the overall network — it is more than the parking lot of a distribution
center. It serves as a connection point of inbound and outbound process flow, as well as a
storage location for containers, trailers, and other means of transport. In the yard, shipments
with high priority can be identified and handled accordingly to prevent delays or even stock-
outs. By effectively controlling the physical movement of assets in the yard, the overall
utilization of scarce resources can be increased.
©Copyright. All rights reserved. 11Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

18. SAP Solutions of Yard Management
Figure 9: SAP Extended Warehouse Management (EWM) Yard Management
This figure shows the simple yard process of the SAP EWM Yard Management functionality.
It starts with the check in of the transportation unit (TU) and the movement of the TU to a
parking lot on the yard. The next process step is the movement of the TU to the door, followed
by loading or unloading the TU. After the loading or unloading process step, the TU is moved
to the checkpoint where the TU will be checked out.
This process shows that the functionality of SAP EWM Yard Management is limited to simple
yard processes.
Business Process and Functions in SAP Yard Logistics
Figure 10: Business Process and Functions in SAP Yard Logistics
This graphic shows the standard process for yard management and the standard
functionality within SAP Yard Logistics 2.0.
The standard process is separated in four steps:
1.Planning
2.Check In
Unit 2: SAP Yard Logistics, Introduction
©Copyright. All rights reserved. 12Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

19. 3.Execution
4.Check Out
Below the standard process, the standard functionalities of SAP Yard Logistics 2.0 are shown.
The explanation of each functionality is part of this course and will be covered in the
respective units.
SAP Yard Logistics offers visibility into inbound and outbound transports, shows alerts as well
as exceptions, and supports planned and unplanned yard movements. Services and activities
such as cleaning, repair, or dangerous goods checks can be applied as well. Through support
for mobile users with smartphones or tablets, slow and inefficient paper-based processes can
be eliminated. To enable a closed-loop business process, a built-in connection to billing
enables yard managers to charge internal and external customers for all activities executed
within the yard. When drivers arrive at warehousing facilities, their shipments often need to be
unloaded within a specified time. If they aren't, the carrier typically charges the distribution
center a daily penalty. The faster that trucks are checked in, unloaded, and sent back on the
road, the better it is for everyone.
SAP Yard Logistics can improve shipment transfer into and out of the yard, promoting
improved service levels, saving time and money, and enhancing the logistics process.
Generally, yard management systems can boost a yard's productivity significantly. SAP Yard
Logistics can also significantly reduce labor and administrative costs: for example, reducing
the time required for yard checks from hours to minutes.
Challenges
There are certain challenges that yard owners face, such as lack of visibility of the yard
activities or inventory. Trailer yards can be supply chain "black holes," existing outside the
visibility provided by transportation and warehouse management systems. Yard information
is often still managed completely manually; it can be incomplete and not up to date, which
means the processes in the yard can't be planned efficiently. As a result, workers might end
up wasting time hunting for trailers or parking trailers in the wrong location. An efficient yard
management solution must create visibility into the yard as well as control movements
effectively. To efficiently and profitably operate a truck, container, or rail yard, a logistics
manager needs real-time visibility into all processes that happen in the yard and the ability to identify future workloads. Dwell times and empty moves can also result in high costs; and the productivity of the yard jockeys, who are responsible for moving assets in the yard (such as
containers or trailers), has huge potential for improvement. The same applies for gate-in and
gate-out processes. Efficiency is key in order to achieve fast processing time in the yard and
less waiting time for the drivers. Based on planning input from diff erent systems, such as SAP
Transportation Management, it is possible to optimize the use of yard resources.
Lesson: Introducing SAP Yard Logistics
©Copyright. All rights reserved. 13Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

20. Figure 11: SAP Yard Logistics - Role Overview
Within SAP Yard Logistics 2.0, diff erent roles can be set up. The figure shows an example of
what these roles could look like.
The Supervisor/ Planner of the yard is responsible for the planning of in- and outbound
transports, resource and capacity planning, the monitoring of the yard by the help of the
graphical yard layout, billing of activities (such as washing a container), and the control and
management of alerts that occur during yard processing.
The Hub Manager is responsible for the management of the yard. His focus is on operating
figures and the smooth process on the yard. To ensure this, he has to use the reporting and
long-term planning functionality of SAP Yard Logistics 2.0.
The Gate Agent is responsible for the in- and outgoing transports and drivers of the yard. His
interest is focused on the check in and check out functionality, on security checks, and the
documentation of load securing within SAP Yard Logistics 2.0. With the printing and hand
over of the transport documents, the last process step before the check out can be executed.
The Driver of the transportation unit has to work with the self check in, if he is not already
notified at the yard. Using the self check in functionality, he can provide personal or transport-
related information. For communication between the yard process participants, diff erent
techniques like SMS, pager, or SAP Fiori apps can be used.
The Yard Operator is the executing work force on the yard. He's responsible for the handling
of transportation units, such as the following:
●Movements
●(Security) inspections
●Washing
●Measurement checks
●Exception handling
Unit 2: SAP Yard Logistics, Introduction
©Copyright. All rights reserved. 14Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

21. Comparison: SAP Yard Logistics and SAP EWM Yard Management
Figure 12: Comparison: SAP Yard Logistics and SAP EWM Yard Management — Summary (1)
Explanation:
●++ Functionality comprehensively covered
●+ Basic functional coverage
●[blank] Functionality not available in standard
SAP offers two solutions for Yard Management:
●SAP Yard Management of Extended Warehouse Management (EWM)
SAP EWM has a standard functionality for simple yard management processes — better
known as SAP Yard Management. This functionality in SAP EWM was added in the past to
set up simple processes for yard management.
●SAP Yard Logistics
Due to customer requirements, which were getting more and more complex, SAP made
the decision to develop a complete new standard yard management solution with
advanced functionality for more complex yard processes.
Note:
●To use the yard management functionality, the customer has to run SAP EWM,
while SAP Yard Logistics is designed to be deployed as a stand-alone solution.
●SAP Yard Logistics also contains planning functionality for yard tasks that were
not foreseen in SAP EWM.
●SAP Yard Logistics provides great visibility of the current yard processes as
well as future tasks in a graphical and document-based way.
Lesson: Introducing SAP Yard Logistics
©Copyright. All rights reserved. 15Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

22. Figure 13: Comparison: SAP Yard Logistics and SAP EWM Yard Management — Summary (2)
Explanation:
●++ Functionality comprehensively covered
●+ Basic functional coverage
●[blank] Functionality not available in standard
The decision for SAP Yard Logistics or Yard Management (as included in SAP EWM) is driven
by process requirements. The figure indicates which functionality is covered in which system.
As a general guidance you might take the following points.
SAP EWM Yard Management might apply to you in the following cases:
●If you already have an SAP EWM implementation onside
●If you have only simple arrival and departure processes, without additional steps in the
yard
Summary of the comparison
If you are looking for any of the following, you should consider SAP Yard Logistics as your
preferred Yard Management solution:
●Multistep processes
●Internal transports
●Storage of items in the yard
●Washing, inspection, and maintenance activities
●Automation of yard processes
The comparison shows the areas where Yard Logistics is more advanced than SAP EWM Yard
Management. Functionalities like container stacking, complex hierarchies, or self check in are
not available in SAP EWM.
Also, the handling of multiple transportation units is not supported in SAP EWM Yard
Management.
Unit 2: SAP Yard Logistics, Introduction
©Copyright. All rights reserved. 16Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

23. Figure 14: Comparison: SAP Yard Logistics and SAP EWM Yard Management (1)
The figure, Comparison: SAP Yard Logistics and SAP EWM Yard Management (1), shows the
main features of the EWM Yard management.
Figure 15: Comparison: SAP Yard Logistics and SAP EWM Yard Management (2)
The figure, Comparison: SAP Yard Logistics and SAP EWM Yard Management (2), shows the
main features of SAP Yard logistics, part 1.
Lesson: Introducing SAP Yard Logistics
©Copyright. All rights reserved. 17Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

24. Figure 16: Comparison: SAP Yard Logistics and SAP EWM Yard Management (3)
The figure, Comparison: SAP Yard Logistics and SAP EWM Yard Management (3), shows the
main features of SAP Yard logistics, part 2.
Yard Logistics Organizational Units and Structure
Figure 17: Organizational Units of a Yard Structure
Theyard numberis the organizational unit at the highest level in Yard Logistics. It is used to
represent the yard. Each yard number has a substructure that maps the spatial relationship in
the yard complex in detail.
There are diff erent forms where transportation units are physically placed in the yard: various
types of parking lots, places for weighing or washing, and inbound or outbound areas. This is
represented withstorage typesas a group of yard bins with similar characteristics. Storage
types are defined on the basis of their spatial or organizational features.
Astorage sectionis a subdivision of a storage type, and represents a group of bins that
generally have some sort of shared attribute. A storage section is an organizational unit within
the storage type, which summarizes storage bins with common attributes for the purpose of
putaway. The use of storage sections in a storage type is only mandatory if you use storage
section control or storage section search in the storage type.
Unit 2: SAP Yard Logistics, Introduction
©Copyright. All rights reserved. 18Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

25. You can divide your storage bins into groups according to their physical attributes (for
example, large bins or small bins). This is done by the storage bin types. During slotting, you
can have the system determine a preferred storage bin type. In combination with the
transportation unit type, a suitable storage bin is suggested to you during putaway.
On the lowest level of the organizational structure are the
storage bins. They are assigned to a
storage section (if used) and a storage type and represent the physical location where the
transportation units are placed within the yard. Whenever you keep a transportation unit in
the yard, you have to indicate its exact residence: the storage bin. The coordinates of the
storage bin tell you the precise position in the yard. Storage bins are considered as master
data
Summary
Yard Number:
●An organizational unit that represents the yard. A yard warehouse has a warehouse
number assigned from SAP EWM that serves as a basis to define the yard's physical
storage layout.
Storage Type: ●A storage type represents a physical or logical subdivision of a yard complex, which is
characterized by its space required, organizational form, or function.
●A storage type consists of one or more storage bins.
Note:
Yard Logistics only supports storage type role Yard.
Storage Section:
●In Yard Logistics, a storage section is an organizational subdivision of a storage type,
which groups together storage bins with similar usage.
●The criteria for grouping bins together are freely definable: doors in a specific area or
groups of parking lots.
Storage Bin Type:
●You can divide your storage bins into groups according to their physical attributes (for
example, large parking lots, small parking lots). The storage bin type holds the information
about length and width of each storage bin in the yard.
●The storage bin type plays an important role during movements creation for the capacity
check as it defines the length and width of the bin.
Storage Bin:
●The storage bin is the smallest spatial unit in the yard.
●The storage bin represents the exact position in the yard where transportation units are
placed (for example, parking lot, checkpoint inbound, washing place, or loading point at
the warehouse).
●For each storage bin, you have to assign the yard number in which the storage bin is
located.
Lesson: Introducing SAP Yard Logistics
©Copyright. All rights reserved. 19Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

26. ●A storage type and a storage section can also be assigned to each storage bin.
The following additional attributes can be defined for a storage bin:
●Storage bin type (for example, for large or small parking lots)
●Maximum weight
●Total capacity
Master Data
Figure 18: General Master Data: Data Transfer Between ERP and Yard Logistics
The Core Interface (CIF) is used for communication between the ERP system and the Yard
Logistics system, whether this is part of a bigger SAP Supply Chain Management (SCM)
system, a standalone system, or an add-on.
Master data, like material master, customers and vendors, which are centrally maintained in
the ERP system, are transferred to the Yard Logistics system through the CIF.
The CIF is the standard and long proven interface solution for the SAP SCM system and SAP
Advanced Planning and Optimization (APO). It was reused for the Yard Logistics integration.
Figure 19: Yard Transportation Unit
A yard transportation unit (TU) represents a business object that can be checked in, checked
out, and handled in the yard by using yard requests, yard orders, and yard tasks.
Unit 2: SAP Yard Logistics, Introduction
©Copyright. All rights reserved. 20Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

27. This business object can be used for wrapping SAP EWM TUs and enhancing them with SAP
Yard Logistics-specific functionality, such as TU grouping, storing of seals, and
measurements.
The transportation unit in SAP Yard Logistics has the following main definition attributes:
●TU Type (general classification criteria, important for various processes like compatibility
checks or stacking)
●Means of Transport
●Packaging Material Type (used for definition of dimensions and capacity checks)
A TU in SAP Yard Logistics represents the diff erent assets in the yard, such as trucks and
trailers, vessels, or railcars, and has the following characteristics:
●A unique identification
●Re-usable
●Can be moved
●Supports stacking
●Can be loaded on top of another TU
●Can be unloaded from another TU
Themeans of transportdefines groups of vehicle resources. Transports can be executed via
air, sea, rail, or street.
For the transportation unit in SAP Yard Logistics, it is necessary to define a means of
transport, which is assigned to the packaging material.
Means of transport in SAP Yard Logistics include the following:
●Airplane
●Train
●Euro Trucking
●ABC shipping
Lesson: Introducing SAP Yard Logistics
©Copyright. All rights reserved. 21Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

28. Figure 20: Definition of a Transportation Unit Type in SAP Yard Logistics Customizing
Within Yard Logistics, a transportation unit has to be defined in the Customizing. The relevant
parameters are listed below:
●Grouping item
A grouping item serves as a grouping object in the hierarchy of items. It does not physically
exist in the yard. You can then assign this grouping item to a yard task.
●Carrying item
These are physical objects in the yard and are non-grouping items. Other items can be
loaded on top of these items. For example, trucks, trailers, locomotives, rail cars.
●Loading Scheme
The loading scheme defines the makeup of the TU in terms of how it supports loading on
other TUs. For example, a container on a trailer
●TU Type Icon
The TU Type Icon defines the icon used in documents associated with this TU type.
●TU Stackable
A TU may be stackable (that is, it can be loaded on top of other TUs in a certain position or
not). If it is stackable, you define the maximum stackable weight of the TU.
Unit 2: SAP Yard Logistics, Introduction
©Copyright. All rights reserved. 22Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

29. Figure 21: Classifications in Yard Logistics
In SAP Yard Logistics, we use the class system to extend yard TU attributes by additional
fields and values. This is used in the TU determination and validation logic.
For this, SAP introduced two new class types: one for classifying yard TUs, and another for
yard order or yard request items.
The yard order item classification can be used to define the properties for a container
(represented by the classification data of a yard TU) that are relevant during the assignment
of such a container to a yard order item. To trigger that determination, SAP Yard Logistics
offers aTU Determinationbutton that searches for a list of available yard TUs that fulfill these
classification properties of the yard order item, based on each the classification data of the
yard TU.
Based on classifications, the system can propose TUs that shall be picked (for example, best
railcar for certain coils of steel) to support efficient yard processing.
Figure 22: Classification of an Yard Order Item and TU
When you create a new yard order or yard request item, you need to provide a TU type.
If this TU type is relevant for classification (See customizing TU type classification
assignment), it is possible to enter characteristics in theClassification Data tab of the yard
order or yard request UI.
Classifications are linked to the following:
Lesson: Introducing SAP Yard Logistics
©Copyright. All rights reserved. 23Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

30. ●Yard Orders
-Characteristics of incoming TUs in inbound yard orders
-Required characteristics for outgoing TUs in outbound yard orders
●Transportation units
-Characteristics of a TU within the yard
-Characteristics can be changed for a TU
For the usage the following setup is needed:
●Classification object types and class types
-In the SAP Customizing Implementation Guide, chooseCross-Application Components
→Classification System →Classes→Maintain Object Types and Class Types.
-Ensure that the same class type (for example, CTU) is created for transportation units
and characteristics
●Classification object keys
-In the SAP Customizing Implementation Guide, chooseCross-Application Components
→Classification System →Classes→Maintain Object Keys.
-Here you may assign classes to existing TUs or yard order items manually, if needed.
●Definition of classes and characteristics
-To either create or edit a classification characteristic, enter transaction code CT04.
There you can define your own characteristic for your purpose.
-To either create or edit a classification class, enter transaction code CL02. There you
can define your own class and assign characteristics.
-In the NWBC menu, choosingMaster Data→Classification →Maintain Classes for TU
Typesallows you to add a new classification class assignment to link a TU type and
classification class.
Figure 23: Container Number Identification — General Understanding
Unit 2: SAP Yard Logistics, Introduction
©Copyright. All rights reserved. 24Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

31. The format of container numbers is described with ISO 6346. It consists of the owner code,
the equipment category identifier, the serial number, and a check digit. An example of an ISO
6346 conforming container number is CSQU 305438 3:
●Owner code ("CSQ" in the example)
The owner code consists of three capital letters of the Latin alphabet to indicate the owner
or principal operator of the container. Such code needs to be registered at the Bureau
International des Conteneurs in Paris to ensure uniqueness worldwide.
●
Equipment category identifier ("U" in the example)
U for all freight containers. No others currently supported in SAP Yard Logistics.
●Serial number ("305438" in the example)
The serial number consists of 6 numberic digits, assigned by the owner or operator,
uniquely identifying the container within that owner/operator's fleet.
●Check digit ("3" in the example)
The check digit consists of one numeric digit providing a means of validating the recording
and transmission accuracies of the owner code and serial number.
Figure 24: Railcar Number Identification — General Understanding
The format of container numbers follows the rules introduced by the UIC Code of Practice
438-3, Identification marking for tractive stock.
The complete wagon number comprises 12 digits. An example of a full wagon number is 91 80
8194 052 7.
The individual digits have the following meaning:
●Digits 1-2: Type of vehicle and indication of the interoperability capacity ("91" in the
example means electric locomotive)
●Digits 3-4: Country Code ("80" in the example means Germany)
●Digits 5-8: Vehicle type information ("8194" in the example means DRG Class E 94)
●Digits 9-11: Individual running number, or serial number ("052" in the example)
●Digit 12: Self-check digit ("7" in the example)
Lesson: Introducing SAP Yard Logistics
©Copyright. All rights reserved. 25Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

32. For a container number validation, there is a standard check implementation available in SAP
Yard Logistics.
To activate this, in Customizing for Yard Logistics, chooseMaster Data→Settings for
Transportation Units→Transportation Unit Validation→General→Define Classes and
Methods for Checking TU number.
There, you need to maintain the following entry underClass/Interfacefor your yard and the
respective TU type for your railcar to be checked according to the railcar number. /SAPYL/
CL_EXT_NO_CHECK_RC
Figure 25: Dangerous Goods Master Data Environment Health Safety Management (EH&S)
Yard Logistics solution uses the scenario for Environment Health Safety Management (EH&S)
handling based on goods with master data.
The goods are represented in EH&S Specification Management, which stores the required
data. In EH&S Specification Management, required data about hazardous substances and
dangerous goods can be maintained and provided for further processing in Yard Logistics.
Unit 2: SAP Yard Logistics, Introduction
©Copyright. All rights reserved. 26Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

33. Figure 26: Master Data
There are three ways of maintaining dangerous goods Information:
●External system: Dangerous goods data comes from the external system, together with
other information. In this case, there is no possibility to change this data in a yard request
or yard order.
●EH&S: Dangerous goods data master and hazardous substances are maintained in and
determined from EH&S. No changes are possible in yard request or yard order.
●Manually: User enters dangerous goods or hazardous substance data manually in yard
request or yard order.
Figure 27: Master Data
If theDangerous Goodsfield is set toYes, you can implement your own checks in the BAdI
which is called during check-in and check-out processes.
The user can switch on or off a separation key check using the yard parameterDG Check.
Lesson: Introducing SAP Yard Logistics
©Copyright. All rights reserved. 27Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

34. Note:
The separation key functionality was provided in release 1 and does not use EH&S
master data.
LESSON SUMMARY
You should now be able to:
●Get an introduction to SAP Yard Logistics
Unit 2: SAP Yard Logistics, Introduction
©Copyright. All rights reserved. 28Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

35. UNIT 3Graphical Yard Layout
Lesson 1
Explaining the Graphical Yard Layout 30
Lesson 2
Using the Yard Cockpit 32
UNIT OBJECTIVES
●Explain the Graphical Yard Layout
●Use the Yard Cockpit
©Copyright. All rights reserved. 29Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

36. Unit 3
Lesson 1
Explaining the Graphical Yard Layout
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Explain the Graphical Yard Layout
Yard Layout
Figure 28: Yard Cockpit
The Yard Cockpit is a monitoring tool that enables you to oversee all activities within a yard
based on the operational documents as well as the current situation using a graphical
visualization. To support these requirements, the Yard Cockpit is split into several areas. The
right side of the screen contains the visual yard, which is the display of the current situation
within the yard in a graphical view. On the left side of the screen, there are lists which allow the
efficient filtering and display of additional data, for example Yard Tasks, Yard Order, TUs and
so on.
The Yard Cockpit contains several overview lists displaying yard tasks, yard orders, alerts,
and so on, such as the Visual Yard, which contains the graphical representation of the yard.
In theOrderssection, you can search for yard orders and yard tasks:
●Yard Order - For a yard order, you can create tasks.
●Yard Task - You can display and edit a yard task from the search result or create a yard
task.
In theAlertssection, you can search for alerts that occurred within your yard. These alerts
could also be triggered from, for example, sensor data of a refrigerated trailer.
©Copyright. All rights reserved. 30Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

37. In theResourcessection, you can search for the handling resources. The system displays the
handling resources assigned to this yard as per your search criteria.
In theTransportation Unitsection, you can search for TUs.
SAP Visual Business
In SAP Yard Logistics, the Yard Cockpit's graphical visualization is based on SAP Visual
Business, which is a technical component for geo-visualization.
SAP Visual Business is a user interface technology that visualizes data from SAP and external
data sources on a single screen. SAP Visual Business applications not only combine diff erent
types of content, but also include interactive graphics that visualize and combine enterprise
data with geographical or three-dimensional real-world scenes. The SAP Visual Business
front-end component used on the UI of SAP Yard Logistics is a client component.
For use on NetWeaver platform release 7.4, SAP Visual Business release 2.1 is recommended.
The corresponding local user interface linked to this release is NetWeaver Business Client 5.0
PL12 (or higher) or NetWeaver Business Client 6.0 PL05.
LESSON SUMMARY
You should now be able to:
●Explain the Graphical Yard Layout
Lesson: Explaining the Graphical Yard Layout
©Copyright. All rights reserved. 31Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

38. Unit 3
Lesson 2
Using the Yard Cockpit
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Use the Yard Cockpit
The Yard Cockpit
Figure 29: Yard Cockpit Yard Layout Editor
The drawing of the yard is done in the yard layout editor of Yard Logistics. Before the yard can
be drawn, the relevant storage bins have to be defined and created as master data.
Once, all required storage bins have been created, they can be used to set up the graphical
yard.
An additional prerequisite is the definition of an assignment between the visual object type
and the storage bin type. This assignment provides the information for the layout, and how the bin shall be shown.
The maintenance of the yard layout starts always with the selection of the bin, either by
picking a bin from the list of storage bins or by selection (mouse click) on the visual yard.
For each storage bin, a traffic light icon in the list represents the status information:
●Red - there are errors in the definition of storage bin or layout
●Yellow - all settings are fine; the bin, however, has not been drawn yet
●Green - settings are found and the bin has been drawn
After the selection, the corresponding storage bin is highlighted in the list and also shown in the layout, if already drawn.
©Copyright. All rights reserved. 32Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

39. ●A storage bin, that has not been drawn yet, can be created right away.
●A storage bin with existing graphical representation is handled directly in change mode.
The user interface guides and supports the user to design the shape of the selected storage
bin, depending on the shape type.
To draw the yard more accurately, coordinates (X, Y, Z) for each bin can be defined in the
yard layout editor.
Figure 30: Yard Cockpit Yard Layout Editor - Definition of Textures
This Customizing setting allows the definition of textures which are a more appropriate
visualization of transportation units (for example, textures for trucks, containers, or railcars).
The texture needs to be defined as yard-specific and requires a MIME-repository
(Multipurpose Internet Mail Extensions) path.
Figure 31: Yard Cockpit Yard Layout Editor - Collada Model
In the Yard Cockpit, you want to graphically display commercial trucks, trailers, and
containers in the yard. This requires Collada (COLLAborative Design Activity) objects that you
Lesson: Using the Yard Cockpit
©Copyright. All rights reserved. 33Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

40. can assign to an object type (for example, commercial truck, locomotive, container) in the
yard logistics menu master data.
Restrictions for Colladas in the current Visual Business version:
●The Collada visualizer supports only triangles and simple materials (colors) and textures.
●Polygons with more than three sides, lines, line sections, and spines are not supported.
●Animations are not supported.
Only with using Collada models, a physical loading (for example, container on top of a railcar),
can be represented in the visual yard.
The Collada model needs to be defined as yard-specific and requires a MIME-repository path.
Figure 32: Yard Cockpit Yard Layout Editor - Visual Object Type
The visual object type defines the look of an object within the yard.
Different shapes (input field Shape) can be used to visualize the object:
Box
A box storage bin will be displayed as a box with a texture. This type is used to display, for
example, buildings. The height of the box is defined at the level of the storage bin type. Box-
storage bins cannot be used for yard operations (storage of TUs).
The floor plan of a box is defined by three coordinates:
●Lower left corner
●Upper left corner
●Upper right corner
Rectangle
A rectangle is used to define a storage bin for the storage of a transportation unit (for
example, parking lane). Length and width are defined at the level of the storage bin. In
addition, the capacity (for example, in meters) and the alignment of a transportation unit (for
example, rotation angle or stacking) within the storage bins are defined.
Such a storage bin can be used, for example, for a single container slot, a straight rail track, a
parking lane, and so on.
Unit 3: Graphical Yard Layout
©Copyright. All rights reserved. 34Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

41. A floor plan of a rectangle will be designed analogous to a box by three coordinates. The left
corners define the starting edge of the storage bin.
Multi-Segment
A storage bin defined by multiple segments can be used to represent a rail track or and
parking area. If the end point of a segment is identical to the start point of the next segment,
both are connected (for example, a track with multiple segments). The width of multi-
segment storage bins is defined at the level of the storage bin type to ensure a consistent
visualization (for example, each rail track has same width). Therefore the floor plan will be
defined by selection of start and end coordinates.
Compound
This shape is used to display objects or buildings with a floor plan unequal to a rectangle. A
compound is defined by a closed polygon as floor plan and a height defined at storage bin
type level. Compound storage bins cannot be used for yard operations. To design a
compound with a floor plan unequal to an rectangle, the user has to define a closed polygon.
The polygon points have to be defined in clockwise order.
Polygon
This shape is used to display a floor plan like a compound, however, only on a two-
dimensional level. Polygon storage bins cannot be used for yard operations (for example,
movement).
The field Fill Colorindicates the color which is used to fill the shape, Border Colordefines the
color of the shape’s border,Highlight Colordefines the color while hovering over the object in
the visual yard. TheSelection Colorfield describes the color of an object while selecting or
clicking it with the mouse in the visual yard.
The field Modelserves as definition of the Collada object. In case you want to display a
container on top for example, of a truck, you would need to useVO Load Ht Off set,VO Load
Lgth Off set, andUnitto indicate height and length in a measurement unit to say that the
object is displayed, for example, half a meter above floor level and two meters to the right to
get a proper display on top of a truck.
After the visual object type is defined, you have to assign it to the relevant packaging material
because the packaging material is used to represent transportation units within the visual yard.
Figure 33: Yard Cockpit Yard Layout Editor - VBI Color Management
Lesson: Using the Yard Cockpit
©Copyright. All rights reserved. 35Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

42. With this application, the colors which are to be used in the visual yard can be defined. These
colors can be used for diff erent object types, representing either storage bins or
transportation units in the yard.
Different color modes (for example, RGB, RGBA, and so on.) can be used to define the colors.
A preview of the color is displayed also.
LESSON SUMMARY
You should now be able to:
●Use the Yard Cockpit
Unit 3: Graphical Yard Layout
©Copyright. All rights reserved. 36Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

43. UNIT 4Check In and Check Out
of Transportation Units
Lesson 1
Planning in SAP Yard Logistics 38
Lesson 2
Checking Transportation Units In and Out 44
Lesson 3
Handling the Arrival and Departure of Transportation Units at the Yard 46
UNIT OBJECTIVES
●Plan in SAP Yard Logistics
●Check in and check out transportation units
●Handle the arrival and departure of transportation units at the yard
©Copyright. All rights reserved. 37Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

44. Unit 4
Lesson 1
Planning in SAP Yard Logistics
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Plan in SAP Yard Logistics
SAP Yard Logistics — Planning
Figure 34: Yard Request and Yard Order - Overview Document Characteristics
The following describes the characteristics of the yard documents. The characteristics for the
yard request and the yard order are equal (except lifecycle status and execution status).
●The system displays the order type. You can select this when you create the yard request.
●The system displays the direction of the yard request (that is, whether the transportation
unit is inbound or outbound). You can select this when you create the yard request.
Explanations about some fields: Lifecycle Status
The yard requestLifecycle Statusfield changes automatically depending on the phase of the
yard request. The lifecycle status of a yard request can be one of the following:
●Created
The status of a yard request is created when you create and save a yard request.
●Activated
The status of a yard request changes to Activated when you release a yard request. The
system creates a yard order.
©Copyright. All rights reserved. 38Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

45. ●Completed
The status of a yard request changes to Completed when the status of the yard order
associated with this yard request changes to Completed.
●Blocked
Assume that two TUs of a yard request carry dangerous goods, but the corresponding
items have to be kept separated from each other with respect to dangerous goods
Customizing. When you save the yard request, the system saves the document but the
status of the yard request changes to Blocked if the separation rules are not obeyed. The
user interface displays a warning message. You have to make changes to the dangerous
goods settings either in the user interface or in the customizing to unblock the yard
request.
The yard orderLifecycle Statusfield changes automatically depending on the phase of the
yard order. The lifecycle status of a yard order can be one of the following:
●Planned
When you release a yard request, the system automatically creates a yard order with the
status as Planned. When you manually create and save a yard order, the status of the yard
order is Planned.
●Active
●Inbound Yard Order:
When you check-in an inbound yard order, the status of the inbound yard order changes
from Planned to Active.
●Outbound Yard Order:
When you select theActivateoption on top of the yard order user interface, the status of
the outbound yard order changes from Planned to Active.
●Completed:
The status of the yard order changes to Completed when:
-Inbound yard order: You select theCompleteoption on the inbound yard order user
interface. In this case, the TU is no longer assigned to this yard order, though the TU is
still on the yard.
-Outbound yard order: You check out the yard order.
Execution Status
The execution status of the yard order changes automatically based on the status of the yard
tasks assigned to this yard order. The execution status of a yard order can be one of the
following:
●Not Started
When the yard request is created and the lifecycle status of the yard order is Planned.
●In Progress
When you select theStart Processingoption on the yard order.
●Partially Completed
Lesson: Planning in SAP Yard Logistics
©Copyright. All rights reserved. 39Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

46. When at least one yard task of the yard order is Confirmed and there is at least one more
yard task left to be executed.
●Completed
When all the tasks of the yard order are completed, that is, the status of the yard tasks are
either Confirmed or Cancelled.
Further information about diff erent fields:
●Vehicle Information: This information is not mandatory.
●Enter the carrier number to identify the entity responsible for executing the transport
approaching or leaving the yard.
●TheSCACfield uniquely identifies a carrier.
●Enter the driver name.
●Enter the language key for the driver's language of communication.
●Enter the telephone number of the driver.
●Dimensions: Dimensions are a total of all the items and the system calculates it
automatically once you create the items.
●Administrative Data: The system determines this information automatically depending on
the user and the time of creation and change of the yard request/ order.
●Locations: The system reads the location data that you have maintained from the user
interface underMaster Data→Yard Layout→
Define Default Location for Yard Order/
Yard Request. The system defaults the arrival information for an inbound yard request or
order and departure information for an outbound yard request or order. You can also overwrite this data.
●Items (for example, truck, trailer, railcar, container)
●Tasks (for example, movement)
●Business Partner
●Date/Time
●Reference: This is the header reference for the yard request/ order.
●Yard Document Flow: Here, you can view all the relevant documents associated with this
yard request/ order. You can see the relevant documents underPredecessor Business
DocumentsandSuccessor Business Documents. For example, for a yard request, under
Successor Business Documents, you can see the yard order and yard tasks associated with
this yard request. You can select the business document number to go to the document
directly from here.
●Change Documents: You can enter a time frame to see all the changes made to the yard
request or order during that time period. If you do not enter any time interval, the system
displays all changes at a glance.
●Output Management: This is based on the Post Processing Framework (PPF). When the
yard request or order lifecycle status changes, the system executes the process in the
background. The result of this background processing is displayed in theOutput
Managementsection.
Unit 4: Check In and Check Out of Transportation Units
©Copyright. All rights reserved. 40Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

47. ●You can select an action inOutput Managementto see the details for the same.
●If an action is unsuccessful, you can regenerate the action.
●You can manually generate a new action from here, for example, manual printing of the
yard request/ order.
●You can regenerate an action from here, for example, reprint the yard request/ order.
Warehouse Visit in SAP YL
In order to allow integration of Yard Logistics with external EWM systems, so called
warehouse visits should be maintained. A warehouse visit represents a combination of an
external EWM system and the EWM warehouse where a transportation unit should be
processed. Warehouse visits must be defined per each yard order item in the corresponding
tab before check-in or the activation of a yard request. Warehouse visits can be generated
automatically based on SAP TM freight order information as well.
Loading Scheme
A loading scheme defines how a TU can be loaded with other TUs. A loading scheme is
assigned to an item.
When the user assigns a subitem to such an item, the system checks if the TU can be loaded
onto the higher level TU.
In a yard order, for an item, based on the TU type that you enter, the system checks whether a
loading scheme can be assigned to it. The system also checks whether the item is a carrying
item or a loading item or both.
●Loading Layout Section
If the item is a carrying item and if the loading scheme can be assigned to the TU, the fields
Loading Scheme and Layout are activated. Once you select the Loading Scheme, it is
mandatory to select the Layout. As a Loading Scheme can consist of up to two levels, you
can define the layout of each level.
●Positioning Section
If the item is a loading item, and you have entered the Loading Scheme and Layout for the
parent item, you can enter the Position and Level for the TU under the Positioning section.
If the item is a carrying item and a loading item, you can enter the carrying details under
the Loading Layout section and the loading details under the Positioning section. .
Lesson: Planning in SAP Yard Logistics
©Copyright. All rights reserved. 41Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

48. Planning in SAP Yard Logistics, Introduction
Figure 35: Planning in SAP Yard Logistics
The planning component allows you to plan the operation workload for a yard. During the
planning stage, you can receive some information from the customer or from the SAP
Transportation Management (TM), based on the freight order.
Furthermore, the planning can also be based on internal production processes, as the yard
could also be assigned for a plant.
You enter the planning process in the system using a yard request. The yard request is an
optional document in SAP Yard Logistics.
The purpose of a yard request is to identify the workload for the yard, for example, based on
customer order, production order, or planned incoming or outgoing transports.
A yard request is in response to a request for some activities in the yard. Once all yard
requests are represented in the system, you have an overview of the planned workload for
your yard in a certain time frame.
A yard request is created during the planning phase in one of the following ways:
●Automatically via process integration, for example, from SAP Transport Management
system (part of standard system) or a legacy system.
●Manually from the user interface.
Yard Request Creation
You create a yard request for a combination of a yard number and an order type.
A yard request has the following features.
●A yard request can be activated and transformed into a yard order.
●You cannot edit a yard request once you released it.
●The system automatically assigns a number to a yard request. This is based on the
customizing of number ranges for the yard requests of a yard.
●Yard requests can be of the following types:
Unit 4: Check In and Check Out of Transportation Units
©Copyright. All rights reserved. 42Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

49. -Inbound yard requests - You create an inbound yard request, for example, when a
loaded truck enters a yard and gets unloaded there.
-Outbound yard requests - You create an outbound yard request, for example, when an
empty truck loads a container and leaves the yard.
●You can use the copy function to make a copy of a yard request. The system adjusts the
date and time to the current date and time. If the copied yard request does not contain the
default yard task, the system adds it to the yard request.
●You can select theTemplateindicator to save this yard request as a template.
A yard order represents the workload to be executed within a certain time period, based on
the planning from the yard requests.
You can create a yard order in one of the following ways:
●Activate a yard request to transform it into a yard order. You can activate a yard request
automatically or manually.
●Create a yard order manually from the user interface.
LESSON SUMMARY
You should now be able to:
●Plan in SAP Yard Logistics
Lesson: Planning in SAP Yard Logistics
©Copyright. All rights reserved. 43Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

50. Unit 4
Lesson 2
Checking Transportation Units In and Out
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Check in and check out transportation units
Check In and Check Out of Transportation Units
Figure 36: Check In and Check Out of Transportation Units
The first process step regarding yard management is the check in at the gate of the yard.
Nowadays, the yards have high security standards which are supported by camera systems,
barriers, and other security equipment. Several checks have to be executed: the yard owner
has to know who entered the yard, when they entered, and when they left. SAP Yard Logistics
2.0 supports the yard owner to answer all these questions. It ensures a consistent, digital
documentation of all data within the system — and the integration of hardware (such as scale,
barrier, camera) into SAP Yard Logistics 2.0 and the processing of that data can also optimize
and accelerate processes at check in and check out.
The check-in and check-out process is one of the most important process steps within SAP
Yard Logistics 2.0.
These process steps are used to get the respective transportation unit into and out of the
Yard Logistics system or visual yard.
During the check-in and check-out process, several functionalities of SAP Yard Logistics 2.0
can be used to optimize the execution at the gates.
©Copyright. All rights reserved. 44Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

51. LESSON SUMMARY
You should now be able to:
●Check in and check out transportation units
Lesson: Checking Transportation Units In and Out
©Copyright. All rights reserved. 45Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

52. Unit 4
Lesson 3
Handling the Arrival and Departure of
Transportation Units at the Yard
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Handle the arrival and departure of transportation units at the yard
Arrival and Departure of Transportation Units at the Yard
Figure 37: Manual Check-In
The check in of transportation units can be executed in diff erent ways within SAP Yard
Logistics 2.0: either manual, automated or via self check in.
A manual check in of transportation units can be done via desktop transaction in Yard
Logistics (for example, NetWeaver Business Client). Therefore, an employee with system user
has to book the check in using theCheck Inbutton in the yard order document. For this to be
done, all relevant data has to be entered into the yard order document: for example, driver
name, item, transportation unit type, and so on.
After the successful check in, the transportation unit will be available in the Yard Logistics
system.
The logic for the departure of a transportation unit is almost the same as for the arrival: the
check out can be executed manually or automatically.
A prerequisite for a successful check out of a transportation unit is that no more open yard
tasks for the respective transportation unit exists within the Yard Logistics system. If a
questionnaire is set up, all questions have to be answered before departure.
©Copyright. All rights reserved. 46Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

53. Automated Check-In — Example Architecture
Figure 38: Automated Check-In — Example Architecture
The opposite of manual check in is the automated check in of transportation units. The topic
of automation is getting more and more important for the business, and also for yard
processes.
By automating yard processes, process costs can be lowered and cycle times can be reduced.
The result is the reduction of process costs regarding the yard.
Due to integration capabilities into yard hardware such as camera systems, barriers, scales,
and also sensor technology, SAP Yard Logistics is driving the automation of the yard
processes.
Nearly all kinds of hardware can be integrated with SAP Yard Logistics 2.0: either direct
integration via SAP Process Integration (PI) or via SAP Cloud Platform. The communication
between the hardware and Yard Logistics or SAP Cloud Platform can be set up via
WebService, Remote Function Call (RFC), or IDOCS technology.
Example Scenario
The following is an example scenario:
1.Transportation unit arrives at the yard
2.Recognition of the transportation unit via proximity sensor
3.Activation of Optical Character Recognition (OCR)
4.Scan license plate of the transportation unit
5.Validation of license plate in SAP Yard Logistics 2.0
6.Validation positive - message from Yard Logistics to the barrier
7.Barrier opens
8.Successful check in of the transportation unit
SAP Yard Logistics 2.0 can integrate nearly every kind of hardware. It has multi vendor
capability.
Lesson: Handling the Arrival and Departure of Transportation Units at the Yard
©Copyright. All rights reserved. 47Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

54. Self Check In
Figure 39: Self Check In
One functionality in SAP Yard Logistics 2.0 for the check-in process is the so called self check
in. The self check-in functionality is a SAP Fiori-based mobile application with a guided
procedure.
Several steps must be executed by the driver, for example, on a terminal screen in front of the
gate. One important fact regarding the self check-in functionality is, that the guided
procedure can be executed in the language of the driver. Therefor, the driver has the
possibility to select his language at the beginning of the self check-in process.
After the selection of the language, the driver has to identify the relevant transport by
entering a document number. This document number be a yard order, yard request, dock
appointment number, or an ERP document number. Within the customizing of SAP Yard
Logistics 2.0 you define the reference types that are used in the Self Check-In application to
search for the yard order document. The reference type can be a customer-specific
document or any other document.
Document Examples:
●Customer contract number
●Freight order number
●Invoice number
The driver has to enter some personal data as well, for example, his name (mandatory),
mobile number (mandatory) and his company or carrier.
Additionally, he has to enter transportation unit related information, for example, the license
plate of the truck and the trailer.
Summary
The main features of the self check-in functionality are as follows:
●Guided procedure for easy use
●Free customizable transaction, supporting the following:
Unit 4: Check In and Check Out of Transportation Units
©Copyright. All rights reserved. 48Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

55. -Language Selection for Driver
-Definable selection criteria for orders
-Review and changing of document header and item information
-Completely definable Questionnaire
●No separate user needed for the driver
Additional information for the Self Check In
Additional languages can be added via Yard Logistics customizing
Document types for identification can be defined via Yard Logistics customizing
Questions for questionnaire can be defined via Yard Logistics customizing
In order to add additional languages to the Self Check-In application, initially an icon ID needs
to be bound to the yard number, language, country and Mime URL for flag icon ( Assign Mime
URL for Each Country Flag).
For more information about SAP Fiori technology, see https://www.sap.com/germany/
products/fiori.html
Figure 40: Self Check In — Questionnaire
One important functionality of SAP Yard Logistics is the questionnaire, which can be set up
for the self check in or check out. The questions for the questionnaire can be set up
individually.
This can be used to retrieve individual topics at the check-in gate: for example, "Is your
security equipment complete?", "Is there any damage to the truck or trailer?", "Do you have a
valid drivers license?", and so on.
After the driver has answered the questions with yes or no, a validation of the answers takes
place in the Yard Logistics system.
Negative-Example
1.Question: "Do you have a valid drivers license?"
2.Driver answer: "No"
3.Validation in the system: Negative
4.Self check in not successful — driver is not allowed to enter the yard
The questions for this questionnaire can be defined individually in the customizing of SAP
Yard Logistics 2.0 .
The questionnaire functionality is not only for the self check in, but also for yard tasks. The
system generates this questionnaire when you create a yard order or yard task. You must
Lesson: Handling the Arrival and Departure of Transportation Units at the Yard
©Copyright. All rights reserved. 49Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

56. answer the questions before you check in or check out the yard order, or confirm the yard
task, respectively. You can answer these questions from the yard order or yard task desktop
application, or from the Fiori UI.
The answers to the questions are stored in the Yard Logistics system.
This functionality is used to control whether all prerequisites for specific processes or yard
internal checks are met: for example, checks for the check in of a yard order or the validation
of an inspection for damages.
To set up the qestionnaire functionality in SAP Yard Logistics, the following settings must be
executed in the Customizing:
●Maintain Conditions for Questionnaire
●Define Texts for Questionnaire
●Assign Checks to Check Groups for Yard Orders
●Assign Checks to Check Groups for Yard Tasks
LESSON SUMMARY
You should now be able to:
●Handle the arrival and departure of transportation units at the yard
Unit 4: Check In and Check Out of Transportation Units
©Copyright. All rights reserved. 50Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

57. UNIT 5Yard Activities
Lesson 1
Understanding Yard Tasks 53
Lesson 2
Explaining Queue Management 58
Lesson 3
Explaining Communication 60
Lesson 4
Handling Dangerous Goods 63
Lesson 5
Performing Location Determination 65
Lesson 6
Executing Measurements 70
Lesson 7
Performing Pick-Up Planning 72
Lesson 8
Explaining Cross Docking 76
UNIT OBJECTIVES
●Understand yard tasks
●Explain queue management
●Explain communication
●Handle dangerous goods
©Copyright. All rights reserved. 51Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

58. ●Perform location determination
●Execute Measurements
●Perform pick-up planning
●Explain Cross Docking
Unit 5: Yard Activities
©Copyright. All rights reserved. 52Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

59. Unit 5
Lesson 1
Understanding Yard Tasks
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Understand yard tasks
Yard Tasks
Figure 41: Execution of Yard Activities — What is a Yard Task and How to Use It?
Within a yard, diff erent kind of activities must be executed. Yard tasks are definitions of
activities that must be done for items. They are activities that model all kinds of services on
the yard like unloading, moving a transportation unit (TU) to a storage place, cleaning a TU,
repairing a TU. The activities can be subdivided into movement and so called non-movement
activities.
Yard tasks are the key entities for planning and execution.
Before you can use the yard task in SAP Yard Logistics 2.0, you have to define the activity
types in Customizing. The activity type is used to identify which kind of activity must be
executed in Yard Logistics. The activity type specifies the basic properties of the yard task.
The most relevant properties are the movement, non-movement, or loading or unloading of
the transportation unit.
Within the activity type you have also the possibility to define whether the yard task should be
confirmed immediately. If theImmediate Confirmationflag is set, the task will be directly
confirmed after starting the yard task — no more manual action will be needed to confirm the
yard task in the system.
In Customizing for the activity type, you can also set the flag Relevant for Sub-system. If this
functionality is activated, the destination location is determined by an additional sub-system,
for example, an SAP EWM system, which is controlling the door assignment.
©Copyright. All rights reserved. 53Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

60. The destination location in the yard can be automatically determined locally in SAP Yard
Logistics 2.0 through additional Customizing options and capacity considerations. Using this
functionality, the flag Putaway Bin Determinationmust be set.
If a sealing (for example, of a trailer or container) must be checked during the execution of
yard activities, the flag Sealing Requiredcan be set for the relative activity type. If the flag is
set, additional sealing information must be entered before the confirmation of the yard task is
possible.
Additional characteristics like planned duration of the activity and default handling
instructions for the relative activity can be adjusted in the customizing for the activity type.
Movement Yard Task
A movement yard task implies that the yard task moves items (for example, truck or trailer)
between two locations (for example, parking lot and warehouse door), or is used for loading or
unloading activities.
The creation of a movement yard task requires the following information:
●An activity type
●One or multiple yard task items (including diff erent hierarchies)
●A source and destination location
●Additional planning information (such as planned start time, duration, and so on)
Non-Movement Yard Task
The non-movement yard task is used for processes like cleaning, weighing, heating, or
maintenance of transportation units. A non-movement yard task only requires a source
location to know where the task will be executed in the yard.
The creation of a non-movement yard tasks requires the following information:
●A source location, where the activity must be executed
●An activity type
●One or multiple yard task items (including diff erent hierarchies)
Internal or Yard Order-Yard Task
●Internal Yard Task: Manually created, has no reference to a yard order, can only be created
as an ad hoc yard task
●Yard Order-Yard Task: Manually or automatically created, has a reference to a yard order,
can be created via yard request or yard order planning, or as an ad hoc yard task
From its lifecycle, a yard task has the status Pending, Active, In Process and Confirmed:
●Pending:
When a yard task is created, its status is Pending.
●Active:
A yard task can be activated (status Active) when all preconditions for activation are given.
Important: The created yard tasks must be assigned to the item, which must be
processed.
Unit 5: Yard Activities
©Copyright. All rights reserved. 54Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

61. One central precondition is the availability of all assigned yard task items at the source
storage bin. Additional preconditions are that the items or transportation units are present
in the hierarchical structure and sequence as defined by the yard task item hierarchy.
●In Process:
A yard task is started (status In Process) by allocating it to a handling resource or a user
respectively. Typically, this is done via the mobile user interface when a user starts a task
from there. It can also be done from the yard task desktop transaction.
●
Confirmed:
When a yard task is finished, it must be confirmed. The confirmation can be done via
mobile user interface (SAP Fiori app) or via desktop transaction. By confirming the task, it
will be closed in the system and the posting of the transportation unit to the destination
location (in case of a movement) is done.
All changes to the involved items or transportation units are stored.
It is also possible to cancel a yard task, for example, if the yard task cannot be executed
because the trailer for the movement is damaged. If a yard task is cancelled, the status of the
yard task changes to Cancelled.
Once a yard task is created, it must be assigned to an item. For example, train items can be
the locomotive and the railcars attached to it. Each railcar can contain one or more container.
Each item has a TU type, such as truck, locomotive, railcar, or container.
Activation of the Yard Task
Once you select theActivateoption on the screen, the yard task is activated for execution.
Alternative: The system activates the first task of the yard order when you select the Start
Processingbutton on the yard order. When you activate a yard task manually, the status of
the yard task changes to Active. When a yard task is confirmed, the status of the subsequent
yard task of the same yard order changes to Active.
When a yard task is activated, you cannot edit the task any more.
Compatibility checks: Compatibility checks are carried out during activation of a yard task.
The system checks diff erent parameters, such as length or capacity of the destination
location. If the check is not successful, the yard task cannot be activated.
Stacking/Unstacking: This function can be used to check the stacking and unstacking of
transportation units on storage bins. When you are activating a yard task for stacking or
unstacking, the system executes some checks. The system only activates the yard task if
these checks are successful. The system checks whether the TU to be off-loaded is on top of
a stack or not. If the TU is not on top, the system gives an error and the yard task is not
activated.
Execution of Yard Tasks
Once the task is activated, you can select theStartoption to indicate that you are starting the
processing of the task. The system assigns the actual user to the task.
When you start the task, you can select theEditor theRejectoption. You can select
theRejectoption to reject the task, in which case the status of the task is reset to Active and
you can start the task again.
Once the task is started, you can select theConfirm option to confirm that the task is
complete.
Lesson: Understanding Yard Tasks
©Copyright. All rights reserved. 55Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

62. If you activate the task, you can select theEditoption. TheIncrease Priorityoption gets
activated. You can select this option to update the planned start time of the task. If you select
this option and the yard task is assigned to a queue, the system automatically determines the
task with the earliest planned start time.
The system maintains the start time for the current task so that it is one second earlier and,
therefore, the first task in the queue.
Exception codes: Exceptions are unexpected situations that may happen in the yard when
yard tasks are executed. You can assign an exception code to a yard task to execute the
settings associated with this exception code in case of an unexpected situation, for example,
block of destination location, or block of TU.
Attachments: If necessary, attachments can be uploaded and attached to a yard task, for
example, a photo of a damaged TU or additional documents.
Rejection of tasks: If a yard task is already started, which means status is In Process but the
execution is not possible, it can be rejected. The status changes back to Active.
Item characteristics:
●You can maintain the child to parent relationship between items.
●You can assign an icon type to a TU type in Customizing. The system displays this icon
against an item associated with this TU type. Otherwise, the system displays a default icon
for the item.
The items can be of the following types:
●Grouping Items
A grouping item serves as a grouping object in the hierarchy of items. It does not physically
exist in the yard. You can create a number of items and group them under a grouping item.
You can then assign this grouping item to a yard task. It saves you from assigning
individual items to a yard task. Grouping items serve as a logical handle to reference the
grouped items. The group can be dissolved in the yard after check in. To create a grouping
item, you have to select the TU type as one that has been defined for a group. You can
enter the TU group external ID in theTransportation Unitfield. This TU group external ID
helps you to identify the TU group. It is not mandatory for you to enter this. If you do enter
the external ID, then it should be unique in scope of a yard order.
●Non-grouping Items
These are physical objects in the yard. Non-grouping items can be of the following types:
-Carrying items: Other items can be loaded on to these items. Mostly, such items are
movable, actively or passively, for example, trucks, trailers, locomotives, or rail cars.
-Loading items: Items that can be loaded on top of other items, for example, containers.
The most complex case for yard order creation are piggyback transports. For example,
trucks that enter a yard and then are loaded onto railcars. Here, the truck is a carrying
item but is also a loading item when it is loaded onto the rail car.
Unit 5: Yard Activities
©Copyright. All rights reserved. 56Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

63. Figure 42: Execution of Yard Activities — Default Tasks
In SAP Yard Logistics, default tasks can be used to increase the level of automation within the
yard processes. Recurring yard process steps can be represented in the system by using the
functionality of default yard tasks.
When you create a yard request, the system checks whether the default tasks are defined. If
they are, the system creates the relevant tasks automatically.
You can create default tasks only for movement and non-movement activities and not for
loading activities. You can delete or edit these default tasks at any time.
In the Yard Logistics Customizing, you can define for the yard number and order type the list
and sequence of activity types and destination storage bins.
These default data is used for automatic yard task creation during the creation of yard
request or yard order.
When the flag Item Assignmentis set, the relevant items in the yard request or yard order are
automatically assigned to the default yard tasks.
LESSON SUMMARY
You should now be able to:
●Understand yard tasks
Lesson: Understanding Yard Tasks
©Copyright. All rights reserved. 57Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

64. Unit 5
Lesson 2
Explaining Queue Management
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Explain queue management
Queue Management
Figure 43: Queue Management
A queue is a logical file to which the yard tasks for processing are assigned. Queues define a
sequence of activities by which work in the yard is managed and assigned.
Queues are used to manage and distribute the work load by assignment of handling resources
(for example, shag truck, forklift) and yard tasks.
The handling resource can only execute a yard task that is allocated to the associated queue
(except if there was a manual assignment).
In Yard Logistics, a handling resource can be assigned to one or multiple queues. The user
assigns him or herself to a handling resource in the mobile. The system can also propose a
handling resource if a handling resource is maintained for the user in the master data. Then,
the system determines potential yard tasks for the user based on the queues maintained for
the handling resource.
When starting the task in the mobile transaction, the assigned user and the handling resource
take over the yard task.
The user can manually enter the handling resource for a yard task as well. In this case, the
system assigns this yard task to only this handling resource.
©Copyright. All rights reserved. 58Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

65. A yard task can be assigned to the queue either manually or automatically by the Yard
Logistics system. For the manual assignment of yard tasks to a queue, you can enter the yard
task queue value manually in the yard task. Using the automatic determination of the queue,
the system determines the queue when you save the yard task. The automatic determination
of the queue runs only for yard tasks that do not have any manual queue assignment and is
based on the activity type, source storage type and the destination storage type of the yard
task.
The automatic queue determination is based on the entries done in the Customizing of SAP
Yard Logistics 2.0.
LESSON SUMMARY
You should now be able to:
●Explain queue management
Lesson: Explaining Queue Management
©Copyright. All rights reserved. 59Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

66. Unit 5
Lesson 3
Explaining Communication
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Explain communication
Communication
Figure 44: Communication
Within Yard Logistics, the yard tasks can be transferred to the responsible worker on the yard
via SMS on a mobile device, as a text message on a pager, or on the SAP Fiori Launchpad on a
mobile device. The transfer of the data takes place when the yard task is activated. The
system assigns the yard tasks for mobile execution to a queue. You are assigned to one or
multiple queues to fetch yard tasks for execution. You can work on only one yard task at a
time.
Using SMS or pager as the communication method, the user receives an SMS with the relative
destination information (for example, the destination storage bin).
Characteristics:
●Automatic and manual task activation supports SMS sending
●Text based on standard text
●SMS can be enriched by dynamically determined information, for example, destination bin
●Text can be manually changed
●Language of the driver is used for communication
©Copyright. All rights reserved. 60Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

67. The SAP Fiori UI can be executed on any device - mobile or desktop - using the Fiori Client
application or the web browser. With this UI, the user can execute the assigned yard tasks as
follows.
In Queue mode, the system loads the yard tasks from the queue that you are assigned to and
you get the next task in the queue automatically. The queues have a unique priority. Hence,
you can view only one task at a time. Once you confirm this task, the application determines
the next yard task available for you depending on the queue priority. If the application cannot
determine any such task, the UI informs you and stays in an automatic refresh mode until a
yard task can be displayed.
In Manual Selection mode, the application displays all the tasks with status as Active or In
Process for the yard and handling resource that you have selected. You can choose a yard
task or search for yard tasks that you want to execute. At the top of the list, there is a search
control, which allows you to search for the yard task. In this mode, once you confirm a yard
task, you will return to the list of tasks. You can choose another yard task.
Fiori UI
The Fiori UI has the following structure and functionality:
●Picture Upload
The Fiori UI allows to make pictures and upload the pictures to the respective Yard Task in
SAP Yard Logistics. If you are using a mobile, you will get the option to select a picture
from your gallery or to take a picture. If you are using a desktop, you will get the option to
select and upload a picture.
●Task List
In Queue mode, the application opens the yard task in the queue. In Manual Selection
mode, it displays the yard task list.
●Task Object Header
Contains the basic information about yard task: source type, source section, source
location, destination type, destination section, and destination location.
●Overviewtab
Lists the source and destination locations of the parent transportation unit (TU),
destination level and position, handling instructions, and list of TUs with their details.
●Picturestab
Displays the picture that you have uploaded with its details. You can edit the details of the
picture or you can delete the picture from here.
●Checkstab
Answer all the questions in theChecks
tab. If you have filled in the questionnaire while
creating the yard task, the same information is defaulted here. It is mandatory to answer
all the questions.
●Measurementstab
Displays the recorded measurements. The measurement types that are displayed are
derived from the Customizing. You can enter the value for a measurement type and save
your entries.
●Sealstab
Lesson: Explaining Communication
©Copyright. All rights reserved. 61Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

68. If sealing is required, you enter the seal number for a TU and save your entries. The system
reads the requested number of seals from the Customizing settings.
●TU Detailstab
Displays the list of TUs assigned to the yard task in a TU hierarchy. You can select the level
of hierarchy that you want to view for a TU. If an item does not have a TU assigned to it,
you can assign a TU to the item and save your entries.
●Exceptionstab
Action buttons at the footer bar.
-Start- Allocates and starts the task. Sets the status of the yard task to In Process.
-Reject- Pushes the yard task back into the queue. The status of the task is reset to
Active. You can start the task again.
-
Confirm - Confirms the current task. In Queue mode, the application opens the next
task. In Manual Selection mode, it displays the yard task list.
-Set Exception- From a list you can choose a exception. The status of the task changes
to Cancelled. In Queue mode, the application opens the next task. In Manual Selection
mode, the application displays the yard task list.
●Take a Picture
ChooseTake a Picture. If you are using a mobile, you will get the option to select a picture
from your gallery or to take a new picture. If you are using a desktop, you will get the option
to select a picture.
LESSON SUMMARY
You should now be able to:
●Explain communication
Unit 5: Yard Activities
©Copyright. All rights reserved. 62Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

69. Unit 5
Lesson 4
Handling Dangerous Goods
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Handle dangerous goods
Dangerous Goods
Figure 45: Dangerous Goods
For the handling of dangerous goods in the yard, SAP Yard Logistics offers specific
functionality. If the transportation unit (TU) contains dangerous goods, it may need to be
separated from other TUs of the same yard request or yard order.
You can enter the product as a dangerous good for a yard request or a yard order.
In the case of a yard request, where two TUs must be kept separated from each other, the YL
system can execute the following:
●The system saves the yard request
●The Status of the yard request changes to Blocked
●The user interface displays a warning message
You must make changes to the dangerous goods settings either in the user interface or in the
Customizing to unblock the yard request.
In the case of a yard order where two TUs must be kept separated from each other, you
receive an error message and the system does not save the yard order.
You must make changes to the dangerous goods settings either in the user interface or in the
Customizing to save the yard order.
©Copyright. All rights reserved. 63Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

70. Determination of Dangerous Goods
The DG Data Source determines the dangerous goods data origin for the yard. This aff ects
the product of an item in a yard order.
You have the following options:
●External System
The dangerous goods master data is stored in the business object yard order. In the yard
order item Content tab, the dangerous goods fields are disabled for input. Once you check-
in the yard order, the data is stored in the business object of the transportation unit.
●EH&S
The dangerous goods master data is stored in the dangerous goods master
(transactions /SEHS/DGD03, /SEHS/HMD). In the yard order item Content tab, the
dangerous goods fields are disabled for input. Once you check-in the yard order, you can
see this data from the overview transaction of the transportation unit. It is automatically
filled from the dangerous goods master data. The system also validates the existence of
EH&S master data for the combination of product and regulation.
●Manually Maintained
The dangerous goods master data is stored in the business object yard order. In the yard
order item Content tab, the dangerous goods fields are enabled for input. Once you check-
in the yard order, the data is stored in the business object of the transportation unit.
The DG check determines whether the dangerous goods checks are applicable for the yard
number. The system checks whether the checks should be applied to the product and the
yard order when you save or enter some data in dangerous goods fields.
No Check: The system does not execute any check.
Separation Key Check: This option switches on checks based on separation keys for the
products. The Customizing required is as follows:
Separation keys are defined for Dangerous Goods Regulation. For each Dangerous Goods
Regulation, you can assign a separation key. For each separation key, you assign a Dangerous Goods Class. The class is a standard parameter and every dangerous good has a class
associated with it.
Check Rule
You assign a Check Rule Implementation Class to the Check Rule ID. You can define your own
rule in the class to determine whether the products associated with the two separation keys
should be allowed or denied together.
For example: You are running a rail yard. You have a train that has a container carrying toxic
material, and a container carrying food products. You may not want to have the container
carrying the toxic material close to the container carrying food products. Hence, the system
has to perform some checks to let you know that these two containers cannot be kept close
to each other.
LESSON SUMMARY
You should now be able to:
●Handle dangerous goods
Unit 5: Yard Activities
©Copyright. All rights reserved. 64Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

71. Unit 5
Lesson 5
Performing Location Determination
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Perform location determination
Location Determination
Figure 46: Location Determination
To utilize the yard space most efficiently, certain logic is needed that supports the movement
creation. One important topic is the determination of destination locations for movements
such as the parking of a trailer or docking to a door.
Location determination consists of multiple functionalities:
●Location determination settings
●Capacity checks
●Stacking rules
The basis for location determination is the yard structure. A storage type and the subsequent
storage bins are determined based on the activity type, TU type, and hazardous substance
data.
These storage bins will be further checked for compatibility between the transportation unit
that is to be moved and the destination storage bin type, using the transportation unit type.
As soon as a compatibility setting is maintained, only compatible TUs will be moved into
storage bins within this storage bin type.
After successful determination of potential destination bins, the available capacity of these
bins is checked against the needed capacity to store the TU that is to be moved.
©Copyright. All rights reserved. 65Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

72. This check is done based on the dimensions of the destination bin and the TUs, for example,
weight, capacity factor, or length. The first storage bin found with enough available capacity is
used as the destination location for the TUs.
The third component of the location determination are the stacking rules. These rules are only
applicable for handling of containers. The function consists of stacking level, stacking
compatibility, and stacking weight settings.
●The maximum stacking level defines the maximum number of containers stacked in a
certain storage type.
●To ensure the safety of the container stack, the stacking compatibility defines per TU type
whether they can be stacked onto another TU type or not.
●The maximum stacking weight per TU type ensures that containers that are on a lower
level in the stack are not damaged by containers stacked on top.
As soon as an error occurs during these checks, the depending storage bin is excluded from
the processing and the system continues with the next location.
Figure 47: Location Determination Settings (1)
Define at least one storage type search sequence for putaway:
●ChooseYard Logistics→Settings for Yard Tasks→Location Determination→Define
Storage Type Search Sequence for Putaway.
Assign at least two storage types to the storage type search sequence:
●ChooseYard Logistics→Settings for Yard Tasks→Location Determination→Assign
Storage Types to Storage Type Search Sequence.
Unit 5: Yard Activities
©Copyright. All rights reserved. 66Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

73. Figure 48: Location Determination Settings (2)
Define at least one storage type search for a movement activity type and a TU type:
●ChooseYard Logistics→Settings for Yard Tasks→Location Determination→Define
Storage Type Search Sequence for Activity Type and TU Type.
Define compatibility between destination storage bin type and TU type
Note:
In hierarchies, only the main item is used for location determination.
Figure 49: Capacity Checks (1)
The location determination runs during task creation and additionally to the mentioned
customizing it respects the capacity.
Capacity checks are based on the following settings:
Lesson: Performing Location Determination
©Copyright. All rights reserved. 67Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

74. ●Within a storage bin the following capacity entries can be maintained:
-Discrete Capacity
-Volume
-Weight
●Within the package material of a TU the several capacity consumption fields are defined.
Figure 50: Capacity Checks (2)
Within the yard order, we can see the relevant properties per item.
Figure 51: Container Stacking - Setting Transportation Unit Types
When stacking containers in the depot, the following checks are done:
●The stacking weight of each container has to be respected.
-The sum of the gross weight of all child TUs of a parent TU must respect the stacking
weight of the parent.
-This is checked for all TUs that are stacked.
●If a TU can be stacked at all.
Unit 5: Yard Activities
©Copyright. All rights reserved. 68Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

75. LESSON SUMMARY
You should now be able to:
●Perform location determination
Lesson: Performing Location Determination
©Copyright. All rights reserved. 69Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

76. Unit 5
Lesson 6
Executing Measurements
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Execute Measurements
Measurements
Figure 52: Measurements
It is becoming more and more important to have an end-to-end documentation of the
transport cooling chain. Therefore, you can use a functionality for measurements which can
be used to document data in SAP Yard Logistics 2.0 either manually or automatically.
For automated documentation of the measurements, a data source such as an integrated
sensor technology is needed. For example, a sensor inside a container or trailer. This sensor
can transfer data such as temperature, humidity, fuel level, or movement data to the Yard
Logistics system. It is integrated in Yard Logistics via the SAP Cloud Platform or SAP PI.
Manual documentation of measurements can be executed in the mobile UI or in the desktop
transaction (SAP Fiori Launchpad) by, for example, a yard worker.
Measurements can be added while a yard task is in status In Progress. The task needs to be in
edit mode and the respective transportation unit needs to be marked in the UI.
Measurement Entry
To enter a measurement in the mobile UI, the following prerequisites must be fulfilled:
©Copyright. All rights reserved. 70Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

77. ●The Customizing entry forDetermine Measurement Typesneeds to be maintained (it is not
optional, as it is for Desktop UI) and the task is in status In Progress. With theDetermine
Measurement TypesCustomizing, it can be predefined for which activity type and TU type
the measurement type is already shown on the yard task UI. Only the value must be
entered in this case.
●In Customizing, the respective types of measurements must be defined.
When you create a yard task with the defined yard number, activity type and transportation
unit type, the system automatically assigns a set of default measurement types to the
measurements section of the item.
The following validation is performed in regards to the yard task activation and confirmation:
If a yard task contains measurements, they are checked against the TU thresholds during
yard task confirmation. If the measurement value exceeds the threshold limit values, an alert
is raised in background. However, the yard task is confirmed as planned. Further details about
the Alert Monitor and thresholds will be discussed in the unit Yard Monitoring.
LESSON SUMMARY
You should now be able to:
●Execute Measurements
Lesson: Executing Measurements
©Copyright. All rights reserved. 71Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

78. Unit 5
Lesson 7
Performing Pick-Up Planning
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Perform pick-up planning
Pick-Up Planning
Figure 53: Pick-Up Planning Process
Pick up is an outbound process in Yard Logistics. It is used for example, if a customer orders a
specific container (identified by container number or container attributes).
Yard Logistics supports the ordering of specific transportation units as well as ordering types
of transportation units based on attributes.
The following functions are available for the pick-up process in an outbound yard request or
yard order:
●Manual creation of documents with pick-up items
●Pick-up items with known or unknown transportation unit
●Task planning for pick-up items
●Check in of pick-up items
©Copyright. All rights reserved. 72Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

79. Figure 54: Pick-up Planning: UI
Each side is output by a search form and tree list. Not all search attributes must be output. To
hide or show search attributes, choose theFilterlink button.
The transaction is enhanced by an automatic TU search feature. This means that if a yard
order item is selected in the right tree (yard order tree), the potential TUs in the left tree are
automatically filtered according to the following logic:
●Show only TUs with fitting master data attributes:
-TU type, means of transport, and packaging material
●If the Yard Order item is also classified, the classification filter is used also:
-Classification filter: The TU classifications are compared with selected yard order item
classifications.
-Only TUs with exactly the requested characteristics are shown.
-The user can switch of this classification filter.
The main purpose of this transaction is to reserve a specific TU, once it is found, for an
outbound yard order. This TU reservation can done in three diff erent ways:
●Manually, by choosingReserve TUat the TU tree list toolbar, when the TU and item are
selected
●Drag and drop functionality
●Free TU number reservation
Note:
During the TU reservation, the classifications of TU and Item are compared and if
there're some diff erences then warning messages are raised. Also it takes place
during the YT confirmation.
Lesson: Performing Pick-Up Planning
©Copyright. All rights reserved. 73Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

80. Figure 55: Pick-up Planning: Manual TU Reservation
To make a TU reservation manually, first select an active outbound yard order item, then
select a TU which you'd like to reserve for it. Next, chooseReserve TUin the tree list toolbar.
Figure 56: Pick-up Planning: Drag and Drop Functionality
To make a TU reservation by drag and drop, drag a TU and drop it at the yard order item.
Figure 57: Pick-up Planning: Free TU Number Reservation
To make a free TU number reservation, select a yard order item and chooseReserve TUin the
yard order tree list toolbar.
Unit 5: Yard Activities
©Copyright. All rights reserved. 74Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

81. Figure 58: Pick-up Planning: Yard Task Creation
A new yard task can be created with assigned TUs or yard order items, depends on whether
the selected TUs are controlled.
●If yard task creation was initiated by the yard order tree list:
-The yard order number is automatically taken over into the yard task.
-The selected yard order items are automatically added to the yard task.
●If yard task creation was initiated by the TU tree list:
-The selected TU is automatically added to the yard task.
-If the selected TU is controlled by a yard order item, then the yard order information is
automatically taken over into the yard task.
LESSON SUMMARY
You should now be able to:
●Perform pick-up planning
Lesson: Performing Pick-Up Planning
©Copyright. All rights reserved. 75Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

82. Unit 5
Lesson 8
Explaining Cross Docking
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Explain Cross Docking
Cross Docking
Figure 59: Cross Docking
If you are aiming to process products and transportation units (TUs) as efficiently as possible,
and to minimize unnecessary load transfer activities in the yard, you can use the cross-
docking process in, for example, a distribution center, warehouse, or rail yard.
Reducing the time in storage in the yard enables you to reduce stockholding costs. In the case
of cross docking, you can also optimize transportation costs.
You transport the products or handling units from check in to check out without putaway
occurring in between.
Using cross docking enables you to fulfil urgent orders, or to reduce processing and storage
costs.
In SAP Yard Logistics, the cross-docking process can be represented in the system with
predefined yard tasks, for example.
The graphic shows an example of the cross-docking process for truck and rail transport.
When the truck arrives empty at the yard, the check in is booked based on the yard order.
©Copyright. All rights reserved. 76Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

83. LESSON SUMMARY
You should now be able to:
●Explain Cross Docking
Lesson: Explaining Cross Docking
©Copyright. All rights reserved. 77Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

84. UNIT 6Yard Monitoring
Lesson 1
Using the Diff erent Tools of Yard Monitoring 79
UNIT OBJECTIVES
●Use the diff erent tools of Yard Monitoring
©Copyright. All rights reserved. 78Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

85. Unit 6
Lesson 1
Using the Diff erent Tools of Yard Monitoring
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Use the diff erent tools of Yard Monitoring
Yard Monitoring Tools
Figure 60: Yard Monitoring
The monitoring of the yard is one of the main functions within SAP Yard Logistics 2.0. By
effectively monitoring the physical movement of assets in the yard, the overall utilization of
scarce resources can be increased.
The yard is an important part of the overall network. It is more than the parking lot of a
distribution center: it serves as a connection point of inbound and outbound process flow as
well as a storage location for containers, trailers, and other means of transport. In the yard,
shipments with high priority can be identified and handled accordingly to prevent delays or
even stock-outs.
An important functionality is the visualization of the individual yard, done in the graphical 3D
yard layout. The details about how to set up the graphical yard layout is covered in the unit
Graphical Yard Layout.
To get a fast overview of the planned appointments regarding your yard, the monitoring
function Loading Appointment List can be used. The Dock Appointment Scheduling (DAS)
functionality is a standard functionality of SAP Yard Logistics 2.0. The DAS topic is covered in
the unit Cross Processes.
In theTransportation Unit Overviewof Yard Monitoring, you can search for transportation
units which are currently in the yard. Filters such as the following can be used to find a specific
transportation unit or a specific type of transportation unit on your yard:
©Copyright. All rights reserved. 79Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

86. ●Yard number
●Transportation unit
●Packaging material
●Means of transport
●Transportation unit type
●Additional external identification
●TU arrival date
●Archiving status
It is very important for the yard owners to know the current situation of their yard to react fast
in the case of unforeseeable events. For example, operators of chemical yards must know
exactly who is in the yard and what the exact location of the transportation unit or asset is, in
case of an emergency. This required information can be found in theFire Department Listof
Yard Logistics.
Within Yard Logistics, thresholds can be defined to monitor and control time- or condition-
sensitive process steps or goods on the yard. Examples for these thresholds can be as
follows:
●Planned loading/unloading time
●Temperature of a cooling trailer
●Duration of the weighing step of a transportation unit
●Duration of a movement from inbound checkpoint to a parking area
●Duration of a stay of a transportation unit in the yard
TheAlert Monitorwithin Yard Logistics enables the user to react immediately if these
thresholds are exceeded or fallen short. For example, a threshold of a cooling trailer is
exceeded by 5 degrees or the duration of a transportation unit in the yard exceeds two hours.
Figure 61: Yard Cockpit — Visual Yard
Unit 6: Yard Monitoring
©Copyright. All rights reserved. 80Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

87. The display of the yard visualization can also be used in full screen mode. You can use the
visual yard to visualize the yard and to execute movements or tasks on the yard.
It is possible to trigger a movement of a transportation unit via drag-and-drop. Doing this, the
driver or yard worker receives a notification on his mobile device (smartphone, pager, and so
on) about the triggered movement.
Settings button
Via theSettingsbutton, diff erent preferences can be maintained. For example, the display
mode of the Visual Business component. It can either be GeoMap (map is displayed as
background) or schematic view (white background).
All settings maintained here are relevant as default settings.
Refresh button
TheRefreshbutton triggers the refresh of the current state of the yard.
Flatten Buildings button If you press this button, objects currently displayed in 3D change to 2D.
Maintain and Reset Filter buttons
You can filter the TUs which are located in the Visual Yard based on some criteria.
Collada Bounds button
This button triggers the painting of boxes around Collada objects to display the full size of the
TU.
The visual yard not only displays the actual situation on the yard, but serves as working
environment as well:
●Trigger Movements (create Yard Tasks)
From the yard cockpit, you can also drag and drop a TU from one storage bin to another.
When you drag and drop, the system prompts you to create a yard task to move the TU
from one storage bin to another.
●Block Locations and Transportation Units
Locations and transportation units can be blocked and unblocked within the visual yard by
right clicking on the location or TU. Locations can be blocked for incoming and outgoing
movements, or general blocks can be set.
●Get Information about the Asset on the Yard
By right clicking on a location or an asset (transportation unit, container), you can retrieve
its details.
The following information can be retrieved for a transportation unit:
-Means of transport
-Packaging material
-TU type
-Length
-Width
Lesson: Using the Diff erent Tools of Yard Monitoring
©Copyright. All rights reserved. 81Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

88. -Height
-Loading weight of TU
-Loading weight of subitems
-Arrival day and time
-Transportation unit empty
The following information can be retrieved for a location:
-Storage bin type
-Storage type
-Storage section
-Length
-Width
Figure 62: Loading Appointment List
To get a quick overview about the booked time slots in the Dock Appointment Scheduling, the
yard monitor includes a list-based view on the available appointments regarding your yard.
You can find specific appointments, which were booked by the carrier, in Yard Logistics by
using search criteria like the following:
●Appointment number
●Status
●Docking location
●Loading point
●TU number
●Driver
●Carrier
●Created on
Unit 6: Yard Monitoring
©Copyright. All rights reserved. 82Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

89. ●Created by
●Planned arrival at checkpoint
The search results are shown in a list-based view. By clicking on the appointment number in
the list-based view, you can jump directly to the appointment.
The topic of Dock Appointment Scheduling (DAS) is covered in detail in the unit Cross
Processes.
Figure 63: Fire Department List
The Fire Department List is used to get an overview of dangerous goods or hazardous
substances that are stored in transportation units in the yard. The Fire Department List
contains a search functionality to enter search criteria and support the filtering for specific
products and transportation units.
The search criteria are as follows:
●Display only hazardous material or dangerous goods products
●Product
●Yard number
●Transportation unit
●Packaging material
●Means of transport
●Transportation unit type
●Additional external identification
●TU arrival date
●Duration of TU stay in yard (in hours)
The user can decide whether the result should contain only products that are considered as
dangerous goods or hazardous substances, or all products.
In addition, only products with no empty quantity, volume, or weight are displayed. The
searches can be saved for reuse by entering a name into theSave Search Asfield and
choosingSave.
Lesson: Using the Diff erent Tools of Yard Monitoring
©Copyright. All rights reserved. 83Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

90. Figure 64: Transportation Unit Overview
The Transportation Unit Overview is used to get an overview about transportation units in the
yard as well as related yard orders, yard tasks, thresholds (alerting), content of the
transportation units, content history, and their status.
The TU Overview contains a search functionality to enter search criteria and to allow filtering
for specific transportation units only.
Additionally, it contains tabs which are showing specific information for any row
(transportation unit) marked within the results list, such as the following:
●Content
●Content history
●Threshold
●Status
●Yard order
●Yard task
It also contains historic information about all movements and measurements that happened
in this yard for this transportation unit, even if they were linked to a diff erent order.
Unit 6: Yard Monitoring
©Copyright. All rights reserved. 84Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

91. Figure 65: Alert Monitor
You use the Alert Monitor function to raise alerts in the case of time deviations for a yard.
The time deviation could relate to one of the following business objects of the yard:
●Yard request
●Yard order
●Yard task
●Transportation unit
You also use this function to monitor alerts if any thresholds were overruled by measurement
values during yard task confirmation. The threshold must be defined in the Customizing for
SAP Yard Logistics 2.0.
When you define a threshold, either in the yard order item or in the transportation unit
directly, you can enter an alert type and a priority. The system takes this into account for the
display of the alerts.
Responsible yard workers can be informed automatically by the system by sending messages
(for example, SMS or email) about the alerts. This enables the responsible person to react
quickly to unforeseen events on the yard.
For example: A container is standing in the yard for more than 24 hours because someone
forgot to move it. In this case, we need to define time-based exceptions and checks for the
container.
LESSON SUMMARY
You should now be able to:
●Use the diff erent tools of Yard Monitoring
Lesson: Using the Diff erent Tools of Yard Monitoring
©Copyright. All rights reserved. 85Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

92. UNIT 7Cross Processes
Lesson 1
Explaining Dock Appointment Scheduling (DAS) 87
Lesson 2
Explaining Billing 92
Lesson 3
Uploading Transportation Units 97
UNIT OBJECTIVES
●Explain Dock Appointment Scheduling (DAS)
●Explain billing
●Upload transportation units
©Copyright. All rights reserved. 86Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

93. Unit 7
Lesson 1
Explaining Dock Appointment Scheduling
(DAS)
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Explain Dock Appointment Scheduling (DAS)
Dock Appointment Scheduling (DAS)
Figure 66: Dock Appointment Scheduling (DAS) (1)
You can use SAP Dock Appointment Scheduling (DAS) to plan vehicle arrivals in your yards
efficiently and to collaborate with the parties (for example, carriers, LSP) involved in an
appointment.
Planning for the Yard
Planning of vehicle arrivals at the yard, and loading and unloading of the vehicles, is important
for managing the efficient running of the yard, and for balancing the workload across the
working day. You can use SAP DAS to schedule loading appointments for loading and
unloading vehicles and to get an overview of the workload of a loading point for each day.
Planning for the Carrier
For a carrier, planning is important to reduce the amount of time when the vehicles are not
available for use, for example, if they are waiting to be unloaded. Carriers with access to the
system can plan loading appointments for their own vehicles directly in the system, and
update details of their loading appointments. By using the web portal for SAP DAS, the carrier
can book the time slots for loading or unloading at the yard.
©Copyright. All rights reserved. 87Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

94. Leading document for the DAS appointment: A leading document is a document from where
you have created the appointment. For example, you have created the appointment from a
yard request and have released the yard request. The same appointment is present in the
corresponding yard order. Here, the yard request is the leading document for that
appointment. You can create more appointments from the yard order for which the yard
order is the leading document.
You can delete an appointment only by deleting the leading document for the appointment. If
you cancel a yard order, the system deletes only those appointments for which the yard order
is the leading document. You must cancel the yard request to delete the appointments
created there. You, however, can delete an appointment manually without cancelling the
leading document.
When you create a yard request or a yard order that is DAS relevant and has a TU type
assigned that is also DAS relevant, the system automatically assigns the docking location and
loading point if a unique docking location and loading point combination is assigned to the
yard request or a yard order and TU type in the settings.
When you save the yard request or yard order, the system calls the Business Add-In /SAPYL/
BADI_ITEM_DAS_DET, which creates an appointment. You can see this appointment under
theDock Appointment Schedulingsection for an item in a yard request or a yard order. You
can click the document number of the appointment to open the appointment document.
Here, you can plan the time slots for the appointment.
Note:
You can maintain this BAdI in Customizing forBAdI: Determine Loading
Appointment Item ChangesunderSAP Customizing Implementation Guide→
Yard Logistics→Business Add-Ins (BAdIs) for Yard Logistics→Integration→
Integration to Dock Appointment Scheduling.
Item to Yard Task Assignment
If an item has only one yard task assigned to it, the system automatically assigns the
appointment for the item to the yard task. If, however, there are multiple appointments for an
item, you must manually select the appointment for the yard task.
You cannot check in a yard order for which the appointment status is Provisional. You must
plan the time slot for the appointment, which changes the status of the appointment to
Planned. Now, you can check in the yard order.
Status of an Appointment:
●Provisional - When the system creates an appointment.
●Planned - When you plan the time slot for the appointment.
●Arrived at Checkpoint - When you check in the yard order.
●Arrived at Dock - Once you confirm the yard task that moves the TU to the dock
(warehouse door).
●Departed from Dock - Once you confirm the yard task that moves the TU from the dock
(warehouse door).
●Departed from Checkpoint - Once you complete the yard order.
The following features of the DAS functionality in SAP Yard Logistics 2.0 are provided:
Unit 7: Cross Processes
©Copyright. All rights reserved. 88Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

95. ●Manual and automatic appointment creation
●Support of multiple appointments for one document
●Integration of appointment date and time into planning of yard execution
●Update of appointment during the yard processing
●Appointment monitoring in Yard Logistics
●Usage of appointment for the check-in process
Dock Appointment Scheduling (DAS) (2)
Figure 67: Dock Appointment Scheduling (DAS) (2)
At yard request or yard order item creation (or change), a loading appointment proposal is
created automatically for each item according to the settings done in Yard Logistics.
The following UI features are provided:
●A tab in theYard Order/Yard Request Itemsection contains loading appointment
information
●Supports manual loading appointment creation, deletion, and navigation to loading
appointment maintenance
●Appointment supports automatic and manual options to assign loading appointments to
task items (thereby yard task date/time is automatically adjusted)
The supported functionalities are as follows:
●DAS document created in status Provisional when saving the yard request or yard order
●All relevant data is copied from the Yard Logistic document into the loading appointment
●
All field updates done in the yard request or yard order are automatically replicated into
the DAS appointment
●Yard request or yard order references are kept within the appointment
If the yard order contains a loading appointment, check in or activation is only allowed when
all loading appointments are planned (slot assignment already executed).
Lesson: Explaining Dock Appointment Scheduling (DAS)
©Copyright. All rights reserved. 89Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

96. TheDock Appointment Schedulingtab represents the current status of the loading
appointment.
At inbound yard order check in or outbound yard order activation, the loading appointments
are updated in DAS. The status changes to Arrived at Checkpoint.
An appointment can be automatically or manually assigned to a yard task item. Only
appointments linked to the yard order and maintained in the yard task are supported.
Updates to the Appointment Status
The yard task confirmation triggers updates to appointment status:
●Destination storage type is assigned to a loading point. The appointment status is changed
to Arrived at Dock.
Actual start date and time in theDock Appointment Schedulingtab of the yard order or yard
request is updated with the Arrived at Dock date and time from the loading appointment.
●Source storage type is assigned to a loading point. The appointment status is set to
Departed from Dock.
Actual end date and time in theDock Appointment Schedulingtab of the yard order or yard
request is updated with the Departed from Dock date and time from the loading appointment.
Ad hoc yard tasks can also be linked to loading appointments, with the following features:
●Supporting a determination across all active yard orders. Only appointments in status
Arrived at checkpoint from the determined active yard orders are selected.
●Appointment field in the ad hoc yard task item is pre-filled when a single loading
appointment is found. Otherwise manual assignment needs to be done via the provided
search help and the user is notified.
The updates of the appointments work the same way as in the yard order or yard task
scenario.
At check out or completion of a yard order, all corresponding loading appointments are
checked if the loading/unloading activity has been confirmed and the status is Departed from
Dock.
The loading appointments are then completed as well.
Note:
Check-out or completion of a yard order is also possible if not all loading
appointments are Departed from Dock. All corresponding loading appointments
are set to Departed from Checkpoint.
Planned End Date and End Time
The planned end date and end time in theDock Appointment Schedulingtab of the yard order
item is updated based on Departed from Checkpoint date and time of the loading
appointment.
Required Customizing in SAP Yard Logistics 2.0:
●Maintain loading appointment relevance for yard order type
●Maintain loading appointment relevance for yard order type and transportation unit type
Unit 7: Cross Processes
©Copyright. All rights reserved. 90Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

97. ●Maintain correspondence between document categories
●Define number range intervals for appointment numbers
Required application settings in SAP Yard Logistics 2.0:
●Assign DL and LP to yard number
●Maintain door assignment to DL and LP
The integration to SAP EWM is enhanced to allow multiple warehousing SAP EWMs
connected to yard storage types represented as warehouse visits.
Warehouse Visits Generation
When a loading point proposal is generated or manually created for a docking location
assigned to a warehouse, the warehouse visit is generated automatically.
Warehouse Visits Deletion
When a loading appointment is deleted from the yard order, and a warehouse visit exists for
this appointment, a warning is raised informing the user that there is still a warehouse visit.
The warehouse visit will not be deleted automatically.
LESSON SUMMARY
You should now be able to:
●Explain Dock Appointment Scheduling (DAS)
Lesson: Explaining Dock Appointment Scheduling (DAS)
©Copyright. All rights reserved. 91Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

98. Unit 7
Lesson 2
Explaining Billing
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Explain billing
Billing
Figure 68: Solution Approach — High-Level Solution Overview
In the SAP Yard Logistics system, you can record the quantity of yard services used for the
services agreed upon in an agreement in the SAP Transportation Management (SAP TM)
system. You can subsequently send this quantity information back to the SAP TM system for
charge calculation and settlement based on the charges you agreed to in the agreement.
This enables you to perform the following:
●Sell yard services to customers and bill the customers periodically based on the services
used for a time period.
●Purchase yard services from external service providers and self-bill periodically to pay the
service provider, based on the yard services used for a time period. The function utilizes
the warehouse billing functionality of SAP Extended Warehouse Management (SAP EWM).
However, as a major restriction, SAP Yard Logistics supports only billing of yard tasks.
The general solution approach is to use and leverage existing standard functionality and
standard processes:
●Existing standard functionality in SAP TM is used for contracting, charge calculation and
settlement.
©Copyright. All rights reserved. 92Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

99. ●Existing standard functionality in SAP ERP is used for billing, self-billing, and invoice
verification processes
The yard billing process has been designed similarly to the warehouse billing process which
was introduced with SAP EWM 9.3 and SAP TM 9.3 to enable billing of warehouse services.
Figure 69: Billing Process with Integration of SAP Yard Logistics, SAP TM, and SAP ERP
Process Step 1: Create agreement (SAP TM)
Contracts are maintained as agreements in SAP TM.
●Freight agreements are used to model contracts for buying yard services from LSPs.
●Forwarding agreements represent contracts with customers (shippers) that you sell your
yard services to.
Charge calculation sheets and rates are used to maintain the agreed upon prices for the yard
services and to define the logic how the total sum is to be calculated. This is all standard SAP
TM functionality.
Process Step 2: Create warehouse billing measurement request and assign measurement
service (SAP YL)
When the agreement is released in SAP TM, the SAP Yard Logistics system automatically
creates a request for warehouse billing measurement (WBMR) from the SAP TM agreement
data.
For each charge type of the SAP TM freight agreement, a measurement request item is
created in SAP YL.
The measurement request can be displayed in the warehouse monitor in SAP YL
(transaction/SCWM/MON).
When a new agreement is created and distributed to SAP YL, the measurement request is
initially not activated. Before it can be activated a billing measurement service needs to be
assigned to each measurement request item. One measurement request item represents one
charge type of the SAP TM agreement.
A billing measurement service is used to measure the yard services and collect the relevant
business data in SAP YL. The available services are displayed below. Once a service has been
assigned, the measurement request can be activated.
Process Step 3: Collect data / record quantity of yard tasks performed (SAP YL)
Lesson: Explaining Billing
©Copyright. All rights reserved. 93Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

100. After the measurement request has been activated, the assigned services record the
quantities of the yard services provided.
The Snapshot Management functionality enables you to periodically calculate the SAP Yard
Logistics business data relevant for measuring the yard services used and to determine the
quantity of yard services used.
In release 1.0, SAP Yard Logistics supports billing of yard tasks only.
Process Step 4: Create and submit warehouse billing measurement document (SAP YL)
The recorded quantities are stored in warehouse billing measurement documents. These are
periodically created by a background job or via transaction/SCWM/WB_BM_GEN.
From the warehouse billing measurement documents, you can then send the quantity
information to the SAP TM system for charge calculation and settlement.
Process Step 5: Create service / forwarding order (SAP TM)
In SAP TM, an order document is automatically created as the basis for the charge
calculation.
●A service order is created if the charges result from a freight agreement for buying yard
services from LSPs.
●A forwarding order is created if the charges result from a forwarding agreement with a
customer (shippers) that you sell your yard services to.
Process Step 6: Calculate charges (SAP TM)
For the created service order or forwarding order, the charges are automatically calculated.
This is standard SAP TM functionality.
Process Step 7: Create and submit settlement document (SAP TM)
In SAP TM, a settlement document is created and submitted to SAP ERP.
This is standard SAP TM functionality.
Process Step 8: Service provider settlement and customer billing (SAP ERP)
In SAP TM, the billing or self-billing/invoice verification is automatically triggered.
This is standard SAP ERP functionality.
Unit 7: Cross Processes
©Copyright. All rights reserved. 94Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

101. Figure 70: Billing Scenario 1: Shipper-Owned Yard Logistics with Self-Billing Process
The figure, Billing Scenario 1: Shipper-Owned Yard Logistics with Self-Billing Process, shows
the typical shipper—owned process.
Figure 71: Billing Scenario 2: LSP-Owned Yard Logistics with Billing or Self-Billing Process
The figure, Billing Scenario 2: LSP-Owned Yard Logistics with Billing or Self-Billing Process,
shows the typical LSP-owned process.
Lesson: Explaining Billing
©Copyright. All rights reserved. 95Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

102. Figure 72: Billing Solution Approach and High-Level Technical Solution Overview
The figure, Billing Solution Approach and High-Level Technical Solution Overview gives a high-
level solution overview.
Snapshot Management
This enables you to periodically calculate the SAP Yard Logistics business data relevant for
measuring the yard services used and to determine the quantity of yard services used.
Warehouse Billing Measurement Request Management
This enables you to use the SAP TM agreement data and determine the warehouse billing
measurement services you must use.
Warehouse Billing Measurement Management
This enables you to generate warehouse billing measurement documents. The warehouse
billing measurements contain the quantity of warehouse services used. You can then send
this quantity information to the SAP TM system for charge calculation and settlement.
LESSON SUMMARY
You should now be able to:
●Explain billing
Unit 7: Cross Processes
©Copyright. All rights reserved. 96Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

103. Unit 7
Lesson 3
Uploading Transportation Units
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Upload transportation units
Upload of Transportation Units
Figure 73: Upload of Transportation Units
SAP Yard Logistics offers the functionality to upload transportation units (TU) data into Yard
Logistics from a *.csv file and to create the TUs based on data in a *.csv file on your local
system.
Features
Enter the following on the selection screen:
●Yard Number
●Local File Name- Choose the directory where the *.csv file is stored
●Test Mode- If you select this indicator, the report runs in a test mode. The report does not
create any TU in the system. The system gives a log of potential errors that can occur
during TU creation.
●Execution Mode- If you select this indicator, the report creates TUs in the system. The
system displays an ALV List with a result of TUs created. You can select theProtocol
option to display the application log with details of TUs created.
©Copyright. All rights reserved. 97Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

104. LESSON SUMMARY
You should now be able to:
●Upload transportation units
Unit 7: Cross Processes
©Copyright. All rights reserved. 98Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

105. UNIT 8Integration Capabilities
Lesson 1
Explaining the Integration to ERP, EWM and SAP TM 100
Lesson 2
Explaining the IoT integration 108
Lesson 3
Exploring the Required Set Up 116
UNIT OBJECTIVES
●Explain the integration to SAP ERP, SAP EWM, and SAP TM
●Explain the IoT integration
●Explore the Required Set Up
©Copyright. All rights reserved. 99Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

106. Unit 8
Lesson 1
Explaining the Integration to ERP, EWM and
SAP TM
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Explain the integration to SAP ERP, SAP EWM, and SAP TM
Integration to SAP ERP, SAP EWM, and SAP TM
Figure 74: Integration Capabilities
SAP Yard Logistics 2.0 enables the user to set up an end-to-end logistics platform due to the
standard integration in SAP EWM and SAP TM.
The integration with the SAP TM and SAP EWM applications for the logistics fulfillment
platform allows an efficient supply chain execution.
Moreover, integration with charge calculation and settlement in SAP TM has been built for
charging and billing the executed yard operations (see the unit Cross Processes).
SAP Yard Logistics can be flexibly used in diff erent system landscapes:
●Fully integrated with SAP TM and SAP EWM together with an SAP ERP system for end-to-
end integrated shipper scenarios
●Fully integrated with SAP TM and SAP EWM without an SAP ERP System for end-to-end
integrated logistics service provider scenarios
●Integrated with SAP TM only (with or without an SAP ERP system)
●Integrated with SAP EWM only (with or without an SAP ERP system)
©Copyright. All rights reserved. 100Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

107. ●Standalone
Outbound Supply Chain Execution Scenario
Figure 75: Outbound Supply Chain Execution Scenario with Integration of SAP ERP and SAP Yard Logistics
The graphic above gives you an overview of the functions supported by the interface between
SAP ERP and SAP Yard Logistics. The figure represents a scenario for an outbound shipment;
an inbound shipment scenario is also supported.
The communication from SAP ERP to SAP Yard Logistics uses a defined, IDoc-based
interface. This interface enables the distribution, creation, and confirmation of shipment data.
The interface is based on the shipment document in SAP ERP and on the yard request in SAP
Yard Logistics.
After finalizing the planning of the shipment, the output management in SAP ERP triggers the
creation and sending of an IDoc to SAP Yard Logistics. In SAP Yard Logistics the respective
in- or outbound yard request is created. Once the execution in the yard is completed,
shipment confirmation is sent via IDoc back to SAP ERP.
The trigger for this message is the completion of the inbound yard order or the check-out
posting of the outbound yard order.
Finalize planning of shipment in SAP ERP:
●Trigger IDoc to SAP Yard Logistics
●Create outbound yard request in SAP Yard Logistics
Check-out posting in SAP Yard Logistics triggers posting in SAP ERP:
●Send confirmation IDoc to SAP ERP shipment
●Update shipment in ERP
Available Functions for an SAP ERP Shipment
The following functions are available for an SAP ERP shipment in SAP Yard Logistics for
processing inbound and outbound yard processes:
●Processing of inbound yard processes
Lesson: Explaining the Integration to ERP, EWM and SAP TM
©Copyright. All rights reserved. 101Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

108. -Planning completion of inbound shipment in SAP ERP triggers transfer of shipment
information, including delivery data, to SAP Yard Logistics. When the shipment
information arrives in YL, it triggers the creation of an inbound yard request, which is
later converted into an inbound yard order.
-Check-in posting and further actions trigger update of the timestamps in the inbound
yard order.
-Completion of inbound yard order triggers update of the ERP shipment by transferring
relevant information to SAP ERP.
●Processing of outbound yard processes
-Planning completion of outbound shipment in SAP ERP triggers transfer of shipment
information, including delivery data, to SAP Yard Logistics. When the shipment
information arrives in YL, it triggers the creation of an outbound yard request, which is
later converted into an outbound yard order.
-Activation posting and further actions trigger update of the timestamps in the
outbound yard order.
-Check-out of outbound yard order triggers the update of the ERP shipment,
transferring the respective information.
Supply Chain Execution Scenario
Figure 76: Supply Chain Execution Scenario with Integration of SAP EWM and SAP Yard Logistics
The communication from Yard Logistics to SAP EWM uses defined interfaces, and enables
distribution, changes to, and confirmation of transportation-relevant data.
The scenario is supported for outbound and inbound shipments.
In Yard Logistics and EWM, the interfaces are based on TUs. Where necessary, SAP Yard
Logistics triggers subsequent communication steps for specific processes. The
communication is asynchronous and uses web services.
The following will describe the process shown in the graphic above:
Based on a yard request or yard order, the check in for a TU is booked within Yard Logistics. In
the same time, the check in and the door determination in SAP EWM is triggered: SAP EWM is
asked to provide a door to dock.
Unit 8: Integration Capabilities
©Copyright. All rights reserved. 102Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

109. When a depending movement to a door is created in Yard Logistics, SAP EWM is requested
which door the TU can be docked to.
Once the TU arrived at the warehouse door, a confirmation of door arrival is sent from Yard
Logistics to the SAP EWM system. After the loading of the TU is finished, SAP EWM sends the
loading or unloading confirmation to SAP Yard Logistics.
When the TU departs from the warehouse door, a message is sent from Yard Logistics to SAP EWM. The check-out posting in Yard Logistics triggers the subsequent posting in the SAP
EWM system.
The direct integration points between SAP Yard Logistics and SAP EWM are described as
the following:
Check In
●When a yard order is checked in in SAP Yard Logistics, an update is sent to SAP EWM
where the corresponding TU is automatically checked in.
●The integration for this process step as well as for all subsequent process steps is
based on the TU.
Door Determination
●After the TU is checked in in SAP EWM, a door can be automatically determined and
assigned to the TU in SAP EWM.
●Yard Logistics requests the door from SAP EWM when a depending movement to a
door is created. The door that has been determined in SAP EWM is then
communicated back to SAP YL and used as destination storage bin for the movement
yard task.
●Door determination is planned at yard task level. The following prerequisites should be
met:
-Activity type should be marked as relevant for subsystem.
-The yard task should be created with a yard order reference.
-At least one warehouse visit should be maintained for assigned yard task items.
-If only one warehouse visit is maintained for the yard task item, the destination
location is determined from corresponding EWM warehouse.
-If multiple warehouse visits are maintained for the yard task item, the destination
storage type should be entered. This storage type should be linked with one of
warehouse visits in Customizing.
Confirmation of Door Arrival
If a yard task to move a TU to a door is being confirmed, this information is automatically
passed over to SAP EWM.
The storage bin representing the door in yard logistics needs to be mapped to an SAP
EWM door. The movement yard task is the linkage to the warehouse system. The
physical loading or unloading of products is done in SAP EWM and not represented in
yard logistics.
Confirmation of Loading/Unloading
When the loading or unloading is confirmed in SAP EWM, this information is sent to Yard
Logistics.
Lesson: Explaining the Integration to ERP, EWM and SAP TM
©Copyright. All rights reserved. 103Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

110. ●For inbound orders, the goods receipt is posted and the unloading confirmed in SAP
EWM.
●For outbound orders, the loading is confirmed in SAP EWM.
Both triggers send loading or unloading information to the Yard Logistics system.
●The purpose of the loading or unloading notification is to keep TU in Yard Logistics
informed about the current state of loaded or unloaded content of an SAP EWM TU.
●When the loading or unloading of the TU is finished in SAP EWM, the notification is
sent to Yard Logistics' TU. It contains information about loading weight and loaded or
unloaded products from assigned deliveries.
During the loading or unloading process, the existing content of the TU will be
recalculated and replaced by products that are currently loaded in or unloaded from the
SAP EWM TU.
Confirmation of Door Departure
If a yard task to move a TU from a door is being confirmed, this information is
automatically passed to SAP EWM.
The storage bin representing the door in Yard Logistics needs to be mapped to an SAP
EWM door.
Check-out posting in SAP YL triggers subsequent posting in SAP EWM.
Warehouse Visit in SAP YL
In order to allow integration of Yard Logistics with external EWM systems, so called
warehouse visits should be maintained. A warehouse visit represents a combination of
external EWM system and EWM warehouse where a TU should be processed. Warehouse
visits must be defined per each yard order item in the corresponding tab before check in
or activation of a yard request. Warehouse visits can be generated automatically based
on SAP TM freight order information as well.
An SAP EWM check in/out is posted for a TU when a yard order gains control, for
example, check in or completion of inbound yard order, activation or check out of
outbound yard order.
The prerequisites for setting up the Yard Logistics to EWM integration are as follows:
●Setup of the processes in SAP EWM, Yard Management is switched off in SAP EWM.
●Maintain the following activities in Customizing underSAP Customizing
Implementation Guide→Yard Logistics→Integration→Integration to SAP
Extended Warehouse Management.
-Assign EWM Business Systems and Warehouses to Yard
-Maintain EWM Checkpoints
Situation:
●You have maintained the EWM warehouses for the EWM business systems
●linked to the yard
●that the diff erent items of the yard request/ yard order are required to be displayed in the
Warehouse Visits tab for the yard request/ yard order item.
The following settings in SAP Yard Logistics must be executed:
Unit 8: Integration Capabilities
©Copyright. All rights reserved. 104Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

111. ●Assign docking location to warehouse
●Assign external warehouse ID to storage type
●Determine EWM door
●Maintain logical ports for EWM integration
The direct integration points between SAP YL and SAP EWM are as follows:
1.Check in propagated from SAP YL to SAP EWM and door sent back from SAP EWM to SAP
YL
2.Confirmation of door arrival sent from SAP YL to SAP EWM
3.Loading confirmation sent from SAP EWM to SAP YL
4.Door departure reported from SAP YL to SAP EWM
5.Check out posting in SAP YL triggers subsequent posting in SAP EWM
Inbound Supply Chain Execution Scenario with Integration of SAP TM and SAP Yard
Logistics
Figure 77: Inbound Supply Chain Execution Scenario with Integration of SAP TM and SAP Yard Logistics
Transportation planning in SAP TM
Transportation planning is done in SAP TM. The resulting transportation plan is stored in SAP
TM using freight order documents. Freight orders specify which cargo needs to be loaded,
transported, and unloaded at which locations and at which point in time.
Creation of yard request in SAP Yard Logistics
The automatic distribution of freight orders to SAP Yard Logistics is supported for both
inbound and outbound yard requests.
The scenario is also supported if there is a SAP ERP system as predecessor system for SAP
TM in place or if a warehousing system is integrated. The yard number in SAP Yard Logistics
is then connected to a SAP EWM warehousing system.
The following describes the process shown in the figure, Inbound Supply Chain Execution
Scenario with Integration of SAP TM and SAP Yard Logistics:
1.Release freight order in SAP TM for yard handling with automatic creation or update of
yard request in SAP Yard Logistics
2.Check in and execute activities in SAP Yard Logistics
Lesson: Explaining the Integration to ERP, EWM and SAP TM
©Copyright. All rights reserved. 105Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

112. 3.Complete yard order in SAP Yard Logistics and send LDAP (LoadingAppointment)
notifications to SAP TM
The freight order data is sent via a loading or unloading instruction message from SAP TM to
SAP Yard Logistics using the LoadingAppointment (LDAP) interface.
The freight order data, which is taken over to the yard request, includes the following
information:
●Planned TUs (for example, truck and trailer); the TU number is determined based on the
registration number or container number entered in SAP TM
●Planned content of the TUs
●Planned arrival and departure date and time
●Reference documents (such as the freight order)
●Involved business partners
●Warehouse visits
The message is triggered when the user chooses the menu functionFollow Up→Send
Loading/Unloading Instructionfor a freight order in SAP TM.
This also applies updates from the freight order to SAP Yard Logistics. If changes are done to
the freight order in SAP TM, the user can trigger the loading or unloading instruction again.
The yard request is then updated in SAP Yard Logistics. These updates are supported prior to
the start of the yard processing. Once a yard request has been released, updates from SAP
TM are no longer possible.
When a freight order needs to load or unload cargo at a yard that is managed with SAP Yard
Logistics, the already available planning information from SAP TM is sent to SAP Yard
Logistics in order to plan and prepare yard handling. In SAP Yard Logistics, a yard request is
automatically created based on the freight order data sent from SAP TM.
This also applies an update from the freight order to SAP Yard Logistics. If changes are made
to the freight order in SAP TM the user can trigger the loading or unloading instruction again.
The yard request is then updated in SAP Yard Logistics. These updates are supported prior to
the start of the yard processing. Once a yard request has been released, updates from SAP
TM are no longer possible.
In case we have an integration with both SAP Yard Logistics and SAP EWM, when the loading
or unloading instructions are triggered from TM, the warehouse information is sent towards
SAP Yard Logistics, and stored for each item in theWarehouse Visitstab.
After finalizing the yard processing and check out, a loading or unloading notification is sent
from SAP Yard Logistics to SAP TM using the LoadingAppointment (LDAP) interface.
For the freight order, the actual events for arrival, loading or unloading start, loading or
unloading end, and departure are posted with their corresponding timestamps in SAP TM.
Unit 8: Integration Capabilities
©Copyright. All rights reserved. 106Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

113. Note:
There is a diff erent behavior for sending the notification to SAP TM
●The loading or unloading notification is only sent from SAP Yard Logistics to
SAP TM if there is no integrated SAP EWM system.
●In a system landscape with SAP Yard Logistics, SAP TM and SAP EWM, the
loading or unloading notification is sent from SAP EWM to SAP TM.
Integration between SAP Yard Logistics and SAP TM requires the following setup:
●Execution of integration settings as SAP TM to SAP EWM direct integration:
-
Only topics specific to SAP Yard Logistics are mentioned in the following sections.
-General setup for SAP TM to SAP Yard Logistics integration is explained in SAP Note
2380509.
●Definition of location in SAP TM:
-Including alternative location identifier for the yard
●Implementation of PPF action for Yard Logistics communication
-Separate action to send LDAP data to Yard Logistics
●Mapping Customizing in SAP Yard Logistics
-Mapping of order type, item type, and so on from SAP TM to SAP Yard Logistics
Figure 78: Summary: Direct Integration Points between SAP YL, SAP EWM, and SAP ERP
LESSON SUMMARY
You should now be able to:
●Explain the integration to SAP ERP, SAP EWM, and SAP TM
Lesson: Explaining the Integration to ERP, EWM and SAP TM
©Copyright. All rights reserved. 107Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

114. Unit 8
Lesson 2
Explaining the IoT integration
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Explain the IoT integration
Internet of Things (IoT) Integration
Figure 79: IoT Integration - Overview
The Internet of Things (IoT) is a crucial part of today's processes in running a successful
supply chain. Especially, both the assets needed to operate a yard and facilities in the yard are
nowadays already enabled with smart devices. Some major examples are containers that
send their temperature data to ensure it stays within an allowed temperature range, or a yard
gate entry facility that opens a barrier automatically to allow a recognized truck to enter the
yard. The truck has already been recognized by an OCR-based scan of its license plate, and
from that scan the corresponding yard order for check in has been determined also.
SAP Yard Logistics 2.0 offers great integration capabilities for IoT scenarios. The following list
gives examples of how IoT can be integrated with SAP Yard Logistics:
●Smart Sensors - Monitor and control all assets in the yard using standard sensor
integration
●Gate Automation - Manage your check-in processes without manual interaction through
integration of hardware such as sensors, scales, barriers or camera systems
●RFID - Manage and control all yard processes using RFID
©Copyright. All rights reserved. 108Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

115. ●Smart Filling - Connects scales, silos, and transportation assets (such as trucks)
automatically, and controls the loading process
●Drone Control - Access difficult assets or distant areas remotely using drones, and receive
immediate information about the current situation
To set up the IoT scenarios, hardware components such as sensors are necessary. The IoT scenarios described in this chapter are no part of the standard functionality of SAP Yard
Logistics 2.0, but the technical prerequisites are available in the solution.
The integration can be set up in two diff erent ways:
●SAP Cloud Platform
●Direct integration via SAP Process Integration (SAP PI)
The available communication channels are as follows:
●WebService
●IDoc
●RFC
●MII
The following features are available:
●Maintenance and registration of SAP Cloud Platform IoT-related settings directly from
Yard Logistics
●Message types
-Device types
-Devices
●Pulling data from an SAP Cloud Platform IoT service and mapping it to transportation unit
measurements
●Sending messages from Yard Logistics to an SAP Cloud Platform IoT service
Connection between Yard Logistics and a SAP Cloud Platform IoT Service
In order to establish the connection between Yard Logistics and a SAP Cloud Platform IoT
service, the destinations to the service instances (URI) must be configured.
There are two services to which Yard Logistics communicates:
●Device Management Service (DMS) - Provides control on all IoT devices with the relevant
settings (device type, message type)
●Message Management Service (MMS) - Provides access to messages received by SCP IoT
services from devices
SAP Cloud Platform is an open platform as a service (PaaS) which provides customers and
partners with in-memory capabilities, core platform services, and unique business services
for building and extending personalized, collaborative, mobile-enabled cloud applications.
SAP Cloud Platform is designed to accelerate digital transformation across your business by
enabling your organization to build the exact application you need more quickly, easily, and
economically - all without the requirement of maintaining or investing in on-premises
Lesson: Explaining the IoT integration
©Copyright. All rights reserved. 109Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

116. infrastructure. Based on open standards, SAP Cloud Platform offers complete flexibility and
control over your choice of clouds, frameworks, and applications.
Example 1: Smart Container
Figure 80: Example 1: Smart Container
A sensor inside the container transfers data such as temperature, humidity, acceleration, and
lumen to the SAP Cloud Platform (SCP). Because SAP Yard Logistics is integrated with the
SAP Cloud Platform, this data is then immediately available in real time in the SAP Yard
Logistics solution.
Using predefined thresholds in SAP Yard Logistics, this sensor data can be used to monitor
the container. For example, the sensor could be used to monitor a cold chain. This makes it
possible to react quickly if necessary. If the temperature in the container increases or
decreases beyond the defined thresholds, SAP Yard Logistics automatically notifies the
person responsible (for example, by SMS or email).
This process focuses on receiving incoming device messages (sent by a smart device on a
container, for example, sending the container's temperature) from the IoT service provided
by SCP. Then, after the data is persisted on the SCP, SAP Yard Logistics can pull that data
from the cloud and record it into the container's representation of a yard TU in the
Measurementstab.
On the SCP, no specific coding for this process is required. Only the setup of the smart device
of the container must be done. For this, in SAP Yard Logistics, you can define such smart
devices and their message interface structures and link them to a Yard TU. After the definition
of such a smart device in SAP Yard Logistics, its registration can be triggered from SAP Yard
Logistics also, since the SCP IoT services also allow remote device configuration via ODATA
services.
In more detail, the following steps need to be processed:
1.Definition of new IoT message type and its registration in SCP
2.Definition of new IoT device type and its registration in SCP
3.Definition and registration of new device
4.Configuration of mapping between message data and yard TU measurements
Unit 8: Integration Capabilities
©Copyright. All rights reserved. 110Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

117. 5.Assignment of IoT device to Yard Logistics transportation unit
6.Sending the device message to SCP using the simulation report
7.Pulling the device data from SCP with updates of measurement details of a corresponding
yard TU
A Connection to a sensor, attached to the asset and thereby automation of sensor data
recording, is possible. It supports:
●Direct update of data in the system
●Automated threshold comparison and alerting
●Support of various sensor data and scenarios
●Dynamic configuration of messages
-Supporting diff erent kind of sensors
-Configuration only, no coding
●Integration to measurement services and threshold
-Automatic data update in SAP Yard Logistics
-Immediate triggering of alerts
The benefits of setting up this scenario are:
●Immediate reporting of sensor data ensures fast reactions
●Supports avoiding critical situation
●Reduces the manual effort for the yard operators
●Increases the quality of data
●Ensures that the SLAs with the customers are kept
Example 2: Automated Yard
Figure 81: Example 2: Automated Yard
The gate in front of a yard is a very important location for the yard operator. At this place,
several steps such as weighing, checks, and the documentation of transportation or driver-
Lesson: Explaining the IoT integration
©Copyright. All rights reserved. 111Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

118. related information must be executed. This is where the decision is made about whether to
allow the transportation unit or driver to enter the yard or not . By validating the license plate
number or the carrier's name in the Yard Logistics system, the barrier opens (or not). The
integrated scale delivers an update of the truck weight in SAP Yard Logistics without any
manual process step.
To get a high degree of automation of this process, several hardware components can
support this process. In this example we are talking about the following hardware
components:
●Integrated Optical Camera Recognition (OCR)
●Integrated scale
●Integrated barrier
The automation of the check-in process supports various features, such as the following:
●
Camera-based identification of incoming and outgoing trucks
●Automatic recording of weight utilizing a weighbridge
●Barrier and traffic light control to steer the truck
●Self-check-in terminals where the driver can enter additional information
●Automatic check-in or check-out posting of trucks in the system
●Communication to drivers and employees via pager or mobiles
The benefits of the automated check-in process are the following:
●Significantly speeds up the gate processes
●Steers the traffic approaching the yard
●Ensures compliance of trucks entering the yard
●Higher quality of operation due to automated checks
●Reduces manual effort for the gate agents
Example 3: RFID
Figure 82: Example 3: RFID
Unit 8: Integration Capabilities
©Copyright. All rights reserved. 112Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

119. Within the Yard Logistics system, movements and non-movements are indicated as yard
tasks, which can be confirmed manually or automatically. The automatic confirmation of a
yard task can be done via an integrated radio-frequency identification (RFID) sensor.
Nowadays, several pagers offer integrated RFID techniques which can be used in Yard
Logistics to confirm yard tasks.
For example: The driver receives a pager when he checks in to the yard. With this pager, the
driver receives messages about his next yard task (for example, “Please drive to Door 4711”).
The same pager has an integrated RFID sensor, which also serves as an identifier. If there are
several checkpoints with RFID readers set up in the yard, the driver can identify himself at the
checkpoints (for example, an RFID reader at door 4711). Once he arrives at the door, he holds
the pager in front of the RFID reader. This step confirms the yard task automatically in the
system and the updated location of the driver is shown in the visual yard layout.
RFID based processing features:
●Supports confirmation of all kind of tasks
●Validation of scanned ID
●Easy RFID assignment during check in
●Confirmation without direct system usage
The benefits of this integration scenario are the following:
●Significantly speeds up the yard processes
●Ensures that assets are moving around in the yard as planned
●Higher quality of operation due to automated checks
●Reduces manual effort for operators
Example 4: Smart Filling
Figure 83: Example 4: Smart Filling
The smart filling scenario is mainly required at yards where bulk freight is handled. Within that
kind of yard, process steps such as the following must be executed and monitored:
●Weighing of incoming and outgoing assets
●Calculation of payload
●Control of flow of products
Lesson: Explaining the IoT integration
©Copyright. All rights reserved. 113Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

120. Without any control of these processes via connected sensors, the risk of accidents or errors
can increase.
The smart filling scenario gives an example of how IoT can support these processes and help
to avoid critical situations during the filling process. The following examples give an overview
of the automation of the filling station:
●Weighbridge handling before and after filling
●Access control to filling station
●Calculation of product to be loaded, based on weighbridge and sensor data
●Product flow control into the asset (for example, a railcar) via integrated sensors
The set up of the smart filling scenario brings the following benefits to the yard operator and
the business partners involved:
●Increases speed of operation due to automated data flow
●Automatic payload calculation takes into account real-time sensor information for optimal
loading result
●Reduction of manual errors due to avoidance of manual data entry
●Connected sensors ensure up-to-date information, and thereby high quality of operation,
combined with reduced risk of accidents
Example 5: Drone Control
Figure 84: Example 5: Drone Control
The drone control scenario illustrates how yards can be monitored using SAP Yard Logistics
and an operating drone.
It starts with additional data available in the digitized world: geographic coordinates are
transmitted from SAP Yard Logistics to the drone to navigate its way in the yard. This allows
the drone to fly autonomously to a specific place in the yard's geographical layout.
Once the drone arrives at the designated location, it can execute diff erent operations, such as
the following:
●Read a QR code or barcode
●Read an RFID chip (for example, on a sea container)
●Take a photo to document the current situation (and upload the photo automatically to the
SAP Yard Logistics' system)
Unit 8: Integration Capabilities
©Copyright. All rights reserved. 114Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

121. ●Record certain physical quantities, such as air pollution or temperature
Using the SAP Cloud Platform, the collected data can be transferred to SAP Yard Logistics,
where the data is available and can be analyzed in real time.
The technical setup and its architecture behind this is simple and easy to handle, which
ensures a smooth usage of the drone-enabled processes.
Upon activation of a yard task, the coordinates for one or several destinations of the drone are
sent to the SAP Cloud Platform. In the SAP Cloud Platform, the information is staged for pick-
up by the drone. As soon as the drone pilot picks up the coordinates, they are uploaded to the
drone and define the "flight" mission, including the tasks to be performed at the diff erent
stops during the flight. The pilot himself need not manually interact with the drone. Almost
everything works automatically — the only task is to supervise the drone's flight.
Once the flight mission is finished, the drone can start its journey and take pictures, scan
barcodes, or record values. This information is send back to the SAP Yard Logistics, via the
SAP Cloud Platform, where the depending yard task is confirmed and the information is
stored
LESSON SUMMARY
You should now be able to:
●Explain the IoT integration
Lesson: Explaining the IoT integration
©Copyright. All rights reserved. 115Librer?a ERP https://libreriaerp.com/us [email protected] Librer?a ERP https://libreriaerp.com/us [email protected]

122. Unit 8
Lesson 3
Exploring the Required Set Up
LESSON OBJECTIVES
After completing this lesson, you will be able to:
●Explore the Required Set Up
Required Set Up
Figure 85: Connection Settings - HTTP Destinations
Use transactionSM59to set up the HTTP destinations to DMS and MMS.
Figure 86: Connection Settings - Assignment to Logical System
Specify destinations configured in the previous step for Yard Logistics by assigning them to
the relevant logical system using transaction code/SAPYL/IOT_CONNECT.
©Copyright. All rights reserved. 116Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

123. Figure 87: Connection Settings - Message Management Service
Using transaction code/IWFND/MAINT_SERVICE to set up the system alias and assign it to
the gateway service/SAPYL/IOTSERVICES_MMS_SRV which is used for accessing the HCP
IoT Message Management Service.
Configuring IoT Services:
The initial configuration must be done prior to starting to use IoT services from Yard Logistics.
This configuration is done using the central transaction code /SAPYL/IOT_SETTINGS and
includes the following settings:
●Definition of message types
●Definition of device types
●Definition of devices
●Mapping incoming IoT data to TU measurements
Figure 88: Definition of New Message Type
Message types are used to define what data is expected to be received from a device. Each
message type must contain at least one field.
Every new message type must be registered in HCP IoT service before it can be used. This is
done by pressing theRegister Message Typebutton on the toolbar in edit mode.
Each registered message type gets its message type ID, which is used by Yard Logistics
during communication with HCP IoT services
Lesson: Exploring the Required Set Up
©Copyright. All rights reserved. 117Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

124. Figure 89: Definition of Device Types
Device type definition contains information about which message types a device can operate
with. At least one message must be assigned to a device. Currently, Yard Logistics supports
only the "From Device" direction.
In order to make the message type known to the HCP IoT service, it must be registered by
pressing theRegister Device Typebutton on the toolbar in edit mode. Registered device types
receive their IDs from HCP IoT.
Figure 90: Definition of Devices
The device definition represents one physical device from which the messages are received.
Devices can be assigned to Yard Logistics objects (such as transportation units).
Similar to device types and message types, devices must be registered in HCP IoT. Each
registered device gets the device ID and device token from the IoT service.
Figure 91: Mapping Incoming Data
Yard Logistics provides functionality to update TU measurement results based on information
received from HCP IoT. In order to process and save the measurement data, the mapping
must be configured using the view Assign to Measurement Types.
There are two possible scenarios which are supported:
1.Simple Scenario - One message type is mapped to one measurement record type
2.Complex Scenario - One message type is mapped to multiple measurement record types
Unit 8: Integration Capabilities
©Copyright. All rights reserved. 118Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

125. Figure 92: Assignment of Device to TU
In order to start using the IoT data, the IoT device defined in the previous step must be
assigned to a TU. This is done using transaction code/SAPYL/ASSIGN_TU.
Only one TU can be assigned per device.
Figure 93: Receiving the IoT Data
Yard Logistics provides the report which connects to HCP IoT instance and fetches the
messages received from devices. This program is accessible via transaction code/SAPYL/
IOT_DATA_PULLand can be run in either dialog mode or scheduled as a background job. The
report collects the data for transportation units which are active in the selected yard and have
devices assigned to them.
The collected information is transformed into measurement results and the corresponding
TUs are updated.
Figure 94: Sending Device Messages to HCP IoT
For testing purposes the simulation tool is provided which allows defining the content and
sending the message to HCP IoT service on behalf of selected device.
Lesson: Exploring the Required Set Up
©Copyright. All rights reserved. 119Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]

126. The simulation tool is accessible via transaction code/SAPYL/IOT_SEND_MSG.
LESSON SUMMARY
You should now be able to:
●Explore the Required Set Up
Unit 8: Integration Capabilities
©Copyright. All rights reserved. 120Librer?a ERm https://libreriaerp.com/us [email protected] Librer?a ERm https://libreriaerp.com/us [email protected]