User Guide | PUBLIC
Document Version: 1.0 – 2022-02-08
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
SAP Transportation Management, Lead to
Agreement for Container Shipping Liners for SAP
S/4HANA
THE BEST RUN
Content
1
Introduction to Lead to Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
2
Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1
Commodity Master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Creating a Commodity Master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Harmonized Tariff Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
UN Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Adding Commodity Long Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Adding Attachments to Commodities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Commodity Output Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Commodity Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
2.2
Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Tabs in Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Brand-Specific Data in Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Approval-Relevant Fields in Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Creating Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Changing Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Copying Partner and Location Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Deactivating Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Reactivating Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Deleting Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Performing Mass Update of Partner Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Uploading Data to PLP Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Uploading Mass Data to Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
POWL for Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
APIs for Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.3
Service Products for Container Shipping Liners. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Creation of Service Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Service Unifier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Finding Service Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Service Product Worklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Service Location Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Service Event Role. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
2.4
Named Account Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Creating Named Account Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
2.5
Commodity Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Creating Commodity Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Content
2.6
Port Zone Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Creating Port Zone Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.7
Transportation Zones Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Classifying Transportation Zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
2.8
Rate Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Rate Table Typed Node Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Creating Rate Tables with Typed Node Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.9
Transportation Charge Calculation Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55
Creating Calculation Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Adding Rate Tables from Rate Table Determination Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Surcharge Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Reference Charge Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.10
Exception Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Creating Exception Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
Editing Exception Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.11
General Rate Increase and General Rate Decrease Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
GRI and GRD Settings for Forwarding Agreement Rate Line Items. . . . . . . . . . . . . . . . . . . . . . . 64
Entering GRI and GRD Settings for Forwarding Agreement Quotation Items. . . . . . . . . . . . . . . . 65
Creating GRI and GRD Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Status Control for GRI and GRD Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Application of GRI and GRD Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
GRI/GRD Worklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Integration with Commodity Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
2.12
Governing Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating Governing Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Publishing Governing Tariffs, Rules, and Subrules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Overview Governing Tariff. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Linking General Rule Sets to Governing Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
Linking Governing Tariffs to Forwarding Agreement Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3
Basic Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
3.1
Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Introduction to Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Preprocessor Report for Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.2
Response Generation and Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
3.3
Data Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Data Aging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Archiving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Blocking and Deletion of Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .138
Change Tracking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170
4
Application Decoupling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Content
PUBLIC
3
5
Tariff Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5.1
Tariff Charge Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
5.2
Classification of Charge Types Used in Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
5.3
Tariff Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Creating Tariff Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Tariff Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
5.4
Creating Rate Tables for Duration-Based Charges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
6
Forwarding Agreement Quotations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
6.1
Forwarding Agreement Quotation Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Forwarding Agreement RFQ Translator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Creation of Forwarding Agreement Quotations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.2
Functions in Forwarding Agreement Quotations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Forwarding Agreement Quotation Header Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Multi-User Enabled Quotations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Request Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Response Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Approving Response Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Status Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232
Duration-Based Charges and Exceptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Conversion of FWAQs to Forwarding Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
6.3
Technical Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
7
Forwarding Agreement Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
7.1
Viewing Rates in Forwarding Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
7.2
Getting of Latest Rates for Agreement Rate Lines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
7.3
Forwarding Agreement Rate Revisions and Renewal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Renewing Forwarding Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245
Revising Forwarding Agreements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
8
L2A SAP Fiori Apps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
8.1
Manage L2A Quotations – CSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
8.2
Manage L2A Agreements – CSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
8.3
Monitor Upcoming Quotation Response Deadline – CSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
8.4
Monitor Upcoming Agreement Renewal – CSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253
8.5
L2A Analysis - CSL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
9
Enhancements to Charge Calculation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
9.1
Charge Automation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
Assigning Maritime Charge Automation Rules to Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Assigning Inland Charge Automation Rules to Tariffs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Charge Automation in Quotations and Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
9.2
4
Other Size Per Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Content
Entering the OSPF Formula in Forwarding Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
OSPF Charge Automation Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Viewing the OSPF Rate Details in the Booking Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
9.3
Equipment Substitution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Maintaining Equipment Substitution Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Determining the Pricing Equipment Type in Bookings with Substituted Equipment. . . . . . . . . . . 276
10
Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
10.1
Charge Calculation in Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Assigning a Customer FWA or Standard Tariff to a Booking. . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Exception Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Rate Construction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Charge Calculation with Proposed Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Multi-Rate Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
11
Regulatory Filing Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
11.1
Basic Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
General Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Data Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
11.2
Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Governing Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
11.3
Tariff Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Set Up of Marine Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Set Up of Arbitrary Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Set Up of Inland Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Tariff Quotations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Uploading Tariff Rate Lines Through API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .336
11.4
Customer Quotations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
11.5
Determination of Filing Relevance of TLI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Determining Filing Relevance in Tariff Quotations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Determining Filing Relevance in Customer Quotations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342
Determining Filing Relevance in Surcharge Rate Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
11.6
Sending of Filing Requests to Queue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Sending of Filing Requests from Tariffs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Sending of Filing Requests from Customer Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352
Sending of Filing Requests from Order to Cash Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Sending of Filing Requests from Legacy System Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
11.7
Processing of Filing Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Querying Filing Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Displaying Filing Request Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Validating Filing Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Getting Charges and Overlaps for Filing Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Content
PUBLIC
5
Getting Duplicates of Filing Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Approving Filing Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .370
Rejecting Filing Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Requesting Approval for Filing Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373
Processing Filing Requests Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
11.8
Publishing Surcharges Through Governing Tariff Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
11.9
Filing at Root Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
11.10
Expiration of Published TLIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Expiring Published TLIs from Tariff Quotations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Expiring Published TLIs from the Tariff Flat View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Expiring Published TLIs from the Tariff Rate Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
12
6
Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Content
1
Introduction to Lead to Agreement
Before you start working with SAP Transportation Management, lead to agreement for container shipping liners
for SAP S/4HANA, we recommend that you familiarize yourself with the following important information.
Working with Web Applications
The SAP Fiori launchpad is the access point for all web-based applications (apps) for the container shipping
liner add-on. Apps are displayed as tiles, and you can launch each app by clicking the corresponding tile on
the launchpad. The tiles displayed on your launchpad home page are arranged into groups, with the group title
displayed at the top of each group.
The set of tiles initially visible to you on the launchpad depends on the business catalogs assigned to the
business roles that your business user is assigned to. The business catalogs and the corresponding tile groups
are delivered as part of the container shipping liners solution.
In the SAP Fiori launchpad frontend system, you can use the /TMCSL/BCR_L2A_ADMIN role as a template,
which contains references to the SAP Fiori tile catalogs or groups that are listed in the following table. This
allows you to access all applications that are relevant for SAP Transportation Management, lead to agreement
for container shipping liners for SAP S/4HANA. We recommend creating your own roles, referencing only the
necessary catalogs required by the various groups of business users.
For more information about creating your own roles, see the section Configuring Your SAP Fiori Launchpad
in the relevant configuration guide for your functional area at https://help.sap.com/tm_csl_l2a_s4hana under
Implement
Configuration .
Business Catalogs
Business Catalog
Technical Name
Reference Technical Catalog
CSL L2A Admin Business Catalog
/TMCSL/BC_L2A_ADMIN
/TMCSL/TC_BE_L2A_APPS
Business Groups
Business Group
Technical Name
CSL Master Data L2A
/TMCSL/BCG_L2A_MD
Displaying Application Help
Most apps in SAP Transportation Management, lead to agreement for container shipping liners for SAP S/
4HANA are Web Dynpro apps. To display context-sensitive application help, select the lower question mark in
the upper right corner and then Help Center. Alternatively, you can press F1 in the app.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Introduction to Lead to Agreement
PUBLIC
7
Displaying Field Help
To view field help in the SAP ABAP system, choose the field and press F1 . To view field help in an app, choose
the field, right-click, and choose More Field Help.
Displaying Quick Help
To view a screen area explanation in an app, right-click anywhere on the screen and choose Display Quick Help.
Described Feature Scope of the Product Assistance
For more information about the features in SAP Transportation Management, lead to agreement for container
shipping liners for SAP S/4HANA, see the feature scope description.
More Information
For more information about the SAP Fiori launchpad, see the SAP Help Portal for SAP S/4HANA at https://
help.sap.com/s4hana_op and choose your version. Under Product Documentation, open the UI Technology
Guide.
For more information about the feature scope for SAP Transportation Management, lead to agreement
for container shipping liners for SAP S/4HANA, see Feature Scope Description for your release at https://
help.sap.com/tm_csl_l2a_s4hana.
Related Information
Master Data [page 9]
Basic Settings [page 81]
Tariff Management [page 173]
Forwarding Agreement Quotations [page 181]
Forwarding Agreement Management [page 243]
Enhancements to Charge Calculation [page 256]
Integration [page 278]
Regulatory Filing Framework [page 287]
8
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Introduction to Lead to Agreement
2
Master Data
Master data represents the business objects used in applications to support transactional processes and
operations.
In addition to the standard Transportation Management (TM) master data objects, the following objects are
part of the SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA
application:
•
•
•
•
•
•
•
•
•
•
•
•
Commodity master
Partner and location profiles
Service product for container shipping liners
Named account groups
Commodity groups
Port zone groups
Transportation zones classification
Rate tables
Transportation charge calculation sheets
Exception templates
General rate increase and decrease rules
Governing tariffs
Related Information
Commodity Master [page 10]
Partner and Location Profiles [page 19]
Service Products for Container Shipping Liners [page 34]
Named Account Groups [page 46]
Commodity Groups [page 47]
Port Zone Groups [page 48]
Transportation Zones Classification [page 50]
Rate Tables [page 52]
Transportation Charge Calculation Sheets [page 55]
Exception Templates [page 61]
General Rate Increase and General Rate Decrease Rules [page 64]
Governing Tariffs [page 71]
For more information about the master data objects in Transportation Management, see the product
assistance for Transportation Management in your SAP S/4HANA release on SAP Help Portal at https://
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
9
help.sap.com/s4hana_op. Open the product assistance and choose
Supply Chain
2.1
Transportation Management (TM)
Enterprise Business Applications
Master Data .
Commodity Master
A commodity master contains all data required for a commodity. A commodity is used to identify the type of
cargo to be moved on behalf of customers. In container shipping liners (CSL) apps, commodities are used in all
key documents such as agreements, bookings, bills of lading, and so on.
Besides general data such as commodity code, description, commodity type, cargo type, International
Maritime Organization (IMO) class, and industry, the commodity master contains administrative data such
as the name of user who created or last changed the commodity data as well as validity information.
Furthermore, it is possible to enter a long description of the commodity, add attachments (such as certificates
or links), and specify output management data.
Related Information
Creating a Commodity Master [page 10]
2.1.1 Creating a Commodity Master
Create a commodity master for cargo that is to be moved on behalf of customers.
Prerequisites
•
The constant value for COMMODITY_CODE_TYPE has been defined in Customizing for Transportation
Management under
•
Container Shipping Liners
Master Data
Classification of Goods
Define Commodity Codes .
The settings for the following Customizing activities have been configured in Customizing for
Transportation Management under
•
•
•
•
•
10
Maintain Configurable Constants .
The commodity code types have been defined in Customizing for Transportation Management under
Transportation Management
•
Basic Settings
Container Shipping Liners
Basic Settings
Commodity Master :
Define Number Ranges for Commodities
Define DnH Code
Define Commodity Code Pattern
Define Commodity Types
Define Industry Code
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
•
•
•
Define IMO Class
Define Cargo Types
Maintain Hierarchy Header
Procedure
1. In your SAP Fiori launchpad, open the Create Commodity Master app.
2. In the General Data section, enter the following commodity code details:
Field
What To Do
Commodity Code
If only an internal number range is defined, then the com­
modity code is generated by the system automatically. If
an external number range is defined, you need to enter
a unique commodity code that matches the commodity
code pattern.
Description
Enter a description for the commodity code.
Commodity Type ID
Select the commodity type, and the system applies the
corresponding validations.
Cargo Type ID
Select the cargo type.
IMO Class
Select the IMO class. This field is mandatory if the com­
modity type ID selected is relevant to dangerous goods.
Industry
Select the industry.
3. In the Administrative Data section, specify the validity period for the commodity code.
4. Save your entries.
Results
The commodity master is created.
Related Information
Commodity Master [page 10]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
11
2.1.2 Harmonized Tariff Schedule
The Harmonized Tariff Schedule (HTS) was developed by the World Customs Organization and comprises
codes that are used to classify and define internationally traded goods.
In most cases, in order to import or export a product internationally, the traded good must be assigned an HTS
code that corresponds with the Harmonized Tariff Schedule of the country of import. In contrast, commodity
codes in the commodity master are more company-specific, but it is possible to link commodity codes to HTS
codes, which may be required in other business processes.
Related Information
Uploading HTS Data [page 12]
Assigning HTS Codes to Commodities [page 13]
2.1.2.1
Uploading HTS Data
Before you can assign Harmonized Tariff Schedule (HTS) codes to commodities in order to categorize them in
accordance with international rules, you first need to upload a Microsoft Excel file containing these codes.
Prerequisites
You have prepared a Microsoft Excel file with HTS codes. You can download the template by choosing Download
Excel Template on the initial screen of the HTS Data Upload application.
Procedure
1. In your SAP Fiori launchpad, open the HTS Data Upload app.
2. In the Import HTS Data step, choose Browse.
3. Select the Microsoft Excel file containing the HTS codes.
4. Choose Upload.
5. Choose Next.
6. Choose Save HTS Data.
12
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Results
The HTS data is uploaded to the system and the HTS codes can be assigned to commodities.
Related Information
Harmonized Tariff Schedule [page 12]
2.1.2.2
Assigning HTS Codes to Commodities
Trade goods that are imported or exported internationally must be assigned a Harmonized Tariff Schedule
(HTS) code that corresponds with the HTS of the country of import. For this reason, you need to assign an HTS
code to the commodity in the commodity master.
Prerequisites
In your SAP Fiori launchpad, the HTS codes have been uploaded to the system using the HTS Data Upload app.
Procedure
1. In your SAP Fiori launchpad, open the Change Commodity Master app, and then open the relevant
commodity.
2. Go to the HTS Tab and choose Insert.
3. Specify the HTS code.
4. Save your entries.
Results
The HTS code is assigned to the commodity.
Related Information
Harmonized Tariff Schedule [page 12]
Uploading HTS Data [page 12]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
13
2.1.3 UN Numbers
UN numbers are four-digit numbers that identify dangerous goods, hazardous substances, and articles (such
as explosives, flammable liquids, toxic substances, and so on) in the framework of international transport.
UN numbers can be assigned for classification of commodity codes that are relevant to dangerous goods
according to international rules.
Related Information
Assigning UN Numbers to Commodities [page 14]
2.1.3.1
Assigning UN Numbers to Commodities
To classify commodities that are relevant to dangerous goods according to international rules, assign UN
numbers to such commodities.
Prerequisites
The dangerous and hazardous (DnH) codes for the commodity have been defined in Customizing for SAP
Transportation Management under
Container Shipping Liners
Basic Settings
Commodity Master
Define
DnH Code
Procedure
1. In your SAP Fiori launchpad, in the Master Data group, open the Change Commodity Master app, and then
open the relevant commodity.
2. Go to the UN Number tab and choose Insert.
3. Specify the UN code.
4. Save the commodity.
Results
The UN number is assigned to the commodity.
14
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Related Information
UN Numbers [page 14]
2.1.4 Adding Commodity Long Descriptions
In the commodity master, enter a long description to describe the relevant commodity in detail.
Prerequisites
The text schema has been defined in Customizing for Cross-Application Components under
Tools for Enterprise Applications
Text Collection
Reusable Objects and Functions for BOPF Environment
Processes and
Dependent Object
Maintain Text Schema .
Context
For example, two different commodities could have the same short description because they are very similar.
In this case, you can add a long description to specify details and differences. Furthermore, you can also add a
long description with a validity in the future (that is, a long description that applies only as of a specific date).
Procedure
1. In your SAP Fiori launchpad, open the Change Commodity Master app, and then open the relevant
commodity.
2. Go to the Long Description tab and choose Insert.
3. Select the text type and language.
4. Enter your content.
5. Specify the validity.
6. Save your description.
Results
The long description is saved in the commodity master.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
15
Related Information
Adding Commodity Long Descriptions [page 15]
2.1.5 Adding Attachments to Commodities
In the commodity master, attach files or links that are relevant to the commodity.
Context
For example, you may want to attach scanned certificates, permissions, and so on. Alternatively, you can also
add links to such documents.
Procedure
1. In your SAP Fiori launchpad, open the Change Commodity Master app, and then open the relevant
commodity.
2. Choose the Attachments tab.
3. Choose Insert File.
 Note
To attach a link, choose
Insert
Link
and enter the URL and a description.
4. Select the attachment type.
5. Enter a description.
6. Choose Next.
7. Browse and select the content.
8. Choose OK.
9. Save the commodity master.
Results
The attachment is saved in the commodity master.
16
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Next Steps
 Note
You can also group attached documents into folders according to business meaning. To do this, choose
Insert
Folder
and move the relevant attachments into the folder.
2.1.6 Commodity Output Management
Output management enables you to print, fax, and e-mail commodity information. You can also execute
application-to-application or business-to-business actions.
Related Information
For more information about the standard Transportation Management functionality for output management,
see the product assistance for Transportation Management in your SAP S/4HANA release on SAP Help
Portal at https://help.sap.com/s4hana_op. Open the product assistance and choose
Applications Supply Chain Transportation Management (TM)
search for Output Management.
Basic Functions
Enterprise Business
Output Management
or
2.1.7 Commodity Hierarchy
A commodity hierarchy allows you to logically group commodities with similar properties in a hierarchical
manner. At each commodity level, the commodities are mutually exclusive.
It also allows you to set parameters not only for one commodity but for all child commodities. For example, if a
validity period is maintained for one commodity, it is updated for all dependent commodities.
Related Information
Maintaining Commodity Hierarchies [page 18]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
17
2.1.7.1
Maintaining Commodity Hierarchies
Maintain a commodity hierarchy to logically group commodities with similar properties.
Prerequisites
The commodity hierarchy settings have been defined in Customizing for Transportation Management under
Container Shipping Liners
Basic Settings
Commodity Master
Maintain Hierarchy Header .
Procedure
1. In your SAP Fiori launchpad, open the Maintain Commodity Hierarchy app.
2. In the hierarchical tree, select the commodity in the tree.
3. Choose Add at Level Below or Add at Same Level.
4. Specify the commodity code.
5. Choose Check for Consistency and Add.
6. Add as many commodities as you wish.
7. You can perform from the following functions when organizing the hierarchy:
Function
Description
Remove
Removes the selected commodity with any underlying
children from the hierarchy
Show Commodity Details
Move
Displays the details for the selected commodity
Moves the selected commodity together with any existing
children to a different location in the hierarchy
Up
Moves the selected commodity together with any existing
children up one level in the hierarchy
Down
Moves the selected commodity together with any existing
children down one level in the hierarchy
8. Save your data.
Results
You have created the commodity hierarchy.
18
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Related Information
Commodity Hierarchy [page 17]
2.1.7.2
Displaying Commodity Hierarchies
Search and display the existing commodity hierarchy.
Procedure
1. In your SAP Fiori launchpad, open the Display Commodity Hierarchy app.
If commodities have been maintained, then the whole commodity hierarchy is displayed.
2. To search for commodities, enter values in one or more of the following fields:
•
•
•
•
Commodity Code
Description
Cargo Type
Cargo Type ID
3. Choose Go.
The commodity hierarchy is displayed.
2.2
Partner and Location Profiles
A partner and location profile (PLP) enables master data objects (such as business partner, location, and
country) in the system to be enhanced with additional attributes.
There are three main types of PLP, which are also referred to as master data (MD) profiles:
•
•
•
Business partner
Location
Country
For each of the above PLP types, there also exists a respective template profile, as listed below:
•
•
•
Business partner template
Location template
Country template
The template profiles are not linked to the real master data object in the system. They can therefore be reused
for creating new MD profiles, thus saving time to enter data all over again.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
19
Related Information
Tabs in Partner and Location Profiles [page 20]
Creating Partner and Location Profiles [page 25]
2.2.1 Tabs in Partner and Location Profiles
A set of tabs is used in a partner and location profile (PLP) to display additional information for the master data
object. Depending on the type of PLP, the set of tabs displayed in the PLP can vary.
The relevance of a particular tab to the corresponding PLP type can be defined in Customizing for
Transportation Management under
Container Shipping Liners
Basic Settings
Partner and Location Profile
Define UI Content Options . The relevance can be specified for each tab even at the level of Business Partner
Party Role Code and Location Type for the Business Partner and Location PLP types accordingly.
Related Information
Content Discrepancies on PLP Tabs [page 20]
2.2.1.1
Content Discrepancies on PLP Tabs
In the partner and location profile (PLP), the content on the various tabs can vary depending on the type of PLP
(Business Partner, Location, and Country) and whether the PLP is a master data (MD) or template profile.
The following table contains an overview of the discrepancies:
Tab
PLP Type
Visible Content Based on PLP Type
General
Template profiles only
Template Description field
MD profiles only
Master Data section
Location with location type Berth
Not applicable
Business partner (MD and template)
E-Signature File Name field
Business partner (MD and template)
Edit Link button
Business partner and location (MD and
Empty Repositioning Approval
template)
Threshold section
Location (MD and template)
Not applicable
Agency
Documentation
20
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Tab
PLP Type
Visible Content Based on PLP Type
Country (MD and template)
Commodity Codes Exempted from
Customs Clearance table
Business partner and country (MD and
DO Generation Rule table
template)
Booking
Business partner (MD only)
Manifest Profile Assignment table
Country (MD and template)
Customs Clearance Required field
Country (MD and template)
Include Prepaid Charges field
Country (MD and template)
Include Collect Charges field
Country (MD and template)
Include DBC Export Charges field
Country (MD and template)
Include DBC Import Charges field
Country (MD and template)
Ignore Discharge Move field
Country (MD and template)
Check only Local Place of Payment field
Business partner (MD and template)
Draft B/L Not Required field
Business partner (MD and template)
Automatic Approval Period (h)
Business partner (MD and template)
Badge Code Provided field
Business partner (MD and template)
Badge Code table
Location with location type Berth
Not applicable
Location and country (MD and tem­
No Show Fee on Booking Cancellation
plate)
table
Business partner and country (MD and
Number Range table
template)
Business partner and country (MD and
Reconfirmation Information section
template)
Location (MD and template)
Allowed as Part-Load Destination field
Location and country (MD and tem­
Dynamic Attributes Profile field
plate)
Country (MD and template)
DBC Auto Rating section
Country (MD and template)
Evaluate Conditions at Receiver field
Country (MD and template)
Default Business Partner Role field
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
21
Tab
PLP Type
Visible Content Based on PLP Type
Business partner and country (MD and
Temperature field
template)
Business partner and country (MD and
Vent Open field
template)
Business partner and country (MD and
Reconfirmation Required field
template)
Business partner and country (MD and
General Information section
template)
Charge Calculation
Business partner (MD and template)
ETA Tolerance Period field
Country (MD and template)
Distribution Profile field
Location with location type Berth
Not applicable
Business partner (MD and template)
General table
Business partner (MD and template)
Place of Payment field
Business partner and location (MD and
Invoicing Data section
template)
Output Management
Location (MD and template)
Authorized Place of Payment field
Business partner and country (MD and
Output Channels table
template)
Business partner (MD and template)
Contact Person for Primary Channel
field
Berth
22
PUBLIC
Business partner (MD and template)
Recipient for Primary Channel field
Business partner (MD and template)
Fax for Primary Channel field
Business partner (MD and template)
E-Mail Address for Primary Channel field
Business partner (MD and template)
Contact Person for Backup field
Business partner (MD and template)
Recipient for Backup Channel field
Business partner (MD and template)
Fax for Backup Channel field
Business partner (MD and template)
E-Mail Address for Backup Channel field
Country (MD and template)
Document/BP Role Assignment table
Location with location type Berth
Berth Draft field
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Tab
Attachment
PLP Type
Visible Content Based on PLP Type
Location with location type Berth
Berth Length field
Business partner, location, and country
Attachment table
(MD and template)
Manifest
Location and country (MD and tem­
Business Partners section
plate) with exception of location type
Berth
Location and country (MD and tem­
Additional Location Characteristics sec­
plate) with exception of location type
tion
Berth
Location and country (MD and tem­
Location Groupings section
plate) with exception of location type
Berth
Location and country (MD and tem­
Short Sea When Coming From section
plate) with exception of location type
Berth
Location and country (MD and tem­
Short/Deep Sea Exceptions section
plate) with exception of location type
Berth
NVOCC
Shipper/Consignee
Business partner and country (MD and
Information and Automation with
template)
Customs section
Business partner (consignee and ship­
Shipper Information section
per functions only) and country (MD
and template)
Business partner (consignee and ship­
Consignee Information section
per functions only) and country (MD
and template)
Business partner (consignee and ship­
Empty Release Order Validity section
per functions only) and country (MD
and template)
Business partner (consignee and ship­
Preferred Vendors section
per functions only) and country (MD
and template)
Business partner (consignee and ship­
Restricted Vendors section
per functions only) and country (MD
and template)
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
23
Tab
PLP Type
Visible Content Based on PLP Type
Storage Capacity
Location and country (MD and tem­
Container Yard Information section
plate) with exception of location type
Berth
Location and country (MD and tem­
Container Storage Capacity section
plate) with exception of location type
Berth
Terminal
Location (MD for location type Terminal Cutoffs section
only), location (Template), and country
(MD and template)
Location (MD for location type Terminal Procured Service Cutoffs section
only), location (Template), and country
(MD and template)
Location (MD for location type Terminal Terminal Characteristics section
only), location (Template), and country
(MD and template)
Location (MD for location type Terminal Documentation section
only), location (Template), and country
(MD and template)
Location (MD for location type Terminal Publish Load/Discharge List section
only), location (Template), and country
(MD and template)
TSP
Business partner (MD) and country
Transport Order Information section
(MD and template)
Business partner (MD) and country
Matchback Information section
(MD and template)
Vessel
Location and country (MD and tem­
Services section
plate) with exception of location type
Berth
Location and country (MD and tem­
Location Details section
plate) with exception of location type
Berth
24
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
2.2.2 Brand-Specific Data in Partner and Location Profiles
A brand is a trade name used by an organization to uniquely identify a maritime freight product or a service.
Certain data in a partner and location profile (PLP) is brand-specific.
Brand-specific information is logically grouped into tables on the user interface where the Brand ID field is
mandatory and a unique parameter. When maintaining this information in a PLP, you can use only those brand
IDs that have been defined in the maintenance view /TMCSL/V_BRAND (using transaction SM30).
2.2.3 Approval-Relevant Fields in Partner and Location
Profiles
Certain fields in a partner and location profile (PLP) must not be changed by nonauthorized users without
additional approval. These fields are referred to as approval-relevant fields (ARFs) and are defined in
Customizing for Transportation Management under
Location Profile
Container Shipping Liners
Basic Settings
Partner and
Define Approval-Relevant Fields .
If the Business Add-In (BAdI) PLP Approval-Relevant Fields is activated, then it is triggered when a
nonauthorized user changes an ARF and saves the change. This BAdI has information about the ARF (such
as old and new values), and is implemented to determine the further workflow.
If the Business Add-In (BAdI) PLP Approval-Relevant Fields is not activated, then it is not triggered when a
nonauthorized user changes an ARF and saves the change. The changed ARF values are subsequently restored
to their old values and a warning message is displayed to state that approval-relevant fields cannot be changed.
When an authorized user changes an ARF and saves the change, the determination and BAdI are skipped and
the change can be saved successfully.
For more information about this BAdI, see the associated Customizing documentation in Customizing for
Transportation Management under
Partner and Location Profile
Container Shipping Liners
Business Add-Ins (BAdIs)
Master Data
BAdI: PLP Approval-Relevant Fields .
2.2.4 Creating Partner and Location Profiles
Create a new partner and location profile (PLP) for a particular master data object.
Prerequisites
In Customizing for Transportation Management under Container Shipping Liners the following activities have
been completed:
•
The number range intervals for PLP have been defined in
Basic Settings
Partner and Location Profile
Define PLP Number Range Intervals .
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
25
•
The PLP types have been assigned to the number range intervals in
Location Profile
Basic Settings
Partner and
Assign PLP Types to Number Range Interval .
Procedure
1. In your SAP Fiori launchpad, open the Create Partner/Location Profile app.
2. On the initial screen, maintain the following details:
•
•
PLP Type: Select the PLP type that you want to use to create a new profile.
•
Template: Select this checkbox if you want to create a template profile. Note: If you select this
checkbox, the previous field for the master data ID is grayed out and not required.
•
Existing Profile: Select an existing MD profile in the system to copy all relevant data from it to the newly
created profile.
•
Profile Template: Select an existing template profile in the system to copy all relevant data from it to the
newly created one.
Master Data ID: This can be the Business Partner, Location, or Country field, depending on the PLP
type selected.
3. Choose Continue.
4. Maintain a description for the profile on the General tab.
5. Save your entries.
Results
You have created the partner and location profile.
Related Information
Changing Partner and Location Profiles [page 27]
Copying Partner and Location Profiles [page 27]
Deactivating Partner and Location Profiles [page 28]
Deleting Partner and Location Profiles [page 30]
Uploading Data to PLP Tables [page 31]
26
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
2.2.5 Changing Partner and Location Profiles
Change an existing partner and location profile (PLP) to update the settings for this profile.
Prerequisites
The PLP that you want to change exists.
Procedure
1. In your SAP Fiori launchpad, open the Change Partner/Location Profile app.
2. Specify the profile ID of the profile you want to change and choose Continue.
3. Change or update the relevant data.
4. Save your changes.
Results
You have updated the relevant partner and location profile.
Related Information
Copying Partner and Location Profiles [page 27]
Deactivating Partner and Location Profiles [page 28]
Deleting Partner and Location Profiles [page 30]
Uploading Data to PLP Tables [page 31]
2.2.6 Copying Partner and Location Profiles
Create a new partner and location profile (PLP) by copying an existing one from the profile's maintenance
screen.
Prerequisites
The PLP to be copied exists in the system.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
27
Procedure
1. In your SAP Fiori launchpad, open the Change Partner/Location Profile app.
2. Specify the profile ID of the profile to be copied and choose Continue.
3. Choose Copy or Copy as Template in the toolbar of the maintenance transaction.
•
•
If you choose Copy, specify a new master data object ID in the dialog box that opens and then confirm.
If you choose Copy as Template, a master data object ID is not required, and you only need to confirm
the dialog box that opens. A new window containing the newly created profile opens.
4. Make any required changes and save your entries.
Results
You have created a new PLP by copying an existing one.
Related Information
Changing Partner and Location Profiles [page 27]
Deactivating Partner and Location Profiles [page 28]
Deleting Partner and Location Profiles [page 30]
Uploading Data to PLP Tables [page 31]
2.2.7 Deactivating Partner and Location Profiles
Deactivate an existing partner and location profile (PLP) if it is no longer relevant. A deactivated profile is no
longer editable and can subsequently be reactivated or deleted.
Prerequisites
The PLP to be deactivated exists in the system.
Procedure
1. In your SAP Fiori launchpad, open the Change Partner/Location Profile app.
2. Specify the profile ID of the profile to be deactivated and choose Continue.
28
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
3. Choose Deactivate in the toolbar of the maintenance transaction.
4. Confirm the dialog box that opens.
Results
You have deactivated the partner and location profile.
Related Information
Reactivating Partner and Location Profiles [page 29]
Deleting Partner and Location Profiles [page 30]
2.2.8 Reactivating Partner and Location Profiles
Reactivate a partner and location profile (PLP) to allow further changes to be made to it.
Prerequisites
The PLP to be reactivated exists in the system and is currently deactivated.
Procedure
1. In your SAP Fiori launchpad, open the Change Partner/Location Profile app.
2. Specify the profile ID of the profile to be reactivated and choose Continue.
3. Choose Reactivate in the toolbar of the maintenance transaction.
4. Confirm the dialog box that opens.
Results
You have reactivated the partner and location profile.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
29
2.2.9 Deleting Partner and Location Profiles
Delete a partner and location profile (PLP) that has been deactivated to completely remove the profile from the
system. Note that the deletion process is not reversible.
Prerequisites
The PLP to be deleted exists in the system and is currently deactivated.
Procedure
1. In your SAP Fiori launchpad, open the Change Partner/Location Profile app.
2. Specify the profile ID of the profile to be deleted and choose Continue.
3. Choose Delete in the toolbar of the maintenance transaction.
4. Confirm the dialog box that opens.
Results
The partner and location profile is completely removed from the system.
2.2.10 Performing Mass Update of Partner Location Profiles
Perform a mass update of partner and location profiles (PLPs) if you need to update profiles with the same
information based on common selection criteria.
Prerequisites
The PLPs to be updated exist in the system.
Procedure
1. Start transaction MASSD in the system.
2. In the Object Type field, select PLP.
30
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
3. Specify the selection criteria for retrieving a target set of PLPs.
 Note
To avoid performance issues, select at least one attribute of the ROOT level.
4. Specify the components and attributes to be maintained or changed.
 Note
The list of attributes available is restricted to a set of change-relevant fields.
5. Choose Select.
6. In the dialog box that opens, choose one of the following options:
•
•
Set Fixed Value if you want to set the same value in the relevant field for all the selected profiles.
Set Values Manually if you want to set different values in the relevant field for all the selected profiles,
and maintain the new values directly in the list
7. Make the necessary changes for the maintainable fields.
8. Save your entries.
Results
The selected PLPs are updated with the newly maintained values.
2.2.11 Uploading Data to PLP Tables
To update an existing partner and location profile (PLP) with external data, upload a CSV file directly into the
PLP. You can do this only for editable tables for which the Upload button appears in the local toolbar.
Prerequisites
•
CSV files with required formats, names, and valid content have been prepared.
 Note
The source files with proper formats and required names can be generated from report /TMCSL/
PLP_BO_DATA_UPLOAD upon selection of the Download Template radio button. You use transaction
SE38 to run the report /TMCSL/PLP_BO_DATA_UPLOAD.
•
The profiles to be updated exist in the system.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
31
Procedure
1. In your SAP Fiori launchpad, open the Change Partner/Location Profile app.
2. Specify the profile ID of the profile to which you want to update data and choose Continue.
3. Find the relevant table for which the Upload button is visible and then choose the button.
4. In the dialog box that opens, select a source file.
5. For adding the data, select the relevant option from the following:
•
Replace Existing Data: Upon choosing this option, the existing information is replaced with the new
data from the source file.
•
Add to Existing Data: Upon choosing this option, the existing information is retained and enriched with
the new data from the source file.
6. Confirm the dialog box.
7. Save your entries.
Results
The data is uploaded from the CSV file into the PLP.
2.2.12 Uploading Mass Data to Partner and Location Profiles
Upload mass data from CSV files into multiple partner and location profiles (PLPs) to replace or enrich the
existing data in these profiles.
Prerequisites
•
CSV files with required formats, names, and valid content have been prepared.
 Note
The source files with proper formats and required names can be generated from report /TMCSL/
PLP_BO_DATA_UPLOAD upon selection of the Download Template radio button.
•
The profiles to be updated exist in the system.
Procedure
1. Start transaction /TMCSL/PLP_UPLD and select a folder directory where all source files are located.
32
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
2. Select the data format used in the files:
•
•
Comma Separated
Semicolon Separated
By default, values in CSV files are separated by a semicolon (;).
3. For adding data, select the relevant radio button for adding data:
•
Replace Existing Data: Upon choosing this option, the existing information is replaced with the new
data from the source file.
•
Add to Existing Data: Upon choosing this option, the existing information is retained and enriched with
the new data from the source file.
4. Execute the report.
Results
The mass data is uploaded from the CSV files into the PLPs.
2.2.13 POWL for Partner and Location Profiles
The Personal Object Worklist (POWL) for the partner and location profile (PLP) can be found in the Partner/
Location Profile Worklist in your SAP Fiori launchpad.
For the ease of working with profiles, the result set of the POWL for PLP inherits all the actions available in the
toolbars on the maintenance screen. The result set is also enriched with useful additional attributes such as
location type, location type description, and so on.
2.2.14 APIs for Partner and Location Profiles
For providing access to partner and location profile (PLP) data, a set of Application Programming Interfaces
(APIs) has been provided within the class /TMCSL/CL_PLP_API. The following table contains a list of the
available APIs.
API
Description
CREATE
Creates new PLPs
READ
Reads existing PLPs
UPDATE
Updates existing PLPs
DELETE
Deletes existing PLPs
COPY
Copies existing PLPs into new master data profiles
COPY AS TEMPLATE
Copies existing PLPs into new template profiles
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
33
API
Description
DEACTIVATE
Deactivates existing PLPs
REACTIVATE
Reactivates existing PLPs
PROFILE_DETERMINATION
Composes a combined profile for the specified consumer
and its business document number
2.3
Service Products for Container Shipping Liners
The service product for container shipping liners (CSL) contains the services of one or multiple sales
organizations. The product manager uses a service product to capture the commercial services that are
made available to the customer. The service product supports stage-relevant catalog types that are defined in
Transportation Management (TM).
The service product for CSL is based on the standard service product catalog solution in Transportation
Management (TM).
 Note
A service product must have at least one sales organization.
You can perform the following tasks for service products:
•
Create service products
You can create service products using the Create Service Product - CSL app or the Service Product Worklist
app.
•
Edit service products
You can edit existing service products in the Edit Service Product - CSL app or in the Service Product
Worklist app.
•
Add services such as the following to the service product:
•
•
•
•
•
•
•
•
•
•
•
34
Insurance
Fumigation
Packing and labelling
Chemical preservation
Document check
Controlled atmosphere service
Container service charge
Security escort
Cargo stuffing
Change the status of a service product
View and search for service products in the Service Product Worklist.
The Service Product Worklist gives an overview of all service products in the system. You can use the
Service Product Worklist to search for service products using different criteria such as sales organization,
service product ID, and status, and to perform various operations on the selected service products.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Related Information
Creation of Service Products [page 35]
Service Product Status [page 39]
Service Product Worklist [page 44]
2.3.1 Creation of Service Products
A service product contains information such as stage relevance, one or more sales organizations, service class,
and usage conditions.
Types of Service Product Catalogs
The system supports the following types of service product catalogs:
•
Inland Origin
A product that can contain services belonging to the inland (pre-carriage) leg of the journey, for example,
fumigation and packing. Such services are planned to be executed on the source inland locations.
•
Marine
A product that can contain services belonging to the ocean (main carriage) leg of the journey, for example,
fumigation, packing, late gate-in, and cargo stuffing. Such services are planned to be executed on the
marine locations.
•
Inland Destination
A product that can contain services belonging to the inland (on-carriage) leg of the journey, for example,
security escort and temperature monitoring. Such services are planned to be executed on the destination
inland locations.
•
Stage Independent
A product that can contain services that are unrelated to their execution locations (stages) or services that
are applicable on events such as booking confirmation, for example, additional bill of lading documents
and document check.
Features
You can perform the following tasks for service products:
•
•
Create new service products.
•
Add notes and attachments on the Attachments tab.
Add value-added services as separate items to the service products.
You can add different services to the service products (for example, fumigation, insurance, or other valueadded services) depending on the product catalog type chosen for creating the product. You can also add
instructions and usage conditions, and you can create a calculation sheet.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
35
•
View administrative data and any changes made to the service product.
You can view when the service product was last saved and by which user on the Administrative Data tab.
•
Generate e-mails and faxes and see a record of documents that were already printed or sent.
On the Output Management tab, you can print, fax, and e-mail service product information. You can also
see a record of the documents that were already printed or sent (by e-mail or fax, for example).
 Note
As of version 2012 of the SAP Transportation Management add-ons for container shipping liners, the
following features are discontinued for the service product for container shipping liners (CSL):
•
•
•
•
•
•
•
Routing and related attributes
Justification
Validity dates
Trade information
Source and destination locations
Brands
Movement types
In previous versions, these attributes were part of the General Data tab and other tabs such as Attributes
and Routes.
Differences to the Standard Functionality
There are differences between the standard product catalog functionality in Transportation Management and
the service product catalog for CSL as follows:
•
General Data
The service product for CSL provides more generic fields such as trade lane, carrier, source of origin
and destination, and movement types. In particular, the following standard fields are not available on the
General Data tab for service products for CSL:
•
•
•
•
•
•
•
Calculation Sheet Template
Archiving Status
Sales Organization
Transportation Mode
Traffic Direction
Items
The service product for CSL is designed only for services, and therefore certain restrictions have been
applied. The creation of an agreement in the add-ons for container shipping liners is done through FWAQ
process.
In particular, the following restrictions apply on the Items tab for service products for CSL:
•
•
•
36
Shipping Type
You can only create items of type Service.
When you create a service product catalog for CSL, by default only one service product record is
created automatically.
The following functions are disabled:
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
•
•
•
Follow Up
Copy
Create Forwarding Agreement Quotation
Related Information
Creating Service Products [page 37]
Service Product Status [page 39]
2.3.1.1
Creating Service Products
Create a service product to capture the value-added services that you offer to customers.
Prerequisites
•
Forwarding agreements (FWAs) and service product catalog types have been defined in Customizing for
Transportation Management under
Master Data
Agreements and Service Products
Define FWA and
Service Product Catalog Types .
•
FWAs and service product item types have been defined in Customizing for Transportation Management
under
•
Master Data
Agreements and Service Products
Event roles for service types have been defined in Customizing for Transportation Management under
Container Shipping Liners
•
Define FWA and Service Product Item Types .
Basic Settings
Service Product
Define Event Roles for Service Types .
Location roles for service types have been defined in Customizing for Transportation Management
under
Container Shipping Liners
Basic Settings
Service Product
Define Location Roles for Service
Types .
•
General settings for catalog types have been defined in Customizing for Transportation Management under
Container Shipping Liners
Basic Settings
Service Product
Define Settings for Service Product
Catalog Types .
 Note
The catalog type chosen for the service product creation must be active.
•
Service types have been defined in Customizing for Transportation Management under
Shipping Liners
Basic Settings
Service Product
Container
Define Service Types for Container Shipping Liners .
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
37
Procedure
1. In your SAP Fiori launchpad, open the Create Service Product - CSL app.
2. Enter the service product catalog type.
The system initially sets the status of the service product to Draft. The stage relevance is set to the
value specified in Customizing for Transportation Management under
Settings
Cargo.
Service Product
Container Shipping Liners
Basic
Define Settings for Service Product Catalog Types . The service class is set to
3. (Optional) On the General Data tab, enter a Service Product ID.
If you leave this field blank, a number is assigned by the system after you save the service product.
4. On the General Data tab, enter the service product description and the sales organization.
 Note
Sales Organization is a mandatory field. If the Multiple Party checkbox is selected for the selected
service product catalog type in the Transportation Management Customizing settings, then a table
appears where you can enter multiple sales organizations. If this flag is not set, then you can only enter
a single sales organization.
5. On the Item tab, choose Insert
following details if required:
Service
to add services to the service product and then enter the
•
(Optional) To define usage conditions for a service, select the Usage Conditions checkbox and then
insert your conditions on the Usages tab.
•
(Optional) Insert any relevant instructions on the Instructions tab.
When you add the services, a calculation sheet is automatically created for the service product. The
calculation sheet contains the charge element corresponding to the service type. You can change the
charge element as well as the other calculation sheet details.
6. (Optional) On the Notes and Attachments tabs, add extra information about the service product in the form
of text files or attached files.
7. (Optional) Set the status of the service product by choosing Set Status.
8. (Optional) Check the consistency of the data in the service product at any time by choosing Check.
The system performs the consistency checks and checks the business rules that are maintained in the
Generic Validation Framework (GVF).
9. Save the service product.
The system performs the consistency checks and checks the business rules that are maintained in the
Generic Validation Framework (GVF). If the checks are passed, the system saves the service product and
assigns an ID to the service product.
Related Information
Creation of Service Products [page 35]
Service Product Status [page 39]
38
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
2.3.1.2
Service Product Status
Service products follow an approval life cycle. The service product status indicates the current life cycle stage
of the service product.
You can view the status of the service product on the General Data tab on the service product screen.
The figure below illustrates the status cycle of a service product:
Service Product Life Cycle
As shown in the figure above, the status life cycle has a specific sequence, which is predefined in the system.
For example, if you want to change the service product status from Rejected to Approved, you must first change
the service product status from Rejected to Ready for Approval. You can then change the service product status
from Ready for Approval to Approved.
Related Information
Changing the Service Product Status [page 39]
Service Product Status Descriptions [page 40]
Creation of Service Products [page 35]
2.3.1.2.1
Changing the Service Product Status
Set the service product status of service products to indicate the current life cycle stage of the service product.
Procedure
1. In your SAP Fiori launchpad, open the Edit Service Product - CSL app, and specify the service product ID.
2. On the Service Product toolbar, choose Set Status.
 Note
Depending on the status of the service product, certain options in the Set Status menu are disabled.
This is to ensure that correct sequence is followed in the service product approval life cycle.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
39
Related Information
Service Product Status [page 39]
Service Product Status Descriptions [page 40]
2.3.1.2.2
Service Product Status Descriptions
The service product status indicates the current life cycle stage of the service product.
The following table describes the different statuses of a service product:
Service Product Status
Description
Draft
This is the initial status for new service products. You can
edit service products in this status. A service product that
has a Draft status can be changed to Ready for Approval or
Canceled.
Ready for Approval
The service product is ready to be approved by the responsi­
ble person. This status can be set only if the service product
data is consistent.
You can edit service products in this status.
A service product that has a Ready for Approval status can
be changed to Approved or Rejected.
Approved
The responsible person sets this status when the service
product has been approved for use in business processes.
You can edit certain fields in service products in this status.
A service product that has an Approved status can be only
changed to Request Discontinuation.
40
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Service Product Status
Description
Rejected
The service product cannot be used in business processes.
You can edit service products in this status. The status of a
rejected service product can be changed back to Ready for
Approval or Canceled.

Example
Consider that you set the status of a service product to
Ready for Approval and ask the responsible manager to
approve it. If the manager does not want to approve the
service product as it is (for example, if some details are
incorrect), then the status can be set to Rejected. This
means that the manager does not want to approve the
service product in its current state, and some changes
are required. Subsequently, you can edit the service
product as needed and change the status from Rejected
to Ready for Approval. You can then ask the manager
again to approve the service product.
Canceled
The service product cannot be used. You cannot edit serv­
ice products in this status. A service product that has a
Canceled status would never have been approved and there­
fore never used in business processes. You might, for exam­
ple, cancel a service product if the data contains an error.

Note
If you set the status to Canceled, the service product is
not deleted from the system, but is obsolete and cannot
be used again.
Request Discontinuation
The service product is not needed for business processes
anymore and the responsible person needs to approve the
discontinuation of the service product. You cannot edit serv­
ice products in this status.
The status of a service product that has a Request
Discontinuation status can be changed back to Approved or
Discontinued.
Discontinued
The service product cannot be used in business processes
anymore. A service product that has a Discontinued status
was previously approved and used in business processes;
however, it is no longer needed for business purposes. You
cannot edit service products in this status.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
41
Related Information
Service Product Status [page 39]
Changing the Service Product Status [page 39]
2.3.2 Service Unifier
The service unifier is a tool that the system executes to identify and deactivate any duplicated or invalid
services. It avoids charges being applied for these duplicated and invalid services.
The service unifier is implemented through the Business Add-In (BAdI) /TMCSL/BADI_SERVICE_UNIFIER.
For more information about this BAdI, see Customizing for Transportation Management under
Shipping Liners
Order to Cash
Business Add-Ins (BAdIs)
Booking
Container
BadI: Enhancement for Service
Unifier .
The service unifier is triggered in the following scenarios:
•
•
When a service item is created or deleted
When the following critical fields are changed:
•
•
•
Service Type
Stage Relevance
Activated Status
A default implementation of the service unifier is provided, which unifies services as follows:
•
Validates the stage relevance.
The service is deactivated if the stage relevance is not supported by the current booking. For example,
in a port-to-port booking, services with the stage relevance Inland Origin and Inland Destination are
deactivated.
•
Deactivates duplicate service types with same stage relevance.
Sometimes, the unifier may deactivate services that are expected. If this happens, you can select the
deactivated service and choose the Activate icon on the Item tab. The system increases the service ranking
and reprocesses the unifier. The selected service is then activated even if another service with same
service type and stage relevance exists.
Related Information
Creation of Service Products [page 35]
42
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
2.3.3 Finding Service Products
Search for service products in a booking based on the booking information and insert the related services into
the booking.
Context
The system uses the booking information as the default criteria for searching for service products. You
can extend the default criteria and query logic using the Business Add-In (BAdI) /TMCSL/BADI_SPF. For
more information about this BAdI, see Customizing for Transportation Management under
Shipping Liners
Order to Cash
Business Add-Ins (BAdIs)
Booking
Container
BAdI: Enhancement for Service
Product Finder .
When a service product is selected and applied, the system performs the following checks:
•
The system checks whether there are existing service products under the container. The same service
product cannot be added to the same container item more than once.
•
•
The system determines the stage relevance based on the service location role.
The service unifier checks for and deactivates any duplicated or invalid services based on the defined logic.
For more detailed information, see the documentation for the service unifier.
Procedure
1. In your SAP Fiori launchpad, open the Change Booking app, and then open the relevant booking.
2. Select the container items to which you want to apply service products.
3. In the Item tab toolbar, choose
Insert
Service from Service Product .
4. In the Search Service Product dialog, enter your selection criteria and choose Search.
5. In the result list, select the service products to be inserted and choose OK.
The selected services along with the service product information are inserted for the selected container
item. The instructions that are maintained for these services in the service product are also added into the
booking instructions.
Related Information
Creation of Service Products [page 35]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
43
2.3.4 Service Product Worklist
The Service Product Worklist for container shipping liners is based on the SAP Personal Object Worklist
(POWL). This means that you can define and store worklists that are defined as queries, and you can configure
the data to be displayed in the worklist.
You can perform the following tasks in the Service Product Worklist:
•
Search for service products
You can use various criteria such as sales organization, created by, created on, service product ID, and
status to search for service products in the system.
 Note
You must specify the sales organization in your search criteria.
•
•
Define queries
•
Maintain selected service products
You can edit, copy, and view a selected service product in the results table using the buttons on the results
table menu. You can also navigate to a service product.
•
Export the worklist to Microsoft Excel.
Create a new service product
You can create a new service product by choosing New on the results table menu.
For more information, see SAP Library for your SAP NetWeaver release on SAP Help Portal at http://
help.sap.com/netweaver. Under
for Personal Worklist.
Application Help
Function Oriented View , open SAP Library and search
Related Information
Creating Service Products [page 37]
2.3.5 Service Location Role
As different services need to be executed at different locations or stages, the service location role is used to
define the relevant service execution locations or stages.
For example, the fumigation service is executed at the port of loading and port of destination and the
temperature monitoring service is executed in the full stages.
The service location role is assigned to a service type in Customizing for Transportation Management under
Container Shipping Liners
Basic Settings
Service Product
Define Service Types for Container Shipping
Liners . It is used to influence the service flow from a booking to the container units and it has an effect on
charge calculation.
The system provides default logic for the service location roles listed in the table below. You can extend the
logic to suit your specific requirements using the class for determining the location role in Customizing for
44
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Transportation Management under
Container Shipping Liners
Basic Settings
Service Product
Define
Location Roles for Service Types .
Location Role
Class
Description
EOM
/TMCSL/CL_LOC_ROLE_EOM
End of Movement
INLD
/TMCSL/CL_LOC_ROLE_INLD
Inland Destination Legs
INLO
/TMCSL/CL_LOC_ROLE_INLO
Inland Original Legs
MAIN
/TMCSL/CL_LOC_ROLE_MAIN
Main Legs
POD
/TMCSL/CL_LOC_ROLE_POD
Port of Discharge
POL
/TMCSL/CL_LOC_ROLE_POL
Port of Loading
SOM
/TMCSL/CL_LOC_ROLE_SOM
Start of Movement
SOS
/TMCSL/CL_LOC_ROLE_SOS
Start of Stage
Related Information
Service Event Role [page 45]
2.3.6 Service Event Role
The service event role is used to define events that trigger service execution. Different services need to be
executed after specific events are triggered, for example, the fumigation service is executed after booking
confirmation.
The service event role is assigned to a service type in Customizing for Transportation Management under
Container Shipping Liners
Basic Settings
Service Product
Define Service Types for Container Shipping
Liners . It is used to influence the service execution.
The system provides default logic for the service event roles listed in the table below. You can extend the logic
to suit your specific requirements using the class to determine the event role in Customizing for Transportation
Management under
Container Shipping Liners
Basic Settings
Service Product
Define Event Roles for
Service Types .
Event Role
Class
Description
BK_CONFIRM
/TMCSL/CL_EVENT_ROLE_BK_CONF
Booking Confirmation
GATE_IN
/TMCSL/CL_EVENT_ROLE_GATEIN
Gate In
Related Information
Service Location Role [page 44]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
45
2.4
Named Account Groups
A named account group represents a set of named accounts, which can be assigned to a request line in a
forwarding agreement quotation.
This enables the carrier to quote a customer with a similar rate for a group of named accounts. Once the
customer approves the proposed rates, the system transfers these quoted rates into agreements. The booking
consumes the rate for a given named account, which is part of the group of named accounts. There can be
multiple versions of a named account group.
A named account group has the following information at the header level:
•
•
•
•
•
ID
Description
Version
Status
Business Partner
In the Item section, you can maintain the list of named accounts.
Related Information
Creating Named Account Groups [page 46]
Additional Actions for Request Lines [page 213]
2.4.1 Creating Named Account Groups
Create a new named account group and approve it so it can be used in a forwarding agreement quotation.
Procedure
1. In your SAP Fiori launchpad, open the Create Named Account Group app.
2. In the Header section, enter the Named Account Group ID, Named Account Group Description, and
Business Party.
The Group Version is defaulted to 1. The default value for the Named Account Group Status is In Process.
You can set the status to Approved, Submit for Approval, or Deprecate (from the Approved status).
3. In the Item section, enter the list of named accounts.
4. Choose
Set Status
Approve
to approve the new named account group.
Only approved named account groups can be used in a forwarding agreement quotation.
46
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
5. Save your entries.
Results
You have created a new named account group and approved it. This named account group can now be used in a
forwarding agreement quotation.
To create a subsequent version of the named account group, choose Create New Version. The data from the
current version is copied to the new version of the named account group.
Related Information
Named Account Groups [page 46]
2.5
Commodity Groups
A commodity group represents a set of commodities, which can be assigned to a request line in a forwarding
agreement quotation.
This enables the carrier to quote a customer with a similar rate for a group of commodities. Once the customer
approves the proposed rates, the system transfers these quoted rates into agreements. The booking consumes
the rate for a given commodity, which is part of the group of commodities. There can be multiple versions of a
commodity group.
A commodity group has the following information at the header level:
•
•
•
•
•
•
ID
Description
Version
Status
Default Commodity Code
Business Partner
In the Item section, you can maintain the list of commodities and mark one of them as default.
Related Information
Creating Commodity Groups [page 48]
Additional Actions for Request Lines [page 213]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
47
2.5.1 Creating Commodity Groups
Create a new commodity group and approve it so it can be used in a forwarding agreement quotation.
Procedure
1. In your SAP Fiori launchpad, open the Create Commodity Group app.
2. In the Header section, enter the Commodity Group ID, Commodity Group Description, and Business Party.
The Group Version is defaulted to 1. The default value for the Commodity Group Status is In Process. The
status can be set to Approved, Submit for Approval, or Deprecate (from the Approved status).
3. In the Item section, enter the list of commodities.
4. Choose Determine Default Commodity.
The system finds the common parent for the commodities in the list. If a common parent cannot be found,
the system defaults to a constant value that is maintained in Customizing for Transportation Management
under
Container Shipping Liners
5. Choose
Set Status
Approve
Basic Settings
Maintain Configurable Constants .
to approve the commodity group.
Only approved commodity groups can be used in a forwarding agreement quotation.
6. Save your entries.
Results
You have created a new commodity group and approved it. This commodity group can now be used in a
forwarding agreement quotation.
To create a subsequent version of the commodity group, choose Create New Version. The data from the current
version will be copied to the new version of the commodity group.
Related Information
Commodity Groups [page 47]
2.6
Port Zone Groups
A port zone group represents a set of port zones, which can be assigned to a request line in a forwarding
agreement quotation, either on the source or the destination side.
This enables the carrier to quote a customer with a similar rate for a group of ports. Once the customer
approves the proposed rates, the system transfers these quoted rates into agreements. The booking consumes
48
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
the rate for a given source or destination location, which is part of the group of port zones. There can be
multiple versions of a port zone group.
A port zone group has the following information at the header level:
•
•
•
•
•
•
ID
Description
Version
Status
Default Transportation Zone
Business Partner
In the Item section, you can maintain the list of transportation zones and mark one of them as default.
Related Information
Creating Port Zone Groups [page 49]
Additional Actions for Request Lines [page 213]
2.6.1 Creating Port Zone Groups
Create a port zone group and approve it so it can be used in a forwarding agreement quotation.
Procedure
1. In your SAP Fiori launchpad, open the Create Port Group app.
2. In the Header section, enter the Port Zone Group ID, Port Zone Group Description, and Business Party.
The Group Version is defaulted to 1. The default value for the Port Zone Group Status is In Process. The
status can be set to Approved, Submit for Approval, or Deprecate (from Approved status).
3. In the Item section, enter the list of transportation zones.
4. Set one of the transportation zones as default.
The Default Transportation Zone field in the Header section is updated.
5. Choose
Set Status
Approve
to approve the port zone group.
Only approved port zone groups can be used in a forwarding agreement quotation.
6. Save your entries.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
49
Results
You have created a new port zone group and approved it. This port zone group can now be used in a forwarding
agreement quotation.
To create a subsequent version of the port zone group, choose Create New Version. The data from the current
version is copied to the new version of the port zone group.
Related Information
Port Zone Groups [page 48]
2.7
Transportation Zones Classification
Transportation zones are groups of locations. In the master data for transportation zones, you can classify
transportation zones according to use.
The following table lists the classifications that you can apply to transportation zones:
Zone
Description
Main business zone
The main business zones are used to define main trades. The main business zone is the highest
level in a zone hierarchy.
Business pricing zone
Pricing zones are used to define pricing trades. These are the intermediate zones in a zone
hierarchy.
City zone
The city zones are the origin and destination transportation zones in pricing rate-table dimen­
sions. The rates are maintained at the city-code zone level in the rate tables. The city zones are
the lowest level in a zone hierarchy.
Transportation zones can be structured as a hierarchy in the transportation zone hierarchy using the
transaction /SAPAPO/RELHSHOW. You must follow a specific structure for the above zone classifications. The
city zones are placed at the lowest level. The next level up is the pricing zones, and the business zones are at
the top of the hierarchy.
50
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
The figure below is an example of the different hierarchical levels in a zone hierarchy:
Transportation Zone Hierarchical Level
Related Information
For more information about the standard Transportation Management functionality for transportation zones
(and transportation zone definition), see the product assistance for your SAP S/4HANA release on SAP Help
Portal at https://help.sap.com/s4hana_op. Open the product assistance and choose
Applications
Supply Chain
Transportation Management (TM)
Master Data
Enterprise Business
Transportation Network
Transportation Zone , or search for Transportation Zone.
Classifying Transportation Zones [page 52]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
51
2.7.1 Classifying Transportation Zones
Classify a transportation zone as a main business zone, a pricing zone, a city zone, or a combination of the
three.
Prerequisites
•
•
Zone master data has been defined using transaction /SCMTMS/ZONE.
The zone hierarchy has been maintained using transaction /SAPAPO/RELHSHOW.
Procedure
1. In your SAP Fiori launchpad, open the Define Transportation Zone app.
2. Use the search field to search for the relevant transportation zone.
3. Select the row with the transportation zone and choose Edit.
4. Classify the zone by specifying X in the Main Business Zone, Business Pricing Zone, and City Code Zone
fields as relevant.
5. Save your entries.
Related Information
Transportation Zones Classification [page 50]
2.8
Rate Tables
A rate table is a grouping of prices for transportation services. The prices (or rates) are listed by validity period
in the rate table.
In SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA, rate
tables are added to calculation sheets in the container shipping liner (CSL) application, which is decoupled
from the standard Transportation Management (TM) application, with the rate table typed storage function.
Related Information
Rate Table Typed Node Storage [page 53]
52
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Creating Rate Tables with Typed Node Storage [page 54]
2.8.1 Rate Table Typed Node Storage
The rate table typed node concept is a feature that allows all the rate table dimensions to be stored in a
flat structure and in readable format rather than in globally unique identifiers (GUIDs). This feature provides
improved performance during data access and charge calculation.
The standard Transportation Management (TM) application has the restriction of allowing only 14 dimensions
in a rate table. This restriction does not apply in SAP Transportation Management, lead to agreement for
container shipping liners for SAP S/4 HANA, and you can therefore add more than 14 dimensions in a rate
table. Furthermore, you can define your own rate table typed nodes with only your required dimensions.
Multiple rate tables can use different rate table typed nodes. Ideally, however, they should use the same
dimensions for rate determination. To achieve better performance, the rate table typed node should have
indexes created as per the general concept of indexes in SAP HANA databases.
 Caution
It is recommended that you do not use very big rate table typed nodes that use only a few dimensions in a
table with non-optimized indexing for different rate lookups.
You should base your decision to split the rate table on the following factors:
•
•
The rate tables that use the rate table typed node should use same dimensions as far as possible.
The dimensions (with indexes) that help database indexes to work faster (that is, a dimension leading to
quick zeroing-in on a specific set of records) should be usable across all the rate tables based on same rate
table typed node.
If a new rate table typed node is introduced, the following steps are required to ensure that it works properly:
•
•
The data structure consists of three parts as follows:
•
•
The rates scales structure must have all the necessary dimensions for business needs.
•
An extension structure can be created and added for extensibility.
The structure /TMCSL/S_RATE_OTHER must be added.
This structure contains technical fields such as administrative data and the linkage to the anchor node
and process node.
For any new calculation base to be added, the corresponding field must be added to the rate table
type node with the same name as the field assignment name used in Customizing for Transportation
Management under
Basic Functions
Charge Calculation
Data Source Binding
Define Calculation
Bases .
The field must be added to the structure /TMCSL/S_FLAT_SCALE_FIELDS as well to make sure it also
works on the user interface (UI).
In addition, the field must be added to structure /TMCSL/S_RATE_READ_ONLY with suffix _FLG to make
sure that the properties of these fields can be properly controlled.
•
All alternative keys as well as the index created in the delivered rate table typed node must also be added to
the new rate table typed node.
•
All the newly introduced rate typed nodes must replace the default implementation class for lock action
with /TMCSL/CL_RATELINE_A_LOCK_V2.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
53
•
All queries created in the delivered rate table typed node must also be added to the new rate table typed
node.
•
All of the following validations and determinations must be added to the new rate table typed node. Ideally,
all the new validation and determination logic can be enhanced to the following ones instead of creating
new ones.
Determination:
•
•
•
•
•
MODIFY_CREATE_UPDATE
MODIFY_DELETE
SAVE_CREATE_UPDATE
SAVE_DELETE
Validation:
•
SAVE_CONS_VAL_RATES_TYPED
Related Information
Creating Rate Tables with Typed Node Storage [page 54]
2.8.2 Creating Rate Tables with Typed Node Storage
Create a new rate table, select the Typed Rate Storage checkbox, and select the Typed Node Name to store the
rates in the rate table typed node instead of the standard scale storage.
Prerequisites
•
Lead to agreement (L2A) rate table types have been maintained in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain L2A Rate Table Types .
•
Rate table typed nodes have been maintained in Customizing for Transportation Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain Rate Table Typed
Node .
Context
 Note
Once the rate table is created and saved, it cannot be changed anymore.
54
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Procedure
1. In your SAP Fiori launchpad, open the Create Rate Table Definition - CSL app.
2. In the initial rate table screen, select the relevant rate table type and choose Continue.
The rate table screen is displayed.
3. In the General Data section, enter the rate table ID and description, and all other necessary information.
4. Select the Typed Rate Storage checkbox and select the predefined rate table typed node in the Typed Node
Name field.
5. Save your entries.
Results
All the rate table entries created in the rate table will be stored in the specified rate table typed node instead of
the standard scale item.
Related Information
Rate Tables [page 52]
Rate Table Typed Node Storage [page 53]
2.9
Transportation Charge Calculation Sheets
Transportation charge calculation sheets (TCCS) are hierarchical tables that the system uses to specify which
transportation charges to calculate and how to calculate them.
The TCCS contains the transportation charge types that are permitted for a document. The Items table in a
TCCS contains the details of the calculation sheet line items, and you can create rate tables for each line item.
In SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA,
TCCS are based on calculation sheets in the standard Transportation Management (TM) application with
enhancements for the following functions:
•
•
•
Surcharge conditions for individual charge types
Reference charge types
Rate tables in rate table determination rule
Integration with Transportation Mangement
For more information about the standard TM functionality for calculation sheets, see the product assistance
for Transportation Management in your SAP S/4HANA release on SAP Help Portal at https://help.sap.com/
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
55
s4hana_op. Open the product assistance and choose
Transportation Management (TM)
Master Data
Enterprise Business Applications
Supply Chain
Charge Management and Service Product Catalog
Setup
of MD for Charge Management and SP Catalogs , or search for Calculation Sheets.
Related Information
Creating Calculation Sheets [page 56]
Adding Rate Tables from Rate Table Determination Rules [page 58]
Surcharge Conditions [page 59]
Reference Charge Types [page 59]
2.9.1 Creating Calculation Sheets
Create a global calculation sheet containing basic ocean freight (OCF) charge items and marine surcharges
items for a marine tariff.
Prerequisites
•
The charge types OCF, OCF Total, and OCF-related surcharges have been defined in Customizing
for Transportation Management under
Basic Functions
Charge Calculation
Basic Settings
Define
Charge Types .
•
The basic ocean freight rate table and marine surcharge rate tables have been created.
Procedure
1. In your SAP Fiori launchpad, open the Create Calculation Sheet - CSL app.
2. Enter a calculation sheet template if you have one, or you can directly choose Continue in the initial
calculation sheet creation screen.
3. Go to the General Data tab, and enter the basic data for the calculation sheet as follows:
56
Field
What To Do
Calculation Sheet ID
Enter your calculation sheet ID.
Description
Enter your calculation sheet description.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Field
What To Do
Charge Usage
Select the charge usage from the dropdown list.
Time Zone
Enter the time zone.
4. Go to the Items tab, add charge items, and maintain the following settings:
Item Hierar­
Instruction
chy
Type
Sum
Sum
> Ocean
Standard
Leading
Reference
Calculation
Calculation
Charge Type
Charge Type
Charge Type
Method Type
Method
OCF
X
-
CSL_CM_RATE
Charges
> Total Ocean
_TYP
X (Reference to
CSL_CM_OCE
Freight
OCF, TAO, and
AN_SUM
Charges
TAD)
> (Any Marine
Standard
Standard
Surcharge)
OCF_Total
(Any Marine
CSL_CM_RATE
Surcharge
_TYP
Type)
> (Any DBC
Standard
Charge)
> Base Origin/
Standard
(Any DBC
2
CSL_CM_DBC
Charge Type)
_CLIPPING
(Any Base Ori­
CSL_CM_RATE
Destination In­
gin/Destina­
_TYP
land Charge
tion Inland
Charge Type)
> Final Origin/
(Final Origin/
X (Reference to
CSL_CM_IN­
Destination In­
Standard
Destination In­
Base)
LAND_SUM
land Charge)
land Charge
Type)
5. Select the basic ocean freight rate charge item and go to the Classification subtab.
6. Check the Statistical Charge field.
7. In the charge item Rate Table field, assign rate tables to the corresponding charge type.
8. If you are using a rate table determination rule for an item in the calculation sheet, then you need to
maintain the same rate tables on the Rate Table Determination Rule tab for this item.
9. Save your entries.
Results
The global calculation sheet for the marine tariff is created.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
57
Related Information
Transportation Charge Calculation Sheets [page 55]
2.9.2 Adding Rate Tables from Rate Table Determination
Rules
Add the rate tables associated with a rate table determination rule to a charge item in a calculation sheet.
Prerequisites
A rate table determination rule is created for the relevant charge type.
Context
This procedure applies when you are using regulatory filing. The rate tables can be viewed in the Flat View. It is
also useful in the case of a tariff with revenue.
Procedure
1. In your SAP Fiori launchpad, open the Edit Calculation Sheet- CSL app, and open the relevant calculation
sheet.
2. Select the charge item in the Items table.
3. In the Rate Table Det. Rule field, enter the relevant rate table determination rule.
4. Choose the Rate Table Determination Rule subtab below the Items table.
5. Choose the Create button and enter the rate tables used in the rate table determination rule.
 Note
The Rate Table Determination Rule subtab is only visible if a rate table determination rule is maintained
for the selected charge type.
6. Save your entries.
Related Information
Transportation Charge Calculation Sheets [page 55]
58
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Regulatory Filing Framework [page 287]
2.9.3 Surcharge Conditions
Surcharge conditions specify the rules for determining the source of the surcharge amount and for calculating
the surcharge amount in the calculation of ocean freight charges.
Surcharge conditions are added to charge types in transportation charge calculation sheets (TCCS). A charge
type can have one of the following surcharge conditions:
Surcharge Condition
Description
Subject To
The surcharge is evaluated from the standard tariff at the time of charge calculation. The
surcharge is used to calculate the overall charge amount.
Subject to Fixed
The surcharge is evaluated from the standard tariff during the quotation process. The calcu­
lated amount is transferred to the forwarding agreement (FWA).
During the charge calculation process in a booking, the system retrieves the existing sur­
charge rate from the FWA instead of from the standard tariff.
Inclusive Of
The surcharge is evaluated from the standard tariff and was already included in the ocean
freight charge during the quotation process.
The surcharge amount is not included in the overall charge amount.
Inclusive of Fixed
The surcharge is negotiated with the customer as part of ocean freight charges during the
quotation process.
The surcharge amount is not included in the overall charge amount.
Related Information
Transportation Charge Calculation Sheets [page 55]
2.9.4 Reference Charge Types
Reference charges, which are charges that are calculated based on another charge type, can be added to
transportation charge calculation sheets (TCCS).
A reference charge type can be based on a particular charge type, for example, an ocean carrier freight (OCF)
charge, and the amount can be fixed or a percentage.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
59
Related Information
Adding Reference Charge Types to a TCCS [page 60]
Transportation Charge Calculation Sheets [page 55]
2.9.4.1
Adding Reference Charge Types to a TCCS
Add one or more reference charge types to a charge item in a transportation charge calculation sheet (TCCS).
Prerequisites
The relevant reference charge type has been defined as a percentage charge type in Customizing for
Transportation Management under
Basic Functions
Charge Calculation
Basic Settings
Define Charge
Types .
Procedure
1. In your SAP Fiori launchpad, open the Edit Calculation Sheet - CSL app, and open the relevant calculation
sheet.
2. Select the charge item in the Items table.
3. Specify the relevant reference charge type in the Charge Type field.
4. Select the Maintain Reference Charge Type checkbox.
5. Choose the Reference Charge Types subtab underneath the Items table.
 Note
The Reference Charge Types subtab is only visible if a reference charge type is selected in the Items
table.
6. Maintain the list of reference charge types for the charge item by adding or deleting charge types in the
Reference Charge Type table.
7. Save your entries.
Results
During charge calculation, the charge for the charge type is calculated based on the values of reference charge
types in the Reference Charge Type table.
60
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Related Information
Transportation Charge Calculation Sheets [page 55]
Reference Charge Types [page 59]
2.10 Exception Templates
An exception template consists of a surcharge rule and a set of charge types that can be applied to single or
multiple rate lines.
The table below lists the surcharge rules that can be assigned to exception templates:
Surcharge Rule
Description
All Inclusive Of
All relevant charge types are included in the leading charge type rate.
All Inclusive Of Except
All relevant charge types except for charge types in the exception list are included in
the leading charge type.
You can create exception templates of the type Surcharge Template. A surcharge exception template consists
of a surcharge rule and a set of charge types. You can use a surcharge exception template to update the
following information for the charge types in rate lines in a forwarding agreement quotation (FWAQ):
•
•
•
•
•
•
•
•
Surcharge conditions
Rate
Currency
Free days information (for duration-based charges)
Place of payment
Settlement terms
Bill-to party
Bill-to party role code
Related Information
Creating Exception Templates [page 62]
Editing Exception Templates [page 63]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
61
2.10.1 Creating Exception Templates
Create a surcharge exception template to specify a surcharge rule and a set of charge types that can be used to
update conditions in rate lines.
Prerequisites
A set of charge types has been defined as surcharges in Customizing for Transportation Management
under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain Charge Type
Definition .
Context
You can use surcharge exception templates to update surcharge conditions in rate lines in forwarding
agreement quotations (FWAQs).
Procedure
1. In your SAP Fiori launchpad, open the Create Exception Template app.
2. In the initial exception template screen, select the template type Surcharge Template and choose Continue.
3. In the main exception template screen, specify the template ID, description, and business partner in the
General Data section.
4. In the Surcharge Rule section, select the relevant surcharge rule.
5. If you select the All Inclusive Of Except surcharge rule, then add the excepted charge types to the Exception
List section.
6. In the Exception List section, enter the following information for each of the charge types:
•
•
Surcharge condition
•
•
Free days information for duration-based charges
Rate (for Subject to Fixed or Inclusive of Fixed charge types provided the surcharge update type is
Surcharge Condition + Rate/Amount)
Payment information
7. Set the template status to Active by choosing the Activate button.
 Note
You must set the status to Active if you want to use the template to update rate lines.
8. Save your entries.
62
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Results
The surcharge exception template can be applied to rate lines in an FWAQ to update the customer requested
surcharge condition and value.
Related Information
Exception Templates [page 61]
2.10.2 Editing Exception Templates
Edit a surcharge exception template to change the status, add exception charge types, delete the template, or
revise the general data.
Prerequisites
A set of charge types has been defined as surcharges in Customizing for Transportation Management
under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain Charge Type
Definition .
Procedure
1. In your SAP Fiori launchpad, open the Change Exception Template app.
2. In the initial exception template screen, specify the template ID and choose Continue.
3. In the main exception template screen, edit the relevant details.
4. Save your entries.
Related Information
Exception Templates [page 61]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
63
2.11
General Rate Increase and General Rate Decrease Rules
A general rate increase (GRI) or a general rate decrease (GRD) is an adjustment applied by carriers to the base
rates for ocean freight.
You can configure GRI and GRD rules to centrally control the ocean freight rates that apply to forwarding
agreements. Once the rules are approved, they can be applied automatically based on their effective dates.
Related Information
GRI and GRD Settings for Forwarding Agreement Rate Line Items [page 64]
Entering GRI and GRD Settings for Forwarding Agreement Quotation Items [page 65]
Creating GRI and GRD Rules [page 66]
Status Control for GRI and GRD Rules [page 68]
Application of GRI and GRD Rules [page 69]
GRI/GRD Worklist [page 70]
Integration with Commodity Hierarchy [page 70]
2.11.1 GRI and GRD Settings for Forwarding Agreement Rate
Line Items
The general rate increase (GRI) and general rate decrease (GRD) settings of forwarding agreements are not
editable. All of the settings are copied from the forwarding agreement quotation. The GRI and GRD settings are
displayed on the Revenue subtab.
Related Information
General Rate Increase and General Rate Decrease Rules [page 64]
Entering GRI and GRD Settings for Forwarding Agreement Quotation Items [page 65]
Creating GRI and GRD Rules [page 66]
64
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
2.11.2 Entering GRI and GRD Settings for Forwarding
Agreement Quotation Items
Enter general rate increase (GRI) and general rate decrease (GRD) information on the GRI/GRD tab of a flat
view item in the Edit Forwarding Agreement Quotation - CSL app.
Context
There is also a Mass Update GRI/GRD function, which is available under the Response Additional button for the
GRI and GRD settings for forwarding agreement quotation (FWAQ) flat view items. The mass update function
allows you to update the GRI and GRD information for multiple flat view items at once.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app, and then open the
relevant FWAQ.
2. Choose Display Flat View.
3. Choose Apply.
4. Select the relevant flat view item.
5. Choose the Revenue tab under the rate line item.
6. On the GRI/GRD subtab, enter the GRI/GRD options as follows:
Options
Values
Description
Subject to GRI
Yes
Enables the GRI rule
No
Disables the GRI rule
Yes
Enables the GRD rule
No
Disables the GRD rule
Blank
Applies for all effective dates in the
Subject to GRD
Effective Date
GRI or GRD rule and when the rule
effective date is within the rate line
validity period
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
65
Options
Values
Description
Exact date
Applies when the entered date is ear­
lier than or on the effective date in the
GRI rule and the rule effective date is
within the rate line validity period
Applies for all the GRD rules when
the rule effective date is within the
rate line validity period, irrespective of
whether the effective date is blank or
exact date
7. Save your entries.
Results
The GRI and GRD information for a response line (type RES) is copied from the tariff agreement when the
FWAQ is getting responses (GRR).
The GRI and GRD information for a response line (type RES) is copied to forwarding agreements (FWAs) when
they are created from the FWAQ.
Related Information
General Rate Increase and General Rate Decrease Rules [page 64]
GRI and GRD Settings for Forwarding Agreement Rate Line Items [page 64]
Creating GRI and GRD Rules [page 66]
2.11.3 Creating GRI and GRD Rules
Create new general rate increase (GRI) and general rate decrease (GRD) rules.
Procedure
1. In your SAP Fiori launchpad, open the Create GRI/GRD Rule app.
2. On the General Data tab, enter the following details:
•
•
66
Rule ID
Description
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
•
•
•
Status
Charge Type
Governing Tariff ID: This is an optional field for filing scenario. It is used to update to the rate line filing
root node.
•
Regulation Type: This is an optional field for filing scenario. It is used to match the rate line filing root
node information.
•
Governing Tariff Rule Number: This is an optional field for filing scenario. It is used to update the rate
line filing root node.
•
Governing Tariff Sub Rule Number: This is an optional field for filing scenario. It is used to update the
rate line filing root node.
•
Sub Rule Version: This is an optional field for filing scenario. It is used to update the rate line filing root
node.
•
•
Effective Date
•
Absolute Value/Percentage Value
Choose either Absolute Value or Percentage Value. If you select Absolute Value, you need to enter an
Amount and a Currency. If you select Percentage Value, you need to enter a Percent.
•
•
Rounding Profile
Increase/Decrease
Choose either Increase or Decrease. The Rule Type field is automatically set to GRI or GRD based on
your selection.
Text Description
Enter the explanatory text to be attached in the rate table GRI/GRD history list.
3. On the Rule Criteria tab, choose Insert and then enter the Attribute Name, Option (Equal or Not Equal To),
and Value.The possible attribute values are as follows:
Attribute Name
Description
Agreement ID
Forwarding agreement ID
Agreement Version
Forwarding agreement version
Equipment
Equipment of rate line
Commodity
Commodity of rate line
Origin Zone
Origin zone of rate line
Destination Zone
Destination zone of rate line
POL
Port of loading (POL) of rate line
POD
Port of discharge (POD) of rate line
DnH Commodity
Dangerous and Hazardous (DnH) com­
Update of Sub Hierarchy (Commod­
ity)
You can select this checkbox to enable
integration with the commodity hier­
archy.
modity of rate line
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
67
4. Save your entries.
Results
The GRI or GRD rule is created. You can later edit the rule you have created by using the Edit GRI/GRD Rule
app.
Next Steps
When you have completed entering the rule, you can submit it for approval by choosing
Set Status
Submit .
Related Information
General Rate Increase and General Rate Decrease Rules [page 64]
GRI and GRD Settings for Forwarding Agreement Rate Line Items [page 64]
Entering GRI and GRD Settings for Forwarding Agreement Quotation Items [page 65]
Integration with Commodity Hierarchy [page 70]
2.11.4 Status Control for GRI and GRD Rules
General rate increase (GRI) and general rate decrease (GRD) rules have a status, which is used to control the
approval of the rules and the application of the rules.
The possible GRI and GRD rule statuses are as follows:
Status No.
Status
Description
00
Draft
The initial status when the rule is first created.
01
Submitted for Ap­
When you have finished entering a rule, you can submit it for approval by choosing
proval
Set Status
Submit
. The system then changes the rule status from Draft to
Submitted for Approval.
02
Approved
The rule has been approved.
03
Rejected
The rule has been rejected.
68
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Status No.
Status
Description
05
Applied
Approved rules can be applied to related rate lines using a report, which can be
scheduled. When the rule has been applied, the system changes the rule status
from Approved to Applied.
06
Canceled
You can cancel a rule by choosing
Set Status
Cancel
. The system then
changes the rule status to Canceled.
07
Pushed Off
You can push-off broadcasted rules by choosing
Set Status
Push Off
.
You can input a later effective date in the Push Off dialog box. When the rule is
successfully pushed off, the system changes the rule status to Pushed Off.
08
Applied with Error
If the rule cannot apply to the agreement due to an error, the system changes the
rule status from Approved to Applied with Error.
The applied with error rule can be applied again after you fix all the errors.
09
Applying in Back­
If the rule is applied from the Fiori UI button Apply Rule and the apply job is
ground Job
running in the background, then the rule status will be Applying in Background Job.
After the job is complete, you can refresh the GRI/GRD rule from the Fiori UI, and
the status will become Applied or Applied with Error.
Related Information
Application of GRI and GRD Rules [page 69]
2.11.5 Application of GRI and GRD Rules
General rate increase (GRI) and general rate decrease (GRD) rules that have been approved can be applied by
running the report /TMCSL/APPLY_GRID_RULES_V2.
You can set up a daily background job to execute and monitor the application of GRI and GRD rules.
To execute the report, you must specify the Effective Date and the Unitization Number. GRA ID is an optional
field, which needs to be specified only when you want to update a rule.
When the report is run, any GRI and GRD rules that have an effective date that matches the one specified in the
report take effect and their status is updated to Applied. The report updates the relevant rate tables as per the
applied GRI and GRD rules.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
69
Related Information
Status Control for GRI and GRD Rules [page 68]
2.11.6 GRI/GRD Worklist
The GRI/GRD Worklist screen provides an overview of all the general rate increase (GRI) and general rate
decrease (GRD) rules in the system.
This worklist is based on the SAP Personal Object Worklist (POWL). This means that you can define and store
worklists that are defined as queries, and you can configure the data to be displayed in the worklist.
To open the GRI/GRD Worklist screen, in SAP NetWeaver Business Client choose
Rules
Master Data
GRI/GRD
GRI/GRD Worklist.
For ease of working with GRI and GRD rules, the result set includes useful details such as Rule Type, Effective
Date, and so on.
Related Information
For more information about POWLS, see SAP Library for your SAP NetWeaver release on SAP Help Portal
at https://help.sap.com/netweaver. Under Application Help, open SAP Library and search for Personal
Worklist.
2.11.7 Integration with Commodity Hierarchy
In a general rate increase (GRI) or a general rate decrease (GRD) rule, you can use the Integration with
Commodity Hierarchy checkbox to enable the automatic update of all the related commodities in the
commodity hierarchy.
The Commodity attribute in a GRI or GRD rule is used to map to a node in the commodity hierarchy.
If you select the Integration with Commodity Hierarchy checkbox, the system applies the rule to all the
commodity's subnode items in the commodity hierarchy. However, if a rule has been set for a lower level
commodity, then that rule has the highest priority.
You implement the integration with the commodity hierarchy as follows:
1. Create the commodity hierarchy master data by choosing
Master Data
Commodity
Maintain
Commodity Hierarchy.
2. Select the Integration with Commodity Hierarchy checkbox for the specific GRI/GRD rule by choosing
Master Data
70
PUBLIC
GRI/GRD Rules
Edit GRI/GRD Rule.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Related Information
Creating GRI and GRD Rules [page 66]
2.12 Governing Tariffs
The governing tariff is used to store the rules used in the charge calculation process. These rules can be linked
to a calculation sheet in a forwarding agreement tariff.
Overview
The governing tariff rules and subrules are grouped by sales organization and charge type. However, some rules
can be defined globally with specific conditions, and therefore a special type of governing tariff called a general
rule set is provided for defining these global rules. In a general rule set, the sales organization is optional. You
can link a general rule set to a governing tariff.
The following types of rules can be defined:
•
•
•
•
General clauses for service contracts
Inland conditions and surcharges
Conditions and surcharges for duration-based charges (DBC)
Bill of lading (B/L) conditions and surcharges
Governing Tariff Screen
The governing tariff screen contains the following sections:
•
General Data
This tab contains details such as the governing tariff ID, the governing tariff type, the status, and the
validity period.
•
Rules
This section contains the following tabs:
•
•
Rules
On this tab, you define the rules for the governing tariff.
•
Overview Linked General Rule Set/Governing Tariff
On this tab, you can view a summary of all the linked general rule sets or governing tariffs.
•
Linked Tariff
On this tab, you can view the linked forwarding agreement tariffs.
Subrules
When you select a rule, the Tariff Subrules subtab and the Text subtab are displayed. You can use the Text
subtab to maintain the text for the rule.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
71
•
Rule Text and Attachments
When you select a subrule, the Rule Text For subtab and the Attachments subtab are displayed. You can use
the Rule Text For subtab to maintain the text for the subrule. You can use the Attachments tab to specify
document links.
Related Information
Creating Governing Tariffs [page 72]
Governing Tariff Maintenance [page 74]
Publishing Governing Tariffs, Rules, and Subrules [page 74]
Overview Governing Tariff [page 76]
Linking General Rule Sets to Governing Tariffs [page 77]
Linking Governing Tariffs to Forwarding Agreement Tariffs [page 78]
Viewing the Linked Governing Tariff Rules and Subrules in FWAs [page 79]
2.12.1 Creating Governing Tariffs
Create a new governing tariff using the Create Governing Tariff app.
Context
You can create a governing tariff in the following ways:
•
•
By manually entering all of the details
By opening an existing governing tariff and choosing Copy
When you copy an existing governing tariff, the system creates a new governing tariff and copies all of the
data from the original one, with the exception of the following fields:
•
•
•
•
•
Governing Tariff Type
Publish Date
Status (set to Pending)
Governing Tariff ID
Amendment Code (set to I)
Procedure
1. In your SAP Fiori launchpad, open the Create Governing Tariff app.
The system displays the initial screen for creating a new governing tariff.
72
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
2. Select the governing tariff type (Governing Tariff or General Rule Set), and then choose Continue.
3. On the General Data tab, enter the following mandatory fields:
•
•
•
•
Governing Tariff ID
Sales Organization (optional for a general rule set)
Valid-From Date
Valid-To Date
4. (Optional): On the Rules subtab, choose Insert to insert a new rule, and then enter the following mandatory
fields:
•
•
•
Rule Number
Valid-From Date
Valid-To Date
5. (Optional): Enter the remaining rule fields as required.
6. (Optional): To enter text for rule, select the relevant rule, and then enter the text on the Text subtab.
7. (Optional): To insert a subrule, select the relevant rule, choose Insert on the Tariff Subrule subtab, and then
enter the required details.
8. (Optional): To add an attachment, select the relevant subrule and then choose one or more of the following
options on the Attachments subtab:
•
•
•
Insert
Folder
Insert
File
Insert
URL
9. Save the governing tariff.
Next Steps
Publish the governing tariff when it is ready for use.
Related Information
Governing Tariffs [page 71]
Governing Tariff Maintenance [page 74]
Publishing Governing Tariffs, Rules, and Subrules [page 74]
Overview Governing Tariff [page 76]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
73
2.12.1.1 Governing Tariff Maintenance
Various maintenance options are available for rules and subrules in the Governing Tariff screen.
You can perform the following actions for rules and subrules that have the status Pending:
•
•
•
•
Insert
•
Publish
Edit
Delete
Copy
When you copy a rule, the subrules that belong to the rule are also copied. All of the data is copied except
for the amendment code and status. The amendment code is set to I, and the status is set to Pending.
If the status of a rule or subrule is Published or Withdrawn, then you can only perform the copy action.
If there are multiple active rules or subrules that are the same (that is, they have the same carrier, governing
tariff ID, rule ID or subrule ID, validity period, and so on), only one of them can be processed normally by the
system. The remaining duplicate rules are automatically set to the status Withdrawn and cannot be edited any
more when you publish them.
Related Information
Governing Tariffs [page 71]
Creating Governing Tariffs [page 72]
Overview Governing Tariff [page 76]
2.12.2 Publishing Governing Tariffs, Rules, and Subrules
Publish a governing tariff, rule, or subrule so that the rules of the tariff can be applied.
Prerequisites
There is an existing governing tariff and it has not been published.
Context
You can use the Publish button to change the status of a governing tariff, rule, or subrule when the rules are
accepted and ready to be applied.
74
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
You can perform the publication process at three different levels as follows:
•
•
•
Tariff
Rule
Subrule
 Note
You can only publish a rule when the related governing tariff has been published, and you can only publish a
subrule when the related rule has been published.
There are two ways to perform the publication process:
•
In the Change Governing Tariff app
This app has a Publish button at each different level.
•
In the Overview Governing Tariff app
This app has a single Publish button and the system automatically determines the relevant level based on
the selected data.
When the governing tariff, rules, and subrules are published, you can no longer update them and the rules and
subrules cannot be deleted. However, you can add new rules and subrules to a published governing tariff.
Procedure
1. In your SAP Fiori launchpad, open the Change Governing Tariff app, and then open the relevant governing
tariff.
2. Choose the relevant option as follows:
Option
To publish the entire governing tar­
iff, choose Publish in the header
toolbar.
Result
•
If the Valid-From Date is before the current date, it is adjusted to the
current date.
•
If the Valid-To Date is before the current date, an error message is dis­
played.
•
When the governing tariff is successfully published, the status of the gov­
erning tariff is updated to Published, and all of the rules and subrules are
also published.
To publish a rule, select the rule on
the Rule subtab, and then choose
Publish in the toolbar of the Rule
subtab.
•
If the Valid-From Date is before the current date, it is adjusted to the
current date, and the status of the rule is set to Published.
•
If the Valid-From Date is after or the same as the current date, the status
of the rule is set to Published.
•
If the Valid-To Date is before the current date, the status of the rule is set
to Withdrawn.
To publish a subrule, select the sub­
rule on the Tariff Subrule subtab, and
•
If the Valid-From Date is before the current date, it is adjusted to current
date, and the status of the subrule is set to Published.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
75
Option
Result
then choose Publish in the toolbar of
the Tariff Subrule subtab.
•
If the Valid-From Date is after or the same as the current date, the status
of the subrule is set to Published.
•
If the Valid-To Date is before the current date, the status of the subrule is
set to Withdrawn.
3. Save the governing tariff.
Results
•
The status of the governing tariff, rules, and subrules that you have published are either Published or
Withdrawn.
•
The published data can no longer be edited. However, you can add new rules and subrules.
Related Information
Governing Tariffs [page 71]
Creating Governing Tariffs [page 72]
Governing Tariff Maintenance [page 74]
2.12.3 Overview Governing Tariff
The Overview Governing Tariff screen is a worklist that provides an overview of all the governing tariffs in the
system.
The worklist is based on the SAP Personal Object Worklist (POWL). This means that you can define and store
worklists that are defined as queries, and you can configure the data to be displayed in the worklist.
To open the Overview Governing Tariff screen, in SAP NetWeaver Business Client, choose
Governing Tariff
Master Data
Overview Governing Tariff .
You can perform the following tasks in the Overview Governing Tariff screen:
•
•
•
Edit a governing tariff
Publish a governing tariff
Export the worklist to Microsoft Excel
Related Information
Governing Tariffs [page 71]
76
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
For more information about POWLS, see SAP Library for your SAP NetWeaver release on SAP Help Portal at
https://help.sap.com/netweaver. Under
search for Personal Worklist.
Application Help
Function Oriented View,
open SAP Library and
2.12.4 Linking General Rule Sets to Governing Tariffs
Link a published general rule set to a governing tariff rule so that some of the rules or subrules in the general
rule set can be used in the governing tariff.
Prerequisites
•
•
There is an existing governing tariff that contains an unpublished rule.
There is a published general rule set.
Context
If a general rule set exists and has at least one rule or subrule with a charge type that is equal to the target
governing tariff rule, then the general rule set can be linked to the target governing tariff rule.
A governing tariff rule can only be linked to one general rule set. A general rule set can be linked to several
governing tariffs.
Procedure
1. In your SAP Fiori launchpad, open the Change Governing Tariff app, and then open the relevant governing
tariff.
2. On the General Data tab on the Rules subtab, select the rule that you want to link to the general rule set.
3. On the Text subtab, specify the target general rule set.
4. Save the governing tariff.
Results
•
The linked general rule set ID is displayed in target governing tariff on the Overview Linked General Rule Set
tab.
•
The linked governing tariff ID is displayed in the target General Rule Set on the Overview Linked Governing
Tariff tab.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
77
•
If you add this governing tariff to a forwarding agreement, the rules and subrules in the general rule set are
included as if they are part of the governing tariff.
Related Information
Creating Governing Tariffs [page 72]
Viewing the Linked Governing Tariff Rules and Subrules in FWAs [page 79]
2.12.5 Linking Governing Tariffs to Forwarding Agreement
Tariffs
Link a published governing tariff to a forwarding agreement of type tariff so that the terms and conditions from
the governing tariff are associated to the trade tariff structure.
Prerequisites
•
•
There is an existing forwarding agreement of type tariff.
There is an existing published governing tariff.
Context
Only published governing tariffs can be linked to forwarding agreement tariffs. In addition, the sales
organization in the governing tariff and the forwarding agreement should be the same.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement app, and then open the relevant
forwarding agreement tariff.
2. On the Governing Tariff tab, choose Insert and enter details of the governing tariff that you want to link to
the forwarding agreement.
3. Save the forwarding agreement.
78
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
Results
The linked governing tariff ID is displayed on the Governing Tariff tab in the forwarding agreement.
Related Information
Viewing the Linked Governing Tariff Rules and Subrules in FWAs [page 79]
2.12.5.1 Viewing the Linked Governing Tariff Rules and
Subrules in FWAs
View the linked governing tariff rules and subrules in a forwarding agreement tariff by displaying the calculation
sheet.
Prerequisites
•
•
There is an existing forwarding agreement tariff with an item that contains a calculation sheet.
There is an existing published governing tariff.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement app, and then open the forwarding
agreement tariff.
2. On the Governing Tariff tab, choose Insert and enter the details of the governing tariff that you want to link
to the forwarding agreement.
3. Save the forwarding agreement.
4. On the Items tab of the forwarding agreement, select the relevant item and choose Display Calculation
Sheet.
5. On the Items tab of the calculation sheet, select one of the charges and choose the Linked Rule/Subrule
tab.
The rules and subrules in the linked governing tariff or in the general rule set that is linked to the governing
tariff are displayed on this tab according to the charge type.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
PUBLIC
79
Related Information
Linking Governing Tariffs to Forwarding Agreement Tariffs [page 78]
80
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Master Data
3
Basic Settings
Certain basic settings are required in SAP Transportation Management, lead to agreement for container
shipping liners for SAP S/4HANA.
The routing process is used to determine possible routes between a source and a destination location. Routing
is integrated with several lead to agreement applications such as product catalog and forwarding agreement
quotation (FWAQ).
In addition, business partner data that is no longer required or used can be blocked and deleted to comply with
data privacy and protection regulations. Business partner data that is still in use cannot be deleted. To help
you determine whether business partners are still in use, corresponding end-of-purpose checks are provided
as part of the product.
Related Information
Routing [page 81]
3.1
Routing
Routing is the process of determining possible routes between a source and destination location.
The following table lists which application area is integrated with routing in each of the container shipping liners
add-ons:
Product
Integrated Applications
SAP Transportation Management, network and operations
for container shipping liners for SAP S/4HANA
Trip plan replanning
SAP Transportation Management, order to cash for con­
tainer shipping liners for SAP S/4HANA
Booking
SAP Transportation Management, lead to agreement for
container shipping liners for SAP S/4HANA
Forwarding agreement quotation (FWAQ)
More Information
For more information about routing for trip plan replanning see the product assistance for SAP Transportation
Management, network and operations for container shipping liners for SAP S/4HANA on SAP Help Portal
at https://help.sap.com/tm_csl_nao_s4hana. Open the Product Assistance and choose
Routing
Basic Settings
Routing for Trip Plan Replanning .
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
81
For more information about routing for booking see the product assistance for SAP Transportation
Management, order to cash for container shipping liners for SAP S/4HANA on SAP Help Portal at https://
help.sap.com/tm_csl_o2c_s4hana. Open the Product Assistance and choose
Basic Settings
Routing
Routing for Booking .
Related Information
Introduction to Routing [page 82]
Preprocessor Report for Routing [page 88]
3.1.1 Introduction to Routing
The routing solution is based on the k-shortest/Dijkstra algorithm. The main goal of the design is the
implementation of a performance-optimized routing solution.
Routing master data is generated using a preprocessor to fill shared memory and the SAP HANA database. The
co-efficient is the basis of the calculation of the edge score, which is used by the algorithms to get the best
possible route.
On a high-level, the optimized performance is achieved with the following main design features:
Performance Aspect
Flexible Frameworks
k-shortest/Dijkstra Algorithm Based Routing Solution
Use of a static route check to minimize the runtime overhead
spent in the generic frameworks and Business Object Proc­
essing Framework (BOPF) integration (Data Crawler).
Coding Approach
Spaghetti coding in the API to minimize the runtime over­
head spent in the technical mass call of methods and func­
tions during iterations in the algorithm.
Route Finding Approach
Creation of only the best routes purely based on a precom­
puted graph and edge score information.
Runtime Calculation
Mass precomputation of all individual graph edge attributes
including preparation of constrained edges and all the inland
connection options as virtual graph edges.
In-Memory Approach
Mass use of in-memory storage, partially based shared
memory (algorithm core-related information), and SAP
HANA database (code push down approach using ABAP
Managed Database Procedures (AMDP) and Core Data Serv­
ices (CDS) views).
•
82
Network Data Generation Using Preprocessor
All routing data is precomputed by the network preprocessor based on the routing-relevant Transportation
Management (TM) and container shipping liners master data and under consideration of the business
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
logic, for example, the carbon emission calculation. The precomputation results are written to the
preprocessing network database. The precomputation needs to be efficient to always provide the actual
routing data in the maximum acceptable latency.
•
Preprocessing Network Database
In the preprocessing network database, all precomputed data is stored in routing algorithm optimized
structures. The preprocessing network database serves as a staging area and is the basis for the upload
into shared memory and can be used for accelerated error analysis.
•
Shared Memory Uploader and Shared Memory Storage
The upload of routing graph or edge data into shared memory only includes data that is essential
to achieve an efficient runtime. The routing algorithm then refers back to the SAP HANA database
for an efficient lookup of any additional route information that is required for the final routing results
presentation.
•
Routing API
The routing API report (/TMCSL/ROUTING_API) can be used to test routing scenarios individually.
•
Routing Computation
The routing computation algorithm is based on shared memory storage.
•
Static Route Check and Static Ranking Business Add-Ins (BAdIs)
The static call of a Business Rule Framework plus (BRFplus) function or ABAP class on fully computed
routes is done through BAdIs.
Related Information
Master Data [page 83]
Example: Routes, Transshipments, and Drayage Moves [page 85]
Routing Integration [page 86]
Dijkstra Shortest Path for Routing [page 86]
3.1.1.1
Master Data
This section describes the network master data that is used for generating routes.
Locations
You use this object type as the basis for transportation processes. In transportation processes, you name
a source location, a destination location, and any transshipment locations necessary to complete the
transportation process. For example, you can define City, Port, Terminal, Ramp, and Hub.
Locations are created for certain movement types and should match the right location types. For example, a
location created to test the Door movement type must have location type 1021 or 9100.
The routing application programming interface (API) uses the following location types:
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
83
Location Type
Description
1021
Business Partner
1030
Terminal
1100
Port
9040
Ramp
9050
Inland Hub
9100
City
 Note
The routing solution supports the movement types Port, Door, and Ramp, and connections that are formed
by the combinations between them.
You can create the locations as follows:
•
•
Using transaction code /SCMTMS/LOC3
Using the Define Location app
Transportation Zones
A transportation zone is comprised of a group of locations. Transportation zones are part of Transportation
Management (TM) master data and are utilized in SAP Transportation Management add-ons for container
shipping liners for SAP S/4HANA. You assign locations such as business partners, ramps, and terminals to the
transportation zone either directly by entering the location name or through city, region and zip code.
Transportation zones can be excluded by deselecting the Routing Relevant checkbox in the definition.
You define a transportation zone in SAP NetWeaver Business Client by choosing
Management
Master Data
Transportation Network
Logistics
Transportation
Define Transportation Zone .
In routing for forwarding agreement quotation (FWAQ), the preferred zones can be passed to the routing
engine if a location is part of multiple zones. Based on the source and destination location passed to the routing
engine, the respective zone is determined internally and is used to find the intermodal stages of the route.
Transportation Lanes
Routing uses the TM transportation lanes for intermodal connections. For more information about TM
transportation lanes, see the product assistance for Transportation Management in SAP S/4HANA on SAP
Help Portal at https://help.sap.com/s4hana_op. Open the product assistance, choose
Applications Supply Chain Delivery and Transportation
for Transportation Lane.
84
PUBLIC
Enterprise Business
Transportation Management (TM) , and search
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Default Routes
Routing uses the TM default route object for intermodal connections. For more information about the TM
default route, see the product assistance for Transportation Management in SAP S/4HANA on SAP Help Portal
at https://help.sap.com/s4hana_op. Open the product assistance, choose
Supply Chain
Route.
Delivery and Transportation
Enterprise Business Applications
Transportation Management (TM) , and search for Default
Schedules
Routing supports the TM ocean and rail schedules for ocean and intermodal connections. For more information
about TM schedules, see the product assistance for Transportation Management in SAP S/4HANA on SAP
Help Portal at https://help.sap.com/s4hana_op. Open the product assistance, choose
Applications Supply Chain
for Schedule.
Delivery and Transportation
Enterprise Business
Transportation Management (TM) , and search
Container Shipping Liner (CSL) Schedules
If SAP Transportation Management, network and operations for container shipping liners for SAP S/4HANA is
installed, routing supports the schedules (voyages) generated from line maintenance.
Related Information
Introduction to Routing [page 82]
3.1.1.2
Example: Routes, Transshipments, and Drayage
Moves
Transshipments and drayage moves are considered during the routing process.
Transshipments
Routes consist of a sequence of stages, where each stage is an independently operated transportation service.
The transition between stages is called transshipment. If you need to transport goods from origin location A to
destination location D, for example, the proposed routes could appear in a number of different permutations
such as follows:
•
A
B
C
D .
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
85
•
•
•
A
B
A
D .
A
B
D .
F
D .
In the above example, the intermediate locations between the origin location A and the destination location D
(B, C, and F) are the transshipment locations.
Drayage Moves
Drayage refers to the transport of cargo over a short distance to facilitate the transshipment, for example, from
one terminal to another terminal within a port.
In the sequence A B' B" C D , for example, B' and B" are different terminals of the same port, B.
These short-distance transshipments are called drayage moves.
3.1.1.3
Routing Integration
Routing is integrated with the forwarding agreement quotation (FWAQ) application area.
If you have installed SAP Transportation Management, order to cash for container shipping liners for SAP
S/4HANA, the route generator is also integrated with the booking process. When you create a booking, you
can generate route proposals for a combination of source and destination location. For bookings in the order to
cash functionality, the route generator is called by the Voyage Suggestion Framework (VSF).
If you have installed SAP Transportation Management,network and operations for container shipping liners
for SAP S/4HANA, the route generator is also integrated with the trip plan replanning process. The route
generator uses the enhanced schedules from Schedule Management to find route proposals.
Related Information
Routing [page 81]
3.1.1.4
Dijkstra Shortest Path for Routing
The Dijkstra shortest path is an algorithm that is used in the routing process to determine connections
between a source location and a destination location.
The Dijkstra determines paths, routes, and reachability within the transportation network between a
source and destination location. While doing so, it takes into account defined transshipment locations and
connections such as schedules, bookings, and transportation lanes. You can call the Dijkstra for each routing
strategy during the route determination process. The logic works as follows:
1. The Dijkstra takes the objects that make up the route from the network.
These consist of standard or maritime line schedules, such as intermodal or feeder schedules, and
transportation lanes for any of the modes of transport for inland transportation such as train, truck,
barge, or non-scheduled feeder legs. Only the scheduled services and lines are restrictive in time frames,
86
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
since they are planned for specific weekdays and have cut-off times for cargo and documentation. These
network objects deliver the durations and distances as input for the time calculation logic.
2. The Dijkstra takes into consideration any restrictions related to opening times and non-working days
for the locations.
3. The Dijkstra performs an iterative search that determines all of the next possible connections from
one location origin.
From each of the connecting locations found, it starts a new search for all possible connections until
the destination location is found or the specified search depth is reached. In addition, with each of the
searches, it determines the durations between the found connections, to determine if a timely connection
is possible. To do this, it uses undated routing information from the proforma schedule as specified in the
cycle plan definition of the line.
4. The Dijkstra adjusts for the schedule milestones.
The connections based on transportation lanes are more flexible, and only deliver duration and distance
in relation to means of transport. Therefore, the Dijkstra can shift these lanes connected to and from a
schedule to fit to the schedule milestones.
Related Information
Routing [page 81]
Routing Integration [page 86]
3.1.1.5
Network Visibility
For an enterprise with multiple companies, the network may not be transparent for all companies. To manage
network visibility, you can select a suitable option based on your business.
As an ocean liner product, container shipping liners (CSL) manages the network visibility based on the
Schedule Management (SDM) lines. For other network data such as transportation lane, default route, or
standard schedule, it's transparent in the system.
To manage the SDM lines' visibility, CSL provides two options: one based on lines in own company, and the
other based on assignment. You can set your required option using the Get Line from Assignment in Routing
checkbox in Customizing for Transportation Management under
Container Shipping Liners
Basic Settings
Define General Settings for Planning .
You can make the settings based on the following details:
•
The Lines in Own Company setting is activated when the Get Line from Assignment in Routing checkbox
is either not visible in Customizing or is not selected. If the checkbox is selected, the routing engine will
query the route proposal based on all lines in the current company. If you want to consume the lines in
different companies (in the same system), you can achieve it via sub-lines. Additionally, if multiple Planning
and Execution (P&E) organizations exist in the company, only the lines in the first P&E organization will be
considered as valid lines.
•
and SAP Note 3096539 . You can
The Assignment option has been introduced via SAP Note 3234472
activate the setting by selecting the Get Line from Assignment in Routing checkbox. Furthermore, you can
define the lines’ visibility for sales organization using the transaction /TMCSL/SORGROUT. For more details,
see SAP Note 3234472
.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
87
3.1.1.6
Routing Movement Type Mapping
A mapping table is provided for mapping the actual predefined movement type to one of the Routing
movement types. This enables the Routing API to find proposals with the mapped movement type instead
of the actual movement type.
You maintain the mapping between movement types in Customizing for Transportation Management under
Container Shipping Liners Network and Operations Routing Assign Routing Movement Types . You
can select one of the following routing-supported movement types and map it with one of the actual movement
types::
•
•
•
•
•
•
•
•
•
DD (Door to Door)
DP (Door to Port)
DR (Door to Ramp)
PD (Port to Door)
PP (Port to Port)
PR (Port to Ramp)
RD (Ramp to Door)
RP (Ramp to Port)
RR (Ramp to Ramp)
As a result:
•
If the mapping for the actual movement type exists, then the mapped routing-supported movement type is
used to find proposals from the Routing API.
•
If the mapping for the actual movement type does not exist, then the actual movement type is used to find
proposals from the Routing API.
3.1.2 Preprocessor Report for Routing
The preprocessor report (/TMCSL/TN_DB_PROCESSOR) is used to create routing master data based on lines,
schedules, and trade lanes created in the system. The preprocessor report is a prerequisite for routing. The
report must be run before running the routing solution.
You can use the preprocessor report to create master data for routing based on a specific line ID and schedule
ID, or you can create master data for all lines and schedules in the system.
You can delete specific inactive versions by using the search help to select the relevant version or
delete all inactive versions by entering a wildcard (*) in the relevant field. This operation is controlled
by an authorization check for model IDs that are marked as protected in Customizing for Transportation
Management under
Container Shipping Liners
Basic Settings
Routing
Maintain Routing Models and
Horizon Configuration .
If the current active version contains corrupt routing master data, you can reactivate an inactive version. You
can choose the inactive version using F4 .
The preprocessor report is a background process that is run by the background job scheduler. You can
schedule the report to run periodically based on your requirements.
The preprocessor report has the following predefined variants, which have been configured for Model 000:
88
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
•
•
•
/DEL_ALL: This variant deletes the root cache, location cache, and graph tables for Model 000.
/ROT_BLD: This variant builds the location cache and root cache for Model 000.
/GPH_BLD: This variant builds the graph cache for Model 000.
Job Scheduler for Preprocessor Report
The report is run through the background job scheduler. You define the background job for the report using
transaction SM36.
 Note
When you schedule the background job for the report, you must add the variants in the following sequence:
1. /DEL_ALL
2. /ROT_BLD
3. /GPH_BLD
Configuration of New Model IDs for Routing
If you configure a different model for routing, you must create new report variants by copying the predefined
variants. You must then define a new background scheduler job for the preprocessor report using the copied
variants.
 Note
When creating copies of the predefined variants, you must use specific selection criteria for each variant.
Configuration of Parallel Processing for Parallel Execution Mode
You need to define a profile for parallel processing in SAP NetWeaver Business Client under
Administration
General Settings
Application
Define Parallel Processing Profile .
When you create a new parallel processing profile, you enter the maximum number of work processes, the
package size, and the queue time. Then you can enter the profile ID on the selection screens of transactions or
reports that support parallel processing.
 Note
The more work processes you assign to a profile for parallel processing, the shorter the execution time, and
the higher the memory consumption and overall usage of system resources.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
89
More Information
For more information about configuring models for routing, see the Configuration Guide for Routing on
SAP Help Portal at https://help.sap.com/l2a. Choose
Implement
Configuration
Configuration Guide for
Routing .
Related Information
Validations and Constraints [page 90]
Graph Generation [page 91]
Log Management [page 91]
Selection Criteria for Report Variant /DEL_ALL [page 92]
Selection Criteria for Report Variant /ROT_BLD [page 93]
Selection Criteria for Report Variant /GPH_BLD [page 94]
Delta Mode [page 95]
Job Schedule Creation for Preprocessor Report for New Model ID [page 96]
3.1.2.1
Validations and Constraints
The routing preprocessor performs validations during the network data generation process.
These validations are as follows:
•
•
Transportation zones must be marked as Routing Relevant in the definition, otherwise they are rejected.
•
•
For a drayage connection, both locations must be inside the same port in the location hierarchy.
The ramps and terminal locations must be maintained in the location hierarchy, otherwise they are
rejected. Ramps can be added either in inland hubs or ports depending on where they are in the network.
Transportation lanes must exist between the consecutive locations of the default routes, otherwise the
default route is rejected.
Related Information
Preprocessor Report for Routing [page 88]
90
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.1.2.2
Graph Generation
The routing preprocessor processes the network master data and stores the records in the database and
shared memory area. One important part of the process is the compression of inland connections.
Compression of Inland Connections
Routing supports 2+1 inland stages on the export and import side of the movement. The two inland stages
(pick-up and precarriage) are compressed into a single stage internally to fetch the connection quickly inside
the routing engine.
For compression, the intermediate locations can be either Ramp or Terminal. That is, Business Partner >
Ramp and Ramp > Terminal connections are compressed into Business Partner > Terminal. Similarly, Business
Partner > Terminal and Terminal > Terminal connections are compressed into Business Partner > Terminal.
Compression works on transportation lanes as well as on a combination of transportation lane and default
route.
The compression size is configurable and can be set with the variable /TMCSL/COMPRESS_SAVE_LIMIT in the
TVARVC table. This value sets the limit for the number of records to be processed in one iteration. For example,
if 1000 records are to be compressed and the size is set to 100, then compression will run in 10 iterations.
Related Information
Preprocessor Report for Routing [page 88]
3.1.2.3
Log Management
The routing preprocessor logs any errors and changes to the network master data that occur during the root
generation step and displays them as an ALV output or job log.
Based on this log, you can manually correct the errors. The errors that are captured in the log are as follows:
•
•
•
Transportation lanes missing between location <L1> and <L2> of default route <D1>.
Schedule <S1> is changed hence considered for delta.
Line study <LS1> is changed hence considered for delta.
Related Information
Preprocessor Report for Routing [page 88]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
91
3.1.2.4
Selection Criteria for Report Variant /DEL_ALL
The table below lists the selection criteria that you must specify when creating a copy of the variant /DEL_ALL
for the preprocessor report (/TMCSL/TN_DB_PROCESSOR).
Section
Field
Information
Processing Options
Datastore for Selections
Specify Trans Network DB.
Processing Mode
Specify Flush Mode.
Save Mode
Specify Synch. Save (Local Update).
Model ID
Enter the model ID (0).
Inactive Versions
Specify inactive versions or enter the
wildcard (*) to delete all inactive ver­
sions.
If no values are entered in this field,
none of the inactive graph versions are
deleted.
Execution Mode
Specify Sequential Execution/Parallel
Execution.
Cache(s) to Update
Graph DB
Select the checkbox.
Root DB
Select the checkbox.
Line Selections
Line ID
Not editable
Std Schedule Selections
Schedule ID
Not editable
TLane Selections
TLane GUID
Not editable
Location From & To
Not editable
Default Route ID
Not editable
Default Route Type
Not editable
Default Route
Related Information
Preprocessor Report for Routing [page 88]
Copying the Predefined Report Variants for a New Model ID [page 98]
92
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.1.2.5
Selection Criteria for Report Variant /ROT_BLD
The table below lists the selection criteria that you must specify when creating a copy of the variant /ROT_BLD
for the preprocessor report (/TMCSL/TN_DB_PROCESSOR).
Section
Field
Information
Processing Options
Datastore for Selections
Specify SAP TM Database.
Processing Mode
Specify Initial Mode.
Save Mode
Specify Synch. Save (Local Update).
Model ID
Enter the model ID (0).
Execution Mode
Specify Sequential Execution/Parallel
Execution.
Cache(s) to Update
Root DB
Select the checkbox.
Line Selections
Line ID
Enter *.
Std Schedule Selections
Schedule ID
Enter *.
TLane Selections
TLane GUID
Enter *.
Location From & To
Enter *.
Default Route ID
Enter *.
Default Route Type
Enter the type of default route.
Default Route
Related Information
Preprocessor Report for Routing [page 88]
Copying the Predefined Report Variants for a New Model ID [page 98]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
93
3.1.2.6
Selection Criteria for Report Variant /GPH_BLD
The table below lists the selection criteria that you must specify when creating a copy of the variant /GPH_BLD
for the preprocessor report (/TMCSL/TN_DB_PROCESSOR).
Section
Field
Information
Processing Options
Datastore for Selections
Specify Trans Network DB.
Processing Mode
Specify Initial Mode.
Save Mode
Specify Synch. Save (Local Update).
Model ID
Enter the model ID (0).
Reactivate Inactive Version
Specify the inactive version to reacti­
vate or deselect the Reactivate Inactive
Version checkbox to generate a new
version of the graph.
Execution Mode
Specify Sequential Execution/Parallel
Execution.
Cache(s) to Update
Graph DB
Select the checkbox.
Line Selections
Line ID
Not editable
Std Schedule Selections
Schedule ID
Not editable
TLane Selections
TLane GUID
Not editable
Location From & To
Not editable
Default Route ID
Not editable
Default Route Type
Not editable
Default Route
Related Information
Preprocessor Report for Routing [page 88]
Copying the Predefined Report Variants for a New Model ID [page 98]
94
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.1.2.7
Delta Mode
The routing preprocessor can be run in delta mode to process only the changed network master data from the
previous run. The master data that is not changed is not processed again.
Delta mode is only supported for the root generation step. While generating the graph in the initial mode, the
entire data is processed with the creation of a new version. Delta mode is not supported for graph generation.
The table below lists the selection criteria that you must specify when generating the root data in delta mode
through the preprocessor report (/TMCSL/TN_DB_PROCESSOR):
Section
Field
Information
Processing Options
Datastore for Selections
Specify SAP TM Database.
Processing Mode
Specify Delta Mode.
Save Mode
Specify Synch. Save (Local Update).
Model ID
Enter the model ID (0).
Execution Mode
Specify Sequential Execution/Parallel
Execution.
Cache(s) to Update
Graph DB
Select the checkbox.
Line Selections
Line ID
Enter *.
Std Schedule Selections
Schedule ID
Enter *.
TLane Selections
TLane GUID
Enter *.
Location From & To
Enter *.
Default Route ID
Enter *.
Default Route Type
Enter the type of default route.
Default Route
The table below lists the selection criteria that you must specify when generating the graph data in initial mode
through the preprocessor report (/TMCSL/TN_DB_PROCESSOR):
Section
Field
Information
Processing Options
Datastore for Selections
Specify Trans Network DB.
Processing Mode
Specify Initial Mode.
Save Mode
Specify Synch. Save (Local Update).
Model ID
Enter the model ID (0).
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
95
Section
Field
Information
Execution Mode
Specify Sequential Execution/Parallel
Execution.
Cache(s) to Update
Root DB
Select the checkbox.
Line Selections
Line ID
Not editable
Std Schedule Selections
Schedule ID
Not editable
TLane Selections
TLane GUID
Not editable
Location From & To
Not editable
Default Route ID
Not editable
Default Route Type
Not editable
Default Route
Related Information
Preprocessor Report for Routing [page 88]
Copying the Predefined Report Variants for a New Model ID [page 98]
3.1.2.8
Job Schedule Creation for Preprocessor Report for
New Model ID
The default routing model that has been configured for the Preprocessor Report (/TMCSL/
TN_DB_PROCESSOR) is 000. If you configure a new model for routing, you must create a new background
job schedule for the Preprocessor Report and create new variants for the new model.
You create the new variants by copying the variants that have been predefined for the Preprocessor Report. You
then specify the new model ID in the new variants. You make copies of the following predefined variants:
•
•
•
/DEL_ALL
/ROT_BLD
/GPH_BLD
You must create a new background job schedule for the Preprocessor Report for the new model and assign the
new variants to the schedule job.
The following table lists the steps that you need to perform to create a new job schedule for the Preprocessor
Report after you configure a new model ID for routing:
96
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Step
Description
1
Create copies of the predefined variants Copying the Predefined Report Variants
for the Preprocessor Report.
for a New Model ID [page 98]
2
Create a new background job schedule
and add the copied variants to the job.
3.1.2.8.1
Related Topic
Creating a Background Schedule Job
for the Preprocessor Report [page 102]
Single Step Execution of Preprocessor Report
The single step execution of the preprocessor report (/TMCSL/ROUTE_PREPROCESSOR_RUN) is an alternative
solution for generating the routing master data based on lines, schedules, and transportation lanes created in
the system. The single step preprocessor report is a prerequisite step for the routing application programming
interface (API).
You can use the single step preprocessor report to delete and build routing master data by selecting the Delete
checkbox. You can also delete specific inactive versions by choosing the relevant version from the search help
or delete all inactive versions based on the authorization check for the protected Model ID.
You can deselect the Delete checkbox to reactivate the inactive version if the current active version contains
corrupted data or to build the routing master data.
Related Information
Selection Criteria for Single Step Preprocessor Report [page 97]
3.1.2.8.1.1 Selection Criteria for Single Step Preprocessor
Report
The table below lists the selection criteria that you must specify when executing the single step preprocessor
report (/TMCSL/ROUTE_PREPROCESSOR_RUN).
Section
Field
Information
Processing Options
Model ID
Specify the model ID.
Delete
Select this checkbox to delete and build
the routing master data.
Deselect this checkbox to build the
routing master data.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
97
Section
Field
Information
Inactive Versions
Specify the inactive graph versions to
be deleted.
If no values are entered in this field,
then none of the inactive graph versions
are deleted.
Simulation Mode
Select this checkbox to run in simula­
tion mode for testing purposes.
Reactivate Inactive Version
Reactivate Inactive Version
Specify the inactive graph version to be
reactivated.
Related Information
Single Step Execution of Preprocessor Report [page 97]
3.1.2.8.2
Copying the Predefined Report Variants for a New
Model ID
Create copies of the variants that have been predefined for the preprocessor report (/TMCSL/
TN_DB_PROCESSOR) and specify a model ID in each variant.
Context
If you have configured a new model ID for the routing solution, you must create a new job schedule for the
preprocessor report, and create copies of the predefined variants for the new model.
The predefined variants that you must copy for the new model ID are as follows:
•
•
•
/DEL_ALL
/ROT_BLD
/GPH_BLD
Procedure
1. Start transaction SE38.
98
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
2. Enter /TMCSL/TN_DB_PROCESSOR in the Program field.
3. Copy the predefined variant /DEL_ALL as follows:
a. Select the subobject Variants.
b. Choose Change.
The system opens the variants screen.
c. Enter the name of the new variant in the Variant field (for example, /DEL_ALL_100).
d. Choose Create and then specify the following selection criteria:
Section
Field
Information
Processing Options
Datastore for Selections
Specify Trans Network DB.
Processing Mode
Specify Flush Mode.
Save Mode
Specify Synch. Save (Local Update).
Model ID
Enter the model ID (0).
Inactive Version
Specify inactive versions or enter
the wildcard (*) to delete all inactive
versions.
If no values are passed to this field,
none of the inactive graph versions
are deleted.
Execution Mode
Specify Sequential Execution/
Parallel Execution.
Cache(s) to Update
Graph DB
Select this checkbox.
Root DB
Select this checkbox.
Line Selections
Line ID
Not editable
Std Schedule Selections
Schedule ID
Not editable
TLane Selections
TLane GUID
Not editable
Location From & To
Not editable
Default Route ID
Not editable
Default Route Type
Not editable
Default Route
e. Choose the Attributes button.
The Variant Attributes screen opens.
f. Enter a description for the variant in the Description field.
g. Save your entries by choosing
Variant
Save .
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
99
4. Copy the predefined variant /ROT_BLD as follows:
a. Select the subobject Variants.
b. Choose Change.
The system opens the variants screen.
c. Enter the name of the new variant in the Variant field (for example, /ROT_BLD_100).
d. Choose Create and then specify the following selection criteria:
Section
Field
Information
Processing Options
Datastore for Selections
Specify SAP TM Database.
Processing Mode
Specify Initial Mode.
Save Mode
Specify Synch. Save (Local Update).
Model ID
Enter the model ID (0).
Execution Mode
Specify Sequential Execution/
Parallel Execution.
Cache(s) to Update
Root DB
Select the checkbox.
Line Selections
Line ID
Enter *
Std Schedule Selections
Schedule ID
Enter *
TLane Selections
TLane GUID
Enter *
Location From & To
Enter *
Default Route ID
Enter *
Default Route Type
Enter the type of default route.
Default Route
e. Choose the Attributes button.
The Variant Attributes screen opens.
f. Enter a description for the variant in the Description field.
g. Save your entries by choosing
Variant
Save .
5. Copy the predefined variant /GPH_BLD as follows:
a. Select the subobject Variants.
b. Choose Change.
The system opens the variants screen.
c. Enter the name of the new variant in the Variant field (for example, /GPH_BLD_100).
d. Choose Create and then specify the following selection criteria:
100
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Section
Field
Information
Processing Options
Datastore for Selections
Specify Trans Network DB.
Processing Mode
Specify Initial Mode.
Save Mode
Specify Synch. Save (Local Update).
Model ID
Enter the model ID (0).
Reactivate Inactive Version
Specify the inactive version to re­
activate or deselect the Reactivate
Inactive Version checkbox to gener­
ate a new graph version.
Execution Mode
Specify Sequential Execution/
Parallel Execution.
Cache(s) to Update
Graph DB
Select the checkbox.
Line Selections
Line ID
Not editable
Std Schedule Selections
Schedule ID
Not editable
TLane Selections
TLane GUID
Not editable
Location From & To
Not editable
Default Route ID
Not editable
Default Route Type
Not editable
Default Route
e. Choose the Attributes button.
The Variant Attributes screen opens.
f. Enter a description for the variant in the Description field.
g. Save your entries by choosing
Variant
Save .
Next Steps
Create a new job for the preprocessor report and assign the new variants.
Related Information
Creating a Background Schedule Job for the Preprocessor Report [page 102]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
101
3.1.2.8.3
Creating a Background Schedule Job for the
Preprocessor Report
Create a background scheduling job for the preprocessor report (/TMCSL/TN_DB_PROCESSOR).
Prerequisites
If you are defining a job schedule for a new model ID, you must have created copies of the predefined variants
in the preprocessor report to new variants.
Context
You add the variants to the background job as steps. The variants must be added in the following order:
1. The variant to delete the graph cache and root cache.
The predefined variant is named /DEL_ALL; however, if you have copied the predefined variant for a new
model, your variant will have a different name.
2. The variant to build the root cache.
The predefined variant is named /ROT_BLD; however, if you have copied the predefined variant for a new
model, your variant will have a different name.
3. The variant to build the graph cache.
The predefined variant is named /GPH_BLD; however, if you have copied the predefined variant for a new
model, your variant will have a different name.
Procedure
1. Start transaction SM36.
The Define Job screen opens.
2. Enter a name for the new job in the Job Name field.
3. In the Job Class field, accept the default entry (C).
4. In the Status field, accept the default entry (Scheduled).
5. Define when the job is scheduled to run by choosing the Start Condition button.
6. In the Start Time dialog box that opens, specify the required schedule details.
7. Save the dialog box.
8. Choose the Step button to add the variants to the job.
9. In the Create Step 1 dialog box that opens, enter the following details:
102
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Section
Field
Specify the Following:
ABAP Program
Name
/TMCSL/TN_DB_PROCESSOR
Variant
/DEL_ALL

Note
If you have copied the predefined
variant you enter the name of the
copied variant here.
10. Save the dialog box.
The Step List Overview screen opens and displays the first variant that you added to the job.
11. Add the next variant by choosing the Create button.
12. In the Create Step 2 dialog box that opens, enter the following details:
Section
Field
Specify the Following:
ABAP Program
Name
/TMCSL/TN_DB_PROCESSOR
Variant
/ROT_BLD

Note
If you have copied the predefined
variant you enter the name of the
copied variant here.
13. Save the dialog box.
The Step List Overview screen opens and displays the two variants that you added to the job.
14. Add the last variant by choosing the Create button.
15. In the Create Step 3 dialog box that opens, enter the following details:
Section
Field
Specify the Following:
ABAP Program
Name
/TMCSL/TN_DB_PROCESSOR
Variant
/GPH_BLD

Note
If you have copied the predefined
variant you enter the name of the
copied variant here.
16. Save the dialog box.
The Step List Overview screen opens and displays the three variants that you added to the job.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
103
17. Choose the Enter button.
18. In the Define Job screen, choose the Save button to save the job.
Related Information
Copying the Predefined Report Variants for a New Model ID [page 98]
Preprocessor Report for Routing [page 88]
3.2
Response Generation and Routing
You create a response line for a request line by generating a route for the request line.
The system creates a response line by calling the route generator application programming interface (API) to
generate routes for the request line. The newly created response line contains the rates for the chosen route.
You can generate routes for response line creation using one of the following features:
•
Search Routes Feature
The system retrieves all of the valid routes for the request based on the maximum number of routes
requested and you choose the appropriate route.
•
Get Response Feature
The system automatically selects the best route for a request.
The call to the route generator to fetch the routes is implemented in a Business Add-In (BAdI), which you can
find in Customizing for Transportation Management under
Business Add-Ins (BAdIs)
Container Shipping Liners
Forwarding Agreement Quotation
Lead to Agreement
BAdI: Preparation of Routes for Response
Generation .
You can use this BAdI to prepare and filter routes for response generation, based on the validity dates, source,
destination locations, and other request parameters.
Related Information
Basic Settings [page 81]
Routing [page 81]
3.3
Data Management
Data Management offers various options to help you to manage your data.
You can use the following options to help you manage your data:
104
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Function
Purpose
More Information
Data Aging
Data aging allows you to move data you
no longer need out of the current data
store to optimize system performance.
Data Aging [page 105]
Archiving
You can use archiving to remove mass
data from the database that is no lon­
ger required in the system but must be
kept in a format that can be analyzed.
Archiving [page 124]
Blocking and Deletion of Personal Data
Personal data that is no longer required
in the system can be first blocked and
later destroyed.
Blocking and Deletion of Personal Data
[page 138]
Change Tracking
Change Tracking [page 170]
You can use this change tracking to
display which data was changed, how
it was changed, when it was changed,
and by whom it was changed for certain
business documents.
Blocking and Deletion of Location Mas­
ter Data
Location master that is no longer re­
quired for any business purposes can
be first blocked and later destroyed.
See application help for Cross Applica­
tions at https://help.sap.com/viewer/
product/BS_CA/750%20SP11/
Under Application Help, open Business
Functions in SAP NetWeaver and
choose
Deletion
Simplified Blocking and
Blocking and Deletion of
SCM Location Master Data
.
3.3.1 Data Aging
Data Aging allows you to optimize system performance by moving data you no longer need out of the current
data store.
Data Aging lets you move business objects that you no longer need in your day-to-day work out of the current
data store into a historical data store, which is typically kept on hard disk. When unused business objects are
no longer taking up space in the current data store, the system can perform at its optimum level allowing you to
work more efficiently.
You can still access and view the aged documents, but you cannot change them or carry out any other activities
on them. If you need to change an aged document, you must first restore it to the current data store using the
data aging undo transaction DAG_UNDO.
 Note
A data aging business object is different from a Business Object Processing Framework (BOPF) business
object. To reflect this difference, we will use the term business objects for data aging business objects, and
the term BOPF business objects for BOPF business objects.
Data Aging is only available for the following objects and documents:
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
105
•
•
•
•
Completed business objects
Canceled business objects
Business objects whose residence period is over
Complete business documents that are ready for data aging, that is, when all related documents listed in
the document flow are ready for data aging
 Note
You define the residence period in the document type Customizing for documents of data aging objects /
SCMTMS/TOR.
For all other data aging objects, you define the residence period in Customizing for Cross-Application
Components under
BOBF Environment
Processes and Tools for Enterprise Applications
Data Aging Adapter
Reusable Objects and Functions for
Maintain BO-specific Residence Periods .
Dependent Objects
Reuse data aging objects exist for all BOPF dependent objects such as the Generic Validation Framework Log,
or the Document Comparison and Reconciliation Log. Transportation Management (TM) data aging objects
include all relevant reuse data aging objects, so that BOPF dependent object data is aged at the same time as
the data of its host business objects.
Parallel Processing
Most of the data aging objects are suitable for parallel processing. You can define a server group, the maximum
number of work processes, and the package size per work process for each data aging object.
Analysis Report
You can simulate a data aging run for a data aging object using transaction DAGADM. A simulation run executes
a data aging run but does not update the document age or move the documents from current data into the
historical data store. A report is available after the run, containing many useful statistics such as data volume,
run times, and any error messages.
Data Aging Procedure
For each business object that you want to age, there must be a corresponding data aging object. You can
also enhance data aging objects, if applicable. During a data aging run, the data aging objects are moved into
partitions. A corresponding partitioning object must exist for each data aging object before it can be moved
into a partition.
106
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
 Note
Data aging objects, partitioning objects, and enhanced data aging objects are provided as standard for
container shipping liners business objects.
You must create one or more data aging groups to execute the data aging run. Once your groups are created,
you can then execute data aging by scheduling a data aging run.
More Information
For more information on Data Aging, see SAP Library for SAP NetWeaver at http://help.sap.com/nw. Choose
your platform, and under Application Help open SAP NetWeaver Library: Function-Oriented View and choose
Solution Life Cycle Management
Data Aging .
Related Information
Why Data Aging? [page 107]
Data Aging Objects [page 108]
Partitions and Partitioning Objects [page 109]
Data Aging Runs [page 111]
Undo Data Aging [page 112]
Prerequisites for Data Aging [page 113]
Data Aging for Business Objects [page 114]
3.3.1.1
Why Data Aging?
Data Aging is a business data management concept for reducing the SAP S/4HANA memory footprint
Data Aging works as follows:
•
•
•
Only operational data (current data) is loaded into SAP S/4HANA main memory.
Other data (historical data) is primarily stored on disk, so it does not influence current data performance.
Current and historical data are separated into partitions. Historical data remains accessible via SQL on
request, that is, you must explicitly request access to historical data.
Data Aging also helps SAP S/4HANA to keep the time for loading, processing, and change operations as short
as possible because the memory contains less data.
Searching aged documents is possible using the standard Transportation Management (TM) POWLs using the
POWL query parameter Document Age (date). The system opens aged documents in display mode only.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
107
 Note
The default of the POWL query parameter Document Age is initial, meaning that the system only searches
current data when looking for business documents.
If you specify a date for the Document Age parameter, as well as searching current data, the system also
searches historical data up to the date you specified. This has an impact on system performance, so only
use this if you need to access historical data.
More Information
For more information on Data Aging, see SAP Library for SAP NetWeaver at http://help.sap.com/nw. Choose
your platform, and under Application Help open SAP NetWeaver Library: Function-Oriented View and choose
Solution Life Cycle Management
Data Aging .
Related Information
Data Aging Objects [page 108]
Data Aging [page 105]
3.3.1.2
Data Aging Objects
Data aging objects must be created for each business object that has to be aged.
Data aging objects contain the following information:
•
•
Database tables that are also aged when you execute a data aging run
•
A data aging runtime class, which contains the functional part of the data aging object. For example, data
selection, parallel processing, error handling, or writing the data aging log.
•
•
A data aging object analysis program, which is used to execute a data aging run in simulation mode.
An optional set of reuse data aging objects
Reuse data aging objects are similar to data aging objects; however, they can only be aged with their host
data aging objects and cannot be aged on their own. Reuse data aging objects can be referenced by one or
more data aging objects.
A list of available enhancement spots
You use transaction DAGOBJ to create or change data aging objects.
108
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
More Information
For more information on Data Aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw and choose your SAP NetWeaver platform. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View and choose
Solution Life Cycle Management
Data Aging .
Related Information
Partitions and Partitioning Objects [page 109]
Data Aging [page 105]
3.3.1.3
Partitions and Partitioning Objects
Data aging objects and database tables used in Data Aging are moved into partitions in the historical data
store. A partitioning object that corresponds to the data aging object must exist before the data aging object
can be partitioned.
Data aging objects and database tables used in Data Aging are moved into partitions in the historical data
store.
You create these partitions using the transaction Manage Partitions (transaction DAGPTM).
Before a data aging object can be moved into a partition, a corresponding partitioning object must be created
for it. The partitioning object defines the set of database tables that are processed at the same time.
A database table can only be part of one partitioning object. When you have specified a partitioning object for a
database table, you can use the table for one or more data aging objects.
You create or change a partitioning object using transaction DAGPTC.
More Information
For more information on Data Aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw and choose your SAP NetWeaver platform. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View and choose
Solution Life Cycle Management
Data Aging .
Related Information
Data Aging [page 105]
Data Aging Objects [page 108]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
109
3.3.1.4
Available Data Aging and Partitioning Objects
The following table lists the partitioning and data aging objects (with the appropriate settings) that we provide
as standard for container shipping liners:
Enhanced Data Aging
Business Object
Data Aging Object
Object
Partitioning Object
Documentation
Agreements
/SCMTMS/FREIGHT­
AGREEMENT
/TMCSL/FREIGHTA­
GREEMENT
/TMCSL/FREIGHTA­
GREEMENT
Aging of Business
Documents for Agree­
ments [page 119]
Calculation Sheets
/SCMTMS/TCCS
/TMCSL/TCCS
/TMCSL/TCCS
Aging of Business
Documents for Calcu­
lation Sheets [page
118]
Rate Tables
/SCMTMS/TC_RATES
/TMCSL/TC_RATES
/TMCSL/TC_RATES
Aging of Business
Documents for Rate
Tables [page 117]
Trade Lanes
/SCMTMS/TRADE­
LANE
Surcharge Exception
/TMCSL/EXCEP­
TION_TEMPLATE
/TMCSL/EXCEP­
TION_TEMPLATE
Aging of Business
Documents for Sur­
charge Exception Pro­
files [page 123]
Filter Templates
/TMCSL/FIL­
TER_TEMPLATE
/TMCSL/FIL­
TER_TEMPLATE
Aging of Business
Documents for Filter
Templates [page 120]
Governing Tariffs
/TMCSL/GOVERN­
ING_TARIFF
/TMCSL/GOVERN­
ING_TARIFF
Aging of Governing
/TMCSL/
RATE_RULES
/TMCSL/
RATE_RULES
Aging of Rate Rules
Templates
Rate General Rules
/TMCSL/TRADELANE /TMCSL/TRADELANE Aging of Business
Documents for Trade
Lanes [page 121]
Tariffs [page 115]
[page 116]
Related Information
Partitions and Partitioning Objects [page 109]
Data Aging [page 105]
110
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.1.5
Data Aging Runs
Data Aging is executed by creating groups for the data aging run and then scheduling the data aging run. After
business objects have been aged, you have the option of viewing them from various applications.
Data Aging Groups
Before you can execute Data Aging, you must create one or more data aging groups. A data aging group
consists of a number of data aging objects to be processed in a defined sequence. A data aging group must
contain at least one data aging object. Each data aging object can belong to only one data aging group. You can
create and change data aging groups using the transaction DAGRUN.
Data Aging Run Schedule
Once the data aging groups have been created, you execute data aging by scheduling a data aging run for your
tables using transaction DAGRUN.
You can control the memory used during a data aging run by specifying the processing package size. You can
also specify the number of parallel processes and the package size per process. Before the next package is
selected and processed, allocated memory is released to keep the memory consumption for the data aging job
constant.
Viewing Aged Documents
You can load aged business objects from the historical data store into the screens of container shipping liners.
The objects are not loaded by default, but you can access them as follows:
•
When you use the personal object worklist (POWL) parameter Document Age to define the maximum age
for the documents to be loaded.
•
When you navigate to an aged business document from the document flow of a current business
document.
•
When you navigate from an aged business document to another aged business document.
 Note
You can only view aged documents; you cannot change or delete them.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
111
More Information
For more information on Data Aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw and choose your SAP NetWeaver platform. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View and choose
Solution Life Cycle Management
Data Aging .
Related Information
Prerequisites for Data Aging [page 113]
3.3.1.6
Undo Data Aging
If you need to change or carry out any other activity on an aged business document, you can undo Data Aging
using the transaction DAG_UNDO.
You can undo Data Aging for documents up to 180 days old. An undo data aging run clears the data aging
information from the documents and loads them back into the current data store, allowing you to use them as
required.
More Information
For more information on Data Aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw and choose your SAP NetWeaver platform. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View and choose
Solution Life Cycle Management
Data Aging .
Related Information
Data Aging [page 105]
112
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.1.7
Prerequisites for Data Aging
Before you can apply data aging to your data, you need to create partitions and ensure that the business
document is closed and has completed its residence period.
Partitions
Before you can start a data aging run, you need to create partitions for the aged data using the transaction
Manage Partitions (DAGPTM).
Business Documents
To be considered for data aging, a business document must be closed for business (for example, the life cycle
status must be Completed or Canceled). In addition, the residence period for a business document must be
over. The residence period is the minimum time in days between the date you closed a document and the date
the system considers the document for data aging.
You can specify the residence period for the following documents in Customizing for Cross-Application
Components under
BOPF Environment
•
•
•
•
•
•
•
•
Processes and Tools for Enterprise Applications
Data Aging Adapter
Reusable Objects and Functions for
Maintain BO-Specific Residence Periods :
Agreements
Calculation Sheets
Rate Tables
Trade Lanes
Surcharge Exception Template
Filter Template
Governing Tariff
Rate General Rules
You can review the data aging objects assigned to the BOPF business objects in Customizing for CrossApplication Components under
Functions for BOPF Environment
Processes and Tools for Enterprise Applications
Data Aging Adapter
Reusable Objects and
Data Aging Residence Times For BOPF Business
Objects
More Information
For more information on Data Aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw and choose your SAP NetWeaver platform. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View and choose
Solution Life Cycle Management
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Data Aging .
PUBLIC
113
Related Information
Data Aging [page 105]
3.3.1.8
Data Aging for Business Objects
The following table lists the data aging object and business object combinations you can use for SAP
Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA.
You use Overview of Data Aging Runs (transaction DAGRUN) to perform Data Aging.
Business Object
Data Aging Object
Documentation
Agreements
/SCMTMS/FREIGHTAGREEMENT
Aging of Business Documents for
Agreements [page 119]
Calculation Sheets
/SCMTMS/TCCS
Aging of Business Documents for Cal­
culation Sheets [page 118]
Rate Tables
/SCMTMS/TC_RATES
Aging of Business Documents for Rate
Tables [page 117]
Trade Lanes
/SCMTMS/TRADELANE
Aging of Business Documents for Trade
Lanes [page 121]
Surcharge Exception Profile
/TMCSL/EXCEPTION_TEMPLATE
Aging of Business Documents for Sur­
charge Exception Profiles [page 123]
Filter Templates
/TMCSL/FILTER_TEMPLATE
Aging of Business Documents for Filter
Templates [page 120]
Governing Tariffs
/TMCSL/GOVERNING_TARIFF
Aging of Governing Tariffs [page 115]
Rate Rules
/TMCSL/RATE_RULES
Aging of Rate Rules [page 116]
More Information
For more information on Data Aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw and choose your SAP NetWeaver platform. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View and choose
Solution Life Cycle Management
Data Aging .
Related Information
Data Aging for Business Objects [page 114]
Data Aging [page 105]
114
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.1.8.1
Aging of Governing Tariffs
Definition
You can use the data aging object /TMCSL/GOVERNING_TARIFF to age governing tariffs.
Structure
Tables
The option for container shipping liners uses the data aging object /TMCSL/GOVERNING_TARIFF to age data
from the nodes of the business object model /TMCSL/GOVERNING_TARIFF.
Prerequisites
The system can age a governing tariff when the following prerequisites are met:
•
•
•
•
The governing tariff is not active.
The dependent objects of the forwarding agreement have been aged.
The governing tariff validity has expired.
The aging residence time has passed.
Functions
You can perform the following tasks after the documents have been aged:
•
•
Review the details of aged documents in a tabular format
Review individual aged documents
You can perform these tasks in the Overview Governing Tariff app in your SAP Fiori launchpad.
You cannot edit aged documents or execute any actions or activities on them. If you want to make changes, you
first need to load the aged document back into the current data store using the undo data aging transaction
DAG_UNDO.
You can undo data aging and use parallel processing for governing tariffs.
More Information
For more information on data aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw. Select your SAP NetWeaver release and then choose
Library: Function-Oriented View
Solution Life Cycle Management
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Application Help
SAP NetWeaver
Data Aging .
PUBLIC
115
Related Information
Data Aging for Business Objects [page 114]
3.3.1.8.2
Aging of Rate Rules
Definition
You can use the data aging object /TMCSL/RATE_RULES to age rate rules.
Structure
Tables
The option for container shipping liners uses the data aging object /TMCSL/RATE_RULES to age data from the
nodes of the business object model /TMCSL/RATE_RULES.
Prerequisites
The system can age a rate rule when the following prerequisites are met:
•
•
•
The rate rule is not active.
The rate rule validity has expired.
The aging residence time has passed.
Functions
You can perform the following tasks after the documents have been aged:
•
•
Review the details of aged documents in a tabular format
Review individual aged documents
You can perform these tasks in the GRI/GRD app in your SAP Fiori launchpad.
You cannot edit aged documents or execute any actions or activities on them. If you want to make changes, you
first need to load the aged document back into the current data store using the undo data aging transaction
DAG_UNDO.
You can undo data aging and use parallel processing for rate rules.
116
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
More Information
For more information on data aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw. Select your SAP NetWeaver release and then choose
Library: Function-Oriented View
Solution Life Cycle Management
Application Help
SAP NetWeaver
Data Aging .
Related Information
Data Aging for Business Objects [page 114]
3.3.1.8.3
Aging of Business Documents for Rate Tables
Definition
You can use the data aging object /SCMTMS/TC_RATES to age rate tables.
Structure
Tables
The option for container shipping liners uses the data aging object /SCMTMS/TC_RATES to age data from the
nodes of the business object model /SCMTMS/TC_RATES.
Prerequisites
The system can age an agreement when the following prerequisites are met:
•
The aging residence time has passed.
Functions
You can perform the following tasks after the documents have been aged:
•
•
Review the details of aged documents in a tabular format
Review individual aged documents
You can perform these tasks in the Charge Management Worklist app in your SAP Fiori launchpad.
You cannot edit aged documents or execute any actions or activities on them. If you want to make changes, you
first need to load the aged document back into the current data store using the undo data aging transaction
DAG_UNDO.
You can undo data aging and use parallel processing for rate tables.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
117
More Information
For more information on data aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw. Select your SAP NetWeaver release and then choose
Library: Function-Oriented View
Solution Life Cycle Management
Application Help
SAP NetWeaver
Data Aging .
Related Information
Data Aging for Business Objects [page 114]
3.3.1.8.4
Aging of Business Documents for Calculation
Sheets
Definition
You can use the data aging object /SCMTMS/TCCS to age calculation sheets.
Structure
Tables
The option for container shipping liners uses the data aging object /SCMTMS/TCCS to age data from the nodes
of the business object model /SCMTMS/TCCS.
Prerequisites
The system can age an agreement when the following prerequisites are met:
•
•
The aging residence time has passed
The calculation sheet is not active
Functions
You can perform the following tasks after the documents have been aged:
•
•
Review the details of aged documents in a tabular format
Review individual aged documents
You can perform these tasks in the Charge Management Worklist app in your SAP Fiori launchpad.
118
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
You cannot edit aged documents or execute any actions or activities on them. If you want to make changes, you
first need to load the aged document back into the current data store using the undo data aging transaction
DAG_UNDO.
You can undo data aging and use parallel processing for calculation sheets.
More Information
For more information on data aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw. Select your SAP NetWeaver release and then choose
Library: Function-Oriented View
Solution Life Cycle Management
Application Help
SAP NetWeaver
Data Aging .
Related Information
Data Aging for Business Objects [page 114]
3.3.1.8.5
Aging of Business Documents for Agreements
Definition
You can use the data aging object /SCMTMS/FREIGHTAGREEMENT to age forwarding agreements and
quotations.
Structure
Tables
The option for container shipping liners uses the data aging object /SCMTMS/FREIGHTAGREEMENT to age data
from the nodes of the business object model /SCMTMS/FREIGHTAGREEMENT.
Prerequisites
The system can age an agreement when the following prerequisites are met:
•
•
•
•
The aging residence time has passed
The agreement is not active
The agreement validity has expired
The dependent objects of the agreement have been aged
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
119
Functions
You can perform the following tasks after the documents have been aged:
•
•
Review the details of aged documents in a tabular format
Review individual aged documents
You can perform these tasks in the Forwarding Agreement Worklist app in your SAP Fiori launchpad.
You cannot edit aged documents or execute any actions or activities on them. If you want to make changes, you
first need to load the aged document back into the current data store using the undo data aging transaction
DAG_UNDO.
You can undo data aging and use parallel processing for forwarding agreements and quotations.
More Information
For more information on data aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw. Select your SAP NetWeaver release and then choose
Library: Function-Oriented View
Solution Life Cycle Management
Application Help
SAP NetWeaver
Data Aging .
Related Information
Data Aging for Business Objects [page 114]
3.3.1.8.6
Aging of Business Documents for Filter Templates
Definition
You can use the data aging object /TMCSL/FILTER_TEMPLATE to age filter templates.
Structure
Tables
The option for container shipping liners uses the data aging object /TMCSL/FILTER_TEMPLATE to age data
from the nodes of the business object model /TMCSL/FILTER_TEMPLATE.
120
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Prerequisites
The system can age a filter template when the following prerequisites are met:
•
The aging residence time has passed.
Functions
You can perform the following tasks after the documents have been aged:
•
•
Review the details of aged documents in a tabular format
Review individual aged documents
You cannot edit aged documents or execute any actions or activities on them. If you want to make changes, you
first need to load the aged document back into the current data store using the undo data aging transaction
DAG_UNDO.
You can undo data aging and use parallel processing for filter templates.
More Information
For more information on data aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw. Select your SAP NetWeaver release and then choose
Library: Function-Oriented View
Solution Life Cycle Management
Application Help
SAP NetWeaver
Data Aging .
Related Information
Data Aging for Business Objects [page 114]
3.3.1.8.7
Aging of Business Documents for Trade Lanes
Definition
You can use the data aging object /SCMTMS/TRADELANE to age governing tariffs.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
121
Structure
Tables
The option for container shipping liners uses the data aging object /SCMTMS/TRADELANE to age data from the
nodes of the business object model /SCMTMS/TRADELANE.
Prerequisites
The system can age a trade lane when the following prerequisites are met:
•
The aging residence time has passed
Functions
You can perform the following tasks after the documents have been aged:
•
•
Review the details of aged documents in a tabular format
Review individual aged documents
You can perform these tasks in the Create/Edit Tradelane app in your SAP Fiori launchpad.
You cannot edit aged documents or execute any actions or activities on them. If you want to make changes, you
first need to load the aged document back into the current data store using the undo data aging transaction
DAG_UNDO.
You can undo data aging and use parallel processing for trade lane documents.
More Information
For more information on data aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw. Select your SAP NetWeaver release and then choose
Library: Function-Oriented View
Solution Life Cycle Management
Application Help
SAP NetWeaver
Data Aging .
Related Information
Data Aging for Business Objects [page 114]
122
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.1.8.8
Aging of Business Documents for Surcharge
Exception Profiles
Definition
You can use the data aging object /TMCSL/EXCEPTION_TEMPLATE to age surcharge exception templates.
Structure
Tables
The option for container shipping liners uses the data aging object /TMCSL/EXCEPTION_TEMPLATE to age
data from the nodes of the business object model /TMCSL/EXCEPTION_TEMPLATE.
Prerequisites
The system can age surcharge exception templates when the following prerequisites are met:
•
The aging residence time has passed
Functions
You can perform the following tasks after the documents have been aged:
•
•
Review the details of aged documents in a tabular format
Review individual aged documents
You can perform these tasks in the Exception Template Worklist app in your SAP Fiori launchpad.
You cannot edit aged documents or execute any actions or activities on them. If you want to make changes, you
first need to load the aged document back into the current data store using the undo data aging transaction
DAG_UNDO.
You can undo data aging and use parallel processing for surcharge exception profiles.
More Information
For more information on data aging, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw. Select your SAP NetWeaver release and then choose
Library: Function-Oriented View
Solution Life Cycle Management
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Application Help
SAP NetWeaver
Data Aging .
PUBLIC
123
Related Information
Data Aging for Business Objects [page 114]
3.3.2 Archiving
You can use transaction AOBJ to create archiving objects. You can specify archiving objects for preprocessing,
writing, and deleting activities. For more information, see Customizing for SAP NetWeaver under
Server
System Administration
Data Archiving
Application
Archiving Object-Specific Customizing .
We provide the following archiving objects with the appropriate settings:
Business Object
Archiving Object
Documentation
Rate Tables
SCMTMSTCRR
Archiving Rate Tables [page 131]
/SCMTMS/RA
/TMCSL/RA
Agreements
Enhanced Archiving Agreements and
SCMTMSFAG
RFQ Masters [page 130]
You can also extend the archiving objects for SAP Transportation Management, lead to agreement for container
shipping liners for SAP S/4HANA liners your own business requirements. You can specify the database tables
from which the system archives the information for the archiving object.
You can use transaction SARA to schedule when the system executes the preprocessing, writing, and deleting
activities for an archiving object. For more information, see
SARA
SAP Easy Access
Tools
Administration
Data Archiving .
You can use the following features in transaction SARA:
•
Preprocessing
We provide each business object with separate selection criteria to identify the instances of the business
object that are ready for archiving. We provide each query with the same logic. The query selects the
instances that are ready and calls the CHECK_ARCHIVABILITY action. The action checks the residence
period and sets the archiving status to Archiving in Process. The action only runs across the relevant
business object.
 Note
You define the residence period in Customizing for Cross-Application Components under
and Tools for Enterprise Applications
Archiving Adapter
Processes
Reusable Objects and Functions for BOBF Environment
Maintain BO-specific Residence Periods .
You can control the memory used during archive preprocessing by specifying the package size, and
describing the number of documents being processed together in one SAP Logical Unit of Work (SAP
LUW). Before the next package is selected and processed, allocated memory is released to keep the
memory consumption for the preprocessing batch job constant.
124
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
•
Writing
The system selects all instances of a business object that have the archiving status Archiving in Process. It
copies the instances into the archive. You can control the memory used during writing in the same way as
for preprocessing.
•
Deleting
The system deletes all records that are archived from the registered database tables.
•
Deleting from Archive
All Transportation Management (TM) archiving objects are ILM-enabled. For more information about SAP
Information Lifecycle Management (SAP ILM), see http://help.sap.com/erp . Choose your release and
open SAP Library. Choose
SAP ERP Cross-Application Functions
Cross-Application Components
SAP
Information Lifecycle Management .
You can load archived documents into the standard TM screens. The system uses only the display mode for
these archived documents. We provide each business object in TM with the following settings:
•
•
Individual archiving object
•
•
•
CHECK_ARCHIVABILITY action
Archiving status
Statuses include Not Archived, Archiving in Process, and Archived.
Programs for each of the preprocessing, write, and delete steps
Individual query to select business objects for the preprocessing step
For more information about the prerequisites you must specify before you can begin archiving, see
Prerequisites for Archiving [page 126].
More Information
For more information about the Archive Information System, see SAP Library for SAP NetWeaver on SAP
Help Portal at http://help.sap.com/nw . Choose your release. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View, and choose
Archiving in the ABAP Application System
Solution Life Cycle Management
Data Archiving
Data Archiving with Archive Development Kit (ADK)
Data
Archive
Information System .
For more information about tables and archiving objects, see SAP Library for SAP NetWeaver on SAP Help
Portal at http://help.sap.com/nw . Choose your release. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View, and choose
Archiving in the ABAP Application System
Administration
Solution Life Cycle Management
Data Archiving
Data Archiving with Archive Development Kit (ADK)
Data
Archive
Tables and Archiving Objects .
Related Information
Why Archive? [page 126]
Prerequisites for Archiving [page 126]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
125
3.3.2.1
Why Archive?
Archiving data from the production database makes the production database faster as it is carrying less
unproductive data.
Archiving Dependent Objects
The system archives charge information, address information, or information from texts or attachments when
you archive a business object. It also archives other objects that are used in business objects for tendering. It
does not archive master data objects in general (with the exception of business partner master).
Index Criteria
You can specify database indexes to enable a query to search for data records efficiently. Ideally, you should
have no more than 8 indexes defined for a database table; otherwise the performance of the query decreases.
The database indexes in Transportation Management (TM) improve the performance of active business
queries, and not archiving queries. For example, you usually do not search the database table for a product
ID in forwarding order items for business reasons. For this reason, we do not provide database indexes for
archiving. The system in general performs a full table scan during preprocessing.
More Information
For more information about the Archive Information System, see SAP Library for SAP NetWeaver on SAP
Help Portal at http://help.sap.com/nw . Choose your release. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View, and choose
Archiving in the ABAP Application System
Solution Life Cycle Management
Data Archiving
Data Archiving with Archive Development Kit (ADK)
Data
Archive
Information System .
Related Information
Archiving [page 124]
3.3.2.2
Prerequisites for Archiving
To be considered for the preprocessing step in archiving, a business document must be closed for business (for
example, the life cycle status must be Completed or Canceled). In addition, the residence period for a business
document must be over.
The residence period is the minimum time in days between the date you closed a document and the date
the system considers the document for archiving. You can specify the residence period for the following
documents in Customizing for Cross-Application Components under
126
PUBLIC
Processes and Tools for Enterprise
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Applications
Reusable Objects and Functions for BOPF Environment
Archiving Adapter
Maintain BO-
Specific Residence Periods :
•
•
Areements
Rate Tables
We enable all the business objects in Transportation Management (TM) for archiving. You can review
the archiving objects that we have assigned to the business objects in Customizing for Cross-Application
Components under
BOPF Environment
Processes and Tools for Enterprise Applications
Archiving Adapter
Reusable Objects and Functions for
Maintain BO-Specific Archiving Objects .
To archive a master data object, the system must verify that the master data object is not used in an active
business document. The system uses the where-used framework (WUF) to verify this.
Related Information
Archiving [page 124]
Archiving for Master Data Objects [page 127]
3.3.2.3
Archiving for Master Data Objects
When the system archives a business document, it also archives the identifiers of any master data objects used
in the business document.
It is not critical if an active business document references a business document that has been archived. The
fact that the object has been archived usually only impacts a small number of business documents, and the
system can read the archived data from the archive database. A master data object can be used many times
across different business documents. Because of this, you must perform additional checks before you archive
a master data object.
Where-Used Framework
You can use the where-used framework (WUF) to identify the master data objects that are no longer being
used. Because of the limitation in the number of database indexes, there are only limited WUF searches
available for Transportation Management (TM). As a result, only a limited number of master data objects can
be archived.
Related Information
Archiving [page 124]
Where-Used Check for Objects [page 128]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
127
3.3.2.3.1
Where-Used Check for Objects
You can use transaction WUF_OBJCUST to review the objects that the where-used framework (WUF) includes in
its where-used check. You can use transaction WUF to detect and display dependencies.
The system checks if the object which is checked is used by an instance of the defined subobjects. The WUF
is used during archiving. If it does not find a usage, the object will be archived when the residence period is
reached.
The following are the objects that the WUF includes in its where-used search:
Master Data Object
Other Object in Which the WUF Searches
Business Partner (/SCMB/BUPA)
Location (APOLOC)
•
•
•
•
•
Request for quotation (RFQ) translator (/TMCSL/RFQ)
Exception template (/TMCSL/ET)
Commodity group (/TMCSL/COM_GROUP)
Named account group (/TMCSL/NAC)
Port group (/TMCSL/PORT_GROUP)
Agreement (/SCMTMS/AGREEMENT)
Related Information
Archiving for Master Data Objects [page 127]
Performing Where-Used Checks [page 128]
3.3.2.3.2
Performing Where-Used Checks
You can perform a where-used check for most master data objects.
Context
The following master data objects can be included in the check:
•
•
128
Locations
Business Partner
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Procedure
1. On the SAP Easy Access screen, choose
General Master Data Functions
SAP Transportation Management
SCM Basis
Master Data
WUF – Where-Used List .
2. On the Where-Used List screen, enter the object type you want to check.
3. In the Selection Criteria screen area, enter the object value you want to check.
For example, enter a business partner number in a business partner check.
4. Under Object Name on the left side of the screen, select the object you want to check.
5. On the right side of the screen, choose the appropriate hosting object.
For example, choose Agreement or Exception Template for a business partner.
Results
The system displays the where-used information for the hosting object you select.
Related Information
Archiving for Master Data Objects [page 127]
Where-Used Check for Objects [page 128]
3.3.2.4
Archiving for Business Objects
The following are the archiving object and business object combinations you can use in processes for SAP
Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA. You can use
transaction SARA (Archive Administration) to perform the archiving.
Business Object
Archiving Object
Documentation
Agreements
SCMTMSFAG
Enhanced Archiving Agreements and RFQ
Masters [page 130]
Rate Tables
SCMTMSTCRR
Archiving Rate Tables [page 131]
/SCMTMS/RA
/TMCSL/RA
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
129
More Information
For more information about data archiving, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw . Choose your release. Under Application Help, open SAP NetWeaver Library: FunctionOriented View, and choose
Application System
Solution Life Cycle Management
Data Archiving
Data Archiving with Archive Development Kit (ADK)
Data Archiving in the ABAP
Archive Information System .
Related Information
Archiving [page 124]
3.3.2.4.1
Enhanced Archiving Agreements and RFQ
Masters
The standard archiving object SCMTMSFAG is used for archiving and deleting agreements and freight agreement
RFQ masters in Transportation Management (TM).
The standard object is enhanced to support the archiving of forwarding agreement quotations (FWAQs) in SAP
Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA. The majority
of functions in the option for container shipping liners are the same as in the standard object for archiving
agreements and RFQ masters.
Structure
Programs
The following program is enhanced for SCMTMSFAG:
Program
Function
/SCMTMS/ARCH_FAG_PRE
Preprocessing
Prerequisites for Writing FWAQ Documents
If the following prerequisites are met, the system can archive a FWAQ:
•
•
130
The document was in the database for the entire residence period.
The document has the status Canceled or Completed
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
More Information
For more information about archiving agreements as part of TM standard features, see the product assistance
for Transportation Management in SAP S/4HANA on SAP Help Portal at https://help.sap.com/s4hana_op and
Enterprise Business Applications
choose your release. Open the product assistance and choose
Chain
Basic Functions
Management (TM)
Data Management in Transportation Management
Archiving Objects for Business Objects
Supply
Archiving in Transportation
Archiving Agreements and RFQ Masters (TM-MD-
CM-AG) .
Related Information
Archiving for Business Objects [page 129]
Archiving [page 124]
3.3.2.4.2
Archiving Rate Tables
You can use the archiving object SCMTMSTCRR to archive rate tables. You can use the archiving objects /
SCMTMS/RA and /SCMTMS/SC to partially archive rate tables and the underlying scale items. You can partially
archive rate tables and the corresponding scale items based on validity periods. You can use the archiving
object /TMCSL/RA to partially archive rate tables on rate line level.
Structure
Tables
Transportation Management (TM) uses the archiving objects SCMTMSTCRR and /SCMTMS/RA to archive
data from the nodes of the business object model /SCMTMS/TC_RATES. When using the archiving object /
SCMTMS/RA, the archiving object /SCMTMS/SC is also used to archive data from the nodes of the business
object model /SCMTMS/TC_SCALE.
SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA uses
the archiving object /TMCSL/RA to partially archive data from the rate typed node level of the enhancement
business object model /TMCSL/TC_RATES.
Programs
The following programs are available for SCMTMSTCRR:
Program
Function
/SCMTMS/ARCH_TCRATES_PRE
Preprocessing
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
131
Program
Function
/SCMTMS/ARCH_TCRATES_WRI
Write
/SCMTMS/ARCH_TCRATES_DEL
Delete
The following programs are available for /SCMTMS/RA and /SCMTMS/SC:
Program
Function
/SCMTMS/ARCH_TCRATEP_PRE
Preprocessing
/SCMTMS/ARCH_TCRATEP_WRI
Write
/SCMTMS/ARCH_TCSCALEP_WRI
Delete
/SCMTMS/ARCH_TCRATEP_DEL
/SCMTMS/ARCH_TCSCALEP_DEL
The following programs are available for /TMCSL/RA:
Program
Function
/TMCSL/ARCH_TCRATEP_PRE
Preprocessing
/TMCSL/ARCH_TCRATEP_WRI
Write
/TMCSL/ARCH_TCRATEP_DEL
Delete
You must perform the following steps to archive rate line data and the related business object (BO) nodes:
1. Execute the Preprocessing function for the rate table partial archiving for the required rate tables using
the /TMCSL/ARCH_TCRATEP_PRE program.
2. Execute the Write function for the rate table partial archiving for the required rate tables using the /TMCSL/
ARCH_TCRATEP_WRI program.
3. Execute the Delete function for the rate table partial archiving using the /TMCSL/ARCH_TCRATEP_DEL
program.
Prerequisites for Writing Rate Tables
The system can archive a rate table if the document has existed in the database for longer than the configured
residence period.
Functions
The Preprocessing and Write functions use the QU_FOR_CHECK_ARCHIVABILITY query to identify objects that
have not yet been archived.
The Preprocessing function uses the CHECK_ARCHIVABILITY action to check whether the object can be
archived. The archiving objects are given the archiving status Archiving in Process if they fulfill the following
prerequisites:
132
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
•
The non-archived rate table has existed in the database for longer than the business object (BO)-specific
residence period. The residence period is configured in Customizing for Cross-Application Components
under
Processes and Tools for Enterprise Applications
Reusable Objects and Functions for BOPF
Environment Archiving Adapter Maintain BO-Specific Residence Periods . The BO-specific residence
period starts from the creation date of the rate table.
•
For a globally created rate table, it is no longer referenced in any non-archived calculation sheets.
The Write function saves all archiving objects that have the status Archiving in Process in an archiving
document. You choose the option ILM Action: Archiving when executing the Write function. The system checks
the residence policy configured with transaction IRMPOL, for the ILM object SCMTMSTCRR and audit area
ARCHIVING. If the ILM end of residence duration is not reached for a rate table, the rate table will not be written
into the archiving document.
When partially archiving a rate table, the Preprocessing and Write functions use the
QU_FOR_CHECK_PARTIAL_ARCHIVABILITY query to identify objects that have not yet been archived. The
Preprocessing function uses the CHECK_PARTIAL_ARCHIVABILITY action to check firstly whether the nonarchived objects are completed and secondly whether their residence period has been reached.
When partially archiving a rate table at rate line level, the Preprocessing and Write functions use the
QU_FOR_CHECK_PARTIAL_ARCHIVABILITY query to identify objects that have not yet been archived. The
Preprocessing function uses the /TMCSL/PARTIAL_ARCHIVBILITY action to check firstly whether the nonarchived or partially archived objects are completed and secondly whether their residence period has been
reached.
Integration
Dependencies
All scales that are created from within a rate table are automatically marked for archiving when archiving
begins for the rate table. Rate tables that are created from within a calculation sheet are automatically marked
for archiving when archiving begins for the calculation sheet.
Before archiving, the system does not check for any references to master data objects used for charge
calculation in business documents such as forwarding orders, freight orders, and settlement documents.
You cannot edit or delete a rate table when the archiving status is Archiving in Process or Archived.
You cannot reference a rate table in a calculation sheet if the rate table is marked for archiving.
Displaying Archived Rate Tables
You can access archived rate tables in the relevant Archived Documents personal object worklist. You can also
use the archive information structure /SCMTMS/RATES for objects that have been archived using the archiving
object SCMTMSTCRR to access archived rate tables using the Archive Information System. Similarly, you can
use the archive information structures /SCMTMS/RAP and /SCMTMS/SCP for objects archived using archiving
objects /SCMTMS/RA and /SCMTMS/SC respectively to access archived rate table validity periods and scale
items using the Archive Information System.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
133
More Information
For more information about the Archive Information System, see SAP Library for SAP NetWeaver on SAP
Help Portal at http://help.sap.com/nw . Choose your release. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View, and choose
Archiving in the ABAP Application System
Solution Life Cycle Management
Data Archiving
Data Archiving with Archive Development Kit (ADK)
Data
Archive
Information System .
Related Information
Archiving for Business Objects [page 129]
Archiving [page 124]
3.3.2.5
ILM Objects for Business Objects
The following are the ILM object and business object combinations you can use for processes in SAP
Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA:
Business Object
ILM Object
Documentation
Rates
SCMTMSTCRR
ILM Objects for Rate Tables [page 135]
Rates (Partial)
TMCSLTCRR_PA
ILM Objects for Rate Tables (Partial)
[page 136]
Agreements
SCMTMSFAG
ILM Objects for Enhanced Agreements
[page 137]
More Information
For more information about SAP ILM, see SAP Library on http://help.sap.com/erp
open SAP Library and then choose
SAP ERP Cross-Application Functions
. Choose your release,
Cross-Application Components
SAP Information Lifecycle Management
Related Information
Archiving [page 124]
134
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.2.5.1
ILM Objects for Rate Tables
The ILM object SCMTMSTCRR is mapped to archiving object SCMTMSTCRR. You can find full information on
mapping of ILM objects to archiving objects using transaction IRM_CUST.
Available Policy Categories
Policy Category
Description
RST
Residence Rules
RTP
Retention Rules
 Note
The policy category RTP is delivered by Transportation Management (TM). The policy category RST is
provided by SAP Transportation Management, lead to agreement for container shipping liners for SAP
S/4HANA, for archiving the write process of rate tables using ILM residence rules.
 Note
The configurations for available time reference, available time offsets, and available condition fields are the
same as those delivered by TM.
More Information
For more information about the ILM object for rate tables, including other configurations, see the
product assistance for your SAP S/4HANA release on SAP Help Portal at https://help.sap.com/s4hana_op.
Open the Product Assistance, choose
Transportation Management (TM)
Transportation Management (TM)
Enterprise Business Applications
Supply Chain
Data Management in Transportation Management
ILM Objects for Business Objects
Basic Functions
Archiving in
SCMTMSTCRR - Rates .
Related Information
ILM Objects for Business Objects [page 134]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
135
3.3.2.5.2
ILM Objects for Rate Tables (Partial)
The ILM object TMCSLTCRR_PA is mapped to archiving object /TMCSL/RA. You can find full information on
mapping of ILM objects to archiving objects using transaction IRM_CUST.
Available Policy Categories
Policy Category
Description
RST
Residence Rules
RTP
Retention Rules
 Note
The policy category RTP is delivered by Transportation Management (TM). The policy category RST is
provided by SAP Transportation Management, lead to agreement for container shipping liners for SAP
S/4HANA, for archiving the write process of rate tables using ILM residence rules.
Available Condition Fields
Condition Field
Description
CATEGORY
Category
TCET
Charge Type
TCUSAGECD085
Charge Usage
For value determination for time references or condition fields use transaction IRM_CUST.
Related Information
ILM Objects for Business Objects [page 134]
136
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.2.5.3
ILM Objects for Enhanced Agreements
The ILM object SCMTMSFAG is mapped to archiving object SCMTMSFAG. You can find full information on
mapping of ILM objects to archiving objects using transaction IRM_CUST.
Available Policy Categories
Policy Category
Description
RST
Residence Rules
RTP
Retention Rules
 Note
The policy category RTP is delivered by Transportation Management (TM). The policy category RST is
provided by SAP TM, lead to agreement for container shipping liners for SAP S/4HANA for archiving the
write process of freight agreements using ILM residence rules.
Prerequisites for Writing Freight Agreement Documents
If the document was in the database for the entire residence period, the system can archive a freight
agreement.
 Note
The configurations for available time reference, available time offsets, and available condition fields are the
same as those delivered by TM.
More Information
For more information about the ILM objects for freight agreements, including other configurations, see
the product assistance for Transportation Management in SAP S/4HANA on SAP Help Portal at https://
help.sap.com/s4hana_op, and choose your version. Open the product assistance and choose
Business Applications
Supply Chain
Basic Functions
Archiving in Transportation Management (TM)
Enterprise
Data Management in Transportation Management
ILM Objects for Business Objects
SCMTMSFAG -
Agreements .
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
137
Related Information
ILM Objects for Business Objects [page 134]
3.3.3 Blocking and Deletion of Personal Data
When a business partner or location is created in the system, it is available for use by different business
documents, for example, partner agreement monitoring documents. Business partner or location master data
that is no longer required in the system can be first blocked and later destroyed.
Overview
The system uses an end of purpose (EoP) check to determine whether the business partner or location is still
relevant for business activities or can be blocked because the EoP has been reached.
The following business objects are included in the EoP check for the lead to agreement processes in the option
for container shipping liners:
Business Partner
Location
Not applicable
/SCMTMS/FREIGHTAGREEMENT
The following business objects that deal with master data and use business partner or location data are
excluded from the EoP check:
Business Partner
Location
TMCSL/EXCEPTION_TEMPLATE
/TMCSL/EXCEPTION_TEMPLATE
/TMCSL/RFQ_TRANSLATOR
/TMCSL/RFQ_TRANSLATOR
/TMCSL/COM_GROUP
Not applicable
/TMCSL/NAC_GROUP
Not applicable
/TMCSL/PORT_GROUP
Not applicable
For legal reasons, it may be necessary to retain personal data related to a business partner or a location in the
system for a specified period of time known as the retention period. The retention period is the total of the
residence period and the blocking period. As soon as the residence period is exceeded, the business partner
or location can be blocked and the blocking period starts. In this case, if the business partner or location is
blocked, access to the personal data is limited and is allowed only for users with a special authorization. After
the blocking period expires, which is also the end of the retention period, personal data of blocked business
partners and locations can be destroyed completely so that it can no longer be retrieved.
138
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
You use the SAP Information Lifecycle Management (ILM) component to support the deletion of personal data
and to control the deletion and blocking of business partner master data and location master data.
For residence and retention periods, ILM policies must be defined in the customer system.
For more information see:
•
•
•
Start of Retention Time (SoRT) [page 145]
End of Purpose Framework [page 143]
Handling of Blocked Business Partners and Locations [page 151]
Prerequisites
To use Data Protection and Privacy in the container shipping liners solution, the following settings are required:
•
You have activated the following business functions:
•
•
•
•
Information Lifecycle Management (ILM)
Business Partner ILM (BUPA_ILM_BF)
Location Master ILM-Deletion (/TMCSL/SCMB_LOC_ILM_1)
You have made the following Customizing settings:
•
Settings related to SAP ILM in Customizing for SAP NetWeaver under
Services
•
Basis
Information Lifecycle Management
Settings related to the blocking and deletion of business partner master data in Customizing for
Cross-Application Components under
•
Application Server
Data Protection
Blocking and Unblocking of Data
Settings related to the blocking and deletion of location master data in Customizing for Transportation
Management under
Master Data
Transportation Network
Location
Location Master Data
Deletion
•
Settings related to the direct output agent (DOA) in Customizing for Cross-Application Components
under
Cross-Application Components
Processes and Tools for Enterprise Applications
Objects and Functions for BOPF Environment
PPF Adapter for Output Management
Reusable
Maintain
Output Management Adapter Settings
•
You have run transaction IRMPOL and maintained the required policies for the application-specific ILM
objects and the master data ILM object CA_BUPA (for business partner) and the master data ILM object
SCMB_LOC (for locations).
•
You have run transaction BUS7 and activated the Data Protection and Privacy specific function modules for
business partner archiving events ARCH4 and DELE2.
In Transportation Management (TM), Data Protection and Privacy for locations supports the location types
Customer (1010), Transportation Service Provider (1020), and Vendor (1011).
For more information on the necessary settings see Customizing Settings for Data Protection and Privacy
[page 141].
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
139
End of Business Check
An end of business check confirms that the documents using a certain business partner or location are
completed in the context of Data Protection and Privacy, and therefore the business partner or location is no
longer used in the system. This means the system can start the retention process for the business partner or
location, assigning a start of retention time (SoRT).
For more information about the end of business conditions for TM documents, see Business-Object-Specific
End-of-Business Conditions [page 147].
For more information about SoRT, see Start of Retention Time (SoRT) [page 145].
End of Purpose Check
The business system provides a central report to process an EoP check and record the EoP status for business
partners or locations. If the defined residence time has elapsed since the SoRT, the report can block the
business partner or location.
For more information, see End of Purpose Framework [page 143].
Related Information
•
Security Guide for TM in SAP S/4HANA
For more information about security in TM in SAP S/4HANA, see http://help.sap.com/s4hana_op. Choose
the relevant release and under Product Documentation open Security Guide.
•
SAP Information Lifecycle Management
The SAP Information Lifecycle Management (SAP ILM) component supports the entire software lifecycle
including the storage, retention, blocking, and deletion of data.
For more information about SAP ILM, see http://help.sap.com/erp. Open the Application Help and
then choose
SAP ERP Cross-Application Functions
Cross-Application Components
SAP Information
Lifecycle Management .
140
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.3.1
Customizing Settings for Data Protection and
Privacy
The following Customizing settings enable you to use Data Protection and Privacy in SAP Transportation
Management, lead to agreement for container shipping liners for SAP S/4HANA.
SAP Information Lifecycle Management (ILM) Customizing and Policy
Settings
The basis for the blocking and deletion of personal data in Transportation Management (TM) is SAP
Information Lifecycle Management (ILM).
The following ILM-specific settings are necessary:
•
Define and maintain application rule groups
The application rule groups are used in the application-specific ILM policies and build the link between the
application-specific ILM policies and the business-partner-specific or location-specific ILM policies.
You can define an application rule group using transaction IRM_CUST_CSS for customer-specific settings
for ILM objects or in Customizing for SAP NetWeaver under
Information Lifecycle Management
•
Application Server
Retention Management
Basis Services
Make Customer-Specific Settings .
Define application rule variants
Application rule variants are used in the master-data-specific ILM policies of the following ILM objects:
ILM Object
Location
CA_BUPA
Archiving Business Partner
SCMB_LOC
Location Master Data
These application rule variants provide a mapping by which the system determines the correct residence
and retention times for a set of business partner or location data.
For more information about the use of application rule variants, see Using Application Rule Variants [page
147].
You can define an application rule variant and assign an application rule group to the application rule
variant in Customizing as follows:
•
Business Partner
See Customizing for Cross-Application-Components under
Unblocking of Data
•
Business Partner
Data Protection
Blocking and
Define and Store Application Rule Variants for EoP Check .
Locations
See Customizing for Transportation Management under
Location
Location Master Data Deletion
Master Data
Transportation Network
Assign Application Rule Variants and Rule Groups for EoP
Check .
•
ILM policies to be maintained
•
Retention period for all application-specific ILM objects
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
141
•
•
Residence period for master data ILM objects CA_BUPA and SCMB_LOC with audit area BUPA_DP
Retention period for master data ILM objects CA_BUPA and SCMB_LOC
You define ILM policies in one of the following ways:
•
In the menu for the ILM Retention Management Cockpit or the ILM Retention Warehouse Cockpit,
choose
•
ILM Rules
Edit Policies .
Use transaction IRMPOL.
For more information about the creation and handling of ILM policies, go to http://help.sap.com/erp and
see:
•
Editing ILM Policies
Application Help
SAP ERP Cross-Application Functions
Information Lifecycle Management
Cross-Application Components
SAP
Using ILM Retention Management in the Application System
Editing ILM Policies
•
Editing Residence Rules
Application Help
SAP ERP Cross-Application Functions
Information Lifecycle Management
Editing ILM Policies
•
Cross-Application Components
SAP
Using ILM Retention Management in the Application System
Editing Residence Rules
Processing Audit Areas
Application Help
SAP ERP Cross-Application Functions
Information Lifecycle Management
Cross-Application Components
SAP
Using ILM Retention Management in the Application System
Processing Audit Areas
Transportation Management Customizing Settings
The following TM-specific settings are necessary:
•
Activate direct output agent for business object
To enable the system to write start of retention time (SoRT) information, you must enable the direct output
agent (DOA) for the relevant business objects.
 Note
In the standard delivery, the DOA for the relevant business objects is disabled.
The table below shows the DOA configuration for the relevant business object:
Business Object
Node
Agent Name
/SCMTMS/FREIGHTAGREEMENT
Root
DPP_SORT_DETERMINATION
You can choose to handle the SoRT processing as a critical task (synchronous) or as an uncritical task
(asynchronous).
142
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
 Note
In the option for container shipping liners, the DOA for the business objects is configured as an
uncritical task (asynchronous).
You enable and maintain the DOA-specific settings in Customizing for Cross-Application Components
under
Processes and Tools for Enterprise Applications
Reusable Objects and Functions for BOPF
Environment PPF Adapter for Output Management Maintain Output Management Adapter Settings .
For more information about SoRT, see Start of Retention Time (SoRT) [page 145].
•
Activate Data Protection and Privacy-relevant function modules for business partner archiving events
To enable the system to delete the database table containing the SoRT information when a business
partner is finally deleted, you need to activate the following function modules related to business partner
archiving events ARCH4 and DELE2:
Archiving Event
Function Module
ARCH4 – Archiving: Delete Archived Data
/SCMTMS/DPP_BUPA_EVENT_ARCH4
DELE2 – Deletion Program: Delete
/SCMTMS/DPP_BUPA_EVENT_DELE2
You run transaction BUS7 to activate the above function modules.
Related Information
Using Application Rule Variants [page 147]
3.3.3.2
End of Purpose Framework
The system provides a central blocking report to process an end of purpose check and record the end of
purpose status of business partner and location master data. The various stages in this process are outlined
below.
End of Business
As soon as a business document such as a forwarding agreement document is completed, the business has
ended for the business partner or location with respect to this document. As soon as all documents in which
the business partner or location is used are completed, the end of business for the business partner or location
is reached. End of business designates the start of retention time (SoRT) for the data.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
143
Residence Period
The residence period is the defined period of time that must be exceeded before application data can be
blocked or archived after the SoRT. During residence time, the data is still available to all users in the
system. The residence periods are defined in the Information Lifecycle Management (ILM) policies of the
corresponding ILM objects as follows:
Master Data
ILM Object
Business Partner
CA_BUPA
Location
SCMB_LOC
The system selects the longest residence time as the final residence time.
If the residence period is exceeded, the end of purpose of the business partner or location is reached and it can
be blocked.
End of Purpose
A business partner or location has reached end of purpose when:
•
•
There are no open business documents in the system using the business partner or location.
The residence time for the business partner or location has elapsed.
If a business partner or location has never had any business in the system, it can be blocked immediately
without considering a residence time.
Blocking Period
Once the business partner or location reaches end of purpose, the blocking period starts and the system
can block it. During the blocking period, access to the personal data of the business partner or location is
restricted. Blocking of data can impact the system behavior.
Retention Period
The retention period is the defined period of time that must be exceeded before application data can be
destroyed after the SoRT. The retention period is the total of the residence period and blocking period. When
the specified retention time elapses, the system can delete the data.
The retention periods for business partners are defined in the ILM policies for ILM object CA_BUPA. The
retention periods for locations are defined in the ILM policies for ILM object .
144
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.3.2.1
Start of Retention Time (SoRT)
Start of retention time (SoRT) designates the end of business (EoB) for business partners and locations.
The SoRT is required to determine the end of purpose (EoP) according to the defined Information Lifecycle
Management (ILM) policies and rules.
In SAP Transportation Management, lead to agreement for container shipping liners, the SoRT information is
handled in two steps as follows:
•
Determination of the SoRT information
Once a business document is completed and is saved, the system determines and stores the SoRT
information in a database table according to business partner or location, business object, and application
rule variant.
•
Use of the SoRT information
During the EoP check, the system consults the database table containing the SoRT information to
determine the relevant SoRT, and based on that, the correct end of residence period according to the
maintained ILM policies and rules.
Determination of the SoRT Information
As soon as a business document is saved, the system checks if the document is completed in the context
of Data Protection and Privacy. In this case, the system determines the SoRT information and stores it in a
database table.
For more information on the conditions to be fulfilled to deem a document to have reached its end of business,
see Business-Object-Specific End-of-Business Conditions [page 147].
SAP Transportation Management uses the direct output agent (DOA) DPP_SORT_DETERMINATION to trigger
the SoRT determination.
In SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA, the
DOA is configured for the business object /SCMTMS/FREIGHTAGREEMENT.
You enable and maintain the DOA for the above business objects in Customizing for Cross-Application
Components under
BOPF Environment
Processes and Tools for Enterprise Application
PPF Adapter for Output Management
Reusable Objects and Functions for
Maintain Output Management Adapter Settings .
For more information, see Customizing Settings for Data Protection and Privacy [page 141].
You can choose to handle the update of the SoRT information in two different modes:
•
Non-exclusive write lock
Allows multiple updates.
•
Exclusive write lock:
The table is locked until the COMMIT is finished.
 Note
The standard delivery uses the non-exclusive write lock. Using the exclusive write lock may have
implications for system performance.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
145
You can implement the Business Add-In (BAdI) method DETERMINE_SORT_WRITE_MODE of the Business
Add-In (BAdI) /SCMTMS/BADI_DPP to overwrite the standard setting.
For more information, see the following Customizing activities:
•
For business partners, see Customizing for Transportation Management under
(BAdIs) for Transportation Management
Master Data
Business Partners
Business Add-Ins
Data Protection
BAdI: Data
Protection and Privacy .
•
For locations, see Customizing for Transportation Management under
for Transportation Management
Master Data
Business Add-Ins (BAdIs)
Transportation Network
Location
Data Protection
BAdI: Data Protection and Privacy .
Use of the SoRT Information
During the EoP check for a business partner or location, the system determines the relevant SoRT information
from the database table containing the SoRT information. The SoRT information is required to determine the
relevant ILM policies and to calculate the correct EoP time depending on the defined ILM policies.
Excluded Business Documents
Certain business objects that deal with master data are excluded from the data destruction process and are
therefore also excluded from the SoRT handling. The system handles these master data objects and their
use of business-partner-related or location-related data in the archiving process or the location destruction
process. As soon as a business partner or location is archived or deleted, the system runs a where-used check
that includes such master data. Thus, it is not possible to archive or delete a business partner or location as
long as such documents are still in use in the system.
Related Information
Customizing Settings for Data Protection and Privacy [page 141]
Business-Object-Specific End-of-Business Conditions [page 147]
146
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.3.2.2
Business-Object-Specific End-of-Business
Conditions
The following table lists the lead to agreement business objects that the system considers during the end of
purpose (EoP) check and the end of business (EoB) condition:
New Business Object for Container
Shipping Liners or Enhanced Stand­
Business Object
EoB Condition
ard Business Object
Agreements (FAG)
Agreement Status: Deactivated
Enhanced Standard Business Object
RFQ/Quotation Status:
Enhanced Standard Business Object
Agreement Category:
•
•
Initial
Service Product
Agreements (FAG)
Agreement Category:
•
•
•
RFQ
•
•
Completed
Canceled
RFQ Assignment
FWAQ Child
3.3.3.2.3
Using Application Rule Variants
Application rule variants provide a mapping that allows the system to determine the correct end of residence
and retention date for a set of business partner or location data.
Context
The use of application rule variants is necessary if the system has to consider more than one residence or
retention rule in an application where business partner or location data is used.
Procedure
1. You define application rule groups.
To use the concept of application rule variants, you need to define application rule groups. These rule
groups are used in the application-specific Information Lifecycle Management (ILM) policies and provide
the link between the application-specific ILM policies and the business-partner-specific or location-specific
ILM policies. The business-partner-specific or location-specific ILM policies use the application rule
variant.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
147
For more information, see Customizing for SAP NetWeaver under
Information Lifecycle Management
(transaction IRM_CUST_CSS.)
Retention Management
Application Server
Basis Services
Make Customer-Specific Settings
2. You define an application rule variant.
You create an application rule variant and assign an application rule group to a variant in Customizing as
follows:
•
Business partners
See Customizing for Cross-Application Components under
Unblocking of Data
•
Business Partner
Data Protection
Blocking and
Define and Store Application Rule Variants for EOP Check .
Locations
See Customizing for Transportation Management under
Location
Location Master Deletion
Master Data
Transportation Network
Assign Application Rule Variants and Rule Groups for EoP
Check .
 Note
For container shipping liner processes, the specific ILM objects and the related condition fields
are available as part of the container shipping liners option. The customer is responsible for the
maintenance of policies and application rule variants.
3. You edit policies.
•
Application-specific policies
If the usage of an application rule group is activated for the ILM object, then the field application rule
group is available in the policy.
•
Business-partner-specific and location-specific policies
The application rule variant is available as a condition field and can be included in the policy assigned
to, for example, CA_BUPA for business partner and SCMB_LOC for locations. The application rule variant
is linked to an application rule group.
For more information about editing policies, see http://help.sap.com/erp. Open the Application Help
and choose
SAP ERP Cross-Application Functions
Lifecycle Management
Cross-Application Components
Using ILM Retention Management in the Application System
SAP Information
Editing ILM
Policies .
Related Information
Example: Application Rule Variants [page 149]
148
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.3.2.3.1 Example: Application Rule Variants
The following example refers to an application rule variant with the Information Lifecycle Management (ILM)
object CA_BUPA. The same procedure applies to the ILM object SCMB_LOC.
You want to define a specific residence and retention period for business partners ILM object CA_BUPA based
on the transportation mode category of a transportation request (TRQ). To achieve this, you use an application
rule variant.
You want to define different residence and retention periods according to the mode of transport category as
follows:
•
•
Road - 1 year
Ocean - 3 years
You first define an application rule group for each of these mode of transport categories, named ROAD and
OCEAN respectively. For each application rule group, you assign the fields that define the retention time as
follows:
•
•
You specify that the retention period for both is to be measured in years.
You specify the retention times required for each group as follows:
•
•
Road - 1 year
Ocean - 3 years
Once you have created an application rule group, you activate the use of rule groups for the relevant ILM
object SCMTMSTRQ. Now, it is possible to maintain ILM policies for ILM object SCMTMSTRQ depending on the
different application rule groups (ROAD and OCEAN). In the next step, you define the application rule variants
TRQ_ROAD and TRQ_OCEAN and link them to application rule groups ROAD and OCEAN.
The application rule variants (TRQ_ROAD and TRQ_OCEAN) are now available for inclusion in the ILM policies of
business partner ILM object CA_BUPA.
Finally, you define policies for business partner ILM object CA_BUPA. By specifying one of the defined variants
you can vary the residence and retention times according to the mode of transport category.
Related Information
Using Application Rule Variants [page 147]
3.3.3.2.4
Business-Object-Specific Settings to Write SoRT
Information
Transportation Management (TM) uses the direct output agent (DOA) to write the start of retention time
(SoRT) information for each business object.
The following DOA output management settings are delivered for each relevant business object. As default, the
direct output agents in the context of Data Protection and Privacy are disabled.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
149
Settings
Value
Node
Root
Agent Name
DPP_SORT_DETERMINATION
Synchronous/Asynchronous
B Has Uncritical o/p: Process after Commit (background)
Processor Class
/SCMTMS/CL_OUTMGMT_DOA_DPP
Enable
No
For each business object to be considered with respect to Data Protection and Privacy, the DOA needs to be
enabled.
For more information, see Customizing for Cross-Application Components under
Processes and Tools for
Enterprise Applications
PPF Adapter for Output
Management
Reusable Objects and Functions for BOPF Environment
Maintain Output Management Adapter Settings .
Related Information
End of Purpose Framework [page 143]
3.3.3.2.5
Rebuilding of SoRT Information
You can use report /SCMTMS/R_EOP_INDEX_REBUILD to rebuild the start of retention time (SoRT) information
for a specific combination of business object and business partner.
This may be necessary, for example, in the following cases:
•
You want to initially build the SoRT information for existing business documents for one of the following
reasons:
•
•
•
•
•
150
You are using Data Protection and Privacy functions for the first time.
You activate switch BUPA_ILM_SWITCH or switch /SCMB/LOC_ILM_SFW_01 for the first time.
You activate switch BUPA_ILM_SWITCH or switch /SCMB/LOC_ILM_SFW_01, but the direct output
agent is disabled and will be enabled in a later step.
SoRT information is missing for some business documents.
New application rule variants or policies are introduced in the Information Lifecycle Management (ILM)
component, and thus new residence times become relevant.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
System Performance Considerations
For system performance reasons, the report can be started in parallel mode. If you choose to run multiple work
processes, the system groups documents into packages and runs parallel work processes to determine the
SoRT information.
You can specify a maximum number of processes to run and can limit the size of packages by specifying the
maximum number of documents to be included in a package.
3.3.3.3
End of Purpose Check
The system uses the end of purpose (EoP) check to decide whether it can block a business partner or location.
A central blocking report calls the EoP check for each registered application, including SAP Transportation
Management, lead to agreement for container shipping liners for SAP S/4HANA.
The following table shows the blocking report for each business object.
Master Data
Report
Business Partner
BUPA_PREPARE_EOP
Location
/SCMB/RLOC_PREPARE_EOP
In SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA, a
business partner or location is deemed to have reached EoP if:
•
•
It is not used in any container shipping liners business document.
There are no open business documents relevant to the business partner or location. All existing documents
using the business partner or location are completed.
In the container shipping liners setup, the system considers business documents of the following business
objects:
•
•
Location: /SCMTMS/FREIGHTAGREEMENT
The residence period defined in the relevant Information Lifecycle Management (ILM) policies for the
business partner or location has elapsed.
As soon as a business partner or location has reached its EoP, the system can block it.
3.3.3.4
Handling of Blocked Business Partners and
Locations
Blocking of data can impact the system behavior in the following ways:
•
Display
The system does not display personal data of a blocked business partner or location.
•
Change
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
151
It is not possible to change a completed business document that contains a blocked business partner or
location.
•
Create
It is not possible to create a business document using a blocked business partner or location. As soon as a
blocked business partner or location is entered, the system raises an error message.
•
Search
The system does not display blocked business partners or locations in the result list of search helps. The
same is true for technical queries on the business object for business partners /SCMTMS/BUPA and the
business object for locations /SCMTMS/LOCATION.
Special Authorization
•
Business Partner
It is possible to display blocked data if a user has special authorization (PFCG rule:
SAP_CA_BP_DP_ADMIN); however, it is still not possible to create or change completed business
documents that contain a blocked business partner.
•
Location
To display a blocked location, you need the authorization for authorization object /TMCSL/LOC combined
with the appropriate authorization group settings in Customizing. You can define the authorization group in
Customizing for Transportation Management under
Location Master Deletion
3.3.3.5
Master Data
Transportation Network
Location
Define Authorization Group Indicating Blocked Master Data .
Destruction Objects for Business Objects
The following table lists the destruction object and business object combinations that you can use in processes
for SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA.
You can use transaction ILM_DESTRUCTION (Data Destruction) to perform the destruction. Transaction code
DOBJ can be used to configure data destruction objects.
Business Object
Destruction Object
Documentation
Exception Templates
/TMCSL/EXCEPTION_TEM_DE­
Destructing Exception Templates [page
STRUCT
153]
RFQ Translator
Commodity Groups
/TMCSL/RFQ_TRANSLATOR_DE­
Destructing RFQ Translator Data [page
STRUCT
155]
/TMCSL/COM_GROUP
Destructing Commodity Groups [page
157]
Named Account Groups
/TMCSL/NAC_GROUP
Destructing Named Account Groups
[page 159]
152
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Business Object
Destruction Object
Documentation
Port Zone Groups
/TMCSL/PORT_GROUP
Destructing Port Zone Groups [page
161]
3.3.3.5.1
Destructing Exception Templates
Use the data destruction object /TMCSL/EXCEPTION_TEM_DESTRUCT to destroy exception template data that
is no longer relevant following the expiry of its retention period. As the data is not archived, you can use the
data destruction program to delete it and thus reduce the amount of stored data.
Prerequisites
You need the following authorizations for data destruction:
Authorization Object
Description
S_ARCD_OBJ
Execute data destruction run for data in the database
S_ARCD_RES
Include resources in deletion packages
S_ARCD_RUN
Execute data destruction run
Context
Program
You can run the following SAP NetWeaver Information Lifecycle Management (ILM) enabled program with data
destruction (transaction ILM_DESTRUCTION) for this data destruction object:
Function
Program
Destroy
/TMCSL/EXCEPTION_TEMPLATE_DES
Business Object
The data destruction program destroys all data from the business object /TMCSL/EXCEPTION_TEMPLATE
(Surcharge Exception Template).
Standard Fields for ILM Object
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
153
This data destruction object supports the ILM function for destroying data. You use the following standard
fields to create ILM policies (transaction IRMPOL) for the data destruction object. The ILM object
TMCSL_EXCEPTION_TEMP_DESTRUCT belongs to this data destruction object.
Available Time Reference
The retention period for the data starts on the COMPLETION_DATE (End Date), which uses the following
database attribute to determine the start date:
Source Field
Description
CHANGED_ON
Created On
Available Condition Fields
Condition Field
Description
EXCEPTION_TYPE
Exception Template Type
TEMPLATE_ID
Exception Template ID
Available Policy Categories
Policy Category
Description
RTP
Retention Rules
Procedure
1. Start transaction ILM_DESTRUCTION (Data Destruction).
2. In the Type of Data to Be Destroyed group box, select the Data from the Database radio button.
3. In the Restrictions group box, enter the ILM object TMCSL_EXCEPTION_TEMP_DESTRUCT.
4. Choose Execute.
5. On the Data Destruction from the Database: Initial Entry screen, choose the action Destroy.
6. Define at least one variant for the data destruction program.
You can restrict the data to be selected for destruction by the data destruction program by entering
specific criteria.
7. Define a start date and the spool parameters for the data destruction run.
8. Choose Execute.
Related Information
Destruction Objects for Business Objects [page 152]
154
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.3.5.2
Destructing RFQ Translator Data
Use the data destruction object /TMCSL/RFQ_TRANSLATOR_DESTRUCT to destroy RFQ Translator data that is
no longer relevant following the expiry of its retention period. As the data is not archived, you can use the data
destruction program to delete it and thus reduce the amount of stored data.
Prerequisites
You need the following authorizations for data destruction:
Authorization Object
Description
S_ARCD_OBJ
Execute data destruction run for data in the database
S_ARCD_RES
Include resources in deletion packages
S_ARCD_RUN
Execute data destruction run
Context
Program
You can run the following SAP NetWeaver Information Lifecycle Management (ILM) enabled program with data
destruction (transaction ILM_DESTRUCTION) for this data destruction object:
Function
Program
Destroy
/TMCSL/RFQ_TRANSLATOR_DES
Business Object
The data destruction program destroys all data from the business object /TMCSL/RFQ_TRANSLATOR (RFQ
Translator).
Standard Fields for ILM Object
This data destruction object supports the ILM function for destroying data. You use the following standard
fields to create ILM policies (transaction IRMPOL) for the data destruction object. The ILM object
TMCSL_RFQ_TRANSLATOR_DESTRUCT belongs to this data destruction object.
Available Time Reference
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
155
The retention period for the data starts on the COMPLETION_DATE (End Date), which uses the following
database attribute to determine the start date:
Source Field
Description
CHANGED_ON
Created On
Available Condition Fields
Condition Field
Description
EXCEPTION_TYPE
Exception Template Type
TEMPLATE_ID
Exception Template ID
Available Policy Categories
Policy Category
Description
RFQ_ID
RFQ ID
RFQ_TYPE
RFQ Translator - RFQ Type
Procedure
1. Start transaction ILM_DESTRUCTION (Data Destruction).
2. In the Type of Data to Be Destroyed group box, select the Data from the Database radio button.
3. In the Restrictions group box, enter the ILM object TMCSL_RFQ_TRANSLATOR_DESTRUCT.
4. Choose Execute.
5. On the Data Destruction from the Database: Initial Entry screen, choose the action Destroy.
6. Define at least one variant for the data destruction program.
You can restrict the data to be selected for destruction by the data destruction program by entering
specific criteria.
7. Define a start date and the spool parameters for the data destruction run.
8. Choose Execute.
Related Information
Destruction Objects for Business Objects [page 152]
156
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.3.5.3
Destructing Commodity Groups
Use the data destruction object /TMCSL/COM_GROUP to destroy commodity group data that is no longer
relevant following the expiry of its retention period. As this data is not archived, you can delete the data using
the data destruction program and thus restrict the amount of data contained in the tables.
Prerequisites
You need the following authorizations for data destruction:
Authorization Object
Description
S_ARCD_OBJ
Execute data destruction run for data in the database
S_ARCD_RES
Include resources in deletion packages
S_ARCD_RUN
Execute data destruction run
Context
Program
You can run the following SAP NetWeaver Information Lifecycle Management (ILM) enabled program with data
destruction (transaction ILM_DESTRUCTION) for this data destruction object:
Function
Program
Destroy
TMCSL/COM_GROUP_DES
Business Object
The data destruction program destroys all data from the business object /TMCSL/COM_GROUP (Commodity
Group).
Standard Fields for ILM Object
This data destruction object supports the ILM function for destroying data. You use the following standard
fields to create ILM policies (transaction IRMPOL) for the data destruction object. The ILM object TMCSLCOMG
belongs to this data destruction object.
Available Time Reference
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
157
The retention period for the data starts on the COMPLETION_DATE (End Date), which uses the following
database attribute to determine the start date:
Source Table
Source Field
Description
/TMCSL/D_COM_GRP
CHANGED_ON
Changed On
Available Condition Fields
Condition Field
Description
COM_GRP_ID
Commodity Group ID
Available Policy Categories
Policy Category
Description
RTP
Retention Rules
Procedure
1. Start transaction ILM_DESTRUCTION (Data Destruction).
2. In the Type of Data to Be Destroyed group box, select the Data from the Database radio button.
3. In the Restrictions group box, enter the ILM object TMCSLCOMG.
4. Choose Execute.
5. On the Data Destruction from the Database: Initial Entry screen, choose the action Destroy.
6. Define at least one variant for the data destruction program.
You can restrict the data to be selected for destruction by the data destruction program by entering
specific criteria.
7. Define a start date and the spool parameters for the data destruction run.
8. Choose Execute.
Related Information
Destruction Objects for Business Objects [page 152]
158
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.3.5.4
Destructing Named Account Groups
Use the data destruction object /TMCSL/NAC_GROUP to destroy named account group data that is no longer
relevant following the expiry of its retention period. As this data is not archived, you can delete the data using
the data destruction program and thus restrict the amount of data contained in the tables.
Prerequisites
You need the following authorizations for data destruction:
Authorization Object
Description
S_ARCD_OBJ
Execute data destruction run for data in the database
S_ARCD_RES
Include resources in deletion packages
S_ARCD_RUN
Execute data destruction run
Context
Program
You can run the following SAP NetWeaver Information Lifecycle Management (ILM) enabled program with data
destruction (transaction ILM_DESTRUCTION) for this data destruction object:
Function
Program
Destroy
/TMCSL/NAC_GROUP_DES
Business Object
The data destruction program destroys all data from the business object /TMCSL/NAC_GROUP (Named
Account Group).
Standard Fields for ILM Object
This data destruction object supports the ILM function for destroying data. You use the following standard
fields to create ILM policies (transaction IRMPOL) for the data destruction object. The ILM object TMCSLCOMG
belongs to this data destruction object.
Available Time Reference
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
159
The retention period for the data starts on the COMPLETION_DATE (End Date), which uses the following
database attribute to determine the start date:
Source Table
Source Field
Description
/TMCSL/D_NAC_GRP
CHANGED_ON
Changed On
Available Condition Fields
Condition Field
Description
NAC_GRP_ID
Named Account Group ID
Available Policy Categories
Policy Category
Description
RTP
Retention Rules
Procedure
1. Start transaction ILM_DESTRUCTION (Data Destruction).
2. In the Type of Data to Be Destroyed group box, select the Data from the Database radio button.
3. In the Restrictions group box, enter the ILM object TMCSLNAC.
4. Choose Execute.
5. On the Data Destruction from the Database: Initial Entry screen, choose the action Destroy.
6. Define at least one variant for the data destruction program.
You can restrict the data to be selected for destruction by the data destruction program by entering
specific criteria.
7. Define a start date and the spool parameters for the data destruction run.
8. Choose Execute.
Related Information
Destruction Objects for Business Objects [page 152]
160
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.3.5.5
Destructing Port Zone Groups
Use the data destruction object /TMCSL/PORT_GROUP to destroy port zone group data that is no longer
relevant following the expiry of its retention period. As this data is not archived, you can delete the data using
the data destruction program and thus restrict the amount of data contained in the tables.
Prerequisites
You need the following authorizations for data destruction:
Authorization Object
Description
S_ARCD_OBJ
Execute data destruction run for data in the database
S_ARCD_RES
Include resources in deletion packages
S_ARCD_RUN
Execute data destruction run
Context
Program
You can run the following SAP NetWeaver Information Lifecycle Management (ILM) enabled program with data
destruction (transaction ILM_DESTRUCTION) for this data destruction object:
Function
Program
Destroy
/TMCSL/PORT_GROUP_DES
Business Object
The data destruction program destroys all data from the business object /TMCSL/PORT_GROUP (Port
Group).
Standard Fields for ILM Object
This data destruction object supports the ILM function for destroying data. You use the following standard
fields to create ILM policies (transaction IRMPOL) for the data destruction object. The ILM object TMCSLPRTG
belongs to this data destruction object.
Available Time Reference
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
161
The retention period for the data starts on the COMPLETION_DATE (End Date), which uses the following
database attribute to determine the start date:
Source Table
Source Field
Description
/TMCSL/D_PRT_GRP
CHANGED_ON
Changed On
Available Condition Fields
Condition Field
Description
PORT_ZONE_GRP_ID
Port Zone Group ID
Available Policy Categories
Policy Category
Description
RTP
Retention Rules
Procedure
1. Start transaction ILM_DESTRUCTION (Data Destruction).
2. In the Type of Data to Be Destroyed group box, select the Data from the Database radio button.
3. In the Restrictions group box, enter the ILM object TMCSLPRTG.
4. Choose Execute.
5. On the Data Destruction from the Database: Initial Entry screen, choose the action Destroy.
6. Define at least one variant for the data destruction program.
You can restrict the data to be selected for destruction by the data destruction program by entering
specific criteria.
7. Define a start date and the spool parameters for the data destruction run.
8. Choose Execute.
Related Information
Destruction Objects for Business Objects [page 152]
3.3.3.6
ILM Objects for Business Objects
The Information Lifecycle Management (ILM) framework calculates the longest retention period starting from
the start of retention time (SoRT) based on the retention times maintained for the business partner or the
162
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
location in ILM. With this, the framework can determine how long the business partner or location is blocked
and the date at which it can be destroyed.
The business partner can be archived during the blocking period if required. When the business partner or
location has reached the end of retention, the system deletes it. If the rate of growth of the volume of business
object data is so low that data archiving is not needed, then an alternative method for data destruction is
provided in the option for container shipping liners through a data destruction object. The following table
lists the ILM object and business object combinations that you can use for processes in SAP Transportation
Management, lead to agreement for container shipping liners for SAP S/4HANA:
Business Object
ILM Object
Exception Template
TMCSL_EXCEPTION_TEMP_DE­
ILM Objects for Exception Templates
STRUCT
[page 163]
TMCSL_RFQ_TRANSLATOR_DE­
ILM Objects for RFQ Translator [page
STRUCT
165]
TMCSLCOMG
ILM Objects for Commodity Groups
Bill of Lading
RFQ Translator
Commodity Groups
Documentation
[page 166]
Named Account Groups
TMCSLNAC
ILM Objects for Named Account Groups
[page 167]
Port Zone Groups
TMCSLPRTG
ILM Objects for Port Zone Groups [page
168]
You can use transaction ILM_DESTRUCTION (Data Destruction) to perform the data destruction.
For more information about SAP ILM, see http://help.sap.com/erp
choose
SAP ERP Cross-Application Functions
. Open Application Help and
Cross-Application Components
SAP Information Lifecycle
Management
3.3.3.6.1
ILM Objects for Exception Templates
The Information Lifecycle Management (ILM) object TMCSL_EXCEPTION_TEMP_DESTRUCT ( Exception
Template) is mapped to destruction object /TMCSL/EXCEPTION_TEM_DESTRUCT. You can find full information
about the mapping of ILM objects to destruction objects using transaction IRM_CUST.
Available Policy Categories
Policy Category
Description
RTP
Retention Rules
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
163
 Note
The policy category RST - Residence Rules is not applicable for the exception template process since
there’s no end of purpose concept for exception templates.
Available Time Reference
Information Retention Manager (IRM) Constant
Description
COMPLETION_DATE
End Date
Available Time Offsets
IRM Constant
Description
END_OF_MONTH
End of Month
END_OF_QUARTER
End of Quarter
END_OF_YEAR
End of Year
Available Condition Fields
Condition Field
Description
EXCEPTION_TYPE
Exception Template Type
TEMPLATE_ID
Exception Template ID
For value determination of time references or condition fields use transaction IRM_CUST.
Related Information
ILM Objects for Business Objects [page 162]
164
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
3.3.3.6.2
ILM Objects for RFQ Translator
The Information Lifecycle Management (ILM) object TMCSL_RFQ_TRANSLATOR_DESTRUCT (RFQ Translator) is
mapped to destruction object /TMCSL/RFQ_TRANSLATOR_DESTRUCT. You can find full information about the
mapping of ILM objects to destruction objects using transaction IRM_CUST.
Available Policy Categories
Policy Category
Description
RTP
Retention Rules
 Note
The policy category RST - Residence Rules is not applicable for the RFQ Translator process since there’s no
end of purpose concept for RFQ Translator.
Available Time Reference
Information Retention Manager (IRM) Constant
Description
COMPLETION_DATE
End Date
Available Time Offsets
IRM Constant
Description
END_OF_MONTH
End of Month
END_OF_QUARTER
End of Quarter
END_OF_YEAR
End of Year
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
165
Available Condition Fields
Condition Field
Description
RFQ_ID
RFQ ID
RFQ_TYPE
RFQ Translator - RFQ Type
For value determination of time references or condition fields use transaction IRM_CUST.
Related Information
ILM Objects for Business Objects [page 162]
3.3.3.6.3
ILM Objects for Commodity Groups
The Information Lifecycle Management (ILM) object TMCSLCOMG (Commodity Group) is mapped to destructing
object /TMCSL/COM_GROUP. You can find full information on the mapping of ILM objects to archiving objects
using transaction IRM_CUST.
Available Policy Categories
Policy Category
Description
RTP
Retention Rules
 Note
The policy category RST - Residence Rules is not applicable for the commodity group process since there’s
no end of purpose concept for commodity groups.
Available Time Reference
Information Retention Manager (IRM) Constant
Description
COMPLETION_DATE
End Date
166
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
Available Time Offsets
IRM Constant
Description
END_OF_MONTH
End of Month
END_OF_QUARTER
End of Quarter
END_OF_YEAR
End of Year
Available Condition Fields
Condition Field
Description
COM_GRP_ID
Commodity Group ID
For value determination of time references or condition fields use transaction IRM_CUST.
3.3.3.6.4
ILM Objects for Named Account Groups
The Information Lifecycle Management (ILM) object TMCSLNAC (Named Account Group) is mapped to
destructing object /TMCSL/NAC_GROUP. You can find full information on the mapping of ILM objects to
archiving objects using transaction IRM_CUST.
Available Policy Categories
Policy Category
Description
RTP
Retention Rules
 Note
The policy category RST - Residence Rules is not applicable for the named account group process since
there’s no end of purpose concept for named account groups.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
167
Available Time Reference
Information Retention Manager (IRM) Constant
Description
COMPLETION_DATE
End Date
Available Time Offsets
IRM Constant
Description
END_OF_MONTH
End of Month
END_OF_QUARTER
End of Quarter
END_OF_YEAR
End of Year
Available Condition Fields
Condition Field
Description
NAC_GRP_ID
Named Account Group ID
For value determination of time references or condition fields use transaction IRM_CUST.
3.3.3.6.5
ILM Objects for Port Zone Groups
The Information Lifecycle Management (ILM) object TMCSLPRTG (Port Zone Group) is mapped to destructing
object /TMCSL/PORT_GROUP. You can find full information on the mapping of ILM objects to archiving objects
using transaction IRM_CUST.
Available Policy Categories
Policy Category
Description
RTP
Retention Rules
168
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
 Note
The policy category RST - Residence Rules is not applicable for the port zone group process since there’s
no end of purpose concept for port zone groups.
Available Time Reference
Information Retention Manager (IRM) Constant
Description
COMPLETION_DATE
End Date
Available Time Offsets
IRM Constant
Description
END_OF_MONTH
End of Month
END_OF_QUARTER
End of Quarter
END_OF_YEAR
End of Year
Available Condition Fields
Condition Field
Description
PORT_ZONE_GRP_ID
Port Zone Group ID
For value determination of time references or condition fields use transaction IRM_CUST.
3.3.3.7
Enhancement Options for Blocking and Deletion
You can use the Business Add-In (BAdI) /SCMTMS/BADI_DPP to overwrite some standard settings or results for
Data Protection and Privacy in Transportation Management (TM). It enables you, for example, to define your
own end of business (EoB) conditions.
For more information, see:
•
Business Partners
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
169
Customizing for Transportation Management under
Management
•
Master Data
Business Partners
Business Add-Ins (BAdIs) for Transportation
Data Protection
BAdI: Data Protection and Privacy .
Locations
Customizing for Transportation Management under
Management
Master Data
Transportation Network
Business Add-Ins (BAdIs) for Transportation
Location
Data Protection
BAdI: Data
Protection and Privacy .
3.3.4 Change Tracking
You can use this function to display which data was changed, how it was changed, when it was changed, and by
whom it was changed for the following business documents:
•
•
•
•
Rate Table
Agreement
Exception Template
RFQ Translator
Prerequisites
•
Change tracking is enabled by default for each business document. Make sure that there are no business
objects maintained with the Enable Change Document field as No in Customizing for Transportation
Management under
Container Shipping Liners
Basic Settings
Maintain Change Document Settings
for Business Object .
•
Make sure you have maintained the following change document objects in Customizing for CrossApplication Components under
Functions for BOPF Environment
170
Processes and Tools for Enterprise Applications
Maintain BO-Specific Change Document Objects :
Business Object
Change Document Object
/SCMTMS/TC_RATES
/TMCSL/CD_RATE
/SCMTMS/FREIGHTAGREEMENT
/TMCSL/CD_FAG
/TMCSL/EXCEPTION_TEMPLATE
/TMCSL/EX_TMP
/TMCSL/RFQ_TRANSLATOR
/TMCSL/RFQ_TRAN
/TMCSL/COM_GROUP
/TMCSL/CD_COMG
/TMCSL/NAC_GROUP
/TMCSL/CD_NAC
/TMCSL/PORT_GROUP
/TMCSL/CD_PRTG
PUBLIC
Reusable Objects and
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
 Note
Most of the change document objects are delivered by default for container shipping liners business
objects. For those standard business objects (for example, /SCMTMS/TC_RATES) where there are
enhanced fields that are required for change tracking, the specific standard change document objects
need to be replaced.
Features
The changes are displayed on the Change Documents tab on the user interfaces of the business documents.
 Note
The Change Documents tab is not shown by default. However, you can display it by choosing the button
for personalizing your user interface. If you want to display more technical information, you can personalize
the views.
You can display the changes in the following views:
•
Flat View
In this view, you can see all the changes made to your business document and the relevant information in a
flat list.
•
Hierarchical View
In this view, you can see who changed the business document and when it was changed. If you select a line,
more details are shown in the lower part of the screen, for example, what exactly was changed.
To display the changes, you need to choose Apply. You can filter the data that is displayed by entering search
criteria.
Depending on the view type that you have chosen, you can use one of the following search criteria to filter your
data:
•
Flat View Search Criteria
You can search by user, from date, and to date. Also, you can search by the fields of a business object node
(technical name or data access definition).
•
Hierarchical View Search Criteria
You can search by user, from date, and to date.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Basic Settings
PUBLIC
171
4
Application Decoupling
SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA is an
add-on to SAP S/4HANA. In previous versions, many of the lead to agreement applications were built on top of
standard Transportation Management (TM) applications.
As of version 2202, the lead to agreement applications are decoupled from the standard TM applications.
Hence you can execute both standard TM features and container shipping liner features separately.
The decoupling is achieved in the following ways:
•
•
In the back-end, the Business Object Processing Framework (BOPF) logic is decoupled.
In the front-end, the user interface (UI) applications are decoupled.
The following applications have been decoupled:
•
•
•
•
•
•
•
•
•
•
•
172
Forwarding Agreement Quotation
Forwarding Agreement Quotation Template
Forwarding Agreement
Forwarding Agreement Template
Transportation Charge Calculation Sheet
Transportation Charge Calculation Sheet Template
Rate Table
Rate Table Template
Maintain Rate Table
Internal Agreement
Service Product
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Application Decoupling
5
Tariff Management
A tariff (or standard tariff) is a basic contract in which general rates are defined. The rates are defined for a
particular trade and apply to all customers in that trade.
A standard tariff is created as a forwarding agreement (FWA) in the system, but has no business partner or
sales organization. A standard tariff contains charge types such as ocean carrier freight (OCF). Standard tariffs
can be defined for different pricing trades using the relevant charge structure.
Standard tariffs are used in the following processes:
•
Response generation in forwarding agreement quotations (FWAQs)
When generating response lines for request lines in the FWAQ, the system determines the standard tariff
of the response line based on the pricing trade of the origin and destination locations in the request line.
The system gets the relevant charges from the standard tariff to build the charge structure in the response
line. The charge structure is displayed on the Revenue tab in the flat view of the FWAQ. You can create
customer-specific rates in the quotation by taking an exception for specific charge types. The customer
rates in the FWAQ are transferred to the target FWA during the agreement conversion process.
•
Charge calculation in bookings
In a booking, you can use the Contract Type field to indicate that the charges should be retrieved from
the standard tariff instead of the customer FWA. During charge calculation, the charge structure and the
corresponding rates are then retrieved from the standard tariff.
If a charge type has the surcharge condition Subject To, then the charge calculation retrieves the charges
for that charge type from the standard tariff (even if the contract type for the booking is a customer FWA).
Related Information
Tariff Charge Types [page 174]
Tariff Types [page 176]
Classification of Charge Types Used in Tariffs [page 174]
Creating Rate Tables for Duration-Based Charges [page 179]
Forwarding Agreement Quotations [page 181]
Forwarding Agreement Management [page 243]
Surcharge Conditions [page 59]
Response Lines [page 217]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Tariff Management
PUBLIC
173
5.1
Tariff Charge Types
The table below lists some of the charge types that can be included in a standard tariff.
Charge Type
Description
Ocean carrier freight (OCF)
The leading charge type, which contains the basic ocean freight charges
Inland origin
Inland transportation charges at the port of origin
Inland destination
Inland transportation charges at the port of destination
Transport additional - origin
Transportation charges from a secondary port to a primary port at origin
(TAO)
Transport additional - destination
Transportation charges from a primary port to a secondary port at destination
(TAD)
Terminal handling charges (THC)
An additional charge collected for the handling of containers at terminal
Bunker adjustment factor (BAF)
An additional charge type to compensate for the fluctuations in fuel cost
Currency adjustment factor
An additional charge type to compensate for the fluctuations in exchange rates
(CAF)
Other charges
Other applicable surcharges
Related Information
Tariff Management [page 173]
5.2
Classification of Charge Types Used in Tariffs
When you create different tariffs in the system, you can use the following charge classification in the various
calculation sheets.
The table below provides example charge types. You can create your own charge types in the system and then
assign the appropriate charge classification depending on the usage of each charge type.
Charge Classification
Example Charge Types
Ocean Freight Charge
OCF
174
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Tariff Management
Charge Classification
Example Charge Types
OCF (Calculated)
OCF_TOTAL
Surcharge
BAF, CAF
Duration-Based Charges
YDTI, YDTE
Origin Arbitrary Charge
TAO
Destination Arbitrary Charge
TAD
Base Origin Inland
BASE_INL_O
Base Destination Inland
BASE_INL_D
Origin Inland
O_INLAND
Destination Inland
D_INLAND
Origin Inland Surcharge
FAF_O
Destination Inland Surcharge
FAF_D
Service Marine
FUM_MAR
Service Inland Origin
FUM_INL_O
Service Inland Destination
FUM_INL_D
Service Stage Independent
DOC_HANDLING
First Mile
FIRST_MILE
Last Mile
LAST_MILE
Surcharge First Mile
FM_BAF
Surcharge Last Mile
LM_BAF
Related Information
Tariff Management [page 173]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Tariff Management
PUBLIC
175
5.3
Tariff Types
You can define and maintain different types of tariff in the system. This allows you to maintain different charge
types in different tariffs.
For example, if there are separate departments or pricers responsible for the various legs such as pre-carriage,
main carriage, and on-carriage, they can maintain the corresponding tariffs and rate tables independently. The
system also supports the usage of one tariff document to maintain the charges for different legs. In this case,
the pricer has to create multiple items in the same document, each corresponding to Inland Origin, Inland
Destination, Marine, Arbitrary Origin, and Arbitrary Destination.
The following different tariff types are available in the system:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Marine
Inland Origin
Inland Destination
Arbitrary Origin
Arbitrary Destination
Service Marine
Service Inland Origin
Service Inland Destination
Service End to End
Marine Automation
Inland Origin Automation
Inland Destination Automation
First Mile
Last Mile
You maintain the tariff types in Customizing for Transportation Management under
Lead to Agreement
Basic Settings
Define Tariff Types
Container Shipping Liners
.
For more information about maintaining tariff types, see the Configuration Guide for Forwarding Agreement
Quotation available on SAP Help Portal at https://help.sap.com/tm_csl_l2a_s4hana.
Related Information
Tariff Management [page 173]
176
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Tariff Management
5.3.1 Creating Tariff Agreements
Create a forwarding agreement of type Tariff.
Prerequisites
•
The Customizing settings required to create an agreement have been done in the standard Transportation
Management (TM) system.
•
For the relevant agreement types, the agreement category has been defined as Tariff in Customizing
for Transportation Management under
Container Shipping Liners
Agreement Quotation and Forwarding Agreement
Lead to Agreement
Forwarding
Maintain CSL Forwarding Agreement Types .
Procedure
1. In your SAP Fiori launchpad, choose the Create Forwarding Agreement - CSL app.
2. Select an Agreement Type that has been defined as a Tariff and then choose Continue.
An agreement document is created with the Agreement Category prefilled as Tariff, and the Agreement
Status as In Process.
3. Enter the agreement items.
4. In the FWAQ Item CSL Type field, classify each agreement item as Inland Origin, Inland Destination, Marine,
Arbitrary Origin, or Arbitrary Destination.
5. Assign a calculation sheet and charge types.
 Note
In the Marine calculation sheet, you can maintain the leading ocean freight charge, marine surcharges,
and duration-based charges. In the Inland Origin calculation sheet, you can maintain the leading charge
type for inland origin and the inland origin surcharges. Similarly, you can maintain the calculation
sheet for Inland Destination. Do not add all the charge types (Inland Origin, Inland Destination, or
Marine Arbitrary Origin/Destination, Charge Automation, or Service Charges relevant) into the Marine
calculation sheet.
6. Choose
Set Status
Released
in the tariff header to release the tariff.
7. Save your entries.
Related Information
Rate Tables [page 52]
Creating Rate Tables for Duration-Based Charges [page 179]
Creating Calculation Sheets [page 56]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Tariff Management
PUBLIC
177
5.3.2 Tariff Determination
The system provides a default configuration for determining the appropriate tariff for charge determination.
The default criteria for tariff determination are listed in the table below. If you have a different set of criteria for
tariff determination, then you can create a Business Add-In (BAdI) implementation to suit your business needs.
The relevant BAdI is located in Customizing for Transportation Management under
Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Charge Determination
Container Shipping
BAdI: Determination of Tariff
TCCS .
Tariff Types
•
•
•
Marine
•
•
•
•
•
•
•
•
•
•
Inland Origin
SAP Fiori Launchpad App
Maintain Standard Tariff
Service Marine
Marine Automation
Maintain Arbitrary Tariff
Inland Destination
Arbitrary Origin
Arbitrary Destination
Service Inland Origin
Service Inland Destination
Determined Based On
•
•
•
Business Pricing Trade
•
•
•
•
•
•
Sales Organization
•
•
•
•
•
•
•
Sales Organization
Sales Organization
Valid-From and Valid-To Dates
Source Country
Destination Country
Source Zone ID
Destination Zone ID
Valid-From and Valid-To Dates
Inland Origin Automation
Inland Destination Automation
First Mile
Last Mile
Service End to End
Maintain End to End Tariff
Business Pricing Trade
Source Country
Destination Country
Source Zone ID
Destination Zone ID
Valid-From and Valid-To Dates
Related Information
Tariff Types [page 176]
Creating Tariff Agreements [page 177]
178
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Tariff Management
5.4
Creating Rate Tables for Duration-Based Charges
Create a rate table for duration-based charges.
Prerequisites
A rate table has been created with rate table typed storage.
Context
To use duration-based charges in the tariff agreements, you need to update certain fields such as Free Days,
Free Day Type, and Chargeable Day Type for a set of rate lines (in which all the calculation bases including the
validity dates and No. of Days are different). These fields are used in the charge calculation process.
Procedure
1. In your SAP Fiori launchpad, open the Create Rate Table Definition - CSL app.
2. Enter the rate table type and choose Continue.
3. Enter some calculation bases, for example, Location, Resource Class, and No. of Days.
4. Create some rate lines.
For example, you could create three rate lines for which the Location and Resource Class are the same, but
the No. of Days, which represents the slabs, is different. For example, you could enter the No. of Days for
the three rate lines as <= 5, <=10, and <=15.
5. Select one of the rate lines and choose Update Free Day Information.
6. In the dialog box that appears, enter the Free Days, Free Day Type, and the Chargeable Day type and then
choose OK.
The free day information is updated to all three rate lines since all the calculation bases except for the No.
of Days is same for this set of rate lines. Note that the validity dates should also be the same for these three
rate lines.
7. (Optional) To clear the free days information that has already been maintained for the existing rate lines,
select a rate line, choose Update Free Day Information and select the Clear Free Days checkbox.
8. Save your entries.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Tariff Management
PUBLIC
179
Related Information
Rate Tables [page 52]
180
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Tariff Management
6
Forwarding Agreement Quotations
A forwarding agreement quotation (FWAQ) is an individual business document that you, as a carrier or
logistics service provider (LSP), proactively send to a shipper or another LSP to bid for the provision of future
transportation services in one or more trade lanes for a defined period.
You can also use an FWAQ to respond to a quotation request (from a shipper or LSP) with your rates for
transportation services.
In SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA, FWAQs
are based on the FWAQ business document in Transportation Management with enhancements in the following
areas:
•
Header information
The following information has been added to the header of the FWAQ:
•
•
•
•
Minimum quantity commitment (MQC)
Carrier space commitment (CSC)
Instruction sets
Agreement creation
 Note
The container shipping liner (CSL) FWAQ does not support multiple parties. You can only maintain one
sales organization in the header of the quotation.
•
Request-response structure
An FWAQ is a collection of request lines and their corresponding response lines. The FWAQ item structure
has been enhanced to hold request lines and additional details in the leading charge type rate table. The
response item rate table for a leading charge type mirrors the structure of the request item rate table. The
response item rate lines are related directly to the request item rate table lines (request lines).
You can add request items of the following types in a forwarding agreement quotation:
•
•
•
•
•
Marine
Inland Origin
Inland Destination
Arbitrary Origin
Arbitrary Destination
The request items are differentiated by the CSL Item Type field. Each type of request item has its own
leading charge type. You can add request lines to inland and arbitrary items and generate responses
similarly to marine request lines. Once the responses are generated based on rates from the configured
tariff agreement, rates can be adjusted in the revenue and then approved to move these response lines into
a forwarding agreement.
•
Advanced flat view
The flat view has been enhanced to work with request and response lines. The flat view can be integrated
with SAP Transportation Management, network and operations for container shipping liners for SAP S/
4HANA to build rates from existing tariffs or customer agreements, and to use advanced surcharge
structures, rate construction, and life-cycle management in response lines.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
181
Related Information
Forwarding Agreement Quotation Creation [page 182]
Tariff Management [page 173]
For more information about the standard TM functionality for FWAQs, see the product assistance for
Transportation Management in SAP S/4HANA on SAP Help Portal at https://help.sap.com/s4hana_op and
choose your version. Open the product assistance and choose
Enterprise Business Applications
Chain Transportation Management (TM) Agreement Management
search for Forwarding Agreement Quotation.
6.1
Supply
Forwarding Agreement Quotation , or
Forwarding Agreement Quotation Creation
Forwarding agreement quotations (FWAQs) can be created manually or by using the request for quotation
(RFQ) translator.
You can use the RFQ translator to upload tenders from a Microsoft Excel file and create an FWAQ in the system.
When creating an FWAQ manually, you can create it from scratch, or you can use a template that you have
already defined in the Create FWAQ Template - CSL app in your SAP Fiori launchpad.
Once the FWAQ is complete, you can create a forwarding agreement (FWA).
FWAQs in the container shipping liners application contain the following functions, which allow you to efficiently
respond to customer requests:
•
•
•
•
•
•
•
Request lines creation
Response lines generation
Status management
Context information
Routing integration
Rates building
Conversion to FWA
Related Information
Creation of Forwarding Agreement Quotations [page 194]
Forwarding Agreement RFQ Translator [page 183]
Creating Request Lines [page 207]
Response Lines [page 217]
Status Management [page 232]
Conversion of FWAQs to Forwarding Agreements [page 237]
Forwarding Agreement Quotations [page 181]
182
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
6.1.1 Forwarding Agreement RFQ Translator
Forwarding Agreement Request for Quotation (RFQ) Translator is a tool that you can use to translate Microsoft
Excel file content into forwarding agreement quotations (FWAQs) in the SAP Transportation Management (SAP
TM) system.
Using this feature, you can perform the following tasks:
•
You can upload request lines belonging to any of the container shipping liners (CSL) item types - marine,
inland origin, inland destination, arbitrary origin, and arbitrary destination. You can map multiple work
sheets from Microsoft Excel to different CSL item types.
•
You can upload request lines with request conditions such as the following:
•
•
•
•
•
•
•
•
•
•
•
•
Charge Type
Surcharge Condition
Surcharge Condition Update Type
Amount
Currency
Free Days
Free Day Type
Chargeable Day Type
Payment Place
Payment Party
Payment Part Type
Settlement Term
•
You can provide named accounts, commodities, and ports to create named account groups, commodity
groups, and source or destination port groups.
•
You can provide service product details to create services for a request line.
 Note
You can manipulate this data according to your requirements using the Business Add-In (BAdI)
located in Customizing for Transportation Management under
Agreement
•
Business Add-Ins (BAdIs)
RFQ Translator
Container Shipping Liners
Lead to
BAdI: Splitting of Charge Conditions .
You can upload the Microsoft Excel file multiple times for negotiations with the tender type of RFQ, which
results in the creation of a newer version of the forwarding agreement quotation.
 Note
You can adjust the request lines according to the negotiation round Microsoft Excel file using the BAdI
located in Customizing for Transportation Management under
Agreement
Business Add-Ins (BAdIs)
RFQ Translator
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Container Shipping Liners
Lead to
BAdI: Status Update in RFQ .
PUBLIC
183
Upload Process
The upload process involves the following steps:
1. You generate the SAP Application Interface Framework interface using the Generation of Structure from
Uploaded Excel File screen (report /TMCSL/EXCEL_GEN_STRUC_V2). This is a one-time setup activity that
needs to be done before you can upload a Microsoft Excel file.
2. You create the RFQ header using the RFQ Translator: Excel Upload screen (transaction /TMCSL/
L2A_UP01).
3. You select an RFQ header and then upload the Microsoft Excel file using the RFQ Translator: Excel Upload
screen (transaction /TMCSL/L2A_UP01).
When a file is uploaded, the system keeps a trace that matches the individual Microsoft Excel lines to a specific
request line in the quotation.
RFQ Translator: Excel Upload Screen
The RFQ Translator: Excel Upload screen is composed of the following sections:
•
Upload Mode
The possible options are as follows:
•
Upload
You select this option when you are uploading the initial Microsoft Excel file received from the
customer, or during a negotiation round for subsequent uploads with customer feedback.
•
New Negotiation Round
When you select this option, the negotiation round is incremented by one. It indicates the start of a
new negotiation round during the tendering process.
•
Off Tender
You select this option when the agreement is already created and the tendering process is closed. It
allows you to add new rate request lines in the existing agreement. The system generates a new FWAQ
with version 0 and only creates the request lines available in the latest Microsoft Excel file.
•
Rate Lines
You can enter the specific set of Microsoft Excel rows that contain the tender information if the tender
details are segregated. Alternatively, you can instruct the system to upload all of the available rows in the
Microsoft Excel file by choosing the All Lines option.
•
Boilerplate
You can indicate whether the Microsoft Excel File to be uploaded contains boilerplate information.
•
RFQ Maintenance
You can create, edit, and delete RFQ headers, and also display the related FWAQs.
•
Related FWAQ
You can view the related FWAQs for the selected RFQ header and also navigate to the log for the selected
FWAQ.
You can perform the following tasks in the RFQ Translator: Excel Upload screen:
•
•
184
Creating RFQ Headers
Editing RFQ Headers
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
•
•
•
•
Creating RFQ Headers by Copying Existing RFQ Headers
Deleting RFQ Headers
Displaying Related FWAQs
Displaying the Log for RFQ Translator Upload
Related Information
Generating Interfaces from Microsoft Excel Files [page 185]
Creating RFQ Headers [page 187]
Editing RFQ Headers [page 189]
Creating RFQ Headers by Copying Existing RFQ Headers [page 190]
Deleting RFQ Headers [page 191]
Displaying Related FWAQs [page 192]
Displaying the Log for RFQ Translator Upload [page 193]
6.1.1.1
Generating Interfaces from Microsoft Excel Files
Convert a request for quotation (RFQ) Microsoft Excel file to an SAP Application Interface Framework interface
using the Generation of Structure from Uploaded Excel File screen (transaction /TMCSL/L2A_GEN01).
Prerequisites
•
•
•
The SAP Application Interface Framework add-on component is installed in the system.
The SAP Application Interface Framework namespace is defined in the system.
Workbench and Customizing transport requests are available in the system to capture the relevant details
of the SAP Application Interface Framework interface and the system-generated structures and table
types.
Context
In this process, the data from the Microsoft Excel file is converted and mapped to the SAP Transportation
Management (SAP TM) input structure. The system generates the data structure and the table type for the
Microsoft Excel file that is to be uploaded, and also creates the SAP Application Interface Framework interface
and file adapter. This is a one-time setup activity that needs to be done before you upload a Microsoft Excel file.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
185
Procedure
1. Start transaction /TMCSL/L2A_GEN01.
The Generation of Structure from Uploaded Excel File screen is displayed.
2. In the File on Local PC section, enter the following details:
•
•
•
Path of the RFQ Microsoft Excel file on the presentation server provided by the customer
Name of the Microsoft Excel worksheet that contains the tender details
Row number that contains the column details
3. Once the Microsoft Excel file is uploaded, press Enter .
Depending on the Microsoft Excel file, the multiple worksheet tab is displayed to enter the SAP Application
Interface Framework related data.
4. In the AIF Related section, enter the following details:
•
•
•
•
•
•
•
•
•
Namespace
Interface Name
Description
Interface Version
Data Structure
Table Type of Data Structure
Member of Raw Structure
Raw Structure
Configuration ID
5. If the Microsoft Excel file contains a boilerplate, then select the Has Boilerplate checkbox and enter the
following details:
•
•
•
Name of the worksheet
Row number of the boilerplate
Column name of the boilerplate
6. In the Transport Information section, enter the transport details.
7. Choose Execute.
Results
The SAP Application Interface Framework Interface is generated with the details provided.
Next Steps
To complete the configuration of the SAP Application Interface Framework interface, you need to map the
generated raw structure to the RFQ Translator destination structure in SAP Application Interface Framework
Customizing (transaction /AIF/CUST).
186
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Related Information
Creating RFQ Headers [page 187]
Editing RFQ Headers [page 189]
Creating RFQ Headers by Copying Existing RFQ Headers [page 190]
Deleting RFQ Headers [page 191]
6.1.1.2
Creating RFQ Headers
Create a request for quotation (RFQ) header using the RFQ Translator: Excel Upload screen (transaction /
TMCSL/L2A_UP01).
Prerequisites
•
The RFQ header number has been defined in Customizing for Transportation Management under
Container Shipping Liners
Lead to Agreement
Request for Quotations
Define Number Range
Intervals for RFQ ID .
•
You have generated the SAP Application Interface Framework interface using the program Generation of
Structure from Uploaded Excel Files (transaction /TMCSL/L2A_GEN01).
•
You have access to the customer's Microsoft Excel file with the tender worksheet containing the details of
the rate request lines.
Context
You must create an RFQ header before uploading the customer's Microsoft Excel file into the system. The RFQ
header contains the header level details of the forwarding agreement quotation (FWAQ) that is created after
the file upload.
Procedure
1. Start transaction /TMCSL/L2A_UP01.
The RFQ Translator: Excel Upload screen is displayed.
2. In the RFQ Maintenance section, choose Create.
The Create/Edit RFQ dialog box is displayed.
3. In the Create/Edit RFQ dialog box, enter the following details:
•
RFQ Type (Tender or Quotation)
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
187
•
•
•
•
•
•
•
•
•
Ordering Party
Description
FWAQ Type
Document Currency
Account Type
Surcharge Template
List of Carriers (all carriers are listed by default)
List of Customer Requested Commodities and Named Accounts (NACs)
FWAQ/Tender Dates
•
•
•
FWAQ Valid-From Date and Valid-To Date
Response Deadline
Agreement Valid-From Date and Valid-To Date
4. Choose Save.
Results
The RFQ header is created with the relevant details.
Next Steps
You can select the RFQ header and then choose Execute to upload the customer's Microsoft Excel file.
Related Information
Editing RFQ Headers [page 189]
Creating RFQ Headers by Copying Existing RFQ Headers [page 190]
Deleting RFQ Headers [page 191]
188
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
6.1.1.3
Editing RFQ Headers
Edit the details of a request for quotation (RFQ) header using the RFQ Translator: Excel Upload screen
(transaction /TMCSL/L2A_UP01).
Prerequisites
In the RFQ Translator: Excel Upload screen, there is an existing RFQ header listed in the RFQ Maintenance
section.
Procedure
1. Start transaction /TMCSL/L2A_UP01.
The RFQ Translator: Excel Upload screen is displayed.
2. In the RFQ Maintenance section, select the relevant RFQ header and then choose Edit.
The Create/Edit RFQ dialog box is displayed with the following details:
•
•
•
•
•
•
•
•
•
•
RFQ Type (Tender or Quotation)
Ordering Party
Description
FWAQ Type
Document Currency
Account Type
Surcharge Template
List of Carriers
List of Customer Requested Commodities and Named Accounts (NACs)
FWAQ/Tender Dates
•
•
•
FWAQ Valid-From Date and Valid-To Date
Response Deadline
Agreement Valid-From Date and Valid-To Date
3. Edit the details as required.
4. Choose Save.
Results
The updated RFQ header is saved with the latest changes.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
189
Next Steps
You can select the RFQ header and then choose Execute to upload the customer's Microsoft Excel file.
Related Information
Creating RFQ Headers by Copying Existing RFQ Headers [page 190]
Deleting RFQ Headers [page 191]
6.1.1.4
Creating RFQ Headers by Copying Existing RFQ
Headers
Create a request for quotation (RFQ) header by copying an existing RFQ header using the RFQ Translator: Excel
Upload screen (transaction /TMCSL/L2A_UP01).
Prerequisites
In the RFQ Translator: Excel Upload screen, there is an existing RFQ header listed in the RFQ Maintenance
section.
Context
In the RFQ Translator: Excel Upload screen, you can use the Create with Reference button to create a copy of an
existing RFQ header. You can then edit the details of the new RFQ header before saving it.
Procedure
1. Start transaction /TMCSL/L2A_UP01.
The RFQ Translator: Excel Upload screen is displayed.
2. In the RFQ Maintenance section, select the relevant RFQ header and then choose Create with Reference.
The Create/Edit RFQ dialog box is displayed with the following details copied from the existing RFQ header.
•
•
•
190
RFQ Type (Tender or Quotation)
Ordering Party
Description
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
•
•
•
•
•
•
•
FWAQ Type
Document Currency
Account Type
Surcharge Template
List of Carriers
List of Customer Requested Commodities and Named Accounts (NACs)
FWAQ/Tender Dates
•
•
•
FWAQ Valid-From Date and Valid-To Date
Response Deadline
Agreement Valid-From Date and Valid-To Date
3. Edit the details as required.
4. Choose Save.
Results
A new RFQ header is created with the relevant details.
Next Steps
You can now select the RFQ header and then choose Execute to upload the customer's Microsoft Excel file.
Related Information
Creating RFQ Headers [page 187]
Editing RFQ Headers [page 189]
Deleting RFQ Headers [page 191]
6.1.1.5
Deleting RFQ Headers
Delete a request for quotation (RFQ) header using the RFQ Translator: Excel Upload screen (transaction /
TMCSL/L2A_UP01).
Prerequisites
In the RFQ Translator: Excel Upload screen, there is an existing RFQ header listed in the RFQ Maintenance
section.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
191
Procedure
1. Start transaction /TMCSL/L2A_UP01.
The RFQ Translator: Excel Upload screen is displayed.
2. In the RFQ Maintenance section, select the relevant RFQ header.
3. Choose Delete.
Results
The selected RFQ header is deleted and removed from the list.
Related Information
Creating RFQ Headers [page 187]
Creating RFQ Headers by Copying Existing RFQ Headers [page 190]
Editing RFQ Headers [page 189]
6.1.1.6
Displaying Related FWAQs
Display the associated forwarding agreement quotation (FWAQ) along with the versions for a given request for
quotation (RFQ).
Prerequisites
An FWAQ exists for the RFQ after the successful upload of the customer's Microsoft Excel file.
Context
The list of FWAQs is shown in the Related FWAQ section of the RFQ Translator: Excel Upload screen
(transaction /TMCSL/L2A_UP01).
192
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Procedure
1. Start transaction /TMCSL/L2A_UP01.
The RFQ Translator: Excel Upload screen is displayed.
2. In the RFQ Maintenance section, select the relevant RFQ header.
3. Choose Related FWAQ.
Results
The list of FWAQs is displayed in the Related FWAQ section. The list is sorted based on round type, round
number, negotiation round number, and upload reference number.
Related Information
Displaying the Log for RFQ Translator Upload [page 193]
6.1.1.7
Displaying the Log for RFQ Translator Upload
Display the logs for a customer's Microsoft Excel file upload in the SAP Application Interface Framework Error
Monitor.
Prerequisites
A customer's Microsoft Excel file has been uploaded.
Context
The status of the upload is displayed alongside the related FWAQ. A traffic light indicator is used to show the
upload status as follows:
•
•
•
Green: successful upload
Yellow: successful upload with warnings
Red: upload ended with an error
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
193
Procedure
1. Start transaction /TMCSL/L2A_UP01.
The RFQ Translator: Excel Upload screen is displayed.
2. In the RFQ Maintenance section, select the relevant RFQ header and then choose Related FWAQ.
3. In the Related FWAQ list, select an upload instance and then choose Display Log.
Results
The system displays the SAP Application Interface Framework Error Monitor screen and opens the specific
instance for the upload showing the relevant logs.
Next Steps
If you need to troubleshoot an error, you can double-click the error message to navigate to the erroneous line in
the staging area of SAP Application Interface Framework.
Related Information
Displaying Related FWAQs [page 192]
6.1.2 Creation of Forwarding Agreement Quotations
Forwarding agreement quotations (FWAQs) can be created from scratch, or you can use a template that you
have already defined in the Create FWAQ Template - CSL app.
Once the FWAQ is complete, you can create a forwarding agreement (FWA). FWAQs in SAP Transportation
Management, lead to agreement for container shipping liners for SAP S/4HANA contain the following
functions, which allow you to efficiently respond to customer requests:
•
•
•
•
•
•
•
194
Request lines creation
Routing integration
Response line generation
Working with responses
Context information
Status management
Conversion to FWAs
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Related Information
Creating Forwarding Agreement Quotations Using Templates [page 195]
Creating Forwarding Agreement Quotations Manually [page 198]
6.1.2.1
Creating Forwarding Agreement Quotations Using
Templates
Create a forwarding agreement quotation (FWAQ) using an FWAQ template.
Prerequisites
•
The settings for forwarding agreement quotation types have been maintained in Customizing for
Transportation Management under
Container Shipping Liners
Agreement Quotation and Forwarding Agreement
Lead to Agreement
Forwarding
Maintain CSL Forwarding Agreement Quotation
Types .
•
The Business Add-In (BAdI) for determining FWAQ creation details has been implemented in Customizing
for Transportation Management under
Container Shipping Liners
Lead to Agreement
Business Add-
Ins (BAdIs) Forwarding Agreement Quotation BAdI: Determination of FWAQ Creation Details .
You can use this BAdI to determine the attributes of the forwarding agreement quotation such as the
following:
•
•
•
•
•
•
•
Proposal Valid From
Proposal Valid To
Proposal Response Deadline
Agreement Valid From
Agreement Valid To
Currency
Time Zone
Context
When you use an FWAQ template to create an FWAQ, the information from the template is prefilled in the new
FWAQ document. In addition, some of the header details of the FWAQ such as the proposal validity dates,
proposal agreement dates, time zone, and document currency are filled based on the settings maintained in
Customizing.
 Note
You follow the standard Transportation Management (TM) process to create the FWAQ template, and also
make some additional settings that are required for lead to agreement processes.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
195
Procedure
1. In your SAP Fiori launchpad, open the Create FWAQ Template - CSL app.
2. Follow the standard Transportation Management (TM) steps to create the FWAQ template.
3. In the Basic Data section, select the L2A Processing Flag checkbox.
4. Enter the FWAQ items and assign the container shipping liners item types (marine, inland origin, inland
destination, arbitrary origin, and arbitrary destination) as required.
5. For each FWAQ item, follow the standard TM steps to create a calculation sheet template.
6. In the calculation sheet template, select the L2A Processing Flag checkbox.
7. Enter one item in the calculation sheet that corresponds to the leading charge type.
8. In the calculation sheet template, ensure the charge classifications are maintained correctly as follows:
CSL Item Type
Leading Charge Classification
Marine
Ocean Freight Charge
Inland Origin
Base Origin Inland
Inland Destination
Base Origin Destination
Arbitrary Origin
Origin Arbitrary Charge
Arbitrary Destination
Destination Arbitrary Charge
In all of the calculation sheet templates, there should be only one item corresponding to the leading charge
type. Rate tables that are part of a lead to agreement FWAQ or FWA support only one instance of validity
node.
9. For this leading charge type, follow the standard TM steps to create a rate table template.
10. In the rate table template, make the following settings:
•
•
•
•
Select the Rate Validity Split checkbox.
Select the Typed Rate Storage checkbox.
Enter the Typed Node Name.
Select the L2A Processing Flag checkbox.
When you create the rate table templates, the validity node instance does need not to be created. When
the FWAQ is created using the template, an instance of the validity node is created by the system and the
dates are updated based on the validity dates maintained in the FWAQ header.
11. Enter the mandatory calculation bases required for the response generation including the following:
•
•
•
•
•
•
196
SOURCELOC_ZONE
DESTLOC_ZONE
COMMODITY_CODE
EQUIP_TYPE
TMCSL_RCPTM
TMCSL_DISCM
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
•
Other calculation bases can be maintained as required.
12. Save the FWAQ template.
13. In your SAP Fiori launchpad, open the Create Forwarding Agreement Quotation - CSL app.
14. In the Quotation Template field, enter the FWAQ template created in the previous steps and then choose
Continue.
15. A new forwarding agreement quotation is created with the information maintained in the template.
At the FWAQ items level, a response item along with the calculation sheet and the rate tables for the
leading charge type are created automatically by the system corresponding to each of the request items
that are part of the FWAQ template.
Note that an FWAQ item of type Response must be created to proceed with the process of response
generation in the flat view.
16. When the response items are generated successfully, go to the flat view and insert the request lines.
You cannot maintain the request lines directly from the rate table of the leading charge type. For request
lines of type inland origin, inland destination, arbitrary origin, and arbitrary destination, the system does
not support the routing. Hence the rating is on a point-to-point basis.
If routes are maintained in the system for a given combination of source and destination zones in the
marine request lines, the system can generate the response lines.
17. Save your entries.
Results
You have created an FWAQ using an FWAQ template.
Related Information
Creating Forwarding Agreement Quotations Manually [page 198]
Instruction Sets [page 200]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
197
6.1.2.2
Creating Forwarding Agreement Quotations
Manually
Create a forwarding agreement quotation (FWAQ) manually using the Create Forwarding Agreement Quotation CSL app.
Prerequisites
•
The settings for forwarding agreement quotation types have been maintained in Customizing for
Transportation Management under
Container Shipping Liners
Agreement Quotation and Forwarding Agreement
Lead to Agreement
Forwarding
Maintain CSL Forwarding Agreement Quotation
Types .
•
The Business Add-In (BAdI) for determining FWAQ creation details has been implemented in Customizing
for Transportation Management under
Container Shipping Liners
Lead to Agreement
Business Add-
Ins (BAdIs) Forwarding Agreement Quotation BAdI: Determination of FWAQ Creation Details .
You can use this BAdI to determine the attributes of the forwarding agreement quotation such as the
following:
•
•
•
•
•
•
•
Proposal Valid From
Proposal Valid To
Proposal Response Deadline
Agreement Valid From
Agreement Valid To
Currency
Time Zone
Context
If you create an FWAQ without using an FWAQ template, then you need to enter the details in the header of the
FWAQ manually.
 Note
You follow the standard Transportation Management (TM) process to create the FWAQ, and also make
some additional settings that are required for lead to agreement processes.
Procedure
1. In your SAP Fiori launchpad, open the Create Forwarding Agreement Quotation - CSL app.
198
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
2. Select the Quotation Type and then follow the standard Transportation Management (TM) steps to create
the FWAQ.
Some fields are filled based on your Customizing settings.
3. On the General Data tab, select the L2A Processing Flag checkbox.
4. Enter the other mandatory header fields such as Sold-To Party and Sales Organization.
5. Enter the FWAQ items and assign the container shipping liners item types (marine, inland origin, inland
destination, arbitrary origin, and arbitrary destination) as required.
6. For each FWAQ item, create a calculation sheet by following the standard TM steps.
7. In the header of the calculation sheet, select the L2A Processing Flag checkbox.
8. In the calculation sheet, add one item corresponding to the leading charge type (select the Leading Charge
Type checkbox) and create a rate table.
9. In the calculation sheet, ensure the charge classifications are maintained correctly as follows:
CSL Item Type
Leading Charge Classification
Marine
Ocean Freight Charge
Inland Origin
Base Origin Inland
Inland Destination
Base Origin Destination
Arbitrary Origin
Origin Arbitrary Charge
Arbitrary Destination
Destination Arbitrary Charge
In all of the calculation sheets, there should be only one item corresponding to the leading charge type.
 Note
You need to assign the calculation method as CSL_CM_RATE_TYP for each of the charge types.
10. For this leading charge type, follow the standard TM steps to create a rate table.
11. In the rate table, make the following settings:
•
•
•
•
Select the Rate Validity Split checkbox.
Select the Typed Rate Storage checkbox.
Enter the Typed Node Name.
Select the L2A Processing Flag checkbox.
Rate tables that are part of a lead to agreement FWAQ or FWA support only one instance of the validity
node.
12. Enter the mandatory calculation bases required for the response generation including the following:
•
•
•
•
•
SOURCELOC_ZONE
DESTLOC_ZONE
COMMODITY_CODE
EQUIP_TYPE
TMCSL_RCPTM
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
199
•
•
TMCSL_DISCM
Other calculation bases can be maintained as required.
13. When you have created the required request items, calculation sheets, and rate tables, in the Items section,
choose Create Response Item to create the response items.
Note that an FWAQ item of type Response must be created to proceed with the process of response
generation in the flat view.
14. When the response items are generated successfully, go to the flat view and insert the request lines.
You cannot enter the request lines directly from the rate table of the leading charge type. For request lines
of type inland origin, inland destination, arbitrary origin, and arbitrary destination, the system does not
support the routing. Hence the rating is on a point-to-point basis.
If routes are maintained in the system for a given combination of source and destination zones in the
marine request lines, the system can generate the response lines.
15. Save your entries.
Related Information
Creation of Forwarding Agreement Quotations [page 194]
Instruction Sets [page 200]
6.1.2.3
Instruction Sets
Instruction sets are clauses that describe the carrier's and the merchant's rights and responsibilities when
dealing with each other.
Instruction sets are made up of individual instructions that are grouped into a sequence of steps for a
particular business process. For example, an instruction set could list a sequence of actions for transporting
dangerous or hazardous goods, clarifying the carrier's lines, or stating a blame collision clause. Instruction
sets and instructions are defined in Customizing for SAP Transportation Management under
Management
Basic Functions
Instructions
Transportation
Define Instructions and Instruction Sets .
Instruction sets can be assigned to forwarding agreement quotations (FWAQs) on the following levels:
•
Header level
When you assign an instruction set to an FWAQ header, the instruction set is a general instruction that
applies to the entire FWAQ.
•
Individual request or response line level
When you assign an instruction to a request or response line, the instruction set applies to the specific
request or response line.
200
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Related Information
Adding Instruction Sets to FWAQ Headers [page 201]
Adding Instruction Sets to Request and Response Lines [page 202]
Creation of Forwarding Agreement Quotations [page 194]
Forwarding Agreement Quotation Creation [page 182]
6.1.2.3.1
Adding Instruction Sets to FWAQ Headers
Add instruction sets to forwarding agreement quotations (FWAQ) to specify procedures that must be carried
out in the execution of the forwarding agreement (FWA).
Prerequisites
•
Instruction sets have been defined in Customizing for Transportation Management under
Functions
•
Instructions
Define Instructions and Instruction Sets .
Instruction sets have been assigned in Customizing for Transportation Management under
Functions
Instructions
Basic
Basic
Assign Instruction Sets .
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the FWAQ number and choose Continue.
3. Choose Edit.
4. Go to the Boilerplate tab and choose the Instruction Sets subtab.
5. Add an instruction set, as follows:
a. Choose
Insert
Instruction Set .
b. In the dialog box that opens, search for and select the relevant instruction set.
c. Confirm the dialog box.
The system adds the instruction set and default instructions to the table on the Instruction Sets subtab.
6. (Optional) Add an instruction to the instruction set, as follows:
a. Select an instruction set and choose
Insert
Instruction .
b. In the dialog box that opens, search for and select the relevant instruction.
c. Confirm the dialog box.
The system adds the instruction underneath the selected instruction set.
7. Save your entries.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
201
Related Information
Instruction Sets [page 200]
Creation of Forwarding Agreement Quotations [page 194]
Forwarding Agreement Quotation Creation [page 182]
6.1.2.3.2
Adding Instruction Sets to Request and Response
Lines
Add instruction sets to request and response lines in forwarding agreement quotations (FWAQ) to specify
procedures that must be carried out for the specific request or response line items.
Prerequisites
•
Instruction sets have been defined in Customizing for Transportation Management under
Functions
•
Instructions
Basic
Define Instructions and Instruction Sets .
Instruction sets have been assigned in Customizing for Transportation Management under
Functions
Instructions
Basic
Assign Instruction Sets .
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the FWAQ number and choose Continue.
3. Choose Display Flat View.
4. In the flat view screen, choose Apply to display the response and request lines.
5. Select the relevant response or request line.
6. Add an instruction set as follows:
a. On the Instruction Set tab, choose
Insert
Instruction Set .
b. In the dialog box that opens, search for and select the relevant instruction set.
c. Confirm the dialog box.
The system adds the instruction set and default instructions to the table on the Instruction Set tab.
7. (Optional) Add an instruction to the instruction set, as follows:
a. Select an instruction set on the Instruction Set tab, and choose
Insert
Instruction .
b. In the dialog box that opens, search for and select the relevant instruction.
c. Confirm the dialog box.
The system adds the instruction to the selected instruction set.
202
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
8. Choose Back to return to the main screen.
9. Save the FWAQ document.
Related Information
Instruction Sets [page 200]
Forwarding Agreement Quotation Creation [page 182]
6.2
Functions in Forwarding Agreement Quotations
Forwarding agreement quotations (FWAQs) in the container shipping liners application contain functions that
allow you to efficiently respond to customer requests.
Once you have created the FWAQ header, you can further build the FWAQ using the following functions:
•
•
•
•
•
•
•
Request lines creation
Routing integration
Response lines generation
Working with responses
Context information
Status management
Conversion to forwarding agreements (FWA)
Related Information
Forwarding Agreement Quotation Header Processing [page 204]
Multi-User Enabled Quotations [page 206]
Request Lines [page 207]
Response Lines [page 217]
Approving Response Lines [page 230]
Status Management [page 232]
Duration-Based Charges and Exceptions [page 233]
Conversion of FWAQs to Forwarding Agreements [page 237]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
203
6.2.1 Forwarding Agreement Quotation Header Processing
After creating the forwarding agreement quotation (FWAQ), either from an FWAQ template or manually, you
need to update certain fields such as Sold-To Party, Sales Organization, Time Zone, Document Currency,
Proposal Validity Dates, and Proposal Agreement Dates.
Some of these fields are updated based on the settings maintained in Customizing for Transportation
Management under
Forwarding Agreement
Container Shipping Liners
Lead to Agreement
Forwarding Agreement Quotation and
Maintain CSL Forwarding Agreement Quotation Types .
You can change the proposal agreement validity dates and use the following features as required:
•
Adjust Validity Periods
Choose Adjust Dates Adjust Validity Periods in the FWAQ header to update the validity dates of the
FWAQ items, calculation sheet, and validity node of the rate table if the agreement dates in the FWAQ
header have been changed and need to be percolated down. The validity dates of the rate lines are not
adjusted by this option. If there are rate lines already created in the rate tables, then the dates for the
validity node of the rate table are not adjusted.
•
Adjust Validity Periods + Rate Validity
Choose Adjust Dates Adjust Validity Periods + Rate Validity in the FWAQ header to update the validity
dates of the FWAQ items, calculation sheet, validity node of the rate table, and the rate lines (request and
response) if the agreement dates in the FWAQ header have been changed and need to be percolated down.
 Note
After you change the validity dates in the FWAQ header, save your changes before choosing this option.
When you choose Adjust Dates Adjust Validity Periods + Rate Validity , a dialog box appears with the
following Adjustment Type options:
•
Adjustment/Truncation Type
Choose this option if the header validity dates must be updated to the items, calculation sheet, rate
table validity, and the validity dates of the request and response rate line.
•
Extension Type
Choose this option to extend the validity dates of the FWAQ items, calculation sheet, rate table validity,
and specific rate lines. You need to enter a Rate Extension Date.
You need to refresh the screen to see your changes.
•
204
Determine Eligible Agreements
Choose Determine Eligible Agreement in the FWAQ header to determine the list of existing forwarding
agreements (FWAs) that are eligible for conversion from a specific forwarding agreement quotation
(FWAQ). In the dialog box that opens, specify the following criteria:
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Field
What To Do
Overwrite Manual Changes
Select one of the following options:
•
Do not overwrite manual changes (default option)
When the system determines the eligible agree­
ments, it will not overwrite any manual changes
that you have previously made to agreements in the
Eligible Agreement List.
•
Overwrite all including manual changes
In the process of determining eligible agreements,
the system overwrites any manual changes that
you previously made to agreements in the Eligible
Agreement List.
Duration of Search in Months
Enter the number of months in the past for which the
system should search for eligible agreements.
The system looks for agreements that have the same attributes such as ordering party, sales organization,
validity dates, named account, participant, and so on. This is the default implementation provided by the
system. It can be enhanced in the Business Add-In (BAdI) /TMCSL/BADI_ELG_CRT_UPD_AGR.
The system determines the following types of agreements based on the proposal agreement validity dates:
•
•
•
Full Overlap: Agreements that completely overlap with the quotation
Partial Overlap: Agreements that partially overlap with the quotation
Historical: Agreements with validities outside the range of the quotation validity
By default, all agreements that fully overlap with the quotation validity have the Target Agreement
checkbox selected. However, during the overlap check, which is part of the approval process for the
response lines, the agreements that have the Eligible Agreement Type as Full Overlap and Partial Overlap
are considered.
You can set one of the agreements as the default agreement. Any response lines that do not find a target
agreement during the approval process are marked to go to this default agreement.
You can create a new temporary agreement using the + button.
You can also determine the eligible agreements by choosing Get Eligible Agreements on the Agreement
Create/Update tab.
The target agreement type for an FWAQ type must be maintained on the CSL Quotation Types Eligible Agreement Types node in Customizing for Transportation Management under
Liners
Lead to Agreement
Container Shipping
Forwarding Agreement Quotation and Forwarding Agreement
Maintain CSL
Forwarding Agreement Quotation Types .
The agreements that are eligible for the FWAQ are displayed in the Eligible Agreement List section of the
Agreement Create/Update tab.
Of all the agreements, if only one agreement has the Target Agreement checkbox selected, then this is
also automatically set as the default agreement in the Default Agreement Assignment for FWAQ Response
Lines section. If there is more than one agreement with the Target Agreement checkbox selected, then no
agreement is set as default in the Default Agreement Assignment for FWAQ Response Lines section.
If the system does not find any eligible agreements, a temporary agreement $1 is created and is also set as
the default agreement.
•
Set/Unset Target Agreement
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
205
On the Agreement Create/Update tab, in the Eligible Agreement List section, you can choose Set/
Unset Target Agreement to select or deselect the Target Agreement checkbox for the selected partially
overlapping agreement.
•
Set Default Agreement
On the Agreement Create/Update tab, in the Eligible Agreement List section, choose Set Default Agreement
to set a fully or partially overlapping agreement as the default agreement.
•
Verify Eligible Agreement List
On the Agreement Create/Update tab, in the Eligible Agreement List section, choose Verify Eligible
Agreement List to check whether the eligible agreements list is up to date.
A message is displayed stating whether the eligible agreements list is correct or needs to be refreshed.
Related Information
Creating Forwarding Agreement Quotations Using Templates [page 195]
6.2.2 Multi-User Enabled Quotations
If multiple users need to work on a forwarding agreement quotation (FWAQ), then this can be controlled
through the Multiple User Enabled checkbox on the General Data tab of the FWAQ.
This option can also be set in Customizing for Transportation Management under
Lead to Agreement
Forwarding Agreement Quotation and Forwarding Agreement
Container Shipping Liners
Maintain CSL Forwarding
Agreement Quotation Types .
If the Multiple User Enabled checkbox is selected for an FWAQ or forwarding agreement, then the document
rate lines can be processed by multiple users from different pricer groups at the same time. Pricer Group is a
rate table field that is available at the rate line level. It is used to lock the rate line. When a user changes a rate
line of an FWAQ or forwarding agreement, the pricer group of the rate line is locked.
 Example
If user 1 is changing rate line 1 with pricer group 50000042, then pricer group 50000042 is locked. If user
2 tries to change rate line 2 with the same pricer group 50000042, then an error message is displayed.
If user 2 tries to change rate line 3 with a different pricer group 50000043, then this is allowed as there is
no lock conflict on the pricer group.
Pricer Group Redetermination and Locking
If some of the fields in the rate line are changed, then the pricer group is redetermined. The old pricer group
and the new target pricer group are both locked. If the new target pricer group is already locked by another
user, all of the rate line information is changed back to the original values.
A Business Add-In (BAdI) is provided to determine the pricer group for a request line at the time of creation
of request lines or when searching for routes or getting responses based on attributes such as equipment
206
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
type, container shipping liners (CSL) item type, delivery mode, and receipt mode. The relevant BAdI is located
in Customizing for Transportation Management under
Business Add-Ins (BAdIs)
Container Shipping Liners
Forwarding Agreement Quotation
Lead to Agreement
BAdI: Determine Pricer Group .
 Example
If the pricer group of a rate line is 50000042, and user 1 changes the equipment type from 20ST to 20G0,
then the pricer group is determined as 50000043. However, as the pricer group 50000043 is locked by
user 2, then user 1 gets a lock conflict error message and the equipment type is reverted back to 20ST. The
pricer group remains as 50000042.
Related Information
Functions in Forwarding Agreement Quotations [page 203]
6.2.3 Request Lines
A request line in a forwarding agreement quotation (FWAQ ) is created to capture the potential booking
information that could come in the future. You add request lines to the flat view of an FWAQ.
Related Information
Creating Request Lines [page 207]
Creating Request Lines with Request Conditions [page 209]
Creating Request Lines with Service Products and Service Types [page 210]
Additional Actions for Request Lines [page 213]
6.2.3.1
Creating Request Lines
Create request lines to add details of a customer request to a forwarding agreement quotation (FWAQ).
Prerequisites
An FWAQ has been created with items that have an appropriate transportation charge calculation sheet
(TCCS) structure.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
207
Context
Request lines are added to the flat view of an FWAQ.
 Note
If the customer request is in a Microsoft Excel file, you can upload the request lines using the request for
quotation (RFQ) translator.
The steps below describe how to create a new request line from scratch. You can also select an existing request
line and choose the Copy button in the flat view. A new request line is created with the same information as the
source. If the source request line has route information attached to it, then the route information is not copied
to the new line.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the FWAQ number and choose Continue.
3. Choose Display Flat View.
4. In the flat view screen, choose Search to view the request and response lines.
5. In the Flat View screen, choose + (Insert) to insert a new request line.
6. In the CSL Item Type field, select one of the container shipping liners (CSL) item types (Marine, Inland
Origin, Inland Destination, Arbitrary Origin, or Arbitrary Destination).
7. Enter the other required information such as Commodity, Source Transportation Zone, Destination
Transportation Zone, Equipment Type, and other required information depending on the different
calculation bases used in the rate table of leading charge type.
 Note
For request lines of type Marine where the route is applicable, information such as the Source
Transportation Zone and Destination Transportation Zone is mandatory.
You can also enter partial data in a newly created request line in the flat view and then complete it at a later
point of time. The system does not delete any newly entered lines due to incomplete data. The data for
the request lines can also be maintained on the Details tab. However, the request lines are not editable if a
response line has been generated for them.
8. Choose Back to return to the main screen.
9. Save the FWAQ document.
Next Steps
Generate response lines for the request lines.
208
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Related Information
Response Lines [page 217]
Forwarding Agreement RFQ Translator [page 183]
Forwarding Agreement Quotation Creation [page 182]
Creating Request Lines with Request Conditions [page 209]
Creating Request Lines with Service Products and Service Types [page 210]
6.2.3.2
Creating Request Lines with Request Conditions
Create request lines with certain request conditions such as surcharge rules to add the details of a customer
request.
Prerequisites
An FWAQ has been created with items that have an appropriate transportation charge calculation sheet
(TCCS) structure.
Context
Request lines are added to the flat view of an FWAQ.
 Note
If the customer request is in a Microsoft Excel file, you can upload the request lines using the request for
quotation (RFQ) translator.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the FWAQ number and choose Continue.
3. Choose Display Flat View.
4. In the flat view screen, choose Search to view the request and response lines.
5. In the Flat View screen area, choose Insert Row to insert a new request line.
6. Enter the required information in the new request line.
7. Select the request lines and choose
Request Additional
Charge Update .
8. In the Change Type field, select Change Surcharge Rule, and then select the required surcharge rule and
enter a reason code.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
209
9. Choose Back to return to the main screen.
10. Save the FWAQ document.
Next Steps
Generate response lines for the request lines.
Related Information
Creating Request Lines [page 207]
Creating Request Lines with Service Products and Service Types [page 210]
Forwarding Agreement Quotation Creation [page 182]
Forwarding Agreement RFQ Translator [page 183]
6.2.3.3
Creating Request Lines with Service Products and
Service Types
Create request lines to add details of a customer request to a forwarding agreement quotation (FWAQ) and
then add services and service types.
Prerequisites
An FWAQ has been created with items that have an appropriate transportation charge calculation sheet
(TCCS) structure.
Context
Request lines are added to the flat view of an FWAQ.
 Note
If the customer request is in a Microsoft Excel file, you can upload the request lines using the request for
quotation (RFQ) translator.
210
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the FWAQ number and choose Continue.
3. Choose Display Flat View.
4. In the flat view screen, choose Search to view the request and response lines.
5. In the Flat View screen area, choose Insert Row to insert a new request line.
6. Enter the required information in the new request line.
7. Select the request line and go to the Services tab.
8. Choose Find Services.
A dialog box is displayed.
9. In the dialog box, select the service products that you want to add to this request line and then choose OK.
The selected service products and its services are added.
10. Choose + to add the individual service types to the request line.
11. Select the stage relevance, service type, and select the Mandatory for Rate checkbox.
12. Choose Back to return to the main screen.
13. Save the FWAQ document.
Next Steps
Generate response lines for the request lines.
Related Information
Creating Request Lines [page 207]
Creating Request Lines with Service Products and Service Types [page 210]
Forwarding Agreement Quotation Creation [page 182]
Forwarding Agreement RFQ Translator [page 183]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
211
6.2.3.4
Creating Request Lines for Empty Containers
Create a request line in a forwarding agreement quotation (FWAQ) to add the details of a customer request for
transporting an empty container.
Prerequisites
An FWAQ has been created with items that have an appropriate transportation charge calculation sheet
(TCCS) structure.
 Note
The rate typed node that is used to capture the details of the request must have the calculation base
TMCSL_EMPTY_CN. For more information, see SAP Note 3163537 .
Context
Request lines are added to the flat view of an FWAQ.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation app.
2. Enter the FWAQ number and choose Continue.
3. Choose Display Flat View.
4. In the flat view screen, choose Search to view the request and response lines.
5. In the Flat View screen area, choose Insert Row to insert a new request line.
6. Enter the required information in the new request line and select the Empty Container checkbox.
7. Choose Back to return to the main screen.
8. Save the FWAQ document.
Next Steps
Generate response lines for the request lines.
212
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Related Information
Creating Request Lines [page 207]
Creating Request Lines with Service Products and Service Types [page 210]
Forwarding Agreement Quotation Creation [page 182]
Forwarding Agreement RFQ Translator [page 183]
6.2.3.5
Additional Actions for Request Lines
You can choose the following options by navigating to the flat view and choosing the Request Additional button.
•
Set Manual Segment and Tier
When you create a request line and enter the commodity, origin, destination, and equipment (CODE)
information, the system determines the segment and tier and updates them in the manual segment and
tier fields. This implementation is done in a Business Add-In (BAdI), which is located in Customizing for
Transportation Management under
Container Shipping Liners
Lead to Agreement
Business Add-Ins
(BAdIs) Forwarding Agreement Quotation BAdI: Fetching of Segment and Tier Dimension Details .
You can use this action to change the manual segment and tier fields of the request line. When you choose
this option, a dialog box appears, and you need to enter a reason code and select the segment and tier. The
changes can be seen on the Other Details tab in the Segment and Tier section.
•
Revert Manual Segment and Tier
Choose this option to clear the manually set segment and tier fields. The system restores the determined
segment and tier in the request line and clears the reason code. The changes can be seen on the Other
Details tab in the Segment and Tier section.
•
Set/Reset Disclose Arbitraries
Choose this option to select or deselect the Disclose Arbitraries checkbox for the selected request lines.
This applies only for marine lines that are not in the Approved or Agreement Created status. The changes
can be seen on the Other Details tab on the Through Rates section.
This action can also be performed from the following locations:
•
•
FWAQ Header: Updates the Disclose Arbitraries checkbox for the FWAQ header, items, and rate lines
for a marine container shipping liners (CSL) item type.
•
FWAQ Item: Updates the Disclose Arbitraries checkbox for items and the corresponding rate lines for a
marine CSL item type.
Prevent/Allow Construction
Choose this option to select or deselect the following rate construction checkboxes for the request line:
•
•
•
•
Inland Origin Not Allowed
Inland Destination Not Allowed
Arbitrary Origin Not Allowed
Arbitrary Destination Not Allowed
This applies only for marine lines that are not in the Approved or Agreement Created status. The changes
can be seen on the Other Details tab in the Prevent Allow Construction Flags section.
This action can also be performed from the following locations:
•
FWAQ Header: Updates the rate construction flags for the FWAQ header, items, and rate lines of a
marine CSL item type.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
213
•
•
FWAQ Item: Updates the rate construction flags for items and the corresponding rate lines of a marine
CSL item type.
Set Commodity Group
Choose this option to assign a commodity group to a request line, provided the request line has the
calculation base for commodity, commodity group, and commodity group version. There must also be a
commodity group in the Approved status.
The commodity group and commodity group version number are updated with the selected value.
The commodity code in the request line is updated according to the value set for the attribute
RFQ_MULTIPLE_COM_CODE in Customizing for Transportation Management under
Liners
Basic Settings
Container Shipping
Maintain Configurable Constants .
•
Unassign Commodity Group
Choose this option to unassign a commodity group from a request line. You can then assign a new
commodity group by choosing Set Commodity Group.
•
Set Source Port Zone Group
Choose this option to assign a source port zone group to a request line, provided the request line has the
calculation base for source zone, source port zone group, and source port zone group version. There must
also be a port zone group in the Approved status.
The source port zone group and source port zone group version number are updated with the selected
value. The source zone in the request line is updated according to the value set for the attribute
PORT_ZN_GROUP in Customizing for Transportation Management under
Basic Settings
Container Shipping Liners
Maintain Configurable Constants .
•
Unassign Source Port Zone Group
Choose this option to unassign a source port zone group from a request line. You can then assign a new
source port zone group by choosing Set Source Port Zone Group.
•
Set Destination Port Zone Group
Choose this option to assign a destination port zone group to a request line, provided the request line has
the calculation base for destination zone, destination port zone group, and destination port zone group
version. There must also be a port zone group in the Approved status.
The destination port zone group and destination port zone group version number are updated with the
selected value. The destination zone in the request line is updated according to the value set for the
attribute PORT_ZN_GROUP in Customizing for Transportation Management under
Liners
Basic Settings
Container Shipping
Maintain Configurable Constants .
 Note
A transportation zone with the ID maintained in the Customizing activity Maintain Configurable
Constants must be created as this will be assigned to the Source Zone field in the request line.
•
Unassign Destination Port Zone Group
Choose this option to unassign a destination port zone group from a request line. You can then assign a
new destination port zone group by choosing Set Destination Port Zone Group.
•
Set Named Account Group
Choose this option to assign a named account group to a request line, provided the request line has the
calculation base for named account, named account group, and named account version. There must also
be a named account group in the Approved status.
In addition, the named accounts in the named account group must be a subset of the named accounts
maintained in the header section of the forwarding agreement quotation.
The named account group and named account group version number are updated with the selected
value. The Named Account field in the request line is updated according to the value set for the attribute
214
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
RFQ_MULTIPLE_NAC_CODE in Customizing for Transportation Management under
Liners
Basic Settings
Container Shipping
Maintain Configurable Constants .
•
Unassign Named Account Group
Choose this option to unassign a named account group from a request line. You can then assign a new
named account group by choosing Set Named Account Group.
•
Set Delete Operation
Choose this option to set the Rate Line Operation field to Delete, which means the rate line will be set to
Delete status when it is merged to the agreement.
For example, if you have a rate line in a forwarding agreement quotation for which the Rate Line Operation
is set as Delete, and if it has an overlap with a rate line in the forwarding agreement, then during the
agreement create/merge process, the existing line in the agreement is split into multiple rate lines. The
rate line in the agreement that has the same validity dates as the rate line from the forwarding agreement
quotation has the status Not Available for Rating (Deleted). These rate lines are not used for rate look-up
during charge calculation.
Deletion of rate lines in a forwarding agreement is a soft delete during the process of agreement create/
merge. The status of such rate lines is set to Not Available for Rating (Deleted)
•
Unassign Commodity Group, Unassign Named Account Group, Unassign Source Port Zone Group, and
Unassign Destination Port Zone Group
Choose these options to remove the assigned group information from the request lines.
•
Set Manual Slot Loss
Choose this option to update the Manual Lost Slots, which is displayed on the Other Details tab in the Cargo
Dimensions section.
You need to enter the reason code and a value for the slot loss.
•
Revert Manual Slot Loss
Choose this option to clear the manually updated value for slot loss. The manual value is replaced with the
value determined by the system at the time of request line creation and the reason code is cleared.
•
Set Manual Cargo Type
Choose this option to change the Manual Cargo Type, which is initially calculated at the time of request
line creation based on the dimensions such as Max. Length, Max. Width, and Max. Height of the equipment
type. This can be seen on the Other Details tab in the Cargo Dimensions section.
You need to enter the reason code and select the cargo type.
•
Revert Manual Cargo Type
Choose this option to clear the manually updated cargo type and replace it with the value determined
at the time of request line creation based on the dimensions of the equipment. The reason code is also
cleared.
•
Clear Routes
Choose this option to clear the routes and POL/POD information from the request line. You can then can
assign a new route by choosing Search Routes.
•
Charge Update
Choose this option to change the surcharge rule and update the payment information (settlement terms
and bill-to party) and manually add new charge types.
In the Charge Update dialog box, you need to choose the change type and enter the required details as
follows:
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
215
Change Type
What to Do
Change Surcharge Rule
Select a Surcharge Rule (All Inclusive Of, All Inclusive
of Except, or blank) and then enter a reason code and
choose OK.
If the Surcharge Rule is All Inclusive Of, the surcharge con­
dition of all the applicable charges is updated to Inclusive
Of with the exception entered.
If the Surcharge Rule is All Inclusive of Except, you are
prompted to enter the charges with the condition, rate,
currency, and rate type.
In this case, except for the charges in the exception list,
the surcharge condition of all other applicable charges will
be updated to Inclusive Of.
If the Surcharge Rule is blank, changes performed with the
surcharge rule as All Inclusive Of or All Inclusive of Except
are reverted.
In all the three cases, the total sum will remain unaffected.
Manual Addition of Charges
Select or deselect the Manual Charge checkbox. If the
Manual Charge checkbox is selected, enter the reason
code and charge details that are to be added. If the
Manual Charge checkbox is deselected, the manually
added charges are deleted.
Update Payment Information
Enter the settlement terms for the charge types. If the
overwrite flag is set for a charge type, then the settlement
terms are overwritten.
Enter the Bill-To Party Code for the charge types. If the
overwrite flag is set, then the Bill-To Party Code will be
overwritten.
Enter the Bill-To Party for the charge types. If the overwrite
flag is set, then the Bill-To Party is overwritten.
Enter the Place of Payment for the charge types. If the
overwrite flag is set, then the Place of Payment is overwrit­
ten.
•
216
Remove Routes
If the route information is updated in the request line, it will not be possible to make any changes to the
request line. You can choose this option to remove the routes from the selected request lines. This action
will only be executed if the response lines are not yet generated.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Related Information
Named Account Groups [page 46]
Commodity Groups [page 47]
Port Zone Groups [page 48]
6.2.4 Response Lines
Response lines contain the rate details that you, as a carrier, propose in reply to a request from a shipper
or logistics service provider (LSP). You can create a response line for each request line in the flat view of a
forwarding agreement quotation (FWAQ).
You create a response line for a request line by generating a route for the request line. The system creates a
response line by calling the route generator application programming interface (API) to generate routes for the
request line. The newly created response line contains the rates for the chosen route.
You can generate routes for response line creation using one of the following features:
•
Search Routes
The system retrieves all of the valid routes for the request and you choose the appropriate route.
•
Get Responses
The system automatically selects the best route for the request. You can generate response lines for
multiple request lines using the Get Responses feature.
Related Information
Forwarding Agreement Quotation Creation [page 182]
Getting Responses [page 217]
Generating Responses with Request Conditions [page 222]
Generation of Responses with Split Profiles [page 224]
6.2.4.1
Getting Responses
Get the responses for a request line in a forwarding agreement quotation (FWAQ) by searching for routes or
choosing Get Responses.
Prerequisites
•
A request line has been created in the FWAQ and it has the container shipping liners (CSL) item type as
either Marine, Inland Origin, Inland Destination, Arbitrary Origin, or Arbitrary Destination.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
217
•
A response item has been created for the request items to which the request lines belong.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the FWAQ number and choose Continue.
3. Choose Display Flat View.
4. Select the request line and then choose one of the following options:
•
•
Get Responses
Get Response
Search Routes and then select one of the routes and choose Pick and GRR.
If you choose the Pick Routes option in the Search Routes dialog box, then the selected route is
assigned to the request line, but no responses are generated. You can then choose
Get Response
Get Responses
to generate a response line.
 Note
•
You can delete the routes attached to a request line by choosing
Request Additional
Remove Routes , provided there are no responses generated for the request line.
•
If you have activated NoReqRout in the Customizing activity Maintain CSL Item Type
Configurations, then, upon generation of the response, the Route will be removed from Request
Rate line.
5. Save your entries.
Results
Depending on the type of CSL item the request line belongs to, the system checks whether routing is applicable
or not. In Customizing, you can configure whether routing is applicable for a CSL item type in a quotation. For
example, the Routing Req. field is selected for the CSL item type MAR (Marine), whereas this field is deselected
for the CSL item types INLO and INLD (Inland Origin and Inland Destination). This setting is maintained
in Customizing for Transportation Management under
Container Shipping Liners
Forwarding Agreement Quotation and Forwarding Agreement
Lead to Agreement
Maintain CSL Forwarding Agreement Quotation
Types .
If routing is applicable, the Routing API is called to fetch the routes. There could be more than one route for
a given combination of source and destination zones. If more than one route is returned, the request line is
duplicated so that each request has only one route solution. For example, if you have one request line and there
were three routes returned by the Routing API, then after you choose Get Responses, there are three request
lines corresponding to each of the three routes and three responses.
You can go to the Revenue tab of the response line to check the rates picked up from the tariff agreements.
Leading Charge Surcharge Condition as Subject To
The surcharge condition of the leading charge type corresponding to each CSL item type could be Subject
To or Subject to Fixed depending on the surcharge condition maintained in the respective calculation sheet
218
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
of the tariff agreement. If you want to manipulate the surcharge condition of the charge type, you can do so
using the Business Add-In (BAdI) located in Customzing for Transportation Management under
Shipping Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Charge Determination
Container
BAdI: Manipulation
of Calculation Sheet Before Charge Calculation .
If the surcharge condition of the leading charge type is maintained as Subject To in a forwarding agreement
quotation, the same surcharge condition is moved to the agreement. If a booking is done against this
forwarding agreement, then during the rate look-up in charge calculation, the system retrieves the rates from
the tariff agreement, and this is reflected in the latest rates.
Service Products
If service products or service types are added to the request line, then during the generation of the response,
the calculation sheets of the relevant service products are processed. For service products, the calculation
sheet has been enhanced with the following fields:
•
•
Deviation from Tariff
Surcharge Condition Source
If a percentage is maintained for the Deviation from Tariff, then the tariff rates are fetched and the percentage
value is applied to derive the final rate for the service charges.
Related Information
Tariff Management [page 173]
Forwarding Agreement Quotation Creation [page 182]
6.2.4.1.1
Example: Rate Construction Using a Tariff
Consider an example of a charge calculation for a container in a door-to-door scenario done against a tariff.
The container is shipped from the customer door location in Beijing to the consignee in Chicago.
The below figure displays the charge calculation logic with the sequence of steps executed by the system to
construct a rate for a door-to-door scenario.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
219
Rate Construction for Door-to-Door Scenario
The following table lists the steps that the system follows when constructing a rate:
No.
Step
Description
1
Preprocess: Find the through-rate.
The system evaluates the ocean carrier
freight (OCF) charge rate table for the
charge calculation using the origin and
destination information. If the system
finds the rates, it creates a through-rate
and stops the charge calculation proc­
ess. Otherwise, the system continues
with the next step.
2
Divide the route at the port of discharge If the system cannot create a through(POD).
rate in Step 1, it divides the route at the
POD to create the inland destination
leg. The inland destination charge type
is evaluated using the POD and the final
destination location. If the system finds
the destination inland rate, it calculates
the OCF rates for the port of loading
(POL) and POD.
3
Divide the route at the POL.
The system divides the route at the
POL, and evaluates the inland origin
charge types for the origin location and
the POL. If the system finds the inland
rate, it calculates the OCF rate for the
POL to the destination location. If the
OCF rate is calculated successfully, the
charge calculation process stops. Oth­
erwise, the system continues with the
next step.
220
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
No.
Step
Description
4
Divide the route at the POL and POD.
The system divides the route at the POL
and POD to allow the following evalua­
tions:
•
The inland origin charge type to be
•
The inland destination charge type
evaluated using the origin and POL
to be evaluated using the POD and
destination
The OCF rate table is retrieved for the
POL and POD.
5
Determine the destination base port.
The system determines the destination
base port by evaluating the arbitrary-atdestination charge type from Customiz­
ing using the POD. The OCF rate table
is evaluated using the POL and destina­
tion base port. The inland origin and in­
land destination charge types are eval­
uated using the methods described in
Steps 2 and 3.
6
Determine the origin base port.
The origin base port is determined
by evaluating the arbitrary-at-origin
charge type from Customizing using
the POL. The OCF rate is evaluated us­
ing the origin base port and POD. The
logic of the inland charge type is eval­
uated using the methods described in
Steps 2 and 3.
7
Determine the origin and base ports.
The origin and destination base ports
are determined from the arbitraryat-origin and arbitrary-at-destination
charge types using the POL and POD.
The OCF rate table is evaluated based
on the origin and destination base
ports. The inland charge type is evalu­
ated using the methods described in
Steps 2 and 3.
The result of the processing above is that a rate is constructed for the given combination of origin and
destination locations using the following charge types: OCF, transport additional origin (TAO), transport
additional destination (TAD), inland origin, and inland destination.
The OCF and marine surcharges are picked from the marine tariff. The inland origin charges and its surcharges
are picked from the inland origin tariff. The inland destination and its surcharges are picked from the inland
destination tariff. The TAO and the TAD charge types are looked-up from the arbitrary origin and arbitrary
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
221
destination tariffs. If service products/services are requested, then the corresponding tariff types (service
inland origin, service marine, and service inland destination) are processed depending on the different legs
involved.
The different tariffs used in the rate construction are maintained in the Maintain Standard Tariff - CSL and
Maintain Arbitrary Tariff - CSL apps. You can maintain the base ports for port of loading and port of destination
in the Maintain Base Port - CSL app.
 Note
Various rate construction scenarios are possible, for example, port-to-port, ramp-to-ramp, port-to-door,
ramp-to-door, and so on. However, all the scenarios follow the same pattern as the door-to-door scenario.
Related Information
Tariff Management [page 173]
Integration [page 278]
Rate Construction [page 281]
Charge Calculation in Bookings [page 278]
6.2.4.2
Generating Responses with Request Conditions
Generate responses with request conditions for a request line in a forwarding agreement quotation (FWAQ).
Prerequisites
A request line has been created in the FWAQ and it has the container shipping liners (CSL) item type as either
Marine, Inland Origin, Inland Destination, Arbitrary Origin, or Arbitrary Destination.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the FWAQ number and choose Continue.
3. Choose Display Flat View.
4. Select the request line and then choose
Get Responses
Generate Response with Request Conditions .
5. Save your entries.
222
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Results
Depending on the type of CSL item the request line belongs to, the system checks whether routing is applicable
or not. In Customizing, you can configure whether routing is applicable for a CSL item type in a quotation. For
example, the Routing Req. field is selected for the CSL item type MAR (Marine), whereas this field is deselected
for the CSL item types INLO and INLD (Inland Origin and Inland Destination). This setting is maintained
in Customizing for Transportation Management under
Container Shipping Liners
Forwarding Agreement Quotation and Forwarding Agreement
Lead to Agreement
Maintain CSL Forwarding Agreement Quotation
Types .
If routing is applicable, the Routing API is called to fetch the routes. There could be more than one route for
a given combination of source and destination zones. If more than one route is returned, the request line is
duplicated so that each request has only one route solution. For example, if you have one request line and there
were three routes returned by the Routing API, then after you choose Get Responses, there are three request
lines corresponding to each of the three routes and three responses.
You can go to the Revenue tab of the response line to check the rates picked up from the tariff agreements. If
service products or service types are added to the request line, then during the generation of the response, the
calculation sheets of the relevant service products are processed. For service products, the calculation sheet
has been enhanced with the following fields:
•
•
Deviation from Tariff
Surcharge Condition Source
If a percentage is maintained for the Deviation from Tariff, then the tariff rates are fetched and the percentage
value is applied to derive the final rate for the service charges.
Related Information
Tariff Management [page 173]
Forwarding Agreement Quotation Creation [page 182]
6.2.4.3
Business Add-Ins for Response Generation
The following Business Add-Ins (BAdIs) are available during the response generation process.
These BAdIs are located in Customizing for Transportation Management under
Lead to Agreement
•
•
•
Business Add-Ins (BAdIs)
Container Shipping Liners
Forwarding Agreement Quotation .
BAdI: Preparation of Routes for Response Generation: Handles the generation and the filtering of the routes.
BAdI: Determine Pricer Group: Determines the pricer group based on attributes such as equipment type,
container shipping liner (CSL) item type, delivery mode, and receipt mode.
BAdI: Adjustment of Communication Structure and Response Node: Adjusts the communication structure
before calling the charge calculation API and update the response data.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
223
Related Information
Getting Responses [page 217]
Generating Responses with Request Conditions [page 222]
6.2.4.4
Generation of Responses with Split Profiles
A split profile consists of a list of charge types. You maintain the validity dates of these charge types in the tariff
agreement and they are used during the generation of responses to determine the number of responses to be
created for a request line.
Split profiles need to be configured carefully, as they could result in the creation of a large number of response
lines and the performance would deteriorate. For a combination of quotation type and container shipping
liners (CSL) item type, you can maintain the split profile ID in Customizing for Transportation Management
under
Container Shipping Liners
Agreement
Lead to Agreement
Forwarding Agreement Quotation and Forwarding
Maintain CSL Forwarding Agreement Quotation Types .
During the response generation, the system reads the split profile ID corresponding to the CSL item type and
generates the responses accordingly. If no profile is maintained, then the responses will not be split. If you want
the responses to be split based on the validity of only the leading charge type, then you can maintain a split
profile with the leading charge type.
 Example
You have maintained a split profile that has OCF and BAF charge types.
The request line has a validity period of 01 January 2020 to 31 December 2020.
In the tariff, you have maintained rate lines with the following validity periods for the OCF charge type:
•
•
01 January 2020 to 30 June 2020
01 July 2020 to 31 December 2020
You have maintained rate lines with the following validity periods for the BAF charge type:
•
•
•
01 January 2020 to 31 March 2020
01 April 2020 to 30 September 2020
01 October 2020 to 31 December 2020
With the above setup, after the response line generation you will see four responses with the following
validity periods:
•
•
•
•
224
Response 1: 01 January 2020 to 31 March 2020
Response 2: 01 April 2020 to 30 June 2020
Response 3: 01 July 2020 to 30 September 2020
Response 4: 01 October 2020 to 31 December 2020
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Related Information
Tariff Management [page 173]
Forwarding Agreement Quotations [page 181]
6.2.4.5
Working with Response Lines
For a request line, the system creates a response line by calling the route generator application programming
interface (API) to generate routes. The newly created response line contains the rates for the chosen route. The
rate details can be viewed on the Revenue tab for each response.
On the Revenue tab, the details are categorized into the following main parts:
•
•
•
Sales-proposed fields
Base fields
Context fields
For example, the values for the surcharge condition and the rate of a charge type in the sales-proposed fields
can be changed by the pricer by making exceptions.
Exception for Percentage Charge Types
For percentage charge types, you can make exceptions on the percentage value in addition to amount as
follows:
1. Select the percentage charge type, and enter an Exception Reason Code.
2. Enter the Surcharge Condition, for example, Subject to Fixed.
3. If the rate type is Percentage, then enter a value in the Rate and % for Rate Currency columns.
4. If you want to fix the amount, then change the rate type to Rate Without Unit and enter the amount and
currency in the Rate and Rate Currency fields.
The base fields refer to the rates and other attributes fetched from the tariff configured in the system. The
context fields have the values of the latest executed actions. For example, when you choose Calculate Compare
with Tariff, the context fields display the results of this action.
You can filter the charge types on the Revenue tab using various views such as Inland Origin, Inland Destination,
Marine, Services, and so on to display only the charge types that belong to a certain leg. You can use the
duration-based charges (DBC) view to display only the DBC-related charge types.
Show Base Rates
On the Revenue tab, you can choose the Show Base Rates button to navigate to the exact rate line from the
tariff rate tables that was used for rate look-up during the generation of responses for a request line. If a rate
appears for any charge types that are picked up from a rate table, you can select the specific charge type and
then choose Show Base Rates. This feature is also available on other tabs such as Agreement Details, Context
Information, and Audit Trail.
You can make many other updates to the response lines using the options under the Response Additional
button.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
225
Related Information
Getting Responses [page 217]
Additional Actions for Response Lines [page 226]
6.2.4.6
Additional Actions for Response Lines
You can choose the following options by navigating to the flat view and choosing the Response Additional
button.
•
Validate Response
Select one or more response lines and choose this option to update the Response Completeness Status to
Manually Completed. This is a mandatory step before the approval of the response lines when there is no
rate found in the tariff for the leading charge type during the response generation process. The values of
the various statuses can be found on the Status tab.
•
Set Agreement
Choose this option to set the Target Agreement for the response lines by selecting one of the agreements
in a dialog box that lists the agreements from the Eligible Agreement List. You must first choose Determine
Eligible Agreements in the FWAQ header. You can see the updated Target Agreement on the Agreement
Details tab.
•
Charge Update
Select one or more response lines and choose this option to change the following details:
•
•
•
•
•
•
•
226
Surcharge Rule
Surcharge Condition
Rate
Subject to New Charge checkbox
Through Rate checkbox
Manually add new charge types
Update payment information such as Settlement Terms, Bill-To Party Role Code, Bill-To Party, and Place
of Payment
You need to choose the appropriate change type as follows:
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Change Type
What to Do
Change Surcharge Rule
Select a Surcharge Rule (All Inclusive Of, All Inclusive
of Except, or blank) and then enter a reason code and
choose OK.
If the Surcharge Rule is All Inclusive Of, the surcharge con­
dition of all the applicable charges is updated to Inclusive
Of with the exception entered.
If the Surcharge Rule is All Inclusive of Except, you are
prompted to enter the charges with condition, rate, cur­
rency, and rate type. In this case, except for the charges
in the exception list, the surcharge condition of all other
applicable charges is updated to Inclusive Of.
If the Surcharge Rule is blank, changes performed with the
Surcharge Rule as All Inclusive Of or All Inclusive of Except
are reverted.
In all the three cases, the total sum remains unaffected. All
the changes can be seen in the sales-proposed fields on
the Revenue tab of the corresponding response lines.
Manual Addition of Charges
Select or deselect the Manual Charge checkbox.
If the Manual Charge checkbox is selected, then enter the
reason code and charge details that are to be added. If
the Manual Charge checkbox is deselected, then manually
added charges are deleted.
Update Payment Information
Enter the Settlement Terms for the charge types. If the
overwrite checkbox is selected for a charge type, then the
Settlement Terms is overwritten.
Enter the Bill-To Party Code for charge types. If the over­
write checkbox is selected, then the Bill-To Party Code is
overwritten.
Enter the Bill-To Party for the charge types. If the overwrite
checkbox is selected, then the Bill-To Party is overwritten.
Enter the Place of Payment for the charge types. If the
overwrite checkbox is selected, then the Place of Payment
is overwritten.
The updated fields can be seen in the sales-proposed
fields of the response line.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
227
Change Type
What to Do
Change Surcharge Condition
Enter the reason code, add the charge types and sur­
charge condition, and then choose OK.
The surcharge condition of the charge types is updated
along with the reason code. The updated fields can be
seen in the sales-proposed fields of the response line.
Change Rate
Enter the reason code, add the charge types and amount
adjustment conditions to change the amount, and then
choose OK.
For the charge types you have entered, the rate is changed
and the amount is recalculated. The updated fields can be
seen in the sales-proposed fields of the response line.
Change Subject to New Charge
Select or deselect the Subject to New Charge checkbox.
By default, the Subject to New Charge checkbox is se­
lected.
If you deselect Subject to New Charge, you must enter a
reason code. Choose OK and the Subject to New Charge
checkbox is updated.
Change Through Rate
Select or deselect the Through Rate checkbox. By default,
the Through Rate checkbox is deselected.
If you select the Through Rate checkbox, you must enter
an exception code.
If the Through Rate checkbox is selected, inland charges
are marked as Inclusive Of when there are any inland legs.
If the Through Rate checkbox is deselected, all the previ­
ous changes done with the Set Through Rate option are
reverted.
•
Adapt Rate (from Context Update)
Choose this option to adapt the rates from the context fields to the sales-proposed fields in the revenue
for the charge types where exceptions have not been made. The context rates can be from a tariff or an
agreement based on your previously executed actions. For more information about how the context fields
are populated, see Calculate (Compare with Tariff) and Calculate (Compare with Existing Agreement) below.
•
Adapt Rate (from Context Overwrite Exceptions)
Choose this option to overwrite the sales-proposed rates in revenue with the rates from the context fields.
The context rates could be from a tariff or an agreement based on your previously executed actions. For
more information about how the context fields are populated, see Calculate (Compare with Tariff) and
Calculate (Compare with Existing Agreement) below.
•
Mass Update GRI/GRD
Choose this option to select one or more response lines and update the general rate adjustment (GRA)
attributes such as Subject to GRI, Subject to GRD, and Effective Date. You can see the updated values on
the GRA tab in the flat view.
•
Get Context Information
228
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Choose this option to get a list of agreements that have rate lines overlapping with the selected response
line. You can see the result on the Context Information tab.
•
Calculate (Compare with Existing Agreement)
Choose this option to compare the sales-proposed rates with the rates from an existing agreement for a
response line. You need to enter a simulation date and an agreement ID. The rates from the agreement are
fetched and the results are overwritten to the context fields and in the header of the revenue.
Sales-proposed rates can be overwritten from the context fields by choosing Adapt Rate (From Context
Update) or Adapt Rate (From Context Overwrite Exceptions).
•
Calculate (Compare with Tariff)
Choose this option to compare the sales-proposed rates with the tariff rates for a response line for a
specified simulation date. The rates for this simulated date are overwritten to the context fields and in the
header of the revenue.
Sales-proposed rates can be overwritten from context fields by choosing Adapt Rates (From Context
Update) or Adapt Rates (From Context Overwrite Exceptions).
•
Validity Exceptions
Choose this option to split an existing response line into multiple responses based on the valid-from and
valid-to dates you enter. The validity dates in the response lines are updated and/or new response lines
(for the same request line) are created/deleted based on the validity dates entered.
•
Revert Exceptions
Choose this option to revert all the exceptions made on the Revenue tab. The initial state of the response
line right after you chose Get Responses is restored.
•
Prevent/Allow Construction
Choose this option to select or deselect the following rate construction checkboxes for the response line:
•
•
•
•
Inland Origin Not Allowed
Inland Destination Not Allowed
Arbitrary Origin Not Allowed
Arbitrary Destination Not Allowed
This option is applicable only for marine lines that are not in the Approved or Agreement Created status.
The changes can be seen on the Other Details tab in the Prevent Allow Construction Flags section.
This action can also be performed from the following locations:
•
FWAQ Header: Updates the rate construction flags for the FWAQ header, items, and rate lines of a
marine CSL item type.
•
FWAQ Item: Updates the rate construction flags for items and the corresponding rate lines of a marine
CSL item type.
Related Information
Response Lines [page 217]
Status Management [page 232]
Tariff Management [page 173]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
229
6.2.4.7
Miscellaneous Actions in the Flat View
You can perform the following actions by navigating to the flat view and choosing the Miscellaneous button.
•
Show Descriptions
Choose this option to display the descriptions of the calculation bases that are part of the request/
response line.
•
Create Commodity Group, Create Named Account Group, and Create Port Group
Choose these options to create commodity groups, named account groups, and port zone groups from the
forwarding agreement quotation. Once the group master data is created and approved, it can be assigned
to the request lines.
•
Replace Commodity Group, Replace Source Port Zone Group, Replace Destination Port Zone Group, and
Replace Named Account Groups
Choose these options to replace the existing commodity group, source port zone group, destination port
zone group, or named account groups and their version number with a new group ID and version. This
option is also available for the FWAQ header and items. You can see the details on the Group Information
tab in the flat view.
Related Information
Creating Named Account Groups [page 46]
Creating Commodity Groups [page 48]
Creating Port Zone Groups [page 49]
6.2.5 Approving Response Lines
Approve response lines to move them from the forwarding agreement quotation (FWAQ) to the forwarding
agreement.
Prerequisites
•
•
•
You have generated a response line for a request line in the FWAQ.
You have chosen Determine Eligible Agreements in the FWAQ header to get the matching agreements.
The consumer codes (for example, OVERLAP or DUPLICATE) and the parameters with which the rate
line comparison should be performed between the source and the target rate lines have been defined
in Transportation Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Set Up Rate Line Comparison .
230
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the FWAQ number and choose Continue.
3. Choose Display Flat View.
4. In the flat view, select one or more response lines and choose Approve.
Results
During the approval of a response line, the system does a duplicate check and an overlap check. The duplicate
check involves checking (other rate lines with the same attributes) against other response lines within the
same FWAQ.
The overlap check is done against rate lines of agreements available in the Eligible Agreement List. The
overlap check can check if there is a single overlap, multiple overlaps, or no overlap. The setting of the target
agreement in the response lines is based on the results of the overlap check. The details of the overlapping
agreement such as the Agreement ID, Agreement Version, Agreement Item No., Rate Table, and Rate Line ID are
displayed along with it’s the validity dates in the Overlapping Agreement Records section.
The possible outcomes are as follows:
•
No Overlap
If there is no overlap, then the default agreement in the FWAQ header is set as the target agreement. This is
indicated in the Target Agreement Type field. The Target Agreement field is not updated.
•
Single Overlap
If there is single overlap with an agreement, then this agreement is set as the Target Agreement, provided
its validity fully covers the validity of the rate line. The Exact Match field in the Overlapping Agreement
Records section must be Yes. If not, the approval is denied.
•
Multiple Overlaps
If the system finds multiple overlaps for a response line, and if the overlapping rate lines are from the same
rate table of the agreement, then it will set as the Target Agreement. If the overlapping rate lines are from
different rate tables, then it is considered as an error.
The process described above is the default implementation. If you want to change the process to suit your own
requirements, you can create your own Business Add-In (BAdI) implementation.
Related Information
Business Add-Ins for the Approval Process [page 232]
Response Lines [page 217]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
231
6.2.5.1
Business Add-Ins for the Approval Process
During the approval of a response line, the system does a duplicate check and an overlap check. Business
Add-Ins (BAdIs) are provided for the duplicate check, overlap check, and setting of the target agreements.
If you want to change the process to suit your own requirements, you can create your own BAdI
implementations. The following BAdIs are available in Customizing for Transportation Management under
Container Shipping Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Forwarding Agreement
Quotation :
•
BAdI: Checking of Duplicates: Performs duplicate checks during the response line approval process in a
forwarding agreement quotation.
•
•
BAdI: Checking of Overlaps: Performs overlap checks on the response lines during the approval process.
BAdI: Setting of Target Agreement: Sets the target agreement for a response line during the approval
process in the forwarding agreement quotation.
Related Information
Approving Response Lines [page 230]
6.2.6 Status Management
The system displays several statuses that allow you to view the progress of request lines and response lines in
forwarding agreement quotations (FWAQs).
SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA provides
the following additional statuses for response lines. You can view the statuses for a response line on the Status
tab in the flat view of an FWAQ.
Status
Description
Life Cycle Status
Indicates the life cycle status of the request/response line.
Duplicate Check Status
Indicates the status of the duplicate check performed during
the approval of the response line.
Overlap Check Status
Indicates the status of the overlap check performed during
the approval of the response line.
External Status
Indicates whether the response entity (at FWAQ header,
item, request line, and response line level) is valid from the
customer's perspective.
232
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Status
Description
Response Completeness Status
Indicates the validation of the response line if there is no rate
found from the standard tariff.
Agreement Creation Status
Indicates the status of the response line with respect to
agreement creation.
In the flat view, you can access the following status-relevant options by choosing the Status button:
•
Set Life Cycle Status (In-Process)
Choose this option to update the response lines with the life cycle status Approved to In Process.
•
Set External Status (Accept/Award)
Choose this option to update the external status to Accepted/Awarded for the FWAQ header and items. At
the rate line level, if the life cycle status is Approved and the external status is Submitted, then it can be
updated to Awarded status.
•
Set External Status (Rejected)
Choose this option to set the external status to Rejected for the FWAQ header, items, and rate lines.
•
Set External Status (Submitted)
Choose this option to set the external status to Submitted for the FWAQ header and items. At the rate
line level, this can be updated only if life cycle status is Approved. A Business Add-In (BAdI) is provided
(/TMCSL/BADI_CNGD_TO_SUBMIT), which you can use to do additional processing.
•
Set External Status (Valid)
Choose this option to initialize the external status to Valid. You can choose this option from the FWAQ
header, items, and rate lines.
Related Information
Response Lines [page 217]
Forwarding Agreement Quotation Creation [page 182]
6.2.7 Duration-Based Charges and Exceptions
Duration-based charges (DBC) and exceptions can be added to individual response lines in a forwarding
agreement quotation (FWAQ).
You add DBC response-line-level exceptions on the Revenue tab of the response line. You must enter a reason
code to add a response-level exception.
 Note
Approved response-line exceptions are copied to the forwarding agreement (FWA) when the FWAQ is
converted.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
233
Related Information
Adding DBC Exceptions to Response Lines [page 236]
Forwarding Agreement Quotation Creation [page 182]
6.2.7.1
Duration-Based Charge Scenarios and Event
Profiles
The duration for duration-based charges (DBC) is based on the events for the containers, which means that
charges are calculated for a period of time between a start and a stop event.
Additionally, the DBC duration needs to be evaluated based on booking information associated with the
container. The state of the booking information governs the determination of the start and stop events for the
duration. To support this, the system allows you to define a DBC scenario for a DBC charge type based on the
booking information. The information about the events to be considered for start and stop events is grouped in
event profiles.
You can define different DBC scenarios for calculating DBC charges in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Duration-
Based Charges Maintain DBC Scenarios and Event Profiles . Each scenario must have a unique set of
attributes (multiple scenarios with the same set of attributes are not permitted).
Before you can define a DBC scenario, you must have already created the event profiles, which are used to
configure start and stop event profiles in the decision layer data. You can configure multiple events for a given
event profile and specify whether the event is expected or not. A prerequisite for this step is that events have
been created.
Below is an example of the START1 event profile:
Event
Description
Expected Event
ARRIV_DEST
Arrival at Destination
X
/CSL/DISCHARGE_BEGIN
Discharge Begin
X
/CSL/GATE_OUT
Gate Out
X
/CSL/LOAD_BEGIN
Load Start
X
Once you have created event profiles, you can define DBC scenarios. Below is an example DBC scenario:
Field Name
Mandatory/Optional
Entry
DBC Scenario
Mandatory
BOM_LEH_E
DBC Scenario Description
Mandatory
MUMBAI <-> LE HAVRE EXPORT
234
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Field Name
Mandatory/Optional
Entry
Charge Type
Mandatory
YDTE (Detention Export)
Direction
Mandatory
Export
Country
Mandatory
AU (Australia)
Resource Class
Optional
Any
Location
Optional
AUBNE-BCT
City
Optional
BRISBANE
DIT Location Role
Optional
Event Profile Start1
Mandatory
START1
Event Profile Stop1
Mandatory
STOP1
You must specify at least one start and one stop event profile when defining a DBC scenario. You can enter up
to three start and stop event profiles for each DBC scenario. For example, if you fill the Event Profile Start1 field,
you must also fill the Event Profile Stop1 field. This also applies to the second and third profiles you enter.
After defining the DBC scenario, you need to define for which movement type the DBC scenario is valid. You
can configure multiple movement types for a given DBC scenario. A prerequisite is that you have already
created DBC scenarios and movement types.
Below is an example of a movement type maintained for a particular DBC scenario:
DBC Scenario
DBC Scenario Description
Movement Type
Description
HAM_MIA_E
HAMBURG <-> MIAMI EX­
DD
Door to Door
PP
Port to Port
PORT
HAM_MIA_E
HAMBURG <-> MIAMI EX­
PORT
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
235
6.2.7.2
Adding DBC Exceptions to Response Lines
Add exceptions for duration-based charges (DBC) at the response line level for a forwarding agreement
quotation (FWAQ).
Prerequisites
The specific charge type for DBC has been maintained in Customizing for Transportation Management
under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain Charge Type
Definition .
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the FWAQ number and choose Continue.
3. Choose Display Flat View.
4. In the flat view screen, choose Search to display the request and response lines.
5. Choose the relevant response line.
6. On the Revenue tab, filter the DBC charges by choosing
Pricing View
Duration Based Charges .
7. Specify a reason code in the Exception Reason Code field.
The system sets the free-days fields as editable.
8. Specify the sales-proposed free day, sales-proposed free day type, and sales-proposed chargeable day
type information.
9. Choose Back to return to the main screen.
10. Save the FWAQ document.
Related Information
Duration-Based Charges and Exceptions [page 233]
Forwarding Agreement Quotation Creation [page 182]
236
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
6.2.8 Conversion of FWAQs to Forwarding Agreements
Once the rates in a forwarding agreement quotation (FWAQ) have been negotiated and finalized with the
customer (the rate requester), you convert the FWAQ to a forwarding agreement (FWA).
During the conversion, the rates are transferred to a new FWA or to an existing FWA. The rates in an FWAQ
become effective for a booking after the FWAQ is converted to an FWA.
The process for converting an FWAQ to an FWA is as follows:
1. Determine the eligible forwarding agreements
You determine a list of existing forwarding agreements (FWAs) that are eligible for conversion from a
specific forwarding agreement quotation (FWAQ). The system looks for agreements that have the same
attributes such as ordering party, sales organization, validity dates, named account, participant, and so on.
The system determines the following types of agreements:
•
•
•
Full Overlap
Partial Overlap
Historical
By default, all agreements that fully overlap with the quotation validity (the proposal agreement validity
dates) have the Target Agreement checkbox selected.
You can also set one of the agreements as the Default Agreement. Any response lines that do not find a
target agreement during the approval process are marked to go to this default agreement.
2. Convert the FWAQ to an FWA
During the conversion, the system performs the following tasks:
•
•
•
Performs overlap checks on the rate lines that are being transferred from the FWAQ to the FWA
Creates and adjusts rate lines and other details on the FWA
Sets the agreement creation status of the response line to Created based on the results of the
conversion activity if the FWAQ is of type Quotation
 Note
If the FWAQ is of type Tender, then after the approval of the response lines, they must be submitted
to the customer for their acceptance. You can use the Submit button in the quotation header or
choose
Set External Status
Submit
at the quotation item level or in the flat view.
Additional processing during the submit process can be implemented in the Business Add-In
(BAdI) /TMCSL/BADI_CNGD_TO_SUBMIT. If the rates (and other conditions) are acceptable to the
customer, then the External Status for these response lines is set to Awarded. The response lines
can now be moved to the Target Agreement.
3. View the audit trail.
Once the FWA has been created, you can view the audit trail, which lists the origin of the rate lines.
Related Information
Forwarding Agreement Quotation Header Processing [page 204]
Creating Agreements from FWAQs [page 238]
Audit Trail [page 240]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
237
Forwarding Agreement Quotation Creation [page 182]
6.2.8.1
Creating Agreements from FWAQs
Convert a forwarding agreement quotation (FWAQ) into a forwarding agreement (FWA) once the rates have
been finalized.
Prerequisites
•
•
You have saved the FWAQ.
•
•
You have approved the response lines.
You have determined the eligible FWAs.
If the list of partial and fully overlapping agreements changes, then the system will stop processing and
prompt you to choose Determine Eligible Agreement. During the quotation to agreement conversion, if new
overlapping rate lines are found, then they are not processed.
You have assigned target agreements to individual response lines as needed.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the FWAQ number and choose Continue.
3. Choose Create/Update Agreement.
Results
The system performs the following tasks:
•
•
Performs overlap checks on the rate lines that are being transferred from the FWAQ to the FWA.
Creates new FWAs or updates existing FWAs, and adjusts rate lines and other details in the FWAs.
You can use a Business Add-In (BAdI) to create or update the header details for a new or updated
agreement. You make the relevant settings in Customizing for Transportation Management under
Container Shipping Liners
Quotation
•
238
Lead to Agreement
Business Add-Ins (BAdIs)
Forwarding Agreement
BAdI: Merging of Headers .
Sets the agreement creation status of the response line to Created.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
Next Steps
•
•
View the creation status on the Status tab for the selected response line.
View the audit trail for the rate lines in the agreement.
Related Information
Audit Trail [page 240]
Status Management [page 232]
Conversion of FWAQs to Forwarding Agreements [page 237]
Forwarding Agreement Quotation Creation [page 182]
6.2.8.2
Background Creation and Update of Agreements in
FWAQs
To improve the system performance, you can execute certain processes for forwarding agreement quotations
(FWAQ) in background mode.
You configure the required settings for background remote function call (bgRFC) activities in the following
Customizing activities:
•
Customizing for Transportation Management under
Basic Settings
•
Lead to Agreement
Maintain Settings for bgRFC Activities
Customizing for Transportation Management under
Basic Settings
Container Shipping Liners
Container Shipping Liners
Lead to Agreement
Maintain Trigger Configuration for bgRFC Activities
These settings are used to execute the following actions in background mode:
•
•
Creation and update of agreements in forwarding agreement quotations
Creation of quotations in forwarding agreements
Once the bgRFC activity is triggered, the FWAQ is shown in display mode and the Edit button is disabled. On the
General Data tab, you can see the bgRFC activity code recorded in red. On the bgRFC tab, you can see the newly
created unit ID and the information recorded. You can also check the status and the number of tried times on
this tab.
Related Information
Conversion of FWAQs to Forwarding Agreements [page 237]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
239
6.2.8.3
Audit Trail
The system stores an audit trail for each forwarding agreement (FWA) rate line. The audit trail shows the origin
of the FWA rate lines and the type of updates.
Audit trails are generated during the conversion of a forwarding agreement quotation (FWAQ) to an FWA. The
audit trail shows an entry for each time a response line is converted to an agreement rate line or an agreement
rate line is updated from a response line.
You can find the audit trails for rate lines on the Audit Trail tab in the flat view of the agreement.
The audit trail includes the following details:
Field
Description
Audit Trail ID
Newly generated number
Adjust Type
Type of adjustment: Creation, Truncation, or Rate Adjust­
ment
Process Type
Process through which rate line was created: Agreement
Creation, Merge, or Regulatory Approval
Created
Indicates if this is a newly created rate line
Reference Document Number
Source quotation
Reference Document Item Number
Item number in the source quotation
Reference Rate Table
Rate table in the source quotation
Reference Audit Trail ID
Audit trail of rate line that led to the creation of new rate line
or adjustment of rate line in agreement.
Past Valid Start Date
Initial start date of rate line
Past Valid End Date
Initial end date of rate line
Related Information
Conversion of FWAQs to Forwarding Agreements [page 237]
Forwarding Agreement Quotation Creation [page 182]
240
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
6.3
Technical Settings
Parallel Processing During Response Generation
To improve the system performance, you can enable parallel processing for the response generation process.
Response generation is triggered when you select one or more request lines in the Flat View and choose Get
Responses or when you choose Search Routes and use the Pick and GRR option.
You can configure the number of request lines to be executed in a batch in Customizing for Transportation
Management under
Forwarding Agreement
Container Shipping Liners
Technical Settings
Lead to Agreement
Forwarding Agreement Quotation and
Maintain Parallel Processing Blocks .
Background Processing
Some of the processes in the forwarding agreement quotation can be run in background mode for a defined
block size called units. This is to enable better memory management during the execution of the processes.
In Customizing, you can maintain actions for the Business Object Processing Framework (transaction BOBF)
action, which is implemented with the job application programming interface (API). The maintained actions are
then called in the job API sequentially, in the back-end or in the front-end.
You maintain the settings for background job activity in Customizing for Transportation Management
under
Container Shipping Liners
Agreement
Technical Settings
Lead to Agreement
Forwarding Agreement Quotation and Forwarding
Maintain Settings for Background Job Activities .
You can use a Business Add-In (BAdI) to check if the BOPF action needs to be executed in the background
job API. The BAdI is inside of the job API, which controls the running of the action in the background or in the
front-end. The BAdI is triggered when you implement the action job API.
You make the relevant settings in Customizing for Transportation Management under
Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Background Job
Container Shipping
BAdI: Checking the Need to Run
BOBF Action in Job API .
To prepare the parameters for the BOBF job API, you can use the BAdI located in Customizing for
Transportation Management under
(BAdIs)
Background Job
Container Shipping Liners
Lead to Agreement
Business Add-Ins
BAdI: Preparation of Parameters for BOBF Action .
For more information about configuring these technical settings, see the Customizing documentation.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
PUBLIC
241
Related Information
Forwarding Agreement Quotations [page 181]
242
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Quotations
7
Forwarding Agreement Management
Forwarding agreements (FWAs) in the container shipping liners solution contain the exception information,
which is applied to rates in addition to the standard tariff.
The header-level information in FWA is taken from the forwarding agreement quotation (FWAQ) from which the
FWA was created or updated.
Each rate line in an FWA rate table contains the exception information and the standard tariff. If you want to
evaluate the complete charges for a rate line, the FWA must be considered in addition to the standard tariff that
is referenced in the leading charge type rate line.
 Note
In SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA,
forwarding agreements are intended to be created from FWAQs. You should avoid manually creating and
updating FWAs.
The field Agreement Category in the General Data section of the agreement will have the value of the Quotation
when they are created from lead to agreement (L2A) forwarding agreement quotations.
For Tariff Agreements, the Agreement Category will be Tariff. More details can be found in section Creating Tariff
Agreements in the system.
Related Information
Viewing Rates in Forwarding Agreements [page 243]
Forwarding Agreement Rate Revisions and Renewal [page 244]
7.1
Viewing Rates in Forwarding Agreements
The rates in a forwarding agreement (FWA) can be viewed in the Flat View.
Prerequisites
The FWA has been created from a forwarding agreement quotation (FWAQ).
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Management
PUBLIC
243
Procedure
1. In your SAP Fiori launchpad, open the Display Forwarding Agreement - CSL app.
2. Enter the agreement number and existing agreement version.
3. Choose the Display Flat View button in the FWA Header. All the rate lines along with the exception and
other details can be viewed from the Flat View.
4. You can also select the relevant item in the Items screen area, and then choose the Display Flat View
button.
Related Information
Forwarding Agreement Management [page 243]
7.2
Getting of Latest Rates for Agreement Rate Lines
You can get the latest rates of an agreement rate line via a Business Object Processing Framework (BOPF)
action (REFRESH_RATE, which is modeled on the anchor node of the business object for rates).
The consumer of this action can decide how to use the results of the action. The results of this action are not
persisted in the forwarding agreement.
You can use a Business Add-In (BAdI) to control the charges that are required to be calculated (resolve
the calculation sheet by deleting the irrelevant charges). You make the relevant settings in Customizing
for Transportation Management under
(BAdIs)
Charge Determination
Container Shipping Liners
Lead to Agreement
Business Add-Ins
BAdI: Resolution of Charges .
Related Information
Forwarding Agreement Management [page 243]
7.3
Forwarding Agreement Rate Revisions and Renewal
Rates in forwarding agreements (FWAs) can be adjusted by converting the FWA to a forwarding agreement
quotation (FWAQ).
You can create new FWAQs from existing rates in an FWA by creating a new FWAQ from the FWA header, or
from individual rate lines in the Flat View of the FWA. After you have amended the rates in the FWAQ, you can
merge it back into the same FWA.
244
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Management
In order to renew the existing FWA and change the header data, you can create a quotation from the FWA
header, which also results in the creation of a new version of the FWA. After the required changes are done in
the renewal FWAQ, it can be merged into the new version of the agreement.
 Note
You can only create an FWAQ from an FWA that was originally created from an FWAQ.
You can specify how the header FWAQ fields are copied from the source FWA to the new FWAQ
by implementing the Business Add-In (BAdI) in Customizing for Transportation Management under
Container Shipping Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Master Data
Agreements
BAdI: Creation of FWAQ Root .
Related Information
Renewing Forwarding Agreements [page 245]
Revising Forwarding Agreements [page 247]
Forwarding Agreement Management [page 243]
7.3.1 Renewing Forwarding Agreements
You can extend an already released agreement by creating a new quotation with revised dates. This also results
in the creation of a subsequent In Process version of the agreement with only the header data. Once the
changes are made to the new quotation, these changes are merged into the new version of the agreement as
part of the Agreement Create/Update action. The previous version of the agreement is truncated so that there
are no overlapping versions for the same agreement.
Prerequisites
The forwarding agreement (FWA) has been created from a forwarding agreement quotation (FWAQ).
Procedure
1. In your SAP Fiori, open the Display Forwarding Agreement app.
2. Enter the agreement number and existing agreement version.
3. Choose Create Quotation.
4. In the dialog box that opens, choose the option Renewal.
5. The Valid From date will be defaulted to the system date plus 1 day. This can be changed to a different date
if required. Enter a date for Valid To.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Management
PUBLIC
245
 Note
Upon changing the validity date, you can choose the Adjust Dates button in the forwarding agreement
quotation to update the dates in the item and the associated rate tables.
6. You can select one FWAQ Template so that FWAQ items missing in agreement are added from the template
to the renewal quotation.
7. The Copy Responses checkbox is selected by default. This option copies all the rate lines in the FWA into
the new renewal quotation. If you deselect this option, then only the header data from the FWA is copied
into the renewal quotation.
8. Select the required options for refreshing the rates.
The three options Recalculate Marine Leading Charge Tariff Rates, Recalculate ‘Subject To’ Marine
Surcharge Rates, and Update Marine Leading Charge Sales Proposed Rates are used to get the latest tariff
rates in the renewal quotation document. These options are applicable for response lines that are part of
the container shipping liners (CSL) item type Marine. You can use these options to refresh the rates for the
leading marine charge and the marine surcharges as follows:
•
Recalculate Marine Leading Charge Tariff Rates: If you select this checkbox, the system gets the latest
tariff rates for the marine leading charge and updates the base rate/amount fields in the revenue of the
response lines.
•
Recalculate ‘Subject To’ Marine Surcharge Rates: If you select this checkbox, the system gets the latest
tariff rates for the marine surcharges with the surcharge condition Subject To and updates the base
rate/amount and the sales proposed rate/amount in the revenue of the response lines.
•
Update Marine Leading Charge Sales Proposed Rates: If you select this checkbox, the system gets the
latest tariff rates for the marine leading charge and updates the sales proposed rate/amount fields in
the revenue of the response lines.
9. Choose OK.
The system creates a new quotation in the foreground or the background mode based on the settings
defined in Customizing for Transportation Management under
Agreement
Container Shipping Liners
Forwarding Agreement Quotation and Forwarding Agreement
Lead to
Technical Settings
Maintain
Settings for Background Job Activities . A new agreement version is also created with only header data
from the current version of the agreement.
10. Revise the data in the newly created FWAQ.
11. Save your entries.
Next Steps
Once you have changed the data, you can merge the FWAQ into the new version of the same FWA. After the
merge, the previous version of the agreement will be truncated so that there are no overlaps between both the
versions of the forwarding agreement.
To retain tariff line items (TLIs) during renewal, you must implement the application programming interface
(API) /TMCSL/CL_TCRATES_UTILITY_B_V2=>UPDATE_RATE_TYPED_RETAIN_FLAG in charge calculation
for the booking. As a result, the field Rate Retaining Flag is set as active. In addition, the following values are set:
•
246
Agreement TLI Rate Line Status is set as Not Available for Rating.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Management
•
Valid-From Date and Valid-To Date are set as the date in the header Valid-To date, and the time is set as
23:59:59.
Related Information
Forwarding Agreement Rate Revisions and Renewal [page 244]
Conversion of FWAQs to Forwarding Agreements [page 237]
Forwarding Agreement Management [page 243]
7.3.2 Revising Forwarding Agreements
Create a new forwarding agreement quotation (FWAQ) from the header of the forwarding agreement (FWA)
in case all the rate lines have to be revised. If only certain rate lines have to be revised, you can go to the flat
view in the agreement, select the rate lines and choose the action Response Additional-Revision. You can then
amend the rates in the FWAQ before merging back the FWAQ back into the same FWA.
Prerequisites
The FWA has been created from an FWAQ.
Procedure
1. In your SAP Fiori launchpad, open the Display Forwarding Agreement app.
2. Enter the agreement number and existing agreement version.
3. Choose the Create Quotation action in the FWA Header. This button is enabled only when the following
conditions are satisfied:
•
•
•
The agreement is in Released status
The Agreement Validity End Date is not in the past.
There is no revision process currently in progress.
4. In the dialog box that appears, select the option Revision.
5. Select an FWAQ template, using which the system will create the missing items in the Revision quotation,
as compared to the existing items in the forwarding agreement.
6. Select the required options for refreshing the rates.
The three options Recalculate Marine Leading Charge Tariff Rates, Recalculate ‘Subject To’ Marine
Surcharge Rates, and Update Marine Leading Charge Sales Proposed Rates are used to get the latest tariff
rates in the renewal quotation document. These options are applicable for response lines that are part of
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Management
PUBLIC
247
the container shipping liners (CSL) item type Marine. You can use these options to refresh the rates for the
leading marine charge and the marine surcharges as follows:
•
Recalculate Marine Leading Charge Tariff Rates: If you select this checkbox, the system gets the latest
tariff rates for the marine leading charge and updates the base rate/amount fields in the revenue of the
response lines.
•
Recalculate ‘Subject To’ Marine Surcharge Rates: If you select this checkbox, the system gets the latest
tariff rates for the marine surcharges with the surcharge condition Subject To and updates the base
rate/amount and the sales proposed rate/amount in the revenue of the response lines.
•
Update Marine Leading Charge Sales Proposed Rates: If you select this checkbox, the system gets the
latest tariff rates for the marine leading charge and updates the sales proposed rate/amount fields in
the revenue of the response lines.
7. Choose OK.
The system creates a new revision quotation in the foreground or background mode depending on the
settings defined in Customizing for Transportation Management under
Lead to Agreement
Container Shipping Liners
Forwarding Agreement Quotation and Forwarding Agreement
Technical Settings
Maintain Settings for Background Job Activities .
8. The new created FWAQ has all the rate lines inserted as response lines from the FWA. In case, you wish to
revise only a few rate lines in the forwarding agreement, select these rate lines in the Flat View and choose
Response Additional - Revision.
As a result, a revision quotation is created only with the selected rate lines.
9. Save your entries.
Next Steps
Once you have revised the rates, merge the FWAQ back into the same FWA.
Related Information
Forwarding Agreement Rate Revisions and Renewal [page 244]
Conversion of FWAQs to Forwarding Agreements [page 237]
Forwarding Agreement Management [page 243]
248
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Forwarding Agreement Management
8
L2A SAP Fiori Apps
SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA provides
various SAP Fiori apps that you can use to manage your agreements and quotations.
There are list report apps that enable you to manage your agreements and quotations in the list report format,
and there is an analytical app that shows the overview of the pending response quotations and the pending
renewal agreements.
List Report Apps
With a list report, you can view and work with a large set of items. You can find and act on relevant items within
a large set of items by searching, filtering, sorting, and grouping:
•
•
•
•
Manage L2A Quotations – CSL
Manage L2A Agreements – CSL
Monitor Upcoming Quotation Response Deadline – CSL
Monitor Upcoming Agreement Renewal – CSL
L2A Analytical App
The L2A Analysis – CSL app enables you to see all the vital data you need for your daily decision-making. This
app provides an analytical view of the following L2A overview information:
•
•
Pending Response Quotations
Pending Renewal Agreements
From the overview page, you can drill down to access more details by navigating from the L2A Analysis – CSL
app to the relevant L2A list report app.
Related Information
Manage L2A Quotations – CSL [page 250]
Manage L2A Agreements – CSL [page 251]
Monitor Upcoming Quotation Response Deadline – CSL [page 252]
Monitor Upcoming Agreement Renewal – CSL [page 253]
L2A Analysis - CSL [page 254]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
L2A SAP Fiori Apps
PUBLIC
249
8.1
Manage L2A Quotations – CSL
This SAP Fiori app enables you to find quotations for the given search criteria.
Key Features
The Manage L2A Quotations - CSL app includes the following features:
•
Flexible Data Selection
In the search criteria panel, you can search for the required service items by entering different search
criteria.
•
Free-Style Search
Fuzzy search is supported to query the required service items.
•
Variant Management for Personalization of the Search Criteria Panel
In the search criteria panel, you can personalize the selection criteria and save default values for them in a
variant. You can create the variant as a public view so that it can be shared with other users.
You can save the currently selected variant as a tile on the SAP Fiori launchpad using the Save as Tile
action in the Share menu.
•
Personalization of the List Report Area
You can personalize the appearance of the list with the following options:
•
•
Display or hide a column
Modify the column sequence
•
Navigation to Related Documents
You can navigate to the related booking document or cargo unit document or service order using the
relevant hyperlink in the list report.
•
Flexible Data Display
Certain columns are visible in the table by default. You can use the Show/Hide Details toggle button to
show or hide the more detailed fields for the trip plan document.
Supported Device Types
•
•
•
Desktop
Tablet
Smartphone
Technical Basis
Fiori ID: F6154
You must activate the OData service UI_TRANSPORTAGREEMENT in the Gateway system.
250
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
L2A SAP Fiori Apps
8.2
Manage L2A Agreements – CSL
This SAP Fiori app enables you to find agreements for the given search criteria.
Key Features
The Manage L2A Agreements - CSL app includes the following features:
•
Flexible Data Selection
In the search criteria panel, you can search for the required service items by entering different search
criteria.
•
Free-Style Search
Fuzzy search is supported to query the required service items.
•
Variant Management for Personalization of the Search Criteria Panel
In the search criteria panel, you can personalize the selection criteria and save default values for them in a
variant. You can create the variant as a public view so that it can be shared with other users.
You can save the currently selected variant as a tile on the SAP Fiori launchpad using the Save as Tile
action in the Share menu.
•
Personalization of the List Report Area
You can personalize the appearance of the list with the following options:
•
•
Display or hide a column
Modify the column sequence
•
Navigation to Related Documents
You can navigate to the related booking document or cargo unit document or service order using the
relevant hyperlink in the list report.
•
Flexible Data Display
Certain columns are visible in the table by default. You can use the Show/Hide Details toggle button to
show or hide the more detailed fields for the trip plan document.
Supported Device Types
•
•
•
Desktop
Tablet
Smartphone
Technical Basis
Fiori ID: F6146
You must activate the OData service UI_TRANSPORTAGREEMENT in the Gateway system.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
L2A SAP Fiori Apps
PUBLIC
251
8.3
Monitor Upcoming Quotation Response Deadline – CSL
This SAP Fiori app enables you to monitor quotations whose response deadline is in the next 15 days.
Key Features
The Monitor Upcoming Quotation Response Deadline- CSL app includes the following features:
•
Flexible Data Selection
In the search criteria panel, you can search for the required service items by entering different search
criteria.
•
Free-Style Search
Fuzzy search is supported to query the required service items.
•
Variant Management for Personalization of the Search Criteria Panel
In the search criteria panel, you can personalize the selection criteria and save default values for them in a
variant. You can create the variant as a public view so that it can be shared with other users.
You can save the currently selected variant as a tile on the SAP Fiori launchpad using the Save as Tile
action in the Share menu.
•
Personalization of the List Report Area
You can personalize the appearance of the list with the following options:
•
•
Display or hide a column
Modify the column sequence
•
Navigation to Related Documents
You can navigate to the related booking document or cargo unit document or service order using the
relevant hyperlink in the list report.
•
Flexible Data Display
Certain columns are visible in the table by default. You can use the Show/Hide Details toggle button to
show or hide the more detailed fields for the trip plan document.
Supported Device Types
•
•
•
Desktop
Tablet
Smartphone
Technical Basis
Fiori ID: F6154
You must activate the OData service UI_TRANSPORTAGREEMENT in the Gateway system.
252
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
L2A SAP Fiori Apps
Related Information
Manage L2A Quotations – CSL [page 250]
8.4
Monitor Upcoming Agreement Renewal – CSL
This SAP Fiori app enables you to monitor agreements whose validity end date is in the next 15 days.
Key Features
The Monitor Upcoming Agreement Renewal - CSL app includes the following features:
•
Flexible Data Selection
In the search criteria panel, you can search for the required service items by entering different search
criteria.
•
Free-Style Search
Fuzzy search is supported to query the required service items.
•
Variant Management for Personalization of the Search Criteria Panel
In the search criteria panel, you can personalize the selection criteria and save default values for them in a
variant. You can create the variant as a public view so that it can be shared with other users.
You can save the currently selected variant as a tile on the SAP Fiori launchpad using the Save as Tile
action in the Share menu.
•
Personalization of the List Report Area
You can personalize the appearance of the list with the following options:
•
•
Display or hide a column
Modify the column sequence
•
Navigation to Related Documents
You can navigate to the related booking document or cargo unit document or service order using the
relevant hyperlink in the list report.
•
Flexible Data Display
Certain columns are visible in the table by default. You can use the Show/Hide Details toggle button to
show or hide the more detailed fields for the trip plan document.
Supported Device Types
•
•
•
Desktop
Tablet
Smartphone
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
L2A SAP Fiori Apps
PUBLIC
253
Technical Basis
Fiori ID: F6146
You must activate the OData service UI_TRANSPORTAGREEMENT in the Gateway system.
Related Information
Manage L2A Agreements – CSL [page 251]
8.5
L2A Analysis - CSL
This SAP Fiori app provides an overview of the pending response quotations and the pending renewal
agreements for the given search criteria.
Key Features
The L2A Analysis - CSL app includes the following features:
•
Flexible Data Selection
In the search criteria panel, you can search for the required service items by entering different search
criteria.
•
Free-Style Search
Fuzzy search is supported to query the required service items.
•
Variant Management for Personalization of the Search Criteria Panel
In the search criteria panel, you can personalize the selection criteria and save default values for them in a
variant. You can create the variant as a public view so that it can be shared with other users.
You can save the currently selected variant as a tile on the SAP Fiori launchpad using the Save as Tile
action in the Share menu.
•
Personalization of the List Report Area
You can personalize the appearance of the list with the following options:
•
•
Display or hide a column
Modify the column sequence
•
Navigation to Related Documents
You can navigate to the related booking document or cargo unit document or service order using the
relevant hyperlink in the list report.
•
Flexible Data Display
Certain columns are visible in the table by default. You can use the Show/Hide Details toggle button to
show or hide the more detailed fields for the trip plan document.
254
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
L2A SAP Fiori Apps
Supported Device Types
•
•
•
Desktop
Tablet
Smartphone
Technical Basis
Fiori ID: F6148
You must activate the OData service UI_TRANSPORTAGREEMENT in the Gateway system.
Related Information
Manage L2A Quotations – CSL [page 250]
Manage L2A Agreements – CSL [page 251]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
L2A SAP Fiori Apps
PUBLIC
255
9
Enhancements to Charge Calculation
The application provides several ennhancements to the standard charge calculation process for forwarding
agreement quotations (FWAQs) and bookings.
Related Information
Charge Automation [page 256]
Other Size Per Formula [page 269]
Equipment Substitution [page 273]
9.1
Charge Automation
During the charge calculation process in forwarding agreement quotations (FWAQs) and bookings, the system
uses the charge automation rules to calculate a rate when no specific rate has been defined for the requested
equipment size and type.
These charge automation rules are defined on the OSPF/Charge Automation tab of a quotation or agreement.
You can also maintain templates for charge automation in Customizing for Transportation Management
under
Container Shipping Liners
Automation
Lead to Agreement
Basic Settings
Pricing
OSPF and Surcharge
Define Surcharge Automation Templates .
When you trigger the charge calculation process in an FWAQ or a booking, the system looks for tariff rates for
the requested equipment. If a rate cannot be found, the system searches for the rate for the charge automation
equipment. If a rate is found, the corresponding surcharge is applied as per the rules.
There are two types of charge automation rules, as follows:
•
Maritime
The maritime rate is the transportation price for the main stage, and the transportation mode is sea.
The maritime charge automation rules are configured for the leg type MAR of an automation type in
Customizing for Transportation Management under
Container Shipping Liners
Lead to Agreement
Basic Settings Pricing OSPF and Surcharge Automation Define Surcharge Automation Templates .
A maritime charge automation rule needs to be configured for each of the following charge automation
types, which are delivered as standard as part of the application:
•
•
•
•
•
256
Open Top
Flat Rack
Tank
Reefer
High Cube
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
•
•
•
•
Shipper-Owned Container (SOC)
Hazardous Goods
Out of Gauge (OOG)
Inland
The inland rate is the transportation price for the inland stage, which can be from the origin to the port, or
from the port to the destination.
The inland charge automation rules are configured for the leg types INLO and INLD of the automation type
in Customizing for Transportation Management under
Container Shipping Liners
Lead to Agreement
Basic Settings Pricing OSPF and Surcharge Automation Define Surcharge Automation Templates .
An inland charge automation rule needs to be configured for each of the following charge automation
types, which are delivered as standard as part of the application:
•
•
•
•
•
•
Open Top
Flat Rack
Tank
Reefer
High Cube
Hazardous Goods
 Note
SOC and OOG are not applicable for inland charge automation.
To use the configured charge automation rules, you need to assign the maritime charge automation rules to a
forwarding agreement tariff.
 Note
Roll-on roll-off (RORO) is not applicable for maritime or inland charge automation.
Related Information
Assigning Maritime Charge Automation Rules to Tariffs [page 258]
Assigning Inland Charge Automation Rules to Tariffs [page 261]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
257
9.1.1 Assigning Maritime Charge Automation Rules to Tariffs
Assign the maritime charge automation rules in a marine tariff.
Prerequisites
The charge automation rules have been configured for the leg type MAR in Customizing for Transportation
Management under
Container Shipping Liners
Surcharge Automation
Lead to Agreement
Basic Settings
Pricing
OSPF and
Define Surcharge Automation Templates .
Context
The maritime charge automation rule is dependent on the pricing trade and always applies for the maritime
rate. You maintain the formula for the charge automation rule in the forwarding agreement quotation (FWAQ)
and forwarding agreement (tariff) in the header level of the document. The charge automation rules are
maintained for a trade lane and a leg type combination.
You can assign maritime charge automation rules to tariffs in the following ways:
•
•
Manually add the charge automation rules
Select an automation template
You can select an automation template that has been configured in Customizing for Transportation
Management under
Container Shipping Liners
and Surcharge Automation
•
Lead to Agreement
Define Surcharge Automation Templates
Basic Settings
Pricing
OSPF
on the Automation template node.
Configure a rule to automatically determine the template
You can use a rule to automatically determine the template. The rule is configured in Customizing for
Transportation Management under
Container Shipping Liners
Pricing OSPF and Surcharge Automation
determine node.
Lead to Agreement
Define Surcharge Automation Templates
Basic Settings
on the Template
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement - CSL app, and open the relevant
forwarding agreement tariff.
2. Go to the OSPF/Charge Automation tab.
3. Choose Insert to insert the Trade Lane and Leg Type.
4. Enter the Trade Lane and Leg Type combination.
5. Assign the maritime charge automation rules in one of the following ways:
•
258
Manually add the charge automation rules as follows:
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
1. Go to the Charge Automation subtab.
2. Add your entries.
3. Save your entries
•
Add the charge automation rules from a template as follows:
1. Choose
Set Automation Template
Select Automation Template .
2. Select the template and then choose OK.
The charge automation rules specified in the template are added on the Charge Automation
subtab.
3. Save your entries.
•
Add the charge automation rules using a template determination rule as follows:
1. Choose Set Automation Template Determine Automation Template .
The template is determined automatically, and the charge automation rules configured for that
template are added on the Charge Automation subtab.
2. Save your entries.
Related Information
Charge Automation [page 256]
Equipment-Relevant Charge Automation for Maritime Stages [page 259]
Non-Equipment-Relevant Charge Automation for Maritime Stages [page 260]
9.1.1.1
Equipment-Relevant Charge Automation for
Maritime Stages
The maritime charge automation rules for special equipment types such as flat racks and reefers are
configured in Customizing. The system uses these rules to calculate the rate for special equipment types
when no specific rate has been defined.
The charge automation rules are configured for the leg type MAR as special equipment automation types in
Customizing for Transportation Management under
Settings
Pricing
OSPF and Surcharge Automation
Container Shipping Liners
Lead to Agreement
Basic
Define Surcharge Automation Templates .
A rule needs to be configured for each of the following equipment-relevant charge automation types:
•
•
•
•
•
Open Top
Flat Rack
Tank
Reefer
High Cube
Each rule is configured by defining a reference equipment type and a surcharge.
When a customer books a special equipment type (such as a flat rack or a reefer), the special equipment type
is entered at the booking item level as the normal equipment type. When you trigger the charge calculation for
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
259
the booking, the system first tries to find the rate quoted for the special equipment type. If no rate is found, the
system applies the charge automation rules.
 Note
In addition, the tariff type must be entered for the leg type. This is mandatory, as this setting is used in tariff
determination.
 Example
There is a booking request is for the equipment type 20OT (a 20' open top container). However, there is
no rate for 20OT. Using the charge automation rules, the system determines that the reference equipment
type for 20OT is 20ST (a 20' standard container), and a surcharge is applicable (the open top surcharge
AUTO_OT). Therefore, to calculate the rate for 20OT, the system finds the rate for 20ST and adds the open
top surcharge AUTO_OT.
Related Information
Charge Automation [page 256]
Assigning Maritime Charge Automation Rules to Tariffs [page 258]
Non-Equipment-Relevant Charge Automation for Maritime Stages [page 260]
9.1.1.2
Non-Equipment-Relevant Charge Automation for
Maritime Stages
The maritime charge automation rules for special cargos and shipper-owned containers (SOCs) are configured
in Customizing. The system uses these rules to calculate the rate for special cargos and SOCs when no specific
rate has been defined.
A customer might want to ship special cargos such as hazardous goods or out of gauge (OOG) cargos, or ship
cargo using an SOC. These details are entered in the booking item or the request in the forwarding agreement
quotation (FWAQ).
The charge automation rules are configured for the leg type MAR for special cargos and SOCs as automation
types in Customizing for Transportation Management under
Basic Settings
Pricing
OSPF and Surcharge Automation
Container Shipping Liners
Lead to Agreement
Define Surcharge Automation Templates .
A rule needs to be configured for each of the following charge automation types:
•
•
•
SOC
Hazardous
OOG
Each rule is configured by defining a surcharge. It is not necessary to configure a reference equipment type for
non-equipment-relevant charge automation types.
260
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
 Note
In addition, the tariff type must be entered for the leg type. This is mandatory, as this setting is used in tariff
determination.
When you trigger the charge calculation for the booking, the system first tries to find the rate for the special
cargo type. If no rate is found, the system applies the relevant surcharge defined in the charge automation
rules. For example, in the case of hazardous cargo, the system first searches for the rate for hazardous cargo.
If no rate is found, the system applies the charge automation rule to find a rate for non-hazardous cargo, and
then adds the relevant surcharge for hazardous cargo.
Related Information
Charge Automation [page 256]
Assigning Maritime Charge Automation Rules to Tariffs [page 258]
Equipment-Relevant Charge Automation for Maritime Stages [page 259]
9.1.2 Assigning Inland Charge Automation Rules to Tariffs
Assign the inland charge automation rules to a tariff.
Prerequisites
The charge automation rules have been configured for the leg types INLO and INLD in Customizing for
Transportation Management under
Pricing
Container Shipping Liners
OSPF and Surcharge Automation
Lead to Agreement
Basic Settings
Define Surcharge Automation Templates .
Context
Inland charge automation rules are maintained in the inland tariff (that is, the tariff specifically created for the
tariff types 04 Origin Inland and 05 Destination Inland).
You enter the formula for the charge automation rule in the forwarding agreement quotation (FWAQ) and
forwarding agreement (tariff) in the header level of the document. The charge automation rules are entered for
a trade lane and leg type combination. Note that for inland legs, the trade lane is not applicable, and you can
therefore enter the wildcard (*) if you do not know the trade lane.
You can assign the inland charge automation rules to the tariff in the following ways:
•
Manually add the charge automation rules
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
261
•
Select an automation template
You can select an automation template that has been configured in Customizing for Transportation
Management under
Container Shipping Liners
and Surcharge Automation
•
Lead to Agreement
Define Surcharge Automation Templates
Basic Settings
Pricing
OSPF
on the Automation template node.
Configure a rule to automatically determine the template
You can use a rule to automatically determine the template. The rule is configured in Customizing for
Transportation Management under
Container Shipping Liners
Pricing OSPF and Surcharge Automation
determine node.
Lead to Agreement
Define Surcharge Automation Templates
Basic Settings
on the Template
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement - CSL app, and open the relevant
forwarding agreement tariff.
2. Go to the OSPF/Charge Automation tab.
3. Choose Insert to insert the Trade Lane and Leg Type.
4. Enter the Trade Lane and Leg Type combination.
5. Assign the inland charge automation rules in one of the following ways:
•
Manually add the charge automation rules as follows:
1. Go to the Charge Automation subtab.
2. Add your entries.
3. Save your entries
•
Add the charge automation rules from a template as follows:
1. Choose
Set Automation Template
Select Automation Template .
2. Select the template and then choose OK.
The charge automation rules specified in the template are added on the Charge Automation
subtab.
3. Save your entries.
•
Add the charge automation rules using a template determination rule as follows:
1. Choose Set Automation Template Determine Automation Template .
The template is determined automatically, and the charge automation rules configured for that
template are added on the Charge Automation subtab.
2. Save your entries.
Related Information
Equipment-Relevant Charge Automation for Inland Stages [page 263]
Charge Automation for Hazardous Goods Inland [page 264]
262
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
9.1.2.1
Equipment-Relevant Charge Automation for Inland
Stages
The inland charge automation rules for special equipment types such as flat racks and reefers are configured in
Customizing. The system uses these rules to calculate the rate for the special equipment type when a specific
rate has not been defined.
The charge automation rules for special equipment for inland stages (leg types INLO and INLD) are configured
as automation types in Customizing for Transportation Management under
Container Shipping Liners
to Agreement
Define Surcharge Automation
Basic Settings
Pricing
OSPF and Surcharge Automation
Lead
Templates .
A rule needs to be configured for each of the following equipment-relevant charge automation types:
•
•
•
•
•
Open Top
Flat Rack
Tank
Reefer
High Cube
Each rule is configured by defining a reference equipment type and a surcharge.
 Note
In addition, the tariff type must be entered for the leg type. This is mandatory, as this setting is used in tariff
determination.
If a customer books a special equipment type such as a flat rack or a reefer, the special equipment type is
entered in the booking item. When you trigger the charge calculation for the booking, the system first tries
to find the rate quoted for the special equipment type. If no rate is found, the system applies the charge
automation rule for the special equipment type.
 Example
There is a booking request is for the equipment type 20OT (a 20' open top container). However, there is no
rate for 20OT. The system determines that the reference equipment type for 20OT is 20ST (a 20' standard
container), and a surcharge is applicable. Therefore, determine the applicable rate for 20OT, the system
finds the inland rate for 20ST and adds the open top surcharge.
Related Information
Assigning Inland Charge Automation Rules to Tariffs [page 261]
Charge Automation for Hazardous Goods Inland [page 264]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
263
9.1.2.2
Charge Automation for Hazardous Goods Inland
The inland charge automation rules for hazardous cargos are configured in Customizing. The system uses
these rules to calculate the rate for hazardous cargos when no specific rate has been defined.
If a customer wants to ship special cargos such as hazardous goods, the details are entered in the booking
item or the request in the forwarding agreement quotation (FWAQ). The charge automation rules for special
cargos and hazardous goods for inland (leg types INLO and INLD) are configured as automation types in
Customizing for Transportation Management under
Settings
Pricing
OSPF and Surcharge Automation
Container Shipping Liners
Lead to Agreement
Basic
Define Surcharge Automation Templates .
A rule needs to be configured for the charge automation type for hazardous goods.
 Note
In addition, the tariff type must be entered for the leg type. This is mandatory, as this setting is used in tariff
determination.
Each rule is configured by defining a surcharge. It is not necessary to configure a reference equipment type for
non-equipment-relevant charge automation types.
When you trigger the charge calculation for the booking, the system first tries to find the rate for the special
cargo type. If no rate is found, the system applies the relevant surcharge defined in the charge automation
rules. For example, in the case of hazardous cargo, the system first searches for the rate for hazardous cargo.
If no rate is found, the system applies the charge automation rule to find a rate for non-hazardous cargo, and
then adds the relevant surcharge for hazardous cargo.
Related Information
Assigning Inland Charge Automation Rules to Tariffs [page 261]
Equipment-Relevant Charge Automation for Inland Stages [page 263]
9.1.3 Charge Automation in Quotations and Bookings
When you calculate charges in forwarding agreement quotations (FWAQs) and bookings, the system uses the
charge automation rules to calculate the rate when no direct rate is found. This can involve calculating and
combining separate rates for maritime and inland stages.
In the charge calculation process for FWAQs and bookings, the system uses the charge automation rules
for inland legs when a matching rate is not found for inland segments (origin or destination). The charge
automation calculation for the origin inland stage and the destination inland stage are independent.
First, the system checks the specified rate for the inland legs. If a matching rate is not found, the system
checks the charge automation rule specified in the inland rate table. The system determines the rate from a
base rate plus a corresponding surcharge (such as an open top surcharge).
264
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
 Example
There is an FWAQ request for the equipment size and type 20OT (a 20' open top container). There is
no direct OCF rate for 20OT, so the system uses the charge automation rules and determines that the
appropriate base rate is OCF tariff 20ST (a 20' standard container), which is $400. No surcharge is
maintained for open top, therefore, the rate for OCF is $400. Automation surcharge AUTO_OT is applied.
It is possible to combine charge automation rules. For ocean freight, it is possible to combine charge
automation rules for equipment type (open top, flat rack, reefer, tank, or high cube), shipper-owned container
(SOC), and hazardous cargo. For inland, it is possible to combine charge automation rules for equipment type
and hazardous cargo.
 Example
The FWAQ or booking request is for the equipment size and type 20OT (a 20' open top container), using an
SOC containing hazardous cargo (HAZ).
Using the maritime charge automation rules, the system determines that the OCF tariff for 20ST (a 20'
standard container) using an SOC containing non-hazardous cargo is applicable, which is $400. Therefore,
the rate for OCF is calculated as follows:
$400 + open top surcharge + HAZ surcharge
For the inland stage, the system determines that the inland tariff for 20ST containing non-hazardous cargo
is applicable, which is $400. Therefore, the rate for inland is calculated as follows:
$400 + open top surcharge + HAZ surcharge
The priority of charge automation follows the order of the charge automation rules.
Related Information
Charge Automation for Inland Stages [page 265]
Using Charge Automation in Quotations [page 266]
Using Charge Automation in Bookings [page 268]
9.1.3.1
Charge Automation for Inland Stages
When an inland rate is required to complete the charge calculation in a forwarding agreement quotation
(FWAQ) or a booking, the system calculates a rate using the charge automation rules when no specific rate
exists.
The system determines the appropriate rate for inland stages as follows:
1. The system checks if there is a rate for the specific equipment size and type, and if a rate is found, it is
used.
2. If there is no rate for the specific equipment size and type, then the system checks if a rate is available
using the charge automation rule. If a suitable rate can be determined for inland plus a surcharge (such as
open top, flat rack, tank, reefer, or high cube), then the system uses it.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
265
3. If no valid rate is found using the charge automation rule (inland plus a surcharge not found), then the
system moves to the next step of rate calculation.
If none of the above steps succeed in finding a rate for inland (including the charge automation steps), then the
charge calculation fails to find an ocean carrier freight (OCF) rate and an inland (INL) rate.
The charge automation rules for ocean freight and inland are evaluated separately. Therefore, the system could
apply the charge automation rules for the inland stage, and apply a specific matching rate for the ocean freight
stage (and verse versa).
If a surcharge is not found during the charge automation evaluation, then the default rate defined in the charge
automation rules is applied.
The reference equipment type is not used to evaluate inland surcharges (including adjustment factors) or
ocean freight surcharges. It is only used to find the ocean freight and inland base rate.
 Note
There is a difference between the charge automation process for quotations and the charge automation
process for bookings. In quotations, if no rate is found for the inland surcharge in the inland charge
automation process, the OCF rate is retained. While in bookings, the OCF rate is blank when no rate is
found for the inland surcharge.
Related Information
Charge Automation in Quotations and Bookings [page 264]
Using Charge Automation in Quotations [page 266]
Using Charge Automation in Bookings [page 268]
9.1.3.2
Using Charge Automation in Quotations
Generate the charges for the selected route in a forwarding agreement quotation (FWAQ).
Prerequisites
•
The forwarding agreement tariffs for marine charges and inland charges have been created in the Create
Forwarding Agreement - CSL app and the tariffs are assigned to the respective tariff types in the tariff
maintenance app.
•
The calculation bases have been defined in Customizing for Transportation Management under
Functions
•
Charge Calculation
Data Source Binding
Define Calculation Bases .
The maritime and inland charge automation rules have been defined in the tariff as well as in Customizing
for Transportation Management under
Pricing
266
Basic
PUBLIC
Container Shipping Liners
OSPF and Surcharge Automation
Lead to Agreement
Basic Settings
Define Surcharge Automation Templates .
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
Procedure
1. In your SAP Fiori launchpad, open the Create Forwarding Agreement Quotation - CSL app.
2. On the initial screen, specify the quotation type, and optionally specify an existing quotation or a quotation
template as a reference.
3. Choose Continue.
4. On the General Data tab, enter the following mandatory details:
•
•
•
•
•
•
FWAQ Valid From
FWAQ Valid To
Agreement Valid From
Agreement Valid To
Ordering Party
Sales Organization
5. On the Items tab, choose
Insert
Item , and then enter the FWAQ item details.
6. On the Items tab, choose
Calculation Sheet
Create Calculation Sheet .
7. On the Calculation Sheet Overview tab on item level, enter the ocean carrier freight (OCF) rate table for the
request, including the following details:
•
•
•
•
•
Source Transportation Zone
Destination Transportation Zone
Delivery Mode
Receipt Mode
Equipment Type
8. In the header toolbar, choose Display Flat View.
9. Choose Apply to display the request lines.
10. Select the request line and choose Search Routes to find the preferred routing.
11. Select the required route.
A response line is generated.
12. Select the response line and choose the Revenue tab.
The system fetches the rates from the tariff.
Related Information
Charge Automation in Quotations and Bookings [page 264]
Charge Automation for Inland Stages [page 265]
Using Charge Automation in Bookings [page 268]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
267
9.1.3.3
Using Charge Automation in Bookings
Calculate the charges for a booking and then view the rates and charge automation rules that have been
applied.
Prerequisites
•
The forwarding agreement tariffs for marine charges and inland charges have been created in the Create
Forwarding Agreement - CSL app and the tariffs are assigned to the respective tariff types in the tariff
maintenance app.
•
The calculation bases have been defined in Customizing for Transportation Management under
Functions
•
Charge Calculation
Data Source Binding
Basic
Define Calculation Bases .
The maritime and inland charge automation rules have been defined in the tariff as well as in Customizing
for Transportation Management under
Pricing
Container Shipping Liners
OSPF and Surcharge Automation
Lead to Agreement
Basic Settings
Define Surcharge Automation Templates .
Procedure
1. In your SAP Fiori launchpad, open the Create Booking - CSL app.
2. On the initial screen, specify the booking type, and optionally specify an existing booking or a booking
template as a reference.
3. Choose Continue.
4. On the General Data tab, enter the following mandatory fields:
•
•
•
•
•
•
•
Booking Party
Source Location
Departure After Date
Destination Location
Sales Organization, Sales Office, and Sales Group
Booking item details
Requested port of loading (POL) and port of discharge (POD)
5. On the toolbar, choose Calculate Charges.
The system fetches the rates from the tariff.
6. On the Charges tab, check the rate and the surcharge for the inland stage.
7. On the Charge Analysis Log subtab, view the messages for the charge automation rules that have been
successfully applied.
268
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
Related Information
Charge Automation in Quotations and Bookings [page 264]
Charge Automation for Inland Stages [page 265]
Using Charge Automation in Quotations [page 266]
9.2
Other Size Per Formula
Other size per formula (OSPF) is a size-based formula that you can use to calculate a rate when there is no
specific rate for the type of equipment.
Overview
Sometimes, the system cannot find a direct rate for a particular equipment type (not even for the reference
equipment type configured in Customizing). When a direct rate cannot be found, the system can try to find a
rate using the OSPF formula if you have maintained it in the tariff.
You can configure OSPF per leg type (for example,inland origin, ocean, and inland destination) and trade lane.
The OSPF formula for an equipment type can only refer to one reference equipment type (only one formula).
You can enter cyclic formulas such as follows:
•
•
20’ container = 80% of 40’ container
40’ container = 90% of 45’ container
However, if you do enter cyclic formulas, the system only evaluates the first formula when applying OSPF.
You can also maintain a rounding profile for OSPF. The system applies the rounding during the charge
calculation process. During the charge calculation process in a booking, the OSPF formula is applied if no
rate can be found for the equipment type specified in the booking.
Related Information
Entering the OSPF Formula in Forwarding Agreements [page 270]
OSPF Charge Automation Process [page 272]
Viewing the OSPF Rate Details in the Booking Screen [page 272]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
269
9.2.1 Entering the OSPF Formula in Forwarding Agreements
Enter the other size per formula (OSPF) details for a forwarding agreement (FWA) tariff on the OSPF/Charge
Automation tab.
Prerequisites
•
The agreement type has been defined in Customizing for Transportation Management under
Data
•
Agreement and Service Products
Master
Define Freight Agreement Types .
The agreement type has been identified as Tariff in Customizing for Transportation Management under
Container Shipping Liners
Lead to Agreement
Forwarding Agreement Quotation and Agreement
Maintain CSL Forwarding Agreement Types .
•
The OSPF templates have been configured in Customizing for Transportation Management under
Container Shipping Liners
Automation
•
Lead to Agreement
Basic Settings
Pricing
OSPF and Surcharge
Define OSPF Templates .
The rules for automatic OSPF template determination have been configured in Customizing for
Transportation Management under
Container Shipping Liners
Pricing OSPF and Surcharge Automation
rule node.
Lead to Agreement
Define OSPF Templates
Basic Settings
on the OSPF template determine
Context
You can enter the OSPF details in the following ways:
•
•
•
Manually
By selecting a template
By determining the template automatically based on configured rules
 Note
You can also follow the steps below in a forwarding agreement quotation and the data you maintain on the
OSPF/Charge Automation tab can be moved to the forwarding agreement during the agreement creation/
update process. When a booking is created against this agreement, the data maintained in the agreement
are considered for the OSPF.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement - CSL app, and then open the relevant
tariff.
270
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
2. On the OSPF/Charge Automation tab, choose Insert and enter the Leg Type (Inland Origin, Marine, or Inland
Destination) and Trade Lane.
3. Select the relevant row and enter the OSPF details in one of the following ways:
•
Manually, as follows:
1. Go to the OSPF subtab.
2. Enter the rounding profile and the formula details as follows:
Read-Only
Field Name
Mandatory
Equipment Type
Yes
(After initial entry)
Description
Equipment type that is
originally requested in the
booking
Sign
Yes
Always equal (“=”)
Value
Yes
Percentage for the for­
mula
Currency/Percentage
Yes
Always percentage (“%”)
Reference Equipment
Yes
Type
Reference equipment
size/type (the rate for
this equipment type is the
basis of the formula)
Rounding Profile
Strategy for rounding the
result
3. Save your entries.
•
By selecting a template, as follows:
1. Choose
Set OSPF Template
Select OSPF Template .
2. Select a template and choose OK.
The OSPF details from the template are added on the OSPF subtab.
3. Save your entries.
•
By determining a template automatically, as follows:
1. Choose Set OSPF Template Determine OSPF Template .
The template is determined automatically and the OSPF details from the template are added on
the OSPF subtab.
2. Save your entries.
Results
When the tariff is released, the OSPF formula is used to calculate a rate if no direct rate or other rate is found
for the specified equipment.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
271
Related Information
Other Size Per Formula [page 269]
OSPF Charge Automation Process [page 272]
Viewing the OSPF Rate Details in the Booking Screen [page 272]
9.2.2 OSPF Charge Automation Process
In the charge automation process for bookings and forwarding agreement quotations (FWAQs), the system
uses the direct rate for the specified equipment type if one is available. If there is no direct rate, the system
uses the other size per formula (OSPF) settings to calculate a rate.
The OSPF formula is only applied to the leading charge type of the corresponding container shipping liners
(CSL) item type. Since surcharges are always maintained for all equipment types, a direct rate is always
available for surcharges.
 Example
A tariff contains the following rates for a 20' standard container (20ST):
•
•
Direct rate (tariff line item (TLI)): 20ST = $1000
OSPF: 20ST = 80% of 40ST = $900
In this example, the system applies $1000 as the rate, because it is a direct rate even though it is higher.
Related Information
Other Size Per Formula [page 269]
Entering the OSPF Formula in Forwarding Agreements [page 270]
Viewing the OSPF Rate Details in the Booking Screen [page 272]
9.2.3 Viewing the OSPF Rate Details in the Booking Screen
View the charge calculation details on the Charge Analysis Log tab in the Display Booking - CSL app when other
size per formula (OSPF) has been applied to calculate a rate for the equipment type.
Prerequisites
•
272
You have defined the OSPF formula in the forwarding agreement tariff in theEdit Forwarding Agreement CSL app.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
•
The following parameters have been added for your user ID in transaction /NSU3 on the Parameters tab:
•
•
/TMCSL/FULL_PRC_VIEW = X
/SCMTMS/TCC_LOG = X
Procedure
1. In your SAP Fiori launchpad, open the Change Booking - CSL app, and then open the relevant booking.
2. Choose Calculate Charges.
If the system cannot find a direct rate for the equipment type specified in the booking item, then the OSPF
rate is applied to the booking.
3. On the Charges tab, select the ocean carrier freight (OCF) rate and then select the Charge Analysis Log tab.
If an OSPF rate has been applied, then the details of the rate calculation are displayed.
4. Save the booking.
Related Information
Other Size Per Formula [page 269]
Entering the OSPF Formula in Forwarding Agreements [page 270]
OSPF Charge Automation Process [page 272]
9.3
Equipment Substitution
During the booking process, the carrier might not have available the equipment type requested by the
customer. In this event, the carrier provides alternative equipment based on predefined rules in the agreement
or the global tariff. The equipment type used for charge calculation is also determined based on these rules.
Overview
When the Voyage Suggestion Framework (VSF) is executed during the booking process to generate a route
proposal, the equipment availability check is also triggered to check the equipment status through SAP
Transportation Resource Planning.
If the booked equipment size is not available at the time of equipment pickup, the system checks the
predefined alternative equipment type and the rules to determine the pricing equipment type in the tariff and
agreement. Finally, the system proposes a substitution equipment and a pricing equipment type. Usually, the
size of the alternative equipment maintained in the tariff or agreement is larger than the requested equipment.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
273
Related Information
For more information about route proposal generation, see SAP Library for your SAP Transportation
Management, order to cash for container shipping liners for SAP S/4HANA release on SAP Help Portal at
https://help.sap.com/tm_csl_o2c_s4hana. Open the Product Assistance and search for Route Proposal
Generation.
For more information about the equipment availability check, see SAP Library for your SAP Transportation
Management, order to cash for container shipping liners for SAP S/4HANA release on SAP Help Portal
at https://help.sap.com/tm_csl_o2c_s4hana. Open the Product Assistance and search for Equipment
Availability Check.
For more information about SAP Transportation Resource Planning, see SAP Library for your
SAP Transportation Resource Planning release on SAP Help Portal at https://help.sap.com/viewer/p/
SAP_TRANSPORTATION_RESOURCE_PLANNING. Under Application Help open SAP Library.
Maintaining Equipment Substitution Rules [page 274]
Determining the Pricing Equipment Type in Bookings with Substituted Equipment [page 276]
9.3.1 Maintaining Equipment Substitution Rules
Maintain the substitution equipment type and the rules used to determine the pricing equipment type in the
Governing Tariff screen.
Prerequisites
•
The agreement type has been defined in Customizing for Transportation Management under
Data
•
Agreement and Service Products
Master
Define Freight Agreement Types .
The agreement type has been identified as Tariff in Customizing for Transportation Management under
Lead to Agreement
Pricing
Master Data
Agreements
Define Forwarding Agreement Types .
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement - CSL app, and then open the relevant
tariff.
2. On the Equipment Substitution tab, enter the following mandatory details:
274
Field Name
Description
Requested Equipment Type
Original equipment type in the booking request
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
Field Name
Substituted Equipment Type
Description
Alternative equipment proposed to the customer to load
the cargo. Usually, the size is larger than the Requested
Equipment Type.
Example
•
•
Pricing Equipment Type
Request Equipment Type: 20G0
Substituted Equipment Type: 40G0
Equipment type proposed to the customer for pricing pur­
poses if certain rules are passed
3. (Optional): Enter the following fields to specify the rules for determining the pricing equipment type in the
booking request:
Field Name
Description
Weight Threshold
Used to compare with the net weight in the booking to
determine the pricing equipment type in the booking.
If the net weight is greater than the weight threshold you
specify here, then the system uses the substituted equip­
ment type.
Weight UoM
Volume Threshold
Unit of measurement (UoM) for weight threshold
Used to compare with the gross volume in the booking to
determine the pricing equipment type in the booking.
If the gross volume in the booking is greater than the
volume threshold you specify here, then the system uses
the substituted equipment type.
If the gross volume in the booking is less than the volume
threshold you specify here, then the system uses the origi­
nally requested equipment type.
Volume UoM
UoM for volume threshold
 Note
If you do not specify these details, then the system uses the Pricing Equipment Type specified in Step 2.
4. Save the tariff.
Next Steps
When the tariff is released, the substitute equipment and pricing equipment can be determined for a booking
during the execution of the Voyage Suggestion Framework in the charge calculation process.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
275
Related Information
Equipment Substitution [page 273]
Determining the Pricing Equipment Type in Bookings with Substituted Equipment [page 276]
9.3.2 Determining the Pricing Equipment Type in Bookings
with Substituted Equipment
Choose a route proposal with an equipment substitution in a booking, and the system determines the pricing
equipment type using the predefined rules in the governing tariff.
Prerequisites
You have maintained the equipment substitution rule in the tariff in the Edit Forwarding Agreement - CSL app.
Context
When you choose a route proposal with an equipment substitution in a booking, the following rules are
executed in sequence to determine the pricing equipment type for the booking:
1. If threshold information is not maintained in the tariff, then the system uses the pricing equipment type
maintained in the tariff.
2. If the net weight is greater than the weight threshold in the tariff, then the system uses the substituted
equipment type.
3. If the gross volume is greater than the volume threshold in the tariff, then the system uses the substituted
equipment type.
4. If the gross volume is less than the volume threshold in the tariff, then the system uses the originally
requested equipment type.
The pricing equipment type is used for charge calculation in the booking, and is set as the originally requested
equipment if no substitution happens.
Procedure
1. In your SAP Fiori launchpad, open the Change Booking - CSL app, and then open the relevant booking.
2. Enter the booking items including the equipment type and quantity.
3. Generate the routes for the booking.
The system executes the Voyage Suggestion Framework (VSF) to generate the route proposals.
276
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
4. Select a route proposal with an equipment substitution.
The system applies the following changes in the booking item:
•
•
•
•
The requested equipment is replaced with the substitution equipment.
The original equipment is entered.
The pricing equipment type is determined using the predefined rules listed above.
The equipment substitution checkbox is selected.
5. Save the booking.
Next Steps
The proposed substitution equipment type is used during the entire transportation phase, and the pricing
equipment type is used for the charge calculation in this booking.
Related Information
Equipment Substitution [page 273]
Maintaining Equipment Substitution Rules [page 274]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Enhancements to Charge Calculation
PUBLIC
277
10 Integration
SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA is
integrated with the charge calculation in the booking app and with routing.
Integration with Charge Calculation in Bookings
The lead to agreement solution is integrated with the charge calculation in the booking app in SAP
Transportation Management, order to cash for container shipping liners for SAP S/4HANA. The integration
allows transportation charges to be calculated based on a customer forwarding agreement (FWA) or a
standard tariff.
Integration with Routing
Forwarding agreement quotations (FWAQs) in the lead to agreement solution are integrated with the routing
solution in the option for container shipping liners during the request for quotation (RFQ) translator upload and
response line generation.
Related Information
Charge Calculation in Bookings [page 278]
10.1 Charge Calculation in Bookings
The booking application in SAP Transportation Management, order to cash for container shipping liners has
been enhanced to support the charge calculation process.
Transportation charges can be calculated in bookings based on a customer forwarding agreement (FWA) or
a standard tariff. The method of processing individual charges depends on the surcharge condition in the
customer FWA or standard tariff. If the customer FWA does not contain a through-rate, the system executes
the rate construction for ocean carrier freight (OCF) charges.
The booking process has been enhanced to support charge calculation as follows:
•
278
Customer FWA or standard tariff determination
In a booking, you can choose to execute the charge calculation based on a customer FWA or a standard
tariff.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Integration
•
Exception processing
If a charge type in a customer FWA includes an exception, the charge calculation retrieves the charges from
the customer FWA based on the surcharge condition.
•
Rate construction
If a through-rate is not found in the customer FWA for OCF charges, the charge calculation attempts to
construct a rate using inland and arbitrary charges.
•
Inland charges
Inland charges are used to price the inland leg of a route when the through-rate is not available in the OCF
rate tables. The inland charges are applicable to the origin and destination legs of the route.
•
Arbitrary charges
Arbitrary charges are used when no direct rates are available between the port of loading (POL) and port
of discharge (POD). The system tries to fetch the rate from a dedicated arbitrary charge type from the
load port to an origin base port (not necessarily the intermediate port in the proposed physical route).
Afterwards, the system retrieves the OCF rate from the origin base port to the discharge port. If the system
successfully retrieves the OCF rate, the rate is constructed based on the load port, origin base port, and
discharge port using the OCF and arbitrary rate tables. The same logic applies to the discharge port.
Related Information
Assigning a Customer FWA or Standard Tariff to a Booking [page 279]
Exception Processing [page 280]
Rate Construction [page 281]
Integration [page 278]
10.1.1 Assigning a Customer FWA or Standard Tariff to a
Booking
Specify whether the charge calculation in a booking is based on a standard tariff that is determined by the
system or on a specific customer forwarding agreement (FWA).
Prerequisites
•
A standard tariff has been created for the pricing trade based on the source and destination location in the
booking.
•
A customer FWA exists and is valid on the day of the booking.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Integration
PUBLIC
279
Procedure
1. In your SAP Fiori launchpad, open the Create Booking - CSL app.
2. In the initial booking screen, specify the required information and choose Continue.
3. In the main booking screen, specify the following details on the General Data tab:
•
•
The source and destination location
One of the following contract types:
Option
Description
Tariff
If you select Tariff, the system determines the standard tariff in­
ternally by using the pricing trade of the source and destination
locations.
Forwarding Agreement
If you select Forwarding Agreement, you must also specify the
customer FWA number in the Forwarding Agreement field. The
system calculates the charges based on the specified FWA.
 Note
If you do not specify a forwarding agreement, then the system will determine all of the agreements
by matching a certain set of attributes. This feature needs to be used carefully, as the performance
can deteriorate if the system determines a large number of agreements and then looks for rates
from each of them.
4. Specify any other required information.
5. Choose Calculate Charges to trigger charge calculation for the booking.
The system calculates the charges based on your chosen contract type, and displays the details on the
Charges tab.
6. Save your entries.
Related Information
Charge Calculation in Bookings [page 278]
10.1.2 Exception Processing
If a customer forwarding agreement (FWA) is selected as the contract type for a booking, the charge
calculation process only retrieves the rates from the FWA for those charges from which an exception has
been taken. The charges must have been processed as exceptions. In all other cases, the system retrieves the
rates from the standard tariff.
During the quotation process, the system generates responses for request lines using the standard tariff. The
exception process begins when a customer asks for an exclusive price for a charge type. The pricer applies an
280
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Integration
exception to the charge type in the forwarding agreement quotation (FWAQ), and then maintains the exception
amount in the revenue of the corresponding leading charge type. There are no rate tables created for these
charge types.
Once the response has been approved, the FWAQ is converted to a forwarding agreement.
During the charge calculation in a booking that specifies a customer FWA as the contract type, the system only
retrieves the rates from the FWA for charges that have gone through the exception process described above.
Related Information
Conversion of FWAQs to Forwarding Agreements [page 237]
Assigning a Customer FWA or Standard Tariff to a Booking [page 279]
Integration [page 278]
10.1.3 Rate Construction
During charge calculation, if the through-rate is not available for the ocean carrier freight (OCF) charge type
(leading marine charge), the system attempts to construct a rate using the inland and arbitrary charge types.
This process for constructing rates is applied in the following scenarios:
•
•
Response line generation in forwarding agreement quotations (FWAQs)
Charge calculation in bookings
The ocean freight rate for the underlying commercial routing is determined when the system performs a
sequence of rate look-ups for a request line in a FWAQ or during the charge calculation in a booking. In addition
to the pure ocean freight logic, which covers the transportation between two ports, a trade tariff can be set up
to evaluate the transport additional arbitrary charges during the charge calculation process.
For charges calculated against a forwarding agreement in the booking, the inland and arbitrary charges can be
stitched using the corresponding agreement items (container shipping liners (CSL) item types inland origin,
inland destination, arbitrary origin, and arbitrary destination) available in the agreement.
The arbitrary charges can be defined between the port of loading (POL), the origin base port, the destination
base port, and the port of discharge (POD). The location connected to the base port can be a port or a ramp.
The origin base port and the destination base port do not appear in the routing since they are a part of the
commercial route rather than the actual route.
Related Information
Integration [page 278]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Integration
PUBLIC
281
10.1.3.1 Example: Rate Construction Using Forwarding
Agreement
Consider an example of a charge calculation for a container in a door-to-door scenario done against an
agreement. The container is shipped from the customer door location in Beijing to the consignee in Chicago.
Assume you have a forwarding agreement that has been created with items for the following container shipping
liners (CSL) item types:
•
•
•
•
•
Inland origin between door to port of loading
Arbitrary origin between port of loading and origin base port
Marine between origin base port and destination base port
Arbitrary destination between destination base port and port of discharge
Inland destination between port of destination to door
The rate construction process follows the stitching logic illustrated below to construct a rate for a door-to-door
scenario. The inland and arbitrary rates are picked from the same agreement as where the OCF is picked for
stitching of rates. If inland and arbitrary rates cannot be determined from the forwarding agreement, then they
are looked up from the corresponding tariffs configured in the system.
Rate Construction for Door-to-Door Scenario
The following table lists the steps that the system follows when constructing a rate:
No.
Step
Description
1
Preprocess: Find the through-rate.
The system evaluates the ocean carrier
freight (OCF) charge rate table for the
charge calculation using the origin and
destination information. If the system
finds the rates, it creates a through-rate
and stops the charge calculation proc­
ess. Otherwise, the system continues
with the next step.
282
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Integration
No.
Step
2
Divide the route at the port of discharge If the system cannot create a through(POD).
Description
rate in Step 1, it divides the route at the
POD to create the inland destination
leg. The inland destination charge type
is evaluated using the POD and the final
destination location. If the system finds
the destination inland rate, it calculates
the OCF rates for the port of loading
(POL) and POD.
3
Divide the route at the POL.
The system divides the route at the
POL, and evaluates the inland origin
charge types for the origin location and
the POL. If the system finds the inland
rate, it calculates the OCF rate for the
POL to the destination location. If the
OCF rate is calculated successfully, the
charge calculation process stops. Oth­
erwise, the system continues with the
next step.
4
Divide the route at the POL and POD.
The system divides the route at the POL
and POD to allow the following evalua­
tions:
•
The inland origin charge type to be
•
The inland destination charge type
evaluated using the origin and POL
to be evaluated using the POD and
destination
The OCF rate table is retrieved for the
POL and POD.
5
Determine the destination base port.
The system determines the destination
base port by evaluating the arbitrary-atdestination charge type from Customiz­
ing using the POD. The OCF rate table
is evaluated using the POL and destina­
tion base port. The inland origin and in­
land destination charge types are eval­
uated using the methods described in
Steps 2 and 3.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Integration
PUBLIC
283
No.
Step
Description
6
Determine the origin base port.
The origin base port is determined
by evaluating the arbitrary-at-origin
charge type from Customizing using
the POL. The OCF rate is evaluated us­
ing the origin base port and POD. The
logic of the inland charge type is eval­
uated using the methods described in
Steps 2 and 3.
7
Determine the origin and base ports.
The origin and destination base ports
are determined from the arbitraryat-origin and arbitrary-at-destination
charge types using the POL and POD.
The OCF rate table is evaluated based
on the origin and destination base
ports. The inland charge type is evalu­
ated using the methods described in
Steps 2 and 3.
The result of the processing above is that a rate is constructed for the given combination of origin and
destination locations using the following charge types: OCF, transport additional - origin (TAO), transport
additional - destination (TAD), inland origin, and inland destination.
The different tariffs used in the rate construction are maintained in the Maintain Standard Tariff - CSL and
Maintain Arbitrary Tariff - CSL apps. You can maintain the base ports for port of loading and port of destination
in the Maintain Base Port - CSL app.
The OCF and marine surcharges are picked from the marine tariff. The inland origin charges and its surcharges
are picked from the inland origin tariff. The inland destination and its surcharges are picked from the inland
destination tariff. The TAO and the TAD charge types are looked-up from the arbitrary origin and arbitrary
destination tariffs. If service products/services are requested, then the corresponding tariff types (service
inland origin, service marine, and service inland destination) are processed depending on the different legs
involved.
 Note
Various rate-construction scenarios are possible, for example, port-to-port, ramp-to-ramp, port-to-door,
ramp-to-door, and so on. However, all the scenarios follow the same pattern as the door-to-door scenario.
Related Information
Tariff Management [page 173]
Integration [page 278]
Charge Calculation in Bookings [page 278]
Rate Construction [page 281]
284
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Integration
10.1.4 Charge Calculation with Proposed Services
In the forwarding agreement quotation process, you can create request lines and add services to them. At the
time of generating responses, the charges are calculated for these services.
These charges can follow the negotiation process and rates can be changed. These details are transferred to
the forwarding agreement during the agreement creation and update processes.
Charges can be calculated in bookings based on a customer forwarding agreement (FWA). In the Booking
screen, when you choose Propose Services and Calculate Charges, a dialog box appears that displays all of
the agreement items (depending on the different legs involved such as marine, inlands, and arbitraries) per
booking item. It has the leading charge type rate lines picked up from the forwarding agreement along with
the services. When you select the rate line from the dialog box, the selected services are added to the booking
item. The system calculates the rates for the leading charge types along with the service charge types. For
every container item available in the booking, you must select at least one agreement item.
You can use a Business Add-In (BAdI) to filter the agreement rate lines based on the service products added to
the booking item during charge calculation rate filtering. The BAdI is available in Customizing for Transportation
Management under
Determination
Container Shipping Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Charge
BAdI: Filtering of Rate Lines by Services .
Related Information
Integration [page 278]
10.1.5 Multi-Rate Scenario
Transportation charges can be calculated in bookings based on a customer forwarding agreement (FWA) or a
standard tariff. As a result of the calculation, multiple rates can be found.
If multiple rates are found for any of the leading charge types for marine, inland origin, or inland destination
legs, then the system does not calculate the rates of their corresponding surcharges initially (that is, marine
surcharges, inland origin surcharges, and inland destination surcharges). Only the leading charge types with
the multi-rate information are displayed. This is because the surcharges and their surcharge conditions depend
on the leading charge type (stored as part of the revenue information) in the case of a customer agreement
with the agreement category Quotation or Tariff with Revenue.
You can choose one of the rates from the dialog box for the leading charge type corresponding to marine
first. Based on the selected rate line, the associated revenue information is processed, and surcharges are
calculated and displayed. Next, you can choose one of the rates for the other leading charges for inland origin
and inland destination. The system follows the same process and calculates the corresponding surcharges.
When the charges are calculated in a booking against a tariff and if multiple rates are found for any charge
types, then you can choose one of the rate lines in any order. There is no dependency between the leading
charge types and their surcharges.
When the charges are calculated in a forwarding agreement quotation against a tariff (for example, during
the generation of response process) and if the system finds multiple rates for any of the charges, the highest
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Integration
PUBLIC
285
rate is picked automatically. This is implemented through a Business Add-In (BAdI). If you want to implement
your own logic, you can create your own implementation in Customizing for Transportation Management under
Container Shipping Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Charge Determination
BAdI:
Rate Determination for Standard Tariff Call from FWAQ .
Related Information
Integration [page 278]
286
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Integration
11
Regulatory Filing Framework
Regulatory filing is a framework built on top of SAP Transportation Management, lead to agreement for
container shipping liners for SAP S/4HANA. It is designed to support the regulatory filing process for container
shipping liners.
The framework is seamlessly integrated with the following lead to agreement applications and functions:
•
•
•
•
•
Forwarding agreement (FWA)
Forwarding agreement quotation (FWAQ)
Charge calculation sheet
Rate table
Transportation charge calculation
Regulatory filing is applicable to the following lead to agreement applications:
•
Tariffs
You create and maintain the leading charge type rates in the tariffs through the Tariff Quotation app. You
can create the following types of tariffs:
•
Marine Tariff
•
•
•
•
Marine Surcharge
Arbitrary Tariff
Inland Tariff
•
•
•
Basic Ocean Freight Rate
Basic Inland Rate
Inland Surcharges
Customer Agreements
You create and maintain customer agreements through the Customer Quotation app. You can create the
following types of customer agreements:
•
•
Spot Quotation
Service Contract
 Note
Surcharge filing is only possible in the tariffs. It is not supported in customer agreements.
Surcharges in the tariff can be filed either through a surcharge filing request or by the rule/subrule in the
governing tariff.
Process Overview
The basic process flow for the regulatory filing of tariff line items (TLIs) is as follows:
1. Set up the regulations.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
287
2. Set up the tariffs and customer agreements.
3. Determine the filing relevance.
4. Send filing requests to the tariff publishing queue.
5. Process filing requests in the tariff publishing queue.
Features
•
•
You can set up multiple regulations for a single tariff.
When setting up regulations, you can specify the filing level as follows:
•
Root level (forwarding agreement root)
Root level filing means to file the required terms and sections of the agreement with the authority.
•
TLI level (rate line item level)
TLI level filing means to publish the individual rate line items of the tariff/agreement . TLI level filing
needs to go through the queue processes.
•
You can send filing requests from a tariff or customer agreement to the queue either manually or
automatically.
•
•
•
•
You can process filing requests in the queue either manually or automatically.
You can send the filing request to the defined approver for approval.
You can expire the published TLIs in the tariff.
You can create and publish a governing tariff, rules, and subrules.
 Note
Commodity group, port group, duration-based charges, and services in regulatory filing are not supported.
Business Add-Ins for Regulatory Filing
The regulatory filing framework does not handle any specific filing regulations. It is a framework with a basic
process flow and various BAdIs. You can implement the BAdIs and extend the tariff publishing queue to
fit your particular regulatory requirements. For more information about the regulatory filing BAdIs, see the
Configuration Guide for Regulatory Filing on the SAP Help Portal at https://help.sap.com/tm_csl_l2a_s4hana.
The regulatory filing BAdIs listed in the following table are delivered with default implementations to run the
general filing processes. For more information about the default implementations, see SAP Note 2990686 .
You can either continue with the default implementation if it fits your needs, or you can replace it with your own
implementation.
Business Add-In
/TMCSL/BADI_FQ_GET_DUPLICATE
Usage
Retrieve the duplicated filing request in the tariff publishing
queue.
288
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Business Add-In
Usage
/TMCSL/BADI_ACTIVATE_RATE_LINE
Turn the status of a TLI in the tariff/customer quotation from
inactive to active after the TLI is published.
/TMCSL/BADI_FQ_GET_CHRG_OVLP
Calculate the filing request in the queue and determine the
overlapped TLIs in the tariff.
/TMCSL/BADI_FILING_QUE_UPDATE
Update the filing request after it is processed.
/TMCSL/BADI_FILING_PROCESS
Approve the filing request in the tariff publishing queue.
/TMCSL/BADI_GOV_TARIFF_PUBLISH
Publish a governing tariff, rule, and subrule.
The BAdIs in the following table are delivered without any default implementation. You can create and activate
implementations with your required business logic for the regulation.
Business Add-In
Usage
/TMCSL/BADI_FILING_QUE_CREATE
Extend the tariff publishing queue.
/TMCSL/BADI_FILING_REL_DET
Determine if a TLI is relevant for regulatory filing.
/TMCSL/BADI_FILING_SEND_EXTERN
Send TLIs to an external system.
/TMCSL/BADI_RATEID_GENERATION
Create TLI IDs in your own format for published TLIs.
/TMCSL/BADI_FILING_RT_PUBLISH
Perform forwarding agreement root level filing.
/TMCSL/BADI_FQ_REQ_APPROVAL
Send the queued TLIs to the defined approver for approval.
Related Information
Basic Settings [page 290]
Master Data [page 297]
Tariff Management [page 310]
Customer Quotations [page 337]
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests to Queue [page 346]
Processing of Filing Requests [page 359]
Publishing Surcharges Through Governing Tariff Rules [page 376]
Filing at Root Level [page 377]
Expiration of Published TLIs [page 378]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
289
11.1
Basic Settings
Before using the regulatory filing framework, you need to configure certain basic settings in SAP Transportation
Management, lead to agreement for container shipping liners for SAP S/4HANA as follows:
•
General Customizing Settings
The Customizing activities for regulatory filing are located in Customizing for Transportation Management
•
Data Management
You can configure the archiving function of the tariff publishing queue to archive filing requests that are no
longer required.
under
Container Shipping Liners
Lead to Agreement
Tariff Filing .
Related Information
General Settings [page 290]
Data Management [page 291]
11.1.1 General Settings
Before using the regulatory filing framework, you need to maintain the general configuration settings.
All of the configuration activities for regulatory filing are located in Customizing for Transportation Management
under
Container Shipping Liners
Lead to Agreement
Tariff Filing .
The basic configurations for regulatory filing are as follows:
•
•
•
•
Maintain Regulation Types
Maintain Filing Levels
Define Tariff Publishing Queue Number Range
Define Tariff Publishing Queue Archiving Residence
For more information about configuring the regulatory filing framework, see the Configuration Guide for
Regulatory Filing available on the SAP Help Portal at https://help.sap.com/tm_csl_l2a_s4hana.
290
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11.1.2 Data Management
The regulatory filing framework offers the following data management option to help you to manage your data:
Function
Purpose
More Information
Archiving
You can use archiving to remove mass
Archiving [page 291]
data from the database that is no lon­
ger required in the system but must be
kept in a format that can be analyzed.
Related Information
Archiving [page 291]
11.1.2.1 Archiving
You can use transaction AOBJ to create archiving objects. You can specify archiving objects for preprocessing,
writing, and deleting activities. For more information, see Customizing for SAP NetWeaver under
Server
System Administration
Data Archiving
Application
Archiving Object-Specific Customizing .
You can use the following archiving object for the tariff publishing queue:
Business Object
Archiving Object
Documentation
Filing Queue
/TMCSL/QUE
Archiving Tariff Publishing Queue [page
294]
You can also extend the archiving objects for SAP Transportation Management, lead to agreement for container
shipping liners for SAP S/4HANA liners based on your own business requirements. You can specify the
database tables from which the system archives the information for the archiving object.
You can use transaction SARA to schedule when the system executes the preprocessing, writing, and deleting
activities for an archiving object. For more information, see
SARA
SAP Easy Access
Tools
Administration
Data Archiving .
You can use the following features in transaction SARA:
•
Preprocessing
We provide each business object with separate selection criteria to identify the instances of the business
object that are ready for archiving. We provide each query with the same logic. The query selects the
instances that are ready and calls the CHECK_ARCHIVABILITY action. The action checks the residence
period and sets the archiving status to Archiving in Process. The action only runs across the relevant
business object.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
291
 Note
You define the residence period in Customizing for Cross-Application Components under
and Tools for Enterprise Applications
Archiving Adapter
Processes
Reusable Objects and Functions for BOBF Environment
Maintain BO-Specific Residence Periods .
You can control the memory used during archive preprocessing by specifying the package size, and
describing the number of documents being processed together in one SAP Logical Unit of Work (SAP
LUW). Before the next package is selected and processed, allocated memory is released to keep the
memory consumption for the preprocessing batch job constant.
•
Writing
The system selects all instances of a business object that have the archiving status Archiving in Process. It
copies the instances into the archive. You can control the memory used during writing in the same way as
for preprocessing.
•
Deleting
The system deletes all records that are archived from the registered database tables.
•
Deleting from Archive
All Transportation Management (TM) archiving objects are ILM-enabled. For more information about SAP
Information Lifecycle Management (SAP ILM), see http://help.sap.com/erp . Choose your release and
open SAP Library. Choose
SAP ERP Cross-Application Functions
Cross-Application Components
SAP
Information Lifecycle Management .
You can load archived documents into the standard TM screens. The system uses only the display mode for
these archived documents. We provide each business object in TM with the following settings:
•
•
Individual archiving object
•
•
•
CHECK_ARCHIVABILITY action
Archiving status
Statuses include Not Archived, Archiving in Process, and Archived.
Programs for each of the preprocessing, write, and delete steps
Individual query to select business objects for the preprocessing step
For more information about the prerequisites you must specify before you can begin archiving, see
Prerequisites for Archiving [page 126].
More Information
For more information about the Archive Information System, see SAP Library for SAP NetWeaver on SAP
Help Portal at http://help.sap.com/nw . Choose your release. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View, and choose
Archiving in the ABAP Application System
Solution Life Cycle Management
Data Archiving
Data Archiving with Archive Development Kit (ADK)
Data
Archive
Information System .
For more information about tables and archiving objects, see SAP Library for SAP NetWeaver on SAP Help
Portal at http://help.sap.com/nw . Choose your release. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View, and choose
292
PUBLIC
Solution Life Cycle Management
Data Archiving
Data
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Archiving in the ABAP Application System
Administration
Data Archiving with Archive Development Kit (ADK)
Archive
Tables and Archiving Objects .
Related Information
Why Archive? [page 126]
Prerequisites for Archiving [page 126]
11.1.2.1.1 Archiving for Business Objects
The following are the archiving object and business object combinations you can use in processes for SAP
Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA. You can use
transaction SARA (Archive Administration) to perform the archiving.
Business Object
Archiving Object
Filing Queue
/TMCSL/QUE
Documentation
Archiving Tariff Publishing Queue [page
294]
More Information
For more information about data archiving, see SAP Library for SAP NetWeaver on SAP Help Portal at http://
help.sap.com/nw . Choose your release. Under Application Help, open SAP NetWeaver Library: FunctionOriented View, and choose
Application System
Solution Life Cycle Management
Data Archiving
Data Archiving with Archive Development Kit (ADK)
Data Archiving in the ABAP
Archive Information System .
Related Information
Archiving [page 291]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
293
11.1.2.1.1.1 Archiving Tariff Publishing Queue
You can use the archiving object /TMCSL/QUE to archive filing queue objects.
Structure
Tables
SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA uses
the archiving object /TMCSL/QUE to archive data from the nodes of the business object model /TMCSL/
FILING_QUEUE.
Programs
The following programs are available for /TMCSL/QUE:
Program
Function
/TMCSL/ARCH_QUEUE_PRE
Preprocessing
/TMCSL/ARCH_QUEUE_WRI
Write
/TMCSL/ARCH_QUEUE_DEL
Delete
Prerequisites for Writing Tariff Publishing Queue
If the following prerequisites are met, the system can archive filing queue requests:
•
•
•
The filing queue request was in the database for the entire residence period.
The filing queue request has an end-of-business status of Rejected or Published.
The filing queue request has an archiving status of Not Archived or Archiving in Process.
Functions
The Preprocessing and Write functions use the QU_FOR_CHECK_ARCHIVABILITY query to identify objects that
have not yet been archived.
The Preprocessing function uses the CHECK_ARCHIVABILITY action to check whether the object can be
archived. The archiving objects are given the archiving status Archiving in Process if they fulfill the following
prerequisite:
•
The non-archived filing queue has existed in the database for longer than the business object (BO)-specific
residence period.
The residence period is configured in Customizing for Transportation Management under
Shipping Liners
Lead to Agreement
Tariff Filing
Container
Define Tariff Publishing Queue Archive Residence .
The BO-specific residence period starts from the approval date or rejected date of the filling queue.
The Write function saves all archiving objects that have the status Archiving in Process in an archiving
document. You choose the option ILM Action: Archiving when executing the Write function. The system
checks the residence policy configured with transaction IRMPOL for the ILM object TMCSLQUE and audit area
294
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
ARCHIVING. If the ILM end-of-residence duration is not reached for a filling queue, the filling queue will not be
written into the archiving document.
The Delete function deletes all archived objects permanently from system.
You cannot edit or delete a filling queue when the archiving status is Archiving in Process or Archived.
More Information
For more information about the Archive Information System, see SAP Library for SAP NetWeaver on SAP
Help Portal at http://help.sap.com/nw . Choose your release. Under Application Help, open SAP NetWeaver
Library: Function-Oriented View, and choose
Archiving in the ABAP Application System
Solution Life Cycle Management
Data Archiving
Data Archiving with Archive Development Kit (ADK)
Data
Archive
Information System .
Related Information
Archiving [page 291]
11.1.2.1.2 ILM Objects for Business Objects
The following are the ILM object and business object combinations you can use for regulatory filing processes
in SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA.
Business Object
ILM Object
Documentation
Filing Queue
TMCSLQUE
ILM Objects for Tariff Publishing Queue
Request [page 296]
More Information
For more information about SAP ILM, see SAP Library on http://help.sap.com/erp
open SAP Library and then choose
SAP ERP Cross-Application Functions
. Choose your release,
Cross-Application Components
SAP Information Lifecycle Management .
Related Information
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
295
Archiving [page 291]
11.1.2.1.2.1 ILM Objects for Tariff Publishing Queue Request
The Information Lifecycle Management (ILM) object TMCSLQUE is mapped to the archiving object /TMCSL/
QUE. You can find full information about the mapping of ILM objects to destruction objects using transaction
IRM_CUST.
Available Policy Categories
Policy Category
Description
RST
Residence Rules
RTP
Retention Rules
 Note
•
The policy category RTP is delivered by Transportation Management (TM). The policy category RST is
provided by SAP Transportation Management, lead to agreement for container shipping liners for SAP
S/4HANA for archiving the write process of the filling queue using ILM residence rules.
•
The configurations for available time reference, available time offsets, and available condition fields are
the same as those delivered by TM.
Available Time Reference
Information Retention Manager (IRM) Constant
Description
COMPLETION_DATE
End Date
Available Time Offsets
IRM Constant
Description
END_OF_MONTH
End of Month
END_OF_QUARTER
End of Quarter
296
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
IRM Constant
Description
END_OF_YEAR
End of Year
Available Condition Fields
Condition Field
Description
QUEUE_ID
Queue ID
For value determination for time references or condition fields use transaction IRM_CUST.
Related Information
ILM Objects for Business Objects [page 295]
11.2
Master Data
Master data represents the business objects used in applications to support transactional processes and
operations.
In addition to the master data objects of SAP Transportation Management, lead to agreement for container
shipping liners for SAP S/4HANA, the master data object, Governing Tariff, is part of the regulatory filing
framework.
Related Information
Governing Tariffs [page 297]
11.2.1 Governing Tariffs
You can create two types of objects in the governing tariff application: rule templates and governing tariffs.
You can create rule templates to maintain common rules and subrules and then use them as templates to
speed up the process when creating governing tariffs. You can create a governing tariff to maintain and publish
the regulatory filing relevant rules, subrules, clauses, and conditions.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
297
In the General Data section of the Governing Tariff app, you can maintain the following information:
•
•
•
•
•
•
•
Governing tariff ID
Description
Regulation type
Source zone
Destination zone
Valid-from date
Valid-to date
The source zone and destination zone define the scope of the governing tariff. You can also see the type and
publishing status of the governing tariff.
On the Rule tab of the Governing Tariff app, there is a hierarchical structure. You can maintain and publish rules
and subrules in this section. One governing tariff can have multiple rules, one rule can have multiple subrules,
and subrules can have multiple versions. You can also maintain attachments for subrules.
You need to publish the governing tariff, rule, and subrule separately by choosing the Publish button at each
different level. You must publish the governing tariff before you can publish the rules, and you must publish the
rule before you can publish the related subrules.
On the Link Governing Tariff tab of the Governing Tariff app, you can link other governing tariffs to your
governing tariff. For example, if you set up inland, detention and demurrage, and bill of lading rates in other
governing tariffs and they are relevant to your governing tariff, you can include them on the Link Governing
Tariff tab.
On the Linked Rate Tariff tab of the Governing Tariff app, you can link your governing tariff to the corresponding
marine tariff, arbitrary tariff, and inland tariff. The governing tariff will cascade to the rate line items in the rate
tariffs during the regulatory filing relevance determination. When the rate line item in the rate tariff is published,
it goes under the umbrella of the governing tariff.
You can use the three Personal Object Worklists (POWL) for governing tariffs, rules, and subrules to search for
governing tariffs, rules, and subrules and then perform certain actions in the worklist.
Related Information
Creating Rule Templates [page 299]
Copying Rule Templates [page 300]
Creating Governing Tariffs [page 301]
Copying Governing Tariffs [page 302]
Publishing Governing Tariffs, Rules, and Subrules [page 306]
Linking Governing Tariffs to Governing Tariffs [page 304]
Linking Governing Tariffs to Rate Tariffs [page 305]
Using the Governing Tariff Worklist [page 307]
Using the Governing Tariff Rules Worklist [page 308]
Using the Governing Tariff Subrules Worklist [page 309]
298
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11.2.1.1 Creating Rule Templates
Create a rule template from scratch and use it to maintain common content for governing tariffs.
Context
When you create a governing tariff, you can use a rule template to help you reduce any repeat maintenance
effort. A rule template is available for use in a governing tariff when its status is Released. After releasing the
rule template, you cannot edit it any further.
Procedure
1. In your SAP Fiori launchpad, open the Create Governing Tariff app.
2. Select the governing tariff type Rule Template, and then choose Continue.
3. On the General Data tab, enter the rule template ID and description.
4. On the Rules tab, choose Insert Rule to create a new rule.
5. Enter the rule number, description, special case, and charge type.
6. Go to the Text Rule subtab to maintain the rule text.
7. Select the relevant rule and go to the Tariff Subrules tab.
8. Choose Insert to create a subrule, and then enter the subrule number, description, special case, and
charge type if applicable.
9. Select the subrule and go to the Text Subrule subtab.
10. Enter the text for the subrule.
11. (Optional) Choose the Attachments tab and create an attachment by inserting a folder, file, or URL.
12. Choose Release in the header toolbar to release the rule template.
13. Save your entries.
Results
The rule template is created and released.
Related Information
Governing Tariffs [page 297]
Copying Rule Templates [page 300]
Creating Governing Tariffs [page 301]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
299
Copying Governing Tariffs [page 302]
11.2.1.2 Copying Rule Templates
Copy a rule template and use it to maintain common content for governing tariffs. You can use a rule template
when creating a governing tariff to help you reduce any repeat maintenance effort.
Context
A rule template is available for use in a governing tariff when its status is Released. After releasing the rule
template, you cannot edit it any further.
Procedure
1. In your SAP Fiori launchpad, open the Edit Governing Tariff app.
2. Enter an existing rule template ID and then choose Continue.
3. Choose Copy in the header toolbar.
4. Make the necessary changes as required.
5. Choose Release in the header toolbar to release the rule template.
6. Save your entries.
Results
The rule template is created and released.
Related Information
Governing Tariffs [page 297]
Creating Rule Templates [page 299]
Creating Governing Tariffs [page 301]
Copying Governing Tariffs [page 302]
300
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11.2.1.3 Creating Governing Tariffs
Create a new governing tariff from scratch.
Procedure
1. In your SAP Fiori launchpad, open the Create Governing Tariff app.
2. Select the governing tariff type Governing Tariff and choose Continue.
3. On the General Data tab, enter the following information:
•
•
•
•
•
•
•
Governing Tariff ID
Description
Regulation Type
Source Zone
Destination Zone
Valid-From Date
Valid-To Date
4. On the Rules tab, choose Insert Rule to create a new rule, and enter the follow information:
•
•
•
•
•
•
Rule Number
Valid-From Date
Valid-To Date
Special Case
Charge Type
Text Rule
You can also choose Insert Rule Template to create new rules from a template. When you choose this
option, the rules in the rule template are copied into the governing tariff.
5. Select the rule and go to the Tariff Subrules tab.
6. Choose Insert to create subrules.
7. Enter the following information:
•
•
•
•
•
•
Subrule Number
Valid-From Date
Valid-To Date
Special Case
Charge Type
Text Rule
8. (Optional) Choose the Attachments tab and create an attachment by inserting a folder, file, or URL.
9. Save your entries.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
301
Results
The governing tariff is created.
Related Information
Governing Tariffs [page 297]
Publishing Governing Tariffs, Rules, and Subrules [page 306]
Using the Governing Tariff Worklist [page 307]
Using the Governing Tariff Rules Worklist [page 308]
Using the Governing Tariff Subrules Worklist [page 309]
11.2.1.4 Copying Governing Tariffs
Create a governing tariff by copying an existing one.
Procedure
1. In your SAP Fiori launchpad, open the Edit Governing Tariff app.
2. Enter an existing governing tariff ID and then choose Continue.
3. Choose Copy in the header toolbar.
4. Make the necessary changes as required.
5. Save your entries.
Results
The governing tariff is created.
Related Information
Governing Tariffs [page 297]
Publishing Governing Tariffs, Rules, and Subrules [page 306]
Using the Governing Tariff Worklist [page 307]
Using the Governing Tariff Rules Worklist [page 308]
Using the Governing Tariff Subrules Worklist [page 309]
302
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11.2.1.5 Creating New Versions of Governing Tariff Subrules
Create a new version of a published governing tariff subrule.
Context
The subrules in the governing tariff have a version. The initial version is set to 0. After the previous version of a
subrule is published, you can create a new version of the subrule.
Procedure
1. In your SAP Fiori launchpad, open the Change Governing Tariff app.
2. Enter the governing tariff ID and choose Continue.
3. Select a rule and go to the Subrule tab.
4. Choose Change View and select All Versions from the dropdown list.
You can see all the existing versions of the subrules.
5. Select a published subrule and choose Generate New Version.
6. Make changes to the new version of the subrule as required.
7. Save your entries.
Results
A new version of the subrule is created. The publish date of the new version of the subrule is empty, and the
publish status is Pending.
Related Information
Governing Tariffs [page 297]
Creating Governing Tariffs [page 301]
Copying Governing Tariffs [page 302]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
303
11.2.1.6 Linking Governing Tariffs to Governing Tariffs
Link a common governing tariff to another governing tariff.
Prerequisites
•
•
The common governing tariff you are going to assign is published.
The master governing tariff you are working on is not published.
Context
Depending on the setup of the governing tariffs, some common governing tariffs are generally applicable and
can be assigned to multiple other governing tariffs. For example, you could assign the inland governing tariff
and bill of lading governing tariff to multiple marine governing tariffs.
Procedure
1. In your SAP Fiori launchpad, open the Change Governing Tariff app.
2. Enter the master governing tariff ID and choose Continue.
3. On the Link Governing Tariff tab, choose Insert.
4. Enter the governing tariff ID or use the search help ( F4 ) to find the relevant governing tariff.
5. Select the linked governing tariff and choose Display Governing Tariff to link it to the master governing
tariff.
6. Save your entries.
Results
The selected governing tariff is linked to the master governing tariff.
Related Information
Governing Tariffs [page 297]
Creating Governing Tariffs [page 301]
Copying Governing Tariffs [page 302]
304
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11.2.1.7 Linking Governing Tariffs to Rate Tariffs
Link a governing tariff to a rate tariff (a marine tariff, arbitrary tariff, or inland tariff).
Prerequisites
The governing tariff has been published.
Context
Only published governing tariffs can be linked to rate tariffs. In addition, the regulation type in the governing
tariff and the regulation type of the rate tariff must be the same.
After you link the governing tariff to the rate tariff, the governing tariff is cascaded to the rate line items of the
marine tariff, arbitrary tariff, or inland tariff during the filing relevance determination. You can see the governing
tariff ID on the Filing Information tab of the rate line item.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement app.
2. Enter the marine tariff, arbitrary tariff, or inland tariff ID and choose Continue.
3. On the Regulation tab, choose Create.
4. Enter the regulation type and the governing tariff ID.
5. Save your entries.
Results
The governing tariff is linked to the marine tariff, arbitrary tariff, or inland tariff.
Related Information
Governing Tariffs [page 297]
Creating Governing Tariffs [page 301]
Copying Governing Tariffs [page 302]
Determination of Filing Relevance of TLI [page 338]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
305
11.2.1.8 Publishing Governing Tariffs, Rules, and Subrules
Publish a governing tariff, rule, and subrules separately and in order so that they are available for use.
Prerequisites
•
•
Before you can publish a rule, the governing tariff must have been published.
Before you can publish a subrule version, the related rule must have been published.
Context
You need to publish a governing tariff, rule, and subrules separately. Publishing a governing tariff does not
publish the rules and subrules within it, and publishing a rule does not publish the related subrules.
You can implement the Business Add-In (BAdI) /TMCSL/BADI_GOV_TARIFF_PUBLISH to send the required
information of the governing tariff, rule, and subrule to an external system. Implementing this BAdI is a
customer implementation task. For more information about the BAdIs of the regulatory filing framework,
see the Configuration Guide for Regulatory Filing available on the SAP Help Portal at https://help.sap.com/
tm_csl_l2a_s4hana.
Procedure
1. In your SAP Fiori launchpad, open the Change Governing Tariff app.
2. Enter the governing tariff ID and choose Continue.
3. Choose Publish in the header toolbar to publish the governing tariff.
4. Select the rule on the Rule tab and choose Publish in the toolbar to publish the rule.
5. Select the subrule version on the Subrule tab and choose Publish in the toolbar to publish the subrule
version.
6. Save your entries.
Results
•
The status of the governing tariff, rules, and subrules that you have published change from Pending to
Published.
•
•
The published governing tariff, rule, and subrule version are no longer editable.
306
When a new version of a subrule is published, the validity of the previous version is truncated.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Related Information
Governing Tariffs [page 297]
Creating Governing Tariffs [page 301]
Copying Governing Tariffs [page 302]
11.2.1.9 Using the Governing Tariff Worklist
Use the governing tariff worklist to search for and work with governing tariffs.
Context
The governing tariff worklist provides an overview of all of the governing tariffs in the system. The worklist is
based on the SAP Personal Object Worklist (POWL). You can define your own search criteria and save your own
worklists. You can also configure the data to be displayed in the worklist.
Procedure
1. In your SAP Fiori launchpad, open the Overview Governing Tariff app.
2. Choose All Governing Tariffs.
3. Enter the following search criteria as required:
•
•
•
•
•
•
•
•
Governing Tariff ID
Governing Tariff Description
Valid From
Valid To
Publish Status
Source Zone
Destination Zone
Regulation Type
4. Choose Apply to search for governing tariffs that meet the selection criteria.
5. In the governing tariff worklist, you can perform the following actions:
•
•
•
•
•
Choose New to create a new governing tariff.
Select one governing tariff and choose Copy to copy the governing tariff.
Select one governing tariff and choose Edit to modify it.
Select one or more governing tariffs and choose Publish to publish the governing tariffs.
Choose Refresh to refresh the search result.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
307
Related Information
Governing Tariffs [page 297]
Using the Governing Tariff Rules Worklist [page 308]
Using the Governing Tariff Subrules Worklist [page 309]
11.2.1.10 Using the Governing Tariff Rules Worklist
Use the governing tariff rules worklist to search for and work with governing tariff rules.
Context
The governing tariffs rules worklist provides an overview of all of the governing tariff rules in the system. The
worklist is based on the SAP Personal Object Worklist (POWL). You can define your own search criteria and
save your own worklists. You can also configure the data to be displayed in the worklist.
Procedure
1. In your SAP Fiori launchpad, open the Overview Governing Tariff app.
2. Choose All Governing Tariff Rules.
3. Enter the following search criteria as required:
•
Governing Tariff General Data
•
•
•
•
Governing Tariff ID
Governing Tariff Description
Publish Status
Governing Tariff Rule Data
•
•
•
•
•
•
•
•
•
Rule Number
Rule Description
Rule Text
Rule Status
Rule Valid From
Rule Valid To
Rule Publish Date
Charge Type
Special Case
4. Choose Apply to search for the governing tariff rules.
5. In the governing tariff rule worklist, you can perform the following actions:
308
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
•
•
•
Select one governing tariff rule and choose Edit to modify it.
Select one or more rules and choose Publish to publish the governing tariff rules.
Choose Refresh to refresh the search result.
Related Information
Governing Tariffs [page 297]
Using the Governing Tariff Worklist [page 307]
Using the Governing Tariff Subrules Worklist [page 309]
11.2.1.11 Using the Governing Tariff Subrules Worklist
Use the governing tariff subrules worklist to search for and work with governing tariff subrules.
Context
The governing tariffs subrules worklist provides an overview of all of the governing tariff subrules in the system.
The worklist is based on the SAP Personal Object Worklist (POWL). You can define your own search criteria and
save your own worklists. You can also configure the data to be displayed in the worklist.
Procedure
1. In your SAP Fiori launchpad, open the Overview Governing Tariff app.
2. Choose All Governing Tariff Subrules.
3. Enter the following search criteria as required:
•
Governing Tariff General Data
•
•
•
•
Governing Tariff Description
Publish Status
Governing Tariff Rule Data
•
•
•
Governing Tariff ID
Rule Number
Rule Description
Governing Tariff Subrule Data
•
•
•
Subrule Number
Subrule Description
Subrule Text
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
309
•
•
•
•
•
•
Subrule Status
Subrule Valid From
Subrule Valid To
Subrule Publish Date
Subrule Charge Type
Subrule Special Case
4. Choose Apply to search for the governing tariff subrules.
5. In the governing tariff subrule worklist, you can perform the following actions:
•
•
•
Select one governing tariff subrule and choose Edit to modify it.
Select one or more subrules and choose Publish to publish the governing tariff subrules.
Choose Refresh to refresh the search result.
Related Information
Governing Tariffs [page 297]
Using the Governing Tariff Worklist [page 307]
Using the Governing Tariff Rules Worklist [page 308]
11.3
Tariff Management
The carrier tariff is a basic agreement that is generally applicable to all customers (shippers). The tariff is
created as a forwarding agreement (FWA) in SAP Transportation Management, lead to agreement for container
shipping liners for SAP S/4HANA.
There are the following kinds of tariffs in lead to agreement:
Tariff
Description
Marine Tariff
A tariff that contains the basic ocean freight rate and marine
surcharges
Inland Tariff
A tariff that contains inland origin or inland destination and
the linked inland surcharges
Arbitrary Tariff
A tariff that contains transport additional origin (TAO) or
transport additional destination (TAD)
In regulatory filing, the tariff is the core application used to store published tariff line items (TLIs) and it must be
set up properly.
310
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Related Information
Forwarding Agreement Management [page 243]
Tariff Management [page 173]
Tariff Charge Types [page 174]
Set Up of Marine Tariffs [page 311]
Set Up of Inland Tariffs [page 323]
Set Up of Arbitrary Tariffs [page 317]
11.3.1 Set Up of Marine Tariffs
A marine tariff contains the basic ocean freight (OCF) charges and the related marine surcharges.
The forwarding agreement of the marine tariff has the agreement category Tariff with Revenue, and the
container shipping liners (CSL) item type of the forwarding agreement is set to Marine.
You create a marine tariff as follows:
1. Create the global rate tables for the marine tariff.
2. Create a calculation sheet for the marine tariff.
3. Create a forwarding agreement for the marine tariff.
You can also create a marine tariff from an existing template.
You maintain the basic ocean freight rates in the marine tariff via the Tariff Quotation app. You can maintain the
marine surcharges directly in the surcharge rate table.
Related Information
Tariff Management [page 310]
Creating Rate Tables for Marine Tariffs [page 312]
Creating Calculation Sheets for Marine Tariffs [page 314]
Creating Forwarding Agreements for Marine Tariffs [page 316]
Setting up Tariff Quotations from Scratch [page 330]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
311
11.3.1.1 Creating Rate Tables for Marine Tariffs
Create global rate tables for basic ocean freight (OCF) and marine surcharges for your marine tariff.
Prerequisites
•
The charge types of OCF, OCF Total, and marine surcharges have been defined in Customizing
for Transportation Management under
Basic Functions
Charge Calculation
Basic Settings
Define
Charge Types .
•
The charge type OCF has been classified as Ocean Freight Charge, and the marine surcharges are classified
as Surcharge in Customizing for Transportation Management under
Agreement
•
Basic Settings
Pricing
Container Shipping Liners
Lead to
Maintain Charge Type Definition .
The lead to agreement (L2A) rate table type has been defined in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain L2A Rate Table Types .
•
The regulatory filing types have been defined and OCF and Surcharge have been enabled for filing in
Customizing for Transportation Management under
Tariff Filing
Container Shipping Liners
Lead to Agreement
Maintain Regulation Types .
Procedure
1. In your SAP Fiori launchpad, open the Create Rate Table Definition - CSL app.
2. Enter the L2A rate table type and choose Continue.
3. On the General Data tab, enter the rate table header information as follows:
Field
What To Do
Rate Table ID
Enter your rate table ID.
Description
Enter your rate table description.
Charge Usage
Select the charge usage from dropdown list.
Time Zone
Enter the rate table time zone.
Change Type
Enter the charge type.
Value Type
Select the value type as absolute value or percentage
value.
312
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Field
What To Do
Rate Validity Split
Select this checkbox.
4. On the General Data tab, choose Insert Scale to create the scales of the rate table.
For example, you could insert the following scales:
•
•
•
•
•
•
Commodity Code
Source Zone
Destination Zone
Equipment Type
Receipt Mode
Delivery Mode
5. Go to the rate table Regulation tab and choose + (Create) to maintain the regulations that this rate table is
subject to.
For a surcharge rate table, you must maintain the Publish Channel as Rate Line or Rule/Subrule.
6. Go to the Dates and Values tab and choose
Insert
Without Scale Items
to insert the validity period.
7. Enter the valid-from and valid-to dates, description, currency, and rounding profile.
8. On the Dates and Values tab, choose
Set Status
Released
to release the validity period.
9. Save your entries.
Results
The global rate tables for the basic ocean freight rate and marine surcharges are created and released for use.
Related Information
Set Up of Marine Tariffs [page 311]
Creating Calculation Sheets for Marine Tariffs [page 314]
Creating Forwarding Agreements for Marine Tariffs [page 316]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
313
11.3.1.2 Creating Calculation Sheets for Marine Tariffs
Create a global calculation sheet containing basic ocean freight (OCF) charge items and marine surcharges
items for a marine tariff.
Prerequisites
•
The container shipping liner (CSL) calculation sheet type has been defined in Customizing
for Transportation Management under
Container Shipping Liners
Basic Settings
Maintain CSL
Calculation Sheet Types .
•
The lead to agreement (L2A) calculation sheet type has been defined in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain L2A Calculation Sheet Types .
•
The charge types OCF, OCF Total, and OCF-related surcharges have been defined in Customizing
for Transportation Management under
Basic Functions
Charge Calculation
Basic Settings
Define
Charge Types .
•
The basic ocean freight rate table and marine surcharge rate tables have been created.
Procedure
1. In your SAP Fiori launchpad, open the Create Calculation Sheet - CSL app.
2. Enter the L2A calculation sheet type or L2A calculation sheet template, and choose Continue.
3. Go to the General Data tab, and enter the basic data for the calculation sheet as follows:
Field
What To Do
Calculation Sheet ID
Enter your calculation sheet ID.
Description
Enter your calculation sheet description.
Charge Usage
Select the charge usage from the dropdown list.
Time Zone
Enter the time zone.
Regulatory Filing Relevant Flag
Select this checkbox.
4. Go to the Items tab, add charge items, and maintain the following settings:
314
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Item Hierar­
Instruction
chy
Type
Sum
Sum
> Ocean
Standard
Leading
Reference
Calculation
Calculation
Charge Type
Charge Type
Charge Type
Method Type
Method
OCF
X
CSL_CM_RATE
Charges
> Total Ocean
_TYP
Standard
OCF_Total
Freight
X (Refer to
CSL_CM_OCE
OCF)
AN_SUM
Charges
> (Any Marine
Standard
Surcharge)
(Any Marine
CSL_CM_RATE
Surcharge
_TYP
Type)
5. Select the basic ocean freight rate charge item and go to the Classification subtab.
6. Check the Statistical Charge field.
7. In the charge item Rate Table field, assign rate tables to the corresponding charge type.
8. Save your entries.
Results
The global calculation sheet for the marine tariff is created.
Related Information
Transportation Charge Calculation Sheets [page 55]
Set Up of Marine Tariffs [page 311]
Creating Rate Tables for Marine Tariffs [page 312]
Creating Forwarding Agreements for Marine Tariffs [page 316]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
315
11.3.1.3 Creating Forwarding Agreements for Marine Tariffs
Create a forwarding agreement and items for a marine tariff.
Prerequisites
•
The forwarding agreement type for Marine Tariff has been defined in Customizing for Transportation
Management under
Master Data
Agreements and Service Products
Define FWA and Service Product
Catalog Types .
Note that Multiple Parties must be deselected in this Customizing activity.
•
The forwarding agreement type for Marine Tariff has been categorized as Tariff with Revenue in
Customizing for Transportation Management under
Container Shipping Liners
Forwarding Agreement Quotation and Forwarding Agreement
Lead to Agreement
Maintain CSL Forwarding Agreement
Types .
In this Customizing activity, the container shipping liners (CSL) item type MAR must be assigned to the
forwarding agreement with a predefined split profile. In addition, Routing Required must be selected for the
CSL item type MAR and the basic ocean freight charge type.
•
The regulatory filing types have been defined and the OCF and surcharges have been enabled for filing
in Customizing for Transportation Management under
Tariff Filing
•
•
Container Shipping Liners
Lead to Agreement
Maintain Regulation Types .
The global calculation sheet for the marine tariff has been created.
(Optional) The governing tariff has been created.
Procedure
1. In your SAP Fiori launchpad, open the Create Forwarding Agreement - CSL app.
2. Enter the forwarding agreement type and then choose Continue.
3. Go to the General Data tab and enter the following marine tariff header level information:
•
•
•
•
•
•
•
Agreement ID
Description
Time Zone
Valid-From Date
Valid-To Date
Sales Organization
L2A Processing Flag (Select this checkbox.)
4. Go to the Regulation tab and choose Create to maintain the regulations that the marine tariff is subject to.
If the governing tariff is relevant, you need to maintain the governing tariff ID.
5. Go to the Items tab and choose Insert Item to insert new item.
316
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
6. Enter the item type and the CSL item type Marine.
7. In the Calculation Sheet field, assign the global transportation charge calculation sheet (TCCS) created for
the marine tariff to the Marine item.
8. Choose
Set Status
Released
in the tariff header to release the marine tariff.
9. Save your entries.
10. In your SAP Fiori launchpad, open the Maintain Standard Tariff app to maintain the marine tariff with the
sales organization, trade lane, and validity period.
The tariff type is 01-Marine.
Results
The marine tariff is created and released for use.
Related Information
Set Up of Marine Tariffs [page 311]
Creating Rate Tables for Marine Tariffs [page 312]
Creating Calculation Sheets for Marine Tariffs [page 314]
11.3.2 Set Up of Arbitrary Tariffs
An arbitrary tariff contains the transport additional origin (TAO) or transport additional destination (TAD)
charges.
The forwarding agreement of an arbitrary tariff must have the agreement category Tariff with Revenue, and
the container shipping liners (CSL) item type of the forwarding agreement must be set as Arbitrary Origin or
Arbitrary Destination.
You create an arbitrary tariff as follows:
1. Create the global rate tables for the arbitrary tariff.
2. Create the calculation sheet for the arbitrary tariff.
3. Create the forwarding agreement for the arbitrary tariff.
You can also create an arbitrary tariff from an existing template.
The transport additional origin (TAO) and transport additional destination (TAD) rates in an arbitrary tariff need
to be maintained via the Tariff Quotation app.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
317
Related Information
Tariff Management [page 310]
Creating Rate Tables for Arbitrary Tariffs [page 318]
Creating Calculation Sheets for Arbitrary Tariffs [page 320]
Creating Forwarding Agreements for Arbitrary Tariffs [page 322]
Setting up Tariff Quotations from Scratch [page 330]
11.3.2.1 Creating Rate Tables for Arbitrary Tariffs
Create global rate tables for arbitrary origin (TAO) or arbitrary destination (TAD) for your arbitrary tariff.
Prerequisites
•
The charge types for TAO and TAD have been defined in Customizing for Transportation Management
under
•
Basic Functions
Charge Calculation
Basic Settings
Define Charge Types .
The charge types TAO and TAD have been classified as Tailored Transport Additional Origin and
Tailored Transport Additional Destination respectively in Customizing for Transportation Management
under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain Charge Type
Definition .
•
The lead to agreement (L2A) rate table type has been defined in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain L2A Rate Table Types .
•
The regulatory filing types have been defined and Arbitrary has been enabled for filing in Customizing
for Transportation Management under
Container Shipping Liners
Lead to Agreement
Tariff Filing
Maintain Regulation Types .
Procedure
1. In your SAP Fiori launchpad, open the Create Rate Table Definition - CSL app.
2. Enter the L2A rate table type and choose Continue.
3. On the General Data tab, enter the rate table header information as follows:
318
Field
What To Do
Rate Table ID
Enter your rate table ID.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Field
What To Do
Description
Enter your rate table description.
Charge Usage
Select the charge usage from dropdown list.
Time Zone
Enter the rate table time zone.
Change Type
Enter the charge type.
Value Type
Select the value type as absolute value or percentage
value.
Rate Validity Split
Select this checkbox.
4. On the General Data tab, choose Insert Scale to create the scales of the rate table.
For example, you could insert the following scales:
•
•
•
•
•
•
Commodity Code
Source Zone
Destination Zone
Equipment Type
Receipt Mode
Delivery Mode
5. Go to the rate table Regulation tab and choose + (Create) to maintain the regulations that this rate table is
subject to.
6. Go to the Dates and Values tab and choose
Insert
Without Scale Items
to insert the validity period.
7. Enter the valid-from and valid-to dates, description, currency, and rounding profile.
8. On the Dates and Values tab, choose
Set Status
Released
to release the validity period.
9. Save your entries.
Results
The global rate tables for transport additional origin (TAO) or transport additional destination (TAD) are
created and released for use.
Related Information
Set Up of Arbitrary Tariffs [page 317]
Creating Calculation Sheets for Arbitrary Tariffs [page 320]
Creating Forwarding Agreements for Arbitrary Tariffs [page 322]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
319
11.3.2.2 Creating Calculation Sheets for Arbitrary Tariffs
Create a global calculation sheet containing transport additional origin (TAO) or transport additional
destination (TAD) charge items for an arbitrary tariff.
Prerequisites
•
The container shipping liner (CSL) calculation sheet type has been defined in Customizing
for Transportation Management under
Container Shipping Liners
Basic Settings
Maintain CSL
Calculation Sheet Types .
•
The lead to agreement (L2A) calculation sheet type has been defined in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain L2A Calculation Sheet Types .
•
The charge types for transport additional origin (TAO) and transport additional destination (TAD)
have been defined in Customizing for Transportation Management under
Calculation
•
Basic Settings
Basic Functions
Charge
Define Charge Types .
The transport additional origin (TAO) and transport additional destination (TAD) rate tables have been
created.
Procedure
1. In your SAP Fiori launchpad, open the Create Calculation Sheet - CSL app.
2. Enter the L2A calculation sheet type or L2A calculation sheet template, and choose Continue.
3. Go to the General Data tab, and enter the basic data for the calculation sheet as follows:
Field
What To Do
Calculation Sheet ID
Enter your calculation sheet ID.
Description
Enter your calculation sheet description.
Charge Usage
Select the charge usage from the dropdown list.
Time Zone
Enter the time zone.
Regulatory Filing Relevant Flag
Select this checkbox.
4. Go to the Items tab and add the transportation charge calculation sheet (TCCS) items with the following
charge item hierarchy structure:
320
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
For transport additional origin (TAO):
Item Hierar­
Instruction
chy
Type
Sum
Sum
> Origin Arbi­
Standard
Leading
Reference
Calculation
Calculation
Charge Type
Charge Type
Charge Type
Method Type
Method
TAO
X
CSL_CM_RATE
trary Charge
_TYP
For transport additional destimation (TAD):
Item Hierar­
Instruction
chy
Type
Sum
Sum
> Destination
Standard
Leading
Reference
Calculation
Calculation
Charge Type
Charge Type
Charge Type
Method Type
Method
TAD
X
Arbitrary
CSL_CM_RATE
_TYP
Charge
5. In the charge item Rate Table field, assign rate tables to the corresponding charge type.
6. Save your entries.
Results
The global calculation sheet for the arbitrary tariff has been created.
Related Information
Transportation Charge Calculation Sheets [page 55]
Set Up of Arbitrary Tariffs [page 317]
Creating Rate Tables for Arbitrary Tariffs [page 318]
Creating Forwarding Agreements for Arbitrary Tariffs [page 322]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
321
11.3.2.3 Creating Forwarding Agreements for Arbitrary Tariffs
Create a forwarding agreement and items for an arbitrary tariff.
Prerequisites
•
The forwarding agreement type for Arbitrary Tariff has been defined in Customizing for Transportation
Management under
Master Data
Agreements and Service Products
Define FWA and Service Product
Catalog Types .
Note that Multiple Parties must be deselected in this Customizing activity.
•
The forwarding agreement type for Arbitrary Tariff has been categorized as Tariff with Revenue in
Customizing for Transportation Management under
Container Shipping Liners
Forwarding Agreement Quotation and Forwarding Agreement
Lead to Agreement
Maintain CSL Forwarding Agreement
Types .
In this Customizing activity, the container shipping liners (CSL) item types MAO and MAD must be
assigned to the forwarding agreement with a predefined split profile. In addition, the CSL item types MAO
and MAD must be set as routing not required.
•
The regulatory filing types have been defined and Arbitrary has been enabled for filing in Customizing
for Transportation Management under
Container Shipping Liners
Lead to Agreement
Tariff Filing
Maintain Regulation Types .
•
•
The global calculation sheet for the arbitrary tariff has been created.
(Optional) The governing tariff has been created.
Procedure
1. In your SAP Fiori launchpad, open the Create Forwarding Agreement - CSL app.
2. Enter the forwarding agreement type and then choose Continue.
3. Go to the General Data tab and enter the following marine tariff header level information:
•
•
•
•
•
•
•
Agreement ID
Description
Time Zone
Valid-From Date
Valid-To Date
Sales Organization
L2A Processing Flag (Select this checkbox.)
4. Go to the Regulation tab and choose Create to maintain the regulations that the arbitrary tariff is subject to.
If the governing tariff is relevant, you need to maintain the governing tariff ID.
5. Go to the Items tab and choose Insert Item to insert new item.
322
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
6. Enter the item type and the CSL item type MAO or MAD.
7. In the Calculation Sheet field, assign the global transportation charge calculation sheet (TCCS) created for
the arbitrary tariff to the MAO or MAD item.
8. Choose
Set Status
Released
in the tariff header to release the marine tariff.
9. Save your entries.
10. In your SAP Fiori launchpad, open the Maintain Arbitary Tariff app to maintain the arbitrary tariff with the
sales organization, source country, destination country, source zone ID, destination zone ID, and validity
period.
The tariff type is 02-Arbitrary Origin for a TAO tariff or 03-Arbitrary Destination for a TAD tariff.
Results
The arbitrary tariff is created and released for use.
Related Information
Set Up of Arbitrary Tariffs [page 317]
Creating Rate Tables for Arbitrary Tariffs [page 318]
Creating Calculation Sheets for Arbitrary Tariffs [page 320]
11.3.3 Set Up of Inland Tariffs
An inland tariff contains the inland origin or inland destination charges and the linked inland surcharges.
The forwarding agreement for an inland tariff must have the agreement category Tariff with Revenue, and the
container shipping liners (CSL) item type of the forwarding agreement must be set as Inland Origin or Inland
Destination.
You create an inland tariff as follows:
1. Create the global rate tables for the inland tariff.
2. Create the calculation sheet for the inland tariff.
3. Create the forwarding agreement for the inland tariff.
You can also create an inland tariff from an existing template.
The inland origin or inland destination rates in an inland tariff need to be maintained via the Tariff Quotation
app.
The inland surcharges can be directly maintained in the surcharge rate table.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
323
Related Information
Tariff Management [page 310]
Creating Rate Tables for Inland Tariffs [page 324]
Creating Calculation Sheets for Inland Tariffs [page 326]
Creating Forwarding Agreements for Inland Tariffs [page 328]
Setting up Tariff Quotations from Scratch [page 330]
11.3.3.1 Creating Rate Tables for Inland Tariffs
Create global rate tables for inland origin and inland destination and the inland surcharges for your inland tariff.
Prerequisites
•
The charge types for inland origin, inland destination, and inland surcharges have been defined
in Customizing for Transportation Management under
Settings
•
Charge Calculation
Basic
Define Charge Types .
The charge types for inland origin and inland destination have been classified as Base Origin
Inland Charge and Base Destination Inland Charge respectively, and the inland surcharges have been
classified as Surcharge Dest. Inland Charge or Surcharge Origin Inland Charge in Customizing for
Transportation Management under
Pricing
•
Basic Functions
Container Shipping Liners
Lead to Agreement
Basic Settings
Maintain Charge Type Definition .
The lead to agreement (L2A) rate table type has been defined in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain L2A Rate Table Types .
•
The regulatory filing types have been defined and Inland has been enabled for filing in Customizing
for Transportation Management under
Container Shipping Liners
Lead to Agreement
Tariff Filing
Maintain Regulation Types .
Procedure
1. In your SAP Fiori launchpad, open the Create Rate Table Definition - CSL app.
2. Enter the L2A rate table type and choose Continue.
3. On the General Data tab, enter the rate table header information as follows:
324
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Field
What To Do
Rate Table ID
Enter your rate table ID.
Description
Enter your rate table description.
Charge Usage
Select the charge usage from dropdown list.
Time Zone
Enter the rate table time zone.
Change Type
Enter the charge type.
Value Type
Select the value type as absolute value or percentage
value.
Rate Validity Split
Select this checkbox.
4. On the General Data tab, choose Insert Scale to create the scales of the rate table.
For example, you could insert the following scales:
•
•
•
•
•
•
Commodity Code
Source Zone
Destination Zone
Equipment Type
Receipt Mode
Delivery Mode
5. Go to the rate table Regulation tab and choose + (Create) to maintain the regulations that this rate table is
subject to.
For a surcharge rate table, you must also maintain the Publish Channel as Rate Line or Rule/Subrule.
6. Go to the Dates and Values tab and choose
Insert
Without Scale Items
to insert the validity period.
7. Enter the valid-from and valid-to dates, description, currency, and rounding profile.
8. On the Dates and Values tab, choose
Set Status
Released
to release the validity period.
9. Save your entries.
Results
The global rate tables for inland origin or inland destination and inland surcharges are created and released for
use.
Related Information
Set Up of Inland Tariffs [page 323]
Creating Calculation Sheets for Inland Tariffs [page 326]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
325
Creating Forwarding Agreements for Inland Tariffs [page 328]
11.3.3.2 Creating Calculation Sheets for Inland Tariffs
Create the global calculation sheet containing inland origin or inland destination and inland surcharge items for
an inland tariff.
Prerequisites
•
The container shipping liner (CSL) calculation sheet type has been defined in Customizing
for Transportation Management under
Container Shipping Liners
Basic Settings
Maintain CSL
Calculation Sheet Types .
•
The lead to agreement (L2A) calculation sheet type has been defined in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Pricing
Maintain L2A Calculation Sheet Types .
•
The charge types for inland origin, inland destination, and inland surcharges have been defined
in Customizing for Transportation Management under
Settings
•
Basic Functions
Charge Calculation
Basic
Define Charge Types .
The inland origin or inland destination rate tables and the inland surcharge rate tables have been created.
Procedure
1. In your SAP Fiori launchpad, open the Create Calculation Sheet - CSL app.
2. Enter the L2A calculation sheet type or L2A calculation sheet template, and choose Continue.
3. Go to the General Data tab, and enter the basic data for the calculation sheet as follows:
Field
What To Do
Calculation Sheet ID
Enter your calculation sheet ID.
Description
Enter your calculation sheet description.
Charge Usage
Select the charge usage from the dropdown list.
Time Zone
Enter the time zone.
Regulatory Filing Relevant Flag
Select this checkbox.
4. Go to the Items tab, add charge items, and maintain the following settings:
326
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
For inland origin:
Item Hierar­
Instruction
chy
Type
Sum
Sum
> Base Inland
Standard
Leading
Reference
Calculation
Calculation
Charge Type
Charge Type
Charge Type
Method Type
Method
BASE_INL_O
X
CSL_CM_RATE
Origin
> Origin Inland
_TYP
Standard
O_INLAND
Charge
> (Any Origin
Standard
X
CSL_CM_IN­
(BASE_INL_O)
LAND_SUM
(Any Origin In­
CSL_CM_RATE
Inland Sur­
land Surcharge
_TYP
charge)
Type)
For inland destination:
Item Hierar­
Instruction
chy
Type
Sum
Sum
> Base Inland
Standard
Leading
Reference
Calculation
Calculation
Charge Type
Charge Type
Charge Type
Method Type
Method
BASE_INL_D
X
CSL_CM_RATE
Destination
> Dest. Inland
_TYP
Standard
D_INLAND
Charge
> (Any Desti­
Standard
X
CSL_CM_IN­
(BASE_INL_D)
LAND_SUM
(Any Destina­
CSL_CM_RATE
nation Inland
tion Inland Sur­
_TYP
Surcharge)
charge Type)
5. Select the inland origin or inland destination charge item and go to the Classification subtab.
6. Check the Statistical Charge field.
7. In the charge item Rate Table field, assign rate tables to the corresponding charge type.
8. Save your entries.
Results
The global calculation sheet for the inland tariff is created.
Related Information
Transportation Charge Calculation Sheets [page 55]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
327
Set Up of Inland Tariffs [page 323]
Creating Rate Tables for Inland Tariffs [page 324]
Creating Forwarding Agreements for Inland Tariffs [page 328]
11.3.3.3 Creating Forwarding Agreements for Inland Tariffs
Create a forwarding agreement and items for an inland tariff.
Prerequisites
•
The forwarding agreement type for Inland Tariff has been defined in Customizing for Transportation
Management under
Master Data
Agreements and Service Products
Define FWA and Service Product
Catalog Types .
Note that Multiple Parties must be deselected in this Customizing activity.
•
The forwarding agreement type for Inland Tariff has been categorized as Tariff with Revenue in Customizing
for Transportation Management under
Container Shipping Liners
Lead to Agreement
Forwarding
Agreement Quotation and Forwarding Agreement Maintain CSL Forwarding Agreement Types .
In this Customizing activity, the container shipping liners (CSL) item types INLO and INLD must be
assigned to the forwarding agreement with a predefined split profile. In addition, the CSL item types INLO
and INLD must be set as routing not required.
•
The regulatory filing types have been defined and Inland has been enabled for filing in Customizing
for Transportation Management under
Container Shipping Liners
Lead to Agreement
Tariff Filing
Maintain Regulation Types .
•
•
The global calculation sheet for the inland tariff has been created.
(Optional) The governing tariff has been created.
Procedure
1. In your SAP Fiori launchpad, open the Create Forwarding Agreement - CSL app.
2. Enter the forwarding agreement type and then choose Continue.
3. Go to the General Data tab and enter the following marine tariff header level information:
•
•
•
•
•
•
•
328
Agreement ID
Description
Time Zone
Valid-From Date
Valid-To Date
Sales Organization
L2A Processing Flag (Select this checkbox.)
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
4. Go to the Regulation tab and choose Create to maintain the regulations that the marine tariff is subject to.
If the governing tariff is relevant, you need to maintain the governing tariff ID.
5. Go to the Items tab and choose Insert Item to insert new item.
6. Enter the item type and the CSL item type INLO or INLD.
7. In the Calculation Sheet field, assign the global transportation charge calculation sheet (TCCS) created for
the inland tariff to the INLO or INLD item.
8. Choose
Set Status
Released
in the tariff header to release the marine tariff.
9. Save your entries.
10. In your SAP Fiori launchpad, open the Maintain Arbitrary Tariff app to maintain the inland tariff with the
sales organization, source country, destination country, source zone ID, destination zone ID, and validity
period.
The tariff type is 04-Inland Origin for inland transportation charges at the port of origin tariff and 05-Inland
Destination for inland transportation charges at the port of destination tariff.
Results
The inland tariff is created and released for use.
Related Information
Set Up of Inland Tariffs [page 323]
Creating Rate Tables for Inland Tariffs [page 324]
Creating Calculation Sheets for Inland Tariffs [page 326]
11.3.4 Tariff Quotations
A tariff quotation is a forwarding agreement quotation that is used to maintain the leading charge type rate in a
marine tariff, arbitrary tariff, or inland tariff.
Leading charge type rates are not only flat rate lines; there are revenue, route, services, and other extra
information attached to the flat rate line. Therefore, to create a new rate line or update an existing rate line for
a leading charge type in the tariff, you need to go through the processes in a tariff quotation. You need to set up
specific forwarding agreement quotation types for a tariff quotation.
You can create a tariff quotation in the following ways:
•
•
•
From scratch
From a template
From RFQ Translator
You can create or update the marine tariff, arbitrary tariff, and inland tariff in one single tariff quotation, or you
can create multiple tariff quotations individually for each kind of tariff.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
329
You can do the following tasks in the tariff quotation:
•
•
•
•
•
•
•
•
Create request lines
Select a route for a request line
Generate response lines from the targeting tariffs
Perform regulatory filing relevance determination
Build the revenue structure for the leading charge type rate by setting the surcharge conditions of each
charge element
Validate and approve the response lines
Update the tariff and move the response lines into the tariff
Send the response lines as filing requests to the tariff publishing queue
Related Information
Setting up Tariff Quotations from Scratch [page 330]
Setting Up Tariff Quotations from Templates [page 332]
Setting Up Tariff Quotations from RFQ Translator [page 333]
Creating New Tariff Rate Lines from Tariff Quotations [page 334]
Updating Existing Tariff Rate Lines from Tariff Quotations [page 335]
11.3.4.1 Setting up Tariff Quotations from Scratch
Create the tariff quotation manually from scratch.
Prerequisites
•
The forwarding agreement quotation type has been defined for Tariff Quotation in Customizing for
Transportation Management under
Master Data
Agreement RFQs and Quotations
Define Forwarding
Agreement Quotation Types .
In this Customizing activity, the Multiple Parties checkbox must be deselected.
•
The forwarding agreement quotation type of Tariff Quotation has been configured in Customizing
for Transportation Management under
Container Shipping Liners
Agreement Quotation and Forwarding Agreement
Lead to Agreement
Forwarding
Maintain CSL Forwarding Agreement Quotation
Types . In this Customizing activity, the following settings are required for the tariff quotation type:
330
•
Under the CSL Quotation Types node, the Tariff Upd and Det. Filing fields are set as True, and the Send
to Queue field is set as Automatic or Manual.
•
Under the CSL Quotation Types - Item Types node, the item types MAR, INLO, INLD, MAO, and MAD are
maintained and configured. The target agreement type for each item type is maintained as 02-Basic
FWAQ(Dummy).
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
•
Under the CSL Quotation Types - Item Types - Charge Types node, the corresponding charge types are
maintained. The CSL item type MAR is set as routing required and the CSL item types INLO, INLD,
MAO, and MAD are set as routing not required.
Procedure
1. In your SAP Fiori launchpad, open the Create Forwarding Agreement Quotation - CSL app.
2. Enter the forwarding agreement quotation type of tariff quotation and choose Continue.
3. In the tariff quotation screen, enter the required header data.
4. In the tariff quotation item, choose Insert to add an item and select the CSL item type for the item.
5. Select the item and choose Create Calculation Sheet to create calculation sheet.
6. In the Calculation Sheet Overview tab, choose Insert to create a charge item for the leading charge type.
7. Configure the leading charge type item, making sure the calculation method type, calculation method and
the statistical charge are set the same as in your corresponding tariff.
8. Select the leading charge item in the Calculation Sheet Overview tab and choose Add Rate Table to create
rate table.
9. In the rate table screen, enter the required information on the General Data tab.
10. Select the Rate Validity Split, Typed Rate Storage, and L2A Processing Flag checkboxes
11. Enter the scales of the rate table.
12. Go to the Dates and Values tab and create the validity item.
13. Choose Back to return to the tariff quotation main screen and the save your entries.
14. In the tariff quotation item section, select the request item.
15. Choose Create Response Item to create the response item.
16. Save your entries.
Results
You have created a tariff quotation manually.
Related Information
Tariff Quotations [page 329]
Creating New Tariff Rate Lines from Tariff Quotations [page 334]
Updating Existing Tariff Rate Lines from Tariff Quotations [page 335]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
331
11.3.4.2 Setting Up Tariff Quotations from Templates
Create a tariff quotation from an existing forwarding agreement quotation (FWAQ) template.
Prerequisites
The FWAQ template for tariff quotations has been created in the Forwarding Agreement Quotation Template
app.
Procedure
1. In your SAP Fiori launchpad, open the Create Forwarding Agreement Quotation - CSL app.
2. Enter the tariff quotation template and choose Continue.
3. In the Tariff Quotation screen, adjust the fields as required.
4. Save your entries.
Results
You have created a tariff quotation from an existing forwarding agreement template.
Related Information
Forwarding Agreement Quotation Creation [page 182]
Tariff Quotations [page 329]
Creating New Tariff Rate Lines from Tariff Quotations [page 334]
Updating Existing Tariff Rate Lines from Tariff Quotations [page 335]
332
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11.3.4.3 Setting Up Tariff Quotations from RFQ Translator
Create a tariff quotation through the Request for Quotation (RFQ) Translator.
Prerequisites
•
The forwarding agreement quotation type has been defined for Tariff Quotation in Customizing for
Transportation Management under
Master Data
Agreement RFQs and Quotations
Define Forwarding
Agreement Quotation Types .
In this Customizing activity, the Multiple Parties checkbox must be deselected.
•
The forwarding agreement quotation type of Tariff Quotation has been configured in Customizing
for Transportation Management under
Container Shipping Liners
Agreement Quotation and Forwarding Agreement
Lead to Agreement
Forwarding
Maintain CSL Forwarding Agreement Quotation
Types . In this Customizing activity, the following settings are required:
•
Under the CSL Quotation Types node, the Tariff Upd and Det. Filing fields are set as True, and the Send
to Queue field is set as Automatic or Manual.
•
Under the CSL Quotation Types - Item Types node, the item types MAR, INLO, INLD, MAO, and MAD are
maintained and configured. The target agreement type for each item type is maintained as 02-Basic
FWAQ(Dummy).
•
Under the CSL Quotation Types - Item Types - Charge Types node, the corresponding charge types are
maintained. The CSL item type MAR is set as routing required and the CSL item types INLO, INLD,
MAO, and MAD are set as routing not required.
Steps
For step-by-step instructions on creating a tariff through RFQ Translator, see Forwarding Agreement RFQ
Translator [page 183].
Related Information
Forwarding Agreement RFQ Translator [page 183]
Tariff Quotations [page 329]
Creating New Tariff Rate Lines from Tariff Quotations [page 334]
Updating Existing Tariff Rate Lines from Tariff Quotations [page 335]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
333
11.3.4.4 Creating New Tariff Rate Lines from Tariff
Quotations
Create new tariff rate lines for the leading charge type in the tariff quotation and move the rate lines into the
corresponding tariff.
Prerequisites
•
•
•
The marine tariff, inland tariff, or arbitrary tariff has been set up.
The applicable surcharges have been published.
The tariff quotation has been created.
Context
You can follow the tariff quotation processes to create the tariff rate line. As it is a new rate line that does
not exist in the tariff yet, when you get the response for the request line the system returns an empty leading
charge rate and the applicable surcharges. You need to maintain the new rate line and move it to tariff.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the tariff quotation ID and choose Continue.
3. Choose Display Flat View.
4. In the flat view, choose Insert to create request line and enter the scale values and information for the
request line.
5. If the leading charge type is set as routing required, select the request line and choose Search Routes, and
then pick the route from option list.
6. Select the request line and choose Get Responses to create response.
7. Select the response line and choose the Revenue tab.
As the rate line does not exist in the tariff yet, the response line leading charge rate is empty.
8. Select the leading charge element and make an exception.
9. Enter the rate amount, adjust the surcharge item if required, and save your changes.
10. Choose
Response Additional
Validate Response
to validate the response line.
11. Choose Approve to approve the response line.
12. Choose Back to return to the tariff quotation screen and save your entries.
13. Choose Update Tariff to move the new rate line into corresponding tariff.
14. Open the target marine tariff, arbitrary tariff, or inland tariff flat view to check the rate line update.
334
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Results
You have created a new rate line for the leading charge in the tariff quotation and moved it to the marine tariff,
arbitrary tariff, or inland tariff.
Related Information
Tariff Quotations [page 329]
Setting up Tariff Quotations from Scratch [page 330]
Setting Up Tariff Quotations from Templates [page 332]
Setting Up Tariff Quotations from RFQ Translator [page 333]
Updating Existing Tariff Rate Lines from Tariff Quotations [page 335]
11.3.4.5 Updating Existing Tariff Rate Lines from Tariff
Quotations
Update the existing leading charge rate lines in the marine tariff, arbitrary tariff, or inland tariff through the tariff
quotation processes.
Prerequisites
•
•
•
The marine tariff, inland tariff, or arbitrary tariff has been set up.
The applicable surcharges have been published.
The tariff quotation has been created.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the tariff quotation ID and choose Continue.
3. Choose Display Flat View.
4. In the flat view, choose Insert to create a request line and enter the information for the request line.
5. If the leading charge type is set as routing required, select the request line and choose Search Routes, and
then pick the route from option list.
6. Select the request line and choose Get Responses to create response.
7. Select the response line and choose the Revenue tab.
8. Adjust the item charge elements as required (rate amount, surcharge conditions, and so on).
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
335
9. Choose
Response Additional
Validate Response
to validate the response line.
10. Choose Approve to approve the response line.
11. Choose Back to return to the tariff quotation screen and save your entries.
12. Choose Update Tariff to move the response line into corresponding tariff.
13. Open the target marine tariff, arbitrary tariff, or inland tariff flat view to check the rate line update.
Results
You have updated a rate line for the leading charge type in the tariff quotation and moved it to the marine tariff,
arbitrary tariff, or inland tariff.
Related Information
Tariff Quotations [page 329]
Setting up Tariff Quotations from Scratch [page 330]
Setting Up Tariff Quotations from Templates [page 332]
Setting Up Tariff Quotations from RFQ Translator [page 333]
Creating New Tariff Rate Lines from Tariff Quotations [page 334]
11.3.5 Uploading Tariff Rate Lines Through API
Upload rate lines into the tariff rate table through the function module /TMCSL/API_RATE_LINES_UPLOAD.
Prerequisites
The tariff rate tables are created and properly defined.
Context
For tariff rate lines that contain extended information such as revenue node information, filing information, and
so on, it is not possible to directly create the rate lines in the rate table. Nor is it possible to upload the rate lines
through the Microsoft Excel integration, as the template does not include the extended structure. You can use
the following approaches to maintain tariff rate lines with node information:
•
•
336
Tariff Quotation Application (see Tariff Quotations [page 329])
Application programming interface (API) /TMCSL/API_RATE_LINES_UPLOAD
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
The API /TMCSL/API_RATE_LINES_UPLOAD is a technical function module with a defined interface. To
consume the API to create rate lines, you need to prepare the rate line information and feed it to the function
module according to the interface parameters.
Procedure
1. Start transaction SE37.
2. Enter the function module name /TMCSL/API_RATE_LINES_UPLOAD.
3. Choose Execute.
4. Enter the relevant information and choose Execute.
5. Check the rate table.
 Note
You can also create your own program to enter the rate line information.
Related Information
Set Up of Marine Tariffs [page 311]
Set Up of Arbitrary Tariffs [page 317]
Set Up of Inland Tariffs [page 323]
11.4 Customer Quotations
The customer quotation application is used to negotiate a customer agreement with a client.
If the rate line items in the customer agreements (spot quotation and service contract) are relevant for
regulatory filing, then the rate line items need to follow the filing process as well. The procedure to create a
customer quotation follows the lead to agreement designed processes exactly. For more information, see the
Related Information below.
Related Information
Forwarding Agreement Quotations [page 181]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
337
11.5
Determination of Filing Relevance of TLI
The determination of the filing relevance of a tariff line item (TLI) checks if the rate line item is governed by a
specific regulation and needs to be filed or published.
The criteria and logic to determine whether a TLI is filing-relevant needs to be implemented in the Business
Add-In (BAdI) /TMCSL/BADI_FILING_REL_DET. If one TLI is subject to multiple regulations, then the
determination logic must be implemented in the BAdI for the multiple regulations.
Your filing relevance BAdI implementation is triggered by the system in the following scenarios:
•
Marine/Inland Surcharge Rate Tables:
•
•
•
When you manually insert rate lines
When you upload rate lines via MS Excel integration
Forwarding Agreement Quotations:
•
•
When response lines are generated in tariff quotation
When response lines are generated in a customer quotation
The result of the filing relevance determination is stored and displayed on the Filing Information tab of the rate
line item. You can view the Filing Information tab in the forwarding agreement, forwarding agreement quotation,
or rate table when you select the TLI.
The Filing Information tab includes the following fields:
Field
Description
Regulation
The regulations that the rate line item is relevant to.
Approved On
The date that the rate line is approved for the regulation.
Status
The status of the regulation for the rate line item. The possi­
ble values are as follows:
•
•
•
•
Governing Tariff ID
New
Sent to Queue
Approved
Rejected
The governing tariff ID is maintained in the tariff header
Regulation tab for the regulation. The ID is propagated to
the rate lines during the filing relevance determination.
Rule
This field is only applicable for surcharges published via a
rule and sub-rule. It indicates the rule ID in which the sur­
charge is published.
Sub-Rule
This field is only applicable for surcharges published via a
rule and sub-rule. It indicates the sub-rule ID in which the
surcharge is published.
338
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Field
Description
Sub-Rule Version
This field is only applicable for surcharges published via a
rule and sub-rule. It indicates the sub-rule version in which
the surcharge is published.
TLI ID
The unique ID that is generated once the rate line is ap­
proved.
TLI ID generation needs to be implemented via the BAdI /
TMCSL/BADI_RATEID_GENERATION. For more information,
see the Configuration Guide for Regulatory Filing available on
SAP Help Portal at https://help.sap.com/l2a.
Overall Status
The overall filing status of the rate line item. The possible
values are as follows:
•
•
•
•
•
•
New
Sent to Queue
Partially Published
Published
Rejected
Expired
The overall status is decided by the status of each regulation
the TLI is subject to.
Related Information
Tariff Management [page 310]
Customer Quotations [page 337]
Determining Filing Relevance in Tariff Quotations [page 340]
Determining Filing Relevance in Customer Quotations [page 342]
Determining Filing Relevance in Surcharge Rate Tables [page 344]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
339
11.5.1 Determining Filing Relevance in Tariff Quotations
Trigger the filing relevance determination in a tariff quotation when generating the response line for marine,
arbitrary, or inland request lines.
Prerequisites
•
The regulation types have been defined in Customizing for Transportation Management under
Shipping Liners
•
Lead to Agreement
Tariff Filing
Container
Maintain Regulation Types .
The Business Add-In (BAdI) /TMCSL/BADI_FILING_REL_DET has been implemented and activated
with the determination logic for the regulation type in Customizing for Transportation Management
under
Container Shipping Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Tariff Filing
BAdI:
Generic Filing Relevance Determination .
•
The regulation types have been maintained on the Regulation tab of the rate table for the marine, arbitrary,
or inland tariff leading charge type.
•
The regulation types/governing tariff ID (optional) are maintained on the Regulation tab in the marine,
arbitrary, or inland tariff header.
•
The tariff quotation has been created.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the tariff quotation ID and choose Continue.
3. Choose Display Flat View on the forwarding agreement quotation (FWAQ) header or item.
4. In the flat view, choose Insert to create a marine, arbitrary, or inland request line item.
5. For a marine request line, choose Search Routes to pick the correct routes. For arbitrary and inland
requests, a route is not required.
6. Select the request line, and choose
Get Responses
Get Response .
7. Select the generated response line and go to the Filing information tab to check the filing relevance
determination result.
8. (Optional) Check and adjust the surcharge condition or rate amount of the charge elements on the
Revenue tab of the response line.
9. Select the response line and choose
Response Additional
Validate Response .
10. Select the response line and choose Approve.
11. Choose Back and then save your changes.
12. Choose Update Tariff.
340
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Results
•
When the response is generated, the filing relevance of the response line is determined, and the result is
displayed on the Filing Information tab of the response line in the tariff quotation.
The following fields are displayed on the Filing Information tab:
Field
Value
Regulation
The regulation name
Approved On
Blank
Status
New
Governing Tariff ID
The linked governing tariff ID
Rule
Blank
Sub-Rule
Blank
Sub-Rule Version
Blank
TLI ID
Blank
Overall Status
New
•
If the response line is relevant to a single regulation, there is one line on the Filing Information tab. If the
response line is relevant to multiple regulations, there are multiple lines on Filing Information tab. If the
response line is not relevant to any filing regulation, the Filing Information tab is empty.
•
When you update the tariff, the filing relevance determination result is copied from the tariff quotation to
corresponding marine, arbitrary, or inland tariff.
Related Information
Tariff Management [page 310]
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests to Queue [page 346]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
341
11.5.2 Determining Filing Relevance in Customer Quotations
Trigger the filing relevance determination in a customer quotation when generating the response line for
marine, arbitrary, or inland request lines.
Prerequisites
•
The regulation types have been defined in Customizing for Transportation Management under
Shipping Liners
•
Lead to Agreement
Tariff Filing
Container
Maintain Regulation Types .
The Business Add-In (BAdI) /TMCSL/BADI_FILING_REL_DET has been implemented and activated
with the determination logic for the regulation type in Customizing for Transportation Management
under
Container Shipping Liners
Lead to Agreement
Generic Filing Relevance Determination
Business Add-Ins (BAdIs)
Tariff Filing
BAdI:
.
•
The regulations have been maintained on the Regulation tab of the rate table for the marine, arbitrary, or
inland tariff leading charge type.
•
The regulation types and governing tariff ID (optional) have been maintained on the Regulation tab of the
marine, arbitrary, or inland tariff.
•
The customer quotation has been created.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the customer quotation ID and choose Continue.
3. Choose Display Flat View in the customer quotation header or item.
4. In the flat view, choose Insert to create a marine, arbitrary, or inland request line item.
5. For a marine request line, choose Search Routes to pick the correct routes. For arbitrary and inland
requests, a route is not required.
6. Select the request line and choose
Get Responses
Get Response .
7. Select the generated response line and go to the Filing information tab to check the filing relevance
determination result.
8. (Optional) Check and adjust the surcharge condition or rate amount of the charge elements on Revenue
tab of the response line.
9. Select the response line and choose
Response Additional
Validate Response .
10. Select the response line and choose Approve.
11. Choose Back and then save your changes.
12. Choose Get Eligible Agreements.
13. Select the target agreement and choose Set Default Agreement.
14. Choose Create/Update Agreement.
342
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Results
•
When the response is generated, the filing relevance of the response line is determined, and the result is
displayed on Filing Information tab of the response line in the customer quotation.
The following fields are displayed on the Filing Information tab:
Field
Value
Regulation
The regulation name
Approved On
Blank
Status
New
Governing Tariff ID
The linked governing tariff ID
Rule
Blank
Sub-Rule
Blank
Sub-Rule Version
Blank
TLI ID
Blank
Overall Status
New
•
If the response line is relevant to a single regulation, there is one line on the Filing Information tab. If the
response line is relevant to multiple regulations, there are multiple lines on Filing Information tab. If the
response line is not relevant to any regulation filing, the Filing Information tab is empty.
•
When you create or update an agreement, the filing relevance determination result is copied from the
customer quotation to the target customer agreement.
Related Information
Tariff Management [page 310]
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests to Queue [page 346]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
343
11.5.3 Determining Filing Relevance in Surcharge Rate Tables
Trigger the filing relevance determination in a surcharge rate table when creating new surcharge rate lines.
Prerequisites
•
The regulation types have been defined in Customizing for Transportation Management under
Shipping Liners Lead to Agreement Tariff Filing Maintain Regulation Types
for the regulatory filing framework in the Customizing.
•
Container
and surcharge is enabled
The Business Add-In (BAdI) /TMCSL/BADI_FILING_REL_DET has been implemented and activated
with the determination logic for the regulation type in Customizing for Transportation Management
under
Container Shipping Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Tariff Filing
BAdI:
Generic Filing Relevance Determination .
•
•
•
The regulations have been maintained in the surcharge rate table on the Regulation tab.
The surcharge rate table is assigned to a marine tariff or an inland tariff.
The regulations/governing tariff ID (optional) have been maintained on the Regulatory tab in the marine
tariff or inland tariff.
Context
For surcharges, you can directly maintain the rates in the rate table. The filing relevance determination is
triggered when you create new surcharge rate lines in the rate table in the following ways:
•
•
•
You insert a new surcharge rate line.
You upload surcharge rate lines via MS Excel integration.
You copy an existing rate line to create a new surcharge rate line.
Procedure
1. In your SAP Fiori launchpad, open the Edit Rate Table Definition - CSL or Maintain Rate Table - CSL app.
2. Enter the surcharge rate table ID and choose Continue.
3. Insert the new surcharge rate lines using one of the following methods:
•
Insert a new surcharge rate line in the rate table.
1. Go to the Dates and Values tab of rate table and choose Insert to create a new rate line.
2. Enter the scale values, rate, and validity and then then press Enter .
3. Select the newly created rate line and open the Filing information tab to check the filing relevance
determination result.
•
Upload surcharge rate lines from MS Excel.
1. Go to the CSL Excel Integration tab.
344
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
2. In the File Upload section, select the MS Excel file and choose Upload.
3. Go to the Dates and Values tab.
4. Select the uploaded surcharge rate and open the Filing Information tab to check the filing
relevance determination result.
•
Copy an existing rate line.
1. Go to the Dates and Values tab of rate table and choose Search.
2. Select an existing rate line and choose Copy.
3. Modify the copied rate line and then press Enter .
4. Select the newly created rate line and open the Filing information tab to check the filing relevance
determination result.
Results
•
•
When you create a new surcharge rate in the rate table, whether it is created directly, uploaded via MS
Excel, or copied from an existing rate line, the filing relevance determination is triggered. The result is
displayed on the Filing Information tab of the newly created surcharge rate line. The following fields are
displayed on the Filing Information tab:
Field
Value
Regulation
The regulation name
Approved On
Blank
Status
New
Governing Tariff ID
The linked governing tariff ID
Rule
Blank
Sub-Rule
Blank
Sub-Rule Version
Blank
TLI ID
Blank
Overall Status
New
If the surcharge rate is relevant to a single regulation, there is one line on the Filing Information tab. If the
surcharge rate is relevant to multiple regulations, there are multiple lines on the Filing Information tab. If
the surcharge rate is not relevant to any regulation filing, the Filing Information tab is empty.
Related Information
Tariff Management [page 310]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
345
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests to Queue [page 346]
11.6
Sending of Filing Requests to Queue
You can send filing requests from multiple applications to the tariff publishing queue for processing.
Filing requests can be sent from the following applications and processes:
•
Tariff
Tariff Type
Marine
Arbitrary
Inland
•
•
Rates that can be Sent to Tariff Publishing Queue
•
•
Basic ocean freight rate (OCF)
•
•
Arbitrary rate at origin (TAO)
•
•
•
Base inland rate at origin
Marine surcharge rate
Arbitrary rate at destination (TAD)
Base inland rate at destination
Inland surcharge rate
Customer Agreement
Customer Agreement Type
Spot Quotation
Service Contract
Rates that can be Sent to Tariff Publishing Queue
•
•
•
•
•
OCF
•
•
•
•
•
OCF
TAO
TAD
Base inland rate at origin
Base inland rate at destination
TAO
TAD
Base inland rate at origin
Base inland rate at destination
•
Bookings from SAP Transportation Management, order to cash for container shipping liners for SAP S/
4HANA
•
Bookings from a legacy system
For the leading charge type rate (OCF, arbitrary, or inland), filing requests can be sent from the applications
listed above to the queue either automatically or manually.
346
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
For marine surcharges and inland surcharges, filing requests can only be sent manually from the marine tariff
or inland tariff to the queue.
Related Information
Tariff Management [page 310]
Setting up Tariff Quotations from Scratch [page 330]
Customer Quotations [page 337]
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests from Tariffs [page 347]
Sending of Filing Requests from Customer Agreements [page 352]
Sending of Filing Requests from Order to Cash Bookings [page 358]
Sending of Filing Requests from Legacy System Bookings [page 358]
Processing of Filing Requests [page 359]
11.6.1 Sending of Filing Requests from Tariffs
From a marine tariff, arbitrary tariff, and inland tariff, the following types of filing request can be submitted to
the tariff publishing queue:
•
•
•
•
Basic ocean freight rate (OCF)
Arbitrary rate at origin (TAO) and arbitrary rate at destination (TAD)
Base inland rate at origin and base inland rate at destination
Marine surcharges and inland Surcharges
The filing requests can be sent to the queue manually or automatically. If you manually submit the filing
request, you can do it from the marine tariff, arbitrary tariff, or inland tariff flat view, or from the rate tables.
 Note
The filing level of the regulation must be set as TLI Level for the forwarding agreement category Tariff
with Revenue in Customizing for Transportation Management under
Agreement
Tariff Filing
Container Shipping Liners
Lead to
Maintain Filing Levels .
Related Information
Sending of Filing Requests to Queue [page 346]
Sending Filing Requests Manually from the Tariff Flat View [page 348]
Sending Filing Requests Manually from the Tariff Rate Table [page 349]
Sending Filing Requests Automatically from a Tariff Quotation [page 351]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
347
11.6.1.1 Sending Filing Requests Manually from the Tariff Flat
View
Send rate line items to the queue manually from a marine tariff, arbitrary tariff, or inland tariff flat view. This
feature applies to leading charges and surcharges. Afterwards, the filing request can be processed in the
queue.
Prerequisites
•
•
The rate line in the tariff has been determined as relevant for regulatory filing.
For leading charges, the Send to Queue option of the corresponding tariff quotation is set to Manual.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement - CSL app.
2. Enter the marine, arbitrary, or inland tariff ID and choose Continue.
3. Choose Display Flat View in the header toolbar.
4. Choose Search in the flat view.
5. Select the rate line item, and then check the Filing Information tab to verify the rate line is relevant for
regulatory filing.
6. Choose
Miscellaneous
Send to Queue .
Results
The selected rate line is sent to the tariff publishing queue. The filing information for the rate line is updated as
follows:
Field
Description
Request Number
A unique request number is generated for the filing request
Regulation
The regulation name
Approved On
Blank
Status
Changed from New to Sent to Queue
Governing Tariff ID
The linked governing tariff ID
348
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Field
Description
Rule
Blank
Sub-Rule
Blank
Sub-Rule Version
Blank
TLI ID
Blank
Overall Status
Changed from New to Sent to Queue
Related Information
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests from Tariffs [page 347]
Processing of Filing Requests [page 359]
11.6.1.2 Sending Filing Requests Manually from the Tariff
Rate Table
Send rate line items to the queue manually from a marine tariff, arbitrary tariff, or inland tariff rate table.
This feature applies to leading charges and surcharges. Afterwards, the filing request can be processed in the
queue.
Prerequisites
•
•
The rate line in the tariff has been determined as relevant for regulatory filing.
For leading charges, the Send to Queue option of the corresponding tariff quotation is set to Manual.
Procedure
1. In your SAP Fiori launchpad, open the Edit Rate Table Definition - CSL app or the Maintain Rate Table - CSL
app.
2. Enter the rate table ID and choose Continue.
3. Go to the Dates and Values tab and choose Search.
4. Select the rate line items and check the Filing Information tab to verify the rate line is relevant for
regulatory filing.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
349
5. Choose Send to Queue.
Results
The selected rate line is sent to the tariff publishing queue. The filing information for the rate line is updated as
follows:
Field
Description
Request Number
A unique request number is generated for the filing request
Regulation
The regulation name
Approved On
Blank
Status
Changed from New to Sent to Queue
Governing Tariff ID
The linked governing tariff ID
Rule
Blank
Sub-Rule
Blank
Sub-Rule Version
Blank
TLI ID
Blank
Overall Status
Changed from New to Sent to Queue
Related Information
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests from Tariffs [page 347]
Processing of Filing Requests [page 359]
350
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11.6.1.3 Sending Filing Requests Automatically from a Tariff
Quotation
Send rate line items to the queue automatically from a tariff quotation.
Prerequisites
•
•
The rate line in the tariff has been determined as relevant for regulatory filing.
In the tariff quotation, the Send to Queue option is set to Automatic.
Context
If the Send to Queue option is set as Automatic in a tariff quotation, when you choose the Update Tariff button,
the response lines are copied into the tariff. At the same time, the response lines are automatically sent to the
queue for filing. The response lines copied to the tariff cannot be used until they are approved in the queue.
This feature only applies to leading charges. It does not apply to surcharges as surcharge maintenance does
not go through the tariff quotation application.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the tariff quotation ID and choose Continue.
3. Choose Display Flat View in the FWAQ header or item.
4. In the flat view, insert a marine, arbitrary, or inland request line item.
5. For a marine request line, choose Search Routes to pick the correct routes. For arbitrary and inland
requests, a route is not required.
6. Select the request line and choose
Get Responses
Get Response .
7. Select the generated response line and go to the Filing information tab to check the filing relevance
determination result.
8. (Optional) On the Revenue tab of the response line, check and adjust the surcharge condition and rate
amount of the charge elements.
9. Select the response line and choose
Response Additional
Validate Response .
10. Select the response line and choose Approve.
11. Choose Back and then save your changes.
12. Choose Update Tariff.
13. Go to the corresponding tariff and check the changes in the tariff.
14. Open the Tariff Publishing Queue - CSL app, and check the filing request.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
351
Results
When you choose Update Tariff in a tariff quotation, the response lines are copied to the corresponding tariff
and sent to the queue automatically.
In the tariff, you can see the filing information of the copied response line is updated as follows:
Field
Description
Request Number
A unique request number is generated for the filing request
Regulation
The regulation name
Approved On
Blank
Status
Changed from New to Sent to Queue
Governing Tariff ID
The linked governing tariff ID
Rule
Blank
Sub-Rule
Blank
Sub-Rule Version
Blank
TLI ID
Blank
Overall Status
Changed from New to Sent to Queue
Related Information
Setting up Tariff Quotations from Scratch [page 330]
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests from Tariffs [page 347]
Processing of Filing Requests [page 359]
11.6.2 Sending of Filing Requests from Customer
Agreements
In SAP Transportation Management, lead to agreement for container shipping liners for SAP S/4HANA, there
are two kinds of customer agreements: spot quotations and service contracts. Rate line items can be sent to
the queue from spot quotations and service contracts, providing that the rate line items in the spot quotation
and service contract are filing-relevant and the regulation filing level is set as TLI Level.
The following types of filing request can be submitted to the queue from spot quotations and service contracts:
352
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
•
•
•
Basic ocean freight (OCF)
Arbitrary rate at origin (TAO) and arbitrary rate at destination (TAD)
Base inland rate at origin and base inland rate at destination
Surcharge filing requests cannot be submitted from customer agreements.
The filing requests can be sent to the queue manually or automatically from customer agreements. If you
manually send the filing request, you can do it from the agreement flat view or from the rate tables.
 Note
The filing level of the regulation must be set as TLI Level for the forwarding agreement category Quotation
and Service Contract in Customizing for Transportation Management under
Lead to Agreement
Tariff Filing
Container Shipping Liners
Maintain Filing Levels .
11.6.2.1 Sending Filing Requests Manually from Customer
Agreement Flat View
Send rate line items to the queue manually from the customer agreement flat view. This feature applies to
leading charges only. Afterwards, the filing request can be processed in the queue.
Prerequisites
•
The customer agreement has been created, and the rate line in the customer agreement has been
determined as relevant for regulatory filing.
•
In the customer quotation, the Send to Queue option is set to Manual.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement - CSL app.
2. Enter the customer agreement ID and choose Continue.
3. Choose Display Flat View in the header toolbar.
4. Choose Search in the flat view.
5. Select the rate line item and check the Filing Information tab to verify the rate line is relevant for regulatory
filing.
6. Choose
Miscellaneous
Send to Queue .
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
353
Results
The selected rate line is sent to the queue. The filing information of the rate line is updated as follows:
Field
Description
Request Number
A unique request number is generated for the filing request
Regulation
The regulation name
Approved On
Blank
Status
Changed from New to Sent to Queue
Governing Tariff ID
The linked governing tariff ID
Rule
Blank
Sub-Rule
Blank
Sub-Rule Version
Blank
TLI ID
Blank
Overall Status
Changed from New to Sent to Queue
Related Information
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests from Customer Agreements [page 352]
Processing of Filing Requests [page 359]
11.6.2.2 Sending Filing Requests Manually from Customer
Agreement Rate Table
Send rate line items to the queue manually from the customer agreement rate table. This feature applies to
leading charges only. Afterwards, the filing request can be processed in the queue.
Prerequisites
•
354
The customer agreement has been created, and the rate line in the customer agreement has been
determined as relevant for regulatory filing.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
•
In the customer quotation, the Send to Queue option is set to Manual.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement - CSL app.
2. Enter the customer agreement ID and choose Continue.
3. Go to the calculation sheet, select the charge item, and choose Display Rate Table.
4. Go to the Dates and Values tab and choose Search.
5. Select the rate line items and check the Filing Information tab to verify the rate line is relevant for
regulatory filing.
6. Choose Send to Queue.
Results
The selected rate line is sent to the tariff publishing queue. The filing information of the rate line is updated as
follows:
Field
Description
Request Number
A unique request number is generated for the filing request
Regulation
The regulation name
Approved On
Blank
Status
Changed from New to Sent to Queue
Governing Tariff ID
The linked governing tariff ID
Rule
Blank
Sub-Rule
Blank
Sub-Rule Version
Blank
TLI ID
Blank
Overall Status
Changed from New to Sent to Queue
Related Information
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests from Customer Agreements [page 352]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
355
Processing of Filing Requests [page 359]
11.6.2.3 Sending Filing Requests Automatically from
Customer Quotations
Send rate line items to the queue automatically from a customer agreement.
Prerequisites
•
•
The rate line in the customer agreement has been determined as relevant for regulatory filing.
In the customer quotation, the Send to Queue option is set to Automatic.
Context
If the Send to Queue option is set as Automatic in the customer quotation, when you choose Create/Update
Agreement, the response lines in the customer quotation are moved into the customer agreement. At the same
time, the response lines are automatically sent to the queue for filing.
 Note
This feature applies to leading charges only.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation - CSL app.
2. Enter the customer quotation ID and choose Continue.
3. Choose Display Flat View in the FWAQ header or item.
4. In the flat view, insert a marine, arbitrary, or inland request line item.
5. For a marine request line, choose Search Routes to pick the correct routes. For arbitrary and inland
requests, a route is not required.
6. Select the request line and choose
Get Responses
Get Response .
7. Select the generated response line and go to the Filing information tab to check the filing relevance
determination result.
8. (Optional) Check and adjust the surcharge condition and rate amount of the charge elements on the
Revenue tab of the response line.
9. Select the response line and choose
Response Additional
Validate Response .
10. Select the response line and choose Approve.
356
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11. Choose Back and then save your changes.
12. Choose Get Eligible Agreement.
13. Select the target agreement and choose Set Default Agreement.
14. Choose Create/Update Agreement.
15. Go to the corresponding customer agreement and check the changes.
16. Open the Tariff Publishing Queue - CSL app, and check the filing request.
Results
When you choose Create/Update Agreement in a customer quotation, the response lines are moved to the
corresponding customer agreement and are automatically sent to the queue.
In the customer agreement, you can see the filing information of the rate line as follows:
Field
Description
Request Number
A unique request number is generated for the filing request
Regulation
The regulation name
Approved On
Blank
Status
Changed from New to Sent to Queue
Governing Tariff ID
The linked governing tariff ID
Rule
Blank
Sub-Rule
Blank
Sube-Rule Version
Blank
TLI ID
Blank
Overall Status
Changed from New to Sent to Queue
Related Information
Customer Quotations [page 337]
Determination of Filing Relevance of TLI [page 338]
Sending of Filing Requests from Customer Agreements [page 352]
Processing of Filing Requests [page 359]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
357
11.6.3 Sending of Filing Requests from Order to Cash
Bookings
You can send filing requests to the tariff publishing queue from a booking created in SAP Transportation
Management, order to cash for container shipping liners for SAP S/4HANA.
During the charge calculation process in an order to cash booking, the system determines the forwarding
agreement and retrieves the rate lines to calculate the charges. If you want to send the filing relevant tariff line
items (TLIs) from the booking to the tariff publishing queue for approval, you can maintain Post Processing
Framework (PPF) settings to trigger an event to send the filing request from the booking. The PPF is called
when the order to cash booking is saved.
In the PPF settings, you can implement your own criteria and logic to suit your business needs. For example
you can implement the following logic:
1. Check the rate lines of the booking charge calculation.
2. Check whether the rate lines are filing-relevant.
3. Collect all filing-relevant rate lines and send them to the tariff publishing queue. (Queue requests are
created.)
The creation of the PPF settings in booking is a customer implementation task. For more information on how to
maintain the PPF settings, see SAP Note 2990686 .
Related Information
Sending of Filing Requests to Queue [page 346]
11.6.4 Sending of Filing Requests from Legacy System
Bookings
You can send filing requests to the tariff publishing queue from bookings created in your own booking system.
If you use your own IT system to maintain bookings, and you need to send tariff line items (TLIs) from your
bookings to the lead to agreement tariff publishing queue, you can use the remote function call (RFC) /TMCSL/
PUBLISH_EXTERNAL_TLI. Before calling this RFC, you need to collect the booking rate line items to be sent to
the tariff publishing queue in your system. The RFC enables you to create filing requests in the tariff publishing
queue with the required information.
Related Information
Sending of Filing Requests to Queue [page 346]
358
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11.7
Processing of Filing Requests
The regulatory filing framework provides a tariff publishing queue to process filing requests submitted from
tariffs or customer agreements.
The following filing request types can be processed in the tariff publishing queue:
•
•
•
•
Ocean Carrier Freight (OCF)
Arbitrary
Inland
Surcharge
You can process the filing requests in the tariff publishing queue as follows:
•
•
•
•
•
•
•
•
Query filing requests
Display filing request details
Validate filing requests
Get charges and overlaps for filing requests
Get duplicates of filing requests
Request approval of filing requests
Approve filing requests
Reject filing requests
The regulatory filing framework also provides the functionality to automatically process a filing request after it
is sent to the queue.
Related Information
Sending of Filing Requests to Queue [page 346]
Querying Filing Requests [page 360]
Displaying Filing Request Details [page 363]
Validating Filing Requests [page 365]
Getting Charges and Overlaps for Filing Requests [page 366]
Getting Duplicates of Filing Requests [page 368]
Approving Filing Requests [page 370]
Rejecting Filing Requests [page 372]
Processing Filing Requests Automatically [page 374]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
359
11.7.1 Querying Filing Requests
Query the filing requests submitted from tariffs and customer agreements to the tariff publishing queue.
Prerequisites
You have the required authorization to query filing requests (authorization object /TMCSL/QUE).
Procedure
1. In your SAP Fiori launchpad, open the Tariff Publishing Queue - CSL app.
2. In the General search criteria area, enter values for the following criteria:
Search Criteria
Description
Request Type
The possible filing request types are as follows:
•
•
•
•
Regulation
Target Rate Tariff ID
OCF
Arbitrary
Inland
Surcharge
The regulation set up in the system
The ID of the marine tariff, arbitrary tariff, or inland tariff
to which the filing request relates
Request Number
The request number generated when the filing request
was sent to the tariff publishing queue
Life Cycle Status
The possible filing request statuses are as follows:
•
•
•
•
•
•
360
PUBLIC
Sent to Queue
Approved
Error
In Process
Sent for Approval
Rejected
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Search Criteria
Description
Source Agreement Type
The type of agreement that the filing request comes from.
The possible types are as follows:
•
•
•
Source Agreement ID
Tariff
Service Contract
Spot Quotation
The ID of the agreement that the filing request comes
from
Expire Flag
Select this checkbox to search for an expired request
Created By
The ID of the user who submitted the filing request to the
tariff publishing queue
Created On
The date the filing request was submitted to tariff publish­
ing queue
Changed By
The ID of the user who modified the filing request in the
tariff publishing queue
Changed On
The date the filing request was modified in the tariff pub­
lishing queue
3. In the Rate Scales search criteria area, enter values for any of the following criteria:
Search Criteria
Description
Commodity Code
The commodity code of the filing request
Transportation Zone of Source Location
The source transportation zone of the filing request
Transportation Zone of Destination Location
The destination transportation zone of the filing request
Equipment Type
The equipment type of the filing request
Port of Loading
The port of loading of the filing request
Port of Discharge
The port of discharge of the filing request
Receipt Mode
The receipt mode of the filing request
Delivery Mode
The delivery mode of the filing request
Mode of Transport at Origin
The mode of transport at origin of the filing request
Mode of Transport at Destination
The mode of transport at destination of the filing request
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
361
Search Criteria
Description
Shipper-Owned Container
Select this checkbox to search for filing requests relating
to shipper-owned containers
Dangerous Goods
Select this checkbox to search for filing requests relating
to dangerous goods
4. Choose Search.
Results
The filing requests matching the selection criteria are selected and displayed in the Publishing Request List. In
the Publishing Request List, the following columns are fixed:
•
•
•
•
•
•
Request Number
Status
Request Type
Regulation
Target Rate Tariff ID
Source Agreement ID
The filing request scale values are displayed as dynamic columns in the Publishing Request List.
 Example
If the selected filing request has the scales Commodity Code, Transportation Zone of Source Location,
Transportation Zone of Destination Location, and Equipment Type, then these four scales are displayed in
the Publishing Request List.
If the selected filing request has the scales Commodity Code, Transportation Zone of Source Location,
Transportation Zone of Destination Location, Equipment Type, Mode of Transport at Origin, and Mode of
Transport at Destination, then these six scales are displayed in the Publishing Request List.
 Note
•
•
By clicking + or - at the right-hand side of the selection criteria, you can add or delete selection criteria.
• You can save any frequently used search criteria as a variant as follows:
1. Enter the criteria values.
2. Enter a variant name in the Save Search As field.
3. Choose Save and then Save as Private or Save as Global.
4. You can select and apply your saved variants using the Saved Searches dropdown list.
•
362
You can specify a number in the Maximum Number of Results field to restrict the maximum number of
search results.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Related Information
Sending of Filing Requests to Queue [page 346]
Processing of Filing Requests [page 359]
11.7.2 Displaying Filing Request Details
Display the detailed information for a filing request in the tariff publishing queue after querying filing requests.
Prerequisites
You have the required authorization to query and display filing requests (authorization object /TMCSL/QUE).
Procedure
1. In your SAP Fiori launchpad, open the Tariff Publishing Queue - CSL app.
2. Enter your selection criteria and choose Search.
3. Select the filing request in the Publishing Request List and go to the Details tab.
The following information is displayed:
General Information:
Field
Description
Source Agreement ID
The marine, arbitrary, inland tariff ID, or customer agree­
ment ID that the filing request comes from
Request Type Rate Table
The rate table ID the filing request comes from
Target Rate Tariff ID
The marine, arbitrary, inland tariff ID that the filing request
relates to (displayed as a link)
Charge Type
The charge type of the filing request
Governing Tariff ID
The governing tariff ID of the filing request (displayed as a
link) - optional
Created By
The ID of the user who sent the filing request
Created On
The date the filing request was sent to the queue
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
363
Field
Description
Archiving Status
The possible values are as follows:
•
•
Not Archived: the filing request is not archived
Archived: the filing request is archived
Tariff Line Item (TLI) Attributes:
Field
Description
Commodity Code
The commodity code of the selected filing request
Transportation Zone of Source Location
The transportation zone of the source location of the se­
lected filing request
Transportation Zone of Destination Location
The transportation zone of the destination location of the
selected filing request
Equipment Type
The equipment type of the selected filing request
Port of Loading
The port of loading of the selected filing request
Port of Discharge
The port of discharge of the selected filing request
Receipt Mode
The receipt mode of the selected filing request
Delivery Mode
The delivery mode of the selected filing request
Mode of Transport at Origin
The mode of transport at origin of the selected filing re­
quest
Mode of Transport at Destination
The mode of transport at destination of the selected filing
request
Shipper-Owned Container Indicator
The shipper-owned container indicator of the selected filing request
Dangerous Goods Indicator
The dangerous goods indicator of the selected filing re­
quest
4. Select the filing request from the Publishing Request List and go to the Notes tab.
If any text information was submitted for the filing request from the tariff or customer agreement, then it is
displayed on the Notes tab.
Related Information
Querying Filing Requests [page 360]
364
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11.7.3 Validating Filing Requests
Validate a filing request for the tariff publishing queue.
Prerequisites
•
•
You have the authorization to process filing requests.
The check method has been configured in Customizing for Transportation Management under
Shipping Liners Lead to Agreement
Point for Filing Objects node.
Tariff Filing
Maintain Regulation Types
Container
on the Define Check
Context
In the tariff publishing queue, the filing request validation check is triggered in the following scenarios:
•
•
•
When you select a filing request and choose the Check button
When you select a filing request and choose the Approve button
When you select a filing request and choose the Request Approval button
You can maintain the validation logic via the check method according to your business requirements. Creation
of the check method is a customer implementation task. To create the check method, you need to implement
the interface /TMCSL/IF_FILING_CHECK_LOG.
For more information on how to configure the check method, see the Configuration Guide for Regulatory Filing
on the SAP Help Portal at https://help.sap.com/l2a.
Procedure
1. In your SAP Fiori launchpad, open the Tariff Publishing Queue - CSL app.
2. Select a filing request, and then trigger the validation check using one of the following approaches:
•
Choose the Check button.
The system triggers the check method, and you can go to the Check Log tab to view the validation
result.
•
Choose the Approve button.
The system triggers the check method and displays a window to show the validation result of the
selected tariff line item (TLI).
•
Choose the Request Approval button.
The system triggers the check method. You can go to the Check Log tab to view the validation result.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
365
Results
The configured check method is triggered when you choose Check, Approve, or Request Approval for the filing
request in the tariff publishing queue.
The validation result is displayed on the Check Log tab. The presentation of the validation result needs to be
implemented in the check method as part of the implementation scope. If there are any errors identified by the
check method, the life cycle status of the TLI is set to Error. If there are no errors, the life cycle status is set to In
Process. The life cycle status is visible on the Details tab.
The filing request can be approved when the validation check is passed or if there is no validation check. The
validation check cannot be executed again after the filing request is approved, expired, or rejected.
Related Information
Processing of Filing Requests [page 359]
Approving Filing Requests [page 370]
11.7.4 Getting Charges and Overlaps for Filing Requests
Get the charges and overlaps to calculate the total amount of the filing request, and determine the overlap
situations in the targeted tariff. This information helps the queue operator to decide whether to approve or
reject the tariff line item (TLI).
Prerequisites
•
•
You have authorization to process filing requests.
The Business Add-In (BAdI) /TMCSL/BADI_FQ_GET_CHRG_OVLP has been implemented and activated in
Customizing for Transportation Management under
Container Shipping Liners
Lead to Agreement
Business Add-Ins (BAdIs) Tariff Filing BAdI: Getting of Charges & Overlaps in Filing Queue .
The solution provides a default implementation, /TMCSL/BADI_IM_GET_CHRG_OVLP, for BAdI /TMCSL/
BADI_FQ_GET_CHRG_OVLP. For more information see SAP Note 2990686 . If you want to apply
your own specific implementation, you can replace the default implementation with your own BAdI
implementation.
For more information about this BAdI, see the Configuration Guide for Regulatory Filing on the SAP Help
Portal at https://help.sap.com/l2a.
 Note
During the calculation of the filing request, if you want to exclude certain
charge types from the TLI total amount, you can implement the method /SCMTMS/
CL_TCCS_GET=>RESOLVE_CALCULATION_SHEETS of BAdI /TMCSL/BADI_CHARGETO_CALCULATE.
366
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Context
Getting the charges and overlaps for the filing requests provides a calculated view of the filing request and
the overlapped rate line item in the tariff. Using this information, you can identify how the filing request would
change the tariff if it is published.
On the Charges & Overlaps tab, you can see the following information:
•
Original Effective Date and Expiration Date
The original validity dates of the filing request are display only. You cannot change the dates.
•
Modified Effective Date and Expiration Date
Initially, these dates are the same as the original effective date and expiration date. You can change the
dates to make the filing request compliant with the regulatory requirement if there is any. The modified
effective date and expiration date are taken as the final validity period for the rate when it is approved for
filing.
•
Calculation Date
This date is used to calculate the filing request and the overlapped tariff line items (TLIs). When you choose
Get Charges & Overlaps, the system takes the modified effective date as the calculation date. If you change
the modified effective date, you need to calculate the charges again.
•
Charges & Overlaps
This section displays the result when you choose Get Charges & Overlaps. The calculation result of the
filing request is always displayed on the top and highlighted in orange, and the overlapped TLIs in the tariff
are highlighted in green. If there are multiple overlapping TLIs, there are multiple green lines.
For both the filing request and the overlapping TLIs, you can find the scale values, rate amount and
currency, and calculated total amount and currency in the list. For leading charges, the total amount is the
sum of the leading charge and the relevant surcharges. For a surcharge filing request, the total amount and
currency is not relevant because there are no associated other charges.
•
Charge Details
When you select a line from the Charges & Overlaps list, you can see the calculation details in the charge
details section, including the following details:
•
•
•
•
•
•
Charge types
Rate amount and currency
Surcharge conditions
Rate type
Quantity
Calculated amount
You can also see the publishing information such as the governing tariff, TLI ID, or the rule and subrule version
if the surcharge is published via a rule.
As the tariff filing queue does not cover any specific regulation, if you need to introduce extra customized fields
to the Charges & Overlaps tab, you can follow the SAP BOBF enhancement guide to add regulation-specific
fields to the queue.
Procedure
1. In your SAP Fiori launchpad, open the Tariff Publishing Queue - CSL app.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
367
2. Enter your selection criteria to find the relevant filing request.
3. Select the filing request and choose the Get Charges & Overlaps.
4. Open the Charges & Overlaps tab and check the result.
5. Select the filing request (orange color) or overlapped TLIs (green color) and check the Charge Details
section.
6. Change the modified effective date and then choose Get Charges & Overlaps again.
7. Check the result on the Charges & Overlaps tab.
Results
When you choose Get Charges & Overlaps for a filing request, the system calculates the request and
determines the overlapping TLIs. The filing request is marked in orange in the first cell. The overlapped tariff
TLI is marked in green in the first cell. When you select either the filing request line or the tariff TLI, you can see
the details of the calculation result.
When you change the modified effective date of the filing request and choose Get Charges & Overlaps for the
filing request, the system takes the modified effective date as the new date and calculates the request again.
The life cycle status of the filing request is set as In Process once you choose the Get Charges & Overlaps
button.
Related Information
Processing of Filing Requests [page 359]
Approving Filing Requests [page 370]
11.7.5 Getting Duplicates of Filing Requests
Get duplicates to determine if there are any duplicated filing requests in the tariff publishing queue.
Prerequisites
•
•
You have authorization to process filing requests.
The Business Add-In (BAdI) /TMCSL/BADI_FQ_GET_DUPLICATE has been implemented for getting
duplicate requests and the implementation has been activated in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Tariff
Filing BAdI: Getting of Duplicates in Filing Queue .
The soloution provides a default implementation, /TMCSL/BADI_IM_GET_DUPLICATE, for BAdI /TMCSL/
BADI_FQ_GET_DUPLICATE. For more information, see SAP Note 2990686
368
PUBLIC
. If you want to apply
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
your own specific implementation, you can replace the default implementation with your own BAdI
implementation.
For more information about the BAdI, see the Configuration Guide for Regulatory Filing on the SAP Help
Portal at https://help.sap.com/l2a.
Context
The tariff publishing queue is a central collector for filing requests. It can happen that filing requests from
different customer agreements target to update the same tariff line item (TLI). When this happens, it is
important that you can view and understand the duplicate filing requests.
 Note
Duplicate filing requests meet the following criteria:
•
•
•
•
Are yet to be published in the queue
Have the same scale value as your selected filing request
Have valid-from and valid-to dates that overlap with your selected filing request
Target the same tariff rate table as your filing request
Procedure
1. In your SAP Fiori launchpad, open the Tariff Publishing Queue - CSL app.
2. Enter your selection criteria to find the relevant filing request.
3. Select the filing requests and choose the Get Duplicate Requests button.
4. Go to the Duplicates tab and check the result.
Results
The duplicate filing request items are determined and, if there are any, they are displayed on Duplicates tab.
Related Information
Processing of Filing Requests [page 359]
Approving Filing Requests [page 370]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
369
11.7.6 Approving Filing Requests
Approve the filing requests directly in the tariff publishing queue.
Prerequisites
•
•
•
You have authorization to process filing requests (authorization object /TMCSL/QUE).
(Optional) You have checked and validated the filing request before approving it.
The Business Add-In (BAdI) /TMCSL/BADI_FILING_PROCESS is implemented and active in Customizing
for Transportation Management under
Ins (BAdIs)
•
Tariff Filing
Container Shipping Liners
Lead to Agreement
Business Add-
BAdI: Processing of Filing Request .
The BAdI /TMCSL/BADI_FILING_QUE_UPDATE is implemented and active in Customizing for
Transportation Management under
(BAdIs)
Tariff Filing
Container Shipping Liners
Lead to Agreement
Business Add-Ins
BAdI: Enhancement of Filing Queue Update .
The solution provides the following default implementations:
•
•
/TMCSL/BADI_IMP_FILING_PROCESS for the BAdI /TMCSL/BADI_FILING_PROCESS
/TMCSL/BADI_IMP_FIQ_UPDATE for BAdI /TMCSL/BAdI_FILING_QUE_UPDATE
For more information about the logic of the default implementations, see SAP Note 2990686 . If you
want to apply your specific implementations, you can replace the CSL implementations with your own BAdI
implementation.
 Note
If you need to create a tariff line item (TLI) ID for the filing request when approving the request, you can
implement the BAdI /TMCSL/BADI_RATEID_GENERATION. No default implementation is provided for this
BAdI.
If you need to send the filing request to an external system, you can implement the BAdI /TMCSL/
BADI_FILING_SEND_EXTERN. No default implementation is provided for this BAdI.
Procedure
1. In your SAP Fiori launchpad, open the Tariff Publishing Queue - CSL app.
2. In the Search section, enter your selection criteria and choose Search.
3. In the Publishing Request List section, select the filing request and choose Approve.
If check methods exist for the filing request, a dialog box appears to display the check result.
4. Choose Continue in the dialog box.
370
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Results
In the tariff publishing queue, the Filing Information tab of the filing request changes as shown in the following
table. The filing request is display only in the queue and cannot be processed further.
Field
Changes
Overall Status
Changed from Sent to Queue to:
•
Published: If all the regulations of the filing request rate
line are approved.
•
Partially Published: If the filing request rate line is rele­
vant to multiple regulations and other regulations are
yet to be approved.
Approved On
The approved-on date is filled with the system date.
Status of Regulation
Changed from Sent to Queue to Approved.
TLI ID
TLI ID is generated according to the implementation of
BAdI /TMCSL/BADI_RATEID_GENERATION.
If the approved filing request is submitted from a tariff, the following changes occur:
•
•
•
In the tariff, the status of the approved rate line is changed to Available for Rating.
In the tariff, the valid-from and valid-to dates of the approved rate line are equal to the modified effective
date and modified expiration date in the queue.
In the tariff, if the approved rate line overlaps with published TLIs, then the system will truncate the validity
of the published TLIs. You can see the truncation record in the Audit Trail tab.
If the approved filing request is submitted from customer agreement, the following changes occur:
•
•
•
•
•
In the customer agreement, the filing information of the rate line is updated to be the same in the queue.
In the customer agreement, if the overall status of the request is published, the rate line status is changed
to Available for Rating.
In the customer agreement, the valid-from date and valid-to date of the rate line do not change.
In the target tariff, if the overall status of the request is published, the rate line is copied into the tariff rate
table. The status of the rate line is Available for Rating. The valid-from and valid-to dates are equal to the
modified effective date and modified expiration date in the queue.
In the tariff, if the approved rate line overlaps with published TLIs, then the system will truncate the validity
of the published TLIs. You can see the truncation record in the Audit Trail tab.
Related Information
Sending of Filing Requests to Queue [page 346]
Processing of Filing Requests [page 359]
Querying Filing Requests [page 360]
Displaying Filing Request Details [page 363]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
371
Validating Filing Requests [page 365]
Getting Charges and Overlaps for Filing Requests [page 366]
Getting Duplicates of Filing Requests [page 368]
11.7.7 Rejecting Filing Requests
Reject filing requests submitted to the tariff publishing queue.
Prerequisites
•
•
You have authorization to process filing requests (authorization object /TMCSL/QUE).
You have maintained the reason codes and texts for /TMCSL/FQ_REJ in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Basic Settings
Define Reason
Categories and Reason Codes .
•
(Optional) You have checked and validated the filing request before rejecting it.
Procedure
1. In your SAP Fiori launchpad, open the Tariff Publishing Queue - CSL app.
2. In the Search section, enter your selection criteria and choose Search.
3. In the Publishing Request List section, select the filing request and choose Reject.
A dialog box appears asking for the rejection reason.
4. Enter the reason code and remarks and then choose Confirm.
Results
In the tariff publishing queue Filing Information tab, the filing request statuses change as described in the
following table:
Field
Description of Change
Overall Status
Changed from Sent to Queue to Rejected
Status of Regulation
Changed from Sent to Queue to Rejected
When you select the regulation, the rejection reason and remarks are displayed. The filing request is display
only and cannot be processed further in the queue.
372
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
In the source document (tariff or customer agreement) from which the filing request was submitted, the
following changes occur:
•
The rejected rate line is not changed in the source document. The status remains as Only Restrictively
Available for Rating.
•
On the Filing Information tab of the rejected rate line, the overall status and the status of the regulation
change from Sent to Queue to Rejected. When you select the regulation, the rejection reason and remarks
are displayed.
The target marine tariff, arbitrary tariff, or inland tariff is not updated by the rejected request.
Related Information
Sending of Filing Requests to Queue [page 346]
Processing of Filing Requests [page 359]
Querying Filing Requests [page 360]
Displaying Filing Request Details [page 363]
Validating Filing Requests [page 365]
Getting Charges and Overlaps for Filing Requests [page 366]
Getting Duplicates of Filing Requests [page 368]
11.7.8 Requesting Approval for Filing Requests
Send the filing request to the defined party for approval. The approval party can either approve or reject the
filing request.
Prerequisites
•
•
•
You have authorization to process filing requests (authorization object /TMCSL/QUE).
(Optional) You have checked and validated the filing request before approving it.
The Business Add-In (BAdI) /TMCSL/BADI_FQ_REQ_APPROVAL is implemented and active in Customizing
for Transportation Management under
Ins (BAdIs)
•
Tariff Filing
Container Shipping Liners
Lead to Agreement
Business Add-
BAdI: Approval Request for Filing Queue Items .
The approval workflow has been set up.
Procedure
1. In your SAP Fiori launchpad, open the Tariff Publishing Queue - CSL app.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
373
2. In the Search section, enter your selection criteria and choose Search.
3. In the Publishing Request List section, optionally you can check and calculate the filing request, and then
choose Request Approval to send the request to the approval workflow.
Results
If the check method is defined, the system triggers checks on the filing request. If there are any errors, the
filing request cannot be sent for approval. Once the filing request is sent for approval, the life cycle status of the
request is changed to Sent for Approval. The filing request is display-only in the queue.
Once the approval party has approved or rejected the filing request through the workflow, the life cycle status
and overall status of the request is changed to Approved/Rejected.
Related Information
Sending of Filing Requests to Queue [page 346]
Processing of Filing Requests [page 359]
Querying Filing Requests [page 360]
Displaying Filing Request Details [page 363]
Validating Filing Requests [page 365]
Getting Charges and Overlaps for Filing Requests [page 366]
Getting Duplicates of Filing Requests [page 368]
11.7.9 Processing Filing Requests Automatically
Process the filing requests automatically in the tariff publishing queue.
Prerequisites
•
You have enabled automatic processing for the regulation type in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Tariff Filing
Maintain Regulation
Types .
•
374
For the option Auto Request Approval option, the approval workflow is set up.
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Context
To enable the automatic processing, you need to configure it in the Customizing activity Maintain Regulation
Types. You can enable automatic processing for each request type separately.
There are two options for automatic processing of the filing requests:
•
Auto Approval
If this option is enabled, when a filing request arrives in the queue, the system automatically checks,
get duplicates, and gets the charges and overlaps for the filing request. If there is no check error or no
duplicated request in the queue, the filing request is approved automatically. If there are any errors or
duplications, the filing request is not approved, and the queue operator needs to take care of the request
manually.
•
Auto Request Approval
If this option is enabled, when the filing request arrives in the queue, the system automatically checks,
gets duplicates, and gets the charges and overlaps for the filing request. If there is no check error or no
duplicated request in the queue, the filing request is automatically sent to the workflow for approval. If
there are any errors or duplications, the filing request is not sent to the workflow, and the queue operator
needs to take care of the request manually.
For both of these automatic processing options, the system creates an application log for the processing steps.
You can access the application log in transaction SLG1.
Procedure
1. Send a filing request from a marine tariff, arbitrary tariff, inland tariff, or customer agreement.
2. In your SAP Fiori launchpad, open the Tariff Publishing Queue - CSL app.
3. In the Search section, enter your selection criteria and choose Search.
4. In the Publishing Request List section, select and check the filing request status.
5. To view the application log, run transaction SLG1 to access the application log with the object /TMCSL/
PUBLISH and sub-object PUBLISH.
Results
The filing requests are processed automatically after they are sent to the tariff publishing queue. If there are
no errors or duplicated requests, the filing request is automatically approved or sent for approval. If there
are blocking errors or duplications, the request life cycle status is Error or In Process. You can then manually
process the filing request in the queue.
The application log is saved in transaction SLG1 for every automatically processed filing request.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
375
Related Information
Sending of Filing Requests to Queue [page 346]
Validating Filing Requests [page 365]
Getting Charges and Overlaps for Filing Requests [page 366]
Getting Duplicates of Filing Requests [page 368]
Approving Filing Requests [page 370]
11.8
Publishing Surcharges Through Governing Tariff Rules
Publish the marine surcharge or inland surcharge through governing tariff rules or subrules.
Prerequisites
•
You have defined the regulation type and enabled the surcharge filing in Customizing for Transportation
Management under
Container Shipping Liners
Lead to Agreement
Tariff Filing
Maintain Regulation
Types .
•
In the surcharge rate table, you have maintained the regulation and set the publishing channel as Rule/
Subrule.
•
You have published the surcharge in the rule or subrules of your governing tariff.
Context
In addition to publishing the surcharge rate line item directly, you can publish surcharges through the governing
tariff rules or subrules, and link the governing tariff, rule, subrule ID, and version to the rate lines in the
surcharge rate table.
Procedure
1. In your SAP Fiori launchpad, open the Edit Rate Table Definition app.
2. Enter the surcharge rate table ID and choose Continue.
3. Go to the Dates and Values tab and choose Insert to create a surcharge rate line.
4. Select the surcharge rate line and choose Update Rule.
5. In the dialog, enter the regulation, governing tariff ID, rule ID, subrule ID, and version and choose Continue.
376
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Results
The entered governing tariff, rule, subrule, and version are stored on the Filing Information tab of the surcharge
rate line. On the Filing Information tab, the statuses are changed as follows:
•
•
The filing status of the regulation is changed to Approved.
•
The surcharge rate line status changes from Only Restrictively Available for Rating to Available for Rating
after the surcharge is published.
The overall status of the surcharge rate is changed to Published if there is no other regulation open for
filing.
Related Information
Regulatory Filing Framework [page 287]
11.9 Filing at Root Level
Perform the root level filing for a forwarding agreement.
Prerequisites
•
The regulation types have been defined in Customizing for Transportation Management under
Shipping Liners
•
Lead to Agreement
Tariff Filing
Container
Maintain Regulation Types .
You have maintained the filing level as root level for the regulation and agreement category in Customizing
for Transportation Management under
Container Shipping Liners
Lead to Agreement
Tariff Filing
Maintain Filing Levels .
•
You have created and activated the implementation of the Business Add-In (BAdI) /TMCSL/
BADI_FILING_RT_PUBLISH in Customizing for Transportation Management under
Liners
Lead to Agreement
Business Add-Ins (BAdIs)
Tariff Filing
Container Shipping
BAdI: Root Level Publishing .
Context
The regulatory filing framework supports two filing levels: root level and tariff line item (TLI) level. You
can configure root level filing in the Customizing activity Maintain Filing Levels. The filing level is set for a
combination of regulation type and agreement category.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
377
 Note
•
Root level means you need to file the forwarding agreement as a whole object to the authority. Root
level filing does not go through the tariff publishing queue.
•
TLI level filing means you file the individual rate line item. TLI level filing goes through the tariff
publishing queue process.
•
If you do not set the filing level for the regulation type and agreement category, the system uses TLI
level filing by default.
On the Regulation tab of the tariff or customer agreement, you can see the filing level of the
regulation. Root level filing is triggered by selecting the regulation and choosing File. The BAdI /TMCSL/
BADI_FILING_RT_PUBLISH is called. Implementing this BAdI is a customer task. For more information about
this BAdI, see the Configuration Guide for Regulatory Filing on the SAP Help Portal at https://help.sap.com/
tm_csl_l2a_s4hana and SAP Note 2990686 .
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement app.
2. Enter the forwarding agreement ID and choose Continue.
3. On the Regulation tab, select the regulation for which the filing level is root and choose File.
Results
When you select the root level regulation and choose File in the forwarding agreement, the BAdI
implementation of /TMCSL/BADI_FILING_RT_PUBLISH is called and the root level filing logic is executed.
Related Information
Regulatory Filing Framework [page 287]
11.10 Expiration of Published TLIs
You can expire published tariff line items (TLIs) in the following ways:
•
•
From a tariff quotation
From a tariff, as follows:
•
•
378
From the tariff flat view
From the tariff rate tables
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
Related Information
Expiring Published TLIs from Tariff Quotations [page 379]
Expiring Published TLIs from the Tariff Flat View [page 381]
Expiring Published TLIs from the Tariff Rate Table [page 382]
11.10.1 Expiring Published TLIs from Tariff Quotations
Expire a published tariff line item (TLI) in a marine tariff, arbitrary tariff, or inland tariff through the tariff
quotation.
Prerequisites
The TLI to be expired is published.
Context
You can create a request with the operation Delete in a tariff quotation. The deletion request reflects what you
want to expire in the tariff. Then you create a response for the request and update the tariff. The response will
move to the tariff. Meanwhile, an Expiration request is sent to the tariff publishing queue either manually or
automatically. Once the expiration request is approved in the queue, the Delete rate line takes effect in the tariff
and the TLI is expired.
You can expire published ocean carrier freight (OCF), arbitrary, and inland TLIs through the tariff quotation. For
surcharge TLIs, you can perform the expiry from the tariff flat view or rate table.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement Quotation app.
2. Enter the tariff quotation ID and choose Continue.
3. Choose Display Flat View.
4. In the flat view, create a request line to reflect what you want to expire.
5. Select the request line and choose
Request Additional
Set Delete Operation .
6. For a marine request line, select the request and choose Search Routes.
7. Select a route proposal in the dialog and then choose Pick Routes.
For arbitrary and inland requests, a route is not required.
8. Select the request line and choose Get Response to generate response for the deletion request.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
379
9. Select the created response line and choose
Response Additional
Validate Response .
10. Select the response line and choose Approve.
11. Save your entries.
12. Choose Back to exit the flat view and then choose Update Tariff.
13. In your SAP Fiori launchpad, open the Edit Forwarding Agreement app.
14. Enter the tariff ID and choose Continue.
15. Choose Display Flat View.
16. Select the Delete response line from the tariff quotation and choose Send to Queue.
 Note
You can set the Send to Queue option in the tariff quotation as Automatic. The Delete response line will
be automatically sent to the tariff publishing queue when you update the tariff.
17. In your SAP Fiori launchpad, open the Tariff Publishing Queue app.
18. Enter the criteria to search for the expiration request.
19. Select the expiration request and choose Approve.
20.Go back to the tariff in the Edit Forwarding Agreement app.
21. Refresh the flat view and check the update of the expiration TLI.
Results
You have created a request with the operation Delete in a tariff quotation and updated it to the tariff. You have
sent an expiration request to the tariff publishing queue and approved it.
The approved expiration TLI becomes active and the rate line is flagged as Deleted in the tariff. If the expired
TLI needs to truncate the validity of the other published TLIs in the tariff, the valid-from date and valid-to date
of the published TLIs are updated.
Related Information
Expiration of Published TLIs [page 378]
Expiring Published TLIs from the Tariff Flat View [page 381]
Expiring Published TLIs from the Tariff Rate Table [page 382]
380
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
11.10.2 Expiring Published TLIs from the Tariff Flat View
Expire the published tariff line items (TLIs) in a marine tariff, arbitrary tariff or inland tariff from the tariff flat
view.
Prerequisites
The TLI to be expired has been published.
Context
You can directly expire the published marine, arbitrary, inland, or surcharge tariff line items (TLIs) from the
tariff flat view. When you expire a published TLI, an expiration request is sent to the tariff publishing queue.
When the expiration request is approved in the queue, the expiration takes effect and the published TLI is
expired.
Procedure
1. In your SAP Fiori launchpad, open the Edit Forwarding Agreement app.
2. Enter the tariff ID and choose Continue.
3. Choose Display Flat View.
4. In the flat view, select the published TLI that you want to expire.
5. Choose
Miscellaneous
Expire .
6. In the dialog box, enter the expire valid-from date and expire valid-to date and choose Continue
.
A TLI expiration request is created and sent to the queue.
7. In your SAP Fiori launchpad, open the Tariff Publishing Queue app.
8. Enter the criteria to search for the expiration request.
9. Select the expiration request and choose Approve.
10. Go back to the tariff in the Edit Forwarding Agreement app.
11. Refresh the flat view and check the update of the expired TLI.
Results
You have sent an expiration request from the tariff flat view to the tariff publishing queue and approve it. The
approved expiration TLI becomes active and the rate line is flagged as Deleted in the tariff.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
381
If the expired TLI needs to truncate the validity of the other published TLIs in the tariff, the valid-from date and
valid-to date of the published TLIs are updated.
Related Information
Expiration of Published TLIs [page 378]
Expiring Published TLIs from Tariff Quotations [page 379]
Expiring Published TLIs from the Tariff Rate Table [page 382]
11.10.3 Expiring Published TLIs from the Tariff Rate Table
Expire the published tariff line items (TLIs) in a marine tariff, arbitrary tariff, or inland tariff from the tariff rate
table.
Prerequisites
The TLI to be expired has been published.
Context
You can directly expire the published marine, arbitrary, inland, or surcharge TLIs from the tariff rate table. When
you expire a published TLI, an expiration request is sent to the tariff publishing queue. When the expiration
request is approved in the queue, the expiration takes effect and the published TLI is expired.
Procedure
1. In your SAP Fiori launchpad, open the Edit Rate Table Definition app.
2. Enter the tariff rate table ID and choose Continue.
3. Go to the Dates and Values tab and choose Search.
4. Select the target published TLI and choose Expire.
5. In the dialog box, enter the expire valid-from date and expire valid-to date and choose Continue.
6. In your SAP Fiori launchpad, open the Tariff Publishing Queue app.
7. Enter the criteria to search for the expiration request.
8. Select the expiration request and choose Approve.
9. Go back to the rate table in the Edit Rate Table Definition app.
382
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
10. Refresh the rate table and check the update of the expired TLI.
Results
You have sent an expiration request from the tariff rate table to the tariff publishing queue and approve it. The
approved expiration TLI becomes active and the rate line is flagged as Deleted in the tariff rate table.
If the expired TLI needs to truncate the validity of the other published TLIs in the tariff, the valid-from date and
valid-to date of the published TLI are updated.
Related Information
Expiration of Published TLIs [page 378]
Expiring Published TLIs from Tariff Quotations [page 379]
Expiring Published TLIs from the Tariff Flat View [page 381]
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Regulatory Filing Framework
PUBLIC
383
12
Glossary
The terms for SAP Transportation Management, lead to agreement for container shipping liners for SAP S/
4HANA are available on the SAP Help Portal.
Description
Component
Where To Find The Terms
Base terms common to all the Trans­
portation Management add-ons for
container shipping liners
TM-ADP-CSL
https://help.sap.com/glossary/?
search=TM-ADP-CSL
Terms relating to the lead to agreement
process for container shipping liners
TM-ADP-CSL-L2A
https://help.sap.com/glossary/?
search=TM-ADP-CSL-L2A
384
PUBLIC
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Glossary
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 an 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.
SAP Transportation Management, Lead to Agreement for Container Shipping Liners for SAP
S/4HANA
Important Disclaimers and Legal Information
PUBLIC
385
www.sap.com/contactsap
© 2023 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