Administration Guide | INTERNAL – Authorized for SAP Customers and Partners
Document Version: 1.0.0 – 2021-09-10
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
Administration Guide for SAP Yard Logistics for
SAP S/4HANA
THE BEST RUN
Content
1
About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1
Document History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2
Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1
Related Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2
Useful Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3
Overview of Required SAP Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.4
Getting Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3
About SAP Yard Logistics for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
3.1
System Landscape for SAP Yard Logistics for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4
Installing SAP Yard Logistics for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1
Prerequisites for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
SAP Notes for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Other Required Documents for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2
Overall Installation Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
SAP Visual Business. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
SAP Fiori Launchpad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Printing from Overview Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Mail Server for Driver Communication (SAPconnect). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Adobe Document Services for Printing of Yard Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
SAP Dock Appointment Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
SAP Information Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5
Migration Reports to Run when Upgrading from a Previous Version. . . . . . . . . . . . . . . . . . . . . 21
5.1
Migration Report: Establish Inb./Outb. S&R Activity Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2
Migration Report: Update Transportation Unit Handling Weights. . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3
Migration Report: Rebuild Transportation Unit Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4
Migration Report: Synchronize Empty Transportation Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.5
Migration Report: Convert Loading Scheme. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.6
Migration Report: Initiate TU No. for TU having Planned S&R Acty. . . . . . . . . . . . . . . . . . . . . . . . . . 23
6
Configuring SAP Yard Logistics for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.1
Technical Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Set Up RFC Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Creating a Logical and Business System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Definition of Logical System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Content
Assignment of Logical System to Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Assign Logical System and Queue Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Maintain Text Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6.2
Basic Customizing for the Yard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Creating Supply Chain Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Definition of Yard Warehouse Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Definition of Yard Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Customizing for Yard Processes (Shipping & Receiving). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Customizing of Attachment MIME Types for Yard Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.3
Yard Logistics Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting up the Yard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Settings for Transportation Units. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Yard Request and Yard Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Settings for Yard Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
6.4
Yard Logistics Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Yard Cockpit Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Handling Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Queue Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
6.5
Additional Customizing (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Stacking of Containers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Seal Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Measurements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Define Collada Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Define Classes and Methods for Checking TU Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Number Validations for Containers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Number Validations for Railcars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Customizing for Dangerous Goods/EH&S-Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Define settings for Location Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Quantity Checks during Location Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Automatic Task Assignments in Mobile Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Alerts Customizing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
External Driver Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Printing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Self-Check-In. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Questionnaire Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
6.6
Settings for Blocking and Deleting Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Settings for ILM Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Customer-specific Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78
Define Audit Areas for ILM Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Content
INTERNAL – Authorized for SAP Customers and Partners
3
Customizing Settings for Blocking and Deleting Business Partner Master Data. . . . . . . . . . . . . . 80
Define Retention Policies for ILM Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Business Partner Role and Category for Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.7
Integration with Internet of Things. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
General Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Integration to SAP IoT Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Integration to SAP IoT Services for Cloud Foundry Environment. . . . . . . . . . . . . . . . . . . . . . . . . 91
Integration to SAP IoT Services for Neo Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.8
Customizing Settings for Integration with Dock Appointment Scheduling (DAS) and SAP Logistics
Business Network (LBN). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Define Number Range Intervals for Appointment Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Define Number Range Intervals for LBN Appointments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Create Docking Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Create Loading Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Maintain Loading Appointment Relevance for Yard Order Type. . . . . . . . . . . . . . . . . . . . . . . . . . 96
Maintain Loading Appointment Relevance for Yard Order Type and TU Type. . . . . . . . . . . . . . . . .97
Assign Document Categories for Dock Appointment Scheduling. . . . . . . . . . . . . . . . . . . . . . . . 97
Assign Docking Location and Loading Point to Yard Number. . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Maintain Door Assignment to Docking Location and Loading Point. . . . . . . . . . . . . . . . . . . . . . . 98
Business Partner Category for LBN Identification Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
Control Automatic Yard Request Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.9
Customizing for EWM Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Maintain EWM Warehouse ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Maintain EWM Checkpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Assign Warehouse ID to Storage Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Determine EWM Door. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100
Assign Docking Location to Warehouse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Automatic Determination of Warehouse Visits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Define Activity Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Integration to External EWM System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101
Integration to Internal EWM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
6.10
Customizing for TM Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Map TM Freight Order Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Map TM Relevant TU Types for Yard Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Map TM Business Partner Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Map Business Transaction Document Type Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106
Map TM Timestamp to Yard Request Time Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Map External Reference Documents to YO Header Reference Documents. . . . . . . . . . . . . . . . . 107
Map External Reference Documents to YO Item Reference Documents. . . . . . . . . . . . . . . . . . . 107
4
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Content
Assign Transportation Unit Type to Packaging Material. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Integration to Plant Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
6.11
Customizing for BRFPlus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Dynamic Yard Order Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109
Dynamic Yard Task Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Dynamic Yard Document creation for Opposite Direction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111
6.12
Customizing for Berth Scheduling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Set up Optimization Function Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Define Customer-specific Attributes and Attribute Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Define Customer-specific Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Define Customer-specific Attribute Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Define Berths, Berth Positions, and Berth Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Define Ship Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Define Decision Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
7
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA. . . . . . . . . . . . . . . . . . . . . . . . . 125
7.1
Inbound Activity Management for Truck Yards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Managing Inbound Truck for Unloading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Managing Inbound Truck with Trailer for Disposal of Trailer. . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Managing Inbound Truck with Trailer for Cleaning and Loading. . . . . . . . . . . . . . . . . . . . . . . . . 132
Managing Inbound Truck with Container. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Planning Appointments for Unloading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7.2
Outbound Activity Management for Truck Yards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Managing Outbound Truck for Trailer Pick-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Managing Outbound Truck for Trailer Pick-up with Seal Numbers. . . . . . . . . . . . . . . . . . . . . . . 135
Managing Outbound Truck for Loading of Predefined Containers. . . . . . . . . . . . . . . . . . . . . . . 136
Managing Outbound Truck for Loading of Freely Selected Containers. . . . . . . . . . . . . . . . . . . . 136
Managing Outbound Planning via Pick-up Planning UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Validating Thresholds (Including Measurement Recording). . . . . . . . . . . . . . . . . . . . . . . . . . . .137
7.3
Internal Activity Management for Truck Yards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Executing Yard Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Executing Yard Tasks with Explicit Reference to an Internal Yard Order. . . . . . . . . . . . . . . . . . . . 139
Managing Yard Operations Using Mobile UI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Monitoring Yard Activities Using the Yard Cockpit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Managing Stacking and Unstacking of Containers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Determining Dangerous Goods Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Classification of Yard TUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
7.4
Internet of Things for Yard Logistics for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
8
Security Information for SAP Yard Logistics for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . 143
8.1
Other Required Documents for Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.2
User Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Content
INTERNAL – Authorized for SAP Customers and Partners
5
User Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
User Administration Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
User Data Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Authentication and Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
8.3
Role and Authorization Concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Authorization Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Standard Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
8.4
Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
8.5
Internet Communication Framework Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
8.6
Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155
Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Information Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Deletion of Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Migration Report for SAP Yard Logistics Drivers to Business Partners. . . . . . . . . . . . . . . . . . . . .161
Report to Update Start of Retention Time for Yard Documents. . . . . . . . . . . . . . . . . . . . . . . . . 161
Change Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Security for Internet of Things Geofencing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
9
Operating SAP Yard Logistics for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165
9.1
Other Required Documents for Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
9.2
Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Alert Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Error Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Workload Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .167
Interface Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Background Job Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
9.3
Administration and Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171
Starting and Stopping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Technical Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Backup and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Periodic Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Load Balancing and Scalability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178
High Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
9.4
Software Change Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
10
Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
10.1
Tips and Tricks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
11
Uninstalling SAP Yard Logistics 2021 for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
6
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Content
1
About This Guide
This guide is the central starting point for the implementation of SAP Yard Logistics 2021 for SAP S/4HANA. It
tells you how to install, configure, and operate the solution. You can also find security information, including
Data Protection and Privacy related information, in this document.
This guide addresses the following target audience:
● System administrators
● Technical consultants
● Key users
1.1
Document History
See what changes have been made to this document since it was first released.
 Note
The latest version of this document is available on SAP Help Portal at https://help.sap.com/yl_s4hana
Date
Change
September 10, 2021
Updated for Release 2021 of SAP Yard Logistics 2009 for
SAP S/4HANA
August 28, 2020
Updated for Release 2009 of SAP Yard Logistics 2009 for
SAP S/4HANA
September 27, 2019
Updated for Feature Pack 01 of SAP Yard Logistics for SAP
S/4HANA
July 31, 2018
Administration Guide for SAP Yard Logistics for SAP S/4HANA
About This Guide
Released
INTERNAL – Authorized for SAP Customers and Partners
7
2
Getting Started
Make sure to read the information in this section before you get started with the installation and configuration
of SAP Yard Logistics 2021 for SAP S/4HANA in your landscape.
2.1
Related Documents
In addition to this document, you can use the following resources to install and operate SAP Yard Logistics 2021
for SAP S/4HANA:
Content
Location
Product Assistance for SAP S/4HANA 2020
Go to https://help.sap.com/viewer/product/
SAP_S4HANA_ON-PREMISE/2020/en-US?task=dis­
cover_task and choose Product Assistance.
Product Assistance for SAP Yard Logistics 2021 for SAP S/
https://help.sap.com/yl_s4hana
4HANA
2.2
Useful Links
The following resources provide access to more information about general topics, such as software downloads,
customer incidents, or high availability.
Resource
Where to Find It
User assistance for SAP S/4HANA 2020
https://help.sap.com/viewer/product/SAP_S4HANA_ONPREMISE/2020/en-US?task=discover_task
Information about creating customer incidents
http://support.sap.com/incident
SAP Notes search
http://support.sap.com/notes
SAP Software Download Center
http://support.sap.com/swdc
Product Availability Matrix
https://support.sap.com/pam
Early Knowledge Transfer and Role-specific Learning Maps
http://support.sap.com/ekt
Sizing
https://www.sap.com/about/benchmark/sizing.html
8
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Getting Started
Resource
Where to Find It
Information about support package stacks, latest software
http://support.sap.com/sp-stacks
versions and patch level requirements
SAP Fiori Deployment Options and System Landscape Rec­
ommendations
2.3
https://www.sap.com/documents/2018/02/f0148939f27c-0010-82c7-eda71af511fa.html
Overview of Required SAP Notes
The following SAP Notes are essential for installing, upgrading, and operating SAP Yard Logistics for SAP S/
4HANA.
 Note
The SAP Notes relevant for installation and upgrade are also listed in the respective sections in this guide.
Make sure that you have the latest version of each SAP Note, which is available on SAP Support Portal at
http://support.sap.com/notes .
SAP Note Number
Title
Description
SAP Note 2230296
Release strategy for the ABAP add-on
This SAP Note contains information
SAP Yard Logistics for SAP S/4HANA,
about planning the installation and up­
component SAPYL
grades of the ABAP add-on SAPYL
SAP Note 2230295
SAP Note 2217489
Release strategy for the ABAP add-on
This SAP Note contains information
SAP Yard Logistics for SAP S/4HANA,
about planning the installation and up­
component SAPYLUI
grades of the ABAP add-on SAPYLUI
Maintenance and Update Strategy for
This note describes the dependencies
SAP Fiori Frontend Server
for the UI specific part (component SA­
PYLUI 400)
SAP Note 2644763
FPM: Visual Business and the SAPUI5
based 3D control
SAP Note 2834250
FPM VisBiz GUIBB: Performance Im­
provement
SAP Note 2644803
WDA: FLP integration: create object of
class CL_WDR_NW7_FLP_ADAPTER
two times
SAP Note 2658930
Correction for Unified Rendering
SAP_UI NW752 TCI 1807
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Getting Started
INTERNAL – Authorized for SAP Customers and Partners
9
SAP Note Number
Title
SAP Note 2670548
Correction for Unified Rendering
Description
SAP_UI NW752 TCI 1808
SAP Note 2692809
Correction for Unified Rendering
SAP_UI NW752 TCI 1810
SAP Note 2777615
Extreme number of
LCL_NODE=>LIF_INITIAL­
IZE~GROUP_INIT calls in trace
3094933
Implementation information about the
integration of SAP Yard Logistics for
SAP S/4HANA and Plant Maintenance
3094768
Implementation information about the
integration of SAP Yard Logistics for
SAP S/4HANA and external warehous­
ing EWM in SAP S/4HA
3093894
Implementation information about the
integration of SAP Yard Logistics for
SAP S/4HANA and TM modeled ASR in
SAP S/4HANA
3093893
Implementation information about the
integration of SAP Yard Logistics for
SAP S/4HANA and internal warehous­
ing EWM in SAP S/4HA
3095553
Implementation information about the
integration of SAP Yard Logistics for
SAP S/4HANA and SAP IoT for geo­
fencing based processing
2.4
Getting Support
If you encounter any problems with SAP Yard Logistics for SAP S/4HANA, report an incident on SAP Support
Portal.
To report an incident, go to SAP Support Portal at http://support.sap.com/incident . The relevant
component is SCM-YL for business functionality and SCM-YL-FIO for SAP Fiori-related incidents.
10
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Getting Started
3
About SAP Yard Logistics for SAP S/
4HANA
This section provides an overview of SAP Yard Logistics for SAP S/4HANA, including relevant business
scenarios and technical system landscape.
3.1
System Landscape for SAP Yard Logistics for SAP S/
4HANA
This section describes the technical system landscape and the software components involved.
This section describes the technical system landscape and the software components involved.
The following figure provides an overview of the system landscape for SAP Yard Logistics for SAP S/4HANA.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
About SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
11
The following software components are either required or optional, as indicated below, for the technical
implementation of SAP Yard Logistics for SAP S/4HANA.
Business Scenario: Inbound Activity Management for Truck Yards
Software Component
Required or Optional
SAP S/4HANA 2020
Required
SAP Yard Logistics for SAP S/4HANA
Required
SAP Yard Logistics for SAP S/4HANA – UI
Required
UI for SAP S/4HANA
Optional (required for the Fiori Tiles for the S/4HANA appli­
cations, like warehousing, transportation management, EHS,
etc.)
Business Scenario: Outbound Activity Management for Truck Yards
Software Component
Required or Optional
SAP S/4HANA 2020
Required
SAP Yard Logistics for SAP S/4HANA
Required
SAP Yard Logistics for SAP S/4HANA – UI
Required
UI for SAP S/4HANA
Optional (required for the Fiori Tiles for the S/4 HANA appli­
cations, like warehousing, transportation management, EHS,
etc.)
Business Scenario: Internal Activity Management for Truck Yards
Software Component
Required or Optional
SAP S/4HANA 2020
Required
SAP Yard Logistics for SAP S/4HANA
Required
SAP Yard Logistics for SAP S/4HANA – UI
Required
UI for SAP S/4HANA
Optional (required for the Fiori Tiles for the S/4 HANA appli­
cations, like warehousing, transportation management, EHS,
etc.)
For managing internal yard tasks in the yard cockpit, the software component SAP Visual Business 2.1 needs to
be installed per SAP GUI on the business user’s local PC or laptop (thiis is required if you are using ActiveX for
rendering your Yard Cockpit).
12
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
About SAP Yard Logistics for SAP S/4HANA
Related Information
Installation and Setup
Administration Guide for SAP Yard Logistics for SAP S/4HANA
About SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
13
4
Installing SAP Yard Logistics for SAP S/
4HANA
This section provides information about how to prepare for installation and what to do before and after the
installation of SAP Yard Logistics for SAP S/4HANA.
4.1
Prerequisites for Installation
This section lists the prerequisites that must be met before you start installation. SAP S/4HANA1909 (software
component S4CORE) must be installed. If you choose the Gateway Central Hub deployment option, then,
depending on the SAP Fiori system setup, you may have to install SAP Frontend Server 4.0 as a separate
system (see section Useful Links [page 8]). For managing internal yard tasks in the Yard Cockpit the software
component SAP Visual Business 2.1 needs to be installed per SAP GUI on the business user's desktop or laptop
(this is required if you are using ActiveX for rendering your yard cockpit).. To have the latest semantic object
definitions, you must install the software component SAP_UI 754 SP02 or greater on the FES system.
Related Information
Useful Links [page 8]
4.1.1 SAP Notes for Installation
Read the following SAP Notes before you start installation. These SAP Notes contain the latest installation
information, as well as any corrections.
 Note
Make sure that you have the latest version of each SAP Note, which is available on SAP Support Portal
http://support.sap.com/notes
SAP Note Number
Title
Description
2507107
SAP NWBC ABAP Runtime Patch 60
System runtime correction
14
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Installing SAP Yard Logistics for SAP S/4HANA
SAP Note Number
Title
Description
2565494
WDA: Program termination if the class
Corrects SAP Fiori Launchpad usage
CL_WD_FLP_API is not used in the FLP
environment
2567046
Wrong messages in system alias check
Corrects SAP Fiori System Alias
report
2644803
WDA: FLP integration: create object of
Corrects endless loop in SAP Floorplan
class CL_WDR_NW7_FLP_ADAPTER
Manager
4.1.2 Other Required Documents for Installation
In addition to this guide, you need the following resources to install SAP Yard Logistics for SAP S/4HANA.
Document
Where to Find It
Installation Guide for SAP S/4HANA 1709 or greater
https://help.sap.com/viewer/product/SAP_S4HANA_ONPREMISE/1709/en-US?task=discover_task
SAP Fiori launchpad in SAP NetWeaver AS for ABAP 7.54
https://help.sap.com/viewer/p/SAP_FIORI_LAUNCHPAD
SAP Fiori Apps Reference Library
https://fioriappslibrary.hana.ondemand.com
SAP Fiori Technology and SAP Fiori Overview, chapter “SAP
https://help.sap.com/viewer/p/FIORI_TECHNOLOGY
Fiori: Setup and Configuration”
SAP NetWeaver Application Server for ABAP 7.54
https://help.sap.com/viewer/p/SAP_NETWEA­
VER_AS_ABAP_752
SAP Visual Business 2.1, chapter “SAP Visual Business 2.1
https://help.sap.com/viewer/p/SAP_VISUAL_BUSI­
NESS_2.1
Installation and Configuration Guide”
SAP Fiori Deployment Options and System Landscape Rec­
https://www.sap.com/documents/2018/02/f0148939-
ommendations
f27c-0010-82c7-eda71af511fa.html
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Installing SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
15
4.2
Overall Installation Sequence
This section provides detailed instructions for installing SAP Yard Logistics for SAP S/4HANA.
Installation Sequence of the Add-on:
Step
Action
Remarks/Subsequent Steps
1
Installation of SAP S/4HANA 1709 or
http://help.sap.com/s4hana_op_1709
1809
2
Installation of User Interface Technol­
ogy 7.54 (SAP_UI software component),
Version 754 SP02 or higher
3
Installation of SAP Yard Logistics for
SAP S/4HANA
4
5
6
Installation of SAP Yard Logistics for
Necessary if you use the embedded
SAP S/4HANA – UI
system option for the FES 4.0 or 5.0
Installation of Visual Business 2.1 (local
Necessary only if you use the visual
SAP GUI installation)
yard cockpit
Install the required noes mentioned in
chapter 4 above
Installation Sequence - Add-on installation of SAP Yard Logistics for SAP S/4HANA UI on FES.
Step
Action
Remarks/Subsequent Steps
1
Installation of SAP Front end server 5.0
See SAP Fiori Technology and SAP Fiori
Overview, chapter “SAP Fiori: Setup
and Configuration”
2
Installation of User Interface Technol­
ogy 7.54 (SAP_UI software component),
Version 754, SP02 or higher
3
4
5
Installation of SAP Yard Logistics for
Necessary if you use the Gateway cen­
SAP S/4HANA – UI
tral hub system option for the FES 5.0
Installation of Visual Business 2.1 (local
Necessary only if you use the visual
SAP GUI installation)
yard cockpit
Install the required noes mentioned in
SAP Notes for Installation [page 14].
16
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Installing SAP Yard Logistics for SAP S/4HANA
 Caution
As the Shipping and Receiving application in SAP EWM defines the Transportation Units warehouseindependent, the business system of SAP Yard Logistics for S/4HANA and the warehousing software
component (namely SAP EWM or the extended warehousing management in SAP S/4HANA 1709 or
higher), must be different as well.
 Caution
SAP Yard Logistics for SAP S/4HANA only supports a local deployment of SAP Dock Appointment
Scheduling on the same system.
4.2.1 SAP Visual Business
In this solution, the yard cockpit graphical visualization is based on SAP Visual Business, which is a technical
component for 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 different types of content, but also include
interactive graphics that visualize and combine enterprise data with three-dimensional representations.
There are two different client implementations of SAP Visual Business that you can choose between for
displaying your yard cockpit in SAP Yard Logistics for SAP S/4HANA; SAP Visual Business 2.1 (ActiveX Plug-In)
and SAP Visual Business (SAPUI5).
SAP Visual Business 2.1 (ActiveX Plug-In).
The SAP Visual Business front-end component used on the SAP Yard Logistics' FPM user interface is a client
component. The client-side installation is integrated into the SAP front-end installer, also known as SAPSetup,
which is available for download from the SAP Support Portal .
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.
SAP Visual Business (SAPUI5)
The SAP UI5 control for SAP Visual Business does not require any separate installation, but needs the
appropriate UI5 stack in the system to run properly. Refer the following table for more information:
SAP UI5 Version
SAP Note No.
Description
UI5 1.71.17
2856654
ABAP SAPUI5 1.71 release
UI5 1.65.16
2802680
ABAP SAPUI5 1.65 release
UI5 1.60.27
2711925
ABAP SAPUI5 1.60 release
UI5 1.52.42
2550980
ABAP SAPUI5 1.52 release
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Installing SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
17
For further information, see:
● SAP Visual Business documentation on the SAP Help Portal at: https://help.sap.com/viewer/
50d59fa70a4544239619259ca8efc2ec/7.51.10/en-US/6e6cfdb0d20946d591eb620c906a4784.html
● Application Help of SAP Visual Business 2.1 at http://help.sap.com/visualbusiness21
● Administration and Configuration topics at http://scn.sap.com/docs/DOC-54524
4.2.2 SAP Fiori Launchpad
The SAP Fiori Launchpad is the entry point for Fiori apps via desktops and on mobile devices. To access these
apps, you must configure SAP Fiori Launchpad so that your users can access the apps that have been assigned
to their respective roles.
For detailed information about the configuration tasks for the SAP Fiori Launchpad, see the following
documentation:
For using Fiori Launchpad on SAP NetWeaver 7.54, go to SAP Help Portal at https://help.sap.com/viewer/
product/SAP_NETWEAVER_750/7.5.4/en-US, and under Application Help, choose
NetWeaver
SAP Fiori Launchpad
UI Technologies in SAP
Setting Up the Launchpad .
 Caution
SAP Fiori Search is not supported in SAP Yard Logistics for SAP S/4HANA.
4.2.3 Printing from Overview Lists
If you want to use the print functionality from the overview lists of yard orders, yard requests and yard tasks
(button Print Version), you must install and configure the printing services, for example, ADS, as described in
1413938 WD ABAP ALV – Creating print version
4.2.4 Mail Server for Driver Communication (SAPconnect)
SAPconnect offers a uniform interface for external communication that supports sending using
telecommunication services such as fax, text messaging (pager/SMS), and e-mails. In SAP Yard Logistics, it is
used to send a short message service (SMS) for driver advice after the check-in of a Yard Order document.
More Information
You find this documentation for SAP NetWeaver 7.52 on the SAP Help Portal. Go to SAP Help portal at https://
help.sap.com and choose Application Help, then go to
Application Server ABAP
Other Services . Select
Function-Oriented View
Application Server
Services for Business Users
SAPconnect .
● Transaction SCOT for setup of SAPconnect
18
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Installing SAP Yard Logistics for SAP S/4HANA
● Transaction SOST for monitoring of SMS sent
● SAP Note 455140 for Configuration of e-mail, fax, paging/SMS via SMTP
SAP Note 552616 for FAQ on SAPoffice – Sending to external recipients
4.2.5 Adobe Document Services for Printing of Yard
Documents
To be able to print the yard-related PDF forms for yard orders, yard tasks, and yard TU’s, the Adobe® Document
Services (ADS) has to be activated in the SAP Yard Logistics system. These ADS services provide a range of
form and document creation and manipulation functions. Adobe® Document Services enhance the document
handling capabilities of SAP Web Application Server (SAP Web AS). Adobe® Document Services allow SAP
applications (either Java or ABAP) to take advantage of the full range of capabilities in Adobe Acrobat®
Professional, Adobe® Acrobat Standard, and Adobe Reader®. These capabilities enable you to:
● Create and deploy interactive forms that look exactly like their paper counterparts
● Generate dynamic PDF documents from data contained in the SAP system
● Embed other file formats inside PDF documents as attachments
For the configuration of the ADS Services, refer 894009 – Adobe™ Document Services: Configuration
4.2.6 SAP Dock Appointment Scheduling
SAP Dock Appointment Scheduling can be deployed as an integrated solution with a local SAP Yard Logistics
for SAP S/4HANA. As a prerequisite, the specific roles for SAP DAS must be added to the roles of the SAP Yard
Logistics for SAP S/4HANA to be able to perform a simple setup of SAP DAS. Go to https://help.sap.com/
EWM95, click on Application Help and choose →
SAP Extended Warehouse Management
SAP Dock
Appointment Scheduling . On the page, follow the link for Roles of Dock Appointment Scheduling. In the
context of SAP Yard Logistics for SAP S/4HANA, we use the SAP DAS as a standalone application as we start
the creation of appointments based on Yard Request and Yard Order items (each yard document item allows
multiple appointments for different docking locations and loading points). Therefore, the setup for SAP DAS
with SAP EWM using the transportation unit as a reference object is not necessary for SAP Yard Logistics
setup. Once the simple setup of the standalone SAP DAS has been executed, (you can find that under Settings
→ Simple Setup for the DAS Administrator's menu), you can assign for a specific yard several docking locations
and loading points. Based on this assignment, the arrival and departure at checkpoint events in the DAS
appointment are updated.
In addition to that, this solution allows the assigning a yard specific "door" storage type to a docking location
and loading point. Once a yard task is targeting to such a storage type or targeting from such a storage type,
the arrival and departure at dock events in the DAS appointment are updated based on the appointment that is
assigned to this yard task.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Installing SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
19
4.2.7 SAP Information Lifecycle Management
You use the Retention Management functions of SAP NetWeaver Information Lifecycle Management (ILM) to
manage the lifecycle of the data of a live application system from its creation (database) to its destruction
(database or ILM store). Since transferred data remains accessible and the periods required by law can be
adhered to, you can regularly store data that is no longer required for operations in the ILM store and optimize
the data volume in your system.
ILM Retention Management offers the following functions:
● Putting legal holds on data that is relevant for legal cases so it cannot be deleted or destroyed. Legal holds
affect the data in the database as well as the data in the ILM store.
● Grouping data objects that are to be stored or queried together in audit areas.
● ILM rules for time-based management of data objects, for the following purposes:
● Restriction of the retention period for reasons of data protection
● Adherence to legal requirements for retention periods for tax auditing and product liability purposes.
● Deleting data for which the retention period has expired and for which there is no legal hold.
● To activate SAP ILM, you need to set the central switch ILM in Customizing for business functions.
 Note
See Using ILM Retention Management in the Application System at https://help.sap.com/viewer/
35d6f7d8cbd04dbf997ca36785c7a795/1709%20002/en-US/
09ec83476f0942bcaea4481bc02ddf23.html?q=Using%20Retention%20management
20
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Installing SAP Yard Logistics for SAP S/4HANA
5
Migration Reports to Run when
Upgrading from a Previous Version
You must execute the following migrationn reports when you upgrade your SAP Yard Logistics for SAP S/
4HANA instance to the current version:
● Migration Report: Establish Inb./Outb. S&R Activity Relationships (/SAPYL/MIGRATE_INOUT)
● Migration Report: Update Transportation Unit Handling Weights (/SAPYL/TU_WEIGHT_MGR)
● Migration Report: Rebuild Transportation Unit Sequence (/SAPYL/SEQ_MIGRATION)
● Migration Report: Synchronize Empty Transportation Units (/SAPYL/SYNC_TU_EMPTY)
● Migration Report: Convert Loading Scheme (/SAPYL/LOAD_SCH_MIGR)
● Migration Report: Initiate TU No. for TU having Planned S&R Acty (/SAPYL/TU_INIT_UPD)
You find the reports under transaction NWBC
Master Data
Migration Tools .
Related Information
Migration Report: Establish Inb./Outb. S&R Activity Relationships [page 21]
Migration Report: Update Transportation Unit Handling Weights [page 22]
Migration Report: Rebuild Transportation Unit Sequence [page 22]
Migration Report: Synchronize Empty Transportation Units [page 23]
Migration Report: Convert Loading Scheme [page 23]
Migration Report: Initiate TU No. for TU having Planned S&R Acty [page 23]
5.1
Migration Report: Establish Inb./Outb. S&R Activity
Relationships
Run transaction /SAPYL/MIGRATE_INOUT to execute this migration report to establish UUID keys between
yard order items of active or completed internal yard order or outbound yard order documents and the related
S&R activities.
This report establishes the UUID key within the yard order item of the internal / outbound yard order document
having statuses Active or Completed, with the relevant S&R Activity. SAPYL release 400 now stores a link
between internal / outbound yard order items and related S&R Activities in order to support new functionality.
The report output contains a summary of the execution results and a link to the detailed output log.
This report must be executed during migration from SAPYL release 300 to release 400.
Prerequisites:
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Migration Reports to Run when Upgrading from a Previous Version
INTERNAL – Authorized for SAP Customers and Partners
21
● You must have authorization to run /SAPYL specific functions.
● You must run this report in case of /SAPYL release migration: from 300 to 400.
Selection
You enter a yard number for handling. If you don't specify a yard number, all yards in the system will be
processed. It is highly recommended to process yards individually.
The report offers two run modes:
● Test mode - No changes are saved.
● Execution mode - all changes are saved.
5.2
Migration Report: Update Transportation Unit Handling
Weights
Run transaction /SAPYL/TU_WEIGHT_MGR and execute this report to convert old handling weight values to
new ones. If previous weight values do not exist, the packaging material values are considered.
Selection:
● Yard Number
● Test Mode
5.3
Migration Report: Rebuild Transportation Unit
Sequence
Run transaction /SAPYL/SEQ_MIGRATION and execute this report to create/update records in the database
table /SAPYL/T303ADD based on records in database table /SAPYL/SBTPVOTP and to clean up the successor
and predecessor fields in the fetched S&R Activities for those instances where the storage bin assigned to
storage bin type has a position type like Unsorted applied to the bin.
Selection:
● Yard number
● Test mode
22
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Migration Reports to Run when Upgrading from a Previous Version
5.4
Migration Report: Synchronize Empty Transportation
Units
Run transaction /SAPYL/SYNC_TU_EMPTY and use this report to migrate the TU Empty flag for old data in the
system that was created before the Search by TU Empty function was introduced. You do not need to run this
report for new TUs.
In order to make the TU overview application search available via the TU Empty status, the TU Empty flag
needs to be saved in the database.
Eelect the yard number for which you want to do the migration. A test mode is also provided.
5.5
Migration Report: Convert Loading Scheme
Run transaction /SAPYL/LOAD_SCH_MIGR and use this report to convert old loading schemes to new ones by
yard number.
You can run this report in test mode to verify the results before executing it in production mode.
5.6
Migration Report: Initiate TU No. for TU having Planned
S&R Acty
Run transaction /SAPYL/TU_INIT_UPD and use this report to update TUs in the Yard Logistics system that
have S&R activities in status Planned.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Migration Reports to Run when Upgrading from a Previous Version
INTERNAL – Authorized for SAP Customers and Partners
23
6
Configuring SAP Yard Logistics for SAP
S/4HANA
The following describes how to configure SAP Yard Logistics for SAP S/4HANA and shows the different
customizing possibilities for the solution. Configuration steps consist of:
● Technical Customizing
● Basic Customizing for Yard Set up - Truck Yard
● Customizing for other yard types, for example, rail yards (optional)
● Additional Customizing settings for integration with SAP Dock Appointment Scheduling, SAP Extended
Warehouse Management and/or SAP Transportation Management, and Customizing for IoT scenario
6.1
Technical Customizing
6.1.1 Set Up RFC Connection
Process for setting up required RFC Connection.
6.1.1.1
Set up RFC User
It is assumed, that the respective user ALEREMOTE already exists.
To verify, go Tools to AdministrationUser Maintenance
transaction SU01D for this purpose.
6.1.1.2
SAP Easy Access
Set Up RFC Destination
In Customizing for SCM Extended Warehouse Management choose
for Creating the System Landscape
24
Display Users . You can also use
SCM Basis
Integration
Basic Settings
Set Up RFC Destination
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Maintain the following entry:
Set Up RFC Destination
e.g. XXXCLNT100
Connection Type
3 (ABAP Connection)
Target Host
Your target host
Instance No.
Your instance no.
Save As
IP Address
User
ALEREMOTE
Trust Relationship
Yes
6.1.2 Creating a Logical and Business System
6.1.2.1
Definition of Business System Group
In Customizing for SCM Extended Warehouse Management choose
Settings for Creating the System Landscape
entry:
SCM Basis
Maintain Business System Group
Integration
Basic
and maintain the following
Business System Group
Description
e.g. XXX_BG1
SAPYL Business System Group
6.1.3 Definition of Logical System
In Customizing for SCM Extended Warehouse Management choose
Settings for Creating the System Landscape
Name Logical Systems
SCM Basis
Basic
and maintain the following entry:
Logical System
Name
e.g. XXXCLNT100
Yard Logistics – Client 100
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Integration
INTERNAL – Authorized for SAP Customers and Partners
25
6.1.4 Assignment of Logical System to Client
In Customizing for SCM Extended Warehouse Management choose
Settings for Creating the System Landscape
SCM Basis
Integration
Basic
Integration
Basic
Assign Logical Systems to a Client .
Maintain the following entry:
Client
Logical System
100
XXXCLNT100
6.1.5 Assign Logical System and Queue Type
In Customizing for SCM Extended Warehouse Management choose
Settings for Creating the System Landscape
following entry:
SCM Basis
Assign Logical System and Queue Type
and maintain the
Business System Group
Logical System
Release
Queue Type
XXX_BG1
XXXCLNT100
70
I (Inbound Queues)
6.1.6 Maintain Text Schema
In Customizing for Cross-Application Components choose
Reusable Objects and Functions for BOPF Environment
Processes and Tools for Enterprise Applications
Dependent Object Text Collection
Maintain Text
Schema .
In the Dialog Structure, switch to “Text Type”. Ensure, that the following entries are maintained there.
Text Type
Description
COMM
Comment Text Type
DFLT
Standard Text Type
HNDL
Handle Instruction Text Type
In the Dialog Structure, switch to “Text Schema”. Ensure, that the following entries are maintained there.
26
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Text Schema
Description
/SAPYL/YO
Yard Order Text Schema
/SAPYL/YT
Yard Task Text Schema
For Text Schema /SAPYL/YO:
Mark the entry /SAPYL/YO and double-click in the Dialog Structure on Text Type to Text Schema Assignment.
Ensure that the following entries are maintained there.
Text Type
Mandatory
Internal
Lang. Text
Access Seq.
Reference
Exit Class
HNDL
Mark the entry /SAPYL/YO and double-click in the dialog Structure on Assign Text Schema to BO and Node.
Ensure that the following entries are maintained there.
Business Object Name
BO Node Name
/SAPYL/YARD_ORDER
ITEM
Business Entity
Txt Schema
/SAPYL/YO
For Text Schema /SAPYL/YT:
Mark the entry /SAPYL/YT and double-click in the Dialog Structure on Text Type to Text Schema Assignment.
Ensure that the following entries are maintained:
Text Type
Mandatory
Internal
Lang. Text
Access Seq.
Reference
Exit Class
HNDL
Mark the entry /SAPYL/YT and double-click in the dialog Structure on Assign Text Schema to BO and Node.
Ensure that the following entries are maintained there.
Business Object Name
BO Node Name
/SAPYL/YARD_TASK
ROOT
6.2
Business Entity
Txt Schema
/SAPYL/YT
Basic Customizing for the Yard
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
27
6.2.1 Creating Supply Chain Units
On the Fiori Launchpad,
Master Data
General Settings
Maintain Supply Chain Unit .
You must maintain a supply chain unit as a prerequisite for your warehouse.
Supply Chain Unit
Type
SCU_TRUCK
1008 (Warehouse)
Choose button Create.
In Description field, enter Supply Chain Unit for Truck Yard
On the Address tab, maintain the following settings:
Country
DE (Germany)
On the Alternative tab, maintain the following entry:
Bus.Attri.
Description
INV
WAREHOUSE
Save your entries.
6.2.2 Definition of Yard Warehouse Numbers
6.2.2.1
Definition of Warehouse Numbers
In Customizing for Yard Logistics, choose
Master Data
Setting up the Yard
Define Warehouse
Numbers .
Maintain the following entry.
Warehouse No.
Description
TRCK
Truck Yard
28
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.2.2.2
Definition of Warehouse Number Control
In Customizing for Yard Logistics, choose
Master Data
Setting up the Yard
Define Warehouse Number
Control .
Open the entry of your Warehouse Number by double-clicking on it.
Maintain the following entries:
Weight Unit
Volume Unit
Currency
Time Unit
Unit of Length
Factory Calend.
KG
M3
EUR
MIN
M
01
Save your entries.
6.2.2.3
Assignment of Warehouse Number to Supply Chain
Unit
In Customizing for Yard Logistics, choose
Settings
Assign Warehouse Numbers/Business Partners :
1. Choose Warehouse Number TRCK and press Continue.
2. For Supply Chain Unit, choose SCU_TRUCK.
3. Save your entries.
6.2.2.4
Activate Application Log
Activate the application log for Yard Logistics.
On the Fiori Launchpad, choose
ACTLOG
Settings
Activate Application Log
-> or use transaction code /SCWM/
Maintain the following entries:
Subobject
Log Active
/SAPYL/INTERFACE_EWM
4 (Additional Information)
/SAPYL/RESET_SEQ
4 (Additional Information)
/SAPYL/YARD_TU
4 (Additional Information)
/SAPYL/YC
4 (Additional Information)
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
29
Subobject
Log Active
/SAPYL/YO
4 (Additional Information)
/SAPYL/YR_REL
4 (Additional Information)
/SAPYL/YT
4 (Additional Information)
/SAPYL/YT_DLOC_DET
4 (Additional Information)
/SAPYL/YT_QDET
4 (Additional Information)
WAREHOUSE_BILLING
4 (Additional Information)
WHS_TASK
4 (Additional Information)
LOG_GENERAL
4 (Additional Information)
6.2.2.5
Define Idle Time per User
On the Fiori Launchpad, choose
Settings
Define Idle Time per User and maintain the following entries:
Yard No.
Idle (sec)
TRCK
3
6.2.3 Definition of Yard Structure
6.2.3.1
Definition of Storage Types
You must define the different storage types which are needed within your Yard.
In Customizing for Yard Logistics choose
Storage Type
Master Data
Setting up the Yard
Yard Structure
Define
and maintain the following entries, each containing the settings below.
Warehouse No.
Storage Type
Description
TRCK
YARD
Storage Type Defines a Yard
30
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Warehouse No.
Storage Type
Description
TRCK
GATE
Inbound and Outbound Gates
TRCK
PARK
Parking Lots
TRCK
DOOR
Warehouse Doors
Save your entries.
6.2.3.2
Definition of Storage Sections
The storage sections for your yard need to be defined.
In Customizing for Yard Logistics choose
Storage Section
Master Data
Setting up the Yard
Yard Structure
Define
and maintain the following entries:
Warehouse No.
Storage Type
Storage Section
Description
TRCK
GATE
INBW
Inbound West Gate
TRCK
GATE
OUTW
Outbound West Gate
TRCK
PARK
EAST
Parking East
TRCK
PARK
NRTH
Parking North
TRCK
DOOR
DOOR
Doors
6.2.3.3
Definition of Storage Bin Types
In Customizing for Yard Logistics choose
Storage Bin Types
Master Data
Setting up the Yard
Yard Structure
Define
and maintain the following entries:
Warehouse No.
Storage Bin Type
Length
Description
Max. Capacity
Positioning Type
TRCK
PRKC
50 m
Container Parking
6
Unsorted
Truck Parking Lot
4
Unsorted
Door
1
Sequenced
Lot
TRCK
PRKT
TRCK
DOOR
25 m
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
31
Warehouse No.
Storage Bin Type
TRCK
GATE
Length
Description
Max. Capacity
Positioning Type
Checkpoint Gate
1
Sequenced
Save your entries.
6.2.3.4
Definition of Storage Bins
Based on the previous Customizing, you can now define you storage bins.
On the Fiori Launchpad, choose
Master Data
Yard Layout
Create Storage Bin .
The following storage bins must be defined:
Warehouse No.
Storage Type
Storage Section
Storage Bin
Storage Bin Type
TRCK
PARK
EAST
PL-TRUCK-01
PRKT
TRCK
PARK
EAST
PL-TRUCK-02
PRKT
TRCK
PARK
EAST
PL-TRUCK-03
PRKT
TRCK
PARK
EAST
PL-TRUCK-04
PRKT
TRCK
PARK
EAST
PL-TRUCK-05
PRKT
TRCK
PARK
NRTH
PL-CONT-01
PRKC
TRCK
PARK
NRTH
PL-CONT-02
PRKC
TRCK
PARK
NRTH
PL-CONT-03
PRKC
TRCK
DOOR
DOOR
DOOR1
DOOR
TRCK
DOOR
DOOR
DOOR2
DOOR
TRCK
DOOR
DOOR
DOOR-DUMMY
DOOR
TRCK
GATE
INBW
CHECKPOINT-INBW
GATE
TRCK
GATE
OUTW
CHECKPOINT-OUTW
GATE
6.2.3.5
Activation of Yard Management for Warehouse
For the usage of Yard Logistics, the Yard Management for Warehouse needs to be activated.
32
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
In Customizing for Yard Logistics choose
Master Data
Setting up the Yard
Activate Yard Management for
Warehouse
Maintain the following settings.
Warehouse No.
Activate Yard Management
TRCK
X
6.2.3.6
Define Warehouse Process Type
In Customizing for Yard Logistics choose
following entry.
Yard Tasks
Define Warehouse Process Type and maintain the
Propose
No Auto­
Warehouse
Whse Proc.
Whse Proc.
Whse Proc.
Confirm Im­
Confir-mat-
matic Re­
No.
Type
Type Desc.
Cat.
mediately
ion
plenish-ment tion Allowed
TRCK
9999
Warehouse
Internal
X
X
X
Supervision
Warehouse
Deactiva-
X
Movement
(3)
6.2.3.7
Define Yard Checkpoints
In Customizing for Yard Logistics choose
Master Data
Setting up the yard
Define Checkpoints .
Maintain the following entries:
Warehouse No.
Checkpoint
Description
TRCK
INBW
Inbound Checkpoint West
TRCK
OUTW
Outbound Checkpoint West
6.2.3.8
Define Warehouse Doors
 Note
Yard Logistics technically needs only one EWM-Door which isn’t needed for any further usage. In the next
two steps, the linking to a Storage Bin happens which is also not relevant for the further usage.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
33
In Customizing for Yard Logistics choose
maintain the following entries.
Master Data
Setting up the yard
Define Warehouse Door
Warehouse No.
Warehouse Door
LoadingDescription
TRCK
DO01
Inbound and Outbound /SCWM/DOOR
6.2.3.9
Action Profile
and
No. Range No.
01
Assign Checkpoints to Yard Bins
On the Fiori Launchpad, choose Master Data Yard Layout Assign Checkpoint to Yard Bin and SCU
select TRCK as warehouse number for yard and confirm your selection.
and
Maintain the following entries:
Checkpoint
Storage Bin
Whse Proc. Type
INBW
CHECKPOINT-INBW
9999
OUTW
CHECKPOINT-OUTW
9999
6.2.3.10 Assign Warehouse Doors to Yard Bins
 Note
Due to a technical restriction in SAP EWM, at least one door must always be linked to a storage bin.
Therefore you must link one storage bin to a door which won’t further be used within the solution.
On the Fiori Launchpad, choose Master Data Yard Layout Assign Warehouse Door to Yard Bin and
select TRCK as warehouse number and press Continue. Maintain the following entry and save:
Whse Door
YrdWhseNo.
Yard Bin
DO01
TRCK
DOOR-DUMMY
6.2.3.11 Maintain General Settings for Shipping and
Receiving
In Customizing for Yard Logistics choose
34
Master Data
Settings for Transportation Units
General Settings
General Settings for Shipping and Receiving
and maintain the following entries for your Warehouse Number.
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Entry
Value
Different Routes
Warning
Different Departure Time
Warning
Copy Route from Door
Copy Route Def. Val. For Door and Next Departure Time to
TU
Copy Route for Outb. Del. Order to TU
Do Not Copy Route Default Value to Assigned TU
Write Unloading Begin to Inb. Del.
Do Not Write Date/Time to Inbound Delivery
Write Loading Begin to Outb. Del. Order
Do Not Write Date/Time to Outbound Delivery Order
Arrival / Departure from Chkpt
None
Post Goods Issue at Departure
X
6.2.4 Customizing for Yard Processes (Shipping & Receiving)
6.2.4.1
Define Number Range for Transportation Units
In Customizing for Yard Logistics choose
Master Data
Define Number Range Interval for Transportation Units
Settings for Transportation Units
and maintain the following settings:
No
From No.
01
0000000000000000 0000000000999999
01
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
General Settings
To Number
NR Status
Ext
0
99
INTERNAL – Authorized for SAP Customers and Partners
35
6.2.4.2
Define Number Range for Shipping & Receiving
Activities
In Customizing for Yard Logistics choose
Master Data
Define Number Ranges for S&R Activities
Settings for Transportation Units
General Settings
and maintain the following settings:
No
From No.
To Number
01
000000000000000001
000000000099999999
6.2.4.3
Define Number Range for Vehicles
In Customizing, navigate to
Cross-Process Settings
Vehicles
SCM Extended Warehouse Management
Shipping and Receiving
Number Ranges
Extended Warehouse Management
Define Number Range Interval for
and maintain the following settings:
No
From No.
To Number
01
000000000000000001
000000000099999999
6.2.4.4
Define Control Parameters for Forming Vehicles/
Transportation Units
Some Control Parameters for Transportation Units need to be maintained.
In Customizing for Yard Logistics choose Master Data -> Settings for Transportation Units -> General Settings > Define Control Parameters for Forming Vehicles/Transportation Units
Maintain the following entry and save it afterwards.
Means of Transport
Vehicle/TU
Number Range Number
PPF Action Profile
TRUCK
TU (Trans. Unit)
01
/SCWM/TU
36
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.2.4.5
Define further Number Ranges for Master Data
1. In Customizing for Yard Logistics choose Master Data Setting up the Yard Define Number Ranges ,
select Define Number Ranges for Warehouse Tasks/Warehouse Documents, choose warehouse number
TRCK and maintain following entries:
No
From No.
To Number
01
000000000000000001
000000000099999999
2. Select Define Number Range Intervals for Warehouse Order and choose warehouse number TRCK, then
maintain the following entries:
.No
From No.
To Number
01
000000000000000001
000000000099999999
3. Select Assign Number Range Intervals to Warehouse Number and maintain the following settings:
NRInt. WO (Warehouse Order Num­
Warehouse Number
No.Rng (Warehouse Task Numbers)
bers)
TRCK
01
01
6.2.4.6
Define Number Ranges for Alerts
In Customizing for Yard Logistics, choose
Alerts
General Settings
Alert Monitor
Define Number Ranges for
and maintain the following entries:
No .
From No
To Number
01
000000000000000001
99999999999999999999
6.2.4.7
Define Means of Transport
In Customizing for Yard Logistics choose
Maintain Means of Transport
Master Data
Settings for Transportation Units
General Settings
maintain the following entry:.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
37
Means of Transport
Description
Transp. Mode
Standard Code
TRUCK
Yard Truck
ROAD
31
6.2.4.8
Define Packaging Material Types
In Customizing for Yard Logistics choose
Master Data
Settings for Transportation Units
General Settings
Maintain Packaging Material Types Master Data -> Settings for Transportation Units -> General Settings ->
Maintain
Add the following entry and save it afterwards.
Pack.Mat.Type
Description
PM Category
0001
Truck
Means of Transport, Transport Element,
Transport Unit
You create the packaging material types in Customizing for Define Packaging Material Types under
Customizing Implementation Guide
38
Logistics-General
INTERNAL – Authorized for SAP Customers and Partners
Handling Unit Management
Basics .
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.2.4.9
Define Packaging Material
You can now define the different Packaging Materials; to do so go to transaction MM01 and enter the following
product to create it:
Product
PACK_TRUCK
1. Go to Global Data and choose Create.
2. Choose industry Sector: Plant engin./construction and material type: Packaging.
3. Press Select View(s) and choose Basic Data 1, Sales: General/Plant Data, “WM Packaging.
4. Enter Plant 0001, Sales Org. 0001, Distr.Channel 01.
5. Fill in a description and select as Base Unit of Measure PC.
6. Go to Additional Data, Units of Measure and maintain the following settings:
Capacity
Gross
Unit of
Unit of Vol­ Consump­
Weight
Weight
Volume
ume
tion
Length
Width
Height
Unit of Di­
mension
120
KG
240 m³
M3
3
13
2
2
M
7. Go to Sales: General/Plant Data tab and maintain the following settings:
Pack.Mat.Type
Allowed pkg Weight
Allowed pkg Volume
0001 (Truck)
6.000 kg
180 m³
8. Go to WM Packaging Data tab and maintain the following settings:
Max. Length
Max. Width
Max. Height
13,6
2,4
2,4 m
9. Save your entries.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
39
6.2.4.10 Link Packaging Material to Means of Transport
On the Fiori Launchpad, choose
(TU) and Means of Transport
Master Data
General Settings
Maintain Link between Packaging Material
and maintain the following entry:
MTr
Pack. Material
Optional
TRUCK
PACK_TRUCK
X
6.2.5 Customizing of Attachment MIME Types for Yard Tasks
Define the MIME-Types and file extension types for uploading pictures that can be used within Yard tasks.
Maintain the following In Customizing for Maintain Attachment Type Schemaunder
Components
Processes and Tools for Enterprise Applications
Environment
Dependent Object Attachment Folder :
Cross-Application
Reusable Objects and Functions for BOPF
1. Attachment Schema:
Attachment Schema
Category
Description
/SAPYL/YT
BS_ATF_DB
Yard Task: Attachments
/SAPYL/TU
BS_ATF_DB
2. Assign Attachment Types:
Attachment Type
Default File
Multiple Occurrence
ATCMT
X
X
3. Assign Schema to BO Nodes:
Business Object
Node
Allow Attachments?
Attachment Schema
/SAPYL/YARD_TASK
ROOT
X
/SAPYL/YT
/SAPYL/YARD_TU
INSP_DETAILS
X
/SAPYL/TU
4. MIME Type dep on BO & Node
40
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Business Object
Node
Seq Num
Mime Type of a Web object
/SAPYL/YARD_TASK
ROOT
1
image/png
/SAPYL/YARD_TASK
ROOT
2
image/jpeg
/SAPYL/YARD_TU
INSP_DETAILS
1
image/pbg
/SAPYL/YARD_TU
INSP_DETAILS
2
image/jpeg
/SAPYL/YARD_TU
INSP_DETAILS
3
image/jpg
6.3
Yard Logistics Customizing
6.3.1 Setting up the Yard
6.3.1.1
Define Yard Numbers
In Customizing for Yard Logistics choose
maintain the following entry:.
Master Data
Setting up the Yard
Yard No.
Yard Number Description
TRCK
Truck Yard
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Define Yard Numbers
and
INTERNAL – Authorized for SAP Customers and Partners
41
6.3.1.2
Define Order Types
In Customizing for Yard Logistics choose
the following entry:
Yard Request and Yard Order
Define Order Types
Order Type
Yard Order Type Description
TRCK
Truck Operations
6.3.1.3
and maintain
Assign Order Type and Threshold for Arrival
The Order Type needs to be assigned to the Yard.
In Customizing for Yard Logistics choose
Yard Request and Yard Order
Assign Order Type and Threshold for
and maintain the following entry:
arrival
 Note
The threshold entries are optional.
Yard Order Type
Threshold Early
Threshold Late
Yard No.
Order Type
Description
Arrival
Arrival
Time Unit
TRCK
TRCK
Truck Operations
4
4
H
6.3.1.4
Define Whether to Activate Yard Task Related to
Yard Order Automatically
To define and control the automatic activation of the first yard task related to a yard order and all subsequent
ones, or activate dynamic operations for yard order/yard task from BRF+, in Customizing for Yard Logistics
choose Yard Request and Yard Order
and maintain the following entry:
Define Whether to Activate Yard Task of Yard Order Automatically
Yard No.
Order Type
ActFirstYT
ActNextYT
TRCK
TRCK
X
X
42
INTERNAL – Authorized for SAP Customers and Partners
ACtDynOpr
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.3.1.5
Define Number Ranges for Yard Request, Yard
Order, and Yard Task
Maintaining number ranges for the different business objects used in SAP Yard Logistics for SAP S/4HANA.
In Customizing for Yard Logistics choose
Request, Yard Order, Yard Task
Master Data
Setting up the Yard
Define Number Ranges for Yard
and proceed as follows:
1. Choose Define Number Ranges for Yard Request and select TRCK as Yard Number and maintain the
following entry:
No
From No.
To Number
NR Status
01
000000000000000
000000000099999
0
001
999
Ext
2. Choose Define Number Ranges for Yard Order, select TRCK as Yard Number and maintain the following
entry:
No
From No.
To Number
NR Status
01
000000000000000
000000000099999
0
001
999
Ext
3. Choose Define Number Ranges for Yard Task, select TRCK as Yard Number and maintain the following
entry:
No
From No.
To Number
NR Status
01
000000000000000
000000000099999
0
001
999
Ext
4. Choose Assign Number Range Intervals for Yard Request and maintain the following entry:
Yard No.
Order Type
No
TRCK
TRCK
01
5. Assign Number Range Intervals to Yard Order:
Yard No.
Order Type
No
TRCK
TRCK
01
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
43
6.3.2 Settings for Transportation Units
6.3.2.1
Define Loading Scheme
A loading scheme can be defined to load a sequence of one TU on top of another TU that has this loading
scheme assigned. A maximum number of levels for definition of the loading scheme should be set in the
following Customizing.
In Customizing for Yard Logistics choose
Stacking
Define Loading Scheme
Master Data
Settings for Transportation Unit
Loading and
and proceed as follows:
 Note
This example entry creates a loading scheme for having two places at one level, while the sequence in first
place has space for 5 meters and second place has place for 4 meters.
1. Under Loading scheme, maintain following entry:
Maximum Level
Loading Scheme De­
Loading Scheme
Length
Length UoM
Number
scription
TRUCK_SCHEME
13
M
1
Truck Scheme
2. Select the entry and choose Sequence Structure, maintain following entry:
Layout
Layout Description
8_5
8m, 5m
3. Highlight the previously-made entry and choose Sequence Numbers on the left side and maintain following
entries:
44
Position
Length
Length UoM
1
8
M
2
5
M
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.3.2.2
Define Transportation Unit Types
In Customizing for Yard Logistics choose
Define Transportation Unit Types
TU Type
Grouping
TR0
Master Data
Settings for Transportation Unit
General Settings
and maintain the following entriesÖ
Loading
Layout (Level
TU Type De­
Carrying
Scheme
1)
scription
TU Type Icon
X
TRUCK_SCHE
8_5
Truck
~Icon/
ME
TR1
BoxTruck
X
CO1
Trailer
~Icon/Trailer
Container
~Icon/
Container
GR0
X
Grouping Item
~Icon/Group
Select the entry TR0 and choose Default Loading Scheme.
Level Number
Layout
Loading Alias
1
8_5
A1
2
8_5
A2
6.3.2.3
Maintain Transportation Unit Loading Hierarchy
Define the Loading Hierarchy of Transportation Units (which TU type can be represented as sub-TU to another
TU).
In Customizing for Yard Logistics choose
Stacking
Master Data
Settings for Transportation Unit
Maintain Transportation Unit Loading Hierarchy
Loading and
and maintain the following entries:
PrntTUType
ChTUType
TR0
CO1
TR1
CO1
6.3.3 Yard Request and Yard Order
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
45
6.3.3.1
Define Default Location for Yard Order/Yard
Request
On the Fiori Launchpad, choose
Yard Request
Master Data
General Settings
Define Default Location for Yard Order/
and maintain the following entries:
Arrival
Order
Departure
Outb.
ArrStor­
ArrStor­
Storage
DepStor­
DepStor­
Storage
Yard No.
Type
Inbound
Ckpt
Typ
Sec
Bin
Typ
Sec
Bin
TRCK
TRCK
INBW
OUTW
GATE
INBW
CHECK­
GATE
OUTW
CHECK­
6.3.3.2
POINT-
INBW
OUTW
Define Date and Time Record Types
In Customizing for Yard Logistics choose
Types
POINT-
Yard Request and Yard Order
Define Date and Time Record
and maintain the following entries:
Yard Order Date Time
Record Type Descrip­
Yard No.
Order Type
Type
tion
DTime Role
TRCK
TRCK
01
Arrival
Planned arrival date
and time
TRCK
TRCK
02
Departure
Planned departure
date and time
TRCK
TRCK
03
Completion
Planned Completion
date and time
TRCK
TRCK
04
Activation
Planned Activation
date and time
TRCK
TRCK
D1
Driver's Working Hours Driver's working hours
 Note
Customizing related to driver's working hours is not mandatory. Maintain and enable it only if you want to
maintain driver's working times.
46
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.3.3.3
Define Business Partner Roles
In Customizing for Yard Logistics choose
maintain the following entries:
Yard Request and Yard Order
Define Business Partner Roles
and
Business Partner Role De­
Yard No.
Order Type
BUPA Role
scription
TRCK
TRCK
0001
Ordering Party
TRCK
TRCK
0002
Bill-to Party
TRCK
TRCK
0003
Requester
TRCK
TRCK
0004
Carrier
6.3.3.4
Auto Complete/Activate Yard Order
In Customizing for Yard Logistics, choose
Order
Yard Request and Yard Order
Auto Complete/Activate Yard
and maintain the following entries:
Yard No.
Order Type
AutoCmpIYO
AutoActOYO
TRCK
TRCK
X
X
6.3.3.5
Auto-Generate Opposite Yard Order/Yard Request
In Customizing for Yard Logistics, choose
Yard Request
Yard Request and Yard Order
Auto-Generate Opposite Yard Order/
and maintain the following entries:
CreateOut
CreatInbY
CreatOutY
CheckInIY
CompInbY
ActvOutbY
Yard No.
Order Type R
CreatInbY
YR
O
O
O
O
O
TRCK
TRCK
X
X
X
6.3.3.6
X
ActDynCR
Define Reference Document Types
In Customizing for Yard Logistics choose
and maintain the following entries
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Yard Request and Yard Order
Define Reference Document Types
INTERNAL – Authorized for SAP Customers and Partners
47
Ref. Type
Yard Order Reference Type Description
INV
Invoice Number
FO
Freight Order
6.3.3.7
Define Reference Document Item Type
In Customizing for Yard Logistics choose
Types
Yard Request and Yard Order
Define Reference Document Item
and maintain the following entry:
Ref. Type
Yard Order Reference Type Description
FOI
Freight Order Item
6.3.3.8
Assign Reference Types to Order Types
Assign the header reference types to order types.
In Customizing for Yard Logistics choose
Types
Yard Request and Yard Order
Assign Reference Types to Order
and maintain the following entries:
Yard Order Reference Type
Yard No.
Order Type
Ref Type
Description
TRCK
TRCK
FO
Freight Order
TRCK
TRCK
INV
Invoice
6.3.3.9
Assign Reference Types to TU Types
Assign the item reference types to the transportation unit types.
In Customizing for Yard Logistics choose
Types
Yard Request and Yard Order
Assign Reference Types to TU
and maintain the following entry::
Yard No.
Order Type
TU Type
Ref. Type
Ref. Item Typ
TRCK
TRCK
TR0
FO
FOI
48
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.3.3.10 Define Additional References for YR/YO Overview
Add additional references to the Yard Request/Yard Order Overview POWL list.
In Customizing for Yard Logistics choose
YR/YO Overview
Yard Request and Yard Order
Define Additional References for
and maintain the following entries:
Yard No.
Ref. Type
TRCK
FO
TRCK
INV
6.3.4 Settings for Yard Tasks
6.3.4.1
Define Activity Type
Define the activity types within the Yard.
In Customizing for Yard Logistics choose
entries:
Activitiy
Yard Tasks
Define Activity Types
and maintain the following
Activity Cat­
Duration
Whse Proc.
Activity Type
Yard Number Type
egory
Planned
type
Desc.
No range no.
Cleaning Ac­
TRCK
MV01
Movement
5
9999
Moving
01
TRCK
CL01
Non-Move­
5
9999
Cleaning
01
5
9999
Loading
01
5
9999
Standard Ac­
01
tivity Type
X
ment
TRCK
LOAD
Loading/
Unloading
TRCK
STD
Non-Move­
ment
TRCK
INSP
Inspection
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
tivity
5
9999
Internal
Movement
01
INTERNAL – Authorized for SAP Customers and Partners
49
6.3.4.2
Define Default Activity Types
Define the default activity types within the Yard.
Yard Tasks
In Customizing for Yard Logistics choose
following entry:
Define Default Activity Types
and maintain the
Yard No.
Order Type
Direction
Seq. No.
Acty Type
Time Point
TRCK
TRCK
Inbound
1
STD
During Yard Re­
quest Creation
TRCK
TRCK
Outbound
1
STD
During Yard Re­
quest Creation
6.3.4.3
Define Exception Codes
Define the Exception Codes within the Yard.
In Customizing for Yard Logistics choose
entries:
Yard Tasks
Define Exception Codes and maintain the following
Yard Task Exception Code
Yard No.
Exception
Description
Alert Type
TRCK
EX01
Damage
2833
TRCK
EX02
Crash
2841
6.3.4.4
Maintain Follow-on Actions for Exception Code
Define the follow-on actions for Exception Codes within the Yard.
In Customizing for Yard Logistics choose
maintain the following entries:
Yard Tasks
Maintain Follow-on Actions for Exception Codes
Yard No.
Exception
Action
TRCK
EX01
Block Source Location
TRCK
EX02
Block TU
50
INTERNAL – Authorized for SAP Customers and Partners
and
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.3.4.5
Define Inspection Categories
Define Inspection Categories for Inspection Yard Tasks.
In Customizing for Yard Logistics, choose
following entry:
Yard Tasks
Define Inspection Categories
Inspection Category
Inspection Category Description
VIN_INSPECTION
VIN Inspection
and maintain the
Select the above entry and click Inspection Activity to maintain the following entries:
Inspection Activity
Inspection Activity Description
CHECK_TRANSMISSION
Check Transmission
WINDSHIELD
Select entry CHECK_TRANSMISSION and click Findings to.maintain the following entries:
Finding
Finding Description
AUTOMATIC
Automatic
MANUAL
Manual
Select entry MANUAL and click Details to maintain the following entries:
Details
Details Description
5_SPEED_GEARBOX
5 speed gearbox
6_SPEED_GEARBOX
6 speed gearbox
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
51
6.3.4.6
Assign Inspection Category to Activity Type
Assign Inspection Category to Activity Type for specific Yard.
In Customizing for Yard Logistics, choose
maintain the following entry:
Yard Tasks
Assign Inspection Category to Activity Type
Yard No.
Activity Type
TU type
TRCK
INSP
TR0
6.4
and
Inspection Category
Yard Logistics Master Data
6.4.1 Yard Cockpit Settings
6.4.1.1
Define Textures
Define the Visual Resource Entries within the Yard.
On the Fiori Launchpad, choose
Master Data
Yard Cockpit
Define Textures
and maintain the following:
Yard No.
Texture Name
Texture MIME Repository URL
TRCK
TRUCK_TEXTURE
Link to texture
TRCK
CONT_TEXTURE
Link to texture
52
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.4.1.2
Define Colors
Define new colors.
On the Fiori Launchpad, choose
entry:
Master Data
Yard Cockpit
Maintain Colors and maintain the following
Alpha charac­
Color
Description
Color Model
Red
Green
Blue
ter
GREY
Grey color
RGBA
200
200
200
0
6.4.1.3
Define Visual Object Type
On the Fiori Launchpad, choose
following entries:
Master Data
Yard Cockpit
Define Visual Object Type and maintain the
Visual Object
Yard Number
Type
Description
Shape
TRCK
TRUCK
Truck
Box
TRUCK_TEXTURE
TRCK
CONT
Container
Box
CONT_TEXTURE
TRCK
DOOR
Door
Rectangle
GREY
TRCK
CONT_PARK
Container Parking
Rectangle
GREY
TRCK
TRUCK_PARK
Truck Parking
Rectangle
GREY
TRCK
CHECKP
Checkpoint
Rectangle
GREY
6.4.1.4
FillColor
Texture
Assign Visual Object Type to Packaging Material
On the Fiori Launchpad, choose
Master Data
Yard Cockpit
Assign Visual Object Type to Packaging
Material and maintain the following entry:
Yard No.
Packaging Material
VisObjType
TRCK
PACK_TRUCK
TRUCK
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
53
6.4.1.5
Assign Visual Object Type to Storage Bin Type
On the Fiori Launchpad, choose
Type
Master Data
Yard Cockpit
Assign Visual Object Type to Storage Bin
and maintain the following entries:
Yard No.
Storage Bin Type
VisObjType
TRCK
PRKC
CONT_PARK
TRCK
PRKT
TRUCK_PARK
TRCK
DOOR
DOOR
TRCK
GATE
CHECKP
6.4.1.6
Define Visual Object Status Color Coding
Define in which color an object with a certain status will be displayed.
On the Fiori Launchpad, choose Master Data
and maintain the following entries:
Yard Cockpit
Define Visual Object Status Color Coding
Yard No.
VOStatus
Color
TRCK
TU is Empty
GREY
6.4.2 Handling Resources
6.4.2.1
Define Handling Resource
On the Fiori Launchpad, choose
maintain the following entry:
Master Data
Handling Resources
Define Handling Resources and
Yard No.
Handling Resource
Handling Resource Description
TRCK
HR_SHAG_TRUCK_01
Shag Truck 01
54
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.4.2.2
Assign User to Resource
Assign the system user to a resource.
On the Fiori Launchpad, choose Master Data
and maintain the following entry:
Handling Resources
Assign Handling Resource to User
Yard No.
User
Handling Resource
TRCK
your system user
HR_SHAG_TRUCK_01
6.4.2.3
SkipRes
Handle Resource Constraints
Assign Transportation Unit Types to Handling Resources
On the SAP Fiori Launchpad, choose
Master Data
Handling Resources
Handling Resource Constraints .
Yard No.
Handling Resource
TU Type
TRCK
HR_SHAG_TRUCK_01
CN0
6.4.3 Queue Management
6.4.3.1
Define Queue
Create Queues.
On the Fiori Launchpad, choose
following entry:
Master Data
Queue Management
Define Queues
and maintain the
Yard No.
Queue
Yard Task Queue Description
TRCK
Q001
Queue 001
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
55
6.4.3.2
Maintain Queue Determination
Maintain the queue determination based on the Customizing.
On the Fiori Launchpad, choose
maintain the following entry:
Master Data
Queue Management
Yard No.
Acty Type
TRCK
MV01
Q001
TRCK
STD
Q001
6.4.3.3
Source Storage Type
Maintain Queue Determination
Dest. Storage Type
and
Queue
Assign Resource to Queue
On the Fiori Launchpad, choose
Master Data
Handling Resources
Assign Handling Resources to
and maintain the following entry:
Queue
Yard No.
Handling Resource
Queue
Sec.No.
TRCK
HR_SHAG_TRUCK_01
Q001
1
6.5
Additional Customizing (optional)
6.5.1 Stacking of Containers
6.5.1.1
Define Stacking Storage Bin types
 Note
This Customizing needs to be applied to define the maximum level of stacking on one storage bin type.
56
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
In Customizing for Yard Logistics, choose
Stacking Storage Bin Types
Master Data
Setting Up the Yard
Yard Structure
and maintain the following:
Yard No.
Storage Bin Type
MaxStckLvl
TRCK
PARK
4
6.5.1.2
Define
Define Stacking Relations
 Note
This Customizing needs to be applied to define which (container) TU type A can be stacked onto which
(container) TU type B.
In Customizing for Yard Logistics, choose
Stacking
Define Stacking Relations
Master Data
Settings for Transportation Units
and enter the following:
TUTypeBelow
TUTypeOntop
CO1
CO1
6.5.1.3
Loading and
Adjust Transportation Unit Type Customizing
The Container TU Type CO1 needs to be made stackable.
In Customizing for Yard Logistics choose
Define Transportation Unit Types
Master Data
Settings for Transportation Units
General Settings
and maintain the following:
TU Type
Stackable
CO1
X
6.5.2 Seal Numbers
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
57
6.5.2.1
Define Number of Seals
The required number of seals per TU Type needs to be defined.
In Customizing for Yard Logistics choose
Define Number of Seals
Master Data
Settings for Transportation Units
and maintain the following entry:
Yard No.
TU Type
NumOfSeals
TRCK
CO1
1
6.5.2.2
Seal Numbers
Adjust Activity Type Customizing
The activity type relevant for seals needs to be adjusted.
In Customizing for Yard Logistics, choose
Define Number of Seals
Master Data
Settings for Transportation Units
Seal Numbers
and maintain the following entry:
Acty Type
SealReq
STD
X
6.5.3 Measurements
6.5.3.1
Define Measurement types
Define the required measurement types.
In Customizing for Yard Logistics, choose
Define Measurement Types
Master Data
Settings for Transportation Units
Measurements
and maintain the following entries:
Yard No.
Rec. Type
TU Record Type Description
TRCK
FUEL
Fuel level
TRCK
TEMPER
Temperature
58
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.5.3.2
Determine Measurement Types
You can predetermine a measurement type based on activity type and TU type being used after a yard task
containing these entries. The entry is already created – the person executing a yard task only needs to enter
the value.
In Customizing for Yard Logistics, choose
Determine Measurement Types
Master Data
Settings for Transportation Units
Measurements
and maintain the following:
Yard No.
Acty Type
Rec. Type
TU Type
TRCK
STD
FUEL
TR0
6.5.4 Define Collada Models
On the Fiori Launchpad, choose
following entry:
Master Data
Yard Cockpit
Define Collada Model
and maintain the
Yard No.
Collada Model
Collada Model MIME Repository URL
TRCK
TRUCK
Link to collada object
6.5.5 Define Classes and Methods for Checking TU Number
This Customizing needs to be applied to check the validations for container and rails car numbers.
In Customizing for Yard Logistics, choose
Unit Validation
General
Master Data
Settings for Transportation Units
Define Classes and Methods for Checking TU Number
Transportation
and maintain the following:
Yard No.
TU Type
Class/Interface
TRCK
CO1
/SAPYL/CL_EXT_NO_CHECK_CNT
TRCK
<Railcar TU type>
/SAPYL/CL_EXT_NO_CHECK_RC
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
59
6.5.6 Number Validations for Containers
In Customizing for Yard Logistics, choose
Unit Validation
Container
Master Data
Settings for Transportation Units
Define Container Number Owner Codes
Transportation
and maintain the following:
Owner Code
Equip.Cat.
Description
XXX
U
<Your Owner Code description>
6.5.7 Number Validations for Railcars
Validation logic Railcar ID (sample UIC wagon numbers with national block Germany): The complete wagon
number comprises 12 digits. The individual digits have the following meaning:
Digits 1-2: Type of vehicle and indication of the interoperability capacity (on multiple units, type)
Digits 3-4: Country Code (Owner before 2006)
Digits 5-8: Vehicle type information
Digits 9-11: Individual running number (serial number)
Digit 12: Self-check digit
6.5.7.1
Define Types of Railway Vehicles (Digit 1 and 2)
In Customizing for Yard Logistics, choose
Unit Validation
Rail
Master Data
Define Types of Railway Vehicles
Settings for Transportation Units
and maintain the following:
Code vehicle
Type of Railway Vehicle
91
Electric locomotive
60
INTERNAL – Authorized for SAP Customers and Partners
Transportation
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.5.7.2
Define Country Code for Railcars (digit 3 and 4)
In Customizing for Yard Logistics, choose
Unit Validation
Rail
Master Data
Settings for Transportation Units
Define Country Code for Railcars
and maintain the following:
CounNumC
Countries
Name
ISO code3
80
DE
Germany
DEU
6.5.7.3
Define Class Number for Railway Vehicles (digits 5
– 8)
In Customizing for Yard Logistics, choose
Unit Validation
Transportation
Rail
Master Data
Settings for Transportation Units
Define Class Number for Railway Vehicles
Transportation
and maintain the following:
UIC Class
Code Vech
UIC Class Number description
8194
97
Class E 94
6.5.8 Classification
6.5.8.1
Define Characteristics
Here you can define the characteristics that can be used.
On the Fiori Launchpad, go to
Master Data
Classification
Characteristics
and enter the following:
1. In the Characteristic input field, enter the name of your characteristic, for example, COLOR and create it.
2. On the Basic Data tab, maintain the following information:
Description
Status
Data Type
Number of Chars
Color
1 – Released
CHAR
1
3. On the Values tab, make the entries BLACK, BLUE, and RED.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
61
6.5.8.2
Define Classes
Here you define the classes that can be used.
On the Fiori Launchpad, go to
confirm:
Master Data
Classification
Class

Classes
and populate the following fields and
Class Type
Example

CO1_CLASS
Example
CTU
On the Basic Data tab, maintain the following information:
Description
Status
Classification for CO1
1 – Released
:
:
On the Char tab, make the following entry:
Char.
Description
Data Type
Number of Chars
COLOR
Classification for CO1
CHAR
10
6.5.8.3
Maintain Classes for TU Types
On the Fiori Launchpad, go to
following:
Master Data
Classification
Assign Classes to TU Types
TU Type
Class
CO1
CO1_CLASS
and maintain the
6.5.9 Customizing for Dangerous Goods/EH&S-Integration
62
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.5.9.1
Adjustments of Customizing for Yard Number
Definition
In Customizing for Yard Logistics, choose
enhance the following entry:
Master Data
Setting up the Yard
Define Yard Numbers
and
Yard No.
Dang. Goods
Dan. Goods Check
DG Data Source
TRCK
Yes or No
No Check or
Separation Key
Check (
External system, EH&S
(
●
Yes. This option
●
switches on the follow­
ing checks
○
Validation for exis­
tence of EHS mas­
ter data for the
combination of
product and regula­
tion
○
Call of BAsI for DG
checks during
check-in/check-out
and setting the YO
blocking status in
case DG checks
have failed.
●
No. The products be­
longing to this yard
number is not equipped
to handle dangerous
○
No Check: No
Checks
●
, or Manually
Maintained (
●
DG Master Data is
Separation Key
stored in YO BO and
Check, see Define Sep­
fields are disabled for in­
aration Keys for Danger­
ous Goods [page 64],
Assign Separation Keys
put in YO Content tab
●
SEHS/DGD03, /SEHS/
[page 64], Define Sep­
HMD) and fields are dis­
aration Check Rules for
abled for input in YO
Dangerous Goods [page
Implementation Class to
EH&S: DG Master Data
is stored in DG Master(/
to Product Master Data
64], Assign Check Rule
External System:
Content tab.
●
Manually
Check Rule ID [page
Maintained: DG Mas­
65]
ter Data is stored in YO
BO and fields are ena­

Note
bled for input in YO Con­
tent tab.
)
)
goods.
●
)
Dangerous Goods Checks:
No checks.
Separation Key Check – this is described under Define Separation Key Checks [HYPERLINK REMOVED]
The following customizing (chapters 6.8.2 [HYPERLINK REMOVED], 6.8.3 [HYPERLINK REMOVED], 6.8.4
[HYPERLINK REMOVED] and 6.8.5 [HYPERLINK REMOVED]) is only needed, if Adjustments of Customizing
“Define Yard Numbers” [HYPERLINK REMOVED] has been set to “Dangerous Goods Checks = Separation Key
Check”.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
63
6.5.9.1.1
Define Separation Keys for Dangerous Goods
If two transportation units (TUs) of a yard request or a yard order carry dangerous goods, the corresponding
items may have to be kept separated from each other with respect to dangerous goods Customizing.
To maintain separation keys, in Customizing for Yard Logistics, choose
Goods
Master Data
Settings for Dangerous
Define Separation Keys for Dangerous Goods .
Separ. Key
DG Separation Key Description
AV_SEPK_1
Gases Separation Key
AV_SEPK_2
Organic Peroxides
AV_SEPK_3
Inflammability-inducing (oxidizing) substances
6.5.9.1.2
Assign Separation Keys to Product Master Data
To assign the separation keys defined in Customizing, to the respective products, on the Fiori Launchpad, go to
Master Data Dangerous Goods
following values:
Assign Separation Keys to Product Master Data
Product
DG Regulation
Separ. Key
First product
Respective DG regulation
AV_SEPK_1
Second product
Respective DG regulation
AV_SEPK_2
Third product
Respective DG regulation
AV_SEPK_3
6.5.9.1.3
and maintain the
Define Separation Check Rules for Dangerous
Goods
Here, you assign the two separation keys and define whether the products associated with the combination of
the two separation keys should be allowed together or not. You can also assign check rule to the combination of
the two separation keys if you are not sure whether they should be allowed or denied together. In this case, you
assign a check rule ID to the two separation keys. This check rule ID can determine, based on your own rules,
whether the products associated with the two separation keys should be allowed or denied together.
64
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
In Customizing for Yard Logistics, choose
Dangerous Goods
Master Data
Settings for Transportation Units
Define Separation Check Rules for Dangerous Goods and maintain the following:
Separ. Key
Separ. Key
Check-Rule
ChRuleID
AV_SEPK_1
AV_SEPK_2
Deny
01
AV_SEPK_1
AV_SEPK_2
Deny
AV_SEPK_2
AV_SEPK_3
Deny
6.5.9.1.4
Settings for
Assign Check Rule Implementation Class to
Check Rule ID
As follows, 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.
In Customizing for Yard Logistics, choose
Dangerous Goods
Master Data
Settings for Transportation Units
Assign Check Rule Implementation Class to Check Rule ID
Settings for
and maintain the following:
ChRuleID
DG Check Rule Implementation Class
01
/SAPYL/CL_TEST
6.5.10 Define settings for Location Determination
6.5.10.1 Changes to “Define Activity Types”
In Customizing for Yard Logistics, choose Master Data Yard Tasks
the following entry so that the destination bin determination is set.
Define Activity Types and enhance
Yard No.
Acty Type
DB Determ.
TRCK
STD
X
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
65
6.5.10.2 Determine Compatibility of TU Type and Storage Bin
Type
In Customizing for Yard Logistics, choose
Yard Tasks
Location Determination
Maintain Compatibility of
TU Type and Storage Bin Type .
By default, all TUs are allowed to be positioned on each storage bin type. In case one entry is maintained there,
only the specified TU type is allowed to be positioned on the defined storage bin type.
Other TU types not maintained here are not allowed on the maintained storage bin type.
Yard No.
Storage Bin Type
TU Type
TRCK
PARK
TR0
6.5.10.3 Define Storage Type Search Sequence for Putaway
A storage type search sequence is an object that summarizes one or multiple storage types. During
determination of a destination bin in the yard task creation the storage type search sequence will be used to
determine potential destination storage types.
In Customizing for Yard Logistics, choose
Search Sequence for Putaway
Yard Tasks
Location Determination
Define Storage Type
and maintain the following:.
Warehouse Number
Storage Type Search Sequence
Description
TRCK
PARK
Parking Storage Types
6.5.10.4 Assign Storage Types and Storage Sections to
Storage Type Search Sequence
You assign one or more storage types and storage sections to a storage type search sequence. These storage
types and storage sections are then used for bin determination. The storage types and sections are checked
according their sequence for potential destination bins. If no destination bin is found for a storage type the next
one in the sequence will be checked.
66
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
In Customizing for Yard Logistics, choose
Yard Tasks
Storage Sections to Storage Type Search Sequence
Srch Seq.
Seq. No.
TRCK
PARK
1
Assign Storage Types and
and maintain the following:
Warehouse Num­
ber
Location Determination
Storage Type
PARK
Storage Section
Description
EAST
Determine Parking
Place
6.5.10.5 Maintain Storage Type Search Sequence for Activity
Type and TU type
Define the relevant storage type search sequence for a specific movement and TU type. This allows the control
of destination bin determination based on different movements and based on the TU type. Also, HazRat1 and
HazRat2 information could possibly be taken into account.
In Customizing for Yard Logistics, choose
Yard Tasks
Search Sequence per Activity Type and TU type
Location Determination
Maintain Storage Type
and maintain the following:
Storage Type
Yard No.
Acty Type
TU Type
TRCK
MV01
TR0
HazRat1
HazRat2
Search Seq.
PARK
6.5.10.6 Assign Permitted Hazard Rating 1 for Each Storage
Type and Storage Section
To assign the permitted hazard rating1 for each storage type and storage section in Customizing for Yard
Logistics, choose
Type
Yard Tasks
Location Determination
Assign Permitted Hazard Rating 1 for Each Storage
and maintain the following:
Yard No.
Storage Type
Storage Section
HazRat1
TRCK
PARK
EAST
WGK 3
The check against allowed hazard rating1 runs during yard task creation.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
67
6.5.10.7 Assign Permitted Hazard Rating 2 for Each Storage
Type and Storage Section
To assign the permitted hazard rating2 for each storage type and storage section in Customizing for Yard
Logistics, choose
Yard Tasks
Type and Storage Section
Location Determination
Assign Permitted Hazard Rating 2 for Each Storage
and maintain the following:
Yard No.
Stor. Bin Type
Storage Section
HazRat2
TRCK
PARK
EAST
A II
The check against allowed hazard rating2 runs during yard task creation.
6.5.11 Quantity Checks during Location Determination
6.5.11.1 Maintain Maximum Stacking Levels for Hazardous
Ratings
To maintain settings for the maximum levels of stacking, hazard rating1 and hazard rating2.in Customizing for
Yard Logistics, go to
Yard Tasks
Location Determination
Quantity Checks
Maintain Maximum Stacking
Levels for Hazardous Ratings
Storage Sec­
Yard No.
Storage Type
tion
TU Type
HazRat1
HazRat2
MaxStckLvl
TRCK
PARK
EAST
CO1
WKG 3
A II
2
These settings are used to check for container storage if the maximum stacking height is respected per storage
type, storage section, and hazard rating.
6.5.11.2 Assign Storage Hazard Type for Storage Classes to
Yard
To assign the storage hazard types to the yard in Customizing for Yard Logistics, go to
Determination
68
Quantity Checks
Yard Tasks
Location
Assign Storage Hazard Type for Storage Classes to Yard
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Yard No.
SHT
TRCK
SCL
These Customizing values are used to determine the storage hazard types per yard number.
6.5.11.3 Define Storage Class Group for Storage Classes
To define groups of storage classes per yard number in Customizing for Yard Logistics, go to
Location Determination
Quantity Checks
Define Storage Class Groups
Yard Tasks
and maintain the following values:
Yard No.
StClassGrp
HazRat2
TRCK
1001
1
6.5.11.4 Maintain Maximum Quantity for Storage Type
To define the maximum quantity, weight, and volume within storage type and storage section per storage class
group, on the Fiori Launchpad, choose
Master Data
Dangerous Goods
Maintain Maximum Quantity for
Storage Type
These settings are used during location determination of the yard task to check that quantity, weight, and
volume of determined destination storage bin is not exceeded.
Storage­
Storage
StClassGr Max.
Yard No.
Type
Section
oup
Quantity
Unit
Max.
Weight
Unit
Max. Vol­
ume
Unit
TRCK
PARK
EAST
1001
1000
PC
1000
KG
1000
M3
6.5.12 Automatic Task Assignments in Mobile Application
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
69
6.5.12.1 Define Offset Time for the Planned Start Time for
Yard Tasks
To define the offset time for the planned start time per yard number and activity type in a yard, in Customizing
for Yard Logistics, go to
the Planned Start Time
Yard Tasks
Automatic Task Assignments in Mobile Application
Define Offset for
and maintain the following settings:
Yard No.
Activity Type
Offset Time
UoM
TRCK
MV01
1
MIN
These settings are used for the report to increase priority in yard tasks.
6.5.12.2 Define Coordinate Types and Calculation Methods
To define the coordinate types and calculation methods per yard number and queue, in Customizing for Yard
Logistics, go to
Yard Tasks
and calculation methods
Automatic Task Assignments in Mobile Application
Define type of coordinates
and maintain the following settings:
Yard No.
Activity Type
Coordinates
Calculation Method
TRCK
Q001
Visual Object Coordinates
Pythagoras Euclidean
Distance
These settings used in the mobile application to find the closest yard task in the queue awating procesing.
6.5.13 Alerts Customizing
6.5.13.1 Maintain Exceeding Dates
To define time-based alerts that can be watched via the alert monitor, in Customizing for Yard Logistics, go to
Yard Tasks
Maintain Exceeding Dates
and maintain the following values:
Yard No.
BO Cat.
Alert Type
Alert Class
Threshold
Time UoM
TRCK
Yard Order
2813
/SAPYL/
2
h
CL_ALERT_2813
For further information and additional alert types used in the solution, see Alert Monitoring [page 165].
70
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.5.14 External Driver Communication
6.5.14.1 Maintain Text Symbols for Driver Communication
On the Fiori Launchpad, go to
Communication
Settings
Driver Communication
Maintain Text Symbols for Driver
and enter the following:
Text Name
BO Name
Node Name
Field name
BINDEST
/SAPYL/YARD_TASK
ROOT
STOR_BINDST
6.5.14.2 Define Texts for Driver Communication
On the Fiori Launchpad, go to Settings Driver Communication
and enter the following values and choose Create.
Define Texts for Driver Communication
Text Name
Text ID
Language
/SAPYL/NEXT_LOC
ST (Standard Text)
EN
On the following screen, type in the text according to your requirements, for example, Please drive to
your destination &BINDEST&.
The text symbol &BINDEST& is the value that has been defined in the Customizing for Maintain Text Symbol for
BO Name.
6.5.14.3 Assign Text Messages to Activity Type
On the Fiori Launchpad, go to Settings
and enter the following values:
Driver Communication
Assign Text Messages to Activity Type
Yard No.
Acty Type
Text Name
TRCK
MV01
/SAPYL/NEXT_LOC
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
71
6.5.15 Printing
6.5.15.1 Condition Maintenance for Yard Request Printing
1. On the Fiori Launchpad, go to Settings Printing Maintain Conditions for Yard Request Printing
maintain the following entries and choose Execute .:
Application
MaintenanceGrp
Maintenance context
PYL
PYL_YR
GCM
and
2. Choose Yard Number and click Create with Reference.
3. On the following screen, choose TRCK as Yard Number. Within the table, the printing action can be defined
in the Action Definition column.
The action definitions that are delivered are:
● /SAPYL/YR_PRINT_DOCUMENT (for YR)
● /SAPYL/YR_PRINT_DOCUMENT_MAN (for YR)
It is differentiated between automatic and manual action definitions.
6.5.15.2 Condition Maintenance for Yard Order Printing
1. On the Fiori Launchpad, go to Settings Printing
maintain the following entries and choose Execute:
Maintain conditions for Yard Order Printing
Application
MaintenanceGrp
Maintenance context
PYL
PYL_YO
GCM
and
2. Choose Yard Number and click Create with Reference.
3. On the following screen, choose TRCK as Yard Number. Within the table, the printing action can be defined
in the Action Definition column.
The action definitions that are delivered are:
● /SAPYL/YO_PRINT_DOCUMENT (for YO)
● /SAPYL/YO_PRINT_DOCUMENT_MAN (for YO)
It is differentiated between automatic and manual action definitions.
72
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.5.15.3 Condition Maintenance for Yard Task Printing
1. On the Fiori Launchpad, go to Settings Printing
maintain the following entries and choose Execute:
Maintain conditions for Yard Task Printing
Application
MaintenanceGrp
Maintenance context
PYL
PYL_YT
GCM
and
2. Choose Yard Number and click Create with Reference.
3. On the following screen, choose TRCK as Yard Number. Within the table, the printing action can be defined
in the Action Definition column.
The action definitions that are delivered are:
● /SAPYL/YT_PRINT_DOCUMENT (for YT)
● /SAPYL/YT_PRINT_DOCUMENT_MAN (for YT)
It is differentiated between automatic and manual action definitions.
6.5.15.4 Define Spool Settings for Printing
On the Fiori Launchpad, go to
following values:
Settings
Printing
Define Spool Settings for Printing
and maintain the
Yard No.
Spool Data
Output Device
New Req.
Copies
TRCK
01
Your printer
X
1
6.5.16 Self-Check-In
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
73
6.5.16.1 User Assignment to Checkpoint
Enable a user to display the self-check-in application screen at the yard checkpoint.
On the Fiori Launchpad, go to Settings Self-Check-In User Assignment to Checkpoint and maintain the
following entries to assign the a system user to yard and checkpoint:
Self Check-In Dummy User
Yard No.
Checkpoint
system user
TRCK
INBW
6.5.16.2 Define Icon IDs and Assign Country, Language, MIME
URL for Country Flags
In Customizing for Yard Logistics, go to
Yard Request and Yard Order
Self-Check-In
Define Icon IDs and
and define the displayed flags per yard and the
Assign Country, Language, MIME URL for Country Flags
referred country, language and MIME URL.
Texture MIME Reposi­
Yard No.
Icon ID
Country
Language
tory URL
TRCK
ENG
GB
EN
Link to texture
TRCK
GER
DE
DE
Link to texture
6.5.16.3 Assign Icon ID to Checkpoint
In Customizing for Yard Logistics, choose
Checkpoint
Yard Request and Yard Order
Self-Check-In
and assign which flags per checkpoint should be displayed in which order.
Yard No.
Checkpoint
Seq. No.
Icon ID
TRCK
INBW
1
ENG
TRCK
INBW
2
GER
74
Assign Icon ID to
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.5.16.4 Define Document Type for Self-Check-In
In Customizing for Yard Logistics, choose
Yard Request and Yard Order
Self-Check-In
Define Document
Type for Self-Check-In and define which reference types should be checked while determining the YO number
based on the driver’s entry within the application.
Button Text for Docu­
Yard No.
Checkpoint
Ref. Type
Seq. No.
ment Identification
TRCK
INBW
INV
1
Invoice Number
TRCK
INBW
FO
2
Freight Order
6.5.16.5 Assign Label and Identification for Self Check-in
Item Details
In Customizing for Yard Logistics, choose
Identification for Self Check-In Item Details
Check-In UI and the Means of Transport.
Yard Request and Yard Order
Self-Check-In
Assign Label and
and maintain the mapping between the texts displayed on the Self
Label Item Details – Self
Identification Item Details –
Yard No.
MTr
Check-In
Self Check-In
TRCK
TRUCK
Truck
License Plate
6.5.16.6 Maintain Default Pager Service
Maintain the following values in Customizing for Default Pager Service for Self Check-in app under
Customizing Implementation Guide
Yard Logistics
Yard Request and Yard Order
Yard No.
Pager Service
TRCK
<Pgsr>
SAP
Self Check-In .
6.5.17 Questionnaire Definition
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
75
6.5.17.1 Define Check Group
In Customizing for Yard Logistics, choose General Settings Questionnaire Define Check Group
maintain the following entries to define a group that will later collect a set of questions.
Check Grp
Check Group Description
Check_Grp
Your Check Group
and
6.5.17.2 Condition Technique
In Customizing for Yard Logistics, choose General Settings Condition Technique
settings for bundle condition tables and types for condition maintenance.
and maintain your
6.5.17.3 Define Questions
You can define the questions using transaction code SO10 in the same way as described in for Define Texts for
Driver Communication [page 71].
6.5.17.4 Assign Checks to Check Groups for Yard Orders
To assign the check ID to a check group and define the expected behavior, on the Fiori Launchpad, go to
Settings
values:
Questionnaire
Assign Checks to Check Group for Yard Orders
and maintain the following
Yard No.
Check Grp
Seq.
Text Name
AllowedRes
Follow-on
TRCK
Check_Grp
1
Your Text 1
Yes
No Action
TRCK
Check_Grp
2
Your Text 2
Yes
Deny Action
6.5.17.5 Assign Checks to Check Groups for Yard Tasks
To assign the check ID to a check group and define the expected behavior, on the Fiori Launchpad, go to
Settings
76
Questionnaire
Assign Checks to Check Group for Yard Tasks
INTERNAL – Authorized for SAP Customers and Partners
and maintain the following values:
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Yard No.
Check Grp
Seq.
AllowedRes
Follow-on
TRCK
Check_Grp
1
Yes
No Action
TRCK
Check_Grp
2
Yes
Deny Action
6.5.17.6 Condition Maintenance for Yard Order
1. On the Fiori Launchpad, go to
create the following entries:
Settings
Questionnaire
Maintain Conditions for Questionnaire
Application
MaintenanceGrp
Maintenance context
QYL
QYL_YO
GCM
-and
2. Choose Yard number and click Create with Reference
.
3. On the following screen, choose TRCK as yard number and enter the determination of the Check Group.
6.5.17.7 Condition Maintenance for Yard Task
1. On the Fiori Launchpad, go to
create the following entries:
Settings
Questionnaire
Maintain Conditions for Questionnaire
Application
MaintenanceGrp
Maintenance context
QYL
QYL_YT
GCM
-and
2. Choose Yard Number and click Create with Reference
.
3. On the following screen, choose TRCK as yard number and enter the determination of the check group, for
example with the activity type.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
77
6.6
Settings for Blocking and Deleting Personal Data
6.6.1 Preparation
1. Start transaction SFW5:
2. Activate the business function ILM-Based Deletion of Business Partner Data (BUPA_ILM_BF).
3. Activate the business function Information Lifecycle Management (ILM).
6.6.2 Settings for ILM Objects
1. In Customizing for SAP NetWeaver, go to
Management
Retention Management
Application Server
Basis Services
Information Lifecycle
Make Settings for ILM Objects
2. Select object category SAP Business Suite (OT_FOR_BS) and double-click on ILM Objects and confirm that
the following ILM Objects are present: ,
○ SAPYL_YO
○ SAPYL_YT
○ SAPYL_YTU
6.6.3 Customer-specific Settings
In Customizing for SAP NetWeaver, go to
Management
Retention Management
Application Server
Basis Services
Make Customer-specific Settings
Information Lifecycle
and proceed as follows:
1. In the dialog box that opens, enter OT_FOR_BS as object category RTP and choose Continue.
2. In the dialog structure on the left-hand-side, double-click on Object Group and enter the following:
Obj.Grp
Description
YO_OBJ_1
YO Object Group
3. Choose Rule Group and enter:
78
Rule Group
Description
Object Group
YOG
Yard Orders
YO_OBJ_1
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
4. Choose Fields and enter:
Result Field Name
Field Value
RET_PERIOD_MAX
1
RET_PERIOD_MIN
1
RET_PER_UNIT
DAY
5. Choose ILM Objects: Customer-specific Settings and enter:
ILM Objects Use
UseRuleGrp
CA_BUPA
X
SAPYL_YO
X
SAPYL_YTU
X
Obj.Grp
YO_OBJ_1
6.6.4 Define Audit Areas for ILM Objects
1. Run transaction ILMARA, select an entry as shown in the following table one after another and click on
Continue.
Audit Area
Description
Policy category
Description
BUPA_DP
BUPA_DP
RST
Residence Rule
BUPA_DP
BUPA_DP
RTP
Retention Rule
2. On the Assignment of Objects to Audit Area screen, choose Edit and activate the following entries for each
audit area:
Object assignment – Ob­
ject Assigned to Audit
Object Category
ILM Object
Description
Area’
SAP Business Suite
CA_BUPA
Archiving Business Partner
X
SAP Business Suite
SAPYL_YO
SAPYL_YO
X
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
79
6.6.5 Customizing Settings for Blocking and Deleting
Business Partner Master Data
1. In Customizing for , go to
Data Protection
Blocking and Unblocking of Data
Application Function Modules Registered for EoP Checks
Business Partner
and check the following entry:
Application Name
Item
Function Module
SAPYL
0
/SAPYL/BUPA_EOP_CHECK
2. In Customizing for Cross-Application Components, go to
Data Business Partner
the following entries:
Define
Data Protection
Blocking and Unblocking of
Assign Application Rule Variants and Rule Groups for EoP Check
and maintain
Application Name
Application Rule
Rule Group
Application Description
SAPYL
YO01
YOG
Yard Orders
6.6.6 Define Retention Policies for ILM Objects
To define Retention Policies for ILM Objects, run transaction IRMPOL and execute the following steps:.
1. Enter the following values on the initial screen and choose New:
Policy Category:
Object Category
Audit Area
ILM Object
Residence Rules
SAP Business Suite
BUPA_DP
CA_BUPA
2. Enter Policy Name: BO_POL1.
3. Select all Field Names in ‘Available Condition Field’, choose Add Item and save.
4. Choose Edit Rules and maintain the following entry for rules for policy BO_POL1:
Application
Aplication Rule
Name
Var
BUP
Residence Time
Partn.Cat.
Residence Period Unit
Time Ref.
1
1
Start of retention
Day
Period
5. Choose Change Status, select following values and click New:
80
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Policy Category
Object Category
Audit Area
ILM Object
Residence Rules
SAP Business Suite
BUPA_DP
SAPYL_YO
6. Press New then enter policy name: YOP1.
7. Select all field names in field Available Condition, choose Add item and save.
8. Choose Edit Rules and maintain the following entry for rules for policy YOP1:
Yard Docu­
Yard Order
Yard Number
ment Categ.
Status
TRCK
YO
05
Residence Pe­
Residence
To
riod
Time Unit
Time Ref.
06
1
Day
Last Changed
on
9. Choose Change Status, select the following values and click New:
Policy Category
Object Category
Audit Area
ILM Object
Retention Rules
SAP Business Suite
BUPA_DP
CA_BUPA
10. Choose New and enter policy name: BO_POL2.
11. Select all field names in Available Condition field, choose Add Item and save.
12. Choose Edit Rules and maintain the following entry for rules for policy BO_POL2:
Application
Aplication
Name
Rule Var
SAPYL
YO01
Partn. Cat.
Min. Reten­
Max. Reten­
Retention
tion Time
tion Time
Time Unit
Time Ref.
Rule Group
1
1
Day
Start of Re­
YOG
tention Pe­
riod
13. Choose Change Status, select following values and click New:
Policy Category
Object Category
Audit Area
ILM Object
Retention Rules
SAP Business Suite
BUPA_DP
SAPYL_YO
14. Press New then enter policy name: YOP2.
15. Select all field names in field Available Condition, choose Add item and save.
16. Choose Edit Rules and maintain the following entry for rules for policy YOP2:
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
81
Yard Docu­
Yard Num­
ment
Yard Order
ber
Categ.
Status
TRCK
YO
05
Min. Re­
Max. Re­
tention
tention
Retention
To
Time
Time
Time Unit
Time Ref.
Rule Group
06
1
1
Day
Last
YOG
Changed
On
6.6.7 Business Partner Role and Category for Driver
In Customizing for Cross-Application Components go to
Business Partner Roles
Settings
Define BP Roles
SAP Business Partner
Business Partner
Basic
and maintain the following entries:
BP Role Categories:
Possible BP Catego­
BP Role Cat.
Title
Description
Diff.Type
ries
ZYLDRV
Yard Log. Driver
Driver entering the
0
Person
Yard
BP Roles:
Std Assignment BP
BP Role
Title
Description
BP Role Cat
Role -> BP Role Cat.
ZYLDRV
Yard Log. Driver
Driver entering the
ZYLDRV
X
Yard.
In Customizing for Yard Logistics, go to
Yard Request and Yard Order
Default Business Partner Role for
and maintain the following entries:
Driver
BP Role
Role Cat.
ZYLDRV
ZYLDRV
In Customizing for Yard Logistics, go to
Master Data
Setting up the Yard
Define Number Ranges for Yard
Request, Yard Order, Yard Task. , select Define Number Ranges for Driver Business Partner in the Select Activity
dialog box and maintain the following intervals:
No
From No.
To Number
01
000000001
999999999
82
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.7
Integration with Internet of Things
6.7.1 General Preparation
Depending on the Internet of Things Services environment to be connected, there are different sets of
configurations available within SAP Yard Logistics to integrate to the Internet of Things Tenant specifically to
the technical needs within that environment.
Refer Internet of Things for Yard Logistics for SAP S/4HANA [page 141] for information about Internet of
Things.
6.7.2 Integration to SAP IoT Services
In case of integration scenario based on SAP IoT geofencing capabilities, refer SAP Note 3095553
information about integrating SAP Yard Logistics for SAP S/HANA with SAP IoT.
6.7.2.1
for more
Prepare Yard Logistics Backend
As prerequisite for SAP IoT Services integration, an OAuth based authentication to the IoT tenant must be
established. A valid configuration of an OAuth 2.0 profile via transaction OA2C_CONFIG – OAuth 2.0 Client
Configuration is required for establishing this authentication, which is the secure store for the specific IoT
services tenant client ID and secret, as well as definition of the actual authentication endpoint.
 Note
For more details about getting this information for the actual IoT services tenant, see documentation for
service Key operations on SAP Help Portal.
The full certificate stack for accessing the BTP Cockpit subaccount and IoT services tenant must be uploaded
via transaction STRUST – Trust Manager with reference to SSL client HANA as technical prerequisite for any IoT
API calls from Yard Logistics backend system.
A proper Cloud Connector setup within the Yard Logistics backend system must be established to allow a
Cloud to On-Premise connection. The Geofencing OData Service is defined under service path /sap/opu/
odata/sapyl/btp_geofence_action_ret_srv/ in the service definition of the Yard Logistics backend
system (transaction SICF), therefore this path (or from upper path part onwards) need to be defined as
accessible from the Cloud side within the Cloud Connector.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
83
Related Information
6.7.2.2
Prepare BTP Subaccount and IoT Services Tenant
As prerequisite for Geofencing IoT scenario, geofence action events must be triggered on the IoT side, which
are transferred in a static format to the Yard Logistics backend system according to the OData Service provided
for receiving these geofence events. The action definition must be done manually within the IoT Services
tenant as it depends on the technical destination setup from the BTP subaccount to the geofencing OData
service of the Yard Logistics backend system.
At first, the destination configuration to the geofencing OData service of the Yard Logistics backend system
must be created as connection type HTTP and proxy type OnPremise, which requires a proper Cloud Connector
setup within the Yard Logistics backend system. As an example, a destination configuration may be set up as
provided in the following table:
Basic Authentica­
Name
Type
Description
URL
<SYSID> Geofenc­ HTTP
<SYSID> Geofenc­ [INSERT LINK TI­
ing
ing
Proxy Type
tion Fields
OnPremise
Your Basic Authen­
TLE HERE]
tication User
Further additional parameters may be required, for instance to handle CSRF, if required based on backend
settings, for example:
SAP-Client
sap.iot.fetchXcsrf
sap.iot.XcsrfURL
<Your SAP Yard Logistics cli­
true
[INSERT LINK TITLE HERE]
ent>
Next, after the full IoT settings are completed n the Yard Logistics backend system, and all objects are
successfully registered within IoT Services tenant, the Geofence Event Action must be defined using the
destination configuration as created in the preceding step. In the IoT Services tenant, go to
Actions
Actions
Create
IoT Rules and
and create a new action for every geofencing relevant Thing type as follows:
Invocation
Response
Name
Triggered By
Thing Type
Action Type
Type
Method
Payload Type Destination
Your Action
Geofence
Your Thing
Service Inte­
Auto
POST
JSON
Name
Event
Type
gration
Your Destina­
tion to OData
Endpoint
Backend
As request body, the following static JSON structure, which is expected on the Yard Logistics backend system
side, must be added to the action using the actual property set as variable for latitude and longitude
parameters:
84
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
 Sample Code
{
"thingId": "${thing.id}",
"thingName": "${thing.name}",
"thingDisplayName": "${thing.description}",
"geofenceId": "${event.geo.fence.id}",
"geofenceName": "${event.geo.fence.name}",
"geofenceState": "${event.geo.fence.state}",
"measureTime": "${event.geo.measure.time}",
"thingLatitude": "${<your_property_set>.<latitude_property>}",
"thingLongitude": "${<your_property_set>.<longitude_property>}",
"eventTime": "${event.time}"
}
6.7.2.3
Maintain Settings for Internet of Things
On the SAP Fiori Launchpad, go to
for IoT as follows:
Internet of Things
Maintain IoT Settings (BTP)
and make the settings
In the dialog structure tree on the left-hand-side of the screen, select Source and choose Download Source. In
the dialog IoT & RFC Destination Registration, provide initially the mandatory information to establish the
technical connection to the IoT Services tenant:
OAuth 2.0 Client Pro­
SSL Client
file
HANA
Your OAuth Client
For technical integration between Yard Logistics and the IoT Services tenant, there are proper RFC destination
definitions required in the backend system for every IoT API endpoint that is needed to register particular types
of objects in the IoT tenant from the Yard Logistics side. Therefore, you must either define each RFC destination
manually in transaction SM59 – RFC Destinations (Display/Edit) or let these destinations be created
automatically by providing the following information for every API endpoint (Skip all Functions set to False):
Individual Skip
RFC Name
RFC Description
RFC Host
Path Prefix
Select false per RFC
Your RFC Destination
RFC Destination De­
API Endpoint (as de­
Endpoint URI
Destination to be cre­
Name per IoT API End­ scription
fined within your Serv­
ated automatically
point
ice Keys)
Select the newly created source entry. All subsequent entries are dependent sub-node settings of this source
entry and based on a GPS measurement example:
1. Go to Capability and create a new table entry with the following values:
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
85
Capability Alternate ID
Tenant ID
GPSCapability
GPS Capability
2. Select the newly created capability entry, go to Property and create a new table entry with the following
values:
Property Name
Data Type
LatitudeProperty
Float
LongitudeProperty
Float
Base Unit of Measure
3. Return to Capability, select the newly created entry TemperatureCapability and choose Register Capability
on the toolbar.
4. Go to Sensor Type and create a new table entry with the following values:
Sensor Type Alternate ID
Sensor Type Name
Your unique ID from 1 to 65535
GPS Sensor Type
5. Select the newly created sensor type entry, go to Map Capability to Sensor Type and create a new table
entry with the following values:
Capability Alternate ID
Type
GPSCapability
measure
6. Return to Sensor Type, select the newly created entry Sensor Type Alternate ID and choose Register Sensor
Type on the toolbar.
7. Go to Gateway and create a new table entry with the following values:
Gateway ID
Name
3
Standard Gateway
8. Go to Device and create a new table entry with the following values:
Device Alternate ID
Device Name
Gateway
GPSDevice
GPS Device
3
9. Select the newly created device entry, go to Sensor and create a new table entry with the following values:
86
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Sensor Alternate ID
Sensor Name
Sensor Type Alternate ID
GPSSensor
measure
Your unique ID from 1 to 65535
10. Return to Device, select the newly created entry GPSDevice and choose Register Device on the toolbar.
11. Go to Authorization Group and create a new table entry with the following values:
Authorization Group Name
Parent Authorization Group Name
GPSAuthorizationGroup
TENANT_ROOT
12. Go to Package and create a new table entry with the following values:
Package Name
Package Description
Your Package Name
Package Description
Select the newly created Package entry. All the following entries are dependent sub-node settings of the
Package entry:
1. Go to Property Set and create a new table entry with the following values:
Property Set ID
Property Set Description
Data Category
Sensitivity Level
GPSPropertySet
GPS Property Set
Time Series
Your Sensitivity Level
2. Select the newly created property set entry, go to Properties and create a new table entry with the
following values:
Property De­
Property ID
scription
Base Unit of
Property Type
LatitudeSetProp­ Measure
Measure
Decimals
Digit Amount
Amount
Numeric Flexible
0
0
Numeric Flexible
0
0
erty
LongitudeSet­
Measure
Property
3. Return to Property Set, select the newly created entry GPSPropertySet and choose Register Device on
the toolbar.
4. Go to Thing Type and create a new table entry with the following values:
Thing Type Name
Thing Type Description
GPSThingType
GPS Property Set
5. Select the newly created thing type entry, go to Map Property Set to Thing Type and create a new table
entry with the following values:
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
87
Property Set ID
GPSPropertySet
6. Return to Thing Type, select the newly created entry GPSThing Type and choose Register Thing Type on
the toolbar.
7. Select the newly created thing type entry, go to Connectivity Mapping and create a new table entry with
the following values:
Mapping De­
Mapping Name
scription
GPSMapping
GPS Mapping
8. Select the newly created connectivity mapping entry, go to Map Sensor Type to Thing Type and create
a new table entry with the following values:
Property Set
Property Name
Property ID
Property Set
LatitudeProperty LatitudeSetProp­
GPSProperySet
erty
LongitudeProp­
LongitudeSet­
erty
Property
GPSProperySet
9. Return to Connectivity Mapping, select the newly created entry GPSMapping and choose Map Sensor
Type to Thing Type on the toolbar
10. Go to Thing and create a new table entry with the following values:
Authorization Group
Thing Alternate ID
Name
Thing Name
Thing Description
GPSThingID
GPSAuthorizationGroup
GPSThing
GPS Thing
11. Select the newly created thing entry, go to Map Sensor to Thing and create a new table entry with the
following values:
Sensor Alter­
nate ID
Mapping Name
GPSSensor
GPSMapping
12. Return to Thing, select the newly created entry GPSThing and choose Register Thing on the toolbar.
13. Go to Assign Thing to TU and create a new table entry with the following values:
88
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Thing Alternate ID
Transportation Unit
GPSThingID
Your Transportation Unit
14. Exception for cases of IoT scenario, where actual measurements shall be stored within TU (here:
Example of temperature measurement; You must also refer to section ). Select the newly created thing
to TU assignment entry, go to Map Measurements to Thing and create a new table entry with the
following values:
Yard No.
Record Type
Property ID
Your Yard Number
TEMPER
TemperatureSet­
Property
6.7.2.4
Maintain Geofence Settings for Internet of Things
On SAP Fiori Launchpad, go to Internet of Things Maintain IoT Geofence Settings (BTP) and make the
settings for IoT as described below. In the dialog structure tree on the left-hand-side of the screen, select
Source and choose your source entry. All now following entries are dependent sub-node settings of this source
entry:
1. Go to Space and create a new table entry with the following values:
Space Name
Space Description
Parent Space Name
YardGeofenceSpace
Space for a Yard’s Geofences
2. Go to Map Yard to Space and create a new table entry with the following values:
Yard Number
Space Name
Your Yard Number
YardGeofenceSpace
3. Go to Geofence Location and create a new table entry with the following values:
Parent Location
Location Name
Location Description
Space Name
GeofenceCheckIn
Yard Check-In Geo­
YardGeofenceSpace
Name
Sensitivity Level
Personal Data
fence
Alternatively choose Download Geofence Location to select and download an already existing Geofence
Location definition from IoT Services Tenant and skip the steps 4 and 5.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
89
4. Select the newly created geofence location entry, go to Geofence Coordinates and create a new table entry
with the following values:
Sequence Number
Latitude Position
Longitude Position
1
7,111179828
49,273528083
2
7,111319303
49,273360082
3
7,111576795
49,273465083
4
7,111469506
49,273640083
5
7,111179828
49,273528083
6
7,111179828
49,273528083
It is important to provide the Position Sequence as a closed Polygon, this means the Positions of first
Sequence Number must be identical to Positions of the last Sequence Number.
5. Return to Geofence Location, select the newly created entry YardCheckIn and choose Register Geofence
Location on the toolbar.
6. Go to Storage Bin Group and create a new table entry with the following values:
Storage Bin Group Name
Storage Bin Group Description
Active for Geofencing
CheckInGroup
Check-In Checkpoint Group
True
7. Select the newly created storage bin group entry, go to Assign Storage Bin to Group and create a new table
entry with the following values:
Storage Bin
CheckInStorageBin
8. Select the newly created storage bin group entry, go to Assign Geofence Location to Group and create a
new table entry with the following values:
Geofence Location Name
GeofenceCheckIn
90
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
9. Go to Geofence Configuration and create a new table entry with the following values:
Property Set
Latitude Prop­ Longitude
Package
Thing Type
ID
erty ID
Property ID
Event Trigger
signment
Your Package
GPSThingType
GPSProperty­
LatitudeSet­
LongitudeSet­
Your desired
True or false
Set
Property
Property
trigger
Name
Exclusive As­
10. In case an Exclusive Assignment is enabled within Geofence Configuration, select the newly created
geofence configuration entry, go to Exclusive Geofence Assignment and create a new table entry with the
following values:
Thing Alternate ID
Location Name
Valid From Timestamp
Valid To Timestamp
GPSThingID
GeofenceCheckIn
Choose Validity from
Choose Validity to
Select the newly created entry and choose Register Assignment on the toolbar.
6.7.3 Integration to SAP IoT Services for Cloud Foundry
Environment
6.7.3.1
Maintain Settings for Internet of Things
On the SAP Fiori Launchpad, go to Internet of Things Maintain IoT Settings (CF) and make the settings
for IoT as described below. In the dialog structure tree on the left-hand-side of the screen, select Source and
create a new entry in the table providing the details for the new message type:
Source
Tenant ID
SAP CP Cloud Foundry Your Tenant ID
Tenant Name
Description
URI
Your Name
Your Description
Your Tenant URI
Select the newly created source entry. All now following entries are dependent sub-node settings of this source
entry:
1. Go to Capability and create a new table entry with the following values:
Capability Alternate ID
Tenant ID
TemperatureCapability
Temperature Capability
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
91
2. Select the newly created capability entry, go to Property and create a new table entry with the following
values:
Property Name
Data Type
Base Unit of Measure
TemperatureProperty
Temperature Property
°C
3. Return to Capability, select the newly created entry TemperatureCapability and choose Register Capability
on the toolbar.
4. Go to Sensor Type and create a new table entry with the following values:
Sensor Type Alternate ID
Sensor Type Name
Your unique ID from 1 to 65535
Temperature Sensor Type
5. Select the newly created sensor type entry, go to Map Capability to Sensor Type and create a new table
entry with the following values:
Capability Alternate ID
Type
TemperatureCapability
measure
6. Return to Sensor Type, select the newly created entry Sensor Type Alternate ID and choose Register Sensor
Type on the toolbar.
7. Go to Gateway and create a new table entry with the following values:
Gateway ID
Name
3
Standard Gateway
8. Go to Device and create a new table entry with the following values:
Device Alternate ID
Device Name
Gateway
TemperatureDevice
Temperature Device
3
9. Select the newly created device entry, go to Sensor and create a new table entry with the following values:
Sensor Alternate ID
Sensor Name
Sensor Type Alternate ID
TemperatureCapability
measure
Your unique ID from 1 to 65535
10. Return to Device, select the newly created entry TemperatureDevice and choose Register Device on the
toolbar.
92
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
11. Go to Map Measurement to Device and create a new table entry with the following values:
Field Measure­ Device Alter­
Sensor Type
Capability Al­
Property
Yard No.
Record Type
ment Value
nate ID
Alternate ID
ternate ID
Name
Your Yard
TEMPER
Temperature
Temperature­
Your unique ID
Temperature­
Temperature­
Device
from 1 to
Capability
Property
Number
65535
12. Go to Assign Device to TU and create a new table entry with the following values:
Device Alternate ID
Transportation Unit
TemperatureDevice
Your Transportation Unit
6.7.4 Integration to SAP IoT Services for Neo Environment
6.7.4.1
Connection Settings for Internet of Things
On the Fiori Launchpad, go to
Things
Internet of Things Settings
Maintain Connection Settings for Internet of
and maintain the following entry for your logical system:
● Destination to DMS (Device Management Service): DMS you have configured
● Destination to MMS (Message Management Service): MMS you have configured
6.7.4.2
Maintain Settings for Internet of Things
On the Fiori Launchpad, go to
Things
Internet of Things Settings
Maintain Message Settings for Internet of
and make the message settings for IoT as follows:
1. In the dialog structure tree on the left-hand-side of the screen, select Message Types and create a new
entry in the table providing the details for the new message type:
Message Type
Description
TemperatureMessage
Temperature
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
93
2. Select the newly created message type TemperatureMessage and create a new table entry under Message
Fields with the following values:
FieldPos
Field Name
Field Type
1
temperature
integer
3. Return to Message Types view and switch to edit mode, select the newly created entry
TemperatureMessage and choose Register Message Type on the toolbar.
4. Go to Device Types and create a new entry in the table providing details of the new device type.
Device Type
Description
TemperatureSensor
Temperature Sensor
5. Select the entry with the TemperatureSensor device type and enter the values in the subsequent view with
the message types assigned to this device:
Message Type
Direction
TemperatureMessage
From Device
6. Return to Device Types view, switch to edit mode and select the entry with message type
TemperatureSensor and choose Register Device Type on the toolbar.
7. Go to Devices view and create a new entry in the table providing the details for the new device:
Device Name
Device Type
Description
Thermometer
TemperatureSensor
Thermometer
8. Switch to edit mode, select the entry with device Thermometer and choose Register Device on the toolbar.
9. Go to Assign to Measurement Types and create a new entry in the table providing the details for the new
device:
94
Yard No.
Message Type
Record Type
Field with MeasVal
Thermometer
TemperatureMessage
TEMPER
temperature
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.7.4.3
Assign Transportation Unit to Devices
On the Fiori Launchpad, go to
maintain the following entries:
Internet of Things Settings
Assign Transportation Unit to Devices
Device Name
Transportation Unit
Thermometer
Your Transportation Unit
6.8
and
Customizing Settings for Integration with Dock
Appointment Scheduling (DAS) and SAP Logistics
Business Network (LBN)
6.8.1 Define Number Range Intervals for Appointment
Numbers
In Customizing for Yard Logistics, choose
Logistics Business Network
following entry:
Integration
Integration to Dock Appointment Scheduling or
Define Number Range Intervals for Appointment Numbers
No
From No.
To Number
01
1
9999999
and maintain the
6.8.2 Define Number Range Intervals for LBN Appointments
In Customizing for Yard Logistics, choose
Integration
Integration to Dock Appointment Scheduling or
Logistics Business Network Define Number Range Intervals for Logistics Business Network Appointments ,
specify the yard number, and maintain the following entry:
No .
From No
To Number
01
1
9999999
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
95
6.8.3 Create Docking Location
On the Fiori Launchpad, go to Dock Appointment Scheduling
and create a docking location using the following entries:
Master Data
Create Docking Location
Docking Location
Number Range
Docking Location
Description
Slot Duration
Time Zone
Country
Number
DL_TRCK
Truck Docking Lo­
15 Minutes
CET
DE
01
cation
6.8.4 Create Loading Point
On the Fiori Launchpad, go to Dock Appointment Scheduling
create a Loading Point using the following entries:
Master Data
Create Loading Point
Loading Point De­
and
Number Range
Loading Point
scription
Slot Duration
Time Zone
Country
Number
LP_TRCK
Truck Loading
15 Minutes
CET
DE
01
Point
6.8.5 Maintain Loading Appointment Relevance for Yard
Order Type
Describe whether SAP Dock Appointment Scheduling should be used for a Yard Order type.
In Customizing for Yard Logistics, choose
Integration
Integration to Dock Appointment Scheduling
Maintain Loading Appointment Relevance for Yard Order Type
and maintain the following entry:
Yard No.
Order Type
Direction
DSAppUsage
TRCK
TRCK
Inbound
X
D1
TRCK
Inbound
96
INTERNAL – Authorized for SAP Customers and Partners
LBN Usage
X
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.8.6 Maintain Loading Appointment Relevance for Yard
Order Type and TU Type
Define whether Dock Appointment Scheduling is relevant for a combination of Yard Number, Order Type and
TU type.
In Customizing for Yard Logistics, choose
Integration
Integration to Dock Appointment Scheduling or
Logistics Business Network Maintain Loading Appointment Relevance for Yard Order Type and TU Type
maintain the following entry:
Yard No.
Order Type
TU Type
TopLvlItem
AppRel
TRCK
TRCK
TR0
X
X
and
6.8.7 Assign Document Categories for Dock Appointment
Scheduling
Specify the SAP Document Appointment Scheduling document category assignment to SAP Yard Logistics
document categories.
In Customizing for Yard Logistics, go to
Integration
Integration to Dock Appointment Scheduling
and maintain the following entry:
Document Categories for Dock Appointment Scheduling
YLDocCat
Direction
DASDocCatH
DASDocCatI
Yard Order
Inbound
IO
IOI
Yard Order
Outbound
OO
OOI
Yard Request
Inbound
IR
IRI
Yard Request
Outbound
OR
ORI
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Assign
INTERNAL – Authorized for SAP Customers and Partners
97
6.8.8 Assign Docking Location and Loading Point to Yard
Number
On the Fiori Launchpad, go to
Settings
Integration to SAP Dock Appointment Scheduling
Assign Docking
and maintain the following entry:
Location and Loading Point to Yard Number
Yard No.
Docking Location
Loading Point
TRCK
DL_TRCK
LP_TRCK
6.8.9 Maintain Door Assignment to Docking Location and
Loading Point
On the Fiori Launchpad, go to
Settings
Integration to SAP Dock Appointment Scheduling
Assignment to Docking Location and Loading Point
Maintain Door
and make the following entries:
Yard No.
Storage Type
Docking Location
Loading Point
LBN Docking Lo­
cation
LBN Loading
Point
TRCK
DOOR
DL_TRCK
LP_TRCK
DL_TRCK
LP_TRCK
6.8.10 Business Partner Category for LBN Identification
Number
In Customizing for Financial Supply Chain Management, go to
Functions SAP Business Partner for Financial Services
Numbers
Define Identification Categories
Treasury and Risk Management
General Settings
Business Partner
Basic
Identification
and maintain the following entries:
BP Role Categories:
Identification
ID Cat.
Description
LBN001 X
LBN Identification
ID Unique
Disp. Only
One ID->BP
Schema
X
6.8.11 Control Automatic Yard Request Release
The automatic Yard Request Release must be triggered with the flag Automatic Release of Yard Request.
98
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
In Customizing for Yard Logistics, go to
Logistics Business Network
Integration
Integration to Dock Appointment Scheduling or
Control Automatic Yard Request Release
and maintain the entries as follows:
Yard No.
Order Type
AutRelYR
TRCK
TRCK
X
6.9
Customizing for EWM Integration
6.9.1 Preparation
In EWM, the respective warehouse and storage bins need to be customized. Also, their assignment to doors
and checkpoints needs to be done.
6.9.2 Maintain EWM Warehouse ID
To be able to map SAP Yard Logistics data with EWM data, EWM Warehouse ID must be maintained. To do so, in
Customizing for Yard Logistics go to
Maintain EWM Warehouse ID
Integration
Integration to SAP Extended Warehouse Management
and maintain the following values:
EWM Warehouse ID.
EWM Warehouse ID Description
EWM_WHSE
Warehouse ID Description
Auto crt TU
6.9.3 Maintain EWM Checkpoints
Specify checkpoints for each EWM warehouse ID, which represents the external or internal EWM system and
EWM warehouse.
In Customizing for Yard Logistics, go to
Maintain EWM Checkpoints
Integration
Integration to SAP Extended Warehouse Management
and enter the following:
EWM Warehouse ID
Checkpoint
Your defined Warehouse ID
Your EWM Checkpoint
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
99
6.9.4 Assign Warehouse ID to Storage Type
Assign the warehouse ID, which represents EWM system and the EWM warehouse, to the SAP Yard Logistics
storage type.
On the SAP Fiori Launchpad, go to
Storage Type
Settings
Integration to SAP EWM
Assign External Warehouse ID to
and enter the following::
Yard No.
Storage Type
EWM Warehouse ID
TRCK
Your Storage Type
EWM_WHSE
These settings are used during the integration with the external or internal EWM system.
6.9.5 Determine EWM Door
On SAP Fiori Launchpad, go to
following:
Settings
Integration to SAP EWM
Determine EWM Door
Yard No.
Storage Bin
EWM Warehouse ID
TRCK
Door1
EWM_WHSE
and enter the
EWM Dr
<EWM Door as defined in
EWM system>
6.9.6 Assign Docking Location to Warehouse
On the Fiori Launchpad, go to
and enter the following:
Settings
Integration to SAP EWM
Yard No.
Docking Location
EWM Whno
TRCK
DL_TRCK
LP_TRCK
100
INTERNAL – Authorized for SAP Customers and Partners
Assign Docking Location to Warehouse
EWM Business System
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.9.7 Automatic Determination of Warehouse Visits
To enable automatic determination of warehouse visits based on TU Type, on SAP Fiori Launchpad, go to
Settings
Integration to SAP EWM
Determination of Warehouse Visits
and enter the following:
Yard No.
TU Type
Direction
EWM Warehouse ID
TRCK
TR0
Inbound/Outbound/Internal
EWM_WHSE
6.9.8 Define Activity Types
The activity type which triggers the information from EWM to SAP Yard Logistics (Dock to Door) must have the
field Relevant for Subsystem selected for value EWM.
In Customizing for Yard Logistics, go to
follows:
Yard Tasks
Define Activity Types
and maintain the entries as
Whse Proc.
Activity Type
Yard No.
Acty Type
ActvtCateg.
Type
Description
No. range no
SubSysRel
TRCK
MODO
Movement
9999
Movement to
01
EWM
Door
6.9.9 Integration to External EWM System
 Note
for release 500 or 2667768
for previous releases for
Before you continue, check SAP Note 3094768
information about integrating SAP Yard Logistics for SAP S/HANA with the EWM warehousing functions in
SAP S/4HANA.
6.9.9.1
Assign EWM Business Systems and Warehouses to
Yard
The storage bins in Yard Logistics representing checkpoints and doors need to be mapped to the EWM door
and EWM checkpoint in EWM warehouse. To do so, in Customizing for Yard Logistics, go to
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Integration
INTERNAL – Authorized for SAP Customers and Partners
101
Integration to SAP Extended Warehouse Management
Business Systems and Warehouses to Yard
Integration with the External EWM
Assign EWM
and maintain the following values:
Yard No.
EWM Business System
TRCK
Your EWM Business System
EWM Whno
EWM Warehouse ID
your EWM Business System
EWM_WHSE
Warehouse Number
6.9.9.2
Maintain Logical Ports for EWM Integration
Maintain logical ports specified in SOAMANAGER. The logical port should be specified per external EWM
system for each of the used proxy classes.
On SAP Fiori Launchpad, go to
Integration
Settings
Integration to SAP EWM
Maintain logical ports for EWM
and enter the following values:
EWM Business System
Proxy Class of Logical Port
Logical Port
your EWM Business System
/SAPYL/CO_DOCK_APP_LOCK
Your Logical Port
your EWM Business System
/SAPYL/CO_DOCK_APP_UNLOCK
Your Logical Port
your EWM Business System
/SAPYL/CO_DOOR_ARR_DEPT
Your Logical Port
your EWM Business System
/SAPYL/CO_QUERY_EXTERNAL_TU
Your Logical Port
your EWM Business System
/SAPYL/CO_QUERY_EXT_TU_DATA
Your Logical Port
your EWM Business System
/SAPYL/CO_TU_CANCEL_CHECK_IN
Your Logical Port
your EWM Business System
/SAPYL/
Your Logical Port
CO_TU_CANCEL_CHECK_OUT
your EWM Business System
/SAPYL/CO_TU_CHECK_IN
Your Logical Port
your EWM Business System
/SAPYL/CO_TU_CHECK_OUT
Your Logical Port
your EWM Business System
/SAPYL/CO_TU_LOCK
Your Logical Port
your EWM Business System
/SAPYL/CO_TU_UNLOCK
Your Logical Port
your EWM Business System
/SAPYL/CO_VEHICLE_CHECK_IN
Your Logical Port
your EWM Business System
/SAPYL/CO_VEHICLE_CHECK_OUT
Your Logical Port
your EWM Business System
/SAPYL/CO_VEHICLE_LOCK
Your Logical Port
your EWM Business System
/SAPYL/CO_VEHICLE_QUERY
Your Logical Port
102
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
EWM Business System
Proxy Class of Logical Port
Logical Port
your EWM Business System
/SAPYL/CO_VEHICLE_UNLOCK
Your Logical Port
your EWM Business System
/SAPYL/CO_VEH_CANCEL_CHECK_IN Your Logical Port
your EWM Business System
/SAPYL/
Your Logical Port
CO_VEH_CANCEL_CHECK_OUT
These entries are used during integration with the external EWM system, which is accessed via webservices.
6.9.10 Integration to Internal EWM
 Note
Before you continue, check SAP Note 3093893
for information about integrating SAP Yard Logistics for
SAP S/HANA with Internal EWM in SAP S/4HANA.
6.9.10.1 Activate Internal EWM
To be able to activate an Internal EWM Integration and use it instead of integration to an external EWM system,
which is used by default, in Customizing for Yard Logistics, go to
Warehouse Management Integration with the internal EWM
maintain the following values:
Integration
Integration to SAP Extended
Activate Internal EWM Integration
Yard No.
Act EWM In.
TRCK
X
and
6.9.10.2 Assign Internal EWM Warehouses to Yard Numbers
The storage bins in Yard Logistics representing checkpoints and doors need to be mapped to the EWM door
and EWM checkpoint in EWM warehouse. To do so, in Customizing for Yard Logistics, go to
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Integration
INTERNAL – Authorized for SAP Customers and Partners
103
Integration to SAP Extended Warehouse Management
Business Systems and Warehouses to Yard
Yard No.
Integration with the internal EWM
and maintain the following values:
EWM Whno
TRCK
Assign EWM
EWM Warehouse ID
your EWM Business System Warehouse EWM_WHSE
Number
6.9.10.3 Define Number Range Interval for Internal EWM
Transportation Units in SAP Yard Logistics for SAP
S/4HANA
In Customizing for Yard Logistics, go to
Integration with the Internal EWM
Logistics
Integration
Integration to SAP Extended Warehouse Management
Define Number Range Interval for Internal EWM Transportation Units in Yard
and maintain the following values:
No .
From No
To Number
01
1
9999999
6.10 Customizing for TM Integration
6.10.1 Preparation
 Note
Before you start making the configuration settings described in the following, you must refer to SAP Note
2667883
- Implementation information about the integration of SAP Yard Logistics for SAP S/4HANA
and SAP TM in SAP S/4HANA 1709.
 Note
For TM modeled Advanced Shipping & Receiving (ASR) Integration, refer to SAP Note 3093894
Implementation information about the integration of SAP Yard Logistics for SAP S/4HANA and TM
modeled ASR in SAP S/4HANA.
104
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.10.2 Map TM Freight Order Types
In Customizing for Yard Logistics choose
Integration
Integration to SAP Transportation Management
Map
TM Freight Order Types
This mapping of the freight order type from TM to order type in Yard Logistics is needed for the creation of a
Yard Request.
This order type is used for the yard request creation.
Yard Order Type De­
FO Type
Yard No.
Order Type
Map Hier.
scription
<your TM FO type>
TRCK
TRCK
Consider TU Loading
Truck Order Type
Hierarchy
6.10.3 Map TM Relevant TU Types for Yard Request
In Customizing for Yard Logistics choose
Integration
Integration to SAP Transportation Management
Map TM Relevant TU Types for Yard Request .
This table contains the mapping of TM item categories, which are delivered by SAP, and the TM means of
transports to yard logistics TU type and means of transport.
Based on this setting the items in the Yard Request will be created.
Yard No.
Order Type
Itm Cat.
Equip/Veh
TM MTr
TRCK
TRCK
AVR
Your TM Equip/ Your TM MTr
MTr
TU Type
TRUCK
TR0
TRAILER
TR1
CONTAINER
CO1
Veh. Type
TRCK
TRCK
PVR
Your TM Equip/ Your TM MTr
Veh. Type
TRCK
TRCK
TUR
Your TM Equip/ Your TM MTr
Veh. Type
6.10.4 Map TM Business Partner Roles
In Customizing for Yard Logistics choose
Integration
Integration to SAP Transportation Management
Map TM Business Partner Roles
It is possible to take over the business partners from TM Freight Order to the Yard Request. Therefore this
mapping of the business partner roles is needed.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
105
TM BUPA
TM Business Partner Role Description BUPA Role
TM BUPA role no. 1
Ordering Party
0001
TM BUPA role no. 2
Bill-to Party
0002
TM BUPA role no. 3
Requester
0003
TM BUPA role no. 4
Carrier
0004
6.10.5 Map Business Transaction Document Type Code
In Customizing for Yard Logistics choose
Integration
Integration to SAP Transportation Management
Map Business Transaction Document Type Code . Also the reference document can be taken over from the TM
Freight Order to the Yard Request. The mapping is used for this functionality.
TM DocType
Ref. Type
TM DocType 1
INV
6.10.6 Map TM Timestamp to Yard Request Time Point
In Customizing for Yard Logistics choose
Integration
Integration to SAP Transportation Management
Map TM Timestamp to Yard Request Time Point ,
In this Customizing activity, you make settings for mapping of Freight Order time points as requested/
acceptable (un)loading, departure and arrival time stamps into Yard Request relevant dates and times, which
are specific for each Yard Number and Yard Request Type combination.
● For outbound scenario, relevant time points are arrival, loading and departure.
● For inbound scenario, relevant time points are arrival, unloading and departure.
YO Date Time Re­
cord Type De­
Yard No.
Order Type
Direction
TM TPoint
RecType
scription
TRCK
TRCK
Inbound
06 Planned Yard
01
Arrival
02
Departure
Arrival Timestamp
TRCK
TRCK
Outbound
05 Planned Yard
Departure Time­
stamp
106
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.10.7 Map External Reference Documents to YO Header
Reference Documents
Integration
In Customizing for Yard Logistics choose
Integration to SAP Transportation Management
Map External Reference Documents to YO Header Reference Documents .
In this Customizing activity, you map the external reference document types to the header reference document
types for the yard order.
TM Doc Typ
RefDocType
Yard No.
Order Type
Ref. Type
TM DocType 1
TO
TRCK
TRCK
FO
6.10.8 Map External Reference Documents to YO Item
Reference Documents
In Customizing for Yard Logistics choose
Integration
Integration to SAP Transportation Management
Map External Reference Documents to YO Item Reference Documents .
In this Customizing activity, you assign the external reference item document types to the item reference
document types for the yard order.
Business
Transaction
TM Doc Typ
Document
TM DocType 1 TM BTD 1
BTD Item
Yard No.
Order Type
TU Type
Ref. Type
RefItem Type
TM BTD Item
TRCK
TRCK
TR0
FO
FOI
TRCK
TRCK
TR1
FO
FOI
TRCK
TRCK
CO1
FO
FOI
1
TM DocType 1 TM BTD 2
TM BTD Item
2
TM DocType 1 TM BTD 3
TM BTD Item
3
6.10.9 Assign Transportation Unit Type to Packaging Material
On the Fiori Launchpad, choose
Settings
Integration to SAP Transportation Management
Assign
Transportation Unit Type to Packaging Material .
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
107
Yard No.
Order Type
Equip/Veh
TU Type
Packaging Material
TRCK
TRCK
Your TM Equip/Veh.
TR0
PACK_TRUCK
TR1
Your own packaging
Type
TRCK
TRCK
Your TM Equip/Veh.
Type
TRCK
TRCK
material for trailer
Your TM Equip/Veh.
CO1
Type
Your own packaging
material for container
6.10.10 Integration to Plant Maintenance
 Note
for information about integrating SAP Yard Logistics for
Before you continue, refer to SAP Note 3094933
SAP S/4HANA with Plant Maintenance in SAP S/4HANA.
6.10.10.1 Define Plant Maintenance Equipment Category
To define an equipment category, which must be assigned to equipment that is created during PM Integration,
in Customizing for Yard Logistics, go to
Equipment Category
Integration
Integration to SAP Plant Maintenance
and maintain the following values:
Yard No.
Equipment Category
TRCK
[equipment category from PM search help]
108
Define PM
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.10.10.2 Define PM Workorder Content Structure
In Customizing for Yard Logistics, go to
Workorder Content Structure
Integration
Integration to SAP Plant Maintenance
Define PM
and maintain the following values for PM workorder header data:
Functional
Storage
PM Order
Planning
Main Work
Business
Planner
loc cate­
Structure
Yard No.
Type
Type
Plant
Center
Area
Group
gory
Indicator
TRCK
DOOR
PM_01t
1000
MD_EE
0001
010
M
YL
These settings are used during Integration to create PM workorders.
6.10.10.3 Define Activity Types
To trigger PM Integration, the activity type must be defined as Relevant for Subsystem.
To make this setting, in Customizing for Yard Logistics, go to
maintain the entries as follows:
Yard Tasks
Define Activity Types
and
Whse Proc.
Activity Type
Yard No.
Acty Type
ActvtCateg.
Type
Description
No. range no
SubSysRel
TRCK
MVPM
Movement
9999
PM Movement
01
PM
6.11
Customizing for BRFPlus
6.11.1 Dynamic Yard Order Operations
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
109
6.11.1.1 Define Whether to Activate Yard Task Related to Yard
Order Automatically
To activate dynamic BRFPlus operations for yard orders, in Customizing for Yard Logistics choose
Request and Yard Order
following entry:
Define Whether to Activate Yard Task of Yard Order Automatically
Yard No.
Order Type
TRCK
TRCK
ActFirstYT
ActNextYT
Yard
and maintain the
ACtDynOpr
X
6.11.1.2 Activate Examples of Rulesets
In transaction BRF+, go to the application /SAPYL/DYN_YT_SYS and enable the following rulesets on the tab
Assigned Rulesets for each function in the following table:
Application
Function
Ruleset
/SAPYL/DYN_YT_SYS
/SAPYL/FU_YO_GENERIC_EXECUTE
/SAPYL/RS_EXAMPLE_CRT_DFLT_YT
/SAPYL/DYN_YT_SYS
/SAPYL/FU_YO_GENERIC_EXECUTE
/SAPYL/RS_EXAMPLE_CANCEL_YT
6.11.2 Dynamic Yard Task Operations
6.11.2.1 Activate BRF+ for Activity Types
Activate dynamic BRF+ operations for yard task.
In Customizing for Yard Logistics choose
following entry:
Yard Tasks
Activate BRF+ for Activity Types
Yard No.
Activity Type
ActDynOpr
TRCK
MV01
X
110
INTERNAL – Authorized for SAP Customers and Partners
and maintain the
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.11.2.2 Activate Examples of Rulesets
In transaction BRF+, go to application /SAPYL/DYN_YT_SYS and enable rulesets on tab Assigned Rulesets for
each function from the following table:
Application
Function
Ruleset
/SAPYL/DYN_YT_SYS
/SAPYL/FU_YT_GENERIC_EXECUTE
/SAPYL/
RS_EXAMPLE_CRT_YT_QUEST
SAPYL/DYN_YT_SYS
/SAPYL/FU_YT_GENERIC_EXECUTE
/SAPYL/
RS_EXAMPLE_MEAS_YT_FUEL
/SAPYL/DYN_YT_SYS
/SAPYL/FU_YT_GENERIC_EXECUTE
/SAPYL/RS_EXAMPLE_INSP_FOLLUP
/SAPYL/DYN_YT_SYS
/SAPYL/FU_INSPECTION_DET
/SAPYL/
RS_EXAMPLE_INSP_PROFILE
6.11.3 Dynamic Yard Document creation for Opposite
Direction
6.11.3.1 Auto-Generate Opposite Yard Order/Yard Request
In Customizing for Yard Logistics, choose
Yard Request and Yard Order
Auto-generate Opposite Yard Order/
Yard Request and maintain the following entries:
CreatInbY
Yard No.
Order Type R
TRCK
TRCK
CreateOut
CreatInbY
CreatOutY
CheckInIY
CompInbY
ActvOutbY
YR
O
O
O
O
O
ActDynCR
X
6.11.3.2 Activate Examples of Rulesets
In transaction BRF+, go to application /SAPYL/YO_OPPOSITE_SYS and enable rulesets on tab Assigned
Rulesets for each function from the following table:
Application
Function
Ruleset
/SAPYL/YO_OPPOSITE_SYS
/SAPYL/FU_YT_GENERIC_EXECUTE
/SAPYL/RS_EXAMPLE_CR_OUTB_YO
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
111
6.12 Customizing for Berth Scheduling
6.12.1 Set up Optimization Function Library
6.12.1.1 Install Application Function Library (AFL) Plug-in
Application Function Libraries (AFL) extend the functionality of SAP HANA by adding additional functions that
can be called, for example, via ABAP managed database procedures. AFLs are SAP HANA system components.
SAP HANA system components can be installed, updated, or uninstalled using the SAP HANA Database
Lifecycle Manager (HDBLCM).
The AFL required for Berth Scheduling is called Optimization Function Library (OFL). The libaflofl.so or
libaflofl.dll is delivered starting with HANA 1.0 SPS08 and can be downloaded and installed using the
default AFL delivery process. It is part of the generic AFL installer. It is not a product specific AFL. Make sure to
have matching versions of your HANA database and AFL package. You can download the AFLs from the SAP
Support Portal , searching entry by component SAP HANA AFL.
The MILP API for solving linear or mixed integer problems is only allowed to be used in SAP products or
projects. Because of licensing restriction customers or partners must not use it directly.
6.12.1.2 Activate SAP HANA Script Server
Activate the script server for the SAP HANA database. The script server is an auxiliary SAP HANA server that is
required to execute application function libraries (AFLs). In SAP HANA studio. You must check beforehand
whether the script server is active. If it is not, you must start it manually. To do this, read and implement SAP
Note 1650957 .
6.12.1.3 Assign Privileges to System User
As with all AFLs, the user executing the AFL must have special authorization roles granting execution. For OFL,
the roles name is AFL__SYS_AFL_OFL_AREA_EXECUTE. This role must be assigned to the HANA DB user that
executes the optimization procedures. The name of the HANA DB user is identical to the schema name used
for SAP Yard Logistics for SAP S/4HANA. If default settings are applied, the username is SAPHANADB.
112
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.12.2 Define Customer-specific Attributes and Attribute
Values
Customer specific attributes are optional. Berth scheduling is possible even if the tables mentioned in this
chapter have no content.
Customer specific attributes allow you to maintain attributes that must be considered for berth planning. For
example, if you as a customer are handling liquid products, for you containers may define an attribute
SPECIAL_EQUIPMENT. This attribute may have values like PUMP or CRANE.
For clarity, we briefly mention how such attributes can be used. This will be elaborated in further detail in the
following sections. An attribute can be assigned to a berth option. For berth options for which attribute
SPECIAL_EQUIPMENT with attribute value PUMP is maintained, a pump is available. On the other side,
attributes can be assigned to ship visits. By assigning attribute SPECIAL_EQUIPMENT with attribute value
PUMP to a ship visit, it can be defined that to handle the cargo of that specific ship visit, a pump is required.
Berth scheduling would select a berth option that is equipped with a pump to berth that specific ship visit.
6.12.3 Define Customer-specific Attributes
You define customer-specific attributes in Customizing for SAP Yard Logistics for SAP S/4HANA under
Logistics
Yard Request and Yard Order
Planning Optimization
Yard
Define Attributes .
The following table shows sample data just in order to facilitate the explanation. As mentioned above, customer
specific attributes are optional, and the table could be empty.
Customizable At­
Customizable At­
tribute Descrip­
Yard No.
tribute ID
tion
TRCK
SPECIAL_EQUIP
TRCK
RAMP_POSITION
Hard Const.
Cost Priority
Operator
Special equipment X
0
AND operator
Available loading
0
OR operator
1
No applicable op­
X
positions for ship
TRCK
MANUFAC
Manufacturer of
cargo
erator
Customizable Attribute ID defines a string that is used as the ID for this attribute. Customizable Attribute
Description is optional. Hard Const. defines whether or not this attribute defines a hard constraint in the sense
that it is used to the determine the set of possible berth options for a ship visit. In case the attribute is not a
hard constraint, it is used to differentiate berth options by price. For example. it might be more economical to
handle a certain manufacturer at a certain berth option compared to other berth options. This will be further
explained in the following sections. Operator is applied in case the attribute defines a hard constraint. In cases
where multiple attributes are assigned, It defines whether just one of the attributes (OR operator) or all them
must be met (AND operator).
Cost Priority is applied to introduce a sequence for the attributes that influences the penalty cost. This
sequence is needed in case there is no prefect match in the penalty cost matrix, and default values are applied.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
113
For attributes with a lower priority (higher number), the logic will try to apply default values first. This will be
further elaborated in one of the following chapters.
Using the sample data provided above; in case you define for a ship visit the attribute SPECIAL_EQUIP with
attribute values PUMP and CRANE see section Define Customer-specific Attribute Values [page 114]) and
define the AND operator, it means that a berth option for that ship visit must provide a crane and a pump. In
case we define for a ship visit the attribute RAMP_POSITION with attribute values STERN and QUARTER (see
section Define Customer-specific Attribute Values [page 114]) and define the OR operator, it means that a
berth option that facilitates loading and unloading via stern or quarter ramp is suitable.
6.12.4 Define Customer-specific Attribute Values
You define customer-specific attribute values in Customizing for SAP Yard Logistics for SAP S/4HANA under
Yard Logistics
Yard Request and Yard Order
Planning Optimization
Define Attributes Values .
The following table shows only sample data. As mentioned above, customer specific attributes are optional,
and the table could be empty.
Yard No.
Customizable attribute ID
Customizable attribute value
TRCK
SPECIAL_EQUIP
PUMP
TRCK
SPECIAL_EQUIP
CRANE
TRCK
RAMP_POSITION
STERN
TRCK
RAMP_POSITION
QUARTER
TRCK
MANUFAC
M1
6.12.5 Define Berths, Berth Positions, and Berth Options
6.12.5.1 Define Berths
114
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
6.12.5.1.1 Maintain Storage Bin Type
You maintain storage bin types in Customizing for SAP Yard Logistics for SAP S/4HANA under
Yard Request and Yard Order
Planning Optimization
Yard Logistics
Maintain Storage Bin Type Relevant for Planning .
The following table shows only sample data.
Yard No.
Plan Type
Storage Bin Type
TRCK
Berth
BRTH
Berth scheduling can be done even without maintaining the storage bin type. It is used in manually assigning
ship visits to berth positions and to display the berth plan.
6.12.5.1.2 Maintain Berth Attributes
As mentioned above, a berth is a storage bin. Unlike other storage bins, a berth has additional attributes that
need to be maintained. To maintain berth attributes, on the SAP Fiori Launchpad, in the Berth Planning tile
group, choose Maintain Berth.
The following table contains sample data for Illustrative purposes:
Min. Spa­
tial Dis­
Min. Time
tance be­
Distance
tween
between
MaxNum­
Max.
Yard No.
Berth
Length
Ships
Ships
Ship
Draft
UoM Time Length
UoM
DG flag
TRCK
Berth1
100
10
60
2
15
MIN
M
X
TRCK
Berth2
80
15
90
1
20
MIN
M
Length defines the length of a berth. Ship visits are only assigned to berth options so that the length of the
berth is not exceeded by ship length.
Min. Spatial Distance between Ships defines the physical space that must be maintained between two ships
that berth at that berth at the same time.
Min Time Distance between Ships defines the time span that must be considered between two ships that are
(partially) using the same berth positions.
MaxNumShip defines the maximum number of ships that can be berthed at the same time.
UoMTime provides the UoM for the time field in this table.
UoMLength defines the unit of measurement for the length dimension.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
115
 Note
UoMLength must be equal for all entries in this table. This UoM will be considered as master UoM for berth
planning and all other length values, for example, ship length, will be converted into this master UoM.
DG Flag defines whether or not dangerous goods can be handled at this berth.
6.12.5.1.3 Maintain Customer-specific Berth Attributes
In previous sections we defined customer-specific attributes. In case of hard constraint attributes, they can be
assigned to a berth. It implies that an attribute, which is defined for a particular berth is applied to all berth
options belonging to the berth. Since a berth can have a large number of berth options, applying attributes at
the berth level facilitates the maintenance of master data.
To maintain berth attributes, on the SAP Fiori Launchpad, in the Berth Planning tile group choose Maintain
Berth Level Optional Attribute Values.
For example, you can maintain the information that the special equipment Pump and Crane are available for all
berth options that belong the berth 1.
The following table contains sample data for Illustrative purposes:
Customizable Attribute
Yard No.
Berth
Customizable Attribute ID
Value
TRCK
Berth1
SPECIAL_EQUIP
PUMP
TRCK
Berth1
SPECIAL_EQUIP
CRANE
6.12.5.2 Define Berth Positions and Berth Options
A berth is usually a very long object that is further discretized (or divided) into a number of berth positions. For
example, a berth, let’s call it Berth1, which is 100 meters long, might be further discretized into 11 berth
positions; one position every 10 meter. This results in berth positions like (Berth 1 – 0, Berth 1 – 10, …, Berth 1 –
90, Berth 1 – 100). Now that we have introduced berth positions, we can introduce berth options. Berth options
describe an option to place a ship at that berth position. A berth option consists of a berth position and an
orientation. The berth position describes where the stern of the ship is placed, for example, at Berth 1 – 20. The
orientation provides the direction in which the bow of the ship is pointing, up or down; up, if the bow is pointing
in the direction of the ascending order of berth positions, and down, if the opposite is the case.
For our example there would be 22 (theoretical) berth options, like (Berth 1 – 0 – UP, Berth 1 – 0 – DOWN,
Berth 1 – 10 – UP, Berth 1 – 10 – DOWN, …, Berth 1 – 90 – UP, Berth 1 – 90 – DOWN, Berth 1 – 100 – UP, Berth 1
– 100 – DOWN). Of course, berth options like Berth 1 – 0 – DOWN and Berth 1 – 100 – UP make only limited
sense. However, they are not a hinderance, as the berth scheduling algorithm automatically determines
feasible berth options for each ship visit.
To maintain berth options, on the SAP Fiori Launchpad, go to
116
INTERNAL – Authorized for SAP Customers and Partners
Berth Planning
Maintain Berth Options .
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
The following table contains sample data for Illustrative purposes:
Yard No.
BerthOptID
Berth
BerthPos
OriBerth
BerPosPrio
DG flag
TRCK
B1_0_U
Berth1
0
Up
1
x
TRCK
B1_10_U
Berth1
10
Up
2
x
TRCK
B1_10_D
Berth1
10
Down
2
x
TRCK
B1_20_U
Berth1
20
Up
2
x
TRCK
B1_20_D
Berth1
20
Down
2
x
The fields Berth, BerthPos and OriBerth should be clear. As a berth option is defined by those three fields, and
because we will use the berth positions in other tables. A berth option ID is introduced in field BerthOptID. This
can be any string as long as it is a key for a berth option.
The field BerPosPrio defines a priority for berth scheduling in case the berth scheduler does not choose
between different berth options. It is easy to imagine that the berth options B1_0_U and B1_10_U might result
in the same cost, because they are just 10 meters apart. In such a case the solver would select the berth option
with the higher priority, expressed by a lower number. So, for our example, B1_0_U would be selected.
Using the DG flag, it can be defined whether an individual berth option is suitable for handling dangerous
goods.
 Note
It is also possible to set this flag at berth level. If set at berth level, it is applied to all berth options that
belong to that berth. In such a case, it is not required to set the flag in this table again for each individual
berth option.
6.12.5.3 Maintain Customer-specific Berth Option Attributes
As for berths, it is possible to assign customer specific attributes to berth options. To do so, on the SAP Fiori
Launchpad, go to the tile group
Berth Planning
Maintain Berth Options Attribute Values .
The following table contains sample data for Illustrative purposes:
Customizable Attribute
Yard No.
BerthOptID
Customizable Attribute ID
Value
TRCK
B1_0_U
SPECIAL_EQUIP
PUMP
TRCK
B1_0_U
SPECIAL_EQUIP
CRANE
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
117
6.12.6 Define Ship Master Data
In previous sections, we have defined data that describes the berth options. One can think of this as the supply
side of the optimization problem. The demand side would be the ship visits. These ship visits must be matched
with berth options in an optimal manner. A ship visit is defined by its arrival and departure time, the cargo that
needs to be loaded or unloaded, and, the ship itself. In this section, we focus on the physical ship. A ship is
modeled as a transportation unit. Each transportation unit has a transportation unit type. In order to identify a
ship, we have to define which transportation unit type identifies a ship. The relevant settings are maintained in
Customizing for SAP Yard Logistics under
Yard Logistics
Yard Request and Yard Order
Maintain
Transportation Unit Type Relevant for Planning. .
The following table contains sample data for Illustrative purposes:
Yard No.
TU Type
PlanType
TRCK
SHIP
Berth
Visit https://help.sap.com/yl_s4hana on SAP Help Portal and refer to the product assistance documentation
for the solution for information on creating transportation units and packaging materials.
6.12.7 Define Decision Criteria
6.12.7.1 Define Berth Option Groups
In previous chapters we have seen how a berth option is defined and that there can be a large number of berth
options. The penalty cost matrix is used to assign a price for each ship visit/berth option combination. We also
saw that similar berth options might have the same cost when we introduced the berth options priorities. In
order to allow to maintain the same costs with a single entry in the penalty cost matrix, berth options can be
grouped in a customer-specific manner. As can be seen from the penalty cost matrix, costs are defined for
berth options groups.
To maintain berth option groups, on the SAP Fiori Launchpad, go to the tile group
Berth Planning
Define
Berth Option Group .
The following table contains sample data for Illustrative purposes:
Yard No.
Berth Option Group ID
BerthOptID
TRCK
BERTH1_FIRST_PART
B1_0_U
TRCK
BERTH1_FIRST_PART
B1_10_U
118
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
Yard No.
Berth Option Group ID
BerthOptID
TRCK
BERTH1_FIRST_PART
B1_10_D
…
…
…
TRCK
BERTH1_SECOND_PART
B1_90_U
TRCK
BERTH1_SECOND_PART
B1_90_D
TRCK
BERTH1_SECOND_PART
B1_100_D
6.12.7.2 Define Penalty Cost Matrix
The penalty cost matrix defines a price for loading or unloading a specific cargo at a berth option group. This is
not necessarily a monetary price. It can also be working time or any other parameter. It is important to
understand that the berth scheduling algorithm will try to assign ship visits to berth options so that the sum of
the penalty cost over all ship visits is minimized.
The cargo for a specific ship visit is defined in planning groups. This is transaction data and explained in the
product assistance guide. Let’s assume the cargo of a ship visit is defined like this:
500 inbound Containers that should be unloaded from the ship to storage bin NE-12. Using the penalty cost
matrix entries P1 and P2 below, we see that if the ship is placed at a berth option that belongs to berth option
group BERTH1_FIRST_PART, the price is 500 time 5.1 which equals 2550. If the ship is placed at a berth option
that belongs to berth option group BERTH1_SECOND_PART, the price is 500 time 5.4 which equals 2700.
Therefore, the berth scheduler would prefer a berth option that belongs to berth option group
BERTH1_FIRST_PART. It is easy to imagine that this matrix can become very large. It is nevertheless the main
criterion for the berth scheduler. To maintain the penalty cost matrix, on the SAP Fiori Launchpad, go to the tile
group
Berth Planning
Maintain Penalty Cost Matrix .
The following table contains sample data for Illustrative purposes:
Penalty
Penalty
Berth
Cost
cost
option
matrix
Quan­
matrix
group
quan­
tity
Storage Storage Storage Direc­
Pen.
Yard No. entry ID ID
tity
UoM
Product DG flag
Bin
Section
Type
tion
cost
TRCK
1
PC
CON­
NE-012
NE
AREA
Inbound 5.1
NE-012
NE
AREA
Inbound 5.4
P1
BERTH1
_FIRST_
TAINER
PART
TRCK
P2
BERTH1
1
PC
_SEC­
CON­
TAINER
OND_PA
RT
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
119
Penalty
Penalty
Berth
Cost
cost
option
matrix
Quan­
matrix
group
quan­
tity
Storage Storage Storage Direc­
Pen.
Yard No. entry ID ID
tity
UoM
Product DG flag
Bin
Section
Type
tion
cost
TRCK
1
PC
CON­
NE-012
NE
AREA
Out­
4.9
P3
BERTH1
_FIRST_
TAINER
bound
PART
TRCK
P4
BERTH1
1
PC
_FIRST_
CON­
NE-012
NE
AREA
TAINER
Out­
5.3
bound
PART
TRCK
P5
BERTH1
1
PC
_FIRST_
CON­
x
NE-013
NE
AREA
TAINER
Out­
5.9
bound
PART
6.12.7.3 Define Penalty Cost Matrix Attribute Values
We can define customer specific attributes in the penalty cost matrix. On SAP Fiori Launchpad, go to the tile
group Berth Planning Maintain Penalty Cost Matrix Attributes . In the matrix below, you see that entry P3
and P4 are equal. However, for entry P4, customer specific attributes are defined. P4 would be applied if the
cargo has the attribute MANUFAC = M1 and P3 would be applied, if otherwise. Again, the attribute for the cargo
is defined for an entity called Planning Group that is explained in the product assistance guide.
The following table contains sample data for Illustrative purposes:
Penalty Cost Matrix Entry
Customizable Attribute
Yard No.
ID
Customizable Attribute ID
TRCK
P3
MANUFAC
TRCK
P4
MANUFAC
Value
M1
6.12.7.4 Apply Cost Priorities and Default Values in Penalty
Cost Matrix
In this section we explain how the cost priority of an attribute is applied and how default values can be defined
in the penalty cost matrix.
120
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
 Note
This information is optional and only needed in case default values are introduced into the penalty cost
matrix. Default values are used in case a full match in all attributes between cargo and entry in penalty cost
matrix entry is not possible.
As mentioned above, cost priorities of the user defined attributes are used to determine the order of evaluation
of these attributes when determining the penalty cost entries that apply for a certain visit.
More precisely, when trying to determine the cost of assigning a certain visit to a certain berth position (group),
the algorithm inspects all the user defined, non-“hard constraint”, attribute values of the visit in the order of
their defined priorities, and tries to match them with the attribute values of the penalty cost matrix entries. This
continues as long as exact matches can be found (the set of values for the currently considered attribute
match exactly between the visit and the cost matrix). When an exact match can no longer be found for a certain
attribute, the cost matrix entry with a default value for that attribute will be used and further evaluation of lower
priority attributes is suspended.
The next example illustrates the process described above:
Suppose we have defined 4 non-“hard constraint” attributes (ATTR_1 – 4, with priorities 1 to 4 in this order),
each with 3 possible values (ATTR_1_VAL_1 – 3, etc).
Suppose we want to find the cost of assigning a visit to a certain berth option group and that this visit has the
following attribute values:
ATTR_1: ATTR_1_VAL_1, ATTR_1_VAL_3
ATTR_2: no values
ATTR_3: ATTR_3_VAL_2
ATTR_4: ATTR_3_VAL_2, ATTR_3_VAL_3
We proceed in the following manner:
First, we find the set of cost matrix entries with matching non-user defined attributes (berth option group,
material, dangerous goods, storage type/ section/ bin). Suppose this set of entries is non-empty, then, among
these entries, we filter those which have the same values for attribute ATTR_1 (exactly ATTR_1_VAL_1 and
ATTR_1_VAL_3). Suppose this filtered set of entries is still non-empty, then, among this newly filtered set of
entries, we filter further for those that have no values for attribute ATTR_2.
Then, among this newly filtered set of entries, we filter further for those that have only ATTR_3_VAL_2 as value
for attribute ATTR_3. Suppose this last filtering yields no results. In that case, we choose the (single) entry with
the default string as the only value for ATTR_3 (from the filtered set of entries determined in the previous step).
We stop here and we don’t filter further for ATTR_4 values.
6.12.7.5 Define Berth Scheduler Configuration
The berth scheduler can be parameterized via a configuration table. To do so, on SAP Fiori Launchpad, go to
the tile group
Berth Planning
Maintain Berth Optimization Configuration .
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
121
Yard No.
Parameter Name
Parameter Value
TRCK
MSGID
/SAPYL/BO_MSG
TRCK
INBOUND_DATE_TIME_RECORD_TYPE 01
TRCK
OUTBOUND_DATE_TIME_RE­
02
CORD_TYPE
TRCK
ORDER_TYPE_BERTH_PLANNING
SHIP
TRCK
OFL_RUNNING_TIME
100
TRCK
OFL_COST_COEFFS_VB_FIXED_COST
0
TRCK
OFL_COST_CO­
10000
EFFS_VB_ORD_IDX_COEFF
TRCK
OFL_COST_CO­
0
EFFS_VB_TIME_DIST_COEFF
TRCK
OFL_OPT_LARGE_BATCH_SIZE
100
TRCK
OFL_MERGE_TO_BE_PLAN­
0
NED_YRS_INTO_EXISTING_PLAN
TRCK
OFL_MAX_NO_YOS_DELTA_OPT
10
TRCK
OFL_OPT_DELTA_DAYS_ARA­
3
OUND_NEW_YO
TRCK
DEFAULT_STRING
DEF
TRCK
BERTH_TDIST_MIN_STR
MIN
Next we explain each parameter.
MSGID provides the name of the message class that holds the messages related to the berth scheduling.
Typically, the provided value should be applied.
INBOUND_DATE_TIME_RECORD_TYPE identifies the date record type that is providing the arrival (ETA) of a
ship visit.
OUTBOUND_DATE_TIME_RECORD_TYPE identifies the date record type that is providing the departure (ETD)
of a ship visit.
ORDER_TYPE_BERTH_PLANNING identifies which yard documents are considered during berth scheduling.
Every yard request and every yard order has an order type.
DEFAULT_STRING identifies the character string designated to be used as default in all situations where such a
string is needed (see section Apply Cost Priorities and Default Values in Penalty Cost Matrix [page 120]).
Default value in case the parameter is not provided: DEF
122
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
BERTH_TDIST_MIN_STR identifies the character string designating the “minute” time unit of measurement
into which all values designating the minimum time distance between visits berthed at the same berth
positions will be converted in the preprocessing phase of the optimization algorithm.
OFL_COST_COEFFS_VB_FIXED_COST, the berth planning algorithm tries to minimize total effort in hours to
handle all planning objects. It can be the case that not all planning objects can be assigned to a berth position,
for example, because the harbor is full. In that case, the planning objects are assigned to a virtual berth
position (VB) according to some prioritization list. This of course, shall be the last option for the algorithm. To
achieve this, the cost of assigning a planning object to the virtual berth position must be higher than any cost of
a real berth position.
For a container terminal, the estimation can be done as follows: The highest expected number of containers to
be unloaded from a ship is x, the highest number of containers to load onto a ship is y. The max penalty cost for
loading 1 container is a, and for unloading it’s b. Therefore, the highest expected cost to berth a ship is a*x+b*y.
The sum over all three parameters OFL_COST_COEFFS_VB_FIXED_COST+
OFL_COST_COEFFS_VB_ORD_IDX_COEFF+ OFL_COST_COEFFS_VB_TIME_DIST_COEFF should be much
larger (one or two orders of magnitude larger, depending on the maximum number of visits that we expect to
plan for) than the largest expected berthing cost: a*x+b*y.
The total cost of placing a ship at the virtual berth is defined by:
OFL_COST_COEFFS_VB_FIXED_COST + TR_ORDER*OFL_COST_COEFFS_VB_ORD_IDX_COEFF +
TR_DIST_TO_MAX * OFL_COST_COEFFS_VB_TIME_DIST_COEFF
The parameter OFL_COST_COEFFS_VB_FIXED_COST defines a fixed cost of placing a ship at the virtual berth.
Default value in case the parameter is not provided=0.
For TR_ORDER*OFL_COST_COEFFS_VB_ORD_IDX_COEFF read below
OFL_COST_COEFFS_VB_ORD_IDX_COEFF. For TR_DIST_TO_MAX *
OFL_COST_COEFFS_VB_TIME_DIST_COEFF read below OFL_COST_COEFFS_VB_TIME_DIST_COEFF
OFL_COST_COEFFS_VB_ORD_IDX_COEFF, (Read information on OFL_COST_COEFFS_VB_FIXED_COST first.)
The total cost of placing a ship at the virtual berth is defined by the formula given above.
TR_ORDER: Ranking of planning object defined by prioritization criteria. The current prioritization criterion is
Arrival Time. The ship that arrives the latest would have rank = 1, making it the cheapest ship to be placed at
the virtual berth and so on.
Default value in case the parameter is not provided=10000.
OFL_COST_COEFFS_VB_TIME_DIST_COEFF, (Read information on OFL_COST_COEFFS_VB_FIXED_COST
first.) The total cost of placing a ship at the virtual berth is defined by the formula given above.
TR_DIST_TO_MAX: The ranking does not take into account the time difference between two registration times.
That means a planning object might be one rank higher than another planning object regardless of whether it
arrives just seconds or some days later than the preceding planning object. You can use this parameter in case
the arrival time difference between planning objects should be taken into account.
Default value in case the parameter is not provided=0.
OFL_RUNNING_TIME defines the runtime limit of the optimizer in seconds (this applies for each call to the
HANA OFL optimization engine, that is, for the optimization of each batch – see below for the definition of a
batch in this context).
Default value in case the parameter is not provided=3600
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
123
OFL_OPT_LARGE_BATCH_SIZE, number of planning objects that define one batch. Each batch is optimized
independently of other batches. This ensures linear runtime as number of planning objects increases. The
parameter OFL_RUNNING_TIME defines the max runtime in seconds for each batch. Set the
OFL_RUNNING_TIME to a value for which you are sure that a single batch can be planned in sufficient quality.
For example, we found that 100 ship visits can be planned to optimality in 60 to 70 seconds. Setting the
OFL_RUNNING_TIME to 100 seconds and the OFL_OPT_LARGE_BATCH_SIZE to 100 ensures a good planning
quality.
To estimate overall time for optimization: (NUMBER OF PLANNING OBJECTS /
OFL_OPT_LARGE_BATCH_SIZE) * OFL_RUNNING_TIME. you must allow some extra time for overhead
processes like the pre- and postprocessing of the data. Default value in case the parameter is not
provided=100.
OFL_MAX_NO_YOS_DELTA_OPT, the berth planner tries to use some techniques to reduce computation time
in case the number of planning objects is small. That makes sense in case there already is a berth plan with a
huge number of planning objects and only a small number of planning objects need planning (for example,
because they have been added or updated). In case the number of planning objects in a planning run with
status To be Planned is less than or equal to this parameter, these techniques are applied. Setting this value to
0 will enforce an optimization of the entire planning horizon.
OFL_OPT_DELTA_DAYS_ARAOUND_NEW_YO, (please see explanation for OFL_MAX_NO_YOS_DELTA_OPT
first.) This is used in case a planning object is added to an existing berth plan and the solver tries to do a delta
optimization. It will first try to directly assign the optimal berth position to this planning object. In case this is
not possible, perhaps because this position is already occupied, it will optimize a time frame around this
planning object. The time frame is defined by (ETA of planning object –
OFL_OPT_DELTA_DAYS_ARAOUND_NEW_YO, ETD of planning object +
OFL_OPT_DELTA_DAYS_ARAOUND_NEW_YO). Default value in case the parameter is not provided=3.
OFL_MERGE_TO_BE_PLANNED_YRS_INTO_EXISTING_PLAN can take values of 0 and 1. Using this parameter,
the delta optimization feature can be switched off (0) and on (1). The effect is the same as setting
OFL_MAX_NO_YOS_DELTA_OPT to 0. Default value in case the parameter is not provided=0.
124
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Configuring SAP Yard Logistics for SAP S/4HANA
7
Business Scenarios in SAP Yard Logistics
for SAP S/4 HANA
The solution addresses the following issues by providing transparency of the yards processes, simplifying the
truck, container, and rail yard management. The main objectives of the SAP Yard Logistics for SAP S/4HANA
solution are to:
● Increase visibility of all yard processes
● Improve efficiency for user roles, such as:
● Dispatchers
● Truck, train, and vessel drivers
● Internal and external workforce
● Security
● Provide planning, execution, and settlement functionality in one central system
● Integrate with existing business processes of the whole supply chain
Companies with yards need professional logistic processes to be able to withstand the competitive pressure in
the worldwide markets. The yards need to be supported by a highly integrated and easy-to-use system in a
complete supply chain. The SAP Yard Logistics solution provides check-in to check-out support for
transportation units and is focused on the functionalities of Planning, Execution, Yard Operations, Yard
Monitoring and Billing.
In the figure above, you see the major business process scenarios for SAP YL.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
INTERNAL – Authorized for SAP Customers and Partners
125
For Planning, the business process is based on two business documents: Yard Request and Yard Order. Yard
Requests are used as interfacing document to other systems and represent the time-based planning load for a
yard. Yard Orders are also planning documents but accepted by the Yard Coordinator and ready for execution.
The collection of Yard Orders represents the actual workload of a yard for a specific period.
The Yard Request/Order processing is split into an inbound process using inbound Yard Request/Yard Order
and outbound process using outbound Yard Request/Yard Order. Moreover, we support the internal yard
planning via an Internal Yard Order that needs only activation and completion, but no check-in nor check-out
will be needed.
For a Check-In process, an existing inbound Yard Order is needed. Use this process to authorize a driver
entering the yard facility by a check-in process step in SAP Yard Logistics where an inbound yard order is
checked-in. When you check-in an inbound yard order, you actually check-in the yard transportation units
associated with that yard order. We provide a simplified user interface of the yard order to execute this process.
For Execution, you need an already checked-in inbound Yard Order for the already arrived yard resources. This
process allows you to execute the movements or operations based on Yard Tasks for a yard asset.
To smoothly handle a complete end-to-end flow, a newly introduced Copy functionality has been implemented
to allow the copy from yard items arrived using an inbound yard order to an outbound yard order when they are
leaving the yard soon after their arrival.
For check-out process, an existing outbound Yard Order is required. All relevant Yard TUs must be pushed to an
outbound checkpoint to announce that they are physically ready to leave the yard. When you check-out an
outbound yard order, you actually check-out the transportation units associated with the yard order. You have a
simplified user interface of the yard order to execute this process.
Besides these inbound and outbound processes, SAP Yard Logistics supports Integration Scenarios (based on
a sample integration functionality) in combination either with SAP TM or with SAP TM and SAP EWM.
The following topics are important features of your solution:
● Transportation unit sequence:
The transportation unit sequence gives you transparency which transportation unit (TU) is located where
in the yard. You can see the TUs preceding and succeeding the current TU. You can also insert a TU by
specifying a predecessor or successor TU.
● Stackable storage bins:
In the solution the Yard TUs on stackable bins are managed in the same way as on non-stackable bins using
predecessor / successor TU references. A stackable bin can be managed sorted or unsorted. A yard task
for a stackable bin is a movement activity. Therefore, no TU hierarchy is created.
● Copy to inbound yard request/yard order (and vice versa):
You can copy an inbound yard request/yard order into a corresponding outbound yard request/yard order
and vice-versa.
● Switch to inbound yard request/yard order (and vice versa):
In the case of a linked inbound and outbound yard request/yard order exists, you can directly switch
between these two.
● Reverse check-in/check-out of yard order:
You can cancel all the actions executed during the check-in of an inbound yard order and check-out of an
outbound yard order.
● Yard Transportation Unit Assignment:
A Yard TU can be assigned to an inbound and an outbound yard order item for planning purposes
simultaneously.
126
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
● Yard TU Control Flag in a yard request/yard order:
In the current solution only one yard order has control over a Yard TU at any point in time (visualized by the
TU Control Flag), although a Yard TU can be assigned to an inbound and an outbound yard order items
simultaneously.
● External TU number for grouping items:
You can enter the TU Group External ID in the field TU number for an item to help you identify the ID for the
group.
● Upload and create Yard Transportation Units:
Now, you can upload TU data from *.csv file to create Yard TUs based on the data in the *.csv file on your
local system.
● Transportation Unit Empty indicator for an item:
You can determine whether a Yard TU is empty or not. The Yard TU is empty if this indicator is set.
● Record Measurements for movement activities:
In the current solution you can create a yard task with movement activity type that requires the task to
collect some measurements.
● In the yard documents, the business user can plan appointments integrated with SAP Dock Appointment
Scheduling.
● SAP Yard Logistics enables the printing of PDF-based yard documents based on the Adobe Document
Services.
● The integration to EH&S management has the following major features:
● EH&S Master Data integration to Yard Request and Yard Order
● Location Determination for Hazardous Substances
● Storage checks for Hazardous Substances
● Fire Department List reporting
● Historical content reporting for Transportation Units
● SAP Yard Logistics allows a nearly real-time recording of measurement data to yard TUs transferred from
smart devices linked to SAP HCP IoT services.
● A UI5/Fiori app is available for the self check-in of a yard order that typically run on automated gate checkin devices.
● Based on yard documents, an external driver communication via SMS, pager is available to communicate
target location information to drivers.
● The yard order and the yard TU document supports the classification, for example, allow the determination
of containers (represented by yard TUs) based on sophisticated properties of containers (specified via
class properties).
● The handling of yard documents is enabled via external applications using RFC-enabled business function
modules.
● The integration to SAP EWM allows multiple warehousing SAP EWMs connected to yard storage types
represented as warehouse visits.
Besides the major topics above we have also adapted and enhanced the solution in the SAP S/4HANA context.
See the next table with more details on it.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
INTERNAL – Authorized for SAP Customers and Partners
127
Function
Type of Change
Description
Internal YR/YO
New
In order to provide planning capabilities
for the internal yard processes an Inter­
nal YO was established with the follow­
ing functionality:
New direction “Internal” was added to
the YO
YO can be started by pressing button
activate, establishing TU control
YO can be completed using button
complete, releasing TU control
Check-in and check-out are not sup­
ported
YO may only handle TUs, which are al­
ready in the yard. This checked during
activation of the YT
Pager communication
New
New functionality implemented to es­
tablish communication with driver via
pager. New fields ‘Pager Service’ and
‘Pager Number’ were added to Yard Or­
der/Yard Request and Yard Task. Pager
data is stored in the driver’s business
partner master data.
Licensing
New
Licensing auditing can be performed
based on Inbound and Outbound Yard
Order items. It includes also a statistics
report for monitoring number of Yard
Order items.
Virtual Data Model for Yard Logistics
New
Virtual Data Model was created for SAP
Yard Logistics for SAP S/4HANA. This
includes CDS Basic Views which cover
SAP Yard Logistics transactional and
master data. These views can be used
for building fast data sheets and analyt­
ical SAP Fiori applications.
Fiori Catalog
New
The central entry point for SAP S/
4HANA applications is the SAP Fiori
Launch Pad. We provide a full set of
Fiori tiles from the SAP Yard Logistics
applications for the usage on a local
desktop or a tablet.
128
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
Function
Type of Change
Description
Yard Task Queue in Mobile App
Enhanced
We adjusted the functionality for the
queueing of yard tasks:: An empty
queue does not lead to initial applica­
tion screen.
UI harmonization
Enhanced
The user interface of SAP Yard Logistics
for SAP S/4HANA has been adapted to
the new Belize Theme which is the de­
fault theme for SAP S/4HANA. More­
over, the main menu functions have
been restricted based on the direction
of the yard order processing: in the pre­
vious release all menu functions have
been visible, in the new version only the
relevant ones based on the YO direction
are visible.
Yard Cockpit
Changed
Only schematic view is being supported
(no more map view)
Location Determination
Enhanced
A new logic for location determination
at activation YT was implemented.
Two new flags were introduced:
●
Destination Bin Determination at
YT creation
●
Destination Bin Determination at
YT activation
Both flags can be set independently. If
“Destination Bin Determination at YT
creation” is set, the location determina­
tion runs during YT creation as it was
before.
If “Destination Bin Determination at YT
activation” is set, the location determi­
nation runs during YT activation.
If the destination bin is already filled
and capacity check of destination bin
failed, it will be re-determined.
The following topics are relevant for SAP Yard Logistics for SAP S/4HANA;
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
INTERNAL – Authorized for SAP Customers and Partners
129
Topic
Description
Packaging Material creation
Since SAP S/4HANA combines together SCM and ERP prod­
uct master data, there is a new approach to Material Master
Data. In the SAP S/4HANA the product master can only be
created via transaction MM01. These products can be dis­
played in transactions /SAPAPO/MAT1 and /SCWM/MAT1.
These transactions are restricted and can be used only for
changes of specific fields related to EWM or APO
Packaging Material Type creation
In S/4HANA new rule for Packaging Material Type creation
shall be applied. To maintain proper assignment of Packag­
ing material to Means of Transport it is required to create
both EWM and ERP Packaging Material Types and they
should be defined with same name.
New navigational paths are:
EWM Packaging Material Type: SPRO -> Master Data -> Set­
tings for Transportation Units -> General Settings -> Define
Packaging Material Types.
ERP Packaging Material Type: SPRO -> Logistics-General>Handling Unit Management->Basics->Define Packaging
Material Type
EH&S in EWM
For S/4HANA the EH&S functions for handling of hazardous
substances and dangerous goods are part of PS&S (Product
Safety and Stewardship). Here are some of blacklisted trans­
actions and replacements for them:
Transaction
Transaction (no
(replacement in
longer available)
Description
SAP S/4HANA)
/SEHS/HMD
Edit Hazardous
HSMD
Substance Master
/SEHS/DGD01
Create Dangerous DGP1
Goods Master
/SEHS/DGD02
Change Danger­
DGP2
ous Goods Master
/SEHS/DGD03
Display Danger­
DGP3
ous Goods Master
130
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
7.1
Inbound Activity Management for Truck Yards
Overview
The scenario for inbound activity management for truck yards focuses on the end-to-end processing of truck
resources arriving in the yard and then processing different internal steps and activities depending on what has
been loaded onto the truck or on a connected trailer. Based on that, the processes are as follows:
● Managing Inbound Truck for Unloading
● Managing Inbound Truck with Trailer for Disposal of Trailer
● Managing Inbound Truck with Trailer for Cleaning and loading
● Managing Inbound Truck with Container
● Simple Appointment Planning for Unloading
As the inbound business scenario is not only restricted to means of transport, Truck, you can also execute the
processes for the means of transport Railcar. The solution supports the process of an inbound Train with
groups of railcars, deposit of this group in the yard, and the departure of the locomotive.
Technical System Landscape
Component
Mandatory
Optional
SAP Yard Logistics for SAP S/4HANA
X
-
SAP Yard Logistics for SAP S/4HANA –
X
-
UI
7.1.1 Managing Inbound Truck for Unloading
The simplest inbound business process is when an inbound truck arrives at the yard for unloading and
departure. The process steps are:
● Plan incoming truck – The yard coordinator does a planning of that incoming truck, which is supposed to
be unloaded in the yard and departs afterwards.
● Finalize planning and create inbound yard order – The yard coordinator finalizes the planning and creates
an inbound yard order as execution document.
● Check-in the inbound yard order – The truck arrives at the yard and the gate agent books check-in based
on this yard order.
● Unload truck – The truck drives to the unloading location and the yard operator unloads it.
● Complete the inbound yard order
● Create corresponding outbound yard order to move the truck out of the yard
● Activate the outbound yard order
● Start Processing of outbound yard order
● Start and confirm the yard task to move the truck to the checkout storage bin (while the containers have
not been moved)
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
INTERNAL – Authorized for SAP Customers and Partners
131
● Check-out yard order – The truck leaves the yard and the gate agent posts check-out.
7.1.2 Managing Inbound Truck with Trailer for Disposal of
Trailer
A more advanced inbound process is when an inbound truck with trailer arrives at the yard, a deposit of trailer
in yard is executed, and the truck departs. During execution of this process, the creation of an inbound yard
request locally in SAP Yard Logistics is executed. The yard request represents the planned workload for the
yard. The process steps are:
● Create inbound yard request with truck and trailer
● Create yard tasks to move truck and trailer from the inbound check point to a parking area – Create this
with reference to the yard request
● Release inbound yard request
● Check-in inbound yard order
● Execute Movement activity for the truck and trailer
● Complete the inbound yard order
● Create corresponding outbound yard order to move only the truck out of the yard
● Activate outbound yard order
● Start Processing of outbound yard order
● Start and confirm yard task to move the truck to the checkout storage bin
● Check-out outbound yard order to let the truck leave the yard
7.1.3 Managing Inbound Truck with Trailer for Cleaning and
Loading
Another typical, more advanced inbound process, can be defined as well - Arrival of an inbound truck with
trailer for cleaning, loading, and departure. The truck with a trailer enters the yard. The truck drives to the
cleaning area. The cleaning activity for the trailer takes place. After that, the truck drives to a loading station
and loads something. Then, the truck leaves the yard. The process steps are:
● Create inbound yard request with truck and trailer
● Create yard tasks - Do this with reference to the inbound yard request
● Release inbound yard request
● Check-in inbound yard order
● Execute Movement activity and cleaning activities
● Complete the inbound yard order
● Create corresponding outbound yard order to move only the truck out of the yard
● Activate outbound yard order
● Start Processing of outbound yard order
● Execute Movement activity for the truck
● Check-out outbound yard order
132
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
7.1.4 Managing Inbound Truck with Container
Another variation of this process is when an inbound truck with loaded container (loading scheme) for deposit
arrives at the yard. Then, the container measurements, like temperature, are recorded, and finally the truck
departs. The process steps are:
● Plan incoming truck – The truck carries two containers (loading scheme definition). The truck leaves the
container for deposit and departs from the yard. For both containers, the temperature should be recorded.
● Finalize planning and create execution document
● Check-in inbound yard order – Truck with container arrives at the yard and books check-in
● Leave containers – Truck drives to the location where containers should be left and unloads them there
● Record temperature data for both containers
● Complete inbound yard order
● Create corresponding outbound yard order to move the truck out of the yard
● Activate outbound yard order
● Start Processing of outbound yard order
● Start and confirm yard task to move the truck to the checkout storage bin (while the containers have not
been moved)
● Check-out outbound yard order to let the truck leave the yard
Technical System Landscape
Component
Mandatory
Optional
SAP Yard Logistics for SAP S/4HANA
X
-
SAP Yard Logistics for SAP S/4HANA –
X
-
UI
7.1.5 Planning Appointments for Unloading
With the linkage between SAP Yard Logistics and SAP Dock Appointment Scheduling (SAP DAS for short), the
planning of loading/unloading point capacity in a yard and the step-by-step integration with Dock Appointment
Scheduling documents, during the yard execution process, is driven by SAP Yard Logistics.
This process focuses on the Yard Logistics - Document Appointment Scheduling integration in a simple
Inbound Yard Request scenario (one single Inbound Yard Request, with a single Yard Request item that is
relevant for SAP DAS, a single yard task and one loading appointment generated for this item).
The following process steps must be executed:
1. Automatic creation of loading appointment when simple inbound scenario is activated
2. Automatic loading appointment assignment to a yard task in a simple scenario with only a single loading
appointment/item. You create a movement yard task. The loading appointment is automatically assigned
to this yard task.
3. Release the Yard Request: The loading appointment information is then copied automatically from Yard
Request to Yard Order
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
INTERNAL – Authorized for SAP Customers and Partners
133
4. Assign a free time slot to this loading appointment in SAP DAS that changes its status from "provisional" to
"planned".
5. Yard Order Check-In: The loading appointment gets status “Arrived at Checkpoint”.
6. Yard Task confirmation: For the movement to a door/ unloading activity: The appointment status changes
to “Arrived at Dock”.
7. Set "Departure from Dock".
8. Set Yard Order to "Complete": The loading appointment status is set to “Departed from Checkpoint”.
9. Finally, the yard order and the loading appointment are both completed successfully.
Technical System Landscape
Component
Mandatory
Optional
SAP Yard Logistics for SAP S/4HANA
X
-
SAP Yard Logistics for SAP S/4HANA -
X
-
X
-
UI
SAP DAS (on same system like SAP
Yard Logistics for SAP S/4HANA)
7.2
Outbound Activity Management for Truck Yards
The scenario for outbound activity management for truck yards focuses on the end-to-end processing of truck
resources arriving in the yard and then picking up or loading different resources, like trailer or containers, to be
transported out of the yard. The process variations come into play when a container is already requested for
transportation or a container that needs to be picked up is only identified by its properties or content. Based on
that, the processes are as follows:
● Managing Outbound Truck for Trailer Pick-up
● Managing Outbound Truck for Trailer Pick-up with Seal Numbers
● Managing Outbound Truck for Loading of Predefined Containers
● Managing Outbound Truck for Loading of Freely Selected Containers
● Managing Outbound Planning via Assignment UI
In addition, the outbound business scenario is not only restricted to trucks as means of transport;, the
processes can also be performed for the means of transport Railcar, for example, in a scenario of an outbound
train to pick up a group of railcars.
Technical System Landscape
Component
Mandatory
Optional
SAP Yard Logistics for SAP S/4HANA
X
-
134
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
Component
Mandatory
Optional
SAP Yard Logistics for SAP S/4HANA -
X
-
UI
7.2.1 Managing Outbound Truck for Trailer Pick-up
The simplest outbound process is the following: An (outbound) truck enters the yard and picks up a trailer.
Then, the truck with trailer leaves the yard. The process steps are:
● Create outbound yard request, that is, planning outbound activities first: truck and concrete trailer which
drive to loading facility and depart together after loading.
● Release outbound yard request.
● Create corresponding inbound yard order (maintaining the incoming truck only).
● Check-in inbound yard order.
● Execute Movement activity, that is, the truck drives to location where trailer is located.
● Complete inbound yard order.
● Activate outbound yard order.
● Start Processing of outbound yard order.
● Truck and trailer drive to locations where loading is executed.
● Execute yard tasks, that is, the truck and the trailer are moved to outbound checkpoint.
● Check-out outbound yard order.
7.2.2 Managing Outbound Truck for Trailer Pick-up with Seal
Numbers
A slight variation of the outbound process is augmented by having seals: An (outbound) truck enters the yard
for loading of an (existing) trailer and departs the yard. The process also includes seal number handling. This
process assumes that a trailer is already located in the yard. The next step is the planning of an incoming truck,
which is supposed to pick up this concrete trailer, drive to the loading facility, load the trailer attached with a
seal number, and both depart together after loading. The process steps are:
● Finalize outbound planning and create outbound execution document with truck and trailer
● Create corresponding inbound yard order (maintaining the incoming truck only)
● Check-in inbound yard order - Truck arrives at the yard
● Complete inbound yard order
● Activate outbound yard order
● Start Processing of outbound yard order
● Pick-up trailer - Drive truck to the location where the trailer is located
● Load trailer - Truck and trailer drive to locations where loading is executed. Two seal numbers are attached
to the trailer.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
INTERNAL – Authorized for SAP Customers and Partners
135
● Check-out outbound yard order - Truck and trailer leave the yard
7.2.3 Managing Outbound Truck for Loading of Predefined
Containers
A more advanced business process that is supported is an (outbound) truck has to pick up multiple containers
(loading scheme) where the container numbers are predefined and are used for departure. This assumes that
the containers are already located in the yard. The process steps are:
● Plan outgoing truck with defined loading scheme - The truck is supposed to load two concrete containers
already located in the yard. First, outbound is planned followed by the inbound planning of the truck.
● Finalize planning and create outbound execution document
● Create corresponding inbound yard order (maintaining the incoming truck only)
● Check-in inbound yard order - Truck arrives at yard, books check-in
● Execute planned yard tasks - Truck drives to the location where containers are located
● Complete inbound yard order
● Activate outbound yard order
● Start Processing of outbound yard order
● Load containers - Truck drives to the location where containers are located and loads them there by
starting and confirming the first two (loading) yard tasks
● Start the third planned yard task to move all items to the outbound checkpoint storage bin
● Check-out outbound yard order - Truck with containers leaves the yard
7.2.4 Managing Outbound Truck for Loading of Freely
Selected Containers
The process described in the section above is also possible with the variation that the container numbers are
not yet predefined, but the yard coordinator can assign them. Then the first process step looks different. The
process steps are:
● Plan outgoing truck with defined loading scheme - The truck is supposed to load two containers already
located in the yard, which are not yet concretely identified (only size is known), and departs together.
● Finalize planning and create outbound execution document.
● Create inbound yard order (maintaining the incoming truck only).
● Check-in inbound yard order - Truck arrives at yard, books check-in.
● Concrete containers to be loaded are known in the meanwhile.
● Maintain TU numbers in outbound yard order via the Yard Order user interface.
● Execute planned yard tasks - Truck drives to the location where containers are located and loads them
there by starting and confirming the first two (loading) yard tasks.
● Complete inbound yard order.
● Activate outbound yard order.
● Start Processing of outbound yard order.
136
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
● Start the third planned yard task to move all items to the outbound checkpoint storage bin.
● Check-out outbound yard order - Truck with containers leaves the yard.
7.2.5 Managing Outbound Planning via Pick-up Planning UI
The assignment UI allows the reserving TUs located in the yard to outbound yard orders.
The truck enters the yard, loads a trailer standing in the yard and leaves the yard. The focus for this process
step is to reserve TUs for the outbound yard orders.
Another usage focuses on adding a new item to a yard order and reserve a TU for it. Both steps are executed on
the assignment UI, which means that the item to be loaded is not maintained beforehand in the yard order item
hierarchy.
7.2.6 Validating Thresholds (Including Measurement
Recording)
In a Yard Order item, the business user can store threshold values on the specific tab Thresholds. These
thresholds can stand for specific measures like temperature and they are represented for specific TU record
types. Each threshold is also defined with an upper and a lower limit. If a threshold is out of this limit's interval,
then a specific threshold-based alert can be triggered, which is visible in the Alert Monitor. The recording of the
thresholds is linked to a yard task that allows recording the threshold values. In addition to that, the IoT process
of receiving thresholds directly for Yard TUs is also possible.
7.3
Internal Activity Management for Truck Yards
The scenario for internal activity management for truck yards is key to manage the limited resources within the
yard in an optimized way. In this scenario, the business user is focusing on the execution of the yard
movements via yard tasks and monitoring the operations of the yard from an E2E view in the yard cockpit (in a
graphical representation supporting the overall operation status of the yard).
The internal scenario is rounded up by a special process where containers are re-arranged within a yard by
stacking or unstacking containers on each other.
Based on these internal activities, the process steps are:
● Executing Yard Tasks
● Managing Yard Operations Using Mobile UI
● Monitoring Yard Activities via Yard Cockpit
● Managing Stacking and Unstacking of Containers
Technical System Landscape
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
INTERNAL – Authorized for SAP Customers and Partners
137
Component
Mandatory
Optional
SAP Yard Logistics for SAP S/4HANA
X
-
SAP Yard Logistics for SAP S/4HANA -
X
-
UI
For the process, Managing Yard Operations Using Mobile UI, the system landscape requires the software
component SAP Yard Logistics for SAP S/4HANA - UI.
7.3.1 Executing Yard Tasks
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. Yard tasks are the key entities for planning and execution within a yard.
Such a yard task is mapped to a warehouse task in the underlying EWM warehouse assigned to the yard
number.
If a yard task cannot be executed, then the business user can enter an exception in that yard task. An exception
may be an unexpected situation that may happen in the yard when executing yard tasks. For example, the
business user receives a task to move a container from one bin to another. When approaching the container,
the business user sees that the container is broken. Then, he could raise an exception instead of confirming the
yard task. For an exception, the business user can assign an alert type. This can be used to trigger an alert that
can be checked by a user using the alert monitor. In addition to an alert, the exception can also be used to
trigger follow-on activities:
● Block Source Location ¬- The system blocks the source storage bin and you cannot execute any further
activity on that storage bin.
● Block Destination Location - The system blocks the destination storage bin and you cannot execute any
further activity on that storage bin.
● Block Transportation Unit - You cannot execute any further action on the transportation unit.
Technical System Landscape
Component
Mandatory
Optional
SAP Yard Logistics for SAP S/4HANA
X
-
SAP Yard Logistics for SAP S/4HANA -
X
-
UI
SAP Visual Business 2.1
138
{X}
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
7.3.2 Executing Yard Tasks with Explicit Reference to an
Internal Yard Order
You use this business process to plan and execute yard activities to manage transportation units within the
yard with explicit reference to a yard order. You can work with activities that model all kinds of services on the
yard like unloading, moving a Yard Transportation Unit (YTU) to a storage place, cleaning a YTU, repairing a YTU
● The business process runs in SAP Yard Logistics as follows:
● Create an Internal Yard Order
○ You create a yard order with a truck.
○ You create a yard task e.g. to clean the truck on the current location.
● Activate the Internal Yard Order
● Activate, start and confirm the yard task which is related to your Internal Yard Order.
● Complete the Internal Yard Order
Technical System Landscape
Component
Mandatory
Optional
SAP Yard Logistics for SAP S/4HANA
X
-
SAP Yard Logistics for SAP S/4HANA -
X
-
UI
SAP Visual Business 2.1
{X}
7.3.3 Managing Yard Operations Using Mobile UI
The mobile UI is based on the newest user interface technology from SAP based on SAP Fiori. This user
interface can be executed on any device – mobile or a desktop – using the Fiori Client application (a mobile app
that can be downloaded in the respective app stores). The system assigns the yard tasks for mobile execution
to a queue.
The business user is assigned to one or multiple queues to fetch yard tasks for execution. This guarantees that
the user can work on only one yard task at a time. The application supports two modes: Queue mode or Manual
Selection mode. In Queue mode, the system loads the yard tasks from the queue that a business user is
assigned to and the user gets the next task in the queue automatically. In Manual Selection mode, the
application displays all the tasks with status as Active or In Process for the yard and handling resource that a
business user has selected at entry. The business user can choose a yard task or search for yard tasks that
he/she wants to execute
Technical System Landscape
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
INTERNAL – Authorized for SAP Customers and Partners
139
Component
Mandatory
Optional
SAP Yard Logistics for SAP S/4HANA
X
-
SAP Yard Logistics for SAP S/4HANA -
X
-
UI
SAP Visual Business 2.1
{X}
7.3.4 Monitoring Yard Activities Using the Yard Cockpit
The Yard Cockpit contains several overview lists displaying yard tasks, yard orders, alerts etc. such as the
Visual Yard, which contains the graphical representation of the yard. Under the Orders section, you can search
for the 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 the Alerts section, you can search for the alerts.
In the Resources section, you can search for the handling resources. The system displays the handling
resources assigned to this yard as per your search criteria.
In the Transportation Unit section, you can search for the TUs.
From 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.
Technical System Landscape
Component
Mandatory
Optional
SAP Yard Logistics for SAP S/4HANA
X
-
SAP Yard Logistics for SAP S/4HANA -
X
-
UI
SAP Visual Business 2.1
{X}
 Note
Refer SAP Note 2239939 Collada-Objects for Yard Cockpit Visualization
monitoring using yard cockpit.
140
INTERNAL – Authorized for SAP Customers and Partners
for more information about
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
7.3.5 Managing Stacking and Unstacking of Containers
The business process focuses on stacking containers on a storage bin. We can put and remove a container
from each position of the stack.
A stackable bin stores TUs strictly as a stack. Only one TU (without a hierarchy) can be placed at a stack level
with one YT. TU's on stackable bins will be managed as on non-stackable bins using predecessor and successor
TU references. On a stackable bin, predecessor means subjacent TU and successor means overlying TU. A
stackable bin is sorted automatically by a given sequence. A put-away into a stackable bin is movement and not
a loading activity. Therefore, no TU hierarchy will be created or updated.
7.3.6 Determining Dangerous Goods Location
In this process, specific yard areas represented as storage types are permitted for specific hazard ratings.
In addition, in Customizing, you can define the hazard ratings of a product that should be checked during
maximal quantity check at location determination of a yard task for such a dangerous goods relevant storage
type.
7.3.7 Classification of Yard TUs
In this solution, 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, we introduced two new class types: one for
classifying yard TUs and one for yard order/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, we offer a new
button TU Determination that searches for a list of available yard TUs fulfilling these classification properties of
the yard order's item, based on each yard TU's classification data.
7.4
Internet of Things for Yard Logistics for SAP S/4HANA
The Internet of Things (IoT) features are a ubiquitous part of today's processes in running a successful supply
chain. Especially, concerning those assets that are needed to operate a yard, as the assets in the yard are, more
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
INTERNAL – Authorized for SAP Customers and Partners
141
often than not, already equipped with smart devices. Frequent examples of IoT capable assets are containers
that send its temperature to control it being in a certain allowed temperature range, or the yard gate entry
facility that allows an automated barrier opens at the gate for an already recognized truck to enter the yard.
The truck has already been recognized by an OCR based scanning of its license plate and by that the
corresponding yard order for check-in has been determined as well.
The functionality for retrieving temperature from a smart container into the container's yard TU is available for
use since release 2009 of the solution.
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 SAP Cloud Platform. Internet of Things (IoT) Service.
Once the data is updated to the SAP BTP, SAP Yard Logistics for SAP S/4HANA can access that data and
record it into the container’s representation of a yard TU on the Measurements tab.
The current release introduces Geofencing as a new IoT process within SAP Yard Logistics. This process
enables the use of GPS sensor data to achieve automatic updates of a yard order and its related yard tasks
based on entry or exit events recorded for a Geofence defined within a yard.
 Caution
The Geofencing scenario imposes special security and data protection requirements, which the customer
must take into account while setting up and running the Geofencing process in a legally compliant manner
on both system sides. For more information, see section Security for Internet of Things Geofencing [page
163].
No coding for is required for using the SAP BTP, Internet of Things Service. You do need to execute the setup
steps for creating and configuring sensors, devices, things, and actions and so on. For more information refer
links provided below.
Technical prerequisites for using the SAP BTP, Internet of Things Service are:
● SAP Yard Logistics for SAP S/4HANA
● SAP Yard Logistics for SAP S/4HANA – UI
● SAP IoT services for SAP BTP for Neo environment (if you are using the IoT Service based on the SAP BTP,
Neo Environment)
Or
● SAP IoT services for SAP BTP for the Cloud Foundry environment (if you are using the IoT Service based on
the SAP BTP, Cloud Foundry Environment)
Or
● SAP Internet of Things (IoT)
 Note
The Geofencing scenario is only compatible with SAP Internet of Thing (IoT) and therefore is not usable
together with SAP IoT Services for SAP BTP for Neo environment or SAP IoT Services for SAP BTP for
Cloud Foundry environment.
142
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Business Scenarios in SAP Yard Logistics for SAP S/4 HANA
8
Security Information for SAP Yard
Logistics for SAP S/4HANA
This section deals with security topics relevant for SAP Yard Logistics for SAP S/4HANA.
8.1
Other Required Documents for Security
This section provides an overview of other security-related documents.
SAP Yard Logistics for SAP S/4HANA is based on the SAP Extended Warehouse Management component of
SAP S/4HANA 2020. This means that the corresponding security guides also apply to this solution.
Resource
Where to Find It
Security Guide for SAP S/4HANA 2020
https://help.sap.com/viewer/product/SAP_S4HANA_ONPREMISE/2020/en-US?task=implement_task
8.2
User Management
This section provides an overview of how you manage and authenticate users in SAP Yard Logistics for SAP S/
4HANA.
SAP Yard Logistics for SAP S/4HANA uses the user management and authentication mechanisms provided for
SAP Netweaver 752. The security recommendations and guidelines for user administration and authentication
as described in the security guide for SAP Netweaver 752 at https://help.sap.com/viewer/p/
SAP_NETWEAVER_AS_ABAP_752 also apply to this solution.
8.2.1 User Types
This section describes the types of users relevant for SAP Yard Logistics for SAP S/4HANA.
User Type
Description
Dialog
Individual, interactive system access
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
143
User Type
Description
System
Background processing and communication within a sys­
tem, such as RFC users for ALE, Workflow, TMS, and CUA
Communication
Dialog-free communication for external RFC calls
Service
Dialog user available to a larger, anonymous group of users
Reference
General, non-person related users that allows the assign­
ment of additional identical authorizations for example, in­
ternet users created with transaction SU01. No logon is pos­
sible here.
 Note
The user in the logical port cannot be a system user, but for logging in to a remote host, it is necessary to
retrieve the WSDL file and execute the ICF SOAP service. For more details refer SAP Note 2347013
.
8.2.2 User Administration Tools
This section lists the tools available for user management and administration for SAP Yard Logistics for SAP S/
4HANA.
Tool
Description
User and role maintenance with SAP NetWeaver AS ABAP
For more information, see topic User and Role Administration
(Transactions SU01, PFCG)
of Application Server ABAP in the documentation for SAP
NetWeaver 7.5 on the Help Portal at https://help.sap.com/
viewer/c6e6d078ab99452db94ed7b3b7bbcccf/7.5.12/enUS.
For details on the user management and authorization concepts used in SAP Fiori apps, see the SAP S/4HANA
UI Technology Guide on the SAP Help Portal under http://help.sap.com/s4hana_op_1709.
8.2.3 User Data Synchronization
This section describes how to synchronize user data in SAP Yard Logistics for SAP S/4HANA.
By synchronizing user data, you can reduce effort and expense in the user management of your system
landscape. Since SAP S/4HANA is based on SAP NetWeaver, you can use all of the mechanisms for user
synchronization in SAP NetWeaver here. For more information, see the SAP NetWeaver Security Guide on the
SAP Help portal under https://help.sap.com/nw75.
144
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
8.2.4 Authentication and Single Sign-On
This section describes how authentication and single sign-on for users are implemented in SAP Yard Logistics
for SAP S/4HANA.
This solution supports the Single Sign-On (SSO) mechanisms provided by SAP NetWeaver. Therefore, the
security recommendations and guidelines for user administration and authentication as described in the SAP
NetWeaver Security Guide apply. for more information, see https://help.sap.com/viewer/p/
SAP_NETWEAVER_AS_ABAP_752.
8.3
Role and Authorization Concept
This section describes the roles and authorizations available in SAP Yard Logistics for SAP S/4HANA.
This solution uses the authorization concept provided by the SAP NetWeaver AS ABAP or AS Java. Therefore,
the recommendations and guidelines for authorizations as described in the SAP NetWeaver AS Security Guide
also apply.
The SAP NetWeaver authorization concept is based on assigning authorizations to users based on roles. For
role maintenance, use the profile generator (transaction PFCG) on the AS ABAP.
 Note
For more information about how to create roles, see the role administration information in the SAP S/
4HANA security guide.
8.3.1 Authorization Objects
The section lists the security-relevant authorization objects that are used by SAP Yard Logistics for SAP S/
4HANA.
The section lists the security-relevant authorization objects that are used by SAP Yard Logistics for SAP S/
4HANA.
● /SAPYL/YC (Authorization Object for Yard Cockpit)
This authorization object is used to regulate access to the Yard Cockpit application.
Field
Description
Yard Number
Yard Number(s) the user can access – As defined in the Cus­
tomizing (transaction SPRO) for SAP Yard Logistics under
Master Data
Setting up the Yard
Define Yard
Numbers
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
145
Field
Description
Activity
Activities that the user is allowed to execute
Possible values are:
BO service name for authorization checks
●
01 Create
●
02 Change
●
03 Display
●
06 Delete
●
39 Check (not used)
Service Name for BOPF authorization checks – This field is
currently not checked for this authorization object

Note
Activities 16 and AF cannot be used)
● /SAPYL/YO (Authorization Object Yard Order)
This authorization object is used to regulate access to the Yard Order / Yard Request applications and
objects.
Field
Description
Yard Document Category
Category of the document – Value can be YO (Yard Order),
YR (Yard Request) or YT (Yard Task).
Yard Number
Yard Number(s) that the user can access – As defined in the
Customizing (transaction SPRO) for SAP Yard Logistics un­
der
Master Data
Setting up the Yard
Define Yard
Numbers
Yard Order Type
Yard Order Types of the Yard Numbers defined above that
the user can access – As defined in the Customizing (trans­
action SPRO) for SAP Yard Logistics under
and Yard Order
146
INTERNAL – Authorized for SAP Customers and Partners
Define Order Types
Yard Request
.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
Field
Description
Activity
Activities that the user is allowed to execute
Possible values are:
●
01 Create or Generate
●
02 Change
●
03 Display
●
06 Delete
●
16 Execute (execute Actions defined in field BO service
name for authorizations)
●
39 Check (not used)
●
AF Prompts (execute Queries defined in field BO service
name for authorizations)
BO service name for authorization checks
Service Name for BOPF authorization checks. Possible val­
ues for Actions and Queries in the /SAPYL/-namespace can
be seen via F4-help.
It is recommended to use an asterisk for this field to allow
appropriate operation on the business object Yard Order.
● /SAPYL/YT (Authorization Object for Yard Task)
This authorization object is used to regulate access to Yard Task related applications and objects.
Field
Yard Number
Description
Yard Number(s) that the user can access – As defined in the
Customizing (transaction SPRO) for SAP Yard Logistics un­
der
Master Data
Setting up the Yard
Define Yard
Numbers
Activity Type
Activity Type(s) the user can access – As defined in Custom­
izing (transaction SPRO) for SAP Yard Logistics under
Tasks
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
Yard
Define Activity Types
INTERNAL – Authorized for SAP Customers and Partners
147
Field
Description
Activity
Activities the user is allowed to execute
Possible values are:
●
01 Create
●
02 Change
●
03 Display
●
06 Delete
●
16 Execute (execute Actions defined in field BO service
name for authorizations)
●
39 Check (not used)
●
AF Prompts (execute Queries defined in field BO service
name for authorizations)
BO service name for authorization checks
Service Name for BOPF authorization checks
Possible values for Actions and Queries in the /SAPYL/namespace can be seen via F4-help.
 Note
Changes on Yard Tasks (for example, Confirmation of the YT) may require follow-on updates on the
corresponding Yard Order and, therefore, the user also needs authorization for updating Yard Orders.
● /SAPYL/YTU (Authorization Object Yard Transportation Unit)
This authorization object is used to regulate access to Yard applications, which focusses on Transportation
Units (Display Transportation Unit / Transportation Unit Overview).
Field
Description
Yard Number
Yard Number(s) the user can access – As defined in the Cus­
tomizing (transaction SPRO) for SAP Yard Logistics under
Master Data
Setting up the Yard
Define Yard
Numbers
Activity
Activities that the user is allowed to execute
Possible values are:
148
INTERNAL – Authorized for SAP Customers and Partners
●
01 Create
●
02 Change
●
03 Display
●
06 Delete
●
39 Check (not used)
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
Field
Description
BO service name for authorization checks
Service Name for BOPF authorization checks – This field is
currently not checked for this authorization object.

Note
Activities 16 and AF cannot be used)
● S_START (Start Authorization Check for TADIR Objects)
To access a Web screen (like a direct URL to a Web Dynpro Application or to an HTML UI), a user can either
log on using the URL of the Web screen in the internet browser directly or can call up the transaction for the
Web screen from the SAP NetWeaver Business Client. To access the Web screen, a user needs appropriate
authorizations.
The S_START authorization object determines if a user can start a Web screen by checking if the user has
the authorization to directly access the Web Dynpro application that lies beneath a Web screen. A Web
Dynpro application is the framework that forms the basis of a Web screen. By checking the Web Dynpro
application, you ensure that only those users who have the right authorization can access the Web screen.
By default, the S_START authorization object is inactive. For more information, see Authorization Checks
underhttps://help.sap.com/saphelp_apo700_ehp03_on_erp/helpdata/en/4c/
a0ac7a68243b9ee10000000a42189b/frameset.htmand Security Considerations for Web Dynpro
Applications under http://help.sap.com/saphelp_nw74/helpdata/en/
48/69eb40e8a607d6e10000000a42189c/frameset.htm.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
149
Field
Description
Object Name
Object name of the Yard Logistics Web Dynpro application.
You can see the possible values in the /SAPYL/-namespace
via F4-help.
Possible values for Object Names available are:
●
/SAPYL/WD_COCKPIT_NEW – Yard Cockpit Application
●
/SAPYL/WD_COLOR_PICKER – VBI Color Picker
●
/SAPYL/WD_YARD_EDITOR – Yard Layout Editor
●
/SAPYL/WD_YO – Yard Order
●
/SAPYL/WD_YO_CICO – Yard Order Check-In(Out)
●
/SAPYL/WD_YO_POWL – Yard Order Overview List
●
/SAPYL/WD_YO_TU – Assignment Transport to Yard Or­
der
●
/SAPYL/WD_YR – Yard request Detail
●
/SAPYL/WD_YR_POWL – Yard Request Overview List
●
/SAPYL/WD_YT – FPM Application for Yard Task
●
/SAPYL/WD_YT_POWL – Yard Task Overview List
●
/SAPYL/WD_YTU – Yard Transportation Unit
●
/SAPYL/WDCA_YARD_TU – Overview Transportation
Unit
●
/SAPYL/WDCA_YARD_TU_FD – Fire Department List
●
/SAPYL/WDCA_DAS – Loading Appointment List
Ensure that all entries are put together as a list into the field
Object Name of the authority profile above.
Object Type
WDYA – This is a fixed value to focus only on Web Dynpro Ap­
plications.
Program ID
R3TR – This is a fixed value due to technical reasons.
● /SAPYL/SLF (Authorization Check for Special Functions)
This authorization object is re-used in reports of in this solution, used for performing special functions, like
uploading Yard TU data, migration, and so on.
Field
Description
Yard Number
Yard Number(s) the user can access – As defined in Cus­
tomizing (transaction SPRO) for SAP Yard Logistics under
Master Data
Setting up the Yard
Define Yard
Numbers
150
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
Field
Description
Special Functions
Special function that will be performed:
●
BC Bin Change: the business user is allowed to change
the destination bin in a Yard Task
●
BC Copy the Coordinates for bins displayed in Visual
Business Visualization (transaction /SAPYL/
COPY_BIN_COOR Copy VisBis Storage Bin Coordi­
nates)
●
BC Load storage bins (transaction /SAPYL/
YARD_UPLOAD Create Yard Layout from CSV file)
●
B1 /SAPYL/YO_DRIVER_BP Migration for Driver to
BusPartner
●
B1 /SAPYL/YO_DRIV_BP Migration for Driver to Bus­
Partner
●
C1 Create and Upload Yard TUs (transaction /SAPYL/
CREATE_TU_CSV)
●
C1 Check-out Yard TUs (transaction /SAPYL/
CHECK_OUT_TU)
●
C1 Migrate YO Node Category (transaction /SAPYL/
YO_NODE_CAT_MIGRATION)
●
C1 Change the layout of a yard for the Visual Business
Visualization (transaction /SAPYL/CHANGE_LAYOUT
Copy Coordinates/Change Dimensions)
●
C1 /SAPYL/VBI_RNDR_MODE Visual Business Ren­
der Mode
●
AR Door Arrival (web service for FM /SAPYL/
WS_DOOR_ARR_DEP)
●
DP Door Departure (web service for FM /SAPYL/
WS_DOOR_ARR_DEP)
●
NF Loading/Unloading Notification (web service for
FM /SAPYL/WS_QUERY_EXTERNAL_TU)
●
NF Import a Function Module for Versioning (web serv­
ice for FM /SAPYL/WS_LOAD_UNLOAD_NOTIF_PR)
●
Q1 Query TU from external Subsystem (web service for
FM /SAPYL/WS_QUERY_EXT_TU)
●
I1 IOT: Pull data from the Cloud (transaction /SAPYL/
IOT_PULL_DATA and /SAPYL/IOT_DATPUL_CF
Pull Data from IoT Cloud (CF))
●
I2 IOT: Send Message (transaction /SAPYL/
IOT_SEND_MSG)
●
LA License Auditing Statistics display (report /SAPYL/
R_LICENCE_ANALYSIS)
●
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
T3 Clean-up Yard (report /SAPYL/CLEAN_UP_YARD)
INTERNAL – Authorized for SAP Customers and Partners
151
Field
Description
●
T3 Determine and Delete TU without SR Activity (trans­
action /SAPYL/DETERM_TU_NO_SR_ACT)
The SAP YL solution uses overview lists for yard orders, yard requests, yard tasks, and yard transportation
units. For these lists, a specific SAP UI Technology have been used – SAP Power Object Lists (POWLs for
short). In the following sections, you will find the relevant information to setup an appropriate authorization
concept for these POWLs.
Transaction POWL_TYPER
This transaction is used for maintaining POWL Type role assignment. Use this transaction to provide POWL
with the feeder types that are available for APPLID. The feeder types available are Role or both.
● For more information, see Customizing POWL under http://help.sap.de/saphelp_crm700_ehp02/
helpdata/en/3d/a958ca376743dba8cf40829a1851de/content.htm?frameset=/en/90/
ae5ab9f47248198663fd6ae2186e31/frameset.htm&current_toc=/en/52/
c3c433bb9c4328b49b70e663271f62/plain.htm&node_id=357 .
POWL lists are used within the SAP Yard Logistics applications Yard Request Overview, Yard Order Over, Yard
Task Overview and Transportation Unit Overview.
The transaction can be used to assign SAP Yard Logistics user roles to SAP Yard Logistics POWL application
IDs.
Only users who have a role assignment maintained here, are allowed to see the corresponding POWL query
lists.
The following table shows the available POWL Types/APPLIDs for SAP Yard Logistics:
Application
POWL Type ID
Description
/SAPYL/YR_APPID
/SAPYL/YR_TYPE
POWL for Yard Requests
/SAPYL/YO_APPID
/SAPYL/YO_TYPE
POWL for Yard Orders
/SAPYL/YT_APPID
/SAPYL/YT_TYPE
POWL for Yard Tasks
/SAPYL/TU_APPID
/SAPYL/TU_TYPE
POWL for Yard Transportation Units
8.3.2 Standard Roles
This section describes the standard roles used by SAP Yard Logistics for SAP S/4HANA.
Sample Business Roles
The solution provides four sample roles predefined with authorizations needed for specific yard-related
business roles. Each role provides a work center menu and authorizations needed to operate with the
applications within the menu.
152
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
As mentioned above, these roles can only be seen as templates and should be copied to the customer
namespace and modified for the individual business needs.
The following template roles are available:
● /SAPYL/SUPERVISOR
The role contains all authorizations and menu links to access any SAP Yard Logistics application.
● /SAPYL/COORDINATOR
The role contains the same authorizations and menu links as the Supervisor except the menu nodes
Master Data and Settings.
● /SAPYL/OPERATOR
This role contains authorizations and menu links for a Yard Operator executing tasks within a yard.
The operator is only allowed to use applications from the menu nodes Yard Execution, Yard Monitoring and
Yard Operations. Therefore, a user who has this role assigned can create, display and edit Yard Tasks, can
get information about specific Transportation Units and enter the Yard Cockpit.
Additionally, the menu contains a link to the SAP Fiori Launchpad to enable the user to execute Yard Tasks
via a mobile UI on a mobile client.
Note: Authorizations needed to work with the mobile UI are contained in separate technical roles (see the
next paragraph).
● /SAPYL/GATE_AGENT
This role contains authorizations and menu links for a Gate Agent checking-in and checking-out yard
orders. Users who have this role assigned are able to display and edit Yard Orders, display Yard Tasks. They
are also allowed to use the overview lists for both kinds of business documents and to launch the Yard
Cockpit.
● /SAPYLUI/SAP_BR_YARD_MANAGER (Fiori-based Role)
This role contains all tiles for managing a yard efficiently without restrictions to specific tiles. It is similar
like the role /SAPYL/SUPERVISOR but must be used in the Fiori context as it contains all relevant SAP Fiori
tile groups and SAP Fiori tile catalogs.
● /SAPYLUI/SAP_BR_YARD_OPERATOR (Fiori-based Role)
This role contains all tiles for yard operations. It is similar like the role /SAPYL/OPERATOR but must be
used in the Fiori context as it contains all relevant SAP Fiori tile groups and SAP Fiori tile catalogs.
Additional Roles for the Mobile UI
For the usage of the mobile client/mobile UI the following roles need to be assigned to a user.
● /SAPYLUI/TCR_T
This technical role is used to provide catalog content for the Fiori Launchpad.
● /SAPYLUI/BCR_YARDOPERATOR_T
This technical role is used to provide the Fiori Launchpad tiles for the Yard Operator using the mobile UI.
● /SAPYLUI/BCR_GATE_AGENT_T
This technical role is used to provide the Fiori Launchpad tiles for the Self Check-In application.
● /SAPYL/YTASK_APP
This is the backend role for the Fiori Launchpad application ‘Yard Task Confirmation’. It provides access to
the SAP Gateway service for executing the business logic in the backend application of SAP YL.
● /SAPYL/SELFCHECKIN_APP
This is the backend role for the Fiori Launchpad application Self Check-In. It provides access to the SAP
Gateway service for executing the business logic in the backend application of SAP YL.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
153
 Caution
In the application for self-check in a supplier (truck driver) can register as another supplier. As there is no
authentication mechanism in place, every user of the terminal can use to enter a known number and can
see in the second screen the container number if already planned in the document. The attacker needs a
correct document number and correct item details in order to see yard document details. Besides the
security measures provided by the SAP solution, you will also need additional (even physical) security
measures to secure your yard facilities.
 Caution
In the application for self-check in the supplier (truck driver) could potentially change the yard order or yard
order item data by tampering if the truck driver’s access to the SAP YL solution is equipped with too many
system authorities. You as a system administrator are responsible to setup the self-check-in role with only
minimal authorizations to mitigate this risk.
8.4
Network and Communication Security
This section provides an overview of the network topology and communication protocols used by SAP Yard
Logistics for SAP S/4HANA.
The network topology for this solution is based on the topology used by the SAP Netweaver ABAP 752. The
security guidelines and recommendations described in the security guide for the SAP NetWeaver ABAP also
apply for this solution.
8.5
Internet Communication Framework Security
This section describes how SAP Yard Logistics for SAP S/4HANA uses Internet Communication Framework
(ICF) services.
For information on the services that need to be activated for SAP Yard Logistics for SAP S/4HANA, refer
2534295 - SICF nodes for SAP Yard Logistics to activate
If your firewall(s) use URL filtering, also note the URLs used for the services and adjust your firewall settings
accordingly.
For more information, see the available user assistance for SAP NetWeaver. To find the relevant documents, go
to SAP Help Portal at http://help.sap.com/nw and open the product page for your SAP NetWeaver release.
Search for activating and deactivating ICF services and ICF security.
154
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
8.6
Data Protection and Privacy
This section provides information about how SAP Yard Logistics for SAP S/4HANA complies with data
protection requirements.
8.6.1 Introduction
Data protection is associated with numerous legal requirements and privacy concerns. In addition to
compliance with general data privacy regulation, it is necessary to consider compliance with industry-specific
legislation in different countries. SAP provides specific features and functions to support compliance with
regards to relevant legal requirements, including data protection. SAP does not give any advice on whether
these features and functions are the best method to support company, industry, regional, or country-specific
requirements. Furthermore, this information does not give any advice or recommendation in regards to
additional features that would be required in particular IT environments; decisions related to data protection
must be made on a case-by-case basis, under consideration of the given system landscape and the applicable
legal requirements.
 Note
In the majority of cases, compliance with applicable data protection and privacy laws will not be covered by
a product feature. SAP software supports data protection compliance by providing security features and
specific data protection-relevant functions, such as simplified blocking and deletion of personal data. SAP
does not provide legal advice in any form. Definitions and other terms used in this document are not taken
from any given legal source.
 Caution
The extent to which data protection is supported by technical means depends on secure system operation.
Network security, security note implementation, adequate logging of system changes, and appropriate
usage of the system are the basic technical requirements for compliance with data privacy legislation and
other legislation.
SAP assumes that you as the yard operating company have a contractual agreement with the drivers giving
their consent to your collecting or transferring their personal data to the system.
You also need to make sure that no personal data enters the system in an uncontrolled or non-purpose related
way, for example, in free-text fields, through APIs, or customer extensions. Note that these are also not subject
to the RAL example configuration.
8.6.2 Glossary
The following terms are relevant in the context of data protection and privacy. Not all terms may be relevant for
SAP Yard Logistics for SAP S/4HANA.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
155
Term
Definition
Blocking
A method of restricting access to data for which the primary
business purpose has ended.
Consent
The action of the data subject confirming that the usage of
his or her personal data shall be allowed for a given purpose.
A consent functionality allows the storage of a consent re­
cord in relation to a specific purpose and shows if a data
subject has granted, withdrawn, or denied consent.
Data subject
An identified or identifiable natural person. An identifiable
natural person is one who can be identified, directly or indi­
rectly, in particular by reference to an identifier such as a
name, an identification number, location data, an online
identifier or to one or more factors specific to the physical,
physiological, genetic, mental, economic, cultural, or social
identity of that natural person.
Deletion
Deletion of personal data so that the data is no longer availa­
ble.
End of business
Date on which the business with a data subject ends, for ex­
ample, the order is completed, the subscription is canceled,
or the last bill is settled.
End of purpose (EoP)
End of purpose and start of blocking period. The point in
time when the primary processing purpose ends, for exam­
ple, a contract is fulfilled.
End of purpose (EoP) check
A method of identifying the point in time for a data set when
the processing of personal data is no longer required for the
primary business purpose. After the EoP has been reached,
the data is blocked and can only be accessed by users with
special authorization, for example, tax auditors.
Personal data
Any information relating to a data subject.
Purpose
The information that specifies the reason and the goal for
the processing of a specific set of personal data. As a rule,
the purpose references the relevant legal basis for the proc­
essing of personal data.
Residence period
The period of time between the end of business and the end
of purpose (EoP) for a data set during which the data re­
mains in the database and can be used in case of subse­
quent processes related to the original purpose.
At the end of the longest configured residence period, the
data is blocked or deleted. The residence period is part of
the overall retention period.
156
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
Term
Definition
Retention period
The period of time between the end of the last business ac­
tivity involving a specific object (for example, a business
partner) and the deletion of the corresponding data, subject
to applicable laws.
The retention period is a combination of the residence pe­
riod and the blocking period.
Sensitive personal data
A category of personal data that usually includes the follow­
ing type of information:
●
Special categories of personal data such as data reveal­
ing racial or ethnic origin, political opinions, religious or
philosophical beliefs, or trade union membership and
the processing of genetic data, biometric data, data
concerning health, sex life or sexual orientation or per­
sonal data concerning bank and credit accounts
●
Personal data subject to professional secrecy
●
Personal data relating to criminal or administrative of­
fenses
●
Personal data concerning insurances and bank or credit
card accounts
Where-used check (WUC)
A process designed to ensure data integrity in the case of
potential blocking of business partner data. An application’s
where-used check (WUC) determines if there is any depend­
ent data for a certain business partner in the database.
If dependent data exists, this means the data is still required
for business activities. Therefore, the blocking of business
partners referenced in the data is prevented.
8.6.3 Information Report
Data subjects have the right to get information regarding their personal data undergoing processing. The
information retrieval feature supports you to comply with the relevant legal requirements for data protection by
allowing you to search for and retrieve all personal data for a specified data subject. The search results are
displayed in a comprehensive and structured list containing all personal data of the data subject specified,
subdivided according to the purpose for which the data was collected and processed.
In SAP Yard Logistics for SAP S/4HANA, this function is implemented in the overview lists for the yard
documents like Yard Order, Yard Request, and Yard Task. Personal data for the driver can be queried to check
which of the yard documents are related to his personal data stored in the system. Technically, this is achieved
by extending the overview lists to enter the driver's name as an additional search parameter.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
157
8.6.4 Deletion of Personal Data
Simplified Blocking and Deletion
When considering compliance with data protection regulations, it is also necessary to consider compliance
with industry-specific legislation in different countries. A typical potential scenario in certain countries is that
personal data shall be deleted after the specified, explicit, and legitimate purpose for the processing of
personal data has ended, but only as long as no other retention periods are defined in legislation, for example,
retention periods for financial documents. Legal requirements in certain scenarios or countries also often
require blocking of data in cases where the specified, explicit, and legitimate purposes for the processing of
this data have ended, however, the data still has to be retained in the database due to other legally mandated
retention periods. In some scenarios, personal data also includes referenced data. Therefore, the challenge for
deletion and blocking is first to handle referenced data and finally other data, such as business partner data.
Deletion of Personal Data
The processing of personal data is subject to applicable laws related to the deletion of this data when the
specified, explicit, and legitimate purpose for processing this personal data has expired. If there is no longer a
legitimate purpose that requires the retention and use of personal data, it must be deleted. When deleting data
in a data set, all referenced objects related to that data set must be deleted as well. Industry-specific legislation
in different countries also needs to be taken into consideration in addition to general data protection laws. After
the expiration of the longest retention period, the data must be deleted.
SAP Yard Logistics for SAP S/4HANA might process data (personal data) that is subject to the data protection
laws applicable in specific countries as described in SAP Note 1825544.
Deletion
To enable even complex scenarios, SAP simplifies existing deletion functionality to cover data objects that are
personal data by default. For this purpose, SAP uses SAP Information Lifecycle Management (ILM) to help you
set up a compliant information lifecycle management process in an efficient and flexible manner. The functions
that support the simplified blocking and deletion of personal data are not delivered in one large
implementation, but in several waves. Scenarios or products that are not specified in SAP Note 1825608
(central Business Partner) and SAP Note 2007926 (ERP Customer and Vendor) are not yet subject to
simplified blocking and deletion.
Nevertheless, it is also possible to destroy personal data for these scenarios or products. In these cases, you
have to use an existing archival or deletion functionality or implement individual retention management of
relevant business data throughout its entire lifecycle. The SAP Information Lifecycle Management (ILM)
component supports the entire software lifecycle including the storage, retention, blocking, and deletion of
data.
SAP Yard Logistics for SAP S/4HANA uses SAP ILM to support the deletion of personal data as described in the
following sections.
All applications register either an end of purpose check (EOP check) in the Customizing settings for the
blocking and deletion of application data (for example, the customer and vendor master or the business
partner) or a WUC.
End of Purpose Check (EoP check)
158
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
An end of purpose check determines whether data is still relevant for business activities based on the retention
period defined for the data. The retention period is part of the overall lifecycle of personal data which consists
of the following phases:
● Business activity: The relevant data is used in ongoing business, for example contract creation, delivery or
payment.
● Residence period: The relevant data remains in the database and can be used in case of subsequent
processes related to the original purpose, for example reporting obligations.
● Blocking period: The relevant data needs to be retained for legal reasons. During the blocking period,
business users of SAP applications are prevented from displaying and using this data; it can only be
processed in case of mandatory legal provisions.
● Deletion: The data is deleted and no longer exists in the database.
The following figure illustrates the lifecycle of personal data:
Blocking
Blocking of data can impact system behavior in the following ways:
● Display: The system does not display blocked data.
● Change: It is not possible to change a business object that contains blocked data.
● Create: It is not possible to create a business object that contains blocked data.
● Copy/Follow-Up: It is not possible to copy a business object or perform follow-up activities for a business
object that contains blocked data.
● Search: It is not possible to search for blocked data or to search for a business object using blocked data in
the search criteria.
It is possible to display blocked data if a user has special authorization; however, it is still not possible to create,
change, copy, or perform follow-up activities on blocked data.
Where-Used Check (WUC)
A where-used check is a simple check to ensure data integrity in case of potential blocking. The WUC for this
product checks whether any dependent data for a customer, vendor, or central business partner (cBP) exists in
the respective table. If dependent data exists, that is, if the data is still required for business activities, the
system does not block that specific customer, vendor, or cBP.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
159
If you still want to block the data, the dependent data must be deleted by using the existing archival and
deletion tools or by using another customer-specific solution.
Specifics for SAP Yard Logistics for SAP S/4HANA
To enable even complex scenarios, SAP simplifies existing deletion functionality to cover data objects that is
personal data by default. For this purpose, SAP Yard Logistics uses SAP Information Lifecycle Management
(ILM) to help you set up a compliant information lifecycle management process in an efficient and flexible
manner. The functions that support the simplified blocking and deletion of personal data are not delivered in
one large implementation, but in several waves. Scenarios or products that are not specified in SAP Note
1825608 (central Business Partner) are not yet subject to simplified blocking and deletion. Nevertheless, it is
also possible to destroy personal data for these scenarios or products. In these cases, you have to use an
existing archival or deletion functionality or implement individual retention management of relevant business
data throughout its entire lifecycle. The SAP Information Lifecycle Management (ILM) component supports the
entire software lifecycle including the storage, retention, blocking, and deletion of data.
Furthermore, the read APIs have been changed, such that no personal data is returned if a business user
queries a document that contains a blocked business partner.
On the user interface of the yard documents (that is, yard order, yard request, or yard task), a blocked business
partner shall not be available for selection from the F4 help. In this manner, the display of personal data of
blocked business partners using any search is prevented.
Within Yard Logistics, the business documents Yard Request, Yard Order, Yard Task, and Yard Transportation
Unit may contain personal data like business partners or users. You can delete such objects using archiving
services. For more information, see section Settingsà Data Archiving in Yard Logistics (SCM-YL) in the
application help for this solution on the SAP Help Portal. To access the application help, go to http://
help.sap.com/yl_s4hana
The available archiving objects are listed in the following table:
Archiving Object and Provided Dele­
Business Document
Yard Order / Yard Request
Description
tion Functionality
Business partners and users are stored
You can use archiving services to delete
in the yard orders/ requests. For exam­
the objects. The archiving objects to be
ple, in the YR/YO header and the tabs
deleted are: /SAPYL/YO
Business Partner and Administrative
Data.
Example fields: Carrier, Driver, Created
by
Yard Task
Yard Tasks contain driver names and
You can use archiving services to delete
phone numbers as well as users on the
the objects. The archiving objects to be
General Data and the Administrative
deleted is:
Data tabs.
Yard Transportation Unit
Yard Transportation Units use details of
You can use archiving services to delete
users and license plate information on
the objects. The archiving objects to be
the TU Header and the Administrative
deleted is:
Data tabs.
160
/SAPYL/YT
INTERNAL – Authorized for SAP Customers and Partners
/SAPYL/TU
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
To delete personal data, you do the following:
● Run transaction IRMPOL and maintain the required residence and retention policies for the central
business partner (ILM object: CA_BUPA).
● Run transaction IRMPOL and maintain the retention policies for the SAP ILM objects of the SAP Yard
Logistics solution:
● SAPYL_YO Yard Orders
● SAPYL_YT Yard Tasks
● SAPYL_TU Transportation Units
● Run transaction BUPA_PRE_EOP to enable the EoP check function for the central business partner.
● Business users can request unblocking of blocked data by using transaction BUP_REQ_UNBLK.
● If you have the necessary authorizations, you can unblock data by running transaction BUPA_PRE_EOP.
● You delete data by using transaction BUPA_PRE_EOP for the ILM objects of SAP Yard Logistics.
8.6.5 Migration Report for SAP Yard Logistics Drivers to
Business Partners
The solution does not allow the direct storing of drivers' personal data in the yard documents such as Yard
Order, Yard Request, or Yard Task, however, the solution offers the feature to create a business partner to
transfer the driver's personal data to it. The driver's business partner will be created automatically for new
business documents. For yard documents created before the introduction of this feature, a migration report is
provided to update existing documents to create a driver's business partner as well.
The report (that you can start by using transaction code /SAPYL/YO_DRIV_BP) creates a business partner for
a driver based on the driver information in one of the newest yard documents available in the solution. The
language, country, and contact number of a driver shall now be stored in the business partner. The ID of the
created business partner is stored in the Driver Type field in the yard documents in which the driver appears.
This report program allows you to select the yard documents for which you want to do the driver-to-businesspartner conversion. You have the option also restrict your selection by yard number.
8.6.6 Report to Update Start of Retention Time for Yard
Documents
In this solution, the system must perform an End of Purpose (EoP) check. An EoP check determines whether
the business partner is still relevant for business activities based on the retention period defined for it. If you
have activated the business function BUPA_ILM_BF, the system automatically updates the SoRT information
for all documents referring to business partners when a document is completed. However, you must note that
enabling this business function does not automatically update the SoRT information in previously-completed
documents that exist in your database.
You use this report (that you can start using transaction code /SAPYL/DPP_SORT) after you have maintained
all Information Lifecycle Management (ILM) policies for the ILM objects in the solution and have assigned the
documents to an ILM rule group via the ILM Live policy. On running the report, the Start of Retention Time
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
161
(SoRT) information is automatically calculated based on the defined ILM rules for all documents that refer to
business partners in the solution.
8.6.7 Change Log
Personal data is subject to frequent changes. Therefore, for review purposes or as a result of legal regulations,
it may be necessary to track the changes made to this data. When these changes are logged, you should be
able to check which employee made which change, the date and time, the previous value, and the current
value, depending on the configuration. It is also possible to analyze errors in this way.
The solution enables this by providing change pointers for all fields containing personal data. The business
objects related to Yard Request, Yard Order, Yard Task, as well as the business object for the Yard TU, have been
extended with this functionality. Thus, when a business user enters personal information into a yard document
such as Yard Request, Yard Order, or Yard Task, especially in fields for Driver, and Telephone Number, including
the prefix for country and region, these changes are written in the change documents and can be displayed for
review purposes. Similarly, when a business user enters or changes personal data on the Administrative tab of
the Yard TU screen, the entries are recorded in the change documents as well and can be reviewed on the
Change Documents tab.
Defining Fields to Be Logged
SAP Yard Logistics for SAP S/4HANA processes personal data of business partners that are involved in change
requests and activities. If any changes are made regarding the business partner, the system logs the following
information on personal data per change request and activity:
● The user who changed data
● The date and time of the change
● The change type (update, insert, deletion, single field documentation)
● The identifying keys and their values of the data records
● The heading name for the attribute that was changed
You can define the fields to be logged under Display Change Document Objects (transaction SCDO).
You use the authorization object to IAM/CHGLOG to control the change logging for change requests and
activities.
Displaying Change Logs
In the worklist of SAP Yard Logistics for SAP S/4HANA, you can access a change log for each change request
and activity.
 Note
Change logs can only be displayed if the user is assigned the authorization role SAP_AUTH_MOC_ADMIN.
Under Evaluate New Audit Trail Enhancement Mode (transaction S_AUT10), you can see all changes that
have been processed for the change document objects in SAP Yard Logistics for SAP S/4HANA, S_/IAM/ACT
(activity) and /IAM/ISSUE (change request).
162
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
For more information about change documents, see the documentation for your SAP NetWeaver release at
http://help.sap.com/nw. Choose the relevant SAP NetWeaver release and open the following documents:
● Under Application Help, choose
ABAP
Other Services
● Under Security, choose
SAP NetWeaver Library: Function-Oriented View
Services for Application Developers
SAP NetWeaver Security Guide
Application Server
Change Documents .
Security Aspects for Lifecycle Management
Auditing and Logging .
8.6.8 Security for Internet of Things Geofencing
The Geofencing scenario relies on GPS sensor data, which allows the tracking of all movements of specific TUs
like trucks that are driven by natural persons through the yard. Therefore, this event data must be considered
as personal data within the Yard Logistics system. On SAP IoT Service system side, all GPS sensor
measurement data is stored with reference to a Thing (Thing Type), which is the business object representation
of a specific TU. Such time series data storage is not under the control of SAP Yard Logistics and this data may
potentially be retained for lengthy periods, or even for an unlimited time within the SAP IoT data stores.
All these aspects together impose special security and data protection requirements, which lie in the
responsibility of the customer to set up and run the Geofencing process in a legally compliant manner on both
system sides.
8.6.8.1
Geofencing Security in Yard Logistics
In the Geofencing process, SAP IoT sends entry and exit event data containing detailed geo-positioning with
reference to a Thing, a Geofence and timestamps, when the measurement and the event precisely happened,
to the Yard Logistics system. For example, a TU (Thing) with an active and registered GPS device arrives at the
check-in gate of a yard where the gate is defined as a Geofence. The GPS device constantly sends geopositioning data to SAP IoT, and once the actual position is determined as entering the Geofence, SAP IoT
sends a Geofence event to Yard Logistics to trigger a yard order check-in. Since this process is an automated
scenario without human involvement, each Geofence event and its detailed request data is stored in a business
application log with reference to technical log object /SCWM/WME, subobject /SAPYL/IOT for traceability
reasons. The yard order affected by such an event may also contain personal data of the assigned TU driver.
The following important technical precautions and recommendations are to be considered in that context:
● SAP Yard Logistics does not store any event data in the business application log without a valid business
reason. Technically, for any Thing or Geofence event sent from SAP IoT, which could not be referenced to a
TU or Geofence within Yard Logistics system, there will not be any log entry created to prevent unintended
storage of data without a valid business reason.
● Handling business application logs is the responsibility of the administrator running the Yard Logistics
system. SAP strongly recommends deleting without delay all business application logs of subobject /
SAPYL/IOT after the legitimate business purpose expires in accordance with the applicable legislation
rules. For more information on how to delete these logs, see SAP Note 195157
.
● SAP Yard Logistics does only allow registration of Geofences, which are at that point in time explicitly
categorized at sensitivity level Personal or even Sensitive. It is the responsibility of the customer running
the Yard Logistics system to ensure that the appropriate sensitivity level is applied in the Yard Logistics
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
163
system, and in the IoT Tenant as well. The customer must ensure that this level is not changed afterwards.
For more information, see section Geofencing Security in SAP Internet of Things [page 164].
SAP strongly recommends considering classifying the property sets used in Geofencing as Personal or even
Sensitive. For more information, see section Geofencing Security in SAP Internet of Things [page 164].
8.6.8.2
Geofencing Security in SAP Internet of Things
Most objects required within SAP IoT to operate the Geofencing scenario can be created or deleted
automatically from the Yard Logistics system. Apart from the limited control at the individual object level, Yard
Logistics does not control the SAP IoT data setup in any way, The customer is wholly responsible for operating
the IoT Tenant, which, among other data, also contains the GPS time series data, in a secure manner. The
following recommendations and resources are especially relevant in this context:
● Every Geofence and property set defined in the SAP IoT Tenant, which is supposed to be used within the
Yard Logistics Geofence scenario, must have sensitivity level Personal or Sensitive assigned. This ensures
that this data is automatically protected by SAP IoT, for example, with respect to read access logging. For
more information, see SAP IoT Security Guide, especially concerning Data Protection and Privacy in
general, and Read Access Logging regarding geolocations and Thing data (incl. GPS measurements) in
particular.
The deletion of time series data, for example, GPS measurements for a thing from SAP IoT according to legal
regulations and adhering to retention time is the responsibility of the customer who owns the IoT Tenant. For
more information about the different data stores of time series data, see Time Series Data Ingestion.
8.6.8.3
Geofencing Security – General Aspects
The following general security related recommendations, not specifically related to SAP, are relevant for
customers who are running the Geofencing process:
● SAP Yard Logistics stores the TU and driver data, whereas the SAP IoT stores the complete movement
measurements for a Thing (representing a TU). This implies that combined use of this data from both
systems may indirectly enable tracking of individual persons. Therefore, SAP strongly recommends
mitigating this risk by not authorizing the same person(s) for system access to both SAP IoT and Yard
Logistics, following the Need to Know and Minimal Privilege principles.
The physical GPS Device access and actual measurements must be protected according to the device
manufacturers’ guidelines to prevent unauthorized and/or incorrect data transmission to SAP IoT.
164
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Security Information for SAP Yard Logistics for SAP S/4HANA
9
Operating SAP Yard Logistics for SAP S/
4HANA
This section contains general information about how to operate SAP Yard Logistics for SAP S/4HANA.
 Note
This section does not replace the operations handbook in which customers or the operations organization
documents specific tasks, involved parties, and interaction procedures.
9.1
Other Required Documents for Operations
This section lists other documents that you need in order to operate SAP Yard Logistics for SAP S/4HANA.
This section lists other documents that you need in order to operate SAP Yard Logistics for SAP S/4HANA.
SAP Yard Logistics for SAP S/4HANA is based on SAP S/4HANA 1709. The general operations information that
is covered in the related operations guides also applies to SAP Yard Logistics for SAP S/4HANA.
Document
Where to Find It
Operations Guide for SAP S/4 HANA 1709
https://help.sap.com/s4hana_op_1709
9.2
Monitoring
Monitoring is an essential task in the management of SAP technology and applications. You can find more
information about monitoring on the SAP Help Portal under http://help.sap.com/nw752abap. Go to Technical
Operations for SAP Netweaver.
9.2.1 Alert Monitoring
Description of available monitoring tools for SAP Yard Logistics for SAP S/4HANA.
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP system environment.
SAP Yard Logistics is technically based on SAP NetWeaver Application Server, and reuses the Alert Monitor
framework used in SAP SCM Basis. You can set up the basic customizing using transaction /SCMB/ALENCFG –
Alert Engine Configuration.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
165
The possible alert categorization is defined via alert structures. These structures represent special topics for
alerting. The following table shows the predefined alert structures:
Alert Structures
Alert Structure
Name
2800
SYL: YT Exception
2810
SYL: Time Based Alerts
2820
SYL: Arrival and Departure
2830
SYL: Storage Bin Block
2840
SYL: Transportation Unit Block
2850
SYL: Thresholds
Based on the alert categorization, you can define the specific alert messages called alert types. The following
table shows the pre-defined alert types:
Alert Object Types
Alert Type
Alert Description
2801
Transportation Unit Damaged
2802
Transportation Unit Blocked
2811
Transportation Unit in Yard
2813
Check-in Delayed
2814
Check-out Delayed
2821
Arrival Date/Time has Passed
2822
Departure Date/Time has Passed
2831
Storage Bin Blocked for Putaways
2832
Storage Bin Blocked for Stock Removal
2833
Storage Bin Blocked for Putaways and Stock Removal
2841
Transportation Unit General Block
2851
Threshold Exceeded
To monitor the specific alerts created by this solution, you can use transaction /SAPAPO/AMON1. Select one of
the overall alert profiles showing all alerts for SAP Yard Logistics to see all posted alerts. For more information,
see; Alert Monitor in the documentation for SAP NetWeaver 7.5 on the SAP Help Portal.
166
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
9.2.2 Error Logs
This section describes the error logs used by SAP Yard Logistics for SAP S/4HANA.
The application log is a re-use tool that collects messages, exceptions, and errors. This information is organized
and displayed in a log. As the technical basis is SAP EWM, all solution-related logs are stored using object /
SCWM/WME. This enables the switching of log messages per SAP user and warehouse.
Application Log Sub Objects
Sub Objects
Description
/SAPYL/INTERFACE_EWM
EWM Interface Messages
/SAPYL/YARD_TU
Yard Transportation Unit
/SAPYL/YC
Yard Cockpit
/SAPYL/YO
Yard Order / Request
/SAPYL/YR_REL
Yard Request Release (by report)
/SAPYL/YT
Yard Task
/SAPYL/YT_DLOC_DET
Yard Task Destination Location Determination
/SAPYL/YT_QDET
Yard Task Queue Determination
/SAPYL/RESET_SEQ
Storage Bin Sequencing
More Information
 Note
For general information about application logs, refer documentation for SAP NetWeaver on SAP Help Portal
at http://help.sap.com/nw752abap and choose
SAP NetWeaver Library: Function-Oriented View
Application Help
Function-Oriented View . Go to
Solution Life Cycle Management
Application Log .
9.2.3 Workload Monitoring
This section describes aspects of workload monitoring for SAP Yard Logistics for SAP S/4HANA.
9.2.3.1
Monitoring Post-Processing Framework
The Post-Processing Framework (PPF) is used in SAP Yard Logistics to perform follow-up process actions
based on existing business objects, that is, yard orders, yard tasks and yard TUs. PPF monitoring can be
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
167
performed in two different ways. The first way is to use directly in the FPM user interface of the single
document maintenance for one of the business objects mentioned above. On these user interfaces, you can
find a custom UIBB area called Output Management that shows all PPF actions related to the current business
object document. For example, to verify whether a particular yard order has been sent to SAP TM, you can
navigate to the UIBB area Output Management and verify that an entry for the PPF action Send LDAP
Notification to SAP TM exists and has a green light. If this is the case, the yard order has been processed
successfully.
In the second, a more conventional method, you can use transaction SPPFP. Here, you have to enter the date
and period of the PPF action that you want to see.
● The application, which is fixed: /SAPYL/PPF for SAP Yard Logistics
● The action profile – /SAPYL/YO for yard orders, /SAPYL/TU for yard TUs, /SAPYL/YT for yard tasks
● The action definition – one of the entries mentioned in the table below
Then, you can see a PPF action processed as resulting list entries. If you have enabled the function, from this
list also you can re-trigger a PPF action.
PPF Actions in SAP Yard Logistics
Business Object
Action Profile
Action Definition
Description
Yard Task
/SAPYL/EXT_COMM
/SAPYL/DRIVER_COMM
Send driver’s notification
Yard Order
/SAPYL/YO_PRINT
/SAPYL/YO_PRINT_DOCU­
Yard Order Print (automated)
MENT
Yard Order
/SAPYL/YO_PRINT
/SAPYL/YO_PRINT_DOCU­
Yard Order Print (manual)
MENT_MAN
Yard Request
Yard Request
/SAPYL/YR_PRINT
/SAPYL/YR_PRINT
/SAPYL/YR_PRINT_DOCU­
Yard Request Print (auto­
MENT
mated)
/SAPYL/YR_PRINT_DOCU­
Yard Request Print (manual)
MENT_MAN
Yard Task
/SAPYL/YT_PRINT
/SAPYL/YT_PRINT_DOCU­
Yard Task Print (automated)
MENT
Yard Task
/SAPYL/YT_PRINT
/SAPYL/YT_PRINT_DOCU­
Yard Task Print (manual)
MENT_MAN
9.2.3.2
Monitoring in the 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, you can see the lists for yard orders, yard tasks, resources, and so on.
168
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
Technically, in these areas, UIBBs are shown in the FPM application, which allows for the efficient filtering and
display of the operational business documents, for example, yard tasks, yard order, TUs, and so on.
In the Yard Cockpit, the different UIBBs mentioned below in table 3, are treated independently. This means, for
example, one Yard Order in the Yard Order UIBB has no impact on the display of the Visual Yard.
The following table contains the UIBBs that are currently available in the yard cockpit.
Table 3 [HYPERLINK REMOVED]: Available UIBBs in the Yard Cockpit
UIBB
Description
Yard Tasks
With this UIBB, you can filter and display yard tasks based
on different criteria, such as creating new ones and editing
existing ones.
Yard Orders
With this UIBB, you can filter and display yard orders based
on different criteria.
Transportation Units
With this UIBB, you can filter and display TUs based on dif­
ferent criteria.
Alerts
With this UIBB, you can filter and display alerts based on dif­
ferent criteria.
Resources
With this UIBB, you can filter and display resources based on
different criteria.
 Note
Can click on the person symbol on the upper right corner to determine the layout of the yard cockpit.
9.2.3.3
Monitoring Driver's Communication via SMS
In SAP Yard Logistics, it is used to send an SMS for driver advice after the check-in of a Yard Order document.
This makes use of SAPconnect, a functionality to set up different communication possibilities sent from the
SAP system. To monitor the SMS sent, you can use transaction SOST.
 Note
Refer documentation on SAP NetWeaver 7.52 on SAP Help portal at http://help.sap.com/nw752abapand
choose Application Help. Go to
Other Services . Then select
Function-Oriented View
Application Server
Services for Business Users
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
Application Server ABAP
SAPconnect .
INTERNAL – Authorized for SAP Customers and Partners
169
9.2.4 Interface Monitoring
This section describes aspects of interface monitoring relevant for SAP Yard Logistics for SAP S/4HANA.
9.2.4.1
Integration Engine Monitoring and Restart
The interface connectivity between the current solution and SAP Transportation Management (SAP TM) is
based on integration scenarios using SAP PI. Therefore, the monitoring of the interface between SAP TM and
SAP Yard Logistics can be done using transaction SXMB_MONI. It is important to mention here that this
monitoring transaction is available in the sending system (for example, the system hosting SAP TM), the
receiving system (for example, the system that is running this solution), and in the PI system connecting both
these systems. Interface messages between these systems can be transferred correctly only if the messages
are processed successfully in all three systems. From this transaction, you can also trigger a message re-start if
the original call has ended in failure. A Restart button to re-process the web service call is available for use in
such a scenario.
9.2.4.2
Queue Monitoring
The integration engine of SAP PI as well as SAP EWM use A2A interfaces based on RFC function calls that are
processed via queued RFCs. The naming of the queues have been taken over from the naming conventions of
these applications. You can perform the basic monitoring using transaction SMQ1 for outbound queues, that is,
qRFC calls at sender side, or transaction SMQ2 for inbound queues, that is, qRFC calls at receiver side.
9.2.5 Background Job Monitoring
In addition to the standard jobs mentioned in Technical Operations for SAP NetWeaver, refer documentation
under Technical Operations for SAP NetWeaver at http://help.sap.com/nw752abap. You must schedule SAP
EWM-specific jobs in your SAP system. You must run all jobs, unless otherwise specified, at times of minimal
system activity, so as not to affect performance or otherwise disrupt your daily operations. You can restart all
jobs.
To release multiple yard requests based on their planned arrival or departure dates, automated via a
background process, the business can use transaction /SAPYL/MASS_YR_ACTIV to release multiple Yard
Requests on a planned arrival or departure date.
To analyze all the business objects in the yard, for example, yard requests, yard orders, yard task,
transportation units you need to plan the report /SAPYL/TIME_BASED_ALERTS_MASS on a periodical basis.
This report calls the relevant alert class that does the validations. If the validation of the alert class determines
that the business object is valid for an alert, the report raises the corresponding alert.
You can use the report /SAPYL/ARR_DEP_ALERTS to check the arrival and departure dates and times of yard
orders frequently during the day. This report triggers an alert automatically based on the settings. Alerts can be
170
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
displayed in the alert monitor. For inbound yard orders, the report checks only those yard orders for which the
check-in is not yet posted and for outbound yard orders, the report checks only those yard orders for which the
check-out is not yet posted
9.3
Administration and Management
This section describes administrator tasks for SAP Yard Logistics for SAP S/4HANA.
9.3.1 Starting and Stopping
SAP Yard Logistics for SAP S/4HANA is installed as Add-on to SAP S/4HANA 1709. The starting and stopping
procedure applicable to SAP S/4HANA 1709 are also valid for this product. For documentation on SAP S/
4HANA 1709, go to SAP Help Portal at https://help.sap.com/s4hana_op_1709, choose Operations Guide and go
to Starting and Stopping.
9.3.2 Technical Configuration
Aspects of technical configuration for SAP Yard Logistics for SAP S/4HANA.
● Yard transportation unit overview (WDCA_YARD_TU)
● Yard cockpit (WD_COCKPIT_NEW)
● Color picker (WD_COLOR_PICKER)
● Yard editor (WD_YARD_EDITOR)
● Yard order (WD_YO)
● Yard order check-in and check-out (WD_YO_CICO)
● Yard order overview (WD_YO_POWL)
● Assignment of TU to yard order (WD_YO_TU)
● Yard request (WD_YR)
● Yard request overview (WD_YR_POWL)
● Yard task (WD_YT)
● Yard transportation unit (WD_YTU)
● Yard task overview (WD_YT_POWL)
These applications are based on the Web Dynpro for ABAP technology. Therefore, we strongly recommend that
you read the operations information available for this UI technology first. This information is provided with the
documentation for your SAP NetWeaver release. You can access this information on SAP Help Portal at https://
help.sap.com/viewer/p/SAP_NETWEAVER.
You must also activate the corresponding SICF nodes to the applications (mentioned in brackets).
More Information
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
171
 Note
See Activating ICF Services. Go to https://help.sap.com/viewer/p/SAP_NETWEAVER_AS_ABAP_752 and
choose
Application Help
Floorplan Manager
UI Technologies in SAP NetWeaver . Go to
Web Dynpro ABAP
Web Dynpro ABAP and
Web Dynpro ABAP Administration
Initial System-Wide
Configuration Settings for Web Dynpro ABAP .
9.3.2.1
Yard Visualization Using SAP Visual Business
To enable the yard visualization in this solution, you must install and configure the SAP Visual Business frontend component (see SAP Visual Business [page 17]). Based on this technical setup, the yard objects to be
visualized need to be completed using the yard object editor
9.3.2.2
SAP Fiori Launchpad and Mobile Apps
To use SAP Fiori Launchpad, you must set it up as described in section SAP Fiori Launchpad [page 18].
Once you have done this, you must provide role-specific authorizations to your business users to access the
Fiori Launchpad applications. To this end, you have to assign the following pre-defined roles to the users:
Technical Role
Description
Notes
/SAPYL/YTASK_APP
SAP Yard Logistics – Backend Role for
Only relevant for the SAPUI5 user inter­
Fiori App – Yard Task Confirmation
face
SAP Yard Logistics – Backend role for
Only relevant for the SAPUI5 user inter­
Fiori App – Self Check-In
face
SAP Yard Logistics – Business Role for
Only relevant for the SAPUI5 user inter­
Yard Operator
face
Business Role for Yard Gate Agent
Only relevant for the SAPUI5 user inter­
/SAPYL/SELFCHECKIN_APP
/SAPYLUI/BCR_YARDOPERATOR_T
/SAPYLUI/BCR_GATEAGENT_T
face
/SAPYLUI/TCR_T
SAP YL – Technical Role for Fiori
Only relevant for the SAPUI5 user inter­
Launchpad
face
After that, populate the Launchpad with the right apps. For this, you can use transaction /UI2/FLP_CONF –
Fiori Launchpad Designer.
172
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
SAP Yard Logistics provides the following catalogs available in the Launchpad:
Catalog ID
Description
X-SAP-UI2-CATALOGPAGE:/SAPYLUI/BC_YARDOPERA­
Apps for SAP YL Yard Operator
TOR_T
X-SAP-UI2-CATALOGPAGE:/SAPYLUI/BCC_GATE_AGENT_T Apps for SAP YL Gate Agent
X-SAP-UI2-CATALOGPAGE:/SAPYLUI/TC_T
Apps for SAP YL
To be able to start the mobile apps, semantic objects YardTask and YardOrderSelfCheckIn are defined.
You must also activate the SICF nodes /default_host/sap/bc/ui5_ui5/sapylui/ytask (for this mobile
application) and the SICF node /default_host/sap/opu/odata/sapyl/das_yard_operator_srv (for
the ODATA service in the SAP Yard Logistics backend).
For the self check-in app, you must activate the SICF node /default_host/sap/opu/odata/sapyl/
self_check_in_srv.
To fully support the SAP Fiori Launchpad, the product has to provide business roles, business catalogs and
technical catalogs tailored to be used in the SAP Fiori Launchpad. The following figure shows the relationships
between these elements.
Besides the Business Catalogs, also technical catalogs need to be defined (on front end as well as backend
side) that contain the links to the different applications: classical gui transactions, Web Dynpro ABAP links
(from our FPM applications) and Fiori app links.
The following naming conventions have been applied:
Maintained on the Frontend
Technical Catalogs
Fiori Applications*)
SAP_TC_<..>_COMMON
Server in FLP Designer
Non-Fiori UI5 Applications
SAP_TC_<...>_OTHER_UI5
Maintained on the Frontend
Server in FLP Designer
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
173
Maintained on the Frontend
Technical Catalogs
Fiori Applications*)
SAP_TC_<..>_COMMON
Server in FLP Designer
WebGUI and Web Dynpro
SAP_TC_<...>_BE_APPS
Maintained in the Backend
ABAP Applications
Server via the Mass Mainte­
nance Tool and replicated to
the Frontend server
Business Catalogs
References to all technical
SAP_<...>_BC_<...>
App Types
Maintained on the Frontend
Server in FLP Designer, com­
prised of references to the
above
The angled brackets and ellipses <…> are placeholders for the area plus subarea, in our case: YL_
9.3.2.2.1
Semantic Objects
Semantic objects and semantic object actions must be defined for the Backend Technical Catalog.
This has to be maintained in transaction MM_APP on the local development system.
The actions can be defined freely whereas the semantic objects need to come from the predefined list of
transaction /UI2/SEMOBJ_SAP – Define Semantic Object – SAP.
The following semantic objects have been defined and will be delivered with SAP_UI 752 SP04.
A Yard Request is the leading document for managing
YardRequest
yard’s planning for a specific yard
YardOrder
A Yard Request is the leading document for managing yard’s
execution for a specific yard
YardTransportationUnit
A Yard Transportation Unit is a representative for a Yard’s as­
set with physical dimensions like a container, a truck or a
railcar
YardTask
A Yard Task is a business object that represents common
tasks/activities on a yard
YardSelfCheckIn
A Yard Order is the leading document for managing yard’s
planning and execution. The YO Self check-in is a special
case for planning the yard check in based on a yard order di­
rectly at the yard’s gate.
YardCockpit
The Yard Cockit is a visualization scheme for the most criti­
cal planning and execution lists in one single view for the
business user
174
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
A Yard Request is the leading document for managing
YardRequest
yard’s planning for a specific yard
YardLoadingAppointment
The Yard Loading Appointment is specific Loading Appoint­
ment related to time-based activities in a yard
YardFireDepartmentList
The Yard Fire Department List is a representation of hazard­
ous information of yard area’s a fire department needs to
have in case of an emergency
YardMaterialSeparation
The Yard Material Separation is used to separate different
materials withing the yards facility based on logistical crite­
ria
YardNumber
The Yard Number is the organisational unit for representing
yards
YardResource
A yard ressource is a person or asset assigned to a yard
document to perform the related activties
YardQueue
A yard queue is the representation of a queue for yard activi­
ties to be performed in a specific order
YardVisualization
The Yard Visualization is a abstract representation of the set­
tings and local data necessary for the yard cockpit
YardSystem
The Yard system is the system representative for a yard
number
YardDriver
A yard driver is a specific ressource to drive an asset in the
yard
YardTaskConfirmation
A Yard Task is a business object that represents common
tasks/activities on a yard. The yard task confirmation is the
step to confirm that the activities in the yard based on the
yard task have been executed
9.3.2.2.2
Definition of Frontend and Business Catalogs
The front end catalogs (containing the Fiori apps) need to be defined in the Fiori Launchpad Designer /UI2/
FLPD_CONF. They are assigned to software component /SAPYL/YLUI.
Starting point for the definition of the front end catalogs is the replicated backend catalog
SAP_TC_YL_BE_APPS that link to our FPM and GUI based applications. Based on this technical catalog the
business catalogs are defined as reference mappings to its tiles and its related target mappings, I.e. the tiles are
re-used and the target mappings as well. The target mapping defines how to call a specific application in the
backend. For example, if you want to call an FPM application you have to define the FPM application name and
its FPM configuration plus the relevant parameters that steer the mode of the screen (whether it is in display or
change mode).
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
175
For the existing UI5/Fiori apps we have the technical catalog SAP_TC_YL_COMMON that contain only the
Frontend apps (no replication from backend needed for these kind of applications).
The following business catalogs have been defined for SAP YL:
● Execution: SAP_YL_BC_EXEC
● Master Data: SAP_YL_BC_MD
● Planning: SAP_YL_BC_PLAN
● Mobile Operations: SAP_YL_BC_MOB
● Monitoring: SAP_YL_BC_MON
● Settings: SAP_YL_BC_SETTINGS
● Yard Operations: SAP_YL_BC_YARDOPS
The backend catalogs (containing the gui transactions and the WDA’s) need to be defined in mass maintenance
tool (transaction MM_APP). They need to be assigned to software component /SAPYL/YL. The business groups
are defined in the Fiori Launchpad Designer. They represent edition-specific (on-premise/cloud) grouping of
visible apps from business catalogs of the product in the Fiori Launchpad. This means, they represent the end
user point of view and should have unique titles within the related business roles.
The following business groups have been defined:
● Master Data and Settings: SAP_YL_BCG_MDS, containing the catalogs for Master Data and Settings
● Monitoring: SAP_YL_BCG_MON containing the catalog for monitoring
● Planning and Execution: SAP_YL_BCG_PLAN_EXEC containing the catalogs for Planning and Execution
● Yard Operations: SAP_YL_BCG_YARDOPS containing the catalog for yard operations
9.3.2.2.3
PFCG Role Definitions for Accessing SAP Fiori
Launchpad
Once the business catalogs and the business groups have been defined, these two artifacts need to be saved to
a PFCG role and assigned to the business user’s SAP user in order to let him access the launchpad.
For this, the PFCG roles have been defined as:
● /SAPYLUI/SAP_BR_YARD_MANAGER containing the full application scope
● /SAPYLUI/SAP_BR_YARD_OPERATOR containing only the yard operations part (that is, the.handling of
yard tasks)
9.3.2.2.4
Definition and Setup of Fiori System Aliases
For SAP YL we have defined a new Fiori system alias S4YL, that reads the technical catalogs from the “remote”
backend system to the FLP frontend server. This concept is used to separate the frontend catalogs from the
backend catalogs.
Technically this is only an entry in maintenance view /UI2/V_SYSALIAS (only reachable via SM30).
176
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
Based on that the client customizing for the Fiori setup can be performed in the views:
/UI2/V_ALIASCAT: for connecting the technical catalog to the Fiori system alias
/UI2/V_ALIASMAP: for mapping the client, Fiori system alias to a target Fiori system alias, i.e., you can map an
alias used for a catalog to a “centrally” configured alias like S4SCM to simplify the system setup
Then, as a next step, for the centrally configured alias S4SCM the full setup of SM59 connections need to be
performed following the naming pattern as described in the online help:
“Set Up RFC Connections to Backend Systems”
From https://help.sap.com/viewer/cc1c7615ee2f4a699a9272453379006c/7.5.9/en-US/
0a3f7e6296d7498d828ec512e8f8d2a4.html
9.3.2.2.5
Replication of the Backend Catalogs to Frontend
In order to have the technical “backend” catalog visible on the FLP designer, the backend catalog needs to be
replicated.
You replicate the backend catalogs to the frontend by running report /UI2/GET_APP_DESCR_REMOTE_DEV
and replicating the technical catalog SAP_TC_YL_BE_APPS with the replication system alias S4YL, if this has
been setup successfully in the previous step.
Now the configuration of the front end catalogs is possible.
9.3.3 Backup and Restore
This section describes procedures for backing up and restoring SAP Yard Logistics for SAP S/4HANA.
You must back up your system landscape regularly to ensure that you can restore and recover it in case of
failure. The backup and restore strategy for the application consists of the following:
● Backup and restore coverage for each component
● Cross-system data dependencies and handling
The backup and restore strategy for your system landscape must not only consider SAP systems but must also
be embedded in the overall business requirements and incorporate your company’s entire process flow. In
addition, the backup and restore strategy must cover disaster recovery processes, such as, the loss of a data
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
177
center through fire. In this context, it is essential that you ensure that backup devices are not lost together with
normal data storage, by using separate storage locations.
SAP Yard Logistics for SAP S/4HANA is based on SAP NetWeaver technology. All related SAP NetWeaver
backup procedures also work for this solution. Therefore, there is no special procedure for this component. For
more information on backup and recovery, see http://help.sap.com/nw752abap. Go to Operations , then
Technical Operations for SAP Netweaver.
9.3.4 Periodic Tasks
This section describes periodic tasks that must be completed for SAP Yard Logistics for SAP S/4HANA.
In addition to the standard jobs mentioned in Technical Operations for SAP NetWeaver, you must schedule SAP
EWM-specific jobs in your SAP system. You must run all jobs, unless otherwise specified, at times of minimal
system activity, so as not to affect performance or otherwise disrupt your daily operations. You can restart all
jobs.
To release multiple yard requests based on their planned arrival or departure dates, automated via a
background process, the business can use transaction /SAPYL/MASS_YR_ACTIV to release multiple Yard
Requests on a planned arrival or departure date.
To analyze all the business objects in the yard, for example, yard requests, yard orders, yard task,
transportation units you need to plan the report /SAPYL/TIME_BASED_ALERTS_MASS on a periodical basis.
This report calls the relevant alert class that does the validations. If the validation of the alert class determines
that the business object is valid for an alert, the report raises the corresponding alert.
You can use the report /SAPYL/ARR_DEP_ALERTS to check the arrival and departure dates and times of yard
orders frequently during the day. This report triggers an alert automatically based on the settings. Alerts can be
displayed in the alert monitor. For inbound yard orders, the report checks only those yard orders for which the
check-in is not yet posted and for outbound yard orders, the report checks only those yard orders for which the
check-out is not yet posted
9.3.5 Load Balancing and Scalability
This section describes aspects of load balancing and scalability that are relevant for SAP Yard Logistics for SAP
S/4HANA.
This solution is installed as an Add-on to SAP S/4HANA 1709. Therefore, you should consult the load balancing
and scalability valid for this product. See SAP Help Portal at https://help.sap.com/s4hana_op_1709, choose
Operations Guideand go to Load Balancing and Scalability
178
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
9.3.6 High Availability
This section describes aspects of high availability that are relevant for SAP Yard Logistics for SAP S/4HANA
This solution is installed as an Add-on to SAP S/4HANA 1709. Therefore, you should consult the high
availability concepts valid for this product. See SAP Help Portal at https://help.sap.com/s4hana_op_1709.
9.4
Software Change Management
This section provides information about how to deploy software changes for your software components.
Software change management standardizes and automates software distribution, maintenance, and testing
procedures for complex software landscapes and multiple software development platforms.
SAP Yard Logistics for SAP S/4HANA is installed as Add-on to SAP S/4HANA 1709. Therefore, you should
consult the software change management valid for this product. See SAP Help Portal at https://help.sap.com/
s4hana_op_1709, choose Operations Guide and go to Software Change Management.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Operating SAP Yard Logistics for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
179
10 Troubleshooting
This section describes troubleshooting options for SAP Yard Logistics for SAP S/4HANA.
.
SAP Yard Logistics for SAP S/4HANA is installed as Add-on to SAP S/4HANA 1709. Therefore, you should
consult the software change management valid for this product. See SAP Help Portal at https://help.sap.com/
s4hana_op_1709, choose Operations Guide and go to Troubleshooting.
10.1 Tips and Tricks
Tips and tricks for troubleshooting
Issue
Resolution
The visualization of the yard cockpit looks strange and you
Clear the cache of the Visual Business GUIBB.
have defined the items in a correct way.
The SAP Visual Business control in the browser caches map
tiles on the front-end machine. It may be necessary to clear
the cache if you encounter misaligned map tiles.
The cache content is controlled through the Visual Business
Property window that you can open with Ctrl + Alt + Right
click Ctrl + Alt + Right click . The window offers
a Cache tab, which shows you the actual cache location and
its content. Furthermore, it allows you to clear the cache
completely.
For more information, see https://help.sap.com/viewer/p/
SAP_VISUAL_BUSINESS_2.1, go to Application Help and
navigate to
180
INTERNAL – Authorized for SAP Customers and Partners
Visual Business Elements
Cache Control.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Troubleshooting
Issue
Resolution
The visualization of the yard cockpit is not starting or shows
This is an issue in the browser security, for example, Internet
a white space or an error message “No map can be dis­
Explorer 11, and for the browser, you have to allow “insecure”
played for VisBis UIBB”
ActiveX controls. See the security setting for IE11 as an ex­
ample:
1

Recommendation
See also 2305753 - FPM Visual Business GUIBB: Only
white space displayed; no VBI control rendered
There is an issue in a Web Dynpro ABAP that is only reprodu­ 2198046 – How to resolve user-specific issues in Web Dyn­
cible by a specific user.
This issue may be represented by a blank screen, a dump or
pro ABAP and use WD application WD_ANALYZE_CON­
FIG_USER
a time-out error.
Changes to BO field control for yard orders, yard requests or
Open transaction SHMM, then find the shared area /BOFU/
yard tasks are not up-to-date after transport.
CL_BO_FIELDCONTROL_SHM and select Delete All
Instances button on the table toolbar. Then refresh the Web
Dynpro application and all the fields are disabled according
to the updated field control database table.

Caution
If several business users are using Web Dynpro applica­
tions in parallel, the solution may crash as a result of the
shared memory instances being deleted.
You have changed Customizing settings for the self check-in
The target system’s client cache needs to be refreshed for
app but you still see the old version in the target system
your user. To do so, start transaction SA38 and run the re­
port /UI2/INVALIDATE_CLIENT_CACHE
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Troubleshooting
INTERNAL – Authorized for SAP Customers and Partners
181
Issue
Resolution
You are using the NWBC locally and have empty F4 value
The reason is a browser bug released in a security patch in
help lists
May by Microsoft, which causes that issue. 2375211
The queues are hanging and you want to automate their re­
You can schedule the following reports on a regular basis:
start
●
RSQOWKEX: Restart QOUT qRFC LUWs
●
RSQIWKEX: Restart QIN qRFC LUWs
.
For more information, please consult the 813029 - Auto­
matic processing of failed XI messages
182
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Troubleshooting
11
Uninstalling SAP Yard Logistics 2021 for
SAP S/4HANA
If, for any technical or business reason, you have to uninstall the SAP Yard Logistics 2021 for SAP S/4HANA
add-on, refer to the information in the following. This section provides information on how to uninstall this addon.
The uninstallation is carried out via transaction SAINT and uninstalls both components, that is, SAPYL and
SAPYLUI.
If you want to uninstall the SAP Yard Logistics 2021 for SAP S/4HANA solution from your landscape, you should
first consult the following SAP Notes:
SAP Note No.
Note Title
SAP Note 2909138
Uninstalling Add-On SAPYL
Purpose
This SAP Note contains information
how to uninstall add-on SAPYL.
SAP Note 2903462
Plug In class for uninstallation of Add On This SAP Note contains information
SAPYL
about the plug-in class to uninstall
.
SAP Note 2230296
Release strategy for the ABAP add-on
This SAP Note also ontains information
SAPYL
about uninstallation.
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Uninstalling SAP Yard Logistics 2021 for SAP S/4HANA
INTERNAL – Authorized for SAP Customers and Partners
183
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
●
●
Links with the icon
: You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
●
The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
●
SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
Links with the icon
: You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms
Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features
Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.
184
INTERNAL – Authorized for SAP Customers and Partners
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Important Disclaimers and Legal Information
Administration Guide for SAP Yard Logistics for SAP S/4HANA
Important Disclaimers and Legal Information
INTERNAL – Authorized for SAP Customers and Partners
185
www.sap.com/contactsap
© 2021 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. The information contained herein may be changed
without prior notice.
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 or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP 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.
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. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for
additional trademark information and notices.
THE BEST RUN