SAP Transportation Management, Order to Cash for … · order-to-cash process for container...

Application Help PUBLIC

Document Version: 2.0 – 2017-06-30

SAP Transportation Management, Order to Cash for Container Shipping Liners

Content

1 Introduction to Order to Cash. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Commodity Master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Creating a Commodity Master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Harmonized Tariff Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12UN Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Adding Commodity Long Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Adding Attachments to Commodities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Commodity Output Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Commodity Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.2 Manifest Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Creating Manifest Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Changing Manifest Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Manifest Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Change Documents for Manifest Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

2.3 Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Tabs in Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Brand-Specific Data in Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Approval-Relevant Fields in Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Creating Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Changing Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Copying Partner and Location Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Deactivating Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Reactivating Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Deleting Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Performing Mass Update of Partner Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Uploading Data to PLP Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Uploading Mass Data to Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62POWL for Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63APIs for Partner and Location Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

2.4 Product Catalog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Creation of Service Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Mass Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Service Product Worklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

3 Basic Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

2 P U B L I CSAP Transportation Management, Order to Cash for Container Shipping Liners

Content

3.1 Generic Validation Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Rules Based on SAP Transportation Management Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . 90Rules Based on Business Rules Framework plus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Rules Based on Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Rules Based on RFC-Enabled Function Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

3.2 Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Introduction to Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Routing for Product Catalog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Routing for Booking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

3.3 Archiving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Why Archive?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Prerequisites for Archiving. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Archiving for Master Data Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Archiving for Business Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129ILM Objects for Business Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

3.4 Blocking and Deletion of Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Customizing Settings for Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137End of Purpose Framework. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140End of Purpose Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Handling of Blocked Business Partners and Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148End of Business Condition for Order to Cash Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

3.5 Change Tracking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1493.6 Blocking and Deletion of Location Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

Blocking Location Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Unblocking Location Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Displaying Stored Application Logs for Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

3.7 Collection and Reporting of Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Running the Personal Data Collection Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Enhancement Options for Personal Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

4 Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1614.1 Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161

Booking Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Creation of Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Booking Life Cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Booking Statuses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Mixed Cargo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179Break Bulk Cargo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Additional Over Dimensional Cargo Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Roll-On Roll-Off Cargo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182Side Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Flat Rack Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

SAP Transportation Management, Order to Cash for Container Shipping LinersContent P U B L I C 3

Booking Consolidation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Split Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Approval Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Booking Confirmation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Booking Cancellation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Detention in Transit Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Diversion Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Invoicing for Partner Cargo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Booking Worklists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216No-Show and Late Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Inland Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Less Than Container Load Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Discarding Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

4.2 Route Proposal Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231Integration with Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Integration with Allocation Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Validating Routes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Process After Acceptance of Route Proposals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234

4.3 Ordered Route Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Standalone Approach. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234Accepting Route Proposals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Automated Route Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Resolving Multiple Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236Skipping of Ordered Route Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

4.4 Equipment Availability Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237Integration with Transportation Resource Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Initial Depot Determination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Depot Determination for Given Container Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Alternative Equipment Proposals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Running the Equipment Availability Check Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Equipment Availability Check for Early Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

4.5 Part-Load Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244Creating Part-Load Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245Creating Part-Load Bookings Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Deleting Part-Load Bookings from Equipment Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Part-Load Booking Cancellation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Consistency Checks for Part-Load Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250Ordered and Actual Route Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Part-Load and Equipment Bookings Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252Part-Load Numbering Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Split Part-Load Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254


Content

Short Shipments in Part-Load Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Disabling of Route Selection and Status Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Inland Bookings for Part-Load Shipments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258Prohibition of Bill of Lading Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Charge Type Levels for Part-Load Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Charge Type Checks When Converting FCL Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

5 Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2615.1 Shipping Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Datatized Shipping Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Non-Datatized Shipping Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Shipping Instruction Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Processing Shipping Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263Shipping Instruction Classes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265Shipping Instruction Worklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Reassigning Shipping Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Canceling Shipping Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

5.2 Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Creation of Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Draft Bill of Lading Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Deposit Statuses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Financial Status and Credit Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Quality Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Operational Statuses in Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294Gate-In Reconciliation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Customer Customs Clearance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298Release of Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302Surrender Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306Cargo Release Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .309Transshipment PINs for Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Bill of Lading Split. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312Merging Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Short Shipments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Hitchment Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319Memo Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320House Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323Canceling Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325Reactivating Canceled Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326Bill of Lading Clauses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

5.3 Manifest. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330Creation of Manifests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Manifest Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333


Determination of Business Partners and Profiles for Manifests. . . . . . . . . . . . . . . . . . . . . . . . . 335Additional Location Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337Manifest Document Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .339Manifest Document Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Manifest Document Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Manifest Document Submission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342Bookings and Bills of Lading in Manifest Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342Manifest Document Tracking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345Manifest Responses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346Assignment of Booking to Manifest. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348Manifest Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

5.4 Delivery Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349Creation of Delivery Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .350Mass Creation of Delivery Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .357Creating Delivery Orders for Part-Load Bills of Lading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357Canceling Delivery Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .358Voiding Delivery Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359Delivery Order Statuses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360Delivery Order Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363Issuing of Delivery Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

5.5 Release Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Release Order Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366Determination of Release Order Amendment or Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . .366Validation of Empty Provisioning Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Creating Release Orders at Booking Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368Creating Release Orders at TU Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Release Order Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370Release Order Cancellation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373Release Order Expiration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373Issuing Release Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375Creation of Release Orders for Merged Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376Creation of Release Orders for Split Bookings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377Release Orders for Carrier Haulage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378Using the Release Order Worklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Keep Determined Depot Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

6 Invoice Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3826.1 Charge Element Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Settlement Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383Place of Payment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384Bill-To Party. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385Responsible Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386


Content

Invoice Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388Requested Invoice Amount. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Invoiced Invoice Amount. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390Payment Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390

6.2 Forwarding Settlement Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391Creating Final Invoice Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392Creating Proforma Invoice Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

6.3 Negative Forwarding Settlement Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394Creating a Negative Forwarding Settlement Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394

6.4 Part-Load Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395


1 Introduction to Order to Cash

The SAP Transportation Management, order to cash for container shipping liners application is an SAP Transportation Management (SAP TM) add-on that allows you to perform all activities connected with the order-to-cash process for container shipping liners.

Integration

SAP Transportation Management, order to cash for container shipping liners can be seamlessly integrated in SAP TM and with other container shipping liner applications.

Features

SAP Transportation Management, order to cash for container shipping liners delivers business capabilities and supports business processes, for example, to:

● Improve the booking process, including the use of templates● Facilitate the integration of route and voyage suggestions● Improve handling of prohibitions and restrictions● Initiate availability checks on equipment and allocations● Facilitate the handling, receiving, and comparing of shipping instructions (SIs) and (house) bills of lading

(B/Ls)● Support invoice and pro forma invoice requests● Enable creation and management of (advanced) manifests● Provide localization based on customer and country profiles

Related Information

For more information about standard SAP TM functionality, see SAP Library for your SAP Transportation Management release on SAP Help Portal at https://help.sap.com/transportationmanagement.

For more information about lead to agreement, see SAP Library for your SAP Transportation Management, lead to agreement for container shipping liners release on SAP Help Portal at https://help.sap.com/tm_csl_l2a, under Application Help.

For more information about network and operations, see SAP Library for your SAP Transportation Management, network and operations for container shipping liners release on SAP Help Portal at https://help.sap.com/tm_csl_nao, under Application Help.

Master Data [page 10]


Introduction to Order to Cash

https://help.sap.com/transportationmanagement

https://help.sap.com/tm_csl_l2a

https://help.sap.com/tm_csl_nao

https://help.sap.com/tm_csl_nao

Basic Settings [page 89]

Bookings [page 161]

Documentation [page 261]

Invoice Preparation [page 382]

SAP Transportation Management, Order to Cash for Container Shipping LinersIntroduction to Order to Cash P U B L I C 9

2 Master Data

Master data represents the business objects used in applications to support transactional processes and operations.

In addition to the standard SAP Transportation Management (SAP TM) master data objects, the following objects are part of the SAP Transportation Management, order to cash for container shipping liners application:

● Commodity master● Manifest profiles● Partner and location profiles● Product catalog

Related Information

Commodity Master [page 10]

Manifest Profiles [page 19]

Partner and Location Profiles [page 51]

Product Catalog [page 63]

For more information about the master data objects in SAP Transportation Management, see SAP Library for your SAP Transportation Management release on SAP Help Portal at https://help.sap.com/transportationmanagement. Under Application Help, open SAP Library and choose SAP Transportation Management (SAP TM) Master Data .

2.1 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 SAP Transportation Management, 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.


Master Data



Related Information

Creating a Commodity Master [page 11]

2.1.1 Creating a Commodity Master

Create a commodity master for cargo that is to be moved on behalf of customers.

Prerequisites

● The number range object /TMCSL/CMD has been defined in standard transaction SNRO.● The commodity code types have been defined in Customizing for SAP Transportation Management under

Transportation Management Master Data Classification of Goods Define Commodity Codes .● Configurable constants have been defined for the Commodity Code Pattern (COMD_CODE_PATTERN) and

Commodity Code Type (COMMODITY_CODE_TYPE) in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Maintain Configurable Constants .

● You have carried out the following Customizing activities in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Commodity Master :○ Define Commodity Types○ Define Cargo Types○ Define IMO Class○ Define Industry Code

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Commodity Create Commodity Master .2. In the General Data section, enter the following commodity code details:

Field What To Do

Commodity Code If an external number range is defined for the commodity master, enter a unique commodity code that matches the configurable constant for the commodity code pattern.

Description Enter a description for the commodity code.

Commodity Type ID Select the commodity type.

Cargo Type ID Select the cargo type.

SAP Transportation Management, Order to Cash for Container Shipping LinersMaster Data P U B L I C 11

Field What To Do

IMO Class Select the IMO class. This field is mandatory if the commodity 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]

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

Assigning HTS Codes to Commodities [page 14]


Master Data

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 SAP NetWeaver Business Client, choose Master Data Commodity Maintain HTS Data Upload .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.

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

HTS codes have been uploaded to the system under Master Data Commodity HTS Data Upload .

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Commodity Change Commodity Master , 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 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


Master Data

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 15]

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


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.

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 Processes and Tools for Enterprise Applications Reusable Objects and Functions for BOPF Environment Dependent Object Text Collection 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


2. Go to the Long Description tab and choose Insert.3. Select the text type and language.4. Enter your content.5. Specify the validity6. Save your description.

Results

The long description is saved in the commodity master.

Related Information

Adding Commodity Long Descriptions [page 16]


Master Data

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


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.

Next Steps

NoteYou 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 SAP TM functionality for output management, see SAP Library for your SAP Transportation Management release on SAP Help Portal at https://help.sap.com/transportationmanagement. Under Application Help, open SAP Library and choose SAP Transportation Management (SAP TM) Basic Settings or search for Output Management.

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]

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 SAP Transportation Management under Container Shipping Liners Basic Settings Commodity Master Maintain Hierarchy Header .


Master Data



Procedure

1. In SAP NetWeaver Business Client, choose Master Data Commodity Maintain Commodity Hierarchy .

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 Displays the details for the selected commodity

Move 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.

Related Information

Commodity Hierarchy [page 18]

2.2 Manifest Profiles

Customs, port, border, and other authorities of all countries across the globe have different regulatory requirements for cargo entering their country, leaving their country, and moving within their territory. To


address these requirements, manifest profiles can be used to store manifest documents and document criteria required for a particular business partner at a particular location.

Related Information

Creating Manifest Profiles [page 20]

2.2.1 Creating Manifest Profiles

Create a manifest profile for a particular business partner (BP) at a particular location.

Prerequisites

● The BP roles and groupings have been defined for manifests in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation ManifestDefine BP Roles and Define BP Groupings .

● The BP role grouping has been assigned to the manifest in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Manifest

Maintain Manifest Settings .

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Manifest Profile Create Manifest Profile .2. In the Profile Definition section, enter the following profile header details:

Field What to Do

Profile ID Enter a unique ID for the manifest profile. You can view existing IDs in the input help (F4).

Description Enter a description for the manifest profile.

Language Select the default language of the documents in the manifest profile. This can be used, for example, to retrieve the description of the translatable element if this element is not mentioned in the key elements, or for printing the PDF form in the correct language.

UOM Select the default unit system for the manifest profile. Possible values are Metric and Imperial. The mapping between different metric and imperial units is defined in the Customizing activity Maintain Manifest Settings.


Master Data

Field What to Do

Validity From Enter the start validity date of the manifest profile.

Validity To Enter the end validity date of the manifest profile.

Type Select the type of manifest profile. This indicates the business partner (BP) role to which the profile can be assigned. This setting is checked when the profile is assigned to the particular business partner (in other words, the business partner must have this role).

Country Select the country of the manifest profile; this value is used for classification of the profiles.

3. Save your entry.

Results

You have created the manifest profile.

Related Information

Changing Manifest Profiles [page 21]Manifest Documents [page 22]Creating Manifest Documents [page 22]

2.2.2 Changing Manifest Profiles

Change an existing manifest profile to update the data within this profile.

Prerequisites

The manifest profile that you want to change exists in the system.

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Manifest Profile Change Manifest Profile .2. Specify the profile ID of the manifest profile you want to change and then choose Continue.3. Make your required changes and save.


Results

You have updated the manifest profile with your changes.

Related Information

Manifest Profiles [page 19]

2.2.3 Manifest Documents

A manifest document lists in detail all of the bills of lading issued by the carrier or agents for a particular voyage. The list of bills of lading to be included in a particular document may differ based on the manifest purpose and local requirements.

You can define the possible types of a manifest document in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Manifest Maintain Manifest Settings .

Related Information

Creating Manifest Documents [page 22]Deleting Manifest Documents [page 26]Reactivating Manifest Documents [page 27]

2.2.3.1 Creating Manifest Documents

Create one or more manifest documents within a manifest profile, depending on the requirements for a particular port.

Prerequisites

● The header data in the manifest profile has been defined.


Master Data

● In Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Manifest Maintain Manifest Settings , the following settings have been defined:○ Document ID number range interval and assignment to the manifest○ Document types○ Communication methods○ EDI formats○ Customs event reference classes if required (for example, ABAP class with interface /TMCSL/

IF_MANPRF_SUBREF)○ Event references

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Manifest Profile Change Manifest Profile , and then open the relevant manifest profile.

2. On the Profile Documents tab, choose Create.3. In the General section, enter the following details:

Field Meaning

Document ID The ID is automatically assigned upon saving the manifest profile, based on the predefined number range. Manual input is disabled for this field.

Document Name Enter a name for the manifest document.

Document Type Select the relevant document type.

Event Reference Select the corresponding event reference.

Reference Validity Select either ETD (expected time of departure) or ETA (expected time of arrival) as the basis for checking the document’s validity.

Valid-From Date Enter the date from which the document is valid for inclusion in the manifest ocean freight bookings.

Valid-To Date Enter a date until which the document is valid for inclusion in the manifest ocean freight bookings.

Status Select the status of the document. The following values are possible:○ Draft: The document description is incomplete and

the document cannot be used in the manifest.○ Final: The document is complete and will be included

in the manifest ocean bookings.

In Use This read-only field indicates if the document is already used in a manifest ocean booking.


Field Meaning

Load Relevant This read-only checkbox indicates whether a Load or Do Not Load response is expected for the selected document type.

Discharge Relevant This read-only checkbox indicates whether a Discharge or Do Not Discharge response is expected for the selected document type.

Release Relevant This read-only checkbox indicates whether a Release or Do Not Release response is expected for the selected document type.

Communication Method Select the communication method.

Communication Format Select the unified message format that is the most suitable for submission of this document. The following formats are available:○ Full B/L (Without Charges) and VV Information○ VV Information Only○ B/L Information Only (With Charges)○ Full B/L (With Charges) and VV Information○ B/L Information Only (Without Charges)

NoteThis selection affects performance because all of the listed information is selected for each bill of lading (B/L) included in the submission. For this reason, always select the minimum set of information required. For example, if charges are not relevant for this document, then select a format without charges.

Layout Select the print layout of the document if this document needs to be printed.

NoteThe selection is limited to all PDF forms created in the system with the PDF interface indicated in the Customizing activity Maintain Manifest Settings.

EDI Format Select the EDI format.

Amendment Type Select the amendment type. This setting specifies whether all or individual bookings or bills of lading on a manifest document are to be resubmitted if amendments are required. Mass amendment leads to complete document resubmission, whereas individual leads to resubmission of the amended B/Ls only.

Include Short-Shipped Container Select whether you want to include containers marked as short-shipped in the submission.

4. Save your document by saving the manifest profile.


Master Data

Results

You have created a manifest document in the manifest profile.

Related Information

Changing Manifest Documents [page 25]Deleting Manifest Documents [page 26]Reactivating Manifest Documents [page 27]Reference Validity [page 28]Event Reference [page 27]

2.2.3.2 Changing Manifest Documents

Change a manifest document within a manifest profile to update the settings for this manifest document.

Prerequisites

The manifest document you want to change exists in the manifest profile.

Procedure


2. Under Profile Documents, select the manifest document you want to change and then make your changes.3. Save your document by saving the manifest profile.

Results

You have changed the relevant manifest document in the manifest profile.

Related Information

Manifest Documents [page 22]


Deleting Manifest Documents [page 26]Reactivating Manifest Documents [page 27]

2.2.3.3 Deleting Manifest Documents

Delete a manifest document in the manifest profile if it is no longer needed or was created by mistake.

Context

If the document has not yet been used, it is permanently deleted from the manifest profile, otherwise it is only deactivated. The usage of the document in manifest ocean bookings is adjusted in the background. In addition to this, any incomplete documents are also marked as deactivated.

Procedure


2. Under Profile Documents, select the document you want to delete3. Choose Delete.4. Save the manifest profile to ensure that your changes are saved.

Results

The document is deleted or deactivated as appropriate.

Related Information

Reactivating Manifest Documents [page 27]


Master Data

2.2.3.4 Reactivating Manifest Documents

Reactivate a deactivated manifest document, for example, if it was deactivated by mistake.

Procedure


2. Under Profile Documents, select the document you want to reactivate.3. Choose Reactivate.4. Save the manifest profile to ensure that your changes are saved.

Results

The document is reactivated. The usage of the document in manifest ocean bookings is adjusted in the background (incomplete documents are activated and may be used for activities).

Related Information

Deleting Manifest Documents [page 26]

2.2.3.5 Event Reference

An event reference defines the number of document instances that are generated in the manifest object for a particular profile document.

The following event references are available:

● Current Port: Only one document instance is generated, whereby the time of activities (such as submissions) is calculated based on arrival or departure to or from the current port.

● Last Load Port: The number of document instances that are generated corresponds to the number of ports defined for the vessel prior to the current port until the port with the same customs union.

● First Port of Entry: The number of document instances that are generated corresponds to the number of first ports of entry defined for the vessel prior to the current port.

ExampleConsider the vessel route NLRTM (EU) – MAPTM – DZDJE – FRMRS (EU), where FRMRS and NLRTM belong to the same customs union; and you are creating manifest documents in the manifest profile for FRMRS.


For documents within FRMRS for which Current port is selected as the event reference, only one instance is generated. The activities time is calculated based on FRMRS estimated time of arrival (ETA) and estimated time of departure (ETD). This seems appropriate for the Import/Export declaration for FRMRS.

For documents having First Port of Entry as the selected event reference, two instances are generated. For the first instance, activities are calculated based on ETA/ETD in MAPTM, and for the second instance, based on ETA/ETD in DZDJE. This corresponds to the advance manifest for FRMRS for all goods that are loaded in previous ports.

Related Information

Creating Manifest Documents [page 22]Reference Validity [page 28]

2.2.3.6 Reference Validity

The reference validity of a manifest document can be set for each manifest document in the manifest profile. It enables the manifest document’s validity to be checked based on either the expected time of departure (ETD) or expected time of arrival (ETA).

ExampleConsider the following scenario:

● A manifest document is valid until February 10● The manifest ocean booking is scheduled to arrive at the port on February 9 and depart on February 11.

To ensure that the manifest document is planned for this port, the reference validity in the corresponding manifest profile must be set to ETA and not to ETD. The reason being:

● The ETA (February 9) lies within the document validity period, that is, before 10 February.● The ETD (February 11) lies outside the document validity period, that is, after 10 February.

Related Information

Creating Manifest Documents [page 22]


Master Data

2.2.3.7 Trigger Rules

Trigger rules determine the prerequisites for including bookings and bills of lading (B/Ls) in the specific manifest document. Based on this information, the system decides whether a document submission has to include a particular B/L or booking.

For example, for an export manifest, only B/Ls loaded at a particular port are required. On the other hand, for an animal declaration, only B/Ls with a specific commodity are required.

When trigger rules are processed, the following logic applies:

● Triggers of the same type are processed with an OR operator● Triggers with different types are processed with an AND operator

ExampleConsider the following trigger types:

Trigger Type Value

Port Activity Transit

Port Activity Relay

BL type Military

If the above trigger types are defined, then a B/L that has the port activity Transit OR Relay AND BL type Military is included in the manifest document. If at least one of the trigger rules is not correct, then the B/L and booking are not included in the manifest document.

Related Information

Creating Trigger Rules [page 29]

2.2.3.7.1 Creating Trigger Rules

Create trigger rules for manifest documents in the manifest profile to specify whether bookings and bills of lading (B/Ls) are to be included in the manifest document. The trigger rule identifies the bookings and B/Ls relevant for the document.

Prerequisites

● The header data for the manifest profile has been defined.


● The header data for the manifest profile document has been defined.● The trigger types have been defined in Customizing for SAP Transportation Management under

Container Shipping Liners Order to Cash Booking and Documentation Manifest Maintain Manifest Settings .

Procedure


2. Under Profile Documents, select the manifest document and then choose the Trigger Rule tab.3. Select the rule for advanced document generation in the Advanced Document Prerequisites.

NoteThis option is only available for document types with the document activity Advanced.

4. Under Bookings and B/Ls, select from the following options:

Option Description

Include Bookings or B/Ls Select this option if B/L information must be included in the submitted document. If an authority only requires vessel and voyage information and not a list of B/Ls, leave this checkbox deselected.

If you select the above option, the following additional checkboxes are enabled; else they remain disabled and cannot be selected:

Option Option

Include House Bookings Select this option if house booking information must be included in the document submitted.

Include House B/Ls Select this option if house B/L information must be included in the document submitted.

5. Under Call type relevance, select all of the call types for which this document needs to be generated. For example, if the document must be created only for commercial ports and not for operational and technical port types, select Commercial only.

6. In the List of Triggers table (which appears only if you select Include Bookings or BLs), select the trigger type.

NoteIn addition to the trigger types defined in Customizing, you can also select from the following:


Master Data

Trigger Type Description

Port Activity The function for the relevant B/L in a port (such as export, import, transit, relay and so on).

Method Any class that implements the Interface for Trigger Class /TMCSL/IF_MANPRF_TRIGGER, where realization of the EXECUTE method must contain the custom validation logic.

7. Now specify whether you want to include or exclude a B/L based on whether it has a value that is equal or not equal to a specific value. You do this using the following fields:

Field Description

Sign Here you select either Including or Excluding.

Option Here you select either Not Equal or Equal.

Value Here you select from a list of possible values, which depend on the trigger type you select:

Trigger Type Possible Values

Port Activity Cargo operations in the port of call

Method Enter the name of the class with the predefined interface. In this case, relevance of the B/L to the specific document is determined by code (any customer-defined logic is allowed).

Any trigger type defined in Customizing

Values are read from the Data Dictionary

Value Description This is a read-only field and displays the description of the value field if available.

Example:

Trigger Type Sign Option Value

BL type Including Not Equal Military

Result: All B/Ls that are not of type Military are included in the manifest document.

8. Save your entries by saving the manifest profile.


Results

You have created the trigger rules for the manifest document.

Related Information

Example: List of Trigger Rules [page 33]Deleting Trigger Rules [page 32]Rule for Advanced Document Generation [page 33]Creating Manifest Documents [page 22]

2.2.3.7.2 Deleting Trigger Rules

Delete trigger rules for a manifest document in the manifest profile if they are no longer applicable.

Prerequisites

The trigger rules you want to delete exist for the relevant manifest document in the manifest profile.

Procedure


2. Under Profile Documents, select the manifest document and then choose the Trigger Rule tab.3. In the List of Triggers table, select the rows containing the trigger rules you want to delete and then choose

Delete.4. Save your changes by saving the manifest profile.

Results

You have deleted the selected trigger rules for the manifest document in the manifest profile.


Master Data

Related Information

Trigger Rules [page 29]Example: List of Trigger Rules [page 33]

2.2.3.7.3 Rule for Advanced Document Generation

The rule for advanced document generation applies to document types for which the document activity Advanced has been defined in Customizing. You specify this rule when creating trigger rules for manifest documents

The following rules are possible:

Rule Impact of Rule

ALL The document is always created.

FPE (First Port of Entry) The document is created only if the port is marked as the First Port of Entry and is deactivated if the port is no longer the first port of entry (U.S. case).

FPF (First Port of Entry Fixed) The document is created only if the port is marked as the First Port of Entry and is not deactivated if the port is no longer the first port of entry (EU case). As a result, the document is reassigned after a diversion notice using a special application programming interface (API).

Related Information


2.2.3.7.4 Example: List of Trigger Rules

Consider the following scenario: for a manifest document, you want to include only bills of lading (B/Ls) with type Commercial OR Government AND Discharged OR Transshipped in the current port. To do this, you would define the following trigger rules for the manifest document in the manifest profile.

Trigger Type Sign Option Value Condition Line Type Value (Description)

Booking type Including Equal 01 Commercial


Trigger Type Sign Option Value Condition Line Type Value (Description)

Booking type Including Equal 02 Government

Port Activity Including Equal 6 Port of Discharge (POD)

Port Activity Including Equal 5 Port of Transshipment (PTS)

Related Information


2.2.3.8 Activities

Activities are actions that can be performed for a particular manifest document. You can configure the activities required for the document and then schedule the execution of these activities.

Examples of activities include:

● Cleanup: This activity is used to validate data that is submitted to an authority. The activity is normally performed before each submission.

● Submission: This activity is used to send the document to the authority for the first time.● Amendments: This activity is used to send updated data to the authority.● Blackout: This activity is used to block the execution of amendment submission for a specified duration.

Scheduling of Activities

The activities can be scheduled based on vessel arrival and departure events (ETA and ETD), preceding activities, or other specific start conditions that may be developed in the Post Processing Framework (PPF) agent class.

Activities are scheduled in the manifest ocean freight booking upon creation, and are rescheduled if the vessel itinerary is changed. In this case, the special standard PPF report RSPPFPROCESS is scheduled to run in the background to check whether the activity is ready to be executed, based on its schedule or specific condition. If ready, the activity is executed and the result is available in the manifest ocean freight booking.


Master Data

Related Information

Creating Activities [page 35]

2.2.3.8.1 Creating Activities

Create activities for manifest documents in the manifest profile to set up and schedule the execution of activities for manifest documents.

Prerequisites

● The header data for the manifest profile has been defined.● The header data for the manifest profile document has been defined.

● The activities have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Manifest Maintain Manifest Settings .

● The Post Processing Framework (PPF) and output management adapter settings have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Manifest Maintain PPF Settings and Maintain Output Management Adapter Settings .

Procedure


2. Select the profile document and then choose the Activities tab.3. Create your activities by entering the following data:

○ Activity to Be Scheduled: Select the activity to be scheduled.○ Event Type: Select from the following the event types, based on which the planned time for the activity

is to be calculated:

Event Type Resultant Planned Time

Event The planned time is determined based on expected events of the vessel such as expected arrival or departure.


Event Type Resultant Planned Time

Activity The planned time is determined based on an earlier activity.

PPF Start Condition This selection indicates that another start condition (and not planned time) is used. In this case, the planned time does not need to be determined. Custom development in PPF agent class is required, which may contain a condition for activity execution that is not linked to the vessel schedule. For example, a condition to execute this activity either when the manifest document submission status is Critical Amendment Required, or when the manifest document submission status is Accepted.

○ Auto/Manual: Select from the following options

Auto/Manual Resultant Activity Schedule

Automatic The activity is scheduled and executed automatically when the required condition or event occurs.

Non-Automatic The activity is scheduled for the manifest, but can only be executed manually using the Execute button in the manifest.

Both The activity is scheduled and executed automatically when the required condition or event occurs, but can also be executed manually using the Execute button in the manifest.

○ Sea Duration Type: Select whether the activity is applicable for a short or deep sea situation or both.○ Event: Select the event used to calculate when the activity is to be executed. This field is enabled only

for activities with event type Event. The possible events are:○ Expected arrival○ Actual arrival○ Expected departure○ Actual departure

NoteIf you select the actual (and not the planned) event, then the activity is only planned after this event has happened.

○ Previous Activity: Select the activity following which the current activity is to be triggered. This field is enabled only for activities with event type Activity.


Master Data

NoteThe activity is planned only after the previous activity has been executed.

○ Time and Time Offset Unit: Enter the time offset for activity planning and select the unit (hours or days).For example, to plan the activity two hours before arrival of the vessel, the entry can be as follows:

Field Value

Event Type Event

Event Expected Arrival

Time -2

Time Offset Units Hours

○ PPF Action: Select the PPF action to be generated for this activity. This action has to be predefined in the Customizing activity Maintain PPF Settings and must belong to the profile assigned to the Manifest Document node (see Prerequisites).

○ PPF Profile and PPF Profile Description: These are read-only fields determined from the PPF action PPF profile you have selected.


Results

You have created activities for the manifest document.

Related Information

Sea Duration Type [page 38]Deleting Activities [page 38]Activities [page 34]Creating Manifest Profiles [page 20]Creating Manifest Documents [page 22]


2.2.3.8.2 Deleting Activities

Delete activities for a manifest document in the manifest profile if these activities are no longer relevant.

Prerequisites

The activities you want to delete exist for the relevant manifest document in the manifest profile.

Procedure


2. Select the profile document and then choose the Activities tab.3. Select the table rows containing the activities you want to delete and choose Delete.4. Save your entries by saving the manifest profile.

Results

You have deleted the selected activities for the manifest document in the manifest profile.

Related Information

Activities [page 34]

2.2.3.8.3 Sea Duration Type

The sea duration type indicates whether a manifest document activity is applicable for a short sea or deep sea situation, or both.


Master Data

Sea Duration Type Resultant Activity Schedule

Short The activity is scheduled only if the location to which it corresponds (that is, the location whose ETA or ETD was taken for planned time calculation) is determined as Short Sea to the location whose authority is requesting the document.

Deep The activity is scheduled only if location to which it corresponds is determined as Deep Sea.

Both The activity is scheduled without checking Short/Deep Sea indicators.

For example, a manifest must usually be submitted to the customs office of the port 24 hours prior to arrival of the vessel. However, in some cases, when ports are situated close to each other, the journey from one port to the next port takes less than 24 hours (referred to as Short Sea). This means that the submission activity for the document needs to be scheduled with a different cut-off time of normally less than 24 hours.

The activity scheduling logic in the manifest ocean booking respects this setting and plans only those activities that correspond to the actual duration. The sea duration is determined in the manifest ocean booking based on the submission location of the document and the parent or recipient location of the document.

Related Information

Activities [page 34]Creating Activities [page 35]

2.2.3.9 Key Elements

Key elements of the manifest document are attributes that require either conversion or translation when the document is submitted.

For example, the gross weight of the cargo may be maintained in kilograms (kg), but a few U.S. ports require gross weight to be specified in pounds (lb). In this case, the gross weight must first be defined in Customizing as a Convertible Key Element. In the manifest profile for the relevant U.S. ports, you then create a key element for gross weight and define it as Convertible with unit LB.

Related Information

Creating Key Elements [page 40]


2.2.3.9.1 Creating Key Elements

In the manifest profile, create key elements of a manifest document for attributes that require conversion or translation when the document is submitted.

Prerequisites

● The header data for the manifest profile has been defined.● The header data for the manifest profile document has been defined.● The key elements have been defined as either convertible or translatable in Customizing for SAP

Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Manifest Maintain Manifest Settings .

Procedure


2. Select the relevant profile document, go to the Key Elements tab, and then choose Create.3. Enter the following details:

Option Description

Key Element ID Select from the list of predefined key elements. Only key elements defined as translatable or convertible are available in the list (see Prerequisites).

Attribute This value is read-only and read from Customizing. It is the technical field name of the key element.

Node This value is read-only and read from Customizing. It is the technical node (database table) name of the key element.

Business Object This value is read-only and read from Customizing. It is the technical business object name of the key element.

Translatable This checkbox can be selected only if the key element is defined as translatable in Customizing. Select this checkbox if the key element must be treated as translatable for this particular manifest document in this particular profile.

Language If the key element is set as translatable in the previous setting, indicate the language for translation. Note that


Master Data

Option Description

the translation of this value must exist in the system, otherwise the value appears in the original language. The future usage of the language and translation requires implementation in the Post Processing Framework (PPF) agent class.

Convertible This checkbox is enabled only if the key element is defined as convertible in Customizing. Select this checkbox if the key element must be treated as convertible for this particular manifest document in this particular profile.

Unit of Measure If the key element is set as convertible in the previous setting, specify the unit of measure for the conversion. Note that the unit must be for the same dimension as in the original field (for example, weight or volume), otherwise conversion may not be possible. The future usage of the unit and conversion requires implementation in the PPF agent class.


Results

You have created key elements for the manifest document in the manifest profile.

Related Information

Deleting Key Elements [page 41]Key Elements [page 39]Creating Manifest Profiles [page 20]Creating Manifest Documents [page 22]

2.2.3.9.2 Deleting Key Elements

Delete key elements of a manifest document in the manifest profile if they are no longer relevant.

Prerequisites

The key elements you want to delete exist for the relevant manifest document in the manifest profile


Procedure


2. Select the relevant profile document and then choose the Key Elements tab.3. Select the table rows containing the key elements you want to delete and then choose Delete.4. Save your changes by saving the manifest profile.

Results

You have deleted the selected key elements for the manifest document in the manifest profile.

Related Information

Key Elements [page 39]

2.2.3.10 Validations

Some authorities may reject the submitted manifest documents if they contain missing or erroneous data. Before submission, it is therefore required to validate data with the compliance rules defined as validations in the manifest profile.

Upon submission, all documents must comply with these validations or rules. You define validations for each document in the manifest profile. The validations are then performed when the cleanup is executed.

Related Information

Creating Validations [page 43]


Master Data

2.2.3.10.1 Creating Validations

Create validations to ensure that manifest documents comply with certain rules before they are submitted.

Prerequisites

● The header data for the manifest profile has been defined.● The header data for the manifest profile document has been defined.● Certain validation classes have been implemented (for example, ABAP classes with interface /TMCSL/

IF_MAN_CLEANUP_VALID or /TMCSL/IF_MAN_CLEANUP_VALID_V).

● The validations have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Manifest Maintain Manifest Settings .

Procedure


2. Select the profile document, go to the Validations tab, and choose Create.3. Enter the following details:

○ Validation: Select from the list of available validations.○ Active: Deselect if you do not want this validation to be executed. Only active validations are executed

when manifest documents are cleaned up.○ Validation Level: This read-only field is read from Customizing and indicates whether data for validation

is read at bill of lading (B/L) or vessel level. For example, the rule to check the Local Voyage Number of the vessel is executed at vessel level, while the rule to check whether all B/Ls have a consignee assigned is executed at B/L level.

○ Criticality: Select the criticality of the validation from the following possible values:

Criticality Result

Abort Manifest document submission is aborted if at least one B/L has been validated with abort.

Error The respective booking or B/L is excluded from submission, but submission may still be carried out for the remaining B/Ls.

Warning Warning messages are saved in the log, but the B/L is included in the submission.


NoteThe proposed behavior may be overwritten in the Post Processing Framework (PPF) agent class (for example, ABAP development required).


Results

You have created validations for the manifest document.

Related Information

Deleting Validations [page 44]Validations [page 42]Creating Manifest Profiles [page 20]Creating Manifest Documents [page 22]

2.2.3.10.2 Deleting Validations

Delete validations for a manifest document in the manifest profile if they are no longer relevant.

Prerequisites

The validations you want to delete exist for the relevant manifest document in the manifest profile.

Procedure


2. Select the profile document and then choose the Validations tab.3. Select the table rows containing the validations you want to delete and then choose Delete.4. Save your changes by saving the manifest profile.


Master Data

Results

You have deleted the selected validations for the manifest document in the manifest profile.

Related Information

Validations [page 42]

2.2.3.11 Responses

Responses can be sent by authorities to carriers to address manifest documents that have been submitted.

For example, the response could be acceptance or rejection of the submitted document (due to missing or incorrect data, or any other reason). It could also be special instructions for the specific cargo listed in the submission. For example, the authorities may prohibit loading or discharging of some cargo in a specific port, or request that cargo be held for inspection, or similar. To address such needs, responses can be created for each manifest document.

Related Information

Creating Responses [page 45]

2.2.3.11.1 Creating Responses

Create responses to allow the port authorities to accept or reject manifest documents, or to provide special instructions for cargo.

Prerequisites

● The header data for the manifest profile has been defined.● The header data for the manifest profile document has been defined● Specific response action classes have been implemented if standard behavior does not suit your business

scenario (for example, ABAP classes with interface /TMCSL/IF_MAN_RESPONSE_EXECUTE).


Procedure


2. Select the profile document, go to the Responses tab, and choose Create.3. Enter the following details:

○ Status: Select the status code of the responses expected from the particular authority. The format of the response must be known and usually published by the authority.

○ Status (Description): Enter the description of the status code.○ Response Action Class: Select the action class that corresponds to the status. This action class is

called by the system when the response is processed and the information required is updated.For example, an authority uses the code RJ when rejecting a submission, which means you would enter the following:

Status Status (Description) Response Action Class

RJ Submission Rejected Submission Rejected (changes the submission status of the respective document to Rejected


Results

You have created responses for the manifest document.

Related Information

Deleting Responses [page 47]Responses [page 45]Creating Manifest Profiles [page 20]Creating Manifest Documents [page 22]


Master Data

2.2.3.11.2 Deleting Responses

Delete responses for a manifest document in the manifest profile if they are no longer relevant.

Prerequisites

The responses you want to delete exist for the relevant manifest document in the manifest profile.

Procedure


2. Select the profile document and choose the Responses tab.3. Select the table rows containing the responses you want to delete and then choose Delete.4. Save your changes by saving the manifest profile.

Results

You have deleted the selected responses for the manifest document in the manifest profile.

Related Information

Responses [page 45]

2.2.3.12 Amendments

In an ideal world, the manifest or bill of lading (B/L) data submitted to the authorities by the carrier is final. However, this data is sometimes not available at the time of submission, or it is changed after the submission, or even new B/Ls are created at the last minute. If critical information is changed, this must be resubmitted to the authority as an amendment.

The Amendments tab in the manifest profile lists all of the attributes of the submission that require amendments to be filed.


Related Information

Creating Amendments [page 48]

2.2.3.12.1 Creating Amendments

Create amendments for all attributes of manifest documents that require an amendment to be filed, for example, if bill of lading (B/L) data is changed, subsequently created, or was previously not available.

Prerequisites

● The header data for the manifest profile has been defined.● The header data for the manifest profile document has been defined.● The key elements relevant for amendments have been defined in Customizing for SAP Transportation

Management under Container Shipping Liners Order to Cash Booking and Documentation ManifestMaintain Manifest Settings .

● The amendment classes have been implemented (for example, ABAP classes with interface /TMCSL/IF_MANPRF_AMENDMENT_TOR or /TMCSL/IF_MANPRF_AMENDMENT_TRQ)The amendment classes have been implemented (for example, ABAP classes with interface /TMCSL/IF_MANPRF_AMENDMENT_TOR or /TMCSL/IF_MANPRF_AMENDMENT_TRQ).

Procedure


2. Select the profile document, go to the Amendments tab and choose Create.3. Enter the following details:

○ Amendment Item: Select the attribute relevant for amendment from the dropdown list. You can select from the following:

Amendment Item Description

Port Activity The action that the B/L is performing in the current port. For example, if the B/L was planned for discharge in the current port and then replanned to stay on board.

Key element The entries that have been predefined in Customizing


Master Data

Amendment Item Description

Method ABAP class with predefined interface (see Prerequisites).

○ Class: Select the amendment class name from the list. This field is enabled only for amendments of type Method.

○ Attribute: This field is read-only and read from Customizing. It shows the technical field name of the key element.

○ Node: This field is read-only and read from Customizing. It is the technical node (database table) name of the key element.

○ Business Object: This field is read-only and read from Customizing. It is the technical business object (BO) name of the key element.

○ Amendment: This field indicates the criticality of the amendment. Select either Critical or Required. This criticality level is set in the manifest ocean freight booking if an amendment is made.For some authorities, critical amendments might be required for submission as soon as possible. If the amendment is noncritical, it can wait for daily or weekly batch amendments. The future usage of the criticality requires implementation in the Post Processing Framework (PPF) agent class.

Results

You have created amendments for the manifest document.

Related Information

Deleting Amendments [page 49]Amendments [page 47]Creating Manifest Profiles [page 20]Creating Manifest Documents [page 22]

2.2.3.12.2 Deleting Amendments

Delete amendments for a manifest document in the manifest profile if they are no longer relevant.

Prerequisites

The amendments you want to delete exist for the relevant manifest document in the manifest profile.


Procedure

1. In SAP NetWeaver Business Client, choose Master Data Manifest Profile Create Manifest Profile , and then open the relevant manifest profile.

2. Select the manifest profile document and choose the Amendments tab.3. Select the table rows containing the amendments you want to delete and then choose Delete.4. Save your changes by saving the manifest profile.

Results

You have deleted the selected amendments for the manifest document in the manifest profile.

Related Information

Amendments [page 47]

2.2.3.13 Document Usage

Once a manifest profile is defined, finalized, and assigned in the partner profile to the respective authority, its documents are planned in the manifest ocean freight bookings wherever the authority is involved. The Document Usage tab of the manifest profile indicates whether the manifest document is in use, and if so, in which manifest ocean freight bookings.

It also shows which business partners the profile is assigned to, the document statuses in the respective voyages (manifest ocean freight bookings), and submission or cleanup planning.

NoteAny changes you make in the manifest profile document are propagated to the respective manifest ocean freight bookings unless either the document submission status or the manifest status is complete.

2.2.4 Change Documents for Manifest Profiles

In the manifest profile, the Change Documents tab displays the changes that have been made in the profile and by which user.

NoteThe standard SAP change log mechanism is used, which means that all of the rules valid for logging changes are also applicable. Change are recorded only for fields for which the change document flag has been set.


Master Data

Related Information

For more information about logging using change documents, see SAP Library for your SAP NetWeaver release on SAP Help Portal at http://help.sap.com/netweaver. Under Application Help Function-Oriented View , open SAP Library and search for Logging Using Change Documents.

For more information about setting the change document flag, see SAP Library for your SAP NetWeaver release on SAP Help Portal at http://help.sap.com/netweaver. Under Application Help Function-Oriented View , open SAP Library and search for Set Change Document Flag.

2.3 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.

Related Information

Tabs in Partner and Location Profiles [page 51]Creating Partner and Location Profiles [page 55]

2.3.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 SAP Transportation Management under Container Shipping Liners Basic Settings Partner and Location Profile


http://help.sap.com/netweaver


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 52]

2.3.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

Agency Business partner (MD and template) E-Signature File Name field

Business partner (MD and template) Edit Link button

Business partner and location (MD and template)

Empty Repositioning Approval Threshold table

Documentation Location and country (MD and template)

Commodity Codes Exempted from Customs Clearance table

Business partner and country (MD and template)

DO Generation Rule table

Business partner (MD only) Manifest Profile Assignment table

Location and 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 DDSM Export Charges field

Country (MD and template) Include DDSM Import Charges field


Master Data


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)


DO Required field


DO Auto Creation Level field


Badge Code Provided field


Badge Code table

Booking Location and country (MD and template)

No Show Fee on Booking Cancellation table


Number Range table


Reconfirmation Information field

Location (MD and template) Allowed as Part-Load Destination field

Location (MD and template) Dynamic Attributes Profile field

Country (MD and template) Evaluate Conditions at Receiver field


Temperature field


Vent Open field


Reconfirmation Required field


General Information section

Business partner (MD and template) ETA Tolerance Period field

Country (MD and template) Distribution Profile field

Charge Calculation Business partner (MD and template) General table



Business partner (MD and template) Place of Payment field

Location (MD and template) Authorized Place of Payment field

Output Management Business partner and country (MD and template)

Output Channels table

Business partner (MD and template) Contact Person for Primary Channel field

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

2.3.2 Brand-Specific Data in Partner and Location Profiles

Certain data in a partner and location profile (PLP) is brand-specific. This kind of 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 maintenance view /TMCSL/V_BRAND (using transaction SM30).

2.3.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 SAP Transportation Management under Container Shipping Liners Order to Cash Basic Settings Partner and Location Profile Define Approval-Relevant Fields .

When a nonauthorized user changes an ARF and saves the change, the BAdI: PLP Approval-Relevant Fields is triggered. This BAdI has information (such as old and new values) about the ARF, and is implemented to


Master Data

determine the further workflow. The changed ARF values are subsequently restored to their old values. For more information about this BAdI, see the associated Customizing documentation in Customizing for SAP Transportation Management under Container Shipping Liners Business Add-Ins (BAdIs) Master DataPartner and Location Profile BAdI: PLP Approval-Relevant Fields .

2.3.4 Creating Partner and Location Profiles

Create a new partner and location profile (PLP) for a particular master data object.

Prerequisites

In Customizing for SAP Transportation Management under Container Shipping Liners the following activities have been completed:

● The number range intervals for PLP have been defined under Basic Settings Partner and Location Profile Define PLP Number Range Intervals .

● The PLP types have been assigned to the number range intervals under Order to Cash Basic SettingsPartner and Location Profile Assign PLP Types to Number Range Interval .

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Partner and Location Profile Create Profile .

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.○ Master Data ID: This can be the Business Partner, Location, or Country field, depending on the PLP

type selected.○ 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.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 56]Copying Partner and Location Profiles [page 57]Deactivating Partner and Location Profiles [page 58]Deleting Partner and Location Profiles [page 59]Uploading Data to PLP Tables [page 61]

2.3.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 SAP NetWeaver Business Client, choose Master Data Partner and Location Profile Change Profile .

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.


Master Data

Related Information

Copying Partner and Location Profiles [page 57]Deactivating Partner and Location Profiles [page 58]Deleting Partner and Location Profiles [page 59]Uploading Data to PLP Tables [page 61]

2.3.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.

Procedure


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 56]Deactivating Partner and Location Profiles [page 58]


Deleting Partner and Location Profiles [page 59]Uploading Data to PLP Tables [page 61]

2.3.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


2. Specify the profile ID of the profile to be deactivated and choose Continue.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 59]Deleting Partner and Location Profiles [page 59]


Master Data

2.3.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


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.

2.3.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



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.3.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.3. Specify the selection criteria for retrieving a target set of PLPs.

NoteTo avoid performance issues, select at least one attribute of the ROOT level.

4. Specify the components and attributes to be maintained or changed.

NoteThe 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:

○ Change w/o Display if you want to set the same value in the relevant field for all the selected profiles.○ Change with Display if you want to set different values in the relevant field for all the selected profiles

7. Make the necessary changes for the maintainable fields.


Master Data

8. Save your entries.

Results

The selected PLPs are updated with the newly maintained values.

2.3.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.

NoteThe 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


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.3.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.

NoteThe 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.

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.


Master Data

2.3.13 POWL for Partner and Location Profiles

The Personal Object Worklist (POWL) for the partner and location profile can be found in SAP NetWeaver Business Client under Master Data Partner and Location Profile Partner/Location Profile Worklist .

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.3.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

DEACTIVATE Deactivates existing PLPs

REACTIVATE Reactivates existing PLPs

PROFILE_DETERMINATION Composes a combined profile for the specified consumer and its business document number

2.4 Product Catalog

A product catalog contains all of the service products for a particular trade lane and carrier. The product manager uses a product catalog to capture the routes and supplemental services that are made available to the customer.

Product catalog is based on the standard service product catalog solution in SAP Transportation Management (SAP TM).

You can perform the following tasks in the product catalog:

● Create service productsYou can create service products using the Create Service Products screen or the Service Product Worklist.

● Edit service productsYou can edit existing service products in the Edit Service Products screen or in the Service Product Worklist.


● Assign routes manually or automatically to a service productA service product must have at least one assigned route. The product catalog calls the route generator application programming interface (API) to get all possible valid routes between a source and destination location for a service product.

● Add services to the service product● Specify whether the service product is published on an external portal● Change the status of a service product● Set the update status of a service product● Mass-update service products

You can use the mass-update application to update multiple service products on a single screen.● 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 and to perform various operations to selected service products.

Related Information

Creation of Service Products [page 64]Service Product Worklist [page 87]Mass Update [page 86]Route Assignment [page 68]

2.4.1 Creation of Service ProductsA service product contains information such as the source and destination locations, validity dates, trade lane, and carrier. Routes are assigned to the service product.

The system supports two types of service products:

● Customized service productsA customized service product is a corridor with only one assigned route.

● Open service productsAn open service product is more flexible in that it consists of a corridor (origin-destination combination) with one (or in exceptional cases more) preferred route and one or two alternative routes. The preferred route is the default route for the service product. If the preferred route is not available then one of the alternative routes can be used by the carrier.

The routes that are assigned to the service product are identified by the route generator application programming interface (API).

You can perform the following tasks when creating a service product:

● Add general data such as validity dates, trade information, and source and destination locations

NoteThere are differences between the standard product catalog functionality in SAP Transportation Management and the product catalog functionality provided in the container shipping liners solution. In


Master Data

particular, the following standard fields are not available on the General Data tab in the container shipping liners solution:○ Shipping Type○ Calculation Sheet Template○ Archiving Status○ Sales Organization○ Transportation Mode○ Traffic Direction

● Add service items to the service productYou can add different services to the service product (for example, fumigation, insurance, and so on) and then define a stage type for each service. You can also add instructions, commodity codes, and can create a calculation sheet.

NoteThere are differences between the standard product catalog functionality in SAP Transportation Management and the product catalog functionality provided in the container shipping liners solution. In particular, the following restrictions apply on the Items tab in the container shipping liners solution:○ You can only create items of type Service.○ When you create a service product catalog, by default only one service product record is created

automatically.○ The following functions are disabled:

○ Follow Up○ Copy○ Create Forwarding Agreement Quotation

● Copy an existing service product● Check the consistency and completeness of the service product data

When you save or check a service product, the system performs consistency checks and checks the business rules that are maintained in the Generic Validation Framework (GVF).

● Specify if the service product is to be published● Assign routes to the service product● View information (attributes) about the assigned routes

The Attributes tab displays information about the assigned routes, for example, departure frequency, cargo types, and transshipments.

● Set the update status of the service product● View reason codes on the Justification tab● Add notes and attachments on the Attachments tab● View administrative data and any changes made to the service product

You can view changes made to the update status fields (Update Status, Update Status Date, and Update Status By on the Change Documents tab. The changes are listed by date and time. 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 sentOn 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).


Related Information

Creating Service Products [page 66]Generic Validation Framework [page 89]Route Generator API for Product Catalog [page 108]Publication Status [page 83]Route Assignment [page 68]Attributes [page 74]Update Status [page 84]Justification [page 79]

2.4.1.1 Creating Service Products

Create a service product to capture the details of routes that you offer to customers.

Prerequisites

● An open service product with the same source and destination location in the same validity period does not exist in the system.

● A customized service product with the same route that has the same stages in the same validity period does not exist in the system.

● Forwarding agreements (FWAs) and service product catalog types have been defined in Customizing for SAP Transportation Management under Transportation Management 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 SAP Transportation Management under Transportation Management Master Data Agreements and Service ProductsDefine FWA and Service Product Item Types .

● Default route types have been defined in Customizing for SAP Transportation Management under Transportation Management Master Data Transportation Network Define Default Route Types .

● General settings have been defined for service products in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Product Catalog Define General Settings for Service Product .

● Justification use cases and reason codes have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Product Catalog Define Justification Use Cases and Reason Codes .

● Service product update statuses have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Product Catalog Define Service Product Update Statuses .

● Movement types and location types have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Product Catalog Define Movement Types .


Master Data

● The impact of changes on service product attributes has been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Product CatalogDefine Impact of Changes on Service Product Attributes .

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management and Service Product Catalogs Service Product Create Service Product .

The system initially sets the status of the service product to Draft and the service product type to Open, which you can change, if needed. The Service Product ID field is a read-only field that contains a temporary number assigned by the system. A permanent number is assigned by the system after you save the service product.

2. On the General Data tab, enter general data about the service product such as transportation network information and the validity period. The following fields must be completed before a route can be assigned to the service product:○ Service Product Type○ Carrier○ Trade Lane○ Movement Type○ Source Location○ Destination Location

After routes have been assigned to the service product, the following fields on the General Data tab cannot be edited:

○ Service Product Type○ Carrier○ Trade Lane○ Movement Type○ Source Location○ Destination Location

3. If you want the service product to be published, select the Publication checkbox on the Publicity screen area of the General Data tab.

If you select the Publication checkbox, you must specify the publication dates and publication type.4. (Optional) On the General Data tab, add services to the service product on the Item screen area.

You can also define a stage type for each service, and add a calculation sheet, preconditions, notes, and instructions to the service product.

5. On the Attributes tab, assign at least one of the carrier’s brands by selecting the Selection checkbox for each relevant brand on the Brands table.

6. On the Routes tab, generate and assign routes manually or allow the system to automatically generate and assign the routes.

The system assigns the routes and displays the assigned route information on the Assigned Routes table and on the Attributes tab.


7. (Optional) Deselect any cargo types on the Attributes tab that you do not need for the service product.8. (Optional) On the Notes and Attachments tabs, add extra information about the service product in the form

of text files or attached files.9. (Optional) Set the status of the service product by choosing Set Status.

NoteIf you change the status to Ready for Approval, you must specify a reason code.

10. (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).

11. 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 64]Generic Validation Framework [page 89]Route Assignment [page 68]Attributes [page 74]Service Product Status [page 79]Justification [page 79]

2.4.1.2 Route Assignment

Routes are assigned to service products after the required general data has been entered. A service product must have at least one assigned route.

Usually, the route with the highest rank is assigned as the preferred route; however, you can also assign a route with a lower ranking as the preferred route. If you assign a lower ranking route as the preferred route, you must specify a reason code.

The Routes tab contains information about the assigned and proposed routes for the service product.

You can perform the following tasks on the Routes tab:

● Generate a list of proposed routes for the service productThe route generator application programming interface (API) searches for all possible routes between the source and destination locations that you specified on the General Data tab. The route generator then returns route proposals with stages relevant for the particular route. The list of route proposals is ranked, and you can view the assigned rank for the route in the Rank field on the Proposed Routes table. The rank for each route is provided by route generator. If any route proposals are considered relevant for the


Master Data

connecting manifest case, an additional aggregation level is provided by the system. Note that the system does not save information about route proposals.

● Manually assign routes to the service productAfter the system generates the proposed routes, you can manually assign the routes to the service product. You can assign one (or in exceptional cases more) preferred route and one or two alternative routes to an open service product. You assign only one route to a customized service product.

NoteYou can only manually assign proposed routes that are not already assigned to the service product.

● Automatically assign routes to the service productYou can allow the system to automatically generate and assign the routes in one step. In this case, the system assigns the highest-ranking route to the service product.

● Change the assignment type of assigned routes of open service products (for example, from an alternative route to a preferred route).

● View if a route has been manually or automatically assigned to the service productIf a route has been manually assigned, the Manual Assignment checkbox is selected on the Assigned Routes table.

● Delete an assigned or proposed route● View the attributes of the assigned preferred route or routes on the Attributes tab● View the status of assigned and proposed routes

Route Status

Assigned and proposed routes are displayed on the Routes tab of the service product application. The status of each route is indicated through the use traffic lights, which are described in the table below:

Traffic Light Color Route Status

Green The route is valid for 30 days or more.

Yellow The route is valid for less than 30 days.

Red The route is invalid and the validity period is out of date.

Connecting Manifest Consideration

An additional aggregation level is provided for route proposals that are returned by the route generator and are considered as relevant for the connecting manifest case.

The following logic is executed after the system calls the route generator and before the proposed routes are displayed on the Routes tab: If the proposals have stages that are marked by the route generator as relevant for the connecting manifest case, they are merged into one stage and the route transit time is summed.


Related Information

Assigning Routes Manually [page 71]Assigning Routes Automatically [page 73]Creation of Service Products [page 64]Creating Service Products [page 66]Route Generator API for Product Catalog [page 108]

2.4.1.2.1 Route Assignment Period Determination

The assignment period of routes is determined by the system based on the route validity dates, the service product validity dates, and the current date. You can also manually change assignment period.

The route assignment period is the Assigned From and Assigned To dates on the Assigned Routes table.

The following values are taken into account when the system determines the assignment period of the proposed routes:

● Current date● Validity dates of the service product

The service product validity dates are the Valid From and Valid To dates on the General Data tab.● Route validity dates

The route validity dates are Valid From and Valid To dates on the Assigned Routes table.● Service product type● Number of preferred routes (in open service products)

The system takes the following rules into account when determining the assignment period of the routes:

● In open service products, the service product validity dates can exceed the route validity dates of the preferred or alternative assigned routes.

● In customized service products, the service product validity dates cannot exceed the route validity dates of the assigned route.

● After manual or automatic assignment of a route to a customized service product, the system automatically changes the route validity dates to match the service product validity dates.

● In an open service product, the Assigned To date of the route date cannot exceed the Valid To date of the route.

● A service product must have at least one preferred route with an assignment period that is dated six months or more from the current date. For example, if the current date is 01-Jan and the Assigned From date is 01-Jan, then the Assigned To date must be later than or equal to 30-June. If the service product validity period is less than six months, the assignment period must be within all the service product validity periods (that is, the service product validity dates, the route validity dates of each assigned route, and the route assignment period). This rule is based on the current date. An exception to this rule is if the Valid From date of the service product is in the future, then this date is used as the start date of the six-month duration.

● If an open service product has more than one preferred route, the assignment periods cannot overlap for preferred routes that have the same departure weekday.

● In an open service product, the assignment periods cannot overlap for an Alternative 1 route and an Alternative 2 route.


Master Data

Related Information

Route Assignment [page 68]Justification [page 79]Attributes [page 74]

2.4.1.2.2 Assigning Routes Manually

Assign routes manually to the service product if you do not want the system to automatically assign the highest-ranking route as the preferred route for the service product. For example, in an open service product, you may want to assign more than one route as the preferred route.

Prerequisites

Reason codes and use cases have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Product Catalog Define Justification Use Cases and Reason

Codes .

Context

You can only manually assign a route from the list of proposed routes if it has not been already assigned to the service product. In an open service product, several routes can be assigned as preferred routes if they have different departure weekdays.

Procedure


2. Complete the mandatory fields on the General Data tab.

3. On the Routes tab, generate the proposed routes by choosing Routes Generate on the Assigned Routes toolbar.

The route generator application programming interface (API) searches for routes and displays a list of proposed routes and stages that are sorted by rank in the Proposed Routes table. You can view the stages for each proposed route by expanding the routes node.

4. Assign the routes to the service product.


Depending on whether the service product type is open or customized, you assign the routes as follows:

Service Product Type Steps to Assign a Route

Open 1. In the Proposed Routes table, select the preferred route for the service product.

2. On the Proposed Routes toolbar, choose Assign As

Preferred .

NoteAll possible routes are sorted by rank in descending order in the Proposed Routes table. If you select a route that is not ranked highest as a preferred route, you must specify a reason code.

3. In the Reason dialog box, specify the relevant reason code.The system adds the route to the Assigned Routes table.

4. Assign an alternative route for the service product by selecting a route in the Proposed Routes table and choosing Assign As in the Routes toolbar.The system adds the alternative route to the Assigned Routes table.

Customized 1. In the Proposed Routes table, select the preferred route for the service product.

2. On the Proposed Routes toolbar, choose Assign.The system adds the route to the Assigned Routes table.

5. (Optional) Change the default assignment periods for the assigned routes by changing the dates in the Assigned From and Assigned To fields on the Assigned Routes table.

6. Delete routes that you do not need from the list of assigned routes.7. (Optional) Change the assignment type of assigned routes in open service products by selecting the

assigned route and choosing Change Type To on the Proposed Routes toolbar.

NoteIf you change the assignment type to Preferred, you must specify a reason code.

Results

Routes are assigned to the service product. The route attributes are displayed on the Attributes tab. Any reason codes entered during the assignment process are displayed on the Justification tab.


Master Data

Related Information

Assigning Routes Automatically [page 73]Route Assignment [page 68]Route Generator API for Product Catalog [page 108]

2.4.1.2.3 Assigning Routes Automatically

Assign routes automatically when you want the system to assign the highest-ranking route to the service product.

Context

Before automatically assigning routes, the system deletes any routes that were previously assigned to the service product.

The automatic assignment logic for open and customized service products differs as follows:

● Open service productThe system assigns the proposed route with Rank 1 as the preferred route. Proposed routes with ranks 2 and 3 (if such routes were generated) are assigned as Alternative 1 and Alternative 2 respectively.

● Customized service productThe proposed route with Rank 1 is assigned to the service product.

Procedure


2. Complete the mandatory fields on the General Data tab.3. On the Routes tab, generate and assign routes to the service product by choosing Generate and Assign on

the Assigned Routes toolbar.

Route proposals are retrieved by the route generator application programming interface (API) and listed in the Proposed Routes table. The highest-ranking route is assigned to the service product and is listed in the Assigned Routes table. The assigned route is marked as assigned in the Proposed Route table.

4. (Optional) Change the default assignment periods for the assigned routes.5. (Optional) Delete routes that you do not need from the list of assigned routes.6. (Optional) Change the assignment type of assigned routes in open service products by selecting the

assigned route and choosing Change Type To.


NoteIf you change the assignment type to Preferred, you must specify a reason code.

Results

One or more routes are assigned to the service product. The route attributes are displayed on the Attributes tab. Any reason codes that you entered during the assignment process are displayed on the Justification tab.

Related Information

Assigning Routes Manually [page 71]Route Assignment [page 68]

2.4.1.3 Attributes

The attributes of the service product are information about the routes that are assigned to the service product.

After one or more routes have been assigned to the service product, the Attributes tab displays information about the assigned routes, for example, departure frequency, cargo types, and transshipments. The system calculates the attributes based on specific rules. The brands that are owned by the carrier are also listed on the Attributes tab. You can select the brands that must be used for the service product.

NoteIf an open service product type has been assigned more than one preferred route, the fields on the Attributes tab display aggregated information about the assigned preferred routes. The cargo types attribute is different to the other attributes in that it takes into account the assigned preferred and alternative routes.

Cargo Types

The Attributes tab also displays which of the following cargo types are supported by the assigned route:

● Out of gauge● Dangerous goods● Reefer

NoteIf the service product type is Open, the cargo types attribute takes into account all preferred and alternative routes.


Master Data

If at least one assigned route supports a cargo type, the checkbox for that cargo type is selected. You can deselect the checkbox for a supported cargo type if you do not need it for the service product.

The system also calculates the following attributes for the assigned preferred route or routes:

Attribute Description

Transit time This value is the length of the assigned preferred route in days.

If more than one preferred route has been assigned to an open service product, the transit time is the range of days of the assigned preferred routes (for example, 25-30 days).

Transshipments This value is the number of points between the maritime stages of the assigned preferred route.

If more than one preferred route has been assigned to an open service product, the number of transshipments is the range of points between the maritime stages of the assigned preferred routes.

Departure frequency This value is the frequency of the assigned preferred route. The frequency can be daily, weekly, N times per week, N times per day, every N days, or N times in M days.

If more than one preferred route has been assigned to an open service product, the departure frequency is the frequency of all the assigned preferred routes.

ExampleAn open service product has two assigned preferred routes: Route 1 and Route 2. Route 1 departs on Mondays and Route 2 departs on Tuesdays. The departure frequency for this service product is 2 (two) times per week.

Departure days This value is the days of departure for the route.

If more than one preferred route has been assigned to an open service product, the departure days indicate the departure days of all the assigned preferred routes.

Line This value is the service or services provided in the maritime stage or stages. This field is visible only for customized service products.


Attribute Description

Transportation modes for pre-carriage and on-carriage stages

This value is the transportation modes used for the pre-carriage and on-carriage stages of route.

If more than one preferred route has been assigned to an open service product, the transportation mode lists all the transportation modes used for the pre-carriage and on-carriage stages of the assigned preferred routes.

Related Information

Route Assignment [page 68]Creation of Service Products [page 64]

2.4.1.3.1 Calculation Rules for Attributes

The system applies specific rules when calculating the routes attributes in a service product.

After one or more routes have been assigned to the service product, the system calculates the attributes and displays the information on the Attributes tab.

The system applies the following rules when calculating the attributes:

● Attributes are calculated based on the assigned routes for the current date.● For open service products, the system takes into account the assignment period of preferred assigned

routes (the cargo types attribute also takes the assigned alternative routes into account) when calculating the attributes.

● For customized service products, the system takes into account the validity period of the assigned route when calculating the service product attributes.

● If the service product is not yet valid (for example, the valid-from date is in the future), the attributes are calculated on the valid-from date of the service product.

● If the service product has ended (for example, the valid-to date is in the past) and if the service product has assigned routes with assignment periods that are valid until the end of service product, the attributes are calculated based on the valid-to date of the service product. Otherwise, the attributes are calculated based on the last valid Assigned To date of the preferred route of the service product.

● If you assign a new route or delete an assigned route from the service product, the system recalculates the attributes.

Related Information

Attributes [page 74]Route Assignment [page 68]


Master Data

2.4.1.3.2 Impact of Route Changes on Service Product Attributes

If you make changes to an assigned route in an existing service product, the system checks if the changes affect the service product attributes (for example, if you add a new route that has different departure days).

If the route changes affect the service product attributes, the system displays a dialog box after you save or check the service product. The dialog box displays detailed information about the impact of the changes on the service product attributes. The information includes a list of the changes and the priority (high, medium, or low) of each change. You can then decide to either proceed with the changes or cancel the process.

Bandwidths can be set for certain attributes (for example, for transshipments, transit time, and departure frequency). The bandwidths can be used as checks to ensure that changes in attributes do not affect the commercial promise of the service product. The bandwidth can be absolute (for example, the number of days) or relative (a percentage change in the value). If the changes to the route results in the attributes exceeding the set bandwidths, a dialog box warns you that the changes exceed the bandwidths (thereby affecting the commercial promise of the service product) and gives you the option to create a new service product. In this case, you can continue with the changes and allow the system to create a new service product, or you can cancel the process.

If you choose to allow the system to create a service product based on the route changes, the following occurs:

● In the existing service product, the new route is removed, a new validity end date is set, and the publication period is updated with the new validity date.

● A new service product is created in Draft status. The new service product has the same key parameters (source and destination locations, carrier, trade lane, and so on) as the original service product. The new route is assigned to the new service product.

● The system displays a dialog box, in which you must specify a reason code for the changes. This reason code is saved on the Justification tab of the newly created service product.

● The system saves the ID of the original service product (the predecessor ID) in the newly created service product. The ID of the new service product (the successor ID) is saved in the original service product. You can view the successor and predecessor ID on the General Data tab.

If the bandwidths are exceeded for the defined attributes, the system also checks that certain conditions are met before it creates a new service product. These conditions are grouped into the following scenarios:

● Current-date case● Future-date case

You can define the impact of the changes and set the relevant bandwidths in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Product Catalog Define Impact of Changes on Service Product Attributes .

Related Information

Route Assignment [page 68]Date Case Conditions for Impact of Route Changes [page 78]Justification [page 79]Attributes [page 74]


2.4.1.3.3 Date Case Conditions for Impact of Route Changes

If the bandwidths that have been set for certain service product attributes are exceeded, the system gives you the option to create a new service product.

Before the system creates a new service product, it checks that certain conditions are met. These conditions are grouped into the following scenarios:

● Current-date case● Future-date case

Current Date Case

In the current-date case, each of the following conditions must be true before the system creates the new service product:

● The service product type is Open.● The status of the service product is Approved.● The service product validity period (the Valid From and Valid To dates on the General Data tab) is not fully in

the future.● At least one of the following changes was made to the assigned routes:

○ A new preferred route was assigned with the current date.○ A preferred route with an assignment period that includes the current date was deleted.○ The assignment period of a preferred route, which initially included the current date, was changed and

the new assignment period does not include the current date.● The difference in the old and new service product attributes on the current date exceeds the bandwidth

limits.

Future Date Case

In the future-date case, each of the following conditions must be true before the system creates the new service product:

● The service product type is Open.● The status of the service product is Approved.● The service product validity period is not fully in the future.● The service product has only one route and it is the preferred route.● One new preferred route with the following characteristics was assigned to service product:

○ The route assignment start date is in the future.○ The route assignment start date is the next day after the assignment end date of the old preferred

route.● The difference in the old and new route attributes exceed the bandwidths.


Master Data

Related Information

Impact of Route Changes on Service Product Attributes [page 77]Attributes [page 74]Route Assignment [page 68]Justification [page 79]

2.4.1.4 Justification

For certain scenarios in the service product, you must justify your actions by specifying a reason code before you can complete your actions.

When you perform certain predefined actions to the service product, the system displays a dialog box in which you must specify a reason code and optionally add a description.

The following scenarios require you to enter a reason code:

● If you change a route assignment type to Preferred● If you assign a proposed route that does not have the highest rank as the preferred route● If you change the service product status to Ready for Approval or Request Discontinuation● If you make changes to the routes that will affect the route attributes

You can view the reason codes that were entered for the service product on the Justification tab. Reason codes and use cases are defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Product Catalog Define Justification Use Cases and Reason Codes .

Related Information

Route Assignment [page 68]Impact of Route Changes on Service Product Attributes [page 77]Creation of Service Products [page 64]

2.4.1.5 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 80]Service Product Status Descriptions [page 81]Creation of Service Products [page 64]

2.4.1.5.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 SAP NetWeaver Business Client, choose Master Data Charge Management and Service Product Catalogs Service Product Edit Service Product , and specify the service product ID.

2. On the Service Product toolbar, choose Set Status.

NoteDepending 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.

3. Depending on the status that you select, you may need to specify a reason code for the status change.

Related Information

Service Product Status [page 79]


Master Data

Service Product Status Descriptions [page 81]Justification [page 79]

2.4.1.5.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 responsible person. This status can be set only if the following conditions are true:

● One or more routes are assigned to the service product.● The publication type and publication period are defined.● The service product data is consistent.

When you set this status, you must specify a reason code.

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.



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.

ExampleConsider 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. 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 service products in this status. A service product that has a Canceled status would never have been approved and therefore never used in business processes. You might, for example, cancel a service product if the data contains an error.

NoteIf 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. When you set this status, you must specify a reason code. You cannot edit service products in this status.

When you set the status to Request Discontinuation the system displays a dialog box, which gives you information about the number of forwarding agreement quotation (FWAQ) and forwarding agreement (FWA) documents that will be affected if the service product is discontinued. You can then decide whether to cancel or continue with the discontinuation request.

The status of a service product that has a Request Discontinuation status can be changed back to Approved or Discontinued.


Master Data


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.

When you set the service product status to Discontinued, the system displays a dialog box, which gives you information about how many FWAQ and FWA documents will be affected if the service product is discontinued. You can then decide whether to cancel or continue with the discontinuation of the service product.

Related Information

Service Product Status [page 79]Changing the Service Product Status [page 80]Justification [page 79]

2.4.1.6 Publication Status

You can specify if a service product is to be published on an external portal, where customers can search for and select the service products you have created. You can also set the publication dates and define the publication type.

You set the publication status of a service product on the General Data tab of the service product screen. If you select the Publication checkbox, the service product is published on an external portal.

The system automatically deselects the Publication checkbox if the status of the service product is Discontinued.

If you choose to publish a service product, you must also define the publication period by specifying the publication-from and publication-to dates. If you don't specify the publication dates, you cannot set the status of the service product to Ready for Approval or Approved.

The publication dates must be within the validity period of the service product, which is defined in the Validity screen area on the General Data tab.

Publication Type

If you choose to publish a service product, you must also specify one of the following publication types:


● PrivateA private service product is created for a particular customer, and is therefore not available to all customers on the external portal.

● PublicA public service product is available to all customers on the external portal.

The default publication type for open service products is Public, and the default publication type for customized service products is Private.

Related Information

Service Product Status [page 79]Creation of Service Products [page 64]

2.4.1.7 Update Status

The update status of a service product indicates that a service product needs to be reviewed and possibly updated or that the service product is already up to date.

Changes in the underlying transportation network (for example, if new faster routes become available) may affect service products. If these changes affect an existing service product, the update status of the affected service products changes in order to alert the relevant manager (for example, the product manager) to review and, if necessary, update the service products.

The Update Status filter criteria in the Service Product Worklist can be used to search for any service products that have a To Be Updated status and need to be reviewed. Service products can be updated using the Edit Service Product screen or the Mass Update application. If you review service products using the Edit Service Product screen, you must manually set the update status of the service product. Any service products that you review using the Mass Update application are marked as up to date by the system.

When you create a new service product, the system automatically sets the update status on the General Data tab as up-to-date. The system enters the creation date of the service product into the Service Product Update Status Date field and the user logon into the Service Product Updated By field.

Related Information

Setting the Update Status [page 85]Mass Update [page 86]Creation of Service Products [page 64]Service Product Worklist [page 87]


Master Data

2.4.1.7.1 Setting the Update Status

Set a service product as to up-to-date once you have reviewed any possible changes that may have arisen from changes in the transportation network.

Prerequisites

Update statuses have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Product Catalog Define Service Product Update Statuses .

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Change Management and Service Product Catalogs Overview Service Products .

2. Use the Update Status filter criteria in the Service Product Worklist to search for any service products that need to be updated.

3. Open the relevant service product.4. On the Service Product toolbar, choose Edit.5. On the Service Product toolbar, choose Mark as Up-to-Date.

NoteIf the service product is already up-to-date, the Mark as Up-to-Date button is disabled.


Results

The system sets the service product update status as up-to-date. The Service Product Update Status Date field displays the current date, and the Service Product Update Status Updated By field displays your user login. You can view the details of the changes on the Change Documents tab.

Related Information

Update Status [page 84]Mass Update [page 86]Service Product Worklist [page 87]Creation of Service Products [page 64]


2.4.2 Mass Update

The mass update application allows you to analyze system-proposed changes to service products, and accept or reject the changes.

Changes in the underlying transportation network may also lead to changes in multiple service products. If these changes affect any existing service products, the system proposes changes to the service products on a single screen. The mass update application allows you to analyze the proposals for a group of service products and then accept or reject the proposals one-by-one.

Only service products that have an Approved status can be updated using the mass update application.

You can perform the following tasks in the Service Product Mass Update screen:

● View a list of the selected service products● View a side-by-side comparison of the current attributes and the system-proposed updates to the

attributes for each service product● Accept or reject the proposed updates● Open a service product to view detailed information or manually assign routes

Related Information

Performing Mass Updates [page 86]Service Product Worklist [page 87]Attributes [page 74]Route Assignment [page 68]Product Catalog [page 63]

2.4.2.1 Performing Mass Updates

Perform a mass update to review and accept or reject system-proposed updates to service products.

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management and Service Product Catalogs Overview Charge Management and Service Product Catalogs .

2. Enter search criteria to find the relevant service products.3. Select one or more service products in the results table.4. Choose Mass Update.

NoteYou can only perform a mass update on service products that have an Approved status.


Master Data

The system opens the Service Product Mass Update screen, which displays the list of service products that you selected in the worklist results table.

5. Select a service product to view and compare the proposed changes to attributes and routes.

Underneath the results list table, you can view the current attributes and assigned routes and the system-proposed attributes and assigned routes for the selected service product.

6. To accept the proposed updates, choose the Update button.

The system removes processed service product from the results table list.

Related Information

Mass Update [page 86]Attributes [page 74]Route Assignment [page 68]Service Product Worklist [page 87]

2.4.3 Service Product Worklist

The Service Product 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.

You can perform the following tasks in the Service Product Worklist:

● Search for service productsYou can use various criteria such as movement type, trade lane, carrier, and so on to search for service products in the system.

NoteYou must specify the following search criteria:

○ Carrier○ Trade Lane

● Define queries● Create a new service product

You can create a new service product by choosing New on the results table menu.● 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.Call the Mass Update application for selected service products.

For more information, see SAP Library for your SAP NetWeaver release on SAP Help Portal at http://help.sap.com/netweaver. Under Application Help Function Oriented View , open SAP Library and search for Personal Worklist.




Related Information

Mass Update [page 86]Creating Service Products [page 66]


Master Data

3 Basic Settings

Certain basic settings are required in the SAP Transportation Management add-ons for container shipping liners . For example, the setup of the Generic Validation Framework (GVF) as an intermediate layer, which enables a calling object or document to be validated based on a specific rules.

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

Generic Validation Framework [page 89]

3.1 Generic Validation Framework

The Generic Validation Framework (GVF) solution is an intermediate layer that is called by an object or a document in the transportation planning and management system. The main aim of this framework is to validate a calling object or document, based on a group of customized rules.

The calling object or document provides a set of data to the GVF, for example:

● Commodity and location (if called from a booking for prohibitions and restrictions (PnR) or dangerous and hazardous (DnH) checks)

● Origin and destination location pair and mode of transport (if called from a delivery order (DO) for subcontracting)

● Other required information

Having received the set of data and knowing the calling object or document, the GVF identifies the rules that must be executed from the list of available rules. Based on the identified rules, the GVF calls one or more rule engines or data validation systems. In turn, the rule engines or data validation systems execute the predefined rules and return a result for each rule to the GVF. Depending on the executed rule, the result might be a number (such as 17), a text (such as Vessel is overloaded or Approval required for shipping commodity), or a status (such as Passed/Failed). The result is forwarded by the GVF to the calling object or document in the transportation planning and management system. The system may display the result to the user or initiate further (manual or automatic) actions.

The validations are used in the following cases:

● Prohibitions and restrictions checks in bookings● Dangerous and hazardous goods checks in bookings● Release rules for bookings, bills of lading, and delivery orders

SAP Transportation Management, Order to Cash for Container Shipping LinersBasic Settings P U B L I C 89

● Confirmation rules of bookings● Denied party check in bookings and delivery orders

GVF supports rules based on:

● SAP Transportation Management conditions● Business Rules Framework plus● Web services● RFC-enabled function modules

Related Information

Rules Based on SAP Transportation Management Conditions [page 90]Rules Based on Business Rules Framework plus [page 92]Rules Based on Web Services [page 93]Rules Based on RFC-Enabled Function Modules [page 95]

3.1.1 Rules Based on SAP Transportation Management Conditions

SAP Transportation Management conditions can be used as a basis for rules in the Generic Validation Framework (GVF). Such conditions determine input values based on master data or transactional data, and derive output values from the determined input values.

This is a relatively flexible method, which is based on Business Rules Framework plus (BRFplus), but requires less technical knowledge compared to BRFplus rules.

Related Information

Generic Validation Framework [page 89]Defining Rules Based on SAP Transportation Management Conditions [page 91]


Basic Settings

3.1.1.1 Defining Rules Based on SAP Transportation Management Conditions

Within the Generic Validation Framework (GVF), a calling object or document can be validated using rules based on SAP Transportation Management (SAP TM) conditions. You can define these rules in Customizing for Container Shipping Liners.

Prerequisites

● SAP TM conditions for the rules have been defined in SAP NetWeaver Business Client under Application Administration General Settings Conditions Create Condition .

● (Optional) SAP TM conditions for profile determination have been defined in SAP NetWeaver Business Client under Application Administration General Settings Conditions Create Condition

● (Optional) Approval types have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Basic Settings Approval Define Approval Types .

● (Optional) Approval source and consumer have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Basic Settings Approval Define Approval Types Define Approval Source and Consumer .

Procedure

1. Go to Customizing for SAP Transportation Management and choose Container Shipping Liners.

2. (Optional) Define the category and subcategory for rules under Basic Settings Generic Validation Framework Define Category and Subcategory for Rules .

3. Under Basic Settings Generic Validation Framework Define Consumer , perform the following steps:

1. Define a consumer2. (Optional) Define a field group and corresponding fields.3. (Optional) Define a profile or condition for profile determination.4. Define rules based on SAP TM conditions.

4. (Optional) Define the settings for parallelization under Basic Settings Generic Validation FrameworkDefine Setting for Parallelization .

5. (Optional) If the SAP TM condition has an interface that cannot be processed by the delivered BAdI implementation, implement the BAdI under Business Add-Ins (BAdIs) Generic Validation FrameworkBAdI: Execution of GVF Rules .


Related Information

Rules Based on SAP Transportation Management Conditions [page 90]Generic Validation Framework [page 89]

3.1.2 Rules Based on Business Rules Framework plus

Business Rule Framework plus (BRFplus) provides a comprehensive application programming interface (API) and user interface (UI) for defining and processing business rules. It allows you to model rules in an intuitive way and to reuse these rules in different applications.

BRFplus rules can be used as rules in the Generic Validation Framework (GVF).

Related Information

Generic Validation Framework [page 89]Defining Rules Based on Business Rules Framework plus [page 92]

3.1.2.1 Defining Rules Based on Business Rules Framework plus

Within the Generic Validation Framework (GVF), a calling object or document can be validated using rules based on Business Rules Framework plus (BRFplus). You can define these rules in Customizing for SAP Transportation Management under Container Shipping Liners.

Prerequisites

● The BRFplus rules have been defined in the standard transaction BRF+.● (Optional) SAP Transportation Management conditions for profile determination have been defined in SAP

NetWeaver Business Client under Application Administration General Settings Conditions Create Condition .

● (Optional) Approval types have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Approval Define Approval Types .

● (Optional) Approval source and consumer have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Approval Define Approval Source and Consumer .

● (Optional) Data crawler profiles have been defined in Customizing for SAP Transportation Management under Transportation Management Basic Functions Conditions Define Data-Crawler Profile .


Basic Settings

Procedure




1. Define a consumer.2. (Optional) Define a field group and corresponding fields.3. (Optional) Define a profile or condition for profile determination.4. Define data sources.5. Define rules based on BRFplus rules.6. Define input for rules.

4. (Optional) Define the settings for parallelization under Basic Settings Generic Validation FrameworkDefine Settings for Parallelization

5. (Optional) If the BRFplus rule has an interface that cannot be processed by the BAdI implementation delivered, implement the BAdI under Business Add-Ins (BAdIs) Generic Validation Framework BAdI: Execution of GVF Rules .

Results

You have defined rules based on BRFplus rules.

Related Information

Rules Based on Business Rules Framework plus [page 92]Generic Validation Framework [page 89]

3.1.3 Rules Based on Web Services

Web services can be used as rules in the Generic Validation Framework (GVF).

Background

A Web service is an independent, modular, self-describing application function or service. Based on XML and other standards, this application function can be described, made available, located, or called using internet


protocols. Each Web service therefore encapsulates a piece of functionality that can be used, for example, to check the availability of an item in an enterprise resource planning system and so on.

Related Information

Generic Validation Framework [page 89]Defining Rules Based on Web Services [page 94]

3.1.3.1 Defining Rules Based on Web Services

Within the Generic Validation Framework (GVF), a calling object or document can be validated using rules based on Web services. You can define these rules in Customizing for SAP Transportation Management under Container Shipping Liners.

Prerequisites

● The Web service has been defined in the target system.● (Optional) SAP Transportation Management conditions for profile determination have been defined in SAP

NetWeaver Business Client under Application Administration General Settings Conditions Create Condition


● (Optional) Approval source and consumer have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Approval Define Approval Source and Consumer .

Procedure




1. Define a consumer.2. (Optional) Define a field group and corresponding fields.3. (Optional) Define a profile or condition for profile determination.


Basic Settings

4. Define rules based on Web services.

4. (Optional) Define the settings for parallelization under Basic Settings Generic Validation FrameworkDefine Settings for Parallelization

5. (Optional) If the BRFplus rule has an interface that cannot be processed by the BAdI implementation delivered, implement the BAdI under Business Add-Ins (BAdIs) Generic Validation Framework BAdI: Execution of GVF Rules .

Results

You have defined rules based on Web services.

Related Information

Rules Based on Web Services [page 93]Generic Validation Framework [page 89]

3.1.4 Rules Based on RFC-Enabled Function Modules

Within the Generic Validation Framework (GVF), it may be necessary to validate a calling object or document by connecting to another SAP system. In this case, the standard Remote Function Call (RFC) interface can be used. This means that RFC-enabled function modules can be used as rules within the GVF.

Related Information

Defining Rules Based on RFC-Enabled Function Modules [page 96]Generic Validation Framework [page 89]


3.1.4.1 Defining Rules Based on RFC-Enabled Function Modules

Within the Generic Validation Framework (GVF), a calling object or document can be validated using rules based on RFC-enabled function modules, which connect to another SAP system. You can define these rules in Customizing for SAP Transportation Management under Container Shipping Liners

Prerequisites

● The RFC-enabled function module on the target system has been defined in the standard transaction SE37.

● The RFC connection to target systems has been configured in the standard transaction SM59.● (Optional) SAP Transportation Management conditions for profile determination have been defined in SAP

NetWeaver Business Client under Application Administration General Settings Conditions Create Condition .


● (Optional) Approval source and consumer have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Basic Settings Approval Define Approval Source and Consumer .

Procedure




1. Define a consumer.2. (Optional) Define a field group and corresponding fields.3. (Optional) Define a profile or condition for profile determination.4. Define rules based on RFC-enabled function modules.

4. (Optional) Define the settings for parallelization under Basic Settings Generic Validation FrameworkDefine Settings for Parallelization .

5. Implement the BAdI under Business Add-Ins (BAdIs) Generic Validation Framework BAdI: Execution of GVF Rules .


Basic Settings

Results

You have defined rules based on RFC-enabled function modules.

Related Information

Rules Based on RFC-Enabled Function Modules [page 95]Generic Validation Framework [page 89]

3.2 Routing

Routing is the process of determining possible routes between a source and destination location. Routing is integrated with the booking and product catalog application areas.

Related Information

Introduction to Routing [page 97]Routing for Product Catalog [page 103]Routing for Booking [page 115]

3.2.1 Introduction to Routing

Overview of the features involved in the routing process.

The routing process is managed using the following features:

● Process Controller Framework (PCF)For each application that consumes routing, you use the PCF to define routing strategies that consist of process steps. In this way, you model a sequence where each step performs a standalone function.

● Path FinderThe path finder is a standard SAP Transportation Management (TM) tool that determines paths, routes, and reachability within the transportation network. You call the path finder for each routing strategy during the route determination process.

● Route GeneratorThe route generator reads network master data such as SAP TM schedules, transportation lanes, and transportation resources, and provides route proposals that can incorporate any planning settings or restrictions.


These routes are then passed to the calling application (product catalog or booking) which takes over the next steps.

Related Information

Path Finder for Routing [page 101]Route Generator for Routing [page 102]Process Controller Framework for Routing [page 99]

3.2.1.1 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 .

● A B D .

● A D .

● A B 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.2.1.2 Routing: Integration

Routing is integrated with the booking and product catalog application areas.

When you create a booking, you can generate route proposals for a combination of source and destination location. The route generator is called by the Voyage Suggestion Framework (VSF).


Basic Settings

For bookings and service products, the route generator behaves differently depending on whether or not you have installed SAP Transportation Management, network and operations for container shipping liners, as follows:

● Is InstalledThe route generator uses the enhanced schedules from SAP Transportation Management, network and operations for container shipping liners to find route proposals.

● Is Not InstalledThe route generator uses the standard schedules from SAP Transportation Management to find route proposals.

Related Information

Routing [page 97]

3.2.1.3 Process Controller Framework for Routing

You use PCF strategies for routing to define the planning steps that the system performs, along with the sequence in which they are performed. Each strategy is comprised of one or more methods that represent the individual planning steps.

The process controller framework (PCF) allows you to define application processes that consist of process steps. The PCF is made up of the following building blocks:

PCF Entity Description

Service Defines the strategies and process steps working on the same process.

Strategy Defines and orders the process steps to be executed

Method Realizes a single process step. Each process has a method pool with all methods, which the application process requires in order to define its strategies. ABAP-OO classes – also called application classes – provide the implementation of the methods.


PCF Entity Description

Controller Entry point for triggering the execution of the application processes. The controller determines the methods for the service-strategy combination and calls them according to their predefined order. Parameters can be passed to the controller, which forwards them to the methods.

These parameters influence the behavior of the respective methods, but do not change the sequence in which the methods are executed. A parameter can have different values in different methods, and in addition, the same method as part of different strategies, or even in the same method of the same strategy as part of different requests.

Method execution by the controller works dynamically, since the definition of a new method includes the name of the providing application class, which is instantiated by the controller before executing a method. The results produced by a method are either passed on to all succeeding methods with the corresponding requests, or they are stored externally.

Request Represents the various business demands (for example, the determination of a best route) on an application process. The controller processes the requests by passing them on to the strategy methods through their interfaces. The requests may further allow the storing of possible solutions.

Related Information

Routing [page 97]Routing: Integration [page 98]Route Generator for Routing [page 102]Path Finder for Routing [page 101]

3.2.1.3.1 Routing Strategies in Process Controller

Routing uses the strategies for booking and product catalog that have been defined in the process controller framework.

You define routing strategies Customizing for SAP Transportation Management under SCM Basis Process Controller . At runtime, the strategy is executed according to the method sequence you have assigned to it in Customizing.


Basic Settings

Routing uses different strategies and methods for the different application areas as follows:

Application Area Strategy Strategy Description

Product Catalog ROUT_PRC Solution Builder for Product Catalog

Booking ROUT_BOOK Solution Builder for Booking

The process controller service CSL_ROUT is available as the common service for routing strategies.

Routing also uses the following defined workbench objects:

● A method pool that is a friend of class /SCTM/CL_CONTROLLEREach of the methods of the method pool are comprised of the business logic to carry out tasks in the individual strategy steps.

● A class for the request objectThis is used to store data. You can access an instance of the request object in all the methods of the method pool created above. The class is inherited from class /SCMTMS/CL_TM_REQUEST

Related Information

Process Controller Framework for Routing [page 99]

3.2.1.4 Path Finder for Routing

The path finder is a standard SAP Transportation Management (TM) tool that is used in the routing process to determine connections within a source location and a destination location.

The path finder 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 path finder for each routing strategy during the route determination process. The logic works as follows:

1. The path finder 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, 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 path finder takes into consideration any restrictions related to opening times and non-working days for the locations.

3. The path finder 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 path finder 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 path finder can shift these lanes connected to and from a schedule to fit to the schedule milestones.

NoteFor the routing strategies of booking, the system only uses the path finder if a service product is not matched during route determination.

Related Information

Routing [page 97]Routing: Integration [page 98]Route Generator for Routing [page 102]Process Controller Framework for Routing [page 99]

3.2.1.5 Route Generator for Routing

The route generator is an application programming interface (API) that provides a set of ranked route proposals from a specific source location to a specific destination location.

You call the route generator API to provide a set of route proposals for a service product or booking.

The route proposals are ranked from the most favorable to the least for a given input set. The API works as follows:

1. Based on the routing consumer type, the system creates a request object.2. Attributes of this request object are populated with information supplied by the user.3. This request object is passed on to the process controller framework (PCF).4. The PCF executes the strategy methods in a sequence defined for the strategy in question (product

catalog or booking).5. The request object is passed on from one method to another method and stores updated information

during the entire process flow.6. After all the strategy methods have been executed, information from the request object is captured in the

output table.


Basic Settings

The route generator considers the following when searching for and returning the route proposals:

Consideration Description

Drayage 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.

Restrictions Routing restrictions with respect to the mode of transport, or legal and commercial rules, are considered.

Dates Routes can be dated or undated. A dated route has specific departure and (estimated) arrival dates. Undated routes are only bound to a validity interval. Within this interval, departure and arrival can happen at several points in time. For example, departure once a week and arrival after an estimated transit time.

Validations Routes are validated using Generic Validation Framework (GVF) rules that have been maintained in Customizing.

Ranking and Weighted Score Routes are ranked based on a weighted score. The weighted score is calculated based on certain parameters such as cost, distance, or duration. The best-ranked routes are then proposed as a result by the route generator API. Routes that are ranked as invalid, or negatively ranked routes, can be discarded, since these routes do not make business sense.

Related Information

Routing [page 97]Routing: Integration [page 98]Path Finder for Routing [page 101]Process Controller Framework for Routing [page 99]

3.2.2 Routing for Product Catalog

Routes are generated for service products in a product catalog that operate between a source location and a destination location.

You use a product catalog to capture the set of service products (such as cleaning, refrigeration, loading and unloading, and so on) that you make available to your customer. The route generator allows you to generate ranked route proposals (most favorable to the least) for a service product between a source and destination location combination. You can reduce the number of route proposals returned by maintaining specific Generic Validation Framework (GVF) rules.


You can generate route proposals for a service product as follows:

● From the New Service Product and Edit Service Product screens in SAP NetWeaver Business Client● With the Solution Builder for Product Catalog report in the SAP Transportation Management system

Related Information

Routing Strategy for Product Catalog [page 106]Route Generator API for Product Catalog [page 108]

3.2.2.1 Example: Finding Routes for a Service Product

Finding routes for a service product between the source location and the destination location.

In this example, there are several possible routes, incorporating various paths, from Shanghai to Rotterdam. When you call the route generator application programming interface (API) from the New Service Product screen, all of the possible path combinations for the source location (Shanghai) to the destination location (Rotterdam) are provided.

Note● A route consists of a sequence of stages, where each stage is an independently operated transportation

service. For example, a shipping line, a rail line, or a truck can be a stage.● Each stage has one or more modes of transport such as shipping, rail, truck, or barge.● The path indicates the number of stages it takes to travel from the source location to the destination.

The total number of route solutions for one path is the product of the number of modes of transport of all the stages. The total number of route proposals returned is the sum of route solutions for all of the different paths.

Door to Door

If a door to door movement type is to be provided, for example, there would be seven stages and the path would look as follows:

Stage Description Type Modes of Transport Number of Modes of Transport

1 Door to warehouse Pickup Rail 1

2 Warehouse to source port

Pre-carriage Rail and air 2

3 Source port to transshipment port terminal 1

Main-carriage Sea 1


Basic Settings


4 Transshipment port terminal 1 to transshipment port terminal 2

Drayage Road 1

5 Transshipment port-terminal 2 to destination port

Main-carriage Sea 1

6 Destination port to warehouse

On-carriage Rail and air 2

7 Warehouse to door Delivery Road and rail 2

The total route solutions for the seven-stage path equals the product of modes of all the stages. Here, there are eight possible ways of movement, based on the combinations of available connections, for a door to door movement type from Shanghai to Rotterdam.

Port to Port

If a port to port movement type from the source port (Shanghai) to the destination port (Rotterdam) is to be provided, no drayage is necessary. In that case, the path has only five stages, as follows:


1 Door to warehouse Pickup Rail 1


Pre-carriage Rail and air 2

3 Source port to destination port

Main carriage Sea 1


On-carriage Rail and air 2

5 Warehouse to door Delivery Road and rail 2

The total route solutions for the five-stage path equals the product of modes of all the stages. Here, there are eight possible ways of movement, based on the combinations of available connections, for a port to port service from Shanghai to Rotterdam.

Total Number of Route Proposals

Overall, the total number of route proposals = equals the sum of route solutions for all different paths.In this example, the total route proposals are derived as follows:

total route proposals = 8 (door-to-door) + 8 (port-to-port) = 16

Similarly, if alternative paths are available, the possible ways of movement increase.


Related Information

Routing for Product Catalog [page 103]

3.2.2.2 Routing Strategy for Product Catalog

You can define a strategy and assign methods in the process controller framework (PCF) to model the routing process for the product catalog.

For the routing strategy for Product Catalog, you use the strategy ROUT_PRC. You assign the following methods to this strategy, to be executed in the following sequence:

Execution Sequence Method Name Logic

1 Dynamic Routing with Path Finder in Product Catalog (ROUT_BK_PF)

Calls the path finder function module to get all available paths and route proposals for a service product. The method does not query the available service products, but instead builds routes dynamically from the available connections.

Further filtering takes place based on the carrier and the required number of transshipments. You can also use the method to define certain routing constraints that the system can check while building the route.

2 Determine Additional Data for Routes in PRC (ROUT_AD_PC)

Filters routes based on modes of transport (MoTs) on the import and export side.

3 Determine Departure Frequency for PRC (ROUT_DF_PC)

Calculates the transit time for each route proposal and filters according to the maximum transit days required. The method also calculates departure days.


Basic Settings


4 Calculate Validity Periods for PRC

(ROUT_VP_PC)

Filters out routes based on the required validity periods. The method checks whether the routes are valid within the specified validity period. If the route proposal validity ends prior to the requested starting validity date, the route proposal is invalid. Similarly, if route proposal validity starts after the required validity end date, the route proposal is made invalid.

5 Aggregate Routes for Product Catalog (ROUT_AG_PC)

Filters out routes based on conditions such as the preferred line study.

By default, the system retains only the schedules of the preferred line study. If a user parameter is set, no filtering takes place, and all routes that contain the line study schedules are returned.

6 Call Generic Validation Framework for PRC (ROUT_GF_PC)

Calls the Generic Validation Framework (GVF) to filter out route proposals based on rules you have set, for example:

● You can set a rule that removes certain locations from consideration if these locations do not allow specific types of goods.

● You can set a rule to make certain locations active for a specific period of time.

Based on these rules, the routes are validated and filtered.

7 Filter Routes by Cargo Types for PRC (ROUT_CT_PC)

Filters routes based on the cargo types (for example, break bulk, dangerous goods, and so on) allowed by the locations.

8 Retrieve Cost (ROUT_BK_RC) Calculates the costs for the stages and routes, based on the rates maintained for the location combination, vessel, and so on.



9 Calculate Ranks for Routes for PRC (ROUT_RK_PC)

Ranks the routes according to the number of transshipments, transit days, and so on. If the ranking takes place according to the cost of the route, you must change the ABAP class assignment for the combination of use case and sub-use case.

The weighted rank is calculated based on transshipments and transit days as follows:

● Weightage: The percentage of preference given for transshipment and transit duration

● Score: Based on number of stages and duration, scores are given by reading the custom decision table defined within the interface method

● Weighted Score = Weightage * Score

Related Information

Routing for Product Catalog [page 103]Route Generator API for Product Catalog [page 108]

3.2.2.3 Route Generator API for Product Catalog

The routing application programming interface (API) for the product catalog searches for and returns ranked route proposals for a source and destination combination for a service product.

You can call the routing API for the product catalog from either the New Service Product screen in SAP NetWeaver Business Client or by using the Solution Builder for Product Catalog report in the SAP Transportation Management system.

API Interface

The API class /TMCSL/CL_ROUT_PRODUCT_CAT contains the method /TMCSL/IF_ROUT_CONSUMER~GET_ROUTE_PROPOSALS that returns all of the route proposals for the supplied input


Basic Settings

set. All of the messages are stored in a message object. The relevant parameters for the route proposals are as follows:

Input Parameters (Input Details) Output Parameters (Route Proposals) Changing Parameters (Message Object)

IT_ROUTE_PROP_INPUT ET_ROUTE_PROP_SOLN CO_MESSAGE

3.2.2.3.1 Generating Routes with the Solution Builder for Product Catalog Report

Generate all possible route proposals for a combination of source and destination location with this report.

Prerequisites

● A strategy has been defined for the product catalog in Customizing for SAP Transportation Management under SCM Basis Process Controller .

● GVF rules have been defined for the product catalog in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Generic Validation Framework .

● Ranking has been defined for the service product catalog in Customizing for SAP Transportation Management Container Shipping Liners Basic Settings Ranking .

● Routing parameters for the solution builder have been defined in Customizing for SAP Transportation Management under Container Shipping Lines Basic Settings Routing Maintain Routing Parameters for Solution Builder .

Procedure

1. In the SAP Transportation Management system, start transaction SE38 and execute the Solution Builder for Product Catalog report (/TMCSL/ROUT_PROD_CATALOG_SOLN).

2. Enter the following data in the report screen:

Field What to Do

Strategy Name Enter a strategy. The process controller executes the methods assigned to the entered strategy.

GVF Consumer Code Enter the code used to fetch the relevant GVF rules to execute.


Field What to Do

Max Rank 1st Select this radio button to indicate that routes with top rank are displayed first.

Min Time 1st Select this radio button to indicate that routes with a minimum transit duration are displayed first.

Max Time 1st Select this radio button to indicate that routes with a maximum transit duration are displayed first.

Min Dist 1st Select this radio button to indicate that routes with a minimum transit distance are displayed first.

Max Dist 1st Select this radio button to indicate that routes with a maximum transit distance are displayed first.

Request Key Enter the request key 1. In product catalog, you can only request route proposals for one location combination, that is, for one input set. Here, the request key is 1, which indicates 1 set.

Source Location Enter the location from where the movement starts.

Destination Location Enter the location where the movement ends.

Movement Type Enter a movement type. The movement type depends on the location type of the source and destination. For example, if the source is a customer location and the destination is a terminal, the movement type will be DP (Door to Port).

Valid From Enter a validity range. Only routes valid in the date range specified here are selected.

Valid To

Location Sequence Specify the location sequence to be followed.

Included/Excluded Locations Enter locations to be included or excluded. Included locations means that only routes covering these locations are displayed, and excluded locations means that routes covering these locations are not displayed.

Include/Exclude MOT Export Export side (stages before first ocean stage)

Enter modes of transport on the export side to be included or excluded. Included MOTs means that only routes with these MoTs are displayed, and excluded MOTs means that routes without these MoTs are not displayed.


Basic Settings

Field What to Do

Include/Exclude MOT Import Import side (stages after last ocean stage)

Enter modes of transport on the import side to be included or excluded. Included MOTs means that only routes with these MoTs are displayed, and excluded MOTs means that routes without these MoTs are not displayed.

Carrier Id Enter a carrier ID. Only routes with schedules belonging to the specified carrier are displayed.

Brand Id Enter a brand ID and a trade ID. Routes are populated with the ID value specified, though the system does not filter routes by ID value.Trade Id

Maximum Routes Enter the maximum number of routes to be displayed.

Maximum Transshipment Enter the maximum number of transshipments to be displayed.

Maximum Transit Days Enter the maximum number of transit days. Only routes with a transit duration less than or equal to the specified days are displayed.

Search Depth (Explicit) Enter the search depth for path finder restrictions.

Search Depth (Implicit) Enter the search depth for path finder restrictions.

Max no of Solutions Enter the maximum number of paths to be displayed from the Path Finder..

Dangerous Goods Select this checkbox to indicate that only routes that allow dangerous goods shall can be displayed.

Reefer Select this checkbox to indicate that only routes that allow reefer goods shall be displayed.

OOG (out of gauge) Select this checkbox to indicate that only routes that allow out-of- gauge goods shall be displayed.

Show GVF Excluded Routes Select this checkbox to indicate that routes that fail the GVF rules can be displayed.

Show Ranking Excluded Routes Select this checkbox to indicate that routes that fail the ranking rules can be displayed.


The route generator application programming interface (API) searches for and returns routes that are consistent with the input set.


Results

A list of ranked proposed routes and stages is displayed. The top node (Solution For) represents the input set number, with the route proposals of the input set listed under the second node and the respective stages of the route proposal listed under the third node.

Related Information

Generating Routes from the New Service Product Screen [page 112]Generating Routes from the Edit Service Product Screen [page 114]

3.2.2.3.2 Generating Routes from the New Service Product Screen

Generate route proposals for a combination of source and destination location from the New Service Product screen in SAP NetWeaver Business Client.

Prerequisites

● A strategy has been defined for the product catalog in Customizing for SAP Transportation Management under SCM Basis Process Controller .

● GVF rules have been defined for the product catalog in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Generic Validation Framework .

● Ranking has been defined for the product catalog in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Ranking .

● A broken trip is visible in the trip plan issue list in SAP NetWeaver business client.

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Charge Management and Service Product Catalogs Service Product Catalogs Create Service Product Catalog.

The system displays the New Service Product screen.2. On the General Data tab, enter the following details:


Basic Settings

Field What to Do

Service Product Description Enter a description for the service product.

Carrier Enter a carrier ID for the service product.

Trade Lane Enter a trade lane ID for the service product.

Movement Type Enter a movement type for the service product. The possible values are Door to Door, Port to Port, Door to Port, and Port to Door.

Source Location Enter a source location ID for the service product.

Destination Location Enter a destination location ID for the service product.

Valid From Enter a valid-from date for the service product.

Valid To Enter a valid-to date for the service product.

Publication Select this checkbox to ensure that the service product is valid for publication.

Publication From Enter a publication-from date for the service product.

Publication To Enter a publication-to date for the service product.

Publication Type Select a publication type for the service product. The possible values are Public and Private.

3. Save your entries.4. On the Routes tab, choose one of the following options:

○ To generate the route proposals for the newly created service product, choose Routes Generate .○ To generate the route proposals and assign them to the newly created service product, choose

Routes Generate and Assign .

The routing engine application programming interface (API) searches for and returns routes that are consistent with the input set.

Results

A list of ranked proposed routes and stages is displayed in the Proposed Routes table. You can view the stages for each proposed route by expanding the nodes.

Related Information

Generating Routes from the Edit Service Product Screen [page 114]


3.2.2.3.3 Generating Routes from the Edit Service Product Screen

Generate route proposals for a combination of source location and destination location from the Edit Service Product screen in SAP NetWeaver Business Client.

Prerequisites

At least one service product exists in SAP NetWeaver Business Client.

Procedure

1. In SAP Netweaver Business Client, choose Master Data Charge Management and Service Product Catalogs Service Product Catalogs Edit Service Product Catalog .

The system displays the Edit Service Product screen.2. Enter a service product ID for an existing service product and choose Continue.

The system displays the General Data tab with the saved details of the service product.3. On the Routes tab, choose one of the following options:

○ To generate the route proposals for the newly created service product, choose Routes Generate .○ To generate the route proposals and assign them to the newly created service product, choose

Routes Generate and Assign .The route generator application programming interface (API) searches for and returns routes that are consistent with the input set.

Results

A list of ranked proposed routes and stages is displayed in the Proposed Routes table. You can view the stages for each proposed route by expanding the nodes.

Related Information

Generating Routes from the New Service Product Screen [page 112]Generating Routes with the Solution Builder for Product Catalog Report [page 109]


Basic Settings

3.2.3 Routing for Booking

During the booking process, you can generate suitable route proposals to match the requirements of a booking. The system supports different booking scenarios, including part-load bookings

The booking process captures customer requests for shipments. You can use the route generator to find the available routes that match an existing booking in SAP NetWeaver Business Client. The route proposals returned by the route generator have executable voyages that are valid for the date range requested for the booking. The routing process for booking carries out the following tasks:

● Calls the route generator API as follows, depending on the functions you have installed:

Function Installed Route Generator

Network and Operations The route generator API is called from the Solution Builder for Booking report in the SAP Transportation Management system.

Order to Cash and Network and Operations The route generator API is called from the Voyage Suggestion Framework (VSF). Since voyages are maintained in the line and line study, route proposals are based on line study voyages.

Order to Cash The route generator API is called from the Voyage Suggestion Framework (VSF). Since there are only standard schedules and voyages, route proposals are based on the standard schedule management entities.

● Searches for a valid service productSince routing consumes service products, the route generator behaves as follows:○ If it finds a valid service product that matches the booking’s details (it has the same source location,

destination location, and so on), the route generator uses the routes assigned to a service product○ If no service product is found, the route generator uses the path finder tool to determine routes for the

booking.

Related Information

Generating Routes with the Solution Builder for Booking Report [page 121]

3.2.3.1 Example: Finding Routes for Booking

Finding routes for a booking.

In this example, a booking exists in the SAP NetWeaver Business Client to move cargo from Rotterdam to Shanghai. There are several possible routes for this movement, incorporating various paths, from Rotterdam to


Shanghai. When you call the route generator application programming interface (API) from the Create or Edit Booking screen in SAP NetWeaver Business Client, all of the possible path combinations for the source location (Rotterdam) to the destination location (Shanghai) are provided.

Note● A route consists of a sequence of stages, where each stage is an independently operated transportation

service. For example, a shipping line, a rail line, or a truck can be a stage.● Each stage has one or more modes of transport, such as shipping, rail, truck, or barge.● The path indicates the number of stages it takes to travel from the source location to the destination.● The total number of route solutions for one path is the product of the number of modes of transport of

all the stages. The total number of route proposals returned is the sum of route solutions for all of the different paths.

Door to Door

If a door to door movement type is to be provided, for example, there would be five stages and the path would look as follows:


1 Door to warehouse Pickup Road and rail 2


Pre-carriage Air, road and rail 3


Main-carriage Sea 1


On-carriage Road and rail 2

5 Warehouse to door Delivery Road 1

The route generator finds combinational paths by breaking down the movement as follows:

● If the total number of route solutions for one path is the product of the number of modes of transport of all the stages, then for the door to door movement type there are 12 possible ways of movement (2x3x1x2x1 =12)

● For each possible connection, the route generator finds executable voyages within the ETD and ETA requested in the booking.

Port to Port


Basic Settings

If a port to port movement type from the source port (Rotterdam) to the destination port (Shanghai) is to be provided, the path has one stage, as follows:



Main-carriage Sea and rail 2

The route generator finds combinational paths by breaking down the movement as follows:

● If the total number of route solutions for one path is the product of the number of modes of transport of all the stages, then for the port to port movement type there are two possible ways of movement (2x1=2).

● For each possible connection, the route generator finds executable voyages within the ETD and ETA requested in the booking.

Related Information

Routing for Booking [page 115]

3.2.3.2 Routing Strategy for Booking

You can define a strategy and assign methods in the process controller framework (PCF) to model the routing process for bookings.

For the routing strategy for bookings, you use the strategy ROUT_BOOK. You assign the following methods to this strategy, to be executed in the following sequence:

Sequence Position Method Name Logic

1 Search for Product (ROUT_BK_PS) Searches for service product catalogs for a given booking. If found, the system prepares route and stage information based on the dated voyages.



2 Dynamic Routing with Path (ROUT_RP_PF)

Searches for legs in your transportation network and takes the following into account in the process:

● Transportation zones● Locations● Transshipment locations● Transportation lanes● Schedules

This enables you to easily determine whether a connection exists between two locations. It also filters route proposals by mode of transport (MoT), location sequence, and routing constraints (for example, No Inland Arrival / Departure in Port scenario). In addition, it filters route proposals by carrier and transshipment details.

Call Catalog Mapper(ROUT_RP_CM) Checks for existing service product catalogs for the given source and destination during booking creation. If found, the system maps the route with the service product and prepares route and stage information. If none are found, the system considers the result (the route and stage information) of the path finder tool. Based on this route and stage information, the system creates a stage combination and search input which it maps with the location hierarchy to find a corresponding terminal, ramp-door, customer, and so on. Next, the system checks if any service product catalogs exist for the given search input criteria. If any exists, the system maps the route with the service product.

Finally, the system provides route and stage information and filters this route and stage information based on the carrier and brand.


Basic Settings


3 Enhance Routes with Dates (ROUT_RP_DT)

Gets all valid transportation lanes and dated voyages based on the source and destination, and maps this data with route and stage information.

4 Determine POL and POD Determines the port of loading (POL) and port of discharge (POD) for a specific route. For the purpose of this method, the POL is the first ocean stage on the export side, and the POD is the last ocean stage on the import side. For example, consider a cargo movement that takes place from A->E with the location call sequence A-> B-> C-> D->E, where the following stage-MoT combinations apply:

● A->B (Rail)● B->C (Sea)● C->D (Sea)● D->E (Road)

In the above sequence, if B-D is the main-carriage, then the locations before B are the export side and the locations after D are the import side. Therefore, B is the POL (where the first ocean stage on the export side starts) and D is the POD (where the last ocean stage on the import side ends).

5 Retrieve Cost (CSL_ROUT) Estimates the costs and currencies of each route and stage information.

Related Information

Routing for Booking [page 115]Route Generator API for Booking [page 120]


3.2.3.3 Route Generator API for Booking

The route generator application programming interface (API) for booking searches for and returns route proposals with executable voyages that are valid within the timeframe requested in the booking.

You call the route generator API for booking in different ways, depending on the functions you have installed. For bookings, you can call the route generator as follows:

Function Installed Route Generator

● SAP Transportation Management, network and operations for container shipping liners

● SAP Transportation Management, order to cash for container shipping liners

Call from the Create/Change Booking screen in SAP NetWeaver Business Client

● SAP Transportation Management, network and operations for container shipping liners

Call by executing the Solution Builder for Booking report in the SAP Transportation Management system

API Interface

The API class /TMCSL/CL_ROUT_BOOKING contains the method /TMCSL/IF_ROUT_CONSUMER~GET_ROUTE_PROPOSALS that returns all the route proposals for the input set supplied. All messages are stored in a message object. The parameters for the route proposals are as follows:

Input Parameters (Input Details) Output Parameters (Route Proposals) Changing Parameters (Message Object)

IT_ROUTE_PROP_INPUT ET_ROUTE_PROP_SOLN CO_MESSAGE

Related Information

Routing Strategy for Booking [page 117]


Basic Settings

3.2.3.3.1 Generating Routes with the Solution Builder for Booking Report

Generate route proposals between a source and a destination location to match the requirements of a the booking.

Prerequisites

● A booking strategy has been defined in Customizing for SAP Transportation Management under SCM Basis Process Controller .

● Routing parameters for the solution builder have been defined in Customizing for SAP Transportation Management under Container Shipping Lines Basic Settings Routing Maintain Routing Parameters for Solution Builder.

● A booking exists in the SAP NetWeaver Business Client.

Context

You can use this report for an existing booking to generate all possible route solutions between the source and the destination locations.

NoteYou can use the report’s parameters to restrict the number of returned route proposals by filtering for specific criteria such as mode of transport (MoT) on the import side and export side, number of transshipments, and so on. However, the Solution Builder for Booking report does not check Generic Validation Framework (GVF) rules or provide ranked route proposals.

Procedure

1. In the SAP Transportation Management system, start transaction SE38 and execute the Solution Builder for Booking report (/TMCSL/ROUT_BOOKING).

2. Enter the following data in the report screen:

Field What To Do

PCF Strategy Enter the strategy ROUT_BOOK.

Booking ID Enter a booking ID.


Field What To Do

Mode of Transport Import Specify specific MoTs on the import side if you want the system to display routes with these modes. You can include or exclude MoTs.

Mode of Transport Export Specify specific MoTs on the export side if you want the system to display routes with these modes. You can include or exclude MoTs.

Port of Loading Enter the port of loading on the export side that has the sea as the first ocean stage in a location sequence.

Port of Discharge Enter the port of discharge on the import side that has the sea as the last ocean stage in a location sequence.

Location sequence Specify the location sequence that has to be followed. For example, in a location sequence A->B->C->D->E, if you enter C and D , the system displays only the route proposals that pass through C first and D next.

Connection Type Specify a particular connection type (such as S or L). The system displays only the route proposals with the connection type you enter here.

Transshipment Number Specify the number of transshipments you wish the route to have. You can restrict the number of returned route proposals this way. For example, if you enter the value 2 for this field, the system displays only route proposals with two or less transshipments.

Min Time 1st Select this radio button to ensure that routes with a minimum transit duration shall be displayed first.

Max Time 1st Select this radio button to ensure that routes with a maximum transit duration shall be displayed first.

Min Dist. 1st Select this radio button to ensure that routes with a minimum transit distance shall be displayed first.

Max Dist. 1st Select this radio button to ensure that routes with a maximum transit distance shall be displayed first.


The route generator application programming interface (API) searches for and returns routes that are consistent with the input set.


Basic Settings

Results

You have generated a list of proposed routes and stages that match the details in the booking. The route proposals of this input set are listed in the top node, with the respective stages of the route proposal listed under the second node.

Related Information

Route Generator API for Booking [page 120]Route Proposal Generation [page 231]

3.3 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 Application Server System Administration Data Archiving Archiving Object-Specific Customizing .

We provide the following archiving objects with the appropriate settings:

Business Object Archiving Object Documentation

Partner and Location Profile /TMCSL/PLP Archiving Partner and Location Profile Documents [page 131]

Booking

Bill of Lading

SCMTMSTRQ Enhanced Archiving Business Documents for FWM [page 129]

You can also extend the archiving objects for SAP Transportation Management, order to cash for container shipping liners to suit 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 SAP Easy Access Tools AdministrationSARA Data Archiving .

You can use the following features in transaction SARA:

● PreprocessingWe 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.


NoteYou define the residence period in the document type Customizing for documents of the archiving object SCMTMSTRQ. For the archiving object /TMCSL/PLP, you define the residence period in Customizing for Cross-Application Components under Processes and Tools for Enterprise Applications

Reusable Objects and Functions for BOBF Environment Archiving Adapter Maintain BO-specific Residence Periods .

NoteFor the archiving object /TMCSL/PLP, the CHECK_ARCHIVABILITY action sets business documents only to archiving status Archiving in Process if the partner and location profile document is deactivated.

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.

● WritingThe 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.

● DeletingThe system deletes all records that are archived from the registered database tables.

● Deleting from ArchiveAll SAP Transportation Management (SAP TM) archiving objects are ILM-enabled. For more information about SAP Information Lifecycle Management (SAP ILM), see http://help.sap.com/erp . Choose your version 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 SAP TM screens. The system uses only the display mode for these archived documents. We provide each business object in SAP TM with the following settings:

● Individual archiving object● Archiving status

Statuses include Not Archived, Archiving in Process, and Archived.● CHECK_ARCHIVABILITY action● 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 Solution Life Cycle Management Data Archiving Data


Basic Settings

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Ferp

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnw

Archiving in the ABAP Application System Data Archiving with Archive Development Kit (ADK) 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 Solution Life Cycle Management Data Archiving Data Archiving in the ABAP Application System Data Archiving with Archive Development Kit (ADK) Archive Administration Tables and Archiving Objects .

Related Information

Why Archive? [page 125]Prerequisites for Archiving [page 126]

3.3.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 SAP Transportation Management (SAP 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 Solution Life Cycle Management Data Archiving Data Archiving in the ABAP Application System Data Archiving with Archive Development Kit (ADK) Archive Information System .




Related Information

Archiving [page 123]

3.3.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 document in Customizing for Cross-Application Components under Processes and Tools for Enterprise ApplicationsReusable Objects and Functions for BOPF Environment Archiving Adapter Maintain BO-Specific Residence Periods :

● Partner and location profile

You must specify the residence period for any remaining business documents in the Customizing activity for the individual business object type. The following table describes these Customizing activities:

Business Object Customizing Activity

Booking

Bill of Lading

Transportation Management Forwarding Order

Management Forwarding Order Define Forwarding Order

Types

You can review the archiving objects that we have assigned to the business objects 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 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 123]Archiving for Master Data Objects [page 127]


Basic Settings

3.3.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 SAP Transportation Management (SAP TM). As a result, only a limited number of master data objects can be archived.

Related Information

Archiving [page 123]Where-Used Check for Objects [page 127]

3.3.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) Partner and location profile (/TMCSL/PLP)

Location (APOLOC) Partner and location profile (/TMCSL/PLP)


Related Information

Archiving for Master Data Objects [page 127]Performing a Where-Used Check [page 128]

3.3.3.2 Performing a Where-Used Check

You can perform a where-used check for most master data objects.

Context

The following master data objects can be included in the check:

● Locations● Business Partner

Procedure

1. On the SAP Easy Access screen, choose SAP Transportation Management SCM Basis Master DataGeneral Master Data Functions 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 location ID in a location 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 Partner and Location Profile for a location.

Results

The system displays the where-used information for the hosting object you select.

Related Information

Where-Used Check for Objects [page 127]Archiving for Master Data Objects [page 127]


Basic Settings

3.3.4 Archiving for Business Objects

The following are the archiving object and business object combinations you can use in SAP Transportation Management, order to cash for container shipping liners. You can use transaction SARA (Archive Administration) to perform the archiving.

Business Object Archiving Object Documentation

Booking

Bill of Lading

SCMTMSTRQ Enhanced Archiving Business Documents for FWM [page 129]

Partner and Location Profile /TMCSL/PLP Archiving Partner and Location Profile Documents [page 131]

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: Function-Oriented View, and choose Solution Life Cycle Management Data Archiving Data Archiving in the ABAP Application System Data Archiving with Archive Development Kit (ADK) Archive Information System .

Related Information


3.3.4.1 Enhanced Archiving Business Documents for FWM

SAP Transportation Management, order to cash for container shipping liners reuses the archiving object SCMTMSTRQ for archiving and deleting the booking and bill of lading business documents.

The majority of functions are the same as the standard function in SAP Transportation Management (SAP TM) for archiving business documents for forwarding order management (TM-FWM) and transportation requests (TM-ERP-TR).

NoteIn the option for container shipping liners, you set the end of business (which means the documents are completed in the context of data protection and privacy) for a booking or bill of lading in one of the following ways:

● When the bill of lading has the status Import Finalized, you complete the booking and bill of lading by running the report /SCMTMS/RECALC_TRQ_STATUS.




● Discard bookings that are relevant to the container shipping liners option. The system discards the bills of lading at the same time.

Dependencies

Before archiving a booking or bill of lading document, the system checks the following in associated objects:

● Freight units or container units are available for archiving.● Other relevant documents in the document flow (for example diversion requests) are available for

archiving.

More Information

Subject More Information

Archive Information System SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw . Choose your release. Under Application Help for Function-Oriented View, open SAP Library and choose

Solution Life Cycle Management Data Archiving Data

Archiving in the ABAP Application System Data Archiving with

Archive Development Kit (ADK) Archive Information System

Define Forwarding Order Types Customizing activity Customizing for Transportation Management under Forwarding

Order Management Forwarding Order Define Forwarding Order

Types

Archiving Business Documents for FWM (TM-FWM) and TR (TM-ERP-TR)

See SAP Library for SAP Transportation Management on SAP Help Portal at https://help.sap.com/tm . Choose your release. Under

Application Help, open SAP Library and choose Basic Functions

Archiving in SAP Transportation Management (SAP TM)

Archiving Objects for Business Objects Archiving Business

Documents for FWM (TM-FWM) and TR (TM-ERP-TR) .

Related Information

Archiving for Business Objects [page 129]Archiving [page 123]


Basic Settings



https://help.sap.com/tm

3.3.4.2 Archiving Partner and Location Profile Documents

You can use the archiving object /TMCSL/PLP to archive and delete partner and location profile (PLP) documents.

Structure

Tables

SAP Transportation Management, order to cash for container shipping liners uses the archiving object /TMCSL/PLP to archive data from the nodes of the business object model /TMCSL/PLP.

Programs

The following programs are available for /TMCSL/PLP:

Program Function

/TMCSL/ARCH_PLP_PRE Preprocessing

/TMCSL/ARCH_PLP_WRI Write

/TMCSL/ARCH_PLP_DEL Delete

Prerequisites for Writing Partner and Location Profile Documents

If the following prerequisites are met, the system can archive a partner and location profile document:

● The document was in the database for the entire residence period.● The document has an end-of-business status of Deactivated.● The document 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 firstly whether the non-archived objects are completed and secondly whether their residence period has been reached. The archiving objects are given the archiving status Archiving in Process if they fulfill these prerequisites.

The Write function saves all archiving objects that have the status Archiving in Process in an archiving document.

NoteYou cannot edit an archived document on the NWBC screens or execute any actions or activities for it.


Integration

Dependencies

The system sets the archiving status Archiving in Process for partner and location profile documents during preprocessing.

Displaying Archived Schedules

You can use the field catalog /TMCSL/PLP and archive information structure /TMCSL/PLP to access archived partner and location profile documents using the Archive Information System. The system archives partner and location profile documents that have an end-of-business status of Deactivated.

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 for Function-Oriented View, open SAP Library and choose Solution Life Cycle Management Data Archiving Data Archiving in the ABAP Application System Data Archiving with Archive Development Kit (ADK) Archive Information System .

Related Information

Archiving for Business Objects [page 129]Archiving [page 123]

3.3.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, order to cash for container shipping liners:

Business Object ILM Object Documentation

Partner and Location Profile TMCSLPLP ILM Objects for Partner and Location Profile [page 133]


Basic Settings


Business Object ILM Object Documentation

Booking

Bill of Lading

SCMTMSTRQ See SAP Library for SAP Transportation Management on SAP Help Portal at https://help.sap.com/tm. Choose your version. Under Application Help, open

SAP Library and choose Basic

Functions Archiving in SAP Transportation Management (SAP TM)

ILM Objects for Business ObjectsSCMTMSTRQ - Business Documents for

Forwarding Order Management .

More Information

For more information about SAP ILM, see SAP Library on http://help.sap.com/erp . Choose your version, open SAP Library and then choose SAP ERP Cross-Application Functions Cross-Application ComponentsSAP Information Lifecycle Management

Related Information


3.3.5.1 ILM Objects for Partner and Location Profile

The ILM object TMCSLPLP is mapped to the archiving object /TMCSL/PLP. 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



http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Ferp

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

PLP_TYPE Partner and Location Profile Type

For value determination for time references or condition fields use transaction IRM_CUST.

Related Information

ILM Objects for Business Objects [page 132]


Basic Settings

3.4 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, bill of lading 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 order to cash processes in the option for container shipping liners:

Business Partner Location

/SCMTMS/TRQ /SCMTMS/TRQ

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

Not applicable /TMCSL/PLP

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.

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 141]● End of Purpose Framework [page 140]● Handling of Blocked Business Partners and Locations [page 148]


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 Application Server Basis Services Information Lifecycle Management

○ Settings related to the blocking and deletion of business partner master data in Customizing for Cross-Application Components under Data Protection Blocking and Unblocking of Data

○ Settings related to the blocking and deletion of location master data in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings 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 Reusable Objects and Functions for BOPF Environment PPF Adapter for Output Management 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 SAP Transportation Management (SAP 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 137].

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 SAP TM documents, see Business-Object-Specific End of Business Conditions [page 143].

For more information about SoRT, see Start of Retention Time (SoRT) [page 141].


Basic Settings

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 140].

Related Information

● Security Guide for SAP TMFor more information about security in SAP TM, see http://help.sap.com/tm. Choose the relevant release and then choose Security Information Security Guide .

● SAP Information Lifecycle ManagementThe 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 .

3.4.1 Customizing Settings for Data Protection and Privacy

The following Customizing settings enable you to use Data Protection and Privacy in SAP Transportation Management, order to cash for container shipping liners.

SAP Information Lifecycle Management (ILM) Customizing and Policy Settings

The basis for the blocking and deletion of personal data in SAP Transportation Management (SAP TM) is SAP Information Lifecycle Management (ILM).

The following ILM-specific settings are necessary:

● Define and maintain application rule groupsThe 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 Application Server Basis ServicesInformation Lifecycle Management Retention Management Make Customer-Specific Settings .

● Define application rule variants


http://help.sap.com/tm

http://help.sap.com/erp

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 143].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 Data Protection Blocking and Unblocking of Data Business Partner Define and Store Application Rule Variants for EoP Check .

○ LocationsSee Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Location Master Data Deletion Assign Application Rule Variants for EoP Check .

● ILM policies to be maintained○ Retention period for all application-specific ILM objects○ 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 Cross-Application Components SAP Information Lifecycle Management Using ILM Retention Management in the Application SystemEditing ILM Policies

○ Editing Residence RulesApplication Help SAP ERP Cross-Application Functions Cross-Application Components SAP

Information Lifecycle Management Using ILM Retention Management in the Application SystemEditing ILM Policies Editing Residence Rules

○ Processing Audit AreasApplication Help SAP ERP Cross-Application Functions Cross-Application Components SAP

Information Lifecycle Management Using ILM Retention Management in the Application SystemProcessing Audit Areas


Basic Settings


SAP TM Customizing Settings

The following SAP TM-specific settings are necessary:

● Activate direct output agent for business objectTo enable the system to write start of retention time (SoRT) information, you must enable the direct output agent (DOA) for the relevant business objects.

NoteIn 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/TRQ Root DPP_SORT_DETERMINATION

You can choose to handle the SoRT processing as a critical task (synchronous) or as an uncritical task (asynchronous).

NoteIn 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 141].

● Activate Data Protection and Privacy-relevant function modules for business partner archiving eventsTo 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

Start of Retention Time (SoRT) [page 141]


Using Application Rule Variants [page 143]

3.4.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 bill of lading 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.

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.


Basic Settings

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 SCMB_LOC.

3.4.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, order to cash for container shipping liners, the SoRT information is handled in two steps as follows:

● Determination of the SoRT informationOnce 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 informationDuring 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 143].

SAP Transportation Management uses the direct output agent (DOA) DPP_SORT_DETERMINATION to trigger the SoRT determination.


In SAP Transportation Management, order to cash for container shipping liners, the DOA is configured for the business object /SCMTMS/TRQ.

You enable and maintain the DOA for the above business objects in Customizing for Cross-Application Components under Processes and Tools for Enterprise Application Reusable Objects and Functions for BOPF Environment PPF Adapter for Output Management Maintain Output Management Adapter Settings .

For more information, see Customizing Settings for Data Protection and Privacy [page 137].

You can choose to handle the update of the SoRT information in two different modes:

● Non-exclusive write lockAllows multiple updates.

● Exclusive write lock:The table is locked until the COMMIT is finished.

NoteThe standard delivery uses the non-exclusive write lock. Using the exclusive write lock may have implications for system performance.

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 SAP Transportation Management under Transportation Management Business Add-Ins (BAdIs) for Transportation Management Master Data Business Partners Data Protection BAdI: Data Protection and Privacy .

● For locations, see Customizing for SAP Transportation Management under Container Shipping LinersBasic Settings Business Add-Ins (BAdIs) Location Master Data Deletion 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.


Basic Settings

Related Information

Customizing Settings for Data Protection and Privacy [page 137]Business-Object-Specific End of Business Conditions [page 143]

3.4.2.2 Business-Object-Specific End of Business Conditions

The following table lists the business objects used in order to cash processes that the system considers during the end of purpose (EoP) check and the end of business (EoB) condition:

CSL Business Object SAP TM Business Object

Booking Transportation Request (TRQ)

Bill of Lading Transportation Request (TRQ)

Manifest Transportation Order (TOR)

Proforma Invoice Request Forwarding Settlement Document (FWSD)

Final Invoice Request Forwarding Settlement Document (FWSD)

More Information

For more information about the SAP Transportation Management (SAP TM) business-object-specific end of business conditions, see https://help.sap.com/tm and choose your SAP TM release. Open the Application Help and choose Basic Functions Blocking and Deletion of Personal Data in SAP TM End-of-Purpose Framework Business Object-Specific End of Business Conditions .

3.4.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.

For more information, see Customizing for SAP NetWeaver under Application Server Basis ServicesInformation Lifecycle Management Retention Management Make Customer-Specific Settings(transaction IRM_CUST_CSS.)

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 Data Protection Blocking and Unblocking of Data Business Partner Define and Store Application Rule Variants for EOP Check .

○ LocationsSee Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Location Master Data Deletion Assign Application Rule Variants and Rule Groups for EoP Check .

NoteFor container shipping liner processes, the specific ILM objects and the related condition fields are available as part of the container shipping liners option for SAP Transportation Management. 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 policiesThe 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 Cross-Application Components SAP Information Lifecycle Management Using ILM Retention Management in the Application System Editing ILM Policies .


Basic Settings


Related Information

Example: Application Rule Variants [page 145]

3.4.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 143]


3.4.2.4 Business-Object-Specific Settings to Write SoRT Information

SAP Transportation Management (SAP 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.

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 Reusable Objects and Functions for BOPF Environment PPF Adapter for Output Management Maintain Output Management Adapter Settings .

Related Information

End of Purpose Framework [page 140]

3.4.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:○ You are using Data Protection and Privacy functions for the first time.○ You activate switch BUPA_ILM_SWITCH or switch /TMCSL/LOC_ILM_SFW_01 for the first time.○ You activate switch BUPA_ILM_SWITCH or switch /TMCSL/LOC_ILM_SFW_01, but the direct output

agent is disabled and will be enabled in a later step.


Basic Settings

● 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.

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.4.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, order to cash for container shipping liners.

The following table shows the blocking report for each business object.

Master Data Report

Business Partner BUPA_PREPARE_EOP

Location /TMCSL/RLOC_PREPARE_EOP

In SAP Transportation Management, order to cash for container shipping liners, 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:○ Business Partner

○ /SCMTMS/TRQ○ /SCMTMS/CFIR○ /SCMTMS/PLP

○ Location○ /SCMTMS/TRQ○ /SCMTMS/CFIR

● 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.4.4 Handling of Blocked Business Partners and Locations

Blocking of data can impact the system behavior in the following ways:

● DisplayThe system does not display personal data of a blocked business partner or location.

● ChangeIt is not possible to change a completed business document that contains a blocked business partner or location.

● CreateIt 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.

● SearchThe 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 PartnerIt 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.

● LocationTo 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 SAP Transportation Management under Container Shipping Liners Basic SettingsLocation Master Data Deletion Define Authorization Group Indicating Blocked Master Data .

3.4.5 End of Business Condition for Order to Cash Processes

You can use the report /SCMTMS/RECALC_TRQ_STATUS to recalculate a bill of lading's (B/L's) lifecycle when it reaches Import Finalized. The B/L’s lifecycle is set to Completed and the end of business (EoB) process is triggered.

Once a B/L’s lifecycle reaches Completed, the following documents in the document flow are also set to Completed:

● Diversion Request● Delay in Transit (DIT) Request● Snapshot● Snapshot B/L● Flat Rack

SAP Transportation Management, order to cash for container shipping liners, implements the Business Add-In (BAdI) /SCMTMS/BADI_DPP for the following EoB processes:


Basic Settings

● Business-partner-related EoB processFor more information, see Customizing for SAP Transportation Management under Transportation Management Business Add-Ins (BAdIs) for Transportation Management Master Data Business Partners Data Protection BAdI: Data Protection and Privacy .

● Location-related EoB processFor more information, see Customizing for SAP Transportation Management under Container Shipping Liners Business Add-Ins (BAdIs) Location Master Data Deletion BAdI: Data Protection and Privacy .

3.5 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:

● Booking● Bill of Lading● Partner and Location Profile

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 SAP 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 Cross-Application Components under Processes and Tools for Enterprise Applications Reusable Objects and Functions for BOPF Environment Maintain BO-Specific Change Document Objects :

Business Object Change Document Object

/SCMTMS/TRQ /TMCSL/TRQ

/TMCSL/PLP /TMCSL/PLP

NoteMost of the change document objects are delivered by default for container shipping liners business objects. For those standard business objects (for example, /SCMTMS/TRQ) 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 page on the user interfaces of the business documents.

You can display the changes in a header-item view, so that 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.

Note● The Change Documents tab page 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.

3.6 Blocking and Deletion of Location Master Data

You can use the SAP Information Lifecycle Management (ILM) component to control the blocking and deletion of location master data.

Overview

Blocking location master data enables you to block data that is no longer required for any business purposes. The data is blocked and not deleted as it is still in the retention period. The blocked data is no longer available for any business transactions or business use. The data is no longer displayed in existing business objects. You cannot edit, create new business objects, or conduct follow-up activities with the blocked data.

Personal data collected in location master data can be blocked as soon as the business activities for which the data is needed are completed and the residence time for the data has elapsed. After this time, only users who are assigned additional authorizations can access the data. After the retention period for the data expires, personal data can be destroyed completely such that it can no longer be retrieved. Residence and retention periods are defined in the customer system.

Authorized users (authorization object: /TMCSL/LOC, ACTVT: 03) can access the blocked data. Authorized users (authorization object: /TMCSL/LOC, ACTVT: 95) can unblock the data in exceptional cases. Blocked data can be unblocked only within the retention period since data is deleted after the retention period.

Implementation Considerations

● The following components have been installed: TMCSL 200 SP01 and SAP NetWeaver 740 SP07 (or higher).


Basic Settings

● You have activated the business function Information Lifecycle Management (ILM).● You have read SAP Note 2631436 before activating the business function ILM-Based Deletion of

Location Master Data (/TMCSL/SCMB_LOC_ILM_1) to verify that all SCM applications that are used in your environment support blocking and deletion of SCM location data using SAP Information Lifecycle Management.

● You have activated the business function Location Master ILM-Deletion (/TMCSL/SCMB_LOC_ILM_1).● The required settings have been configured in Customizing for SAP Transportation Management under

Container Shipping Liners Basic Settings Location Master Data Deletion .● You have the necessary authorization for blocking and unblocking:

○ Authorization object: /TMCSL/LOC○ Activity (ACTVT): 05 for blocking; 95 for unblocking

● You have the necessary authorization for viewing blocked location master data:○ Authorization object: /TMCSL/LOC○ Activity (ACTVT): 03○ Authorization group (BRGRU) defined in the Customizing activity Define Authorization Group Indicating

Blocked Master Data● You have defined the residence period and retention period rules for location master data in ILM

(transaction IRMPOL).

Features

The following features are available for blocking and deletion of location master data:

● Blocking of location master dataYou can block location master data after the residence period has ended using the Block Location Master Data report (transaction /TMCSL/LOC_PRE_EOP). Only authorized users can access the blocked data.The system performs an end of purpose (EoP) check to determine whether the data related to the location master data is used. An EoP indicates that business is complete and the residence time for the location master data is over.The report considers the residence period and retention period rules maintained in ILM to determine if a location master has reached the EoP with respect to a dependent application. When the EoP is ensured in all the dependent applications, only then is the data blocked. If the data is still used and business activities are not completed, the system does not block the data. If the data is not used by any applications, the system blocks the data.Blocking of data can impact system behavior in the following ways:○ Display: The system does not display blocked data.○ Change: It is not possible to change a business object that contains blocked data.○ Create: It is not possible to create a business object that contains blocked data.○ Copy or Follow-Up: It is not possible to copy a business object or perform follow-up activities for a

business object that contains blocked data.○ Search: It is not possible to search for blocked data or to search for a business object using blocked

data in the search criteria.You can display blocked data if you have the special authorization (authorization object: /TMCSL/LOC, ACTVT 03, authorization group specified in Customizing for Location Master Data Deletion). You are not authorized, however, to create, change, or copy business objects with blocked data, or perform follow-on activities with these business objects.


http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2631436

If you need to display blocked data and do not have the required authorization, you can do one of the following:○ Contact a business user who is authorized to display this data○ Contact a business user who is authorized to unblock this data (in case the data should be used

further in business processes)● Unblocking of location master data

If you have the required authorization, you can unblock customer master data that has been mistakenly blocked using the Unblock Location Master Data report (transaction /TMCSL/RLOC_UNBLOCK).

● Deletion of location master dataAfter the retention period, you can delete the location master data in the database.

Related Information

Blocking Location Master Data [page 152]Unblocking Location Master Data [page 156]

3.6.1 Blocking Location Master Data

Use the Block Location Master Data report (transaction /TMCSL/LOC_PRE_EOP) to block data related to locations.

Prerequisites

● You have maintained the residence period and retention period rules in the SAP Information Lifecycle Management (ILM) portal (transaction IRMPOL).

● You are authorized to block location master data. You can use this report if the authorization object /TMCSL/LOC is set with ACTVT 05.

● The required settings for blocking location master data have been made in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Location Master Data Deletion .

Context

The report checks with the dependent applications if business is complete and the residence period is over and then blocks the location master data. You can no longer display, edit, create business objects, or conduct follow-up activities with the blocked data. The blocked data can be displayed only by users who have the appropriate permissions.

You can unblock data that you might have blocked inadvertently using the Unblock Location Master Data report (transaction /TMCSL/RLOC_UNBLOCK).


Basic Settings

Procedure

1. Start transaction /TMCSL/LOC_PRE_EOP (Block Location Master Data).

2. 2. Enter the following information:

Option Description

Data to be Processed Unblocking on General Level is automatically selected.

NoteThe Unblocking on Company Code Level option is not available for container shipping liner processes.

Selection Enter the location type that you want to process. You can then further narrow down the selection using location name.

Options Select the appropriate checkboxes as follows:

○ Skip Subsequent EoP Checks if Ongoing Business FoundIf ongoing business is found for master data in an application, the master data cannot be blocked. The report provides an option to optimize the end of purpose (EoP) check. Choose this checkbox to skip subsequent EoP checks for the data from being conducted in the other applications.For example, three applications, APPL_1, APPL_2, and APPL_3 are registered for EoP check for master data A, B, and C. If APPL_1 has open business activities for master data A and B, then APPL_2 is called for master data C only. Again, if APPL_2 has open business activities for master data C, then APPL_3 is not called at all.

○ Consider Next Check DateFor data that has ongoing business activities, applications return a date when the next EoP check can be conducted. You can also set the default next check date period by configuring the activity Define Next Check Date Period under Customizing for Location Master Data Deletion. The report considers the default value if the application has not returned any next check date or if the next check date returned by the application is too far in the future.If you select the Consider Next Check Date option, the report considers the next check date before triggering an EoP check for the data


Option Description

Processing Parameters Specify the required processing parameters as follows:

○ Number of Objects per ProcessSpecify the minimum number of objects per process. All dependent objects are handled in the same process. There is no strict upper limit, since the system ensures that all objects are always processed together.However, processing runs in packages and the packages are formed internally, using SAP blocking logic. Therefore, it is possible that more objects will need to be processed in a package. When defining the package size, you should start with a value like 25, then measure the runtime and moderately increase or decrease the values as appropriate. Then measure the runtime again. The optimum package size needs to be predetermined for each system.

○ Parallel ProcessingSelect this checkbox to trigger parallel processing, which significantly improves runtime. Similar to synchronous processing, parallel processing also runs in packages. When you select this option, the default values for parallel processing made in Define Parallel Processing Settings under Customizing for Location Master Data Deletion are used. You can also change these settings as per your requirement when you run this report.

○ Maximum Number of Parallel Processes and Maximum Utilization of the Server GroupThe percentage of maximum utilization of the server group that you specify determines or restricts the maximum number of parallel processes, in relation to the work processes of the server group that are available at runtime. Therefore, ensure that you specify at least one of the two values when selecting parallel processing. If you specify one parameter, the number of parallel processes is defined using only this parameter. If you specify both parameters, the number of parallel processes is determined using the parameter that applies first.For example, if you define 10 parallel processes as maximum and 50% maximum utilization, but after seven parallel processes you already reach 50% utilization of the server group, the report will not start another parallel process. Similarly, if you would have only 25% utilization with 10 parallel processes reached, the report will not start more than these 10


Basic Settings

Option Description

parallel processes to get the maximum utilization of 50%.

○ Server GroupIn parallel processing several dialog work processes on one or more application servers are used for the processing, regardless of whether they are called from a dialog program or a background job. The server group specifies which application servers can be used to what extent for parallel processing. You must specify a server group to use parallel processing.

Processing Options Select Test Mode to view the data that meets the EoP check criteria and can be blocked. In this mode, data is not blocked. Select Production Mode to actually block the data.

Detail Log Select one of the following options:

○ Without Success MessagesChoose this option to list only summary messages or error messages.

○ CompleteChoose this option to list all messages.

Log Output Use the options Application Log and List and Application Log to save the logs so that they can be analyzed using the report Display Stored Application Logs for Location (transaction /TMCSL/LOC_DISPL_LOG).

3. Choose Execute.

Based on the data you choose, and the execution criteria you specify, the report triggers an EoP check and blocks data. It stores the start of retention time (SoRT) in the table SoRT Details of Location for Each Application (/TMCSL/LOC_SORT) and blocks the location master data by setting the blocking indicators in the database tables.

Related Information

Unblocking Location Master Data [page 156]Displaying Stored Application Logs for Location [page 157]


3.6.2 Unblocking Location Master Data

Use the Unblock Location Master Data report (transaction /TMCSL/RLOC_UNBLOCK) to unblock location master data that was blocked accidentally.

Prerequisites

You are authorized to unblock location master data. You can use this report if the authorization object /TMCSL/LOC is set with the value ACTVT 95.

Procedure

1. Start transaction /TMCSL/RLOC_UNBLOCK.

2. Enter the following information:

Option Description

Data to be Processed Unblocking on General Level is automatically selected.

NoteThe Unblocking on Company Code Level option is not available for container shipping liner processes.

Selection Enter the location type that you want to process. You can then further narrow down the selection using location name.

Processing Options Select one of the Test Mode options to view the data that can be unblocked without actually unblocking it. Select Production Mode to unblock the data.

Detail Log Select one of the following options:

○ Without Success MessagesChoose this option to list only summary messages or error messages.

○ CompleteChoose this option to list all messages.

Log Output Use the options Application Log and List and Application Log to save the logs so that they can be analyzed using the report Display Stored Application Logs for Location (transaction /TMCSL/LOC_DISPL_LOG).

3. Choose Execute.


Basic Settings

Related Information

Blocking Location Master Data [page 152]Displaying Stored Application Logs for Location [page 157]

3.6.3 Displaying Stored Application Logs for Location

Use transaction /TMCSL/LOC_DISPL_LOG to display the application log of the application log object Blocking Process Location (/TMCSL/LOC_LOG).

Prerequisites

● You have activated the business function ILM-Based Deletion of Location Master Data (/TMCSL/SCMB_LOC_ILM_1).

● You have the authorization object /TMCSL/LOC set with ACTVT 05.● You have the authorization to display application log objects.

Context

This report provides more contextual details at the level of the log items compared to the Analyze Application Log report (transaction SLG1). It helps you analyze blocking or unblocking logs of location master data and provides access to specific additional information such as:

● Location type● Location ID● Location name● Application name● System where the log item has been raised● Status

Procedure

1. Start transaction /TMCSL/LOC_DISPL_LOG.

2. Enter the following details:


Option Description

Subobject Select a log subobject.

Time Restriction Optionally, you can enter a time range.

Log Triggered By Optionally, you can specify a user, transaction code, or program.

Log Class Choose a log classification. All Logs is selected by default.

Log Creation Choose a log creation mode. Any is selected by default.

Log Source and Formatting Choose a formatting option. Format Completely from Database is selected by default.

3. Choose Execute.

Related Information

Blocking Location Master Data [page 152]Unblocking Location Master Data [page 156]

3.7 Collection and Reporting of Personal Data

As part of normal business processing, personal data is widely used in various applications and is stored whenever transactions occur. As it is sensitive data, you need to know exactly what personal data is being stored during these business dealings.

To support this requirement, a personal data collection report is provided for you to search all the stored personal data from all data sources and display the details in a friendly way (transaction /TMCSL/DCOL). In addition, the results can be downloaded in a machine-readable format for further processing.

As personal data is used in different business applications (such as bookings and line maintenance), it is mandatory to first define which applications reference personal data and which data sources are being used to store such data. You configure these settings in Customizing for SAP Transportation Management under

Container Shipping Liners Basic Settings Personal Data Collection Define Data Source .

In the option for container shipping liners, the following applications collect personal data:

Application Description

BUPA Business Partner Master Data

SAPAPO_LOC Personal Data in Location


Basic Settings

Application Description

SCMTMS_FAG Agreement

SCMTMS_TCRATES Transportation Charge Rates

SCMTMS_TRQ Transportation Request

TMCSL_LINE Line Maintenance

Related Information

Running the Personal Data Collection Report [page 159]Enhancement Options for Personal Data Collection [page 160]

3.7.1 Running the Personal Data Collection Report

Run the personal data collection report to view the personal data being stored for a specific business partner.

Prerequisites

● The data source for each application has been configured in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Personal Data Collection Define Data Source .

● You have been granted access to run report with the authorization object /TMCSL/DCL.

Context

Procedure

1. Start transaction /TMCSL/DCOL.

2. In the selection screen, enter a full business partner ID.

NoteThis report only supports searches with an exact business partner ID. Fuzzy searches are not possible.


3. Choose Execute.

The results are displayed in a simple hierarchical view.4. (Optional) In the toolbar, choose Download to download the result in a flat view.

Related Information

Collection and Reporting of Personal Data [page 158]Enhancement Options for Personal Data Collection [page 160]

3.7.2 Enhancement Options for Personal Data Collection

The personal data collection report allows you to display the stored personal data of a specific business partner from all the relevant data sources. You can use the Business Add-In (BAdI) /TMCSL/BADI_DATA_RETRIEVE to change the data selection result from the data sources before displaying it.

For more information, see Customizing for SAP Transportation Management under Container Shipping LinersBusiness Add-Ins (BAdIs) Personal Data Collection BAdI: Selection Value Assignment and Data

Collection .

Related Information

Collection and Reporting of Personal Data [page 158]Running the Personal Data Collection Report [page 159]


Basic Settings

4 Bookings

In SAP Transportation Management, order to cash for container shipping liners, you use the booking features to capture all of the details for a customer's request for a shipment.

The system supports different booking scenarios and can handle part-load bookings. During the booking process, you use the Voyage Suggestion Framework to generate suitable route proposals.

Related Information

Bookings [page 161]Route Proposal Generation [page 231]Part-Load Bookings [page 244]

4.1 Bookings

You use the booking process to capture customer requests for shipments. You can use the booking features to create, edit, and confirm bookings from your ordering parties. You can also specify the route and calculate the transportation charges. The booking forms the basis for the transportation planning.

Overview

In this context, the booking is mainly focused on the ocean liner business scenario. A booking is an order from an ordering party to a carrier for the transportation of goods from a shipper to a consignee according to agreed conditions.

You enter all of the information about the transportation of goods, which you have agreed with the ordering party, in a booking business document. You can either enter the data manually (for example, after a telephone call with the ordering party) or the data can be transferred automatically through SAP Process Integration interfaces or through electronic data interchange (EDI).

The system supports different types of booking business processes. The content of the Booking screen and the validations performed by the system depend on the booking type that you specify when you create the booking. The system can also handle different types of cargo items, including standard containers, packages, out of gauge (OOG) cargo, break bulk, and roll-on roll-off (RORO) cargo.

The booking contains the most important data for planning and executing the transportation, such as the pickup and delivery addresses, dates and times, and details of the goods that are to be transported. From the booking, you can determine and define the transportation route, create freight units, and create a transportation plan. You can also calculate the transportation charges and start the invoicing process.

SAP Transportation Management, Order to Cash for Container Shipping LinersBookings P U B L I C 161

Integration

The booking process is integrated with the following other processes within the overall solution:

Integration

Feature Description of Integration

Shipping Instructions The cargo details are recorded in a shipping instruction.

Bill of Lading (B/L) The B/L is created from the booking for charge calculation and tracking purposes.

Voyage Suggestion Framework (VSF) The VSF is executed during the booking process to check the equipment availability, check the allocation availability, and return the ranked route proposals for future planning purposes.

Part-Load Process The part-load scenario is a special booking process, in which one container is shared by several B/Ls.

Manifest After a booking is confirmed, it is eventually assigned to one or more manifests.

Partner and Location Profile (PLP) The booking process is adjusted based on the additional settings in the PLP. For example, the PLP is used to specify which destinations are allowed for part-load bookings.

Generic Validation Framework (GVF) The GVF is executed during the booking process to determine whether the booking data conflicts with the predefined restriction and prohibition rules, and also to generate any necessary approval items.

Routing Solution A Business Add-In (BAdI) is provided within the VSF process. Customers need to incorporate their own routing logic.

Allocation Check A BAdI is provided within the VSF process. Customers need to incorporate their own allocation check logic.

Equipment Check A BAdI is provided within the VSF process. You can either incorporate your own equipment check logic or you can use the SAP Transportation Resource Planning solution.

Related Information

Shipping Instructions [page 261]Bills of Lading [page 273]Route Proposal Generation [page 231]Partner and Location Profiles [page 51]


Bookings

Generic Validation Framework [page 89]

4.1.1 Booking Screen

You can use the booking screen to manually create, edit, and confirm bookings. You can also perform follow-up actions such as creating diversion requests and detention in transit requests.

The design of the booking screen is determined by the following settings:

● The booking types that have been defined in Customizing and the user interface profile assigned to each booking type

● Your individual screen settings in SAP NetWeaver Business Client

When you create a new booking, on the initial screen of the booking, you must enter the Booking Type and you can optionally also specify the Booking Party and the Booking Contact Person. The booking screen is automatically adjusted based on the requirements of the business process related to the booking type. The booking type also predefines which additional information or special tabs (or even certain fields) are displayed for each business process. For example, the Diversion Detail tab is only displayed for diversion requests.

You can also configure your settings in SAP NetWeaver Business Client to define whether a tab, assignment block, or specific fields in the booking are displayed or hidden.

Related Information

User Interface Profiles [page 163]Creating Bookings [page 165]

4.1.1.1 User Interface Profiles

User interface (UI) profiles are used to control the properties of the fields and buttons on the Booking screen, based on business conditions.

The UI profile framework consists of the following parts:

● UI profileUI profiles are defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Profile Settings Maintain Booking UI Profile .

● SAP Transportation Management (SAP TM) conditionSAP TM conditions are assigned to booking types in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for Booking Type Define Basic Settings for Booking Document Type .

● Condition assignment


Condition types are defined in Customizing for SAP Transportation Management under Transportation Management Basic Functions Conditions Define Condition Types .

You can define the field properties in the UI profile based on specific scenarios. This means that for the same booking type, you can define multiple UI profiles to match different booking scenarios.

The system determines the UI profile from the assigned SAP TM condition, and then changes the field properties based on the determined UI profile definition. If no UI profile is determined, the system displays the original UI without any changes.

The UI profile can control not only field properties, but also button properties. Buttons are identified by event IDs.

4.1.2 Creation of Bookings

You can create bookings either manually or automatically. To speed-up the process of creating bookings manually, you can use a booking template or copy an existing booking.

You can create a new booking in the following ways:

● Based on a templateYou can create booking templates that contain the most important and the most frequently used data such as the sales organization or the Incoterms. When you create a new booking based on a template, the data from the template is copied into the new booking and thus speeds-up the creation of the new booking.

● Based on a quotationWhen you create a booking based on a quotation, the data from the quotation is copied into the new booking.

● As a copy of an existing bookingWhen you create a new booking based on an existing booking, most of the data from the existing booking, including data about the route, is copied into the new booking. The system does not copy any dates and times, or any follow-on documents such as freight units or freight orders.You can enter a new booking type for the new booking you are creating. This can, however, lead to inconsistencies with the copied data, if, for example, the copied data has been determined from the Customizing settings for the booking type (such as the transportation mode and the shipping type). If the data for the new booking type is unique, the system updates the data automatically. Otherwise, you have to change the inconsistent data manually.

● Using SAP Process Integration interfacesThe system can also receive booking data directly from the ordering party by means of an SAP Process Integration interface.

Related Information

For more information about the standard SAP functionality for creating forwarding quotations and their conversion to forwarding orders, see SAP Library for your SAP Transportation Management release on SAP Help Portal at https://help.sap.com/transportationmanagement. Under Application Help, open SAP Library and search for Creation and Editing of a Forwarding Quotation.

Creating Bookings [page 165]


Bookings


Approval Workflow [page 193]

Booking Confirmation [page 197]

4.1.2.1 Creating Bookings

Create bookings manually and optionally copy data from existing bookings or templates to speed-up the data entry process.

Prerequisites

You have made the settings required for the booking.

Context

You can include mixed cargo in bookings such as container cargo, roll-on roll-off (RORO) cargo, and break bulk cargo. You can also create a hierarchy of booking items (for example, a container that contains packages). However, RORO items and break bulk items can only be inserted at the highest level in the cargo item hierarchy. They cannot be inserted under a container item.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Create Booking .

The system displays the initial screen for new bookings.2. To create this new booking as a template, select the Template checkbox.3. Specify the booking type, and optionally specify an existing booking or a booking template as a reference,

then choose Continue.

The system displays a new booking that has the booking status New. If you have specified an existing booking or a booking template as a reference, the system copies the relevant data into the new booking.

4. To enter the booking number manually, rather than use a system-generated number, select the Ext. Assigned checkbox next to the Booking Number field, and then enter the booking number.

5. On the General Data tab, enter the general data for the booking such as the sales organization, the agreement reference, and the delivery mode. The following fields are mandatory:

○ Contract Type○ Booking Party○ Delivery Mode (The system determines the movement type based on the delivery mode.)○ Depart-After Date


○ Source Location○ Destination Location

If the relevant settings have been defined in Customizing for the booking type, the system automatically determines the Sales Organization.

6. Enter additional information for the booking on the following tabs:

○ Cargo Details: Enter the information for empty provision and empty return.○ Additional General Characteristics: Enter any additional general information that is required for the

booking. The fields on this tab are dependent on the dynamic profile for the booking type.○ Approval: If additional approval is required, create the necessary approval item.

7. In the Items section, insert the required cargo items by choosing one or more of the following options:

○ Insert Container

○ Insert Package

○ Insert RORO

○ Insert Break Bulk

The system calculates the total quantities and weights of the entered items and saves the totals to the header data.

8. In the toolbar, choose one of the following options:

○ Generate Routes Present Booking Solution

○ Generate Routes Present the Best Route

○ Generate Routes Verify Manual Route

The system uses the Voyage Suggestion Framework to determine the appropriate routes, and then displays the route proposals in a dialog box.

9. Select a route and confirm your choice.10. Save the booking by choosing one of the following buttons in the toolbar:

○ SaveIf the booking is created using an internal number, the system assigns it an ID from the number range for the document type. In addition, the system checks the entered data for completeness and consistency. The system displays the results of these checks as error messages and a completeness status. If the booking is saved successfully, it has the booking status New.

○ Save DraftIf you haven't completed entering the booking information, you can save a draft version of the booking. The system bypasses most of the validation checks and saves the booking data. The booking has the booking status Draft.

Results

You can later edit the booking you have created, by choosing Booking Booking Change Booking . You can change any data in the booking except the booking number and the booking type.


Bookings

Next Steps

Any approval items need to be approved by an authorized user. When the booking is accepted by both the ordering party and the carrier, you can confirm it.

Related Information

Approval Workflow [page 193]Booking Confirmation [page 197]

4.1.2.2 Additional Location Characteristics

Some ports request specific information based on local legal requirements. To support this, the system allows you to configure dynamic fields based on location. These fields are displayed on the Additional Location Characteristics tab on the Booking screen when the relevant locations are included in the route.

Dynamic attribute profiles are defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Profile Settings Maintain Dynamic Profiles for Field Attributes.

You can assign a dynamic attribute to a location in the location profile, by choosing Master Data Partner and Location Profile Create Profile . The Dynamic Attribute Profile field is on the Booking tab.

To avoid missing any locations that are not maintained for booking stages, the system gets all of the locations from the manifest assigned stages.

The following fields are listed in the table on the Additional Location Characteristics tab:

Additional Location Characteristics Fields

Field Description

Item Indicates the sequence of the location in the trip.

Location Displays the description of the location.

Profile ID Specifies the profile ID that the system has determined based on the location ID and the location profile. If this field is blank, it means that the system didn't find a relevant profile for the location.


Field Description

Inactive Indicates whether the location is valid for this trip. Sometimes, you maintain additional attributes for a location, and then the route is changed. In some cases, if the location is not valid in the new route, and you have maintained information for this location, the system retains this location with the Inactive checkbox selected.

When you select an entry in the table, the system displays detailed information from the following sources below the table:

● ProfileIf a profile has been determined, the system displays the fields maintained in the profile. You can edit these fields.

● ManifestThe system displays the location information.

Related Information

Example: Additional Location Characteristics [page 168]Partner and Location Profiles [page 51]

4.1.2.2.1 Example: Additional Location Characteristics

The location-specific fields that are displayed on the Additional Location Characteristics tab on the Booking screen are determined based on the location profile. The system determines the relevant locations using the manifests for the booking.

ExampleThe data for the booking stage is as follows:

Booking Stage Data

Sequence Source Location Destination Location Vessel Voyage

10 A B ODIN 210001

20 B C POSEIDON 320001


Bookings

The system finds Manifest 1 based on the vessel (ODIN) and the voyage (210001), and then finds the intermediate ports between location A and location B. The data for Manifest 1, vessel ODIN, and voyage 210001, is as follows:

Manifest 1 Data

Sequence Source Location Destination Location

10 Z A

20 A A1

30 A1 A2

40 A2 B

50 B D

The system also finds Manifest 2 based on the vessel (POSEIDON) and the voyage (320001), and then finds the intermediate ports between location B and location C. The data for Manifest 2, vessel POSEIDON, and voyage 320001 is as follows:

Manifest 2 Data

Sequence Source Location Destination Location

10 Y B

20 B B1

30 B1 B2

40 B2 C

50 C E

Based on the tables above, the following locations are displayed on the Additional Location Characteristics tab on the Booking screen:

● A● A1● B● B1● B2● C

Related Information

Additional Location Characteristics [page 167]


4.1.2.3 Ordered Route Determination

When you generate the routes for a booking, the Voyage Suggestion Framework (VSF) sends the necessary information to the routing component to determine the available route proposals. It is important to have an ordered route for a booking. Therefore, the determination of the ordered route is an essential step.

During the quotation process, the ordered route information from the product catalog is already stored in the rate table line item. In this scenario, the VSF triggers the charge calculation as the first step and retrieves all of the charge information. Then the VSF determines the ordered route as a follow-up step by retrieving the ordered route from the relevant rate table line item (if any). The ordered route is displayed on the Consolidated Trip Plan tab in the Booking screen.

4.1.2.4 Splitting Booking Items Automatically

Add multiple containers as one item, and the system automatically splits the item into multiple items (one for each container) when you save the booking.

Prerequisites

In Customizing for SAP Transportation Management under Transportation Management Forwarding Order Management Define Item Types for Forwarding Order Management , the One Piece per Item checkbox has been deselected for item types that can contain more than one item.

Procedure

1. In SAP NetWeaver Business Client, create a booking or open an existing booking.

2. In the Items section, choose Insert Container.3. In the Quantity field, enter a quantity greater than one for the container.4. If the container has no subitems (for example, packages or products), enter a gross weight for the

container.5. If the container has subitems, select the container in the Item Hierarchy table and choose Insert. You must

specify a gross weight for each subitem that you add. Note that the information you enter for the subitem is for one container only. For example, say there are are 5 containers (each weighing 20 tons) and one subitem, you would enter 20 tons for the subitem gross weight.

The system adds the subitems as subnodes of the container.6. Save the booking.


Bookings

Results

The system creates one item for each container as follows:

● The quantity of each container is 1.● The subitems in the original container are copied to each of the new container items.

The container information is summarized in the item summary table.

Related Information

Split Bookings [page 190]Creating Bookings [page 165]Confirming Bookings [page 198]Booking Statuses [page 177]

4.1.2.5 Entering SDO and SDD Details

Enter additional information on the SDO/SDD tab if the cargo receipt mode is store door origin (SDO), or the cargo delivery mode is store door destination (SDD).

Prerequisites

● The cargo modes have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings

Define Cargo Modes .● The equipment types have been defined in Customizing for SAP Transportation Management under

Transportation Management Master Data Resources Define Equipment Groups and Equipment Types .

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and then open the relevant booking.

2. On the General Data tab, select the required options as follows:

○ To indicate that the containers are to be picked up from the customer's premises, select Door as the cargo receipt mode.

○ To indicate that the containers are to be delivered to the customer's premises, select Door as the cargo delivery mode.


When one or more of the above options is selected, the system displays the SDO/SDD tab.3. On the SDO/SDD tab, in the Additional Information section, enter the following information:

Field What To Do

Customer Paid Transportation Origin Select this checkbox to indicate that the customer pays the charge for the origin inland leg. This checkbox is for information only and does not affect any further processes.

Customer Paid Transportation Destination Select this checkbox to indicate that the customer pays the charge for the destination inland leg. This checkbox is for information only and does not affect any further processes.

Load Reference and Remarks Optionally, you can enter default values that are copied to the corresponding fields at item level each time you insert a new entry.

4. On the SDO/SDD tab, choose the relevant sub-tab: SDO or SDD.5. Choose Insert to add a new row to the table, and then enter the following details for the container item:

Field Description

Quantity and Quantity Unit Enter the quantity and the unit of measurement (UoM).

Equipment Type/Size Enter the container type. Note that only standard equipment types are allowed.

Multiple Stop Group This field can be used in a top-off scenario where the cargo for a container is picked-up from multiple locations. You can create two entries for the same container, and assign different locations but the same multiple stop group to both entries. The system treats the two entries as one container. To use this field, enter a character string.

Pickup Date (To) Enter the date and time that the container is to be picked up.

Drop & Pick Select this checkbox to indicate that this is a drop and pick scenario, where the delivery of the container is combined with the collection of another container at the same location and time. These 2 activities are planned in one intermodal transport. For example, a regular customer receives an empty container at the export store-door location of the booking, and a full container can be picked up to be delivered to the port of loading. This checkbox is for information only and does not affect any further processes.

Drop & Collect Select this checkbox to indicate that this is a drop and collect scenario, where separate intermodal transports are planned and executed for the delivery and collection of the containers. This checkbox is for information only and does not affect any further processes.

Trucker Company Enter the trucker company that will transport the container from the pickup location to the port of loading. This value will be overwritten by the first line of the name of the location if the location is changed.

Address of Location The location details are defaulted from the booking location. In the Store Door Origin table, the source location is used as the default value, and in the Store Door Destination table, the destination location is used as the default value. When the item location is changed, the system copies the address from the location master data to the item location details. You can change the location details manually if necessary.

Contact Name, Telephone, Fax, and E-Mail Enter the contact name, language key, and contact details.

Remarks and Load Reference Enter any additional information that you wish to record for this item. If you have entered values for these fields in the header, the values will be copied to each new item you create, and can be adjusted if necessary.



Bookings

The system performs the following consistency checks:○ Equipment type and unit of measurement (UoM)

The item equipment type and UoM must exist in the booking items.○ Quantity

The number of items with a particular equipment type and UoM must not be greater than the number of booking items with the same equipment type and UoM. These numbers are checked for SDO and SDD separately.

4.1.2.6 Entering the Dimensions of OOG and Break Bulk Cargo

Enter the dimensions for out of gauge (OOG) and break bulk items, so that this information can be further used for the transportation approval decision.

Prerequisites

You have a booking that contains at least one of the following types of items:

● A container item with the Overdimensional Cargo checkbox selected (an OOG container)● A package item with the Break Bulk checkbox selected (a break bulk item)

Context

Certain types of cargo are too large to be packed into a standard container. Such cargo can either be loaded into a normal container with one or more sides open (OOG cargo), or it can be loaded onto a flat rack container (break bulk).

OOG cargo is handled in SAP Transportation Management (SAP TM) as a container booking item with the Overdimensional Cargo checkbox selected. Break bulk is handled in SAP TM as a package booking item with the Break Bulk checkbox selected.

If either the Overdimensional Cargo checkbox or the Break Bulk checkbox is selected for a booking item, then an additional OOG/Break Bulk Information tab is displayed in the item details section of the Booking screen.

Procedure


2. In the Items section of the screen, select the relevant OOG or break bulk cargo item.

The system displays the item details, including the OOG/Break Bulk Information tab.


3. On the OOG/Break Bulk Information tab, enter the dimensions of the cargo in the Height, Length, and Width fields.


4.1.2.7 Verified Gross Mass

In accordance with the Safety of Life at Sea (SOLAS) regulations, the shipper must declare the verified gross mass (VGM) of a packed container to the port terminal authorities before the container is loaded on board the vessel.

To ensure the correct stowage and stacking of a container, it is important that the accurate gross mass of the container is known. The incorrect declaration of cargo weight is a hazard that can result in cargo claims and structural damage to vessels and also poses a significant risk to the lives of staff.

The shipper (or the shipper's representative) is responsible for providing the VGM, and it must be stated in the shipping document and provided to the port terminal authorities within a prescribed cut-off date and time.

The SOLAS regulation for weighing containers permits the following methods of weighing packed containers to obtain the VGM:

● Weighing the packed container using a calibrated device● Weighing all of the cargo items and adding the tare mass of the container

Related Information

Entering the Verified Gross Mass [page 174]

4.1.2.7.1 Entering the Verified Gross Mass

Enter the verified gross mass (VGM) of the packed container on the Container Details tab in the Booking screen.

Context

Before each container is loaded on board the vessel, you must declare the VGM of the packed container to the port terminal authorities.

NoteIf you change the VGM data after the booking has been confirmed, the system automatically resets the confirmation status, and the booking has to be reconfirmed.


Bookings

Procedure


2. In the Items section of the screen, select the relevant container in the item hierarchy table.

The system displays the item details below the item hierarchy table.3. On the Container Details tab, in the Verified Gross Mass (VGM) group box, enter the following details:

Field What To Do

VGM Received Select this checkbox to indicate that the VGM has been received.

VGM Signed Select this checkbox to indicate that the VGM document has been signed by an authorized person.

VGM Weight Specify the weight stated on the VGM document. You must also select the unit of measurement (UoM).

Sent By Specify the business partner that has provided the VGM.

Date Received Specify the date that the VGM was received.

Verification Method Select one of the following options:○ Mass by calibrated device○ Mass by tare plus sum of goods

4. Save your changes and confirm the booking.

4.1.3 Booking Life Cycle

Bookings follow a life cycle, which is managed by means of a life cycle status. The system uses the life cycle status to control the possible actions. For example, a booking confirmation can only be sent to the customer when the booking status is confirmed.

In the Booking screen, the booking life cycle status is shown at the top of the screen in brackets after the booking number. When you first create a booking, the system assigns it the life cycle status New.

When you confirm the booking, the system runs the booking validations and checks the business rules maintained in the Generic Validation Framework (GVF) and the Customizing for the booking type. If all of these checks are passed successfully, the system sets the booking's life cycle status to Confirmed. The booking can then be released. If any of the validation checks fail, the system assigns the life cycle status Pending to the booking.

You can also save the booking in Draft status. When the booking is saved as Draft, the system does not execute any checks or validations.

The following table lists the possible values of the booking life cycle status:


Life Cycle Status Description

New The initial status for new bookings as follows:

● The booking has been created but has not been saved or assigned a booking number.

● The booking has been saved without any errors or failed validation checks, but has not yet been confirmed.

Draft The booking has been saved as draft.

Pending Confirmation The status that typically occurs due to failed checks during booking confirmation.

Confirmed The booking has been confirmed successfully with no errors or failed validation checks.

Completed The bill of lading for the booking has been produced.

Canceled The booking has been canceled.

Pending Cancellation The cancellation process is blocked by follow-up actions. The booking shall be cancelled once the follow-up actions are completed. For example, the empty provision container must be returned if it has been gated-out.

Discarded The booking won’t be reused, and the discarded status can’t be changed. A booking with the discarded status can be archived.

The following figure depicts the status transitions of the booking life cycle status:

Status Transitions of the Booking Life Cycle Status


Bookings

In addition, a booking has a set of other statuses that are used to inform you about the progress of various activities. Although these statuses are independent, they can impact the life cycle status.

Related Information

Booking Statuses [page 177]

4.1.4 Booking Statuses

The Statuses tab on the Booking screen displays a set of statuses that are intended to inform you about the progress of various activities. Although these statuses are independent of the booking's life cycle status, they can impact the life cycle status.

A booking has the following statuses:

Field Description

Booking Approval Status

Certain types of cargo items may need approval before the booking can be confirmed. The system generates approval items based on the rules maintained in the Generic Validation Framework (GVF).

Route Status You can select a route using the Voyage Suggestion Framework (VSF). After the VSF is called, the system sets the route status as one of the following:

● Not Planned: indicates that route generation is not called yet● Planned: indicates that the route is determined● Planned Fail: indicates that no route is available

Equipment Status During route selection, the system checks whether the requested equipment is available, and then sets the equipment status as one of the following:

● Available: indicates that the requested equipment is available● Substituted: indicates that the requested equipment is replaced with a substitution, for ex

ample, due to unavailability or repositioning purposes● Fail: indicates that no equipment is available

Allocation Status During route selection, the system checks whether the requested capacity is available, and then sets the allocation status as one of the following:

● Passed: indicates that carrier capacity is available● Failed: indicates that carrier capacity is not available● Not required: indicates that the capacity check is not required


Field Description

Threshold Status The system compares the booking’s net-to-vessel (NTV) with the NTV threshold and then updates the threshold status, as follows:

● Not Checked● Above● Below

Prohibition Check Status

You can maintain prohibition-related rules in the GVF. The system checks these rules when you save or check the booking and then updates the status, as follows:

● Passed: indicates that the prohibition check passed● Failed: indicates that a prohibition exists and the check failed

Restriction Check Status

You can maintain restriction-related rules in the GVF. The system checks the rules when you save or check the booking and then updates the status, as follows:

● Passed: indicates that the restriction check passed● Failed: indicates that a restriction exists and the check failed

Cut-Off Status This field indicates whether the schedule has been checked to determine whether the required cut-off dates and time can be met, as follows:

● Not Checked● Passed: indicates that the schedule can meet the cut-off date and time● Failed: indicates that the schedule cannot meet the cut-off date and time

Customs Hold This field indicates whether there is a Customs hold, as follows:

● Inactive: indicates that there is no Customs hold● Active: indicates that there is a Customs hold

Rolling Status This field indicates whether the booking is rolled or not, as follows:

● Not Rolled: indicates that the booking has not been rolled● Rolled: indicates that the booking has been rolled

Filing Status If the booking involves a quotation rate, this field indicates whether the rate has been published to tariff, as follows:

● Not Checked: indicates that the filing status check is not required for the booking● Pending for TLI Publication: indicates that the quotation rate is used and not published to

tariff● TLI Published: indicates that the quotation rate is used and published to tariff● Irrelevant to FMC: indicates that the quotation rate is not used in the booking

Related Information

Approval Workflow [page 193]


Bookings

4.1.5 Mixed Cargo

A mixed cargo booking is a booking that contains two or more different types of cargo items. Cargo types include, but are not limited to, container cargo, roll-on roll-off (RORO) cargo, and break bulk cargo

Cargo can be RORO or break bulk, but not both. RORO and break bulk cargo items can only be inserted at the highest level in the item hierarchy. They cannot be inserted under a container item. You can set RORO and break bulk cargo as dangerous goods, and you must enter additional details for any dangerous goods in the booking.

Mixed cargo bookings can be linked to other types of bookings as follows:

● Flat rack bookings: bookings for special equipment that is used to reposition break bulk cargo● Side equipment bookings: bookings for special equipment with wheels that is used to drive containers and

break bulk cargo on and off vessels

Related Information

Break Bulk Cargo [page 179]Roll-On Roll-Off Cargo [page 182]Flat Rack Bookings [page 184]Side Equipment [page 183]

4.1.6 Break Bulk Cargo

Break bulk cargo does not fit within the dimensions of the frame for a single containerized structure and is carried on a flat bed trailer or on a platform container. Therefore, it must be loaded individually, and not in intermodal containers or in bulk as for coal or grain.

You can add a break bulk cargo item in the Booking screen by choosing Insert Break Bulk in the Items section. The system automatically selects the following Break Bulk checkboxes on the booking screen:

● For the specific cargo item in the Items table● For the overall booking in the Special Cargo group box on the General Data tab.

Break bulk items can only be inserted at the highest level in the cargo item hierarchy. They cannot be inserted under a container item. Flat rack equipment can be used by the carrier to reposition the break bulk cargo. You can link a flat rack booking to a booking with a break bulk cargo item.

Related Information

Creating Bookings [page 165]Side Equipment [page 183]Flat Rack Bookings [page 184]


4.1.7 Additional Over Dimensional Cargo Process

In addition to the original out of gauge (OOG) or break bulk (BB) process, you also have the option of over dimensional cargo process.

NoteThis process shall work only if SAP Transportation Management, lead to agreement for container shipping liners is installed.

You can enter the cargo dimension in a container item and then determine if it's an OOG cargo or a BB cargo, while comparing the cargo dimension with the predefined equipment dimension threshold. If a booking item is determined as a BB item, then flatrack booking is not necessary to track the container for carrier convenience, since the item is already a container item in the booking.

ExampleFor a particular sales organization, the following dimension threshold is defined:

Equipment Type Equipment Group Over Length ( Meter) Over Width ( Meter) Over Height ( Meter)

20G0 CN 1.5 0.5 0.4

The following rule is then applied after the booking item is entered:

● Normal Cargo: None of the cargo dimensions exceed the container dimension.● OOG Cargo: At least one cargo dimension exceeds the container dimension, however the extra

dimension is less than the respective threshold.● BB Cargo: At least one cargo dimension exceeds the respective container dimension threshold.

Consider the booking container item with the following information:

Item No. Equipment Type

Equipment Group

Length

( Meter)

Width

( Meter)

Height

( Meter)

Cargo Length

( Meter)

Cargo Width

( Meter)

Cargo Height

( Meter)

1 20G0 CN 5.1 2.9 2.8 4.8 2.4 2.3

2 20G0 CN 5.1 2.9 2.8 5.8 2.6 2.5

3 20G0 CN 5.1 2.9 2.8 5.9 3.6 2.6

After the rules are applied, the booking item numbers are determined as follows:

● Booking item number 1 is determined as normal cargo.● Booking item number 2 determined as OOG cargo, and the checkbox Overdimensional Cargo is

automatically selected.● Booking item number 3 is determined as break bulk item, and the checkbox Break Bulk is automatically

selected.


Bookings

Related Information

Entering the Dimensions of OOG and Break Bulk Cargo [page 173]

Break Bulk Cargo [page 179]

Flat Rack Bookings [page 184]

Determining Over Dimensional Cargo Type [page 181]

For more information about lead to agreement, see SAP Library for your SAP Transportation Management, lead to agreement for container shipping liners release on SAP Help Portal at https://help.sap.com/tm_csl_l2a, under Application Help.

4.1.7.1 Determining Over Dimensional Cargo Type

After the cargo dimension is entered into the booking item, it will be determined as normal cargo, OOG (out of gauge) cargo, or BB (break bulk) cargo, depending on the threshold for the respective equipment type.

Prerequisites

● The dimension threshold information has been defined in the input view /TMCSL/V_OOG_BB using the transaction SM30.

● The following user parameters have been added to user settings, using the transaction SU3:○ /TMCSL/UPBBO2C: If this parameter is active, then the Break Bulk checkbox is automatically selected

when cargo is determined as break bulk.○ /TMCSL/UPBBASOOGO2C: If this parameter is active, then then at least the Overdimensional Cargo

checkbox is automatically selected when cargo is OOG cargo.

Context

NoteYou can perfom this task only if SAP Transportation Management, lead to agreement for container shipping liners is installed.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Display Booking , and then open the relevant booking


https://help.sap.com/tm_csl_l2a

2. Insert a container item into the booking.3. Select the item and go to the Container Details tab; then enter cargo dimension and all other necessary

information.4. Save the booking.

Results

Once the cargo dimension is entered, the over dimension will be calculated and updated in the OOG/Break Bulk information tab. Accordingly the respective checkbox (Break Bulk or Overdimensional Cargo) in the booking item will be automatically selected depending on the predefined threshold for respective equipment type.

Related Information

Additional Over Dimensional Cargo Process [page 180]Break Bulk Cargo [page 179]Entering the Dimensions of OOG and Break Bulk Cargo [page 173]

4.1.8 Roll-On Roll-Off Cargo

Roll-on roll-off (RORO) cargo is wheeled onto and off vessels by means of a ramp. Examples of RORO cargo are cars, trailers, trucks, and machinery.

RORO cargo can be classified as follows:

● Self-driveSelf-drive RORO cargo is driven (usually by a stevedore) onto and off a vessel on its own wheels. Self-drive cargo is usually priority cargo and can have a late gate-in. Examples of self-drive cargo are cars and trucks.

● OtherFor all other RORO cargo, additional equipment (for example, a MAFI chassis and tractor) is used to drive the cargo onto and off the vessel. This additional equipment is referred to as side equipment. Examples of other RORO cargo types are trailers, normal containers, break bulk cargo, cars, industrial machines, and agricultural machines.

You add RORO cargo to a booking in the same way as other cargo types (for example, packages or containers). However, RORO items must always be at the highest level in the item hierarchy, that is, you cannot add a RORO item under a container item. You can also add any side equipment at the time of creating a booking.

When you add RORO cargo to a booking, the system automatically selects the following RORO checkboxes on the booking screen:

● For the specific cargo item in the Items table● For the overall booking in the Special Cargo group box on the General Data tab


Bookings

Before adding RORO cargo to a booking, you should ensure the following:

● An item category has been defined as a Passive Vehicle Resource and a resource class has been defined as a Trailer for the item type RORO in Customizing for SAP Transportation Management under

Transportation Management Forwarding Order Management Define Item Types for Forwarding Order Management .

● An equipment group and equipment type have been defined for RORO items in Customizing for SAP Transportation Management under Transportation Management Master Data Resources Define Equipment Groups and Equipment Types .

Related Information

Adding Side Equipment to Bookings [page 184]Side Equipment [page 183]Mixed Cargo [page 179]Creating Bookings [page 165]

4.1.9 Side Equipment

Side equipment with wheels is used to carry containers and break bulk cargo, and to drive them on and off vessels. Some types of side equipment can also be used to move cargo during intermodal transport on the road.

Typical examples of side equipment are as follows:

● MAFIMAFI trailers are used in ports to transport cargo on and off vessels. MAFI tractors are used to move MAFI trailers together with the cargo.

● Container ChassisA container chassis is a type of trailer onto which a container can be loaded. The chassis can be coupled to a pulling tractor, which can be used for inland movements to transport the container to the customer from the port.

Side equipment can be added on the Trip Plan tab in the Transportation Unit or Freight Unit screen to enable tracking or tracing. For example, a MAFI can be added as a resource on the transportation unit (TU) stage level for containerized cargo items, or on the freight unit (FU) stage level of break bulk cargo items. The MAFI travels together with the cargo items on specific stages of the transport.

Related Information

Adding Side Equipment to Bookings [page 184]


4.1.9.1 Adding Side Equipment to Bookings

Assign a side equipment resource such as a MAFI or a container chassis to a transportation unit (TU) for containerized cargo, or a freight unit (FU) for break bulk cargo.

Prerequisites

● MAFI and Chassis have been defined as resource classes with the resource type Transportation Unit Resources in Customizing for SAP Transportation Management under Transportation ManagementMaster Data Resources Define Resource Class .

● The resource classes have been assigned to the resource category in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash > Booking and DocumentationBooking Settings for Equipment and Resources Define Additional Resource Class for Resource Category .

● You have created MAFI or chassis resource master data with assignment to the corresponding resource classes in SAP NetWeaver Business Client under Master Data > Resources > Define Resource.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and open the relevant booking.

2. In the Item Hierarchy table, navigate to the FU/TU column and then click on the relevant FU/TU number.

The system displays the FU/TU screen.3. On the Trip Plan tab, select the relevant TU stage or FU stage in the Actual Route table.

The system displays the stage details below the table.4. On the Additional Resource tab, choose Add, and then enter the resource name for the MAFI or chassis.5. Save your entries.

4.1.10 Flat Rack Bookings

Break bulk cargo can require two bookings: one for the break bulk cargo itself and one for the flat rack equipment, which is used by the carrier to reposition the cargo. The flat rack booking is linked to the break bulk booking.

You can create flat rack bookings in the following ways:

● From the break bulk bookingYou can create a flat rack booking by opening a break bulk booking and choosing Follow Up Create Flat Rack Booking . The system automatically creates the link between the two bookings, which you can view


Bookings

on the Related Documents tab. The system only allows you to create a flat rack booking from a break bulk booking. This means that the booking must have at least one break bulk cargo item.

● As a new bookingYou can also create a flat rack booking as a new booking, which is independent from any break bulk booking. Then you can link the bookings manually on the Related Documents tab. When you link the bookings, the system validates that you are linking the flat rack booking to a booking that has at least one break bulk cargo item.

Related Information

Break Bulk Cargo [page 179]Creating Flat Rack Bookings from Break Bulk Bookings [page 185]Linking Flat Rack Bookings to Break Bulk Bookings [page 186]

4.1.10.1 Creating Flat Rack Bookings from Break Bulk Bookings

Create a flat rack booking by opening a break bulk booking and choosing Follow Up Create Flat Rack Booking . The system automatically creates the link between the two bookings.

Prerequisites

The flat rack booking type has been maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for Booking

Type Define Basic Settings for Booking Document Type .

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and then open the relevant break bulk booking.

2. In the toolbar, choose Follow Up Create Flat Rack Booking .

3. In the Items section, choose Insert Container , and insert the flat rack containers.4. Enter the required data.5. Save the booking.


Results

The system automatically adds the flat rack booking on the Related Documents tab of the break bulk booking, and also adds the break bulk booking on the Related Documents tab of the flat rack booking.

Related Information

Break Bulk Cargo [page 179]Flat Rack Bookings [page 184]Creating Bookings [page 165]Linking Flat Rack Bookings to Break Bulk Bookings [page 186]

4.1.10.2 Linking Flat Rack Bookings to Break Bulk Bookings

Create a flat rack booking using the usual procedure for creating bookings, and then manually link it to a break bulk booking. The system verifies that the booking to which you link your flat rack booking has at least one break bulk cargo item.

Prerequisites

The flat rack booking type has been maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for Booking

Type Define Basic Settings for Booking Document Type .

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Create Booking , and then create a flat rack booking by specifying the appropriate booking type.

2. Enter the required data, and then save the flat rack booking.

3. Choose Booking Booking Change Booking , and then open the relevant break bulk booking.

4. On the Related Documents tab, choose Add Flat Rack Booking .

The system displays a dialog box that lists the available flat rack bookings.5. Select the relevant flat rack booking and then confirm your entry.6. Save the booking.


Bookings

Results

The flat rack booking is added on the Related Documents tab of the break bulk booking, and the break bulk booking is added on the Related Documents tab of the flat rack booking.

Related Information

Break Bulk Cargo [page 179]Flat Rack Bookings [page 184]Creating Bookings [page 165]Creating Flat Rack Bookings from Break Bulk Bookings [page 185]

4.1.11 Booking Consolidation

If a customer requests it, you can use the booking consolidation feature to merge multiple bookings that have identical customer and route information into one of the existing bookings.

When you consolidate bookings, you have to enter an appropriate reason. The system aggregates all of the container data, costs, and rates from the original bookings into the consolidated booking and then recalculates the net-to-vessel (NTV) and charge. The booking validations are bypassed wherever appropriate. If a bill of lading (B/L) already exists for one or more of the bookings, the system automatically consolidates the relevant B/Ls.

The system stores the relationship between the original bookings and the consolidated booking, so that you can view the linkage between the original bookings and consolidated booking on the Document Flow tab in the Booking screen.

The system automatically cancels all of the original bookings after the consolidation. If a release order has already been created for an empty provisioning case, the corresponding release order is also consolidated.

Related Information

Consolidating Bookings [page 188]Creation of Release Orders for Merged Bookings [page 376]Creation of Release Orders for Split Bookings [page 377]


4.1.11.1 Consolidating Bookings

Consolidate multiple bookings with the same customer and route information into one booking using the Merge feature in the Booking screen.

Prerequisites

The reason code for the reason category MERGE has been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation BookingBasic Settings Define Activity Log Objects .

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and then open the main booking into which the other bookings are to be merged.

2. In the toolbar, choose Merge.

The system displays a dialog box.3. Specify the appropriate reason code and any additional remarks that you wish to record.4. Choose Add and enter the number of the booking that you want to merge into the current booking. You can

add multiple bookings as necessary.5. When you have added all of the relevant bookings, confirm your entries.

The system performs the following validation checks:

○ Compares the header data of the bookingsThe following fields must be the same:○ Booking Type○ Forwarding Agreement○ Shipper○ Consignee○ Ordering Party○ Source Location○ Destination Location○ Contract Type○ Load Vessel○ Load Voyage○ Load Port○ Discharge Port○ Carrier○ Origin Site Type

○ Compares the business partners


Bookings

All of the party roles and corresponding business partners must be consistent (if maintained), and one of the following cases must apply:○ The party role exists in the original booking but is not found in consolidation booking.○ The party role exists in the original booking and consolidation booking and the partners for this

party role are the same.○ The party role exists in the original booking and consolidation booking and the partner for this

party role in the original booking is blank.○ The party role exists in the original booking and consolidation booking and the partner for this

party role in the consolidation booking is blank.In all remaining cases, the validation check fails, and the system displays an error message.

○ Compares the stagesThe vessel/voyage should be consistent for the first main leg in the original booking and the consolidation booking.

○ Checks the template status of the bookings, and one of the following cases must apply:○ The original booking is a booking template.○ The original booking and the consolidation booking are not booking templates.

If the original booking is not a booking template and the consolidation booking is a booking template, then the check fails

○ Checks the booking confirmation status according to the following matrix:

Original Booking Status Consolidated Booking Status Consolidation is Allowed

Unconfirmed Unconfirmed Yes

Unconfirmed Confirmed No

Confirmed Unconfirmed No

Confirmed Confirmed Yes

NoteThere are three possible confirmation statuses: New, Pending Confirm, and Confirmed. In the table above, the status Unconfirmed includes New and Pending Confirm.

If the validation checks are successful, the bookings are consolidated. If the status of the consolidated booking is Confirmed, the system will re-confirm the booking when you save it.

6. Save the booking.

Results

Following the consolidation, the system voids the original bookings as they no longer have any booking items.

In the consolidated booking, you can view the link to the original bookings on the Document Flow tab and the consolidation event is recorded in the Activity Log tab along with the reason code and remarks you entered.

In the original booking, you can view the link to the consolidated booking on the Document Flow tab.


4.1.12 Split Bookings

A booking with one or more containers can be divided into multiple bookings. A booking can be split because of a customer request or an operational request (for example, insufficient space on the vessel).

Before splitting a booking, the system checks the booking status and the status of the assigned bill of lading (B/L). If a booking is confirmed and the corresponding B/L is generated, then the booking cannot be split and the system activates a B/L split.

You can split the following item types:

● Container itemsIn this scenario, the whole container is moved to the split booking and the related container unit for the container item is reassigned to the split booking. You can split a booking on the container level even if you do not know the container number at the time of the split. In this case, the booking is split by quantity and not by container.

● Package items under a container itemIn this scenario, only selected package items are reassigned to the new container in the split booking. The package item’s parent container information in the master booking is copied to the new container in the split booking. The package item’s parent container is in the master booking.

NoteYou cannot split package items that do not have a container as a parent.

You can create a new booking for the split or use an existing booking document. When you create a new booking for the split, the system copies the relevant information from the master (original) booking to the new booking. However, if you use an existing booking for the split, the booking data of the master booking is not copied to the existing booking.

After you split a booking, the system recalculates the booking confirmation status and related statuses.

If a release order has already been created for an empty provisioning case, the corresponding release order is also split.

Related Information

Splitting Bookings [page 191]Creation of Release Orders for Merged Bookings [page 376]Creation of Release Orders for Split Bookings [page 377]


Bookings

4.1.12.1 Splitting Bookings

Split a booking with single or multiple containers into multiple bookings. You usually split a booking because a customer requests it or for operational reasons such as shortage of space in the vessel.

Prerequisites

A reason code has been defined for the reason category SPLIT in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation BookingBasic Settings Define Activity Log Objects .

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and then open the booking that you want to split.

2. (Optional) On the Split tab, enter a reason code for the split and enter any additional remarks.3. On the Split tab, in the Item Hierarchy table, select the item or items that you want to split.4. In the Split Documents section, choose Add, and then select one of the following options:

○ NewThis option allows you to create a new booking for the split items. The master booking header data for the master (original) booking is copied to the split (target) booking without the item information. To enter an externally assigned booking number, you must first select the Ext. Assigned (Externally Assigned) checkbox.

○ ExistingThis option allows you to search for an existing booking, to which you can assign the split items. When you choose an existing booking, the booking header data of the master booking is not copied to the target booking.

5. Select the target booking in the table in the Split Documents section, and then choose Split.

The system checks the following data:

○ Header dataThe following header data in the master booking must match the data in the split booking:○ Booking Type○ Forwarding Agreement○ Shipper○ Consignee○ Ordering Party○ Source Location○ Destination Location○ Contract Type○ Load Vessel


○ Load Voyage○ Load Port○ Discharge Port○ Carrier○ Origin Site Type

○ Business partiesFor all party roles in the master booking, one of the following business party scenarios must be true:○ The party role exists in the master booking, but not in the split booking.○ The party role exists in the master booking and the split booking, and the partner for this party role

is the same in the master booking and split booking.○ The party role exists in the master booking and the split booking, and the partner for this party role

is blank in the master booking.○ The party role exists in the master booking and the split booking, and the partner for this the party

role is blank in the split booking.○ Stages

The vessel or voyage in the first main leg of the master booking must match the vessel or voyage in the split booking.

○ Template settingsOne of the following template scenarios must be true:○ The master booking is a booking template.○ Neither the master booking nor the split booking is a booking template.

For example, if the master booking is not a booking template and split booking is booking template, the system will not split the booking.

○ Booking statusThe system checks the confirmation status according to the following table:

Master Booking Status Split to New/Existing Booking

Split Booking Status Split is Possible

Unconfirmed New Not Applicable Yes

Confirmed New Not Applicable Yes

Unconfirmed Existing Unconfirmed Yes

Unconfirmed Existing Confirmed No

Confirmed Existing Unconfirmed No

Confirmed Existing Confirmed Yes

NoteThere are three possible confirmation statuses: New, Pending Confirm, and Confirmed. In the table above, the status Unconfirmed includes New and Pending Confirm.


The system saves and confirms the booking if the status of master booking status is confirmed.


Bookings

Results

You can view the following information about the split:

● The link to the split booking and master booking on the Document Flow tab● The split booking number in the split document table on the Split tab● The reason code and remarks on the Activity Log tab

Related Information

Split Bookings [page 190]Bill of Lading Split [page 312]Splitting Booking Items Automatically [page 170]Booking Confirmation [page 197]Creating Bookings [page 165]Booking Statuses [page 177]

4.1.13 Approval Workflow

If a booking contains special types of cargo, such as dangerous goods, break bulk, or out of gauge cargo, approval may be required before the booking can be confirmed.

When you save or check a booking, the system automatically generates the necessary approval items, based on the predefined rules in the Generic Validation Framework (GVF). You can also create approval items manually. These approval items are displayed on the Approval tab in the Booking screen.

The approval workflow begins when you choose the Submit for Approval button on the Approval tab. The system triggers the approval workflow using a Business Add-In (BAdI). The responsible user can then approve or reject each approval item as appropriate. An approval item contains the following information:

Field Description

Approval Type Defines the category of the approval item. In particular, the approval type can be used for special cargo (such as break bulk (B/B), out of gauge (OOG), and dangerous goods (DG)).The approval type is mandatory when creating a new approval item. When the GVF populates the approval item, the approval type is not editable.

Approval Role A free text field that is used to store the role, person, or party who is responsible for approving the item.


Field Description

Approval Mode Indicates the channel for approval. This field is used by the BAdI implementation and triggers the correct workflow. The following values are possible:

● 01 – E-Mail● 02 – Phone● 03 – Workflow

Approval Location Indicates the related location for the approval item. Only locations from the standard location master data are allowed for this field.

Approval Requirement Includes additional information such as detailed information about the cargo item. It is filled by the GVF only when the item is generated. It cannot be changed manually once the approval item is generated.

Approval Status Specifies the current status of the item

External Reference Number Free text and for reference only

Rejection Reason Code Specifies why the approval item is rejected and can be filled by the following methods:

● Manually● Output parameters from the Business Add-In (BAdI)

implementation● Workflow from an external system

Related Attachment You can link one attachment to each approval item.

Related Information

Submitting Booking Items for Approval [page 195]Approving or Rejecting Booking Items [page 196]Approval Status [page 197]


Bookings

4.1.13.1 Submitting Booking Items for Approval

Begin the approval workflow for a booking by submitting approval items for special cargo such as dangerous goods, break bulk, or out of gauge cargo.

Prerequisites

● The approval types have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Approval Define Approval Types .

● The rejection reason codes have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings

Define Activity Log Objects .The reason codes should be added under the reason category APPREJ.

● The Business Add-In (BAdI) /TMCSL/BADI_APP_ACTION_SUBMIT has been implemented in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Business Add-Ins (BAdIs) Approval BAdI: Triggering of External Approval Workflow .

Procedure


2. On the Approval tab, select the items that you want to submit for approval. The current approval status of the items must be New.

3. Choose Submit for Approval.

Results

The status of the selected items is changed to Pending Approval and the approval workflow begins.

Next Steps

The booking can only be confirmed when the status of all the approval items is either Approved or Conditionally Approved.


4.1.13.2 Approving or Rejecting Booking Items

Approve, conditionally approve, or reject booking items on the Approval tab of the Booking screen.

Prerequisites

● The approval types have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Approval Define Approval Types .

● The rejection reason codes have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings

Define Activity Log Objects .The reason codes should be added under the reason category APPREJ.

● The Business Add-In (BAdI) /TMCSL/BADI_APP_ACTION_SUBMIT has been implemented in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Business Add-Ins (BAdIs) Approval BAdI: Triggering of External Approval Workflow .

Procedure


2. On the Approval tab, select the items that you want to approve or reject. The current approval status of the items must be Pending Approval.

3. Choose one of the following options:

○ Approve○ Conditionally Approve○ Reject

Results

The status of the selected items is updated.

Next Steps

The booking can only be confirmed when the status of all the approval items is either Approved or Conditionally Approved.


Bookings

4.1.13.3 Approval Status

Each approval item has a status, and the overall booking approval status is determined by the highest priority approval item status as follows:

Priority Status Description Can Booking be Confirmed?

1 Rejected Rejected during the approval process

No

2 New Created but not submitted for approval yet

No

3 Pending Approval Submitted for approval No

4 Conditionally Approved Approved with a condition Yes

5 Approved Approved Yes

For example, if a booking contains two approval items, one with the status Approved and one with the status Rejected, the overall booking approval status is Rejected, and the booking cannot be confirmed.

Related Information

Submitting Booking Items for Approval [page 195]Approving or Rejecting Booking Items [page 196]

4.1.14 Booking Confirmation

Booking confirmation is an important step in the booking process. When you change the status of a booking to confirmed, the system performs a number of validation checks before assigning the container units to the manifest and consuming the allocated capacity.

A booking has a confirmation status, which is initially Not Confirmed. You can confirm a booking once the booking is accepted by both the ordering party and the carrier. As part of the confirmation process, the system performs a number of validation checks. If the validation process is successful, the status of the booking is changed to Confirmed, and the system consumes the allocated capacity and assigns the booking to a manifest

You can only create a bill of lading for a booking after the booking has been confirmed. If the booking confirmation status is set to Pending Confirm due to changes, no changes are permitted in the bill of lading.

When the booking confirmation status is confirmed, the system performs the confirmation validation checks each time the booking is saved.


Related Information

Confirming Bookings [page 198]

4.1.14.1 Confirming Bookings

Change the status of a booking to confirmed when it is accepted by both the ordering party and the carrier.

Prerequisites

● The forwarding order type has been defined in Customizing for SAP Transportation Management under Transportation Management Forwarding Order Management Forwarding Order Define Forwarding

Order Type .● The basic settings for the booking document type have been defined in Customizing for SAP

Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for Booking Type Define Basic Settings for Booking Document Type .

● The reason category BOKCNF and the reason code CONFMED have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings Define Activity Log Objects .

Procedure


2. In the header toolbar, choose Confirm.The system performs a consistency check on the booking. If any errors are found, the system stops the confirmation process and displays a message. The system also performs the following status checks, which are dependent on the Customizing settings for the booking document type:

Status Check Customizing Setting Processing

Route Status Not Relevant Not checked

Relevant The booking can only be confirmed if the Route Status is Planned

Charge Calculation Status Not Relevant Not checked


Bookings

Status Check Customizing Setting Processing

Calculated The booking can be confirmed only when the charge calculation status is Calculated.

Calculated or Calculation Error The booking can be confirmed when the charge calculation status is Calculated or Calculation Error.

Equipment Status Not Relevant Not checked

Available, Substituted, or Fail The booking can only be confirmed when the equipment availability status is Available, Substituted, or Not Required.

Threshold Status Not Relevant Not checked

Above The booking can only be confirmed when threshold status is Above.

Below The booking can only be confirmed when threshold status is Below.

Prohibition Status Not Relevant Not checked

Relevant The booking can only be confirmed when the prohibition status is Passed.

Restriction Status Not Relevant Not checked

Relevant The booking can be confirmed only when the restriction status is Passed.

Booking Approval Status Not Relevant Not checked

Relevant The booking can only be confirmed when the booking approval status is Not Required, Approved, or Conditionally Approved.

Allocation Status Not Relevant Not checked

Relevant The booking can only be confirmed when the allocation status is Passed.

If the validation process is successful, the system performs the following steps:1. Assigns the container units to the manifest (container units for no-show booking items are not

assigned to the manifest)


2. Records the confirmation event in the activity log with the category BOKCNF and the reason code CONFMED

3. Consumes the allocated capacity4. Changes the booking confirmation status to Confirmed.

If any of the validation checks fail, the status of the booking is changed to Pending Confirm.

Next Steps

You can proceed to create the bill of lading.

4.1.15 Booking Cancellation

The system allows authorized users to manually cancel bookings, for example, when requested to do so by the customer or in the event of a no-show. In certain situations, bookings are automatically canceled, for example, during booking consolidation.

You can manually cancel a booking, for example, in the following scenarios:

● The customer requests the booking to be canceled.● The booking is a no-show.● The customer fails to meet any of the mandatory cut-off dates for the booking.

The system automatically cancels a booking when all the items are consolidated or split to other bookings.

Only authorized users can manually cancel bookings, and the system verifies your authorization when you try to cancel a booking. The necessary authorization can be provided based on your user role or based on your individual user ID.

When you cancel a booking, you select the relevant reason from a preconfigured list of reason codes. Then the system performs several validation checks to ensure that it is appropriate to cancel the booking. For example, you are not permitted to cancel a booking if the cargo for the booking has already been loaded. In certain cases, the system changes the status of the booking to Pending Cancel, and performs no other changes to the booking until further events occur.

As part of the cancellation process, the system removes all linkages to the booking, and if a bill of lading (B/L) has been generated, the system automatically cancels it.

You can reuse a canceled booking number by reactivating the canceled booking. The reactivated booking is actually a new booking and has no relationship with the original booking.

If a booking is canceled due to a no-show, the system can automatically determine the reason code based on business rules for the country or the customer. Then based on the reason code, you must enter some required data for the charge calculation process to trigger re-rating and invoicing according to this specific cancellation reason code

If a release order has already been created for this booking, the booking cancellation also leads to cancellation of the release order.


Bookings

Related Information

Canceling Bookings [page 201]Reactivating Canceled Bookings [page 203]No-Show and Late Handling [page 218]Release Order Cancellation [page 373]

4.1.15.1 Canceling Bookings

Cancel a booking, for example, when requested to do so by the customer or in the event of a no-show.

Prerequisites

● The reason code for the reason category CANCEL has been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking

Basic Setting Define Activity Log Objects .● The forwarding order types have been defined in Customizing for SAP Transportation Management under

Transportation Management Forwarding Order Management Forwarding Order Define Forwarding Order Types .

● The movement types have been defined in Customizing for SAP Transportation Management under Transportation Management Forwarding Order Management Define Movement Types .

● The operational statuses for events have been assigned in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill of Lading Assign Operational Statuses for Events .

● You have the required authorization to cancel bookings.

Procedure


2. In the toolbar, choose Cancel.

The system displays a dialog box.3. Specify the appropriate reason code, enter any additional explanatory remarks, and then confirm your

entries.

The system performs the following validation checks:

○ If the Manifest Load Status is Loaded or Partially Loaded, the system stops the cancellation and displays an error message.


○ If the status of the booking is New or Draft, the cancellation is allowed to continue.○ If the Set Default Destination Location from Consignee Location option is set for the booking movement

type, the status is set to Pending Cancel.○ For bookings with empty provision or empty return items, the system checks whether all released

containers have been returned, and if not, the system sets the booking status to Pending Cancel.

If a bill of lading (B/L) has been generated for the booking, the system performs the following validation checks:

○ If charge calculation is enabled, the system checks the Export Financial Status for the B/L. If the status is Not Paid or Partially Paid, the system sets the booking status to Pending Cancel.

○ If any of the following conditions apply to the B/L, the system sets the booking status to Pending Cancel:○ The B/L type is Original Bill of Lading (OBL).○ The B/L validation code is Received for Shipment (RFS).○ The B/L release status is Authorized or Released.○ The documentation status is not Cleared.

If all of the validation checks are passed and the booking status has not been changed to Pending Cancel, the system performs the cancellation as follows:

1. Adds an event to the activity log with the entered reason code and remark2. Changes the booking status to Canceled (unless the booking status is Void, in which case it remains as

Void)3. Cancels all freight units (FU), transportation units (TU), and container units (CU) that have been

generated by the freight unit building rule4. If the reason code for the cancellation is NOSHOW, selects the No-Show checkbox for all of the booking

items5. Resets the following statuses:

○ Empty Container Release Status○ Empty Container Return Status○ Manifest Load Status○ Gate-In (Port of Loading) Status○ Load (Last Port of Transshipment) Status○ Discharge Status for Manifest

6. For part-load bookings, the system deletes replicated items in the related equipment booking.

Results

After the booking has been successfully canceled, you can see the cancellation event listed on the Activity Log tab. You can make no further changes to a canceled booking; however, if you wish to reuse the booking, you can reactivate it.


Bookings

4.1.15.2 Reactivating Canceled Bookings

Reuse a canceled booking number by reactivating the canceled booking. The reactivated booking is in effect a new booking and has no relationship with the original booking. The reactivated booking undergoes the same validation processes as a new booking.

Prerequisites

● The reason code REACTIV for the reason category REATVE has been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings Define Activity Log Objects .

● The forwarding order types have been defined in Customizing for SAP Transportation Management under Transportation Management Forwarding Order Management Forwarding Order Define Forwarding

Order Types .● The movement types have been defined in Customizing for SAP Transportation Management under

Transportation Management Forwarding Order Management Define Movement Types .● The operational statuses for events have been assigned in Customizing for SAP Transportation

Management under Container Shipping Liners Order to Cash Booking and Documentation Bill of Lading Assign Operational Statuses for Events .

Procedure


2. In the header toolbar, choose Reactivate Booking.3. The system performs the following steps:

○ Changes the Booking Confirmation Status to Not Confirmed○ Changes the Booking Status to New○ Deselects the Booking Confirmed checkbox○ Deselects the No-Show checkbox for any no-show booking items

Results

After the booking has been successfully reactivated, you can see the reactivation event listed on the Activity Log tab, and you can continue to edit the booking as necessary.


4.1.16 Detention in Transit Requests

A detention in transit (DIT) is a request from a customer to delay the cargo while it is in transit and hold it for storage at a location other than the origin or destination.

While a booking is in transit, you can delay the cargo if requested to do so.

When a DIT is requested, you create a DIT request document. This DIT request document is a copy of the original booking, which can be edited and includes some additional information. The data you enter in the DIT request document is validated against the same rules as the original booking type.

The system also redetermines the costs, calculates the charges, calculates the contribution, and runs a customer credit check if the costs for the DIT need to be charged to the customer.

If all of the validation checks are passed successfully, the system activates the DIT request, which must be approved before it can be applied to the booking. When the DIT request is applied, the system overwrites the master booking with the details from the DIT request and adjusts all the related documents such as the manifest assignment and the bill of lading.

DIT Request Statuses

A DIT request follows a life cycle and requires approval before it can be applied to a booking. The possible statuses are as follows:

Status Description

Draft The DIT request has been saved using the Save Draft option, and therefore, no validation checks have been run.

Pending The DIT request has passed all the validation checks, and one or more of the approval items are still awaiting approval.

New The DIT request has passed all validations, and all the approval items have been approved. DIT requests with the status New can be applied to the master booking.

Applied The DIT request has been applied to the master booking and is now read-only.

Rejected The DIT request has been rejected, and is now read-only.

Related Information

Creating DIT Requests [page 205]Applying DIT Requests [page 207]Rejecting DIT Requests [page 208]


Bookings

4.1.16.1 Creating DIT Requests

Create a detention in transit (DIT) request for cargo items that are in transit if requested to do so by the customer. DIT requests are subject to an approval process.

Prerequisites


Order Types .● The basic settings for booking document type have been defined in Customizing for SAP Transportation

Management under Container Shipping Liners Order To Cash Booking and Documentation BookingSettings for Booking Type Define Basic Settings for Booking Document Type .

● The reason category DITR and an appropriate reason code under this category have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Basic Settings Define Activity Log Objects .

● The reason category DITREQ and an appropriate reason code under this category have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Basic Settings Define Activity Log Objects .

● The reason category DITAPP and the reason code DITAPL under this category have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Basic Settings Define Activity Log Objects .

Context

The Create DIT Request option is only enabled when the following conditions apply:

● The booking status is either Confirmed or Completed.● There are no active (that is New or Pending) DIT requests or diversion requests for the booking.● The booking is a master booking.

NoteYou cannot create a DIT request for the following types of booking:

● Less than container load (LCL) booking● Inland booking● Flat rack booking● Part-load booking● Partner cargo recovery booking


Procedure


2. In the toolbar, choose Follow Up Create DIT Request .

The system displays the new DIT request document, which looks similar to a booking and has an extra DIT tab.

3. Enter the following information:

○ On the DIT tab, enter the mandatory information such as the DIT port, the DIT reason, and the DIT duration in days.

○ In the Items section, adjust the item details if necessary, for example, you can delete any items that are not being detained, or you can reduce the quantity.

○ On the Charges tab, adjust the charge items if necessary.4. Save the DIT request using one of the following options:

○ Choose Save Draft to bypass all validation and set the status of the DIT request status to Draft.○ Choose Save to perform all of the validation checks and create an approval item. If the validation

checks are passed, the status of the DIT request is set to Pending.5. Choose Generate Routes to generate the route proposals for the DIT request, and then choose the

appropriate route.6. On the Approval tab, choose Submit for Approval.

Next Steps

When the DIT request been approved, you can apply it to the master booking.

Related Information

Applying DIT Requests [page 207]Rejecting DIT Requests [page 208]


Bookings

4.1.16.2 Applying DIT Requests

Apply an approved detention in transit (DIT) request to the master booking. The system updates the master booking as necessary and also makes the required updates to the associated manifest.

Prerequisites



Management under Container Shipping Liners Order To Cash Booking and Documentation BookingSettings for Booking Type Define Basic Settings for Booking Document Type .




Procedure


2. In the toolbar, choose DIT Apply DIT .

The subsequent processing depends on the DIT scenario as follows:

○ Full DIT (no changes to the booking items or quantities)The system performs the following steps:1. Checks the DIT request status2. Updates the activity log in the master booking to include the application of the DIT3. Unassigns the freight unit (FU) from the manifest4. Copies the route from the DIT request to the master booking5. Assigns the FU to the manifest based on the new route6. Copies the created service items from the DIT request to the master booking7. Copies the manual charge item line from the DIT request to the master booking8. Copies the DIT request status to the master booking and reconfirms the master booking


During the master booking confirmation, the system changes the DIT request status to Apply Started. This is a temporary status.

9. Sets the DIT request status to Applied when the master booking is confirmed○ Partial DIT (booking items have been deleted or quantities have been reduced)

The system performs the following steps:1. Creates a new booking (a split booking) for the booking items that are included in the DIT request2. Checks the DIT request status3. Updates the activity log in the master booking and the split booking to include the application of

the DIT.4. Unassigns the FU of the split booking from the manifest5. Copies the route from the DIT request to the split booking6. Assigns the FU to the manifest based on the new route in the split booking7. Copies the created service items from the DIT request to the split booking8. Copies the manual charge item line from the DIT request to the split booking9. Changes the master booking number in the DIT request to the split booking number10. Adds the DIT request number in the document flow for the split booking number11. Copies the DIT request status to the split booking and reconfirms the split booking

During the split booking confirmation, the system changes the DIT request status to Apply Started. This is a temporary status.

12. Sets the DIT request status to Applied when the split booking is confirmed

Related Information

Creating DIT Requests [page 205]Rejecting DIT Requests [page 208]

4.1.16.3 Rejecting DIT Requests

Reject a detention in transit (DIT) request, so that no changes are made to the original booking and manifest.

Prerequisites



Management under Container Shipping Liners Order to Cash Booking and DocumentationBooking Settings for Booking Type Define Basic Settings for Booking Document Type .


Bookings




Procedure


2. In the toolbar, choose DIT Reject DIT .3. The system displays a dialog box.4. Enter a reason code and remark for the rejection, and then confirm your entries.

The system updates the document statuses as follows:

1. Changes the master booking status back to the status it was before the DIT request was created2. Changes the DIT request status to Rejected

Related Information

Creating DIT Requests [page 205]Applying DIT Requests [page 207]

4.1.17 Diversion Requests

A diversion request is a request to change the destination of a booking after the cargo has already been loaded onto the vessel. Diversion requests can be initiated by the shipper, the consignee, or the carrier.

After a booking is confirmed, you can still change the destination or divert the booking to another routing. To process a change of destination, you create a diversion request document. This diversion request document is a copy of the original booking, which can be edited and includes some extra fields. You enter the details of the diversion request in this new diversion request document and then recalculate the route, rate, and net-to-vessel (NTV) without changing the original booking. The data in the new diversion request booking is validated against the same rules as the original booking type.

The system also re-determines the costs, calculates the charges, calculates the contribution, and runs a customer credit check if the costs for the change need to be charged to the customer (determined by the


reason code provided in the diversion request). If the diversion is due to the carrier’s operational issues, no additional diversion charges should be applicable to the customer.

If all of the validation checks are passed successfully, the system activates the diversion request and updates the requested routing. Diversion requests follow an approval process similar to new bookings. When the diversion request is approved and then applied, the system overwrites the master booking with the data in the diversion request and adjusts all of the related documents such as the manifest assignment and the bill of lading.

Diversion Request Document Statuses

A diversion request follows a life cycle and requires approval before it can be applied to a booking. The possible statuses are as follows:

Status Description

Draft The diversion request has been saved using the Save Draft option, and therefore, no validation checks have been run.

Pending The diversion request has passed all the validation checks, and one or more of the approval items are still awaiting approval.

New The diversion request has passed all validations, and all the approval items have been approved. Diversion requests with the status New can be applied to the master booking.

Applied The diversion request has been applied to the master booking and is now read-only.

Rejected The diversion request has been rejected, and is now read-only.

Related Information

Creating Diversion Requests [page 211]Applying Diversion Requests [page 213]Rejecting Diversion Requests [page 214]


Bookings

4.1.17.1 Creating Diversion Requests

Create a diversion request for a booking, and then enter the details of the diversion. The diversion request must be approved before you can apply it to the master booking.

Prerequisites



Management under Container Shipping Liners Order to Cash Booking and Documentation BookingSettings for Booking Type Define Basic Settings for Booking Document Type .


● The reason category DIT and an appropriate reason code under this category have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Basic Settings Define Activity Log Objects .

Context

The Create Diversion Request option is only enabled when the following conditions apply:

● The booking status is Confirmed or Completed.● There are no active (that is, new or pending) detention in transit (DIT) requests or diversion requests for

the booking.● The booking is a master booking.

NoteYou cannot create a diversion request for the following types of booking:

● Less than container load (LCL) booking● Inland booking● Flat rack booking● Part-load booking● Partner cargo recovery booking


Procedure


2. In the toolbar, choose Follow Up Create Diversion Request .

The system displays the new diversion request document, which looks similar to a booking and has an extra Diversion Details tab.

3. Enter the following information:○ On the Diversion Details tab, enter the mandatory information such as the new destination location

and the new consignee.○ In the Items section, adjust the item details if necessary, for example, you can delete any items that are

not being diverted, or reduce the quantity.On the Charges tab, adjust the charge items if necessary.

4. Save the diversion request using one of the following options:

○ Choose Save Draft to bypass all validation and set the status of the diversion request to Draft.○ Choose Save to perform all of the validation checks and create an approval item. If the validation

checks are passed, the status of the diversion request is set to Pending.5. Choose Generate Routes to generate the route proposals for the diversion request, and choose the

appropriate route.6. On the Approval tab, choose Submit for Approval.

Next Steps

When the diversion request been approved, you can apply it to the master booking.

Related Information

Rejecting Diversion Requests [page 214]Applying Diversion Requests [page 213]


Bookings

4.1.17.2 Applying Diversion Requests

Apply an approved diversion request to the master booking. The system updates the master booking as necessary and also makes the required updates to the associated manifest.

Prerequisites




● The reason category DITR and an appropriate reason code under this category have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings Define Activity Log Objects .

● The reason category DIT and an appropriate reason code under this category have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings Define Activity Log Objects .

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and then open the relevant diversion request.

2. In the toolbar, choose Diversion Apply Diversion .

The subsequent processing depends on the diversion scenario as follows:

○ Full Diversion (no changes to the booking items or quantities)The system performs the following steps:1. Checks the diversion request status2. Unassigns the freight unit (FU) from the manifest3. Copies the route from the diversion request to the master booking4. Assigns the FU to the manifest based on the new route5. Copies the created service items from the diversion request to the master booking6. Copies the manual charge item line from the diversion request to the master booking7. Copies the diversion request status to the master booking and reconfirms the master booking

During the master booking confirmation, the system changes the diversion request status to Apply Started. This is a temporary status.

8. Sets the diversion request status to Applied when the master booking is confirmed○ Partial Diversion (booking items have been deleted or quantities have been reduced)


The system performs the following steps:1. Creates a new booking (a split booking) for the booking items that are included in the diversion

request2. Checks the diversion request status3. Unassigns the FU of the split booking from the manifest4. Copies the route from the diversion request to the split booking5. Assigns the FU to the manifest based on the new route in the split booking6. Copies the created service items from the diversion request to the split booking7. Copies the manual charge item line from the diversion request to the split booking8. Changes the master booking number in the diversion request to the split booking number9. Adds the diversion request number in the split booking number document flow10. Copies the diversion request status to the split booking and reconfirms the split booking

During split booking confirmation, the system changes the diversion request status to Apply Started. This is a temporary status.

11. Sets the diversion request status to Applied when the split booking is confirmed

Related Information

Creating Diversion Requests [page 211]Rejecting Diversion Requests [page 214]

4.1.17.3 Rejecting Diversion Requests

Reject a diversion request, so that no changes are made to the original booking and manifest.

Prerequisites





● The reason category DIT and an appropriate reason code under this category have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Basic Settings Define Activity Log Objects .


Bookings

Procedure


2. In the toolbar, choose Diversion Reject Diversion .

The system displays a dialog box.3. Enter a reason code and a remark for the rejection, and then confirm your entries.

The system updates the document statuses as follows:

○ Changes the master booking status back to the status it was before the diversion request was created○ Changes the diversion request status to Rejected

Results

The diversion request document is now read-only.

Related Information

Creating Diversion Requests [page 211]Applying Diversion Requests [page 213]

4.1.18 Invoicing for Partner Cargo

Create forwarding settlement documents based on bookings with restricted follow-on processing for the partner cargo settlement process.

Prerequisites

The booking type for partner cargo has been defined as a commercial booking type in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation

Booking Settings for Booking Type Define Basic Settings for Booking Document Type , and the booking category is 03 – Cargo Settlement.


Context

Restricted follow-on processing means that the booking type is only relevant for invoicing. Due to this restriction, you do not need to enter all of the execution-related data in the booking.

In general, when you save a booking, the system validates the booking and displays error messages if any mandatory data is missing. The system also checks that the entered data is consistent to perform the execution processes. To enable certain processes such as partner cargo settlement, certain validation checks can be turned off in the Customizing activity Define Basic Settings for Booking Document Type. The system provides a specific booking category called Cargo Settlement, and you can create a booking type with this booking category to bypass any unnecessary validation checks for partner cargo settlement.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Create Booking .2. On the initial screen, specify the relevant booking type for partner cargo, and choose Continue.3. Enter the required data.4. Save your changes.5. To create the forwarding settlement document, choose one of the following options:

○ Follow Up Create Final Invoice Request

○ Follow Up Create Proforma Invoice Request

NoteFor more information about the standard SAP functionality for settlement, see SAP Library for your SAP Transportation Management release on SAP Help Portal at https://help.sap.com/transportationmanagement. Under Application Help, open SAP Library and search for Settlement.

4.1.19 Booking Worklists

Booking worklists provide easy access to individual bookings that share common attributes and allow you to execute actions on selected bookings. Booking worklists are based on the SAP Personal Object Worklist (POWL), which means that you can define and store worklists that are defined as queries.

The following booking worklists are available, each of which contain predefined queries:

● Overview Bookings● Overview Bookings with Expired Release Orders

To access the worklists in SAP NetWeaver Business Client, choose Booking Worklist .


Bookings



Related Information

Viewing Special Cargo Types in Worklists [page 217]Viewing Bookings with Expired Release Orders [page 218]

4.1.19.1 Viewing Special Cargo Types in Worklists

Use the Show Quick Criteria Maintenance feature to find all of the bookings with out of gauge (OOG) and break bulk cargo.

Prerequisites

The personal object worklist (POWL) type SCMTMS_TRQ_03 has been assigned to you in the transaction POWL_COCKPIT.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Worklist Overview Booking Booking .2. Choose Show Quick Criteria Maintenance.3. Specify the required search criteria, for example, as follows:

○ To view bookings with roll-on roll-off cargo, specify True in the RORO field.○ To view bookings with break bulk cargo, specify True in the Break Bulk field.○ To view bookings with OOG cargo, specify True in the OOG Cargo field.

4. Choose Apply.5. Choose Hide Quick Criteria Maintenance.

Related Information

Booking Worklists [page 216]


4.1.19.2 Viewing Bookings with Expired Release Orders

Use the Show Quick Criteria Maintenance feature to find all of the bookings with expired release orders.

Prerequisites

The personal object worklist (POWL) type /TMCSL/POWL_TYPE_TRQ_RO_EXPIR has been assigned to you in the transaction POWL_COCKPIT.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Worklist Overview Bookings with Expired Release Orders .

2. Choose Show Quick Criteria Maintenance.3. Specify the required search criteria, for example, as follows:

○ To view bookings with expired release orders, set the Release Order Life Cycle Status field to Expired.

NoteThis field is set to Expired by default and cannot be changed.

○ To view bookings with expired release orders for a sales office, specify the organization ID in the Sales Office field.

4. Choose Apply.5. Choose Hide Quick Criteria Maintenance.

Related Information

Release Orders [page 365]Release Order Expiration [page 373]

4.1.20 No-Show and Late Handling

If a container does not gate-in before the container yard cut-off, but is loaded onto the vessel, it is handled as a late container. If a container is not loaded onto the vessel, it is handled as a no-show. There may be additional fees for late and no-show items.

If you set a cargo item as late or no-show, the system can charge additional fees. These fees are based on the business rules that are maintained for markets or countries, or are contracted directly with customers.


Bookings

To handle late items, you set the cargo item as late on the Booking screen for charge calculation purposes. There is no other special functionality for this scenario. To handle no-show items, you set the cargo item as a no-show on the Booking screen. In addition to enabling the charge calculation, the no-show flag also prevents any subsequent activities for the item.

You can also reset late and no-show cargo items to the normal status.

Related Information

Setting Cargo Items as Late [page 219]Resetting Late Cargo Items [page 220]Setting Cargo Items as No-Show [page 221]Resetting No-Show Cargo Items [page 222]

4.1.20.1 Setting Cargo Items as Late

Set a cargo item as late when the container was not gated-in before the container yard cut-off, but was still loaded onto the vessel, so that the appropriate late handling fee can be charged.

Prerequisites

● The block reason code N1 has been defined in Customizing for SAP Transportation Management under Transportation Management Basic Functions General Settings Define Block Reason Codes .

● The booking status is Confirmed.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and open the relevant confirmed booking.

2. In the Items section, select the relevant cargo items.

3. In the Items table toolbar, choose Set as No Show Set as Late .

On the Container Details tab for the selected cargo items, the system selects the Late checkbox. The system also sets the booking status to Pending Confirm. You need to reconfirm the booking manually.

4. To reconfirm the booking, choose Confirm in the toolbar.5. Save the booking.


Related Information

Resetting Late Cargo Items [page 220]

4.1.20.2 Resetting Late Cargo Items

Reset the Late checkbox for a cargo item that has previously been set as late.

Prerequisites



Procedure


2. In the Items section, select the relevant cargo items that have the Late checkbox selected.

3. In the Items table toolbar, choose Set as No Show Reset Late .

On the Container Details tab for the selected cargo items, the system deselects the Late checkbox for the selected items. The system also sets the booking status to Pending Confirm. You need to reconfirm the booking manually.

4. To reconfirm the booking, choose Confirm in the toolbar.5. Save the booking.

Related Information

Setting Cargo Items as Late [page 219]


Bookings

4.1.20.3 Setting Cargo Items as No-Show

Set a cargo item as a no-show when the container is late and is not loaded onto the vessel, so that the cargo item is processed appropriately and the no-show fee can be charged.

Prerequisites



Procedure


2. In the Items section, select the relevant container items.

3. In the Items table toolbar, choose Set as No Show Set as No Show .

The system performs the following actions:

○ Selects the No Show checkbox (displayed in the Items table and on the Container Details tab)○ Sets the booking status to Pending Confirm○ Unassigns the related freight units (FUs) from the manifest○ Blocks the related FU’s planning with reason code N1

NoteRelated FUs are the FUs that are generated based on the no-show items.


Results

When items are set as no-shows, the system separates the no-show items from normal cargo items as follows:

● The system doesn’t consider no-show items as actual items. That is, the system doesn’t transfer no-show items to the Voyage Suggestion Framework (VSF) for route suggestion and capacity booking.

● The system doesn’t copy no-show items to the following processes:○ DIT request○ Diversion request○ Inland booking○ Delivery order


● The system doesn’t consider no-show items when assigning FUs to the manifest.

As no-show fees are required for no-show items, the system supports charge calculation and forwarding settlement for no-show items.

Related Information

Resetting No-Show Cargo Items [page 222]

4.1.20.4 Resetting No-Show Cargo Items

Reset the No Show checkbox for a cargo item that has previously been set as a no-show.

Prerequisites



Procedure


2. In the Items section, select the relevant container items that have the No Show checkbox selected.

3. In the Items table toolbar, choose Set as No Show Reset No Show .

On the Container Details tab for the selected items, the system deselects the No Show checkbox. The system also sets the booking status to Pending Confirm. You need to reconfirm the booking manually.

4. To reconfirm the booking, choose Confirm in the header toolbar.5. Save the booking.

Related Information

Setting Cargo Items as No-Show [page 221]


Bookings

4.1.21 Inland Bookings

An inland booking is used to transport the cargo on an international booking from the port of discharge to the destination location. An inland booking is added to an existing international booking.

Inland bookings are a special type of booking and are processed in the system in the same way as the booking type Commercial Laden.

You assign inland bookings to international bookings. Multiple inland bookings can be assigned to one international booking, but only if the total of the cargo items in the inland bookings is less than or equal to the total cargo items in the international booking. When you assign an inland booking to an international booking, the system copies the cargo items from the international booking to the inland booking.

NoteCargo items that are marked as no-show or cargo items that are linked to an active inland booking are not copied to the inland booking.

After assigning an inland booking, you can view the relationship between the inland booking and the international booking on the respective booking’s Document Flow tab.

You cannot perform the following operations on an inland booking:

● Create an inland booking● Create a delay in transit request● Create a diversion request● Generate a bill of lading● Assign the booking to a manifest● Split the booking● Consolidate the booking

Related Information

Creating Inland Bookings [page 224]Creating Bookings [page 165]


4.1.21.1 Creating Inland Bookings

Assign an inland booking to an existing international booking when you need to transport cargo over land from the port of discharge to the destination location.

Prerequisites

● The inland booking type has been assigned to the commercial booking type in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for Booking Type Define Basic Settings for Booking Document Type.

● The relevant cargo modes have been defined, and the Inland checkbox is selected for the relevant cargo delivery mode in Customizing for SAP Transportation Management under Container Shipping LinersOrder to Cash Booking and Documentation Booking Basic Settings Define Cargo Modes.

● The quantity of the valid items in the inland booking is less than the quantity of the valid items in the international booking.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Display Booking and then open the relevant international booking.

2. Choose Follow Up Create Inland Booking .

Before creating the new inland booking, the system checks the following information in the international booking:

○ The subcategory for the international booking is 01 (International).○ The booking status of the international booking is not Canceled or Pending Cancel.○ The Store Door Destination checkbox on the General Data tab is not selected.○ A consignee is assigned to the international booking on the General Data tab.

If the checks are passed, the system performs the following steps:

○ Creates a new inland booking with the booking type Inland Booking○ Copies the cargo items from the international booking to the inland booking

NoteNote that the system does not copy any items that are marked as no-show or are linked to an active inland booking.

○ Copies the following information from the international booking to the new booking:


Bookings

International Booking Fields Inland Booking Fields

Consignee Booking Party

Shipper

Destination Location Source Location (read only)

Cargo Delivery Mode Cargo Receipt Mode

3. Delete any items that are not required for the inland booking, for example, partial items that have an additional inland leg.

4. Enter the relevant inland booking details.5. Save the inland booking.

Results

You can view the related information for each of the bookings as follows:

● On the Document Flow tab of the international booking, you can view the details of the inland booking.● On the Document Flow tab of the inland booking, you can view the number of the international booking.

Related Information

Inland Bookings [page 223]Creating Bookings [page 165]

4.1.22 Less Than Container Load Bookings

Less than container load (LCL) bookings refer to bookings for which the cargo cannot occupy a full container. The carrier may consolidate cargo from multiple LCL bookings into one container, which is referred to as an LCL shipment.

Related Information

Creating Less Than Container Load Bookings [page 226]


4.1.22.1 Creating Less Than Container Load Bookings

Create a less than container load (LCL) booking with shipping type LCL in cases when the cargo cannot occupy a full container.

Prerequisites

● The LCL shipping types have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Less Than

Container Load Maintain Relationship Between Shipping Type and LCL .● The LCL transportation unit document types have been defined in Customizing for SAP Transportation

Management under Container Shipping Liners Order to Cash Booking and Documentation BookingLess Than Container Load Maintain Relationship Between TOR Type and LCL .

● The indicator specifying whether an LCL type can be changed in an LCL booking has been maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Setting for Booking Type – > Define Basic Settings for Booking Document Type.

● The Business Add-In BAdI: Fetching of Location Usage Type has been implemented to identify the container freight station (CFS) location in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Business Add-Ins (BAdIs) Booking BAdI: Fetching of Location Usage Type .

Context

After creating the LCL booking, you generate freight units (FUs) at package level, create a container unit (CU) with the necessary information, and assign related FUs of the LCL booking to this CU. The system then checks all FUs that are assigned to the CU and updates the CU stages accordingly. In the execution phase, this CU is considered a container and assigned to the manifest. All of the LCL FUs in the same TU will share the same execution information.

Procedure

1. In SAP NetWeaver Business Client, create the relevant booking with LCL shipping type.2. Enter the following information on the LCL Information tab:


Bookings

Field Description

LCL Type Specifies the LCL shipment type (for example, Military Stuffing, Military Break Bulk, or LCL Consolidation)

LCL Charge Clarification Indicates how LCL charges are calculated

Note: The value in this field is read-only and determined from the LCL type.

LCL Equipment Type Specifies the equipment type in which the LCL cargo is shipped. This value is used to compare with CU equipment type if Fixed Equipment Type is true.

Quantity of Container Specifies the number of containers into which the cargo is to be consolidated.

Note: This field is not mandatory. It must be maintained only in the main LCL booking, which is the booking that is used to consume the equipment using VSF. The sub-LCL booking shares the equipment of main LCL booking.

Fixed Equipment Type Specifies the equipment type as one of the following:

○ Fixed: The cargo is consolidated into the equipment type maintained in the LCL Equipment Type field.

○ Changeable at Consolidation: The cargo can be consolidated into equipment of a different type than indicated in the LCL Equipment Type field if the required equipment is not available.

3. Insert the package items with item type package and maintain the necessary information.

NoteThe system copies the equipment type from the LCL Information tab to the package items.

4. Select the route using VSF.The system transfers the equipment type and container quantity as the required capacity. For the main LCL booking, you can maintain the container quantity. For the sub-LCL booking that does not occupy additional container capacity, leave the container quantity as empty.

5. Save and confirm the LCL booking.

NoteYou may need to resolve blocking issues before being able to confirm the booking.

6. Create the container unit with the specific CU type. Enter following information in the top-level Item tab:


Field What To Enter

Equipment Number Container number of the CU

Equipment Type Equipment type of the CU

Note: This field is mandatory if you want to assign an LCL booking to a CU.

7. Assign the LCL booking to the CU by switching to the Item tab, select the top-level item, and choose Insert FUs for LCL. In the next dialog box, specify the LCL booking number as the search criteria and choose Search.

8. Select the items that you want to assign to the CU and choose OK9. Save the CU.

Results

The system carries out the following processes:

1. Compares the main carriages for all of the FUs

NoteIf the CFS-CFS stages of these FUs are inconsistent, the system raises an error message and stops the assignment.

2. Involves GVF to check whether all LCL bookings are suitable for the CU.

NoteIf CU stage is initial, the system copies CFS-CFS stages of the first FU.

3. Assigns all of the FUs to the TU.4. Copies the equipment number from the CU to the booking items whose FU is assigned to this CU.5. Assigns all of the FUs to the TU.

The system then assigns the CU stages to the manifest based on the vessel and voyage at stages and saves all changes. You can view the relationship in the document flow.

Related Information

Less Than Container Load Bookings [page 225]


Bookings

4.1.23 Discarding Bookings

Discard a canceled booking if it is no longer required or you want to archive it. Only discarded bookings can be archived.

Prerequisites



Transportation Management Forwarding Order Management Define Movement Types .● You have the required authorization to discard bookings.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Display Booking , and then open the relevant booking.

2. In the header toolbar, choose Discard Booking.

Results

After the booking has been successfully discarded, the booking status is changed to Discarded, and you can archive the booking as necessary.

Related Information

Discarding Multiple Bookings [page 230]


4.1.23.1 Discarding Multiple Bookings

Discard multiple canceled bookings if they are no longer required or if you want to archive them. Only discarded bookings can be archived.

Prerequisites



Transportation Management Forwarding Order Management Define Movement Types .● You have the required authorization to discard bookings.

Context

Procedure

1. In SAP NetWeaver Business Client, choose Booking Work List Overview Bookings .2. Select the bookings to be discarded (multiple selection is supported).3. Choose Discard Booking and confirm the dialog box.

NoteThe system checks whether the status of all of the selected booking is Canceled. If any non-canceled bookings are found, then an error message is raised and the action for discarding is stopped for all of the selected bookings.

Results

After the booking has been successfully discarded, the booking status is changed to Discarded, and you can archive the booking as necessary.


Bookings

Related Information

Discarding Bookings [page 229]

4.2 Route Proposal Generation

During the booking process, the route proposals are generated by the Voyage Suggestion Framework (VSF). When you generate the routes for a booking, the VSF is called to check the equipment availability and the allocation availability, and to return the ranked route proposals for future planning purposes.

You trigger the VSF from the booking screen by choosing one of the following options:

● Generate Routes Present Booking SolutionWhen you choose this option, the system displays a dialog box that lists all of the returned route proposals.

● Generate Routes Accept the Best RouteWhen you choose this option, the system accepts the best proposal based on the predefined ranking criteria.

The returned route proposals are categorized as follows:

● Valid proposal with enough space● Valid proposal without enough space● Invalid proposal

Detailed information is displayed for each proposal such as the route details, the allocation details, the check logs, and so on.

Prerequisites

Before generating route proposals, ensure that the following settings have been made:

● The route profile (VSF profile) ID has been configured for a particular booking type in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for Booking Type Define Basic Settings for Booking Document Type .

● The route profile (VSF profile) itself has been configured in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Voyage Suggestion Framework Maintain Profile for Voyage Suggestion Framework .

● Each column of the VSF dialog box has been configured to be visible or invisible based on the different authorization roles in Customizing for SAP Transportation Management under Container Shipping Liners

Order to Cash Booking and Documentation Voyage Suggestion Framework Assign VSF Columns to Role .


Integration

The VSF is integrated with the following other processes within the overall solution:


Ordered Route Determination The ordered route for the booking is determined and used to finalize the routing proposal list.

Routing Solution A Business Add-In (BAdI) is provided within the VSF process. Customers must incorporate their own routing logic.

Allocation Check A BAdI is provided within the VSF process. Customers must incorporate their own allocation check logic.

Equipment Check A BAdI is provided within the VSF process. Customers must either incorporate their own equipment check logic or use the SAP Transportation Resource Planning solution.

Generic Validation Framework The GVF is executed during the booking process to determine whether the booking data conflicts with the predefined restriction and prohibition rules, and also to generate any necessary approval items.

Related Information

Ordered Route Determination [page 234]Integration with Routing [page 232]Integration with Allocation Check [page 233]Validating Routes [page 233]Process After Acceptance of Route Proposals [page 234]

4.2.1 Integration with Routing

You can implement your own specific routing logic within the Voyage Suggestion Framework (VSF). When you generate the routes for a booking, the VSF is triggered to determine the route proposals and then display them in a dialog box. You can then choose the most appropriate route.

The Business Add-In (BAdI) /TMCSL/BADI_VSR_ROUTE_SCH can be used for implementing routing logic. You can create an implementation that implements your own routing logic in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Business Add-Ins (BAdIs) Voyage Suggestion Framework BAdI: Retrieval of Route Proposal .

For more information about this BAdI, see the related Customizing documentation in the system.


Bookings

4.2.2 Integration with Allocation Check

You can implement your own specific allocation check logic within the Voyage Suggestion Framework (VSF). When you generate the routes in a booking, the VSF is triggered. The VSF can in turn trigger the allocation check logic and then display the relevant allocation details along with the route proposals.

The Business Add-In (BAdI) /TMCSL/BADI_ALLO_PROCESS can be used for implementing allocation check logic. You can create an implementation that implements your own allocation check logic in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Business Add-Ins (BAdIs) Booking BAdI: Allocation Process .


4.2.3 Validating Routes

When you generate the routes in a booking, the Voyage Suggestion Framework (VSF) is triggered to generate the route proposals. The VSF uses the Generic Validation Framework (GVF) to validate the route proposals with predefined rules and then categorize them into valid routes or invalid routes.

Prerequisites

● The check logs have been enabled in the route profile (VSF profile) in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Voyage Suggestion Framework Maintain Profile for Voyage Suggestion Framework .

● The consumer for the GVF has been configured in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Generic Validation Framework Define Consumer .

● The rule category for the GVF has been configured in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Generic Validation Framework Define Consumer .

● The settings for the GVF parallelization have been configured in Customizing for SAP Transportation Management under Container Shipping Liners Basic Settings Generic Validation Framework Define Settings for Parallelization .

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and open the relevant booking.

2. In the toolbar, choose Generate Routes Present Booking Solution .

The VSF dialog box is displayed.3. In the VSF dialog box, select one proposal and then choose the Check Logs tab to view the logs related to

the selected proposal.


4.2.4 Process After Acceptance of Route Proposals

You can implement your own specific logic to be executed within the Voyage Suggestion Framework (VSF) after one route proposal is accepted.

The Business Add-In (BAdI) /TMCSL/BADI_ROUTE_ACCEPT can be used for implementing your own special logic to be executed after one route proposal is accepted. You can create an implementation that implements your own logic in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Business Add-Ins (BAdIs) Voyage Suggestion Framework BAdI: Additional Info After Route Proposal Application .


4.3 Ordered Route Determination

Ordered route determination (ORD) is executed right after charge calculation to determine the ordered route:

● Either from the rate table line used for the charge calculation● Or as a dynamic build from the solution builder

Ordered route determination takes places after the Voyage Suggestion Framework is triggered. Once ORD is carried out, the ordered route, together with the trade and brand, are updated to the booking. They can then be used further to determine the actual route list from the routing engine.

Related Information

Standalone Approach [page 234]Accepting Route Proposals [page 235]Automated Route Generation [page 236]

4.3.1 Standalone Approach

In the standalone approach to ordered route determination, the ordered route together with the trade and brand information are determined by the solution builder.

Related Information

Ordered Route Determination [page 234]


Bookings

4.3.2 Accepting Route Proposals

Accept a route proposal to update the ordered route to the booking.

Prerequisites

You have the required authorization to execute the Present Booking Solution function.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Display Booking , and then open the relevant booking.

2. In the header toolbar, choose Present Booking Solution.3. Select any of the ordered routes in the dialog box and choose Pick Route.

Results

The accepted ordered route is updated to the booking ordered route on the Consolidated Trip Plan tab, and the Route Determined Via Solution Builder indicator is selected automatically. The trade and brand on the General booking tab is updated either from the relevant rate table line or determined from the solution builder, and the product ID is brought to the ordered route in the booking.

If the ordered route is not found, the Voyage Suggestion Framework is aborted with the following error message:

● No ordered route found

Meanwhile the route status on the Statuses tab is also set to No Ordered Route Found.

If no rate is found for a tariff case, the following error message is displayed:

● No ocean tariff rate found

Related Information

Ordered Route Determination [page 234]Automated Route Generation [page 236]


4.3.3 Automated Route Generation

Automated route generation triggers the automatic acceptance of the ordered route with the highest ranking. In this case, the user is not prompted to accept an ordered route.

Automated route generation can be activated for specific booking channels in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings Define Booking Channel .

Related Information

Ordered Route Determination [page 234]Accepting Route Proposals [page 235]

4.3.4 Resolving Multiple Rates

Resolve multiple rates when the system finds unresolved multiple rate lines for a booking. In this case, ordered route determination stops and the following message is displayed: Resolve multiple rate hit(s).

Prerequisites

You have executed the Present Booking Solution function.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Display Booking and then open the relevant booking.

2. On the Charge tab, choose Multiple Rate and select one rate.3. Then execute the VSF again.

Results

The ordered route determination runs successfully.


Bookings

Related Information


4.3.5 Skipping of Ordered Route Determination

Skipping of ordered route determination (ORD) can be activated in the Customizing settings for the booking type. The ORD logic is then skipped when the Voyage Suggestion Framework (VSF) is executed, whereby the dialog box for the ordered route is suppressed and a message appears indicating that ORD was skipped for the booking type.

In addition, ordered route determination is skipped if the ordered route has already been determined with the current booking data and has been accepted. In this case, the Ordered Route Determined by Solution Builder indicator is selected on the Consolidated Trip Plan tab of a booking. If the VSF is triggered again with the same booking data, ORD is skipped.

NoteIf any changes to the booking cause the booking status to change from Confirmed to Pending Confirmation, the Ordered Route Determined by Solution Builder indicator is deselected, which means that ORD can be executed again.

Related Information


4.4 Equipment Availability Check

The equipment availability check (EAC) is used to check whether sufficient quantities of an equipment type are available for a booking. It can be triggered either within the Voyage Suggestion Framework (VSF) when booking solutions are generated, or separately by means of a button on the user interface.

When the EAC is executed, the initial depot for the empty container pickup is also determined to establish where to pick up the container. If the container ID is already maintained in the booking item, the initial depot is determined based on the last reported location of this equipment (location where the Gate-in event is reported).


The EAC can return one of the following results:

Case Result Equipment Availability Check Status

If a complete match for the equipment request is found

A success message is displayed and a dialog box is not generated.

Passed

If an alternative proposal is found (not a complete match)

A dialog box is generated with a proposed alternative date, location, or equipment. The alternative proposal is updated to the booking item after one of the proposals is accepted.

Passed

If the equipment availability check fails A dialog box is generated to indicate which equipment type failed for the EAC.

Failed

Before the EAC can be used, the following settings are required:

● The Business Add-In to check equipment availability has been implemented in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Business Add-Ins (BAdIs) Voyage Suggestion Framework BAdI: Retrieval of EAC Equipment Proposals .

● The valid location types for the empty container pickup have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings Define Valid Empty Provisioning Location Type .

● The default location hierarchy ID for EAC has been maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking

Basic Settings Maintain Default Location Hierarchy ID for EAC .

● The ranking of substitution equipment has been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking

Settings for Equipment and Resources Define Substitution Equipment Ranking .● The gate-in events have been defined in Customizing for SAP Transportation Management under

Container Shipping Liners Order to Cash Booking and Documentation Bill of Lading Assign Operational Statuses for Events .

● The default global pickup depot for transportation zones in the location hierarchy has been defined in SAP NetWeaver Business Client under Master Data Logistics Define Default Depot .

Related Information

Route Proposal Generation [page 231]Integration with Transportation Resource Planning [page 239]Initial Depot Determination [page 239]


Bookings

4.4.1 Integration with Transportation Resource Planning

Integration with an installed Transportation Resource Planning (TRP) system enables the equipment availability check (EAC) to connect to TRP to retrieve supply and demand information and check whether the requested equipment in the booking is available. Furthermore, TRP provides the alternative equipment proposal or indicates the detailed information for the limited equipment type.

If the equipment is gated out from the depot, it cannot be captured and planned in TRP. In addition, creation of the repositioning booking can be triggered from the TRP system.

Context

Transportation Resource Planning is a standard product with which you can plan and track the empty equipment to maximize equipment utilization and balance the equipment between the depots by leveraging the demand and supply in the depot.

Related Information

Equipment Availability Check [page 237]Initial Depot Determination [page 239]

4.4.2 Initial Depot Determination

Initial depot determination is triggered when the equipment availability check (EAC) is executed. It determines the initial depot for the empty container pickup to establish where the container is to be picked up.

The initial depot is mandatory information when the empty provisioning transportation unit is planned through the Transportation Resource Planning (TRP) system.

Before initial depot determination can take place, the following settings are required:

● The allowed location types for the empty pickup location have been maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings Define Valid Empty Provisioning Location Type .

● The global pickup location for the transportation zone and equipment type has been maintained in SAP NetWeaver Business Client under Master Data Logistics Maintain Default Depot .

● The Business Add-In to determine empty provisioning and empty return depots has been implemented in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBusiness Add-Ins (BAdIs) Booking BAdI: Empty Provisioning and Empty Return Depot Determination .

If a preferred city for depot provisioning or for depot return is maintained in the booking, the depot determination logic first tries to validate the location type for the preferred city based on the Customizing


settings. If there is no match, the BAdI mentioned above is used to determine the default pickup depot for the transportation zone of the source location.

NoteTRP cannot plan the empty provisioning transportation unit without the initial depot.

Related Information

Equipment Availability Check [page 237]Depot Determination for Given Container Number [page 240]

4.4.3 Depot Determination for Given Container Number

Depot determination for a given container number is a scenario in which the booking agent knows which containers are available for a booking and enters the container number directly in the booking. An empty pickup depot is then determined based on the current location of the container and the equipment availability check (EAC) is skipped for this container.

When a container number is maintained in the booking, the last event recorded for the resource is determined in the Empty Pickup Location field on the Empty Provisioning tab if the event is defined as Gate-in in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Bill of Lading Assign Operational Statuses for Events . If the current location is not gated, an error message is shown indicating that this container cannot be reused.

NoteAfter a release order has been created, the source location is not updated if the container number is updated. The stop fixing status is set to Fixed in the empty provisioning transportation unit to exclude the container from replanning in Transportation Resource Planning. The equipment availability check is then skipped if the container number is entered in the booking.

Related Information



Bookings

4.4.4 Alternative Equipment Proposals

Alternative equipment proposals are returned if the equipment availability check (AEC) does not find a complete match.

The following alternative equipment proposals can be returned:

Alternative Equipment Proposal Description

Alternative pickup time An equipment proposal with an alternative pickup time is returned. The proposal can be up to a certain time frame in days from the requested date based on the EAC-relevant time defined in Customizing (for skipping the EAC for early bookings).

Alternative pickup location An equipment proposal with an alternative pickup is returned.

The request type for the alternative location is determined as follows:

● City: The location used as the requested provisioning location can provision a specific depot (for example, CNSHA_DEP1).

● Virtual alternative location: The location used as the requested provisioning location (for example, city CNSHA) cannot provision the equipment (the location is checked against the valid location types defined in Customizing). The city is then determined based on the location hierarchy maintained in transaction /SAPAPO/RELHSHOW.

Equipment Substitution An equipment proposal with alternative equipment is returned. The equipment substitution allowed is defined in Customizing and the alternative proposal can be determined based on this information.

Related Information

Accepting Alternative Equipment Proposals [page 242]Equipment Availability Check [page 237]


4.4.4.1 Accepting Alternative Equipment Proposals

Accept alternative equipment proposals if the equipment availability check (EAC) does not find a complete match for the originally requested equipment and returns possible alternatives.

Prerequisites

The EAC has been run and has returned alternative equipment proposals.

Procedure

1. In the EAC window that opens after the EAC is run, select the proposals you want to accept:○ All proposals○ Alternative date proposal○ Alternative depot proposal○ Equipment substitution proposal

2. Choose the required option:

Option What To Do

To accept the proposal and update the booking item Choose Accept.

To refuse the proposal, abort the VSF process, and set the Equipment Availability Status in the booking to Proposal Refused

Choose Refuse Proposal.

To close the window and abort the VSF process without a status change

Choose Close.

Results

If you have accepted one of the alternative proposals, it is updated in the booking item.

Related Information

Equipment Availability Check [page 237]


Bookings

4.4.5 Running the Equipment Availability Check Manually

Run the equipment availability check (EAC) manually in cases when you want to run the EAC without calling the Voyage Suggestion Framework (VSF).

Prerequisites

The booking has not yet been confirmed.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Edit Booking , and then open the relevant booking.

2. On the Empty Provisioning tab under the item, enter the pickup date for the empty container.3. In the header toolbar, choose Check Equipment Availability.

Results

The initial depot is determined at the pickup location for the empty provisioning container, and the equipment proposal screen is displayed with detailed information of the proposed empty container pickup.

NoteAfter the booking has been confirmed, the EAC can no longer be run manually. This ensures that the initial source locations in the booking are not reset by the initial depot determination functionality.

Related Information


4.4.6 Equipment Availability Check for Early Bookings

The equipment availability check is skipped for early bookings that are placed much in advance of the requested pickup date. In this case, the EAC is skipped for the entire booking and the equipment status on the Status tab is set to Not Required. In this booking, the required containers are always allocated no matter how


many are available. If only some of the booking items qualify as an early booking, only these items are skipped during the EAC.

The global time period for early bookings, which is used to determine if the EAC is to be skipped, can be maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings Maintain Global Time Period for EAC .

Related Information


4.5 Part-Load Bookings

In part-load shipments, multiple bills of lading (B/Ls) share multiple containers.

The system treats part-load shipments by means of a full container load (FCL) equipment booking and several less than container load (LCL) part-load bookings. FCL rates and other charge types calculated on the equipment booking can be prorated to the part-load bookings, for example, by cargo weight or volume.

A part-load shipment comprises the following parts:

● Equipment bookingThe freight forwarder sets up a part-load booking by first creating an FCL booking, which is called the equipment booking. The equipment booking includes several containers. Each of these containers is shared by different shippers and has more than one B/L. The freight forwarder also does the consolidation and stuffing for the booking. You can add or delete containers, and change container information in the equipment booking, but you cannot add or delete packages, or change package information.

● Part-load bookingsThe part-load bookings are created from shipping instructions sent by the booking parties and contain only the packages for the booking. You can add or delete packages, or change package information in the part-load booking, but you cannot add or delete containers, or change container information.

The part-load booking scenario is a mixture of an LCL shipment and buyer’s consolidation.

The system performs consistency checks to ensure that the information in the equipment booking matches the information in the related part-load bookings.

On the Related Documents tab of the respective bookings, you can view the relationship between the part-load bookings and the equipment booking. The following table lists the tasks you can perform on the Related Documents tab of each booking:


Bookings

Related Documents Tab Tasks

Related Documents tab in the part-load booking ● View the related equipment booking● View other part-load bookings related to the same

equipment booking

Related Documents tab in the equipment booking ● Link a part-load booking to the equipment booking● View all part-load bookings linked to the equipment

booking

Related Information

Creating Part-Load Bookings [page 245]Creating Part-Load Bookings Automatically [page 246]Charge Type Levels for Part-Load Bookings [page 259]Consistency Checks for Part-Load Bookings [page 250]

4.5.1 Creating Part-Load Bookings

Create a part-load booking by creating an equipment booking and a part-load booking and then linking the two bookings.

Prerequisites

The shipping types for part-load bookings and equipment bookings have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation

Booking Settings for Booking Type Define Shipping Types for Equipment BKG or Part-Load BKG .

Procedure

1. Create a part-load booking as follows:

a. In SAP NetWeaver Business Client, choose Booking Booking Create Booking .b. Create a new booking with a part-load booking type.c. On the General Data tab, specify a shipping type for part-load bookings.d. In the Items table, add package items and specify the container number for each package.e. Save the part-load booking.

2. Create an equipment booking as follows:


a. In SAP NetWeaver Business Client, choose Booking Booking Create Booking .b. Create a new booking with an equipment booking type.c. On the General Data tab, specify the shipping type for equipment bookings.

d. On the Related Documents tab, choose Add Part-Load Booking .e. In the dialog box that opens, search for and select the related part-load booking.f. Choose OK to confirm.g. Repeat steps d-f for each related part-load booking.h. On the General Data tab, add containers to the Items table and specify the container number for each

container.i. Save the booking.

Results

The equipment booking and part-load bookings are created and linked. You can view the relationship between the bookings on the Related Documents tab of the respective booking.

Related Information

Part-Load Bookings [page 244]Creating Part-Load Bookings Automatically [page 246]

4.5.2 Creating Part-Load Bookings Automatically

Create part-load bookings from shipping instructions (SIs) on the Shipping Instructions tab of the equipment booking.

Prerequisites

● The forwarding order type for part-load bookings has been defined in Customizing for SAP Transportation Management under Forwarding Order Management Forwarding Order Define Forwarding Order Types .

● The package item type has been assigned to the forwarding order type for part-load bookings in Customizing for SAP Transportation Management under Transportation Management Forwarding Order Management Forwarding Order Assign Item Types to Forwarding Order Types .

● A shipping type has been defined for part-load and equipment bookings in Customizing for SAP Transportation Management under Transportation Management Forwarding Order ManagementDefine Shipping Types . The Item Assignment for the equipment booking shipping type has been set to All


Bookings

Cargo Items Must Be Assigned to Equipm. Item or Resource, and the Item Assignment for the part-load booking shipping type has been set to Cargo Items Must Not Be Assigned to Equipm. Item or Resource.

● A new booking subtype has been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for

Booking Type Define Booking Categories and Types .● A new basic booking document type has been assigned to part-load bookings in Customizing for SAP

Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for Booking Type Define Basic Settings for Booking Document Type . The part-load booking type has been specified in the Type (Part Load Booking Type) and Shpg Type (Shipping Type of Equipment Booking) fields for the equipment booking document type.

● The relevant shipping type has been specified for equipment bookings and part-load bookings in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Settings for Booking Type Define Shipping Types for Equipment BKG or Part-Load BKG .

● The part-load shipping type has been specified for the part-load document type and receipt mode in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Settings for Booking Type Determine Shipping Types .

Context

Part-load bookings are created from SIs received from the customer. The SIs that the customer submits contain a reference to the original equipment booking. The system creates additional part-load bookings that are linked to the equipment booking based on the part-load SIs sent by the customer.

Procedure


2. Go to the Shipping Instructions tab.3. Select one or more SIs and choose Create Part-Load Booking.

The system checks the following:

○ The booking includes only container cargo items (no packages, no break bulk, or no roll-on roll-off (RORO) cargo).

○ A bill of lading (B/L) has not been issued for the booking.○ Forwarding settlement documents have not been created for the booking.

If any of the checks fail, the system does not create the part-load booking and displays an error message.


Results

If only one SI item is selected, the system creates the part-load booking as follows:

● The SI is reassigned to a new part-load booking.● The original booking shipping type is assigned to the default equipment booking shipping type.● A document flow is created between the part-load booking and the equipment booking.● The part-load booking is added on the Related Documents tab of the equipment booking.

If more than one SI is selected, the system creates the part-load booking in the background as follows:

● The SI is reassigned to a new part-load booking.● The original booking shipping type is assigned to the default equipment booking shipping type after one of

the part-load bookings is created.● The document flow is created between the part-load booking and the equipment booking.● The part-load booking is added on the Related Documents tab of the equipment booking.● After the part-load bookings are created, you can see the header data and the business partner details of

original booking on the part-load booking screen.

NoteYou can check the log for the part-load booking creation in the Application Log (transaction SLG1) by specifying the object /TMCSL/PARTLOAD and the subobject /TMCSL/PARTLOAD_CRT.

Related Information

Part-Load Shipping Instructions [page 269]Processing Part-Load Shipping Instructions [page 270]

4.5.3 Deleting Part-Load Bookings from Equipment Bookings

Delete part-load bookings from an equipment booking on the Related Documents tab of the equipment booking.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and open the relevant equipment booking.

2. On the Related Documents tab, select the relevant part-load booking.3. Choose Delete.4. Save the booking.


Bookings

Related Information

Part-Load Booking Cancellation [page 249]Canceling Part-Load Bookings [page 249]

4.5.4 Part-Load Booking Cancellation

A complete part-load shipment, which includes the part-load booking and the equipment booking, is canceled by first canceling all part-load bookings and then canceling the equipment booking.

When you cancel an equipment booking, the system checks if all related part-load bookings have a Canceled status. If any related part-load bookings do not have a Canceled status, the system displays an error message and does not cancel the booking. When you cancel a part-load booking, it is not automatically removed from the list of related documents in the equipment booking. If required, you can manually delete a canceled part-load booking on the Related Documents tab in the equipment booking. When you cancel a part-load booking, all of the assigned freight units in the part-load packages are also canceled. The canceled freight units are unassigned from the equipment booking containers, and the part-load package information is removed from the equipment booking. If you want to undo a cancellation of a part-load booking, you must first reactivate the part-load booking, and then reactivate the equipment booking.

Related Information

Canceling Bookings [page 201]Reactivating Canceled Bookings [page 203]Canceling Part-Load Bookings [page 249]Deleting Part-Load Bookings from Equipment Bookings [page 248]

4.5.4.1 Canceling Part-Load Bookings

Cancel a complete part-load shipment by first canceling all part-load bookings in the shipment and then canceling the equipment booking.

Procedure

1. Cancel a part-load booking as follows:

a. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and open the relevant part-load booking.

b. In the toolbar, choose Cancel Booking.


c. In the dialog box that opens, specify the appropriate reason code and optionally enter any explanatory remarks.

d. Confirm the dialog box.e. Repeat steps a-d for each part-load booking in the shipment.

2. Cancel the related equipment booking as follows:

a. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and open the relevant equipment booking.

b. In the toolbar, choose Cancel Booking.c. In the dialog box that opens, specify the appropriate reason code and optionally enter any explanatory

remarks.d. Confirm the dialog box.

Related Information

Booking Cancellation [page 200]Canceling Bookings [page 201]Reactivating Canceled Bookings [page 203]Part-Load Booking Cancellation [page 249]

4.5.5 Consistency Checks for Part-Load Bookings

The system performs consistency checks on part-load bookings to ensure that the information in the equipment booking matches the information in the related part-load bookings.

The system performs the part-load consistency checks after each of the following scenarios:

● A part-load package is assigned or unassigned to a container in an equipment booking.● A part-load booking is added or deleted on the Related Documents tab of an equipment booking.● An equipment booking is split.● A part-load booking is split.

A part-load bill of lading can only be released if the Part Load Consistency Status is Consistent. If the status is not Consistent, the system does not release the bill of lading and displays an error message.


Bookings

Part-Load Booking Consistency Checks

You can view the status of the consistency checks for the part-load booking in the Statuses tab on the Bill of Lading screen for the part-load booking. The Part Load Consistency Status field displays one of the following statuses:

Status Meaning

Consistent All packages in the part-load bill of lading (B/L) are assigned to a container in the equipment booking.

Not Consistent At least one package in the part-load booking is not assigned to a container in the equipment booking.

Not Applicable The booking is not a part-load booking.

Equipment Booking Consistency Checks

You can view the status of the consistency checks for the equipment booking in the Part Load Execution tab on the Booking screen of the equipment booking. The Part Load Consistency Status field displays one of the following statuses:

Status Meaning

Consistent Each container in the equipment booking has at least one part-load package assigned and the consistency status of all related part-load bookings is Consistent.

Not Consistent One or both of the following scenarios are true:

● At least one container of the equipment booking has no assigned part-load packages.

● At least one related part-load booking has a Not Consistent status.

NoteThe Part Load Execution tab is only displayed for equipment bookings; it's invisible for other booking types.

Related Information

Split Part-Load Bookings [page 254]Deleting Part-Load Bookings from Equipment Bookings [page 248]Creating Part-Load Bookings [page 245]


4.5.6 Ordered and Actual Route Synchronization

The ordered and actual routes are synchronized between equipment bookings and related part-load bookings. Any changes in the actual and ordered routes in the equipment booking are copied to the ordered and actual routes in the related part-load bookings.

Ordered Route Synchronization

When you link a part-load booking to an equipment booking on the Related Documents tab, the synchronization process between the ordered route in the equipment booking and the part-load booking is enabled. The system overwrites the ordered route in the part-load booking with the ordered route in the equipment booking.

Actual Route Synchronization

When you assign items in a part-load booking to items in an equipment booking, the synchronization process between the actual route in the equipment booking’s container unit and the part-load booking’s freight unit is enabled. If you change the actual route in the equipment booking, the system overwrites the actual route of the freight unit in the part-load booking with the actual route of the equipment booking.

Related Information

Creating Part-Load Bookings [page 245]

4.5.7 Part-Load and Equipment Bookings Synchronization

When package information is changed in the part-load booking, the system updates the package information in the equipment booking.

General cargo and package information is entered in the equipment booking and detailed package information is entered in the related part-load bookings. However, certain processes that are performed on the equipment booking, for example, charge calculation and prorating of charges, need detailed package information. To allow the system to perform these processes, package information in the related part-load bookings is replicated to the equipment booking. When the package information in the part-load booking changes, the system automatically updates the package information in the equipment booking.


Bookings

Changes in the Part-Load Booking

When you assign a container number to a package in a part-load booking, the system replicates the package information to the corresponding container in the equipment booking. You can add or delete a package, or change package information in the part-load booking.

Changes in the Equipment Booking

When you change a container number in an equipment booking, the package information for the new container is synchronized with the part-load booking.

In the equipment booking, you can add or delete a container, or change container information, but you cannot add, change, or delete packages that are related to part-load booking. The packages in the part-load booking are read-only in the equipment booking.

When you copy an equipment booking or copy an individual container in the equipment booking, the package items are not copied, as they are not yet related to a part-load booking.

Related Information

Creating Part-Load Bookings [page 245]

4.5.8 Part-Load Numbering Logic

A special numbering logic, which creates part-load booking numbers based on the related equipment booking number, can be implemented for part-load bookings.

The Business Add-In (BAdI) /TMCSL/BADI_TRQ_NR_RANGE is provided within the booking process. This BAdI is called during the booking creation process to generate booking numbers. As this BAdI is also called when a part-load booking is created from an equipment booking, you can create an implementation of this BAdI to specify a numbering logic for part-load booking numbers. For more information about this BAdI, see the related Customizing documentation in the system.

ExampleYou could implement the BAdI /TMCSL/BADI_TRQ_NR_RANGE so that part-load booking numbers are a combination of the booking number plus and a two digit number that is incremented for each subsequent part-load booking (that is, part-load booking number = equipment booking number + 01, 02, 03, and so on). You then create a part-load equipment booking, and the system assigns the booking number 123456789 to the booking. Any part-load bookings that you create on the Shipping Instruction tab of the equipment booking would be numbered as follows: 12345678901, 12345678902, 12345678903, and so on.


Related Information

Creating Part-Load Bookings Automatically [page 246]

4.5.9 Split Part-Load Bookings

The equipment booking and related part-load bookings for a part-load shipment can be split into new or existing bookings.

Equipment Booking Split

In the part-load scenario, the containers are added to the equipment booking and the packages are added to the related part-load bookings. The containers in the equipment booking are empty. You can split the empty containers to new or existing equipment bookings. However, since the empty containers have no packages attached to them, no part-load booking information is added to the new split equipment booking.

Part-Load Booking Split

In the part-load scenario, the packages are saved in the part-load booking, and you can split packages into a new or an existing part-load booking. If you split packages into a new part-load booking, the new part-load booking is automatically linked to the same equipment booking as the original part-load booking.

If you split packages into an existing part-load booking, the existing part-load booking must be linked to the same equipment booking as the part-load booking that you are splitting. If the equipment booking is not the same for both part-load bookings, the system does not perform the split.

Related Information

Split Bookings [page 190]Splitting Bookings [page 191]

4.5.10 Short Shipments in Part-Load Bookings

Memo bills of lading (B/Ls) can be created for any short shipments in the part-load booking.

When you mark a container in a part-load equipment booking as short shipped, the system creates a memo B/L for the equipment booking and any related part-load bookings.


Bookings

The following figures depict the the model of the short shipment process for a short-shipped part-load container.

The following figure shows an equipment booking with two containers. Each container is linked to a package in a part-load booking.

Equipment and Part-Load Bookings Before Short Shipment

The following figure shows a model of the equipment booking and the part-load B/Ls after a short shipment.

Equipment Booking and Part-Load B/Ls After Short Shipment


The following figure shows the equipment and part-load booking memo B/Ls after short shipment.

Memo Equipment Booking and Part-Load Memo B/Ls After Short Shipment

Related Information

Creating Memo Bills of Lading for Short Shipments [page 256]Short Shipments [page 316]Handling Short Shipments [page 318]

4.5.10.1 Creating Memo Bills of Lading for Short Shipments

Create memo bills of lading (B/Ls) for part-load shipments that are short-shipped.

Prerequisites

● A memo part-load booking type has been defined in Customizing for SAP Transportation Management under Transportation Management Forwarding Order Management Forwarding Order Define Forwarding Order Types . The Enable Change Calculationcheckbox has been deselected for this memo part-load booking type.

● The item type PKG has been assigned to the relevant forwarding order type in Customizing for SAP Transportation Management under Transportation Management Forwarding Order ManagementForwarding Order Assign Item Types to Forwarding Order Types .

● A basic booking document type has been defined for memo part-load bookings in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and


Bookings

Documentation Booking Settings for Booking Type Define Basic Settings for Booking Document Type . For this new memo part-load booking type, the Memo B/L checkbox has been selected, the part-load booking type has been specified in the Booking Subtype field, and the part-load booking type has been specified in the Type Memo field.

● A user interface profile has been configured for memo part-load bookings in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Profile Settings Maintain Booking UI Profile . The Confirm, Calculation Charge, Reactive/Cancel, and Generate Route actions have been disabled for memo part-load bookings.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Change Booking , and then open the relevant equipment booking.

2. Go to the Short Shipment tab.3. Specify a reason code for the short shipment.4. Select a container and choose Short Shipment.

The system creates the memo B/Ls as follows:

○ If there is only one part-load package assigned to the selected container, the system creates one equipment memo booking and one memo part-load B/L.

○ If there are several part-load packages assigned to selected container, the system creates in the background one equipment memo booking and a memo part-load B/L for each part-load package.

NoteYou can check the log for the part-load booking creation in the Application Log (transaction SLG1) by specifying the object /TMCSL/PARTLOAD and the subobject /TMCSL/PARTLOAD_CRT.

Results

● The destination location on the memo B/L is filled-in from the location in the part-load B/L.● The Short Shipped checkbox is selected for the container in the equipment booking.● On the Document Flow tab of the original equipment booking, you can view and link to the memo B/L.● On the Document Flow tab of the memo equipment booking, you can view and link to the memo part-load

B/L and the original equipment booking.

Related Information

Short Shipments [page 316]Handling Short Shipments [page 318]


Short Shipments in Part-Load Bookings [page 254]

4.5.11 Disabling of Route Selection and Status Checks

Route selection, allocation checks, and equipment status checks can be disabled for part-load bookings. Disabling these checks ensures that route selection is performed only on the equipment booking of a part-load shipment.

You can configure part-load shipments so that you can only perform route selection on the equipment booking. The system then propagates the selected route to the related part-load bookings.

Route selection and the allocation and equipment check functionality can be disabled for part-load bookings in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Settings for Booking Type Define Basic Settings for Booking Document Type . Route selection is disabled by specifying Not Relevant in the Equipment Status and Allocation Check fields for the part-load document type.

If you disable route selection for part-load bookings you can view the following changes on the Booking screen:

● The Generate Routes button on the Booking screen is disabled.● On the Statuses tab, the Equipment Status and the Allocation Status fields display Not Checked.

Related Information

Route Proposal Generation [page 231]Validating Routes [page 233]

4.5.12 Inland Bookings for Part-Load Shipments

In the part-load scenario, inland bookings can only be created for the containers in the equipment booking. An inland booking cannot be created from a part-load booking.

You can create multiple inland bookings from an equipment booking and each inland booking may include one or more containers. You create the inland booking for an equipment booking in the same way as you create an inland booking for an international booking.

Related Information

Inland Bookings [page 223]Creating Inland Bookings [page 224]


Bookings

4.5.13 Prohibition of Bill of Lading Creation

A bill of lading (B/L) cannot be created from an equipment booking.

When you try to create a B/L from an existing booking, the system checks the shipping type of the booking. If the shipping type is for an equipment booking, the system does not create the B/L and displays an error message.

Related Information

Creating B/Ls from Bookings [page 275]

4.5.14 Charge Type Levels for Part-Load Bookings

In the part-load scenario, some charge types have to be calculated and invoiced on the equipment booking and some charge types have to be calculated and invoiced on the part-load bookings.

In the part-load scenario, charges are usually calculated on the equipment booking, and are prorated to the linked part-load bookings for invoicing. However, certain charge types have to be calculated and invoiced on the part-load bookings (for example, documentation fees).

For each charge type, you can define whether the calculation level or invoice level is on the equipment booking or part-load booking. The charge type level can be defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Basic Settings Define Charge Type Attributes for Order to Cash .

The following combinations are possible for charge type levels:

Calculation Level Invoice Level

Equipment Booking Equipment Booking

Equipment Booking Part-Load Booking

Part-Load Booking Part-Load Booking

Related Information

Charge Type Checks When Converting FCL Bookings [page 260]


4.5.15 Charge Type Checks When Converting FCL Bookings

A full container load (FCL) booking that has a charge item with an Invoiced status cannot be converted to an equipment booking if the charge type calculation level or invoice level is Part-Load Booking.

In certain circumstances in the part-load scenario, you may need to calculate the charges on an FCL booking and then convert the booking to an equipment booking. If a charge item in the FCL has an Invoiced status, you can only convert the FCL booking to an equipment booking if the charge type for both the calculation level and invoice level is Equipment Booking. If the charge type for the calculation level is Part-Load Booking or the invoice level is Part-Load Booking and the charge item is Invoiced, the system will not change the FCL booking to an equipment booking.

ExampleSay you create an FCL booking and calculate the charges. If you change the FCL booking type to an equipment booking type, the system checks the calculation level, invoice level, and the invoice status. If the either the calculation level or the invoice level is not Equipment Booking and charge item has an Invoiced status, the system displays an error message and does not convert the booking.

The charge type level is defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Basic Settings Define Charge Type Attributes for Order to Cash .

Related Information

Invoice Status [page 388]Changes to Invoice Status [page 388]Charge Type Levels for Part-Load Bookings [page 259]


Bookings

5 Documentation

Documentation in SAP Transportation Management, order to cash for container shipping liners refers to documents containing the key information and data required for completion of shipping operations and covers the processes of export documentation, manifesting, and import documentation.

The documents are exchanged, for example, between customers and carriers, carriers and shippers, or carriers and authorities, as part of the order-to-cash process. In the system, the documents are essential for completion of the shipping process and contain all of the data required by the system.

The most important documents used for container shipping liners are listed below:

● Shipping instructions● Bills of lading● Manifests● Delivery orders

Related Information

Shipping Instructions [page 261]Bills of Lading [page 273]Manifest [page 330]Delivery Orders [page 349]

5.1 Shipping Instructions

A shipping instruction (SI) is a document, provided by a customer to the carrier, containing details of the cargo to be shipped and the requirements for its physical transportation.

The SI contains basic information that is required to draw up the bill of lading (B/L), such as:

● Booking number or B/L number● B/L parties including shipper, consignee, and notify party● Vessel or voyage or both● Place of receipt● Port of loading● Port of discharge● Final destination● Container number● Seal number● Shipping mark

SAP Transportation Management, Order to Cash for Container Shipping LinersDocumentation P U B L I C 261

● Cargo description● Quantity● Weight and measurement● B/L type● Service agreement● Payment terms (prepaid or collect)● House bill of lading (HBL) number and information

The shipping instruction is always indexed to a booking or a bill of lading. Once indexed, the shipping instruction is available in SAP Transportation Management (SAP TM) for processing. Once a shipping instruction has been processed, a bill of lading is created from a booking. The shipping instruction is always indexed to a booking or a bill of lading. Once indexed, the shipping instruction is available in SAP Transportation Management (SAP TM) for processing. Once a shipping instruction has been processed, a bill of lading is created from a booking.

Related Information

Processing Shipping Instructions [page 263]

5.1.1 Datatized Shipping Instructions

Datatized shipping instructions are the shipping instructions received in SAP Transportation Management (SAP TM) in any standard communication format used for transmitting business information electronically. For example, by means such as EDI or XML.

The data provided in the datatized shipping instruction is parsed into the corresponding attributes of the shipping instruction in SAP TM.

Related Information

Non-Datatized Shipping Instructions [page 262]

5.1.2 Non-Datatized Shipping Instructions

Non-datatized shipping instructions are the ones received not by means of any standard communication format used for transmitting business information electronically between the systems (for example, by means such as EDI or XML). Non-datatized shipping instructions can exist as e-mails, e-mail attachments, fax messages, scans, and so on.

It’s not possible to parse data from non-datatized shipping instructions to SAP Transportation Management (SAP TM) automatically. However, non-datatized shipping instructions can also be indexed to a booking or bill


Documentation

of lading in SAP TM. The object of a non-datatized shipping instruction contains only the link to the file with the information specified by the exporter.

Related Information

Datatized Shipping Instructions [page 262]

5.1.3 Shipping Instruction Types

The shipping instruction type is determined by the SAP Transportation Management (SAP TM) system.

The following types exist:

Type Description

New First shipping instruction indexed to a booking or bill of lading

Amendment Second, third, or further shipping instructions indexed to a booking or bill of lading

Duplicate Shipping instructions having exactly the same date as any of the previous shipping instructions indexed to the same bill of lading

Related Information

Shipping Instruction Classes [page 265]Processing Shipping Instructions [page 263]

5.1.4 Processing Shipping Instructions

Once shipping instructions are available in the SAP Transportation Management (SAP TM) system, they need to be processed.

Context

You can do this either from a shipping instruction worklist, a booking application, or a bill of lading application. It involves copying information from the shipping instruction to the booking or bill of lading. If the shipping


instruction is datatized, the data is copied in an automated process, but if the shipping instruction is non-datatized, you have to copy the data manually.

Procedure

1. In SAP NetWeaver Business Client, go to the bill of lading or booking and choose the Shipping Instructions tab, or alternatively, open the SI by way of the shipping instruction worklist.

2. Select the relevant shipping instruction and choose Process.

The system opens a simplified view of the bill of lading document used for creating or amending the bill of lading based on the shipping instruction. The shipping instruction itself opens in a separate window. Depending on the shipping instruction datatization, the result is as follows:

SI Datatization Result

Datatized SI The attributes that are not specified (blank) in the booking or bill of lading are copied automatically from the corresponding attributes in the shipping instruction. For all other attributes, you can perform one of the following options:

○ To copy the value of the individual attribute from the shipping instruction to the bill of lading, choose C next to the attribute.

○ To copy all attributes from the shipping instruction, choose Copy all from SI.

Non-datatized SI No attributes are automatically copied to the bill of lading from the non-datatized shipping instruction. You have to enter the data manually by referring to the non-datatized shipping instruction, which is opened in parallel.

3. When you have finished processing the shipping instruction, choose Save and Submit and confirm the dialog box that appears.

NoteThe procedure for normal shipping instructions is described here. For information about processing other shipping instruction classes (such as split, merge, and so on), see the related links below.

Related Information

Datatized Shipping Instructions [page 262]Non-Datatized Shipping Instructions [page 262]Split Shipping Instructions [page 265]Merge Shipping Instructions [page 267]


Documentation

House Bill of Lading Shipping Instructions [page 268]Part-Load Shipping Instructions [page 269]

5.1.5 Shipping Instruction Classes

Besides normal shipping instructions (SIs), there are four other classes of shipping instructions. The class reflects the requirements of the shipper, and the procedure for processing the shipping instruction differs based on the respective class.

The class can be provided by the shipper or can be specified by the carrier when the shipping instruction is received. It is the only SI attribute that can be changed by the carrier. An overview of the classes is provided below:

Class Description

Split (SPT) The shipper wants a few items from the original bill of lading to be moved to a new or different bill of lading.

Merge (CON) The shipper wants to merge two bills of lading into one.

House Bill of Lading (HBL) The shipper wants a house bill of lading to be created for the original bill of lading.

Part Load (PAL) The shipper wants a part-load booking to be created for an equipment booking in the case of a part-load scenario.

Related Information

Split Shipping Instructions [page 265]Merge Shipping Instructions [page 267]House Bill of Lading Shipping Instructions [page 268]Part-Load Shipping Instructions [page 269]

5.1.5.1 Split Shipping Instructions

Split shipping instructions are used when the shipper wants to move part of the items from the original bill of lading into a new or different bill of lading. The split shipping instruction (class SPT) contains the items to be split from the original bill of lading.

In cases where the items are to be moved to an existing bill of lading, class SPT also contains the ID of the original bill of lading.


Related Information

Processing Split Shipping Instructions [page 266]

5.1.5.1.1 Processing Split Shipping Instructions

When the shipper provides split shipping instructions (SIs), split the relevant items to a new or different bill of lading (B/L).

Procedure


2. Select the split shipping instruction and choose Process.

The system displays two windows: one showing the split shipping instructions and one containing the bill of lading application on the Split tab.

3. Then proceed as follows:

Scenario Procedure

If the split SI is datatized The items are moved automatically from the original B/L to the split B/L.

If the split SI is non-datatized Move the items manually by copying the data from the window containing the split SI to the window displaying the B/L on the Split tab.

4. Confirm the split operation by choosing Save and Submit.

Results

The relevant items are moved to the new or different bill of lading.

Related Information

Split Shipping Instructions [page 265]


Documentation

5.1.5.2 Merge Shipping Instructions

The shipper may request in the shipping instruction (SI) that two bills of lading are to be merged into one. This is known as a merge shipping instruction and has SI class CON.

The merge shipping instruction contains the number of the bill of lading number to be merged into the master bill of lading to which the shipping instruction is indexed.

Related Information

Processing Merge Shipping Instructions [page 267]

5.1.5.2.1 Processing Merge Shipping Instructions

When the shipper provides merge shipping instructions, merge the relevant bills of lading into one.

Procedure


2. Select the merge shipping instruction and choose Process.3. The bill of lading is opened in production mode with items moved from the to be merged bill of lading to

the master bill of lading.4. Confirm the merge operation by choosing Save and Submit.

Results

The relevant bill of lading is merged into the master bill of lading.

Related Information

Merge Shipping Instructions [page 267]


5.1.5.3 House Bill of Lading Shipping Instructions

Shipping instructions (SIs) for house bill of lading are indexed to the original bill of lading and are used when the shipper wants a house bill of lading to be created for the original.

A shipping instruction for a house bill of lading has SI class HBL. The information provided in this shipping instruction is limited to house bill of lading number, parties, and item details.

Related Information

Processing House B/L Shipping Instructions [page 268]

5.1.5.3.1 Processing House B/L Shipping Instructions

As soon as house bill of lading (HBL) shipping instructions have been indexed to the original bill of lading, process them to create a house bill of lading for the original bill of lading.

Prerequisites

The original bill of lading must have HBL type Manual and the HBL assignment level must be specified.

Procedure

1. In SAP NetWeaver Business Client, open the original bill of lading in edit mode and choose the Shipping Instructions tab.

2. Select the shipping instruction for house bill of lading and choose Process.

The House Bill of Lading tab opens in the bill of lading application and shows the new house bill of lading created with all the information provided in the processed shipping instruction. The shipping instruction itself opens in a separate window.

3. Then proceed as follows:

Scenario Procedure

If the HBL SI is datatized The information is copied to the HBL automatically.

If the HBL SI is non-datatized Copy the information manually.

4. Double-check the correctness of the copied data.


Documentation

5. Finish by choosing Save and Submit.

Results

The new house bill of lading is created with the data from the HBL shipping instructions.

Related Information

House Bill of Lading Shipping Instructions [page 268]

5.1.5.4 Part-Load Shipping Instructions

Part-load shipping instructions (SIs) are used to create a part-load booking for an equipment booking in the case of a part-load scenario. They are first indexed to the equipment booking. You can then create a part-load booking for this equipment booking using the part-load shipping instruction.

When the part-load booking is created, the shipping instruction is automatically reassigned to it from the equipment booking. You can then process the part-load shipping instruction to create a part-load bill of lading. A part-load shipping instruction has SI class PAL.

NoteA part-load shipping instruction is processed in the same way as a normal shipping instruction

Related Information

Processing Part-Load Shipping Instructions [page 270]Creating Part-Load Bookings Automatically [page 246]


5.1.5.4.1 Processing Part-Load Shipping Instructions

Process part-load shipping instructions (SIs) to create a part-load bill of lading (B/L) from a part-load booking.

Procedure

1. In SAP NetWeaver Business Client, open the part-load booking and choose the Shipping Instructions tab.2. Select the part-load shipping instruction and choose Process.

Two windows open: one showing the part-load shipping instruction and one showing the part-load B/L.3. Then proceed as follows:

Scenario Procedure

If the part-load SI is datatized The information is copied automatically from the part-load SI to the part-load B/L.

If the part-load SI is non-datatized Copy the information manually from the window showing the part-load SI to the window showing the part-load B/L.

4. Confirm by choosing Save and Submit.

Results

The part-load B/L is created.

Related Information

Part-Load Shipping Instructions [page 269]Creating Part-Load Bookings Automatically [page 246]

5.1.6 Shipping Instruction Worklist

The shipping instruction (SI) worklist provides you with an overview of all shipping instructions that have been indexed to any booking or bill of lading (B/L) 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. You can configure the data to be displayed in the worklist, such as:

● B/L number, type, and status


Documentation

● SI queue ID, type and status● SI datatization● Order party ID● Shipper ID

From this worklist, you can navigate to the relevant booking or bill of lading, and then process the shipping instructions.

Related Information

For more information, see SAP Library for your SAP NetWeaver release on SAP Help Portal at http://help.sap.com/netweaver. Under Application Help Function-Oriented View , open SAP Library and search for Personal Worklist.

5.1.7 Reassigning Shipping Instructions

Reassign shipping instructions (SIs) in a booking or bill of lading, for example, if they were assigned by mistake, or if a shipping instruction was previously canceled and you want to reactivate it.

Prerequisites

The shipping instruction has not yet been processed.

Procedure


2. Select the shipping instruction that you want to reassign.3. Choose Reassign.4. In the dialog box that opens, enter a booking or bill of lading to which you want to reassign the shipping

instruction.

NoteIf you want to reactivate a canceled shipping instruction, enter the same (current) booking or bill of lading.

5. Choose OK.6. Save the booking, or save and submit the bill of lading.




Results

The reassigned shipping instruction disappears from the list of shipping instructions assigned to the current booking or bill of lading. If you have reassigned a shipping instruction that was previously canceled, its status changes to Not Processed.

Related Information

Processing Shipping Instructions [page 263]Canceling Shipping Instructions [page 272]Shipping Instruction Worklist [page 270]

5.1.8 Canceling Shipping Instructions

Cancel a shipping instruction if it contains poor quality data or insufficient data, for example.

Prerequisites

● The reason codes for canceling shipping instructions (reason category CANLSI) have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill Of Lading Define Activity Log Objects

● The shipping instruction has not yet been processed.

Procedure


2. Select a shipping instruction that you want to cancel.3. Choose Cancel SI.4. In the dialog box that appears, enter a reason code and any remarks.5. Choose OK.6. Save the booking or bill of lading.


Documentation

Results

The status of the shipping instruction changes to Canceled.

Related Information

Reassigning Shipping Instructions [page 271]

5.2 Bills of Lading

A bill of lading (B/L) is a document that must be issued by the carrier to the shipper, booking party, and so on. It is a receipt for the goods, proof of the contract of carriage, and also a document of title.

Overview

The B/L includes details about the goods such as the weight and the number of packages. It also includes the terms and conditions of the contract of carriage.

Certain types of B/Ls are negotiable documents, which means that the title of the goods can be traded. Other types of B/Ls such as waybills are nonnegotiable, which means that the carrier is required to deliver the goods to the consignee named on the document. A waybill is a special type of B/L, which unlike a normal B/L is not a document of title.

The B/L document is created from either the shipping instruction (SI) or the booking. When you create a B/L, the system copies the data from the SI or the booking to the B/L. The B/L always needs to be connected to a booking; it is not possible to store a B/L in the system without an assigned booking. The only exception is memo B/Ls, which can be created without a reference to other bookings or B/Ls, for example, for shipping ship spares, empty containers, or returned cargo.

The system also determines customer-specific or country-specific data from the partner and location profiles for B/L creation, for example, the default number of B/L copies. You can make manual changes to a B/L in the system. The system provides the Bill of Lading screen where you can enter data in a B/L or change the existing data in a B/L.

It is possible to split one B/L with single or multiple containers into multiple B/Ls (either to a new B/L or appended to an existing B/L) and to merge multiple B/Ls into one B/L.

A draft B/L can be issued to verify the details with the shipper, booking party, and so on, before the original B/L is released. Once the draft B/L is approved and the containers are gated-in into the terminal or yard, the recorded unit of cargo information is validated against the booking and B/L data. For example, the seal types, the seal IDs, the container types, the weight, and the container number are all validated against the booking and B/L data.

Before you can manually release a B/L, several system checks must be successful, including the following:


● The draft B/L has been accepted.● The containers or cargo have been gated-in or loaded on board the vessel.● The export charges have been paid.

Before you can release the B/L cargo, several system checks must be successful, including the following:

● The containers or cargo have been discharged at the destination.● The import charges have been paid.

Integration

The B/L is integrated with the following other processes within the overall solution:

Integration


Shipping Instruction The cargo details are recorded in a shipping instruction.

Booking The B/L is created from the booking for charge calculation and tracking purposes.

Voyage Suggestion Framework (VSF) The VSF is executed to check the equipment availability, check the allocation availability, and return the ranked route proposals for future planning purposes.

Part-Load Process The part-load scenario is a special booking process in which one container is shared by several B/Ls.

Manifest The B/L is eventually assigned to one or more manifests.

Partner and Location Profile (PLP) The B/L is adjusted based on the additional settings in the PLP. For example, the PLP is used to specify the number of B/L originals.

Generic Validation Framework (GVF) The GVF is used to determine whether the B/L data conflicts with the predefined restriction and prohibition rules, and also to generate any necessary approval items.

Forwarding Settlement Document (FWSD) The FWSD is generated for invoice processing.

Delivery Order (DO) The delivery order is issued during the B/L cargo release process.

Related Information

Shipping Instructions [page 261]Bookings [page 161]Route Proposal Generation [page 231]Part-Load Bookings [page 244]


Documentation

Manifest [page 330]Partner and Location Profiles [page 51]Generic Validation Framework [page 89]Delivery Orders [page 349]

5.2.1 Creation of Bills of Lading

There are multiple ways to create bills of lading (B/Ls) in the system, such as directly from a booking or from a booking through a shipping instruction.

You can create a B/L in one of the following ways:

● Directly from a booking● From a booking through a shipping instruction● From a booking and a template● From a booking and an existing B/L● As a memo B/L (with no booking reference)

Related Information

Creating B/Ls from Bookings [page 275]Processing Shipping Instructions [page 263]Creating B/Ls from Bookings and Templates [page 276]Creating B/Ls from Bookings and Existing B/Ls [page 277]Creating Memo B/Ls [page 322]

5.2.1.1 Creating B/Ls from Bookings

Create a bill of lading (B/L) from a confirmed booking to copy all of the relevant data from the booking into the new B/L.

Prerequisites

The booking is confirmed.


Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Create Bill of Lading .2. Specify the booking number and choose Continue.

The system displays the Bill of Lading screen and copies all the relevant data from the booking.3. Enter the required data such as the B/L type, the B/L subtype, any missing business partners, the cargo

description, the cargo item details, and so on.4. Save the B/L.

5.2.1.2 Creating B/Ls from Bookings and Templates

Create a bill of lading (B/L) from a confirmed booking and a B/L template to copy all of the relevant data from the booking, and then overwrite the booking data with the corresponding data from the template.

Prerequisites

● The booking is confirmed.● A relevant B/L template to copy from exists.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Create Bill of Lading .2. Specify the booking number and the B/L template number, and then choose Continue.

The system displays the Bill of Lading screen. The relevant data is copied from the booking. Then, the fields in the booking are overwritten with the corresponding field values from the template.

3. Enter the required data such as the B/L type, the B/L subtype, any missing business partners, the cargo description, the cargo item details, and so on.

4. Save the B/L.


Documentation

5.2.1.3 Creating B/Ls from Bookings and Existing B/Ls

Create a bill of lading (B/L) from a confirmed booking and an existing B/L to copy all of the relevant data from the booking, and then overwrite certain fields with the corresponding fields from the existing B/L.

Prerequisites

● The booking is confirmed.● The relevant B/L to copy from exists.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Create Bill of Lading .2. Specify the booking number and the existing B/L number.

The system displays the Bill of Lading screen. The relevant data is copied from the booking, and then the following field values are overwritten with the corresponding field values from the existing B/L:

○ Number of items, their types, and commodity codes○ Source and destination locations○ Business partners○ Cargo description○ Clauses○ B/L type and B/L subtype

The following fields are not copied from the existing B/L:

○ Dates○ Secure B/L numbers○ Container IDs○ Seal numbers○ Shipping instructions○ House bills of lading○ Surrender information○ External Web printing information

3. Enter the required data such as the B/L type, the B/L subtype, any missing business partners, the cargo description, the cargo item details, and so on.

4. Save the B/L.


5.2.1.4 Address Data Check for Business Partners

In a bill of lading (B/L), each business partner's name and address are initially defaulted from master data. If you manually adjust the defaulted name and address, the system calculates a deviation score, so that you can quickly see how much the default details have been changed.

For each business partner in the B/L, you can view the Name Deviation Score and the Address Deviation Score as a percentage. These fields are displayed when you select a business partner on the Business Partner tab and under each business partner on the General Data tab.

The Business Add-In (BAdI) /TMCSL/BADI_BL_PARTY_DEVIATION is provided to compare and score the name and address master data with the name and address data modified in the B/L for printing purposes. This BAdI is triggered each time you change the business partner name and address data.

NoteThe BAdI /TMCSL/BADI_BL_PARTY_DEVIATION must be implemented to enable this functionality. SAP does not provide any default implementation. If the BAdI /TMCSL/BADI_BL_PARTY_DEVIATION is not implemented, then all of the deviation scores are always set to 0%.

Customers can implement this BAdI to compare the name and address from master data with one of the following addresses:

● The address entered in a structured way on the Business Partner tab (possible for any business partner)● The name and address entered as free text on the General Data tab (possible for any business partners

with the roles shipper, consignee, forwarding agent, and notify party)

5.2.1.5 Country-Specific Information in B/Ls

It is possible to store country-specific information, which is mainly related to the manifest and Customs processes (for example, the UN location code for Customs clearance location, location of goods, and so on). This information is stored in the booking and the bill of lading (B/L).

The solution provides the following country-specific information:

Country Field

Angola National Council of Chargers/Shippers Certificate

Ireland Consolidation Flag

Madagascar Electronic Cargo Tracking Note

Guinea-Bissau Electronic Cargo Tracking Note

Niger Electronic Cargo Tracking Note

Canada Customs Clearance


Documentation

Country Field

Location of Goods

Burkina Faso Electronic Cargo Tracking Note

Republic of Congo ECTN/Unique Registration Number

Nigeria Form M

Kenya Import Declaration Form

Ecuador Manifest Sequence Number Code

These fields are available for the dynamic field profile configuration in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation BookingProfile Settings Maintain Dynamic Profiles for Field Attributes .

NoteCountry-specific attributes are defined as components of the structure /TMCSL/S_TRQ_ADD_ATTR_P. This structure has an enhancement include /TMCSL/INCL_EEW_TRQ_ADD_ATTR_P, where customers can add their own country-specific attributes included in the append structure.

The dynamic field profile is assigned to a location through a location profile in Master Data Partner and Location Profile Change Profile . The dynamic attributes profile is maintained on the Booking tab. When a booking or a B/L is manifested, all of the stops from all of the related manifests are available on the Additional Location Characteristics tab in the Booking screen and the Bill of Lading screen.

Related Information

Partner and Location Profiles [page 51]Entering Country-Specific Information in B/Ls [page 280]


5.2.1.5.1 Entering Country-Specific Information in B/Ls

Enter country-specific information on the Additional Location Characteristics tab in bookings and bills of lading (B/Ls). This information is mainly related to manifest and Customs processes (for example, the UN location code for Customs clearance location, location of goods, and so on).

Prerequisites

● The dynamic fields profile has been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Profile Settings

Maintain Dynamic Profiles for Field Attributes .● The dynamic attributes profile has been specified in the location and country profile in SAP NetWeaver

Business Client under Master Data Partner and Location Profile Change Profile .

NoteIf the dynamic attributes profile has not been specified in the location profile, the country profile is chosen.

● The B/L is manifested.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading , and open the relevant B/L.

2. On the Additional Location Characteristics tab, select the relevant location.

The system displays the additional country-specific fields.3. Enter the required data.4. Save the B/L.

5.2.1.6 Reefer Details in Bookings and B/Ls

The Reefer Details tab is used to capture additional information for reefer equipment in the Booking screen and the Bill of Lading (B/L) screen.

The additional reefer fields are only available for items with item types that are configured as reefers in Customizing for SAP Transportation Management under Transportation Management Master DataResources Define Equipment Groups and Equipment Types .

Reefer fields are only relevant for cargo items of type Container and roll-on roll-off (RORO). In a booking or a B/L, you can manually indicate if a dry container (a non-reefer container) needs a reefer plug during transport.


Documentation

To do so, select the relevant container or RORO item in the item hierarchy table, and then select the Dry Container Plug checkbox on the Container Details tab for the selected item. When the Dry Container Plug checkbox is selected, the Reefer Details tab is displayed for the item. If the selected equipment item is of type Reefer, then the Dry Container Plug checkbox is disabled.

The fields available on the Reefer Details tab are as follows:

● Options (Checkboxes):○ Nonoperated Reefer: This option is not relevant for dry containers with the Dry Container Plug

checkbox selected, as the two options are mutually exclusive.○ Generator Origin○ Generator Destination○ Vent Open Flag: When selected, enables the Vent Open and Vent Open % fields.○ Humidity Control: When selected, enables the Humidity % field.○ Cold Treatment○ Generator Set Required○ Refrigerated○ Super Freeze: Indicates that a carrying temperature lower than -30 Celsius is required.○ Multiset Temperatures: Enables the table for entering the temperature sets.

● Temperature settings:○ Temperature From/To○ Carrying Temperature○ Preset Temperature

● Preset Code● Controlled Atmosphere: You can specify either not required, controlled, or regulated.● Gas percentage in atmosphere: You can enter up to five different gases and percentages.

The default unit of measurement (UoM) for temperature fields is based on the country profile and is determined from the country of the port of loading. The system supports automatic conversion to this UoM if you specify the temperatures in a different UoM.

5.2.1.7 Entering Container Seal Details

Enter the seal number, the seal type, and the seal party on the Container Seals tab for a container item in the Bill of Lading (B/L) screen.

Prerequisites

● You have created a B/L with container items.● The following settings have been made in Customizing for SAP Transportation Management under

Container Shipping Liners Order to Cash Booking and Documentation Bill Of Lading Define Seal Types :○ The seal types have been maintained.○ One of the seal types has been marked as default.


● The following settings have been made in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Define Business

Party Role Control :○ The seal parties have been identified by selecting the Seal Allwd (Seal Allowed) checkbox.○ One of the seal parties has been marked as default by selecting the Seal Dflt (Seal Default) checkbox.

Procedure


2. In the Items section, select the relevant container item.

The system displays the container details below the items table.3. On the Container Seals tab, choose Add.4. Enter the seal number, the seal type, and the seal party.5. Save the B/L.

5.2.1.8 Printing Options for Bills of Lading

Printing options are displayed on the Print Options tab in the Bill of Lading screen. Most of these settings are defaulted from the partner and location profile.

The following printing options are defined in the shipper's business partner profile:

● Number of originals● Number of copies (sea waybill) with rates● Number of copies (sea waybill) without rates● Number of copies (nonnegotiable copies) with rates● Number of copies (nonnegotiable copies) without rates

The following printing options are defined in the country profile for the port of loading:

● Suppress shipper address● Print settlement terms● Print order number● Print equipment type● Print quantity/type● Print weight● Print measurement● Convert weight and cube● Print commodity description● Print net weight● Print converted net weight● Print equipment for carrier convenience


Documentation

● Metric weight unit of measurement (UoM)● Metric measurement UoM● Imperial weight UoM● Imperial measurement UoM● Print charges● Sea waybill print charges

You can change the B/L printing options in Master Data Partner and Location Profile Change Profile . Open the corresponding profile, and you'll find the relevant settings on the Documentation tab. If you change the shipper or the port of loading in a B/L, the system automatically updates the print options from the relevant partner and location profile.

Related Information

Partner and Location Profiles [page 51]

5.2.2 Draft Bill of Lading Status

The Draft B/L Status indicates the progress of a bill of lading (B/L) through the customer approval process.

Once a B/L is completed, the draft B/L is sent to the customer for approval. The customer needs to review the draft and either approve it or request modifications. By default, the approval of the draft B/L should be received within 48 hours of being sent to the customer. Beyond this time, and in the absence of any reply from the customer, the draft B/L is automatically considered as approved.

You can change the time period for automatic draft B/L approval in the partner profile for the customer. You can also define that a draft B/L is not required, because some customers may not require a draft B/L for approval.

If a new or amended shipping instruction (SI) is indexed and draft B/L approval is required for the customer, then the draft B/L needs to be approved again.

The Draft B/L Status is displayed on the Statuses tab in the Bill of Lading screen and has the following possible values:

● Not Required● In Progress● Pending Approval● Approved by Customer● Automatically Approved● Authorized● Information Requested from Agency● Information Provided by Agency● Information Requested from Customer● Information Provided by Customer


The Draft B/L Status is checked before the B/L is released. If draft B/L approval is required and the draft has not yet been approved or authorized, the system prevents the B/L from being released.

APIs for Updating the Draft B/L Status

The sending of the draft B/L to the customer is out of the scope of the system. However, the system provides an application programming interface (API) that should be called during the sending process to update the Draft B/L Status to Pending Approval. The system also provides an API to set the Draft B/L Status to one of the following values:

● Information Requested from Agency● Information Provided by Agency● Information Requested from Customer● Information Provided by Customer

Manual Authorization of the Draft B/L Status

If you have the required authorization, you can override the draft B/L status by authorizing the B/L manually. You must enter a reason code when you do so, and the system records the event in the activity log.

Related Information

Changing the Draft B/L Automatic Approval Time [page 284]Setting Draft B/L as Not Required [page 285]Authorizing Draft B/Ls [page 285]

5.2.2.1 Changing the Draft B/L Automatic Approval Time

Change the automatic approval time for draft bills of lading (B/Ls) in the partner profile for the customer.

Context

By default, in the absence of any reply from the customer, a draft bill of lading (B/L) is automatically considered as approved 48 hours after initially being sent to the customer.


Documentation

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Partner and Location Profile Change Profile , and open the profile for the relevant business partner.

2. On the Documentation tab, enter the required value in the Automatic Approval Period (h) field.3. Save your changes.

5.2.2.2 Setting Draft B/L as Not Required

Specify that a draft B/L is not required for a particular customer in the partner profile for the customer.

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Partner and Location Profile Change Profile , and open the profile for the relevant business partner.

2. On the Documentation tab, select the Draft B/L Not Required checkbox.3. Save your changes.

5.2.2.3 Authorizing Draft B/Ls

Authorize a draft bill of lading (B/L) manually on the Statuses tab in the Bill of Lading screen.

Prerequisites

● On the Statuses tab in the Bill of Lading screen, the Draft B/L Status is one of the following values:○ In Progress○ Pending Approval○ Information Requested from Agency○ Information Provided by Agency○ Information Requested from Customer○ Information Provided by Customer

● The reason codes for overriding the draft B/L status have been defined under the reason category DRAFT in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Bill Of Lading Define Activity Log Objects .

● You have the required authorization.


Procedure


2. On the Statuses tab, choose Authorize next to the Draft B/L Status field.

The system displays a dialog box.3. Specify the reason code, enter the reason text, and confirm your entries.4. Save the B/L.

Results

The Draft B/L Status value is updated to Authorized.

5.2.3 Deposit Statuses

The system records deposit statuses for both export and import. The export deposit status is used to determine if the equipment can be released from the depot. The import deposit status is used to determine if the cargo can be released to the receiver or the nominated party.

The export deposit status is visible in the Booking screen and in the Bill of Lading (B/L) screen. The import deposit status is only visible in the Bill of Lading screen.

The possible deposit status values are as follows:

● Not Required● Required● Cleared● Refunded● Authorized

To release the equipment, the required deposits on all of the containers must be cleared (if applicable). These statuses also indicate whether the deposit is refunded. The export deposit is refunded after the containers are gated-in at the terminal at the port of loading (POL). The import deposit is refunded after the empty containers are returned to the return depot.

When all of the containers in a booking or a B/L are shipper-owned, the deposit status is set to Not Required. The system provides a Business Add-In (BAdI) that sets the deposit status to Required or Not Required when the booking is saved. The system also provides an application programming interface (API) that sets the deposit status to Cleared or Refunded.

System Validation Checks

The system checks the export deposit status when you confirm the booking. The booking cannot be confirmed while the export deposit is required. The system checks the import deposit status when you release the cargo.


Documentation

The system prevents the cargo from being released when the import deposit is required. To set the B/L status to Import Finalized, the import deposit status must be Refunded or Not Required.

In the part-load scenario, an equipment booking can only be completed when both the export and the import deposit statuses are Refunded or Not Required.

Manual Authorization of Deposit Statuses

If you have the required authorization, you can override the deposit statuses by authorizing the deposit statuses manually. You must enter a reason code when you do so, and the system records the event in the activity log.

Related Information

Authorizing Deposit Statuses [page 287]

5.2.3.1 Authorizing Deposit Statuses

Authorize the export deposit status or the import deposit status for a bill of lading (B/L) manually on the Statuses tab in the Bill of Lading screen.

Prerequisites

● Either the export deposit status or the import deposit status is Required.● The reason codes for authorizing the deposit status have been defined in Customizing for SAP

Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill Of Lading Define Activity Log Objects . The reason codes for authorizing the export deposit status are configured in the reason category AUDE_E, and the reason codes for authorizing the import deposit status are configured in the reason category AUDE_I.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading and open the relevant B/L.

2. On the Statuses tab, choose Authorize next to the relevant Deposit Status field.

The system displays a dialog box.


3. Specify the reason code, enter the reason text, and then confirm your entries.4. Save the B/L.

Results

The deposit status value is changed to Authorized. The manual authorization event is recorded in the activity log for the B/L.

5.2.4 Financial Status and Credit Check

The system provides credit check and financial statuses for both export and import. Export statuses are available in the Booking and the Bill of Lading (B/L) screens. Import statuses are only available in the Bill of Lading screen.

Credit Check

The Credit Check field is displayed on the Statuses tab and has the following possible values:

● Credit● Cash

The export credit check is determined before the B/L release. The import credit check is determined before the cargo release.

Financial Status

The Financial Status field is displayed on the Statuses tab and has the following possible values:

● Not Paid● Partially Paid● Fully Paid● Authorized● Not Required

The financial statuses are recalculated every time you save the B/L. Export and import financial statuses show whether the respective prepaid and collect charges are paid. Statistical, deactivated charges, or charges with zero amount are excluded from the status determination. The system determines the financial status as follows:

● If no charges exist or all of them have zero amount, the status is Not Required.● If all charges are not paid, the status is Not Paid.


Documentation

● If some charges are paid and some are not, the status value is Partially Paid.● If all charges are paid, the status is Fully Paid.


The export credit and financial status are checked before the B/L is released. When credit check is Cash and the financial status is Not Paid or Partially Paid, the system prevents the B/L from being released. The import credit and financial status are checked before cargo release. The system prevents the cargo from being released when the credit check is Cash and the financial status is Not Paid or Partially Paid.

Manual Authorization of Financial Status

If you have the appropriate authorization, you can override the financial status by authorizing it manually. You are required to enter a reason code if you do so, and the system records the event in the activity log.

Related Information

Authorizing the Financial Status in B/Ls [page 289]

5.2.4.1 Authorizing the Financial Status in B/Ls

Authorize the financial status for a bill of lading (B/L) manually on the Statuses tab in the Bill of Lading screen.

Prerequisites

● Either the export or the import financial status in the B/L is Not Paid or Partially Paid.● The reason codes for authorizing the financial status have been configured in Customizing for SAP

Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill Of Lading Define Activity Log Objects . The reason codes for authorizing the export financial status are configured in the reason category AUFI_E, and the reason codes for authorizing the import financial status are configured in the reason category AUFI_I.



Procedure


2. On the Statuses tab, choose Authorize next to the export or import financial status.


Results

The status value is updated to Authorized.

5.2.5 Quality Checks

In some cases, it’s necessary to perform a manual quality check for a bill of lading (B/L). The quality check may be required on the export side of the shipment, or on the import side of the shipment, or on both.

You can specify that manual quality checks are required for a B/L in the following ways:

● In the partner and location profileThe system can automatically determine whether the quality check is required for a B/L based on the partner and location profile for the countries of the port of loading (POL) and the port of discharge (POD). You specify the relevant settings under Master Data Partner and Location Profile Change Profile . In the profile for the country, on the Documentation tab, you select the Required checkbox for Import Quality Check and/or Export Quality Check.

● In the bill of ladingIf based on the country profile the quality check is not required, you can set it as required for an individual B/L. In the Bill of Lading screen, choose Export Quality Check Required and/or Import Quality Check Required , as appropriate.

You can view the quality check status on the Statuses tab in the Bill of Lading screen. If quality checks are required, the corresponding cleanup status is also required. The export cleanup status is checked when the B/L is released, and the import cleanup status is checked when the cargo is released.

Related Information

Setting Quality Checks as Required in PLP [page 291]Setting Quality Checks as Required in B/Ls [page 291]Updating the Export Quality Check Status [page 292]Updating the Import Quality Check Status [page 293]


Documentation

5.2.5.1 Setting Quality Checks as Required in PLP

Specify the default settings for bill of lading (B/L) quality checks in the profile for a country.

Context

When you create a B/L, the system automatically determines whether the quality check is required based on the partner and location profile for the countries of the port of loading (POL) and the port of discharge (POD). The quality check may be required on the export side of the shipment, or on the import side of the shipment, or on both.

Procedure


2. Open the profile for the relevant country.3. On the Documentation tab, in the Statuses section, select Required for the Import Quality Check field, or

the Export Quality Check field, or both as appropriate.4. Save your changes.

5.2.5.2 Setting Quality Checks as Required in B/Ls

Specify that a manual import quality check, a manual export quality check, or both are required for a specific bill of lading (B/L) and override the default settings in the country profile.

Prerequisites

● You have created a (B/L).● The B/L is not released.● The export quality check status is currently Not Required and/or the import quality check status is

currently Not Required.

Procedure



2. Choose the relevant option as follows:

○ To set the export quality check status to Required, choose Export Quality Check Required .

○ To set the import quality check status to Required, choose Import Quality Check Required .3. Save the B/L.

5.2.5.3 Updating the Export Quality Check Status

Enter the outcome of the export quality check in the Bill of Lading (B/L) screen.

Prerequisites

● You have created the B/L.● You have not released the B/L.● The export quality check status is Required.● The reason codes for the quality check status failure have been defined within the reason category EQA_F

in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Bill Of Lading Define Activity Log Objects.

Context

If a manual export quality check is required for a B/L, you must enter the outcome of the quality check in the Bill of Lading screen. To release a B/L, the export quality check status must be either Successful or Not Required.

Procedure



○ If the manual quality check was successful, choose Export Quality Check Successful .The system updates the export quality check status to Successful.

○ If the manual quality check failed, choose Export Quality Check Failed .For a failed quality check, the system displays a dialog box where you specify the reason code and you can also enter the reason text. When you save your entries, the system updates the export quality check status to Failed.

3. Save the B/L.


Documentation

5.2.5.4 Updating the Import Quality Check Status

Enter the outcome of the import quality check in the Bill of Lading (B/L) screen.

Prerequisites

● You have created the B/L.● The cargo release status is On Hold.● The import quality check status is Required.● The reason codes for quality check status failure have been defined within the reason category IQA_F in

Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Bill Of Lading Define Activity Log Objects.

Context

If a manual import quality check is required for a B/L, you must enter the outcome of the import quality check before the cargo can be released.

Procedure



○ If the manual quality check was successful, choose Import Quality Check Successful .The system updates the import quality check status to Successful.

○ If the manual quality check failed, choose Import Quality Check Failed .For a failed quality check, the system displays a dialog box where you specify the reason code and you can also enter the reason text. When you save your entries, the system updates the import quality check status to Failed.

3. Save the B/L.


5.2.6 Operational Statuses in Bills of Lading

Operational statuses reflect the aggregated status for various operations such as gate-in and loading that occur for the units of cargo in bookings and bills of lading (B/Ls).

A trip plan is used to manage the coordination of the end-to-end flow of the units of cargo throughout the transportation chain. The operational trip plan is available on unit of cargo level, and contains all of the expected, actual, and unexpected operational events that are planned or reported.

The following statuses are available on the Statuses tab in the Bill of Lading screen:

Status Possible Values Description

Empty Container Release Status ● Not Required● Not Released● Partially Released● Fully Released

This status is applicable only when empty provisioning is requested for at least one container in the B/L. It indicates whether the empty containers were released from the equipment depot for further stuffing.

Gate-In (POL) Status ● Not Gated-In● Partially Gated-In● Fully Gated-In

When none of the units of cargo are gated-in at the port of loading (POL), the status is set to Not Gated-In. When some of the units of cargo are gated-in, the status is set to Partially Gated-In. When all of the units of cargo are completely gated-in, the status is set to Fully Gated-In.

Load (POL) Status ● Not Loaded● Partially Loaded● Fully Loaded

When none of the units of cargo are loaded at the POL, the status is set to Not Loaded. When some of the units of cargo are loaded at the POL, the status is set to Partially Loaded. When all of the units of cargo have been loaded onto the vessel at the POL, the status is set to Fully Loaded.

Load (Last PTS) Status ● Not Required● Not Loaded● Partially Loaded● Fully Loaded

When none of the units of cargo are loaded at the last port of transshipment (PTS), the status is set to Not Loaded. When some of the units of cargo are loaded at the last PTS, the status is set to Partially Loaded. When all the units of cargo have been loaded onto the vessel at the last PTS, the status is set to Fully Loaded. When there’s no port of transshipment in the trip plan, the status is set to Not Required.


Documentation

Status Possible Values Description

Discharge (POD) Status ● Not Discharged● Partially Discharged● Fully Discharged

When none of the units of cargo are discharged at the port of discharge (POD), the status is set to Not Discharged. When some of the cargo units are discharged, the status is set to Partially Discharged. When all of the units of cargo have been discharged from the vessel the status is set to Fully Discharged.

Empty Container Return Status ● Not Required● Not Returned● Partially Returned● Fully Returned

This status is applicable only when empty provisioning or empty return is requested for at least one container in the B/L. It indicates whether the empty containers were returned to the equipment depot.

5.2.7 Gate-In Reconciliation

Gate-in reconciliation is a crucial step before the bill of lading (B/L) can be released. The gate-in reconciliation process includes the comparison of the cargo items declared in the draft version of the B/L with the actual cargo received in the terminal at gate-in.

The actual cargo data is stored as an item in the manifest that the B/L is assigned to at gate-in. In other words, it’s always stored in the first manifest for the B/L.

You cannot release a B/L if the reconciliation for the items is not successful, that is, if there are discrepancies between the B/L and the actual cargo data after the terminal gate-in at the port of loading (POL).

Gate-in reconciliation includes the following data checks for containers:

● Number of containers (mandatory)● Seal IDs

The system checks if the seal IDs are recorded in the B/L. The number of seals does not have to match.

● Weight (mandatory)There is a weight tolerance indicator in the business partner profile for each customer.

If a gate-in reconciliation data check fails, a discrepancy is recorded in the document where the gate-in (actual) data is reported.


Discrepancy Types

The following types of discrepancy have been configured in the system:

Cargo Item Type Discrepancy Type

Container ● Weight● Container number● Seal

Break Bulk ● Weight● Size (length, width, or height)

Roll-on Roll-off (RORO) ● Weight● Truck/trailer vehicle identification number (VIN)● Vehicle registration plate● Driver license number● Driver passport number

Related Information

Resolving Gate-In Reconciliation Failures [page 296]Gate-In Reconciliation Status [page 298]

5.2.7.1 Resolving Gate-In Reconciliation Failures

Investigate and resolve gate-in reconciliation failures using the options available on the Discrepancies and Events tab in the Bill of Lading (B/L) screen.

Prerequisites

The gate-in reconciliation status is Failed.

Context

If any of the data checks fail during the gate-in reconciliation process, discrepancies are added to the B/L, and the gate-in reconciliation status is set to Failed. You need to investigate the discrepancies, and then make the necessary corrections.


Documentation

Procedure


2. In the Items section, select a cargo item.

The system displays the item details below the item hierarchy table.3. In the item details, on the Discrepancies and Events tab, check if there are any unresolved discrepancies for

failed gate-in reconciliation.

You need to repeat this step for each cargo item.

NoteIf the gate-in reconciliation status is Failed, but there are no discrepancies for the B/L items, then the number of gated-in cargo items does not match the number of items in the B/L.

4. (Optional) Check whether each item is gated-in, as follows:a. Navigate to the TU/FU for the cargo item by clicking the link in the TU/FU column of the item hierarchy

table, or by clicking the link in the Business Document column on the Document Flow tab.

The system displays the TU/FU screen.b. On the Trip Plan tab, choose the Event Overview/Reporting sub-tab.

All of the operational events that have happened for this particular unit are recorded here.c. Check if the gate-in event at the port of loading is listed.

5. If you find an unresolved discrepancy for failed gate-in reconciliation, resolve the gate-in reconciliation failure using one of the following methods:

○ Update the data in the B/L manually, so that it corresponds to the actual data reported at gate-in.○ Above the item hierarchy table, choose Overwrite from Gate-In.

The system copies all of the relevant data from the manifest item and thus all the discrepancies for the item are resolved.

○ Above the item hierarchy table, choose Discard Gate-In.The system skips the discarded item during the reconciliation process.

○ On the Statuses tab, choose Authorize next to the Gate-In Reconciliation field.The system updates the gate-in reconciliation status to Authorized.

6. Save the B/L.

Results

The gate-in reconciliation status is Successful or Authorized.

Related Information

Gate-In Reconciliation Status [page 298]


5.2.7.2 Gate-In Reconciliation Status

The gate-in reconciliation process results in a gate-in reconciliation status, which is available on the Statuses tab in the Bill of Lading screen.

The possible status values are as follows:

Status Meaning

Not Performed Actual data is not stored in the system for any single cargo item from the B/L.

Failed One of the following scenarios applies:

● Actual data is stored in the system for at least one cargo item but not for all.

● Actual data is stored in the system for all cargo items from the B/L, but is different from the ordered data at least for one container so that it leads to a discrepancy.

Successful Actual data is stored in the system for all cargo items from the B/L and there are no discrepancies.

Authorized An authorized user has authorized the gate-in reconciliation status manually. The previous status was either Not Performed or Failed.

Related Information

Resolving Gate-In Reconciliation Failures [page 296]

5.2.8 Customer Customs Clearance

The export Customs clearance status must be Cleared or Authorized before the bill of lading (B/L) can be released, and the import Customs clearance status must be Cleared or Authorized before the cargo can be released.

Overview

The Customs clearance status for a B/L is an aggregation of the Customs clearance statuses for the individual cargo items. The Statuses tab on the Bill of Lading screen displays the aggregated status for both export


Documentation

Customs clearance and import Customs clearance. The possible values for the Customs clearance status are as follows:

● Not Required● Not Cleared● Cleared● Authorized

The system sets the initial value of the export and the import Customs clearance status for an item to either Not Required or Not Cleared. The initial value of the export Customs clearance is determined from the location profile for the port of loading (POL). The initial value of the import Customs clearance is determined from the location profile for the port of discharge (POD). For some locations, the Customs clearance status is not required, and for some countries, certain commodities can be exempted from Customs clearance. If the commodity code for an item is exempted, then the system sets the Customs clearance status for the item to Not Required.

The system provides an application programming interface (API) to set the Customs clearance status for an item to Cleared.


The system checks the export Customs clearance status before the B/L is released. If the status is Not Cleared, the system prevents the B/L from being released. The system checks the import Customs clearance status before cargo release and prevents the cargo from being released when the status is Not Cleared.

Manual Authorization

If you have the appropriate authorization, you can override the Customs clearance status by authorizing the Customs clearance status manually. You must enter a reason code when you do so, and the system records the event in the activity log. The reason codes for authorizing the Customs clearance status are configured in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Bill Of Lading Define Activity Log Objects . The reason codes for export Customs clearance are configured in the reason category AUC_E, and the reason codes for import Customs clearance are configured in the reason category AUC_I.

Related Information

Authorizing Customs Clearance for B/Ls [page 300]Authorizing Customs Clearance for B/L Items [page 301]


5.2.8.1 Authorizing Customs Clearance for B/Ls

Change the Customs clearance status for a bill of lading (B/L) from Not Cleared to Authorized manually.

Prerequisites

● Either the export Customs clearance status or the import Customs clearance status in the B/L is Not Cleared.

● The reason codes for authorizing the Customs clearance status have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill Of Lading Define Activity Log Objects . The reason codes for export Customs clearance are configured in the reason category AUC_E, and the reason codes for import Customs clearance are configured in the reason category AUC_I.

● You have the appropriate authorization.

Context

If you have the appropriate authorization, you can manually authorize the export and import Customs clearance status for a B/L. When you authorize the Customs clearance for the entire B/L, all of the items that have the status Not Cleared are updated to the status Authorized.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading , and then open the relevant B/L.

2. On the Statuses tab, choose Authorize next to the relevant export or import Customs Clearance field.3. Specify the reason code, enter the reason text, and confirm your entries.4. Save the B/L.

Results

● The Customs clearance status for the B/L is updated to Authorized.● The Customs clearance status of any items that had the value Not Cleared is updated to Authorized.


Documentation

Related Information

Authorizing Customs Clearance for B/L Items [page 301]

5.2.8.2 Authorizing Customs Clearance for B/L Items

Change the Customs clearance status for a cargo item in a bill of lading (B/L) from Not Cleared to Authorized manually.

Prerequisites

● Either the export Customs clearance status or the import Customs clearance status of the item in the B/L is Not Cleared.

● The reason codes for authorizing the Customs clearance status have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill Of Lading Define Activity Log Objects . The reason codes for export Customs clearance are configured in the reason category AUC_E, and the reason codes for import Customs clearance are configured in the reason category AUC_I.

● You have the appropriate authorization.

Procedure


2. In the Items section, select the relevant item.

The system displays the item details below the item hierarchy table.3. On the Customer Customs Clearance tab in the item details, choose Authorize next to the export or import

Customs clearance status.


Results

● The Customs clearance status value for the item is updated to Authorized.● If this is the only item that was not authorized or cleared, then the aggregated Customs clearance status of

the B/L is also updated to Authorized.


Related Information

Authorizing Customs Clearance for B/Ls [page 300]

5.2.9 Release of Bills of Lading

The release process for bills of lading (B/Ls) is determined based on the B/L type and the release mode Customizing settings. The progress of the release process is tracked using the B/L Release Status.

In some cases, original documents (secure B/Ls) are issued and then need to be surrendered before the cargo release. For an external release, document copies are published to an external system, or are sent electronically to an electronic data interchange (EDI) platform. Express release, which is usually used for sea waybills, is the quickest variation of a B/L release and in this case an original B/L is never issued.

The party to whom the B/L is to be released (B/L Release-to Party) is defaulted from the profile for country of the port of loading (POL) based on specified brand. If no brand is specified for the B/L, the system uses the first release-to party value from the profile. The release mode is defaulted from the business partner profile of the release-to party.

You can enter release-specific information in the Bill of Lading screen (for example, a tracking number or a mail service provider if the B/L is released by mail, and so on). The system provides the following release-specific fields:

● Bar Code Number● Mail Tracking Number (AWB)● Mail Service Provider Name● Date Sent● Release Date● Release User

The behavior of these fields is controlled by the Business Add-In (BAdI) Setting of Field Properties in Bill of Lading.

NoteRelease-specific attributes are defined as components of the structure /TMCSL/S_BL_RELEASE_INFO. The structure has the enhancement include /TMCSL/INCL_EEW_ BL_RELEASE_INF, where customers may add their own release-specific attributes included in the append structure.

Related Information

Defining Release-To Parties for B/Ls [page 303]Releasing Bills of Lading [page 303]External Printing of Released B/Ls [page 305]


Documentation

5.2.9.1 Defining Release-To Parties for B/Ls

Define the party to whom bills of lading (B/Ls) are to be released in the country profile for the relevant port of loading (POL).

Context

The system determines the release-to party automatically, based on the POL and the brand for the B/L. If no release-to party is specified in the country profile, the default release-to party is taken from Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings Define Business Party Role Control .

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Partner and Location Profile Change Profile , and then open the profile for the relevant country.

2. On the Documentation tab, choose Add to insert a new line in the B/L Release Information table. Alternatively, if there is already an entry for the brand, you can change the existing line in the table.

3. Specify the brand and the release-to party.4. Save your entries.

Related Information

Releasing Bills of Lading [page 303]External Printing of Released B/Ls [page 305]

5.2.9.2 Releasing Bills of Lading

Release a bill of lading (B/L) by choosing Release on the Statuses tab in the Bill of Lading (B/L) screen.

Prerequisites

● You have created the B/L.● If the B/L is a part-load B/L, the part-load consistency status of the equipment booking is Consistent.


● The location-specific fields check is successful.● The export financial status is either Not Required, Fully Paid, or Authorized, or credit is provided.● The draft B/L status is Approved.● The container reconciliation is successful.● The export customs clearance status is Cleared.● The export cleanup status is successful.● The list of possible business partner roles for B/L release has been configured in Customizing for SAP

Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Basic Settings Define Business Party Role Control (Rel. Allwd (Release Allowed) checkbox is selected).

● The release mode settings have been configured in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill Of Lading Define Bill of Lading Release Modes .

For an original release or an express release, the following prerequisites also apply:

● If it is a secure B/L, the number of papers from the secure B/L list that are not voided is equal to number of originals.

● The secure B/L setting for the B/L type has been configured in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill Of Lading Define B/L Types and Subtypes .

● The B/L release mode is not set as relevant for external release and external printing.

For an external release the following prerequisites also apply:

● The B/L release mode is set as relevant for external release.

Context

The system determines how to release the B/L based on B/L type and release mode Customizing settings.

Procedure


2. In the toolbar, choose Release.3. Save the B/L.

Results

For an original release or an express release, the result is as follows:


Documentation

● On the Statuses tab, the B/L Release Status is changed to Released.● Your user name and the release date are shown in Release Information section on the Print Options tab.

For an external release, the result is as follows:

● After you choose Save and Submit, the B/L Release Status is changed to Send to Web Platform.● After the API call in the external system, the B/L Release Status is changed to Released.● Your user name, the release date, and the Web Platform from which the API was called are displayed in the

Release Information section on the Print Options tab.

Related Information

Country-Specific Information in B/Ls [page 278]Financial Status and Credit Check [page 288]Draft Bill of Lading Status [page 283]Operational Statuses in Bills of Lading [page 294]Customer Customs Clearance [page 298]Quality Checks [page 290]Defining Release-To Parties for B/Ls [page 303]External Printing of Released B/Ls [page 305]

5.2.9.3 External Printing of Released B/Ls

The release mode for a bill of lading (B/L) can be configured for external printing, so that the B/L can be printed from the Web platform.

An application programming interface (API) is used to send the following information from the external platform to SAP Transportation Management (SAP TM):

● Number of printed copies● User● Date and timestamp

This information is stored in the B/L, and you can view it on the Print Options tab.

The release modes for B/Ls are configured in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill Of Lading Define Bill of

Lading Release Modes . To use external printing, on the Print Options tab, you must specify a Release Mode that is configured as relevant for external release and external printing.


5.2.10 Surrender Bills of Lading

A surrender bill of lading (B/L) is a document that allows a consignee to legally own the shipped items. Surrender information for B/Ls is entered on the B/L screen.

Overview

For certain B/L types, a specified number of B/Ls must be surrendered before the units of cargo in the B/L can be released by the system. The types of B/Ls that need to be surrendered are maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Bill of Lading Define B/L Types and Subtypes . The number of B/Ls that need to be surrendered is specified in the Total Originals field on the Print Options tab.

B/L surrender information is displayed in the B/L Surrender table on the Statuses tab. Surrender information includes the following details:

● Number of B/Ls to be surrendered● Surrender date● Surrender office location● Surrender location classification● Surrendering party● Reason code for surrendering● Reason for surrendering● Endorsement details● Specific delivery instructions

Documentation Status

The Documentation Status field in the Import Status group box on the Statuses tab indicates whether the B/L needs to be surrendered. The possible documentation statuses are as follows:

● Not RequiredThe cargo can be released without surrendering the B/L.

● RequiredThe B/L has to be surrendered before the cargo can be released.

● ClearedThe system sets the documentation status to Cleared if one of the following conditions is true:○ At least one B/L document has been surrendered at the destination location.○ The number of documents specified in the Total Originals field on the Print Options tab have been

surrendered at other locations.● Authorized

An authorized user can change the documentation status from Required to Authorized, which means that the B/L does not have to be surrendered before the cargo can be released.


Documentation

When an amendment shipping instruction is processed, the documentation status is automatically changed from Cleared to Required, and all previously entered surrendered B/Ls are voided.

Related Information

Authorizing Documentation Statuses [page 307]Surrendering Bills of Lading [page 308]

5.2.10.1 Authorizing Documentation Statuses

Change the documentation status of a bill of lading (B/L) from Required to Authorized manually.

Prerequisites

● The documentation status is Required.● The authorization reason codes have been defined for the category AUTHDO in Customizing for SAP

Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill of Lading Define Activity Log Objects .


Context

The document status indicates whether the B/L must be surrendered.

Procedure


2. On the Statuses tab, next to the Documentation Status field, choose Authorize.

The system displays a dialog box.3. Specify the reason code, optionally enter a reason description, and then confirm your entries.4. Save the B/L.


Results

The documentation status is Authorized and the cargo can be released without surrendering the B/L.

Related Information

Surrender Bills of Lading [page 306]Surrendering Bills of Lading [page 308]

5.2.10.2 Surrendering Bills of Lading

Enter the details of bills of lading (B/L) that must be surrendered on the on the Statuses tab on the Bill of Lading (B/L) screen.

Prerequisites

● You have created a B/L.● The Total Originals field on the Print Options tab is not zero.● The documentation status on the Statuses tab is Required.● The SurNotReq (Surrendering Not Required) checkbox has been deselected for the B/L type in

Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Bill Of Lading Define B/L Types and Subtypes .

● The Surr. Allwd (Surrendering Allowed) checkbox has been selected for the business partner role in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Basic Settings Define Business Party Role Control .

● The reason codes for surrendering have been defined for the reason category SURREN in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill Of Lading Define Activity Log Objects .

Context

If the documentation status for a B/L is Required, then at least one B/L document has to be surrendered at the destination location, or the number of copies specified in the Total Originals field has to surrendered at other locations.


Documentation

Procedure


2. On the Statuses tab, in the B/L Surrender screen area, choose Create.3. Enter the details for the B/L that is to be surrendered.4. Save the B/L.

Results

● In the B/L Surrender table, the Recorded On field is filled with the current date and the Recorded By field is filled with the name of the user who entered the B/L surrender details.

● The documentation status is changed to Cleared.

Related Information

Surrender Bills of Lading [page 306]Authorizing Documentation Statuses [page 307]

5.2.11 Cargo Release Status

The Cargo Release Status field represents the progress of the cargo release process and is displayed in the Import Status group box on the Statuses tab in the Bill of Lading (B/L) screen. You cannot release the delivery order unless the Cargo Release Status is Ready to Release.

The possible values for the Cargo Release Status are as follows:

● Not Released● On Hold● Ready to Release● Released

The value of the Cargo Release Status is determined based on the values of the following sub-status fields, which are also displayed on the Statuses tab:

● Financial Status● Credit Check● Customs Clearance● Documentation Status● Deposit Status● Cleanup Status


● Discharge Status

These sub-statuses are listed below the Cargo Release Status in the Import Status group box, with the exception of the Discharge Status, which is listed in the Customs Response Statuses group box.

NoteThe similarly named fields that are listed in the Export Status group box (such as Financial Status, Credit Check, Customs Clearance, and so on) are not relevant for the Cargo Release Status.

The cargo items in a B/L can only be released (that is, the Cargo Release Status is Ready to Release) if all of the sub-statuses listed above are displayed with a green traffic light (Successful, Cleared, Paid, and so on) or are Not Required. Once the delivery order is released, the Cargo Release Status is set to Released.

The system recalculates the Cargo Release Status each time you save the B/L and when any of the sub-statuses are modified. The system checks the Cargo Release Status before you release the delivery order. If the Cargo Release Status is not Ready to Release, then the system prevents you from releasing the delivery order.

You can exclude the Discharge Status from the system checks that are performed before the cargo release as follows:

● In the Discharge Port country profile, choose Master Data Partner and Location Profile Change Profile. Then open the relevant country profile, and on the Documentation tab, select the Ignore Discharge Move checkbox.

● In a B/L, on the Statuses tab next to the Cargo Release Status field, choose Ignore Discharge.

Related Information

Ignoring the Discharge Status [page 310]

5.2.11.1 Ignoring the Discharge Status

Exclude the Discharge Status from the system checks that are performed before the cargo release.

Prerequisites

● The Cargo Release Status in the B/L is either Not Released or On Hold.● The Ignore Discharge Move checkbox has not been selected in the destination country profile.● The reason codes for ignoring the discharge status have been configured in the reason category IG_DIS in

Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Bill Of Lading Define Activity Log Objects .


Documentation

Procedure


2. On the Statuses tab, next to the Cargo Release Status field, choose Ignore Discharge.

The system displays a dialog box.3. Specify the reason code and the reason text and then confirm your entries.4. Save the B/L.

5.2.12 Transshipment PINs for Bills of Lading

Transshipment personal identification numbers (PINs) can be added to bills of lading (B/Ls) that contain units of cargo that will be transferred between two terminals.

You can manually enter the transshipment PIN and expiry date for the unit of cargo. The system can automatically generate the transshipment PIN and expiry date by means of an application programming interface (API).

Related Information

Entering Transshipment PINs in B/Ls [page 311]

5.2.12.1 Entering Transshipment PINs in B/Ls

Enter the transshipment personal identification number (PIN) manually for a unit of cargo or allow the system to automatically generate the PIN.

Prerequisites

● You have created a bill of lading (B/L).● The selected route has a transshipment.


Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading .2. In the Items section, select a container.

The system displays the container details below the item hierarchy table.3. In the Details section, choose the Transshipment PINs tab.4. Specify the transshipment location.5. Choose one of the following options for entering the transshipment PIN and expiry date:

Transshipment PIN Entry Option Step

Manual Specify the transshipment PIN and expiry date.

System generated Choose the Generate button.

NoteIf you manually enter the transshipment PIN, the system checks that the PIN number contains seven digits. If the PIN number has more than or less than seven digits, the system displays a warning message and does not save the B/L.

6. Save the B/L.

Related Information

Transshipment PINs for Bills of Lading [page 311]

5.2.13 Bill of Lading Split

The cargo from a single bill of lading (B/L) can be split into multiple other B/Ls using the Split tab on the Bill of Lading screen.

Full Container Split

You can split one or more containers from a single B/L into multiple other B/Ls. In this case, the split containers are removed from the source B/L and are added to the target B/L.


Documentation

Partial Container Split

You can split cargo (packages) from a container in a source B/L to another container in a target B/L. In this case, you have to specify the number of packages to be split. After a partial split is performed, the weight values are proportionally adjusted in both the source B/L and the target B/L. However, it can happen that the automatically adjusted values differ from the actual values. In this case, you need to correct the weight values manually.

NoteMeasurement values, if specified, are not adjusted and should always be corrected manually.

Related Information

Splitting to a New B/L [page 313]Splitting to an Existing B/L [page 314]

5.2.13.1 Splitting to a New B/L

Split the cargo from a source bill of lading (B/L) into a new B/L using the Split tab on the Bill of Lading screen.

Prerequisites

The source B/L has been created.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading , and then open the source B/L.

2. On the Split tab, specify a reason for the split and enter any remarks that you want to record.3. If you are performing a cargo description split, in the Cargo Description table, select the cargo to be split as

follows:

○ For a full cargo description split, select the corresponding line to be split.○ For a partial cargo description split, select the corresponding line to be split and enter the number of

split packages in the Split Outer Number of Packages field.4. If you are performing an items split, in the item hierarchy table, select the cargo to be split as follows:

○ For a full container split, select the containers to be split.


○ For a partial container split, select the line to be split and enter the number of packages to be split in the Split Number of Packages field.

5. In the Split Documents screen area, choose Add New .

A new target document is added to the table below. If required, you can add multiple target documents.6. Select the target document where the split cargo is to be added, and then choose Split.

The selected containers (or packages) are moved from the source B/L to the target B/L.7. If necessary, adjust the data in the target B/L.8. Save the B/L.

Related Information

Bill of Lading Split [page 312]Splitting to an Existing B/L [page 314]

5.2.13.2 Splitting to an Existing B/L

Split the cargo from a source bill of lading (B/L) into another existing B/L using the Split tab on the Bill of Lading screen.

Prerequisites

● The source B/L has been created.● The target B/L has been created.● The following data is identical in the source B/L and the target B/L:

○ Parties (shipper, consignee, notify party, and so on)○ Location data (origin, load, discharge, destination, and issuing location/port)○ Forwarding agreement number○ First maritime leg

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading , and then open the source B/L.

2. On the Split tab, specify a reason for the split and enter any remarks that you want to record.3. If you are performing a cargo description split, in the Cargo Description table, select the cargo to be split as

follows:


Documentation

○ For a full cargo description split, select the corresponding line to be split.○ For a partial cargo description split, select the corresponding line to be split and specify the number of

split packages in the Split Outer Number of Packages field.4. If you are performing an items split, in the item hierarchy table, select the cargo to be split as follows:

○ For a full container split, select the containers to be split.○ For a partial container split, select the line to be split and specify the number of packages to be split in

the Split Number of Packages field.

5. In the Split Documents screen area, choose Add Existing .

The system displays a dialog box where you can search for and select the target B/L.6. Specify the target B/L and confirm your entry.

The target document is added to the table below. If required, you can add multiple target documents.7. Select the target document where the split cargo is to be added, and then choose Split.

The selected containers (or packages) are moved from the source B/L to the target B/L.8. If necessary, adjust the data in the target B/L.9. Save the B/L.

Related Information

Bill of Lading Split [page 312]Splitting to a New B/L [page 313]

5.2.14 Merging Bills of Lading

Consolidate all of the items from selected B/Ls into one master B/L.

Prerequisites

● The master B/L and all of the B/Ls to be merged into it exist.● The following data is identical in the master B/L and all of the B/Ls to be merged:

○ Parties (shipper, consignee, notify party, and so on)○ Location data (origin, load, discharge, destination, and issuing location or port)○ Forwarding agreement number○ First maritime leg


Context

During the merging process, the system checks that the B/Ls you have selected to merge adhere to the relevant restrictions. You can merge B/Ls with containerized cargo and non-containerized cargo (for example, break bulk). You can also merge B/Ls by processing shipping instructions of the class merge. After the merging process, all of the B/Ls except the master one have no items, have the life cycle status Void, and are not editable.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading , and then open the B/L that you want to be the master B/L.

2. In the toolbar, choose Merge B/L.

The system displays a dialog box where you can enter the B/Ls that you want to merge.3. Enter a reason code and any additional remarks that you would like to record.4. Choose Add to specify the B/Ls that you would like to merge, and then confirm your entries.

The system checks that the B/Ls you have specified adhere to the relevant restrictions for merging, and displays an error message if the restrictions are not met.

5. Save the B/L.

Results

● All of the items from the merged B/Ls are moved to the master B/L.● The life cycle status of all of the merged B/Ls is Void.● The merged B/Ls are not editable.● The details of the related merged and master B/Ls are displayed on the Document Flow tab.

Related Information

Merge Shipping Instructions [page 267]

5.2.15 Short Shipments

Short shipment occurs when part of the cargo (some items) that is listed on a bill of lading (B/L), and is intended to be loaded, is not loaded onto the vessel due to an operational reason.

In the event of a short shipment, a memo B/L is generated for the short-shipped units of cargo and is linked to the original B/L on the Document Flow tab. As a result of the short shipment, the items remain on the original


Documentation

B/L with their Short-Shipped checkboxes selected, and the corresponding transportation units are moved to the memo B/L. The following figure shows the relationship between the B/L line items and the transportation units (containers) before and after a short shipment:

Transportation Unit Assignment for Short Shipment

Related Information

Handling Short Shipments [page 318]


5.2.15.1 Handling Short Shipments

Select containers and flag them as short-shipped in the Bill of Lading screen. The system creates a memo B/L for the relevant transportation units.

Prerequisites

● The B/L contains more than one item and some of the items are operationally short-shipped.● The reasons for short shipment have been configured in the reason category SHSHIP in Customizing for

SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill of Lading Define Activity Log Objects .

Procedure


2. On the Short Shipment tab, specify a reason for the short shipment and enter any relevant remarks if necessary.

3. Select the short-shipped containers and then choose Short Shipment.

The system adds a new memo B/L for the selected containers.

NoteIf there are multiple short-shipped containers for the current B/L, you can assign them to different memo B/Ls depending on the operational situation.

4. Save the B/L.

Results

● A new memo B/L is created and is visible on the Short Shipment tab, on the Document Flow tab, and in the Items table.

● The new memo B/L contains the short-shipped items with the relevant transportation units, or freight units, or both.

● The source and destination locations in the memo B/L are defaulted from the original B/L.● The line items for the short-shipped containers remain in the original B/L, but the corresponding

transportation units are no longer assigned to it.● In the original B/L, the line items have the Short-Shipped checkbox selected and contain a reference to the

corresponding memo B/L.


Documentation

5.2.16 Hitchment Bills of Lading

A hitchment bill of lading (B/L) is used when two or more portions of one shipment originate at different locations and move under one B/L from one shipper to one consignee.

A hitchment B/L usually consists of hitchment revenue and one or more hitchment memos. The hitchment revenue portion usually covers the majority of a divided shipment and carries the entire revenue. The system allows you to add multiple hitchment memos to one hitchment revenue. You can view the related B/Ls on the Document Flow tab and on the Related Documents tab in the Bill of Lading screen.

Related Information

Adding Hitchment Bills of Lading [page 319]

5.2.16.1 Adding Hitchment Bills of Lading

Add a bill of lading (B/L) to another B/L as a hitchment B/L on the Related Documents tab in the Bill of Lading (B/L) screen.

Prerequisites

The B/Ls have the same document type, shipper, consignee, and destination location.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading , and then open the B/L that is to be used as the hitchment revenue B/L.

2. On the Related Documents tab, choose Add Hitchment Memo B/L .

The system displays a dialog box, where you can specify the relevant B/L.3. Specify the relevant B/L and confirm your entry.4. Save the B/L.

Results

● The hitchment memo B/L is visible on the Related Documents tab and on the Document Flow tab of the hitchment revenue B/L.


● The hitchment revenue B/L is visible on the Related Documents tab and on the Document Flow tab of the hitchment memo B/L

● Both the hitchment memo and the hitchment revenue B/L sub-type are changed to Hitchment.● The hitchment memo B/L type is changed to Memo Bill of Lading.

5.2.17 Memo Bills of Lading

A memo bill of lading (B/L) is a non-negotiable, non-transferable, unfreighted B/L that is only used as a receipt of goods and does not classify as a document of title. The system automatically generates memo B/Ls for certain scenarios such as short shipment. You can also manually create memo B/Ls.

Overview

Forwarding order types can be configured as relevant for memo B/Ls in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation BookingSettings for Booking Type Define Basic Settings for Booking Document Type . Any B/Ls that you create for such forwarding order types are handled by the system as memo B/Ls.

Memo B/Ls differ from regular B/Ls as follows:

● Not relevant for draft B/L approval● Not relevant for charge calculation● Not relevant for invoicing● Cannot be released● Cannot be surrendered (documentation status is not relevant)● Can be merged only with other memo B/Ls (except in the short shipment scenario) or split to existing

memo B/Ls

A memo B/L can be issued in several specific business scenarios such as the following:

● Short Shipment● Hitchment● Flat Rack● For seals, stationary, ship spares, empty containers, returned cargo, and so on

Memo B/L for Short Shipment

In the case of a short shipment, the system generates a memo B/L for the short-shipped units of cargo and links it to the original B/L on the Document Flow tab. It is possible to indicate which booking types are used for short shipment memo B/Ls in the configuration settings for original booking type in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation

Booking Settings for Booking Type Define Basic Settings for Booking Document Type (see the Type


Documentation

Memo B/L field). The short shipment memo B/L contains the short-shipped line items and the related transportation units, or the freight units, or both.

Memo B/L for Hitchment

Hitchment memo B/Ls are used to cover portions of one shipment that originate at different locations and move under one B/L (hitchment revenue) from one shipper to one consignee.

Memo B/L for Flat Rack

If a booking has a break bulk cargo item, you can create another booking for the flat rack equipment that is used for the carrier's convenience. When you create a flat rack booking, the system automatically creates a memo B/L for it.

Other Memo B/L Scenarios

You can also create memo B/Ls without a reference to other bookings or B/Ls, for example, for shipping ship spares, empty containers, or returned cargo.

Related Information

Short Shipments [page 316]Hitchment Bills of Lading [page 319]Flat Rack Bookings [page 184]Creating Memo B/Ls [page 322]


5.2.17.1 Creating Memo B/Ls

Create a memo bill of lading (B/L) without any reference to a booking or another B/L, for example, for shipping ship spares, empty containers, or returned cargo.

Prerequisites

At least one booking type has been configured as a memo B/L in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation BookingSettings for Booking Type Define Basic Settings for Booking Document Type .

Context

A memo B/L is a non-negotiable, non-transferable, unfreighted B/L that is only used as a receipt of goods.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Create Bill of Lading .2. On the initial screen, select the Memo Bill of Lading checkbox, specify the Forwarding Order Type, and then

choose Continue.3. Enter the mandatory information such as the general data, the cargo items, the route, and so on.4. Save the B/L.

Results

● A new memo B/L is created and assigned to the manifest.● The Draft B/L Status is Not Required.● The Documentation Status is Not Required.● The Release button is disabled.


Documentation

5.2.18 House Bills of Lading

A house bill of lading (HBL) is issued to a customer by a non-vessel operating common carrier (NVOCC) or a freight forwarder. In turn, the master bill of lading is issued to the NVOCC or freight forwarder by the shipping line (carrier). Multiple HBLs can be created for a master bill of lading.

HBL items can be assigned to either container or package level items of a master bill of lading. You can control this option using the HBL Assignment field on the General Data tab of the master bill of lading. You can create HBLs in the following ways:

● Automatic HBLsAutomatic HBLs do not contain any data and are linked directly to the relevant item in the master bill of lading.

● Manual HBLsManual HBLs are linked to a master bill of lading. However, they also contain their own header data and items that can be linked to the items in the master bill of lading. If you specify the HBL assignment level as Package, you cannot create a HBL with items linked to packages from different containers in the master bill of lading.

Related Information

Creating House B/Ls Automatically [page 323]Creating House B/Ls Manually [page 324]

5.2.18.1 Creating House B/Ls Automatically

Create house bills of lading (HBLs) automatically for either containers or packages in a master bill of lading.

Prerequisites

In the master bill of lading, on the General Data tab, you have specified the HBL Type as Automatic.

Context

Automatic HBLs do not contain any data and are linked directly to the relevant item in the master bill of lading.


Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading , and open the master bill of lading.

2. In the Items section, select either a container or a package depending on the HBL Assignment level you have specified on the General Data tab.

3. On the House Bill of Lading tab, enter the HBL number.4. Save your entries.

Related Information

House Bills of Lading [page 323]Creating House B/Ls Manually [page 324]

5.2.18.2 Creating House B/Ls Manually

Create house bills of lading (HBLs) manually for either containers or packages in a master bill of lading.

Prerequisites

In the master bill of lading, on the General Data tab, you have specified the HBL Type as Manual.

Context

Manual HBLs have their own header data and items, which you can link to the items in the master bill of lading.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading , and then open the master bill of lading.

2. On the House Bill of Lading tab, choose Create.3. Specify the HBL number, the receipt and delivery modes, the destination location, and the parties (shipper,

consignee, and notify party).4. Enter the cargo description and the relevant items for the HBL.


Documentation

5. To link the items in the HBL to the items in the master bill of lading, enter the BL Item ID.6. Save your entries.

Related Information

House Bills of Lading [page 323]Creating House B/Ls Automatically [page 323]

5.2.19 Canceling Bills of Lading

You can cancel a bill of lading (B/L) manually. The system determines whether it is possible to cancel the B/L. If the cancellation is allowed, the system sets the life cycle status to Canceled. If follow-up actions are required first, the life cycle status is set to Pending Cancellation.

Prerequisites

● You have created a B/L.● The cargo has not been loaded on the export vessel.● The reason codes for B/L cancellation have been defined under the reason category CANCEL in

Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Bill Of Lading Define Activity Log Objects.

Context

You cannot cancel a B/L when the cargo has been loaded on the export vessel. If a B/L has been created, then the cancellation cannot be triggered from the Booking screen.

Procedure


2. In the toolbar, choose Cancel.

The system displays a dialog box.3. Specify the reason code, enter the reason text, and then confirm your entries.


The B/L is either canceled right away, or if any of the following conditions apply, it is set to the status Pending Cancellation:○ The containers have been released from the empty depot. That is, the empty container release status

is either Partially Released or Fully Released.○ The cargo receipt mode is set as Door.○ The invoice status on one of the charge lines is set to Sent to CI, Received in CI, or Invoiced in CI.

Next Steps

If the B/L is saved in the status Pending Cancellation, it will be fully canceled when it is saved again if both of the following conditions apply:

● All empty containers are returned to the depot. That is, the empty container return status is either Not Required or Fully Returned.

● The export financial status is Cleared, Authorized, or Not Required.

5.2.20 Reactivating Canceled Bills of Lading

Reuse the ID of a canceled bill of lading (B/L) by reactivating the canceled B/L.

Prerequisites

The B/L has been canceled.

Context

The reactivated B/L is independent from the originally canceled one, and new TUs/FUs are created for it. You can generate new routes and assign the B/L to new manifests.

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Bill of Lading Change Bill of Lading , and open the canceled B/L.

2. In the toolbar, choose Reactivate B/L.


Documentation

5.2.21 Bill of Lading Clauses

Bill of lading clauses are standard texts used in a bill of lading. Clause texts can be preconfigured in the system, and there's also an option to add a one-time free text clause in the bill of lading.

Clauses can be customized as:

● Mandatory: Such clauses appear in the bill of lading by default without an option to remove them.● Changeable: The original clause text is derived from Customizing but it can be changed for the individual

bill of lading.

Examples of clauses include:

Clause What the Shipping Liner Is Confirming

Shippers Load, Stow, and Count (SLAC) The shipper has loaded, stowed, and counted the contents.

Said to Contain (STC) Based on the shipper’s declaration, the container is said to contain XYZ cargo but the contents has not been verified. It is the shipper’s responsibility to ensure that it declares the actual and correct cargo loaded onto the container.

Shipped on Board The container has been loaded on board the ship specified in the bill of lading.

Received for Shipment The container has been received and is being prepared for shipment on a nominated vessel.

Freight Prepaid The freight for the carriage of the cargo has been paid for at the port of origin.

Freight Collect The freight for the carriage of the cargo must be paid at the port of destination.

Freight Payable at location XYZ The freight for the carriage of the cargo must be paid at a specified location.

Related Information

Adding Clauses to Bills of Lading [page 328]


5.2.21.1 Adding Clauses to Bills of Lading

Add a clause to a bill of lading in order to use a standard text in a bill of lading.

Prerequisites

● The predefined clause texts have been maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill of Lading Define Clauses .

● The text types for manual clauses have been maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill of Lading Define Extended Settings for Text Type .

Procedure

1. In SAP NetWeaver Business Client, open the relevant bill of lading and choose the Print Option tab.2. In the Clauses section, proceed as follows:

Option What To Do

To add a predefined clause Choose Add Customized Clause and select the clauses you require.

To add a free-text clause Choose Add Manual Clause .


Results

You have added clauses to the bill of lading.

Related Information

Changing Clauses in Bills of Lading [page 329]Deleting Clauses from Bills of Lading [page 330]Bill of Lading Clauses [page 327]


Documentation

5.2.21.2 Changing Clauses in Bills of Lading

Change a clause in a specific bill of lading to meet your requirements.

Prerequisites

● The clause text has been defined as changeable in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill of Lading Define

Clauses .● The text types for manual clauses have been maintained in Customizing for SAP Transportation

Management under Container Shipping Liners Order to Cash Booking and Documentation Bill of Lading Extended Settings for Text Type .

Procedure

1. In SAP NetWeaver Business Client, open the relevant bill of lading and choose the Print Option tab.2. In the Clauses section, select the clause you want to change and enter the necessary text in the box under

the list of clauses.3. Save your changes.

Results

You have changed the relevant clause in the bill of lading.

Related Information

Deleting Clauses from Bills of Lading [page 330]Bill of Lading Clauses [page 327]


5.2.21.3 Deleting Clauses from Bills of Lading

Delete a clause from a bill of lading if it is no longer required.

Prerequisites

The clause text has been defined as changeable in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Bill of Lading Define

Clauses .

Procedure

1. In SAP NetWeaver Business Client, open the relevant bill of lading and choose the Print Option tab.2. In the Clauses section, select the relevant clause and choose Delete.3. Save your changes.

Results

You have deleted the relevant clause from the bill of lading.

Related Information

Bill of Lading Clauses [page 327]Adding Clauses to Bills of Lading [page 328]

5.3 Manifest

A manifest is a special type of ocean freight booking that is used for executing and tracking manifest-related activities. A manifest ocean freight booking is unique for a specific vessel and voyage combination.

Validation mechanisms are used to prevent creation of a duplicate manifest for the same vessel and voyage combination. An additional manifest submission page with manifest information is provided in the system.


Documentation

Related Information

Creation of Manifests [page 331]

5.3.1 Creation of Manifests

The creation of manifest ocean freight bookings is required in the system before the first booking is saved for the respective vessel and voyage combination.

All of the manifest information, including documents and their activities, is generated when the manifest ocean freight booking is created (or updated) and immediately available on the manifest submission page.

Related Information

Creating Manifests [page 331]Performing Mass Creation of Manifests [page 332]

5.3.1.1 Creating Manifests

Create a manifest ocean freight booking before the first booking is saved for the respective vessel and voyage combination.

Prerequisites

● The freight booking type has been defined in Customizing for SAP Transportation Management under Transportation Management Freight Order Management Freight Booking Define Freight Booking

Types .● The document type for manifests has been defined in Customizing for SAP Transportation Management

under Container Shipping Liners Order to Cash Booking and Documentation Manifest Maintain Manifest Settings .

Procedure

1. In SAP NetWeaver Business Client, choose Manifest Create Manifest .2. On the standard Freight Booking page, go to the Stages tab.


3. Enter all the itinerary details including locations and expected arrival and departure times.4. Choose Save.

Results

You have created the manifest ocean freight booking. The documentation schedule is calculated automatically.

NoteIf any changes are made to the vessel itinerary (port omissions, delays, and so on), these changes have to be entered manually in the details of the freight booking stages. The changes are then, automatically reflected in the documentation schedule.

5.3.1.2 Performing Mass Creation of Manifests

Perform mass creation of manifest ocean freight bookings from CSV files when you want to create independent manifests that are not linked to SAP Transportation Management schedules.

Prerequisites

● The freight booking type has been defined in Customizing for SAP Transportation Management under Transportation Management Freight Order Management Freight Booking Define Freight Booking

Types .● The document type for manifests has been defined in Customizing for SAP Transportation Management

under Container Shipping Liners Order to Cash Booking and Documentation Manifest Maintain Manifest Settings .

Procedure

1. Start transaction SE38.

2. Run report /TMCSL/TOR_CREATE_MASS, which generates multiple manifest ocean freight bookings based on the selection parameters and stages file.

NoteFor more information, see the associated report documentation in the system.


Documentation

Results

Multiple manifest ocean freight bookings are created. The documentation schedule is calculated automatically based on the manifest profile settings and vessel itinerary.

NoteIf any changes are made to the vessel itinerary (port omissions, delays, and so on), these changes have to be entered manually in the details of the freight booking stages. The changes are then reflected in the documentation schedule automatically.

5.3.2 Manifest Locations

Manifest locations are derived from the ocean freight booking stages along with the correct sequence number, actual and planned arrival and departure times, and certain location details.

Any changes in the ocean freight booking stages (including port omission, changes in planning time, actual arrival, and so on) are immediately reflected in the manifest locations.

If the port has been omitted from an ocean freight booking stage, but the manifest document has already been sent to the respective authority, the stage is deleted from the ocean freight booking. However, the manifest location is only marked as omitted and disabled, but still remains. All the information submitted is still available on the Manifest Submission page.

Related Information

Manifest [page 330]

5.3.2.1 Determination of Location Profiles for Manifest

Further details of Manifest locations are derived from the location profile of corresponding port attributes such as Customs Union and Sea Duration. These are described below:

● Customs Union is derived and used to determine the First Port of Entry.● Sea Duration is determined based on the following two locations:

○ Source from where the manifest document is sent○ Destination at which the manifest document is received


The following figure depicts the logic to determine the Sea Duration Type:

Determination of Sea Duration Type

As shown above, the system uses the following logic to determine the Sea Duration Type:

1. Check Short Sea Grouping: If source and destination are in the same Short Sea Grouping, then the result is Short; else go to Step 2.

2. Check Exceptions: If source is maintained in Short/Deep Sea Exceptions of the destination location profile, then the result is derived from the exception value (either Short or Deep); else go to Step 3.


Documentation

3. Compare Durations: If Short Sea Duration is maintained in the destination location profile, for example, 12 hours, then it acts as a range. Accordingly, if the expected duration from source to destination is within this range, then the result is Short, else it is Deep. However, if Short Sea Duration is not maintained in the destination location profile, then go to Step 4.

4. Check Short Sea When Coming From: If source location group is maintained in Short Sea When Coming From of the destination location profile, then the result is Short, else the result is Not Defined.

Related Information

Manifest [page 330]Partner and Location Profiles [page 51]

5.3.3 Determination of Business Partners and Profiles for Manifests

Determination of default business partners and profiles in generated manifests is an automatic process performed by the system.

The determination process is as follows:

1. The system reads the business partner from the location profile of the respective location, for each business partner role that has been defined in the Customizing settings for the role grouping. If the default value is incorrect, you can subsequently change the business partner in the manifest.

2. For each business partner, the system then automatically determines the manifest profiles assigned to the partners in the profiles for each business partner role.

Related Information

Setting Up Business Partner and Profile Determination [page 336]Local Voyage References [page 337]


5.3.3.1 Setting Up Business Partner and Profile Determination

Set up business partner and profile determination to enable default business partners and profiles to be determined for manifests.

Prerequisites

● The BP roles relevant for manifesting (such as Terminal, Operator, Customs, and so) have been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Manifest Define BP Roles .

● The BP role grouping containing all the manifest BP roles has been defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Manifest Define BP Role Groupings .

● The BP role grouping has been defined as manifest relevant in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and DocumentationManifest Maintain Manifest Settings .

Procedure

1. In SAP NetWeaver Business Client, choose Master Data Partner and Location Profile Change Profile and then open the relevant location profile.

2. On the Manifest tab, assign the business partners to the manifest roles in the location profile.

For example, assign the ID of the Customs BP to the Customs Office manifest role in the location profile of the specific location.

3. Open the relevant partner profile.4. In the Manifest Profile Assignment table, assign manifest profiles to the manifest roles of the partner.

For example, if the same organization works as customs and terminal operator, you would assign two different profiles to this partner to reflect each role.


Results

When the manifest is generated, the system reads all of the above settings, and the default business partners and manifest profiles for all of the locations. As mentioned above, the default business partner can be changed in the manifest, if required.


Documentation

NoteIf vessel itinerary is changed (and thus also the details of the standard freight booking stages), the system once again executes the business partner and profiles determination. However, if at least one document was submitted for the specific business partner, the business partner is locked and not updated. The same applies to the business partners changed manually.

Related Information

Determination of Business Partners and Profiles for Manifests [page 335]

5.3.3.2 Local Voyage References

For all roles on the Manifest BP tab where the business partner was automatically found by the system or entered manually, you can manually specify export and import local voyage references that are relevant for this business partner.

To validate this input, a Business Add-In is available, which can be found in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Business-Add Ins (BAdIs) BAdI: Manifest Objects . For example, the business partner may have its own voyage numbering or assign certain IDs to the manifest correspondence. These references could later be used in the submissions, for example, if the recipient requires this reference number for identification purposes.

Related Information

Determination of Business Partners and Profiles for Manifests [page 335]

5.3.4 Additional Location Characteristics

Additional location characteristics are fields that you can add to the manifest for each location.

The system allows you to add up to five fields each for the following field types:

● Character● Timestamp● Quantity● Unit of measure

Additional location characteristics are hidden in the manifest by default and so are not used. However, you can configure such additional fields to be visible by making the necessary settings in Customizing and in the location profile. You can also specify whether the fields are mandatory or read-only.


Related Information

Configuring Additional Location Characteristics [page 338]

5.3.4.1 Configuring Additional Location Characteristics

To make additional location characteristics visible in the manifest, configure the necessary settings in Customizing and in the location profile.

Procedure

1. In Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBooking and Documentation Booking Profile Settings Maintain Dynamic Profiles for Field Attributes , make the following settings:1. Define the dynamic attribute profile.2. Select the profile type as Manifest Location.3. Define the field attributes:

○ Technical Field○ Label○ Visible○ Read-Only○ Mandatory

NoteYou can add up to five fields each for the following field types: character, timestamp, quantity, and unit of measure.

2. In SAP NetWeaver Business Client, choose Master Data Partner and Location Profile Change Profile and open the relevant location profile of the respective port.

3. In the Additional Location Characteristics group box, enter the dynamic profile in the Dynamic Attribute Profile field.

Results

The fields are available in the manifest on the Additional Location Characteristics tab.


Documentation

Related Information

Additional Location Characteristics [page 337]

5.3.5 Manifest Document Generation

A manifest document is the standalone instance of the profile document generated for a particular Vessel Voyage Port Call (VVPC). It is required for submission during the voyage lifecycle.

Manifest documents are generated when manifest ocean freight bookings are created. For each manifest business partner, the system determines the manifest profile from the partner profile of this business partner. The system then creates an instance of all the documents valid at the estimated time of arrival (ETA) or departure (ETD) of the current port. The ETA or ETD is chosen based on the Reference Validity document setting in the manifest profile. The number of document instances generated is controlled by the event reference class assigned to the corresponding document in the manifest profile.

If a manifest profile is later changed, document instances already created in manifest ocean freight bookings are updated (deleted) if they have not yet been submitted, while those documents already submitted remain unchanged.

Related Information

Reference Validity [page 28]Event Reference [page 27]

5.3.6 Manifest Document Activities

Manifest document activities are the actions that need to be executed for a particular manifest document at a specific point in time. For each activity, a Post Processing Framework (PPF) trigger is scheduled (which is displayed on the Output Management tab).

When the manifest ocean booking is created, activities are executed for all active documents based on the manifest profile settings and PPF settings. Once activities are executed, their status and other details are updated and displayed on the Activity tab, and the activities are assigned a reference ID, which can be used for response processing or auditing purposes on the Tracking tab.

Related Information

Executing Activities for Manifest Documents Manually [page 340]


5.3.6.1 Execution of Manifest Document Activities

Manifest document activities, each having a Post Processing Framework (PPF) trigger, can be executed either manually from the manifest maintenance screen or automatically by report RSPPFPROCESS.

In the case of the report RSPPFPROCESS, which is scheduled in the background, the start condition of the PPF action must be fulfilled, which in most cases, is the passing of a specific date. However, any other behavior can be implemented in the custom implementation of the PPF agent class. Alternatively, the report /TMCSL/R_PPF_EXECUTE_MANIFEST can be used for activity execution and does not require any PPF-based input.

Related Information

Executing Activities for Manifest Documents Manually [page 340]Activities [page 34]

5.3.6.1.1 Executing Activities for Manifest Documents Manually

Execute manifest document activities manually for those activities that cannot be scheduled for a particular reason. You can also interrupt or overwrite the automatically executed activities by executing them again manually. You can do this either on the Activity tab or BL/Booking tab in the manifest ocean booking.

Prerequisites

Manifest documents have been generated.

Procedure

1. In SAP NetWeaver Business Client, choose Manifest Change Manifest .2. Specify the ID of the manifest containing the manifest documents for which you want to execute activities.3. Under Document Details, choose the BL/Booking tab.4. Then proceed as follows:

Option Description

If you want to execute all activities Choose Apply All

If you want to execute selected activities Choose Apply Selected


Documentation

5. Save the manifest.

Results

All or the selected bookings or bills of lading are passed to the Post Processing Framework (PPF) agent class, where they are processed as per document requirements. Default processing is proposed in the provided example agent implemented class.

Related Information

Manifest Document Activities [page 339]

5.3.7 Manifest Document Cleanup

Manifest document cleanup is the process of validating documents before they are sent to a port authority. The cleanup process is important, especially since some authorities may fine the carrier for incorrect or incomplete filing.

To allow time for additional information to be requested from customers, the cleanup process is scheduled before submission of documents. In the system, the cleanup is executed as a normal document activity, which must first be created in the manifest profile for the respective document along with the validations assigned to this document.

Once the validation process is complete, the cleanup status of the document is set, and the result is saved in the application log, which is then displayed on the Cleanup tab in the manifest ocean booking. The cleanup ID in the log corresponds to the log number. You can also check this ID in the Application Log Analyzer in the back-end system by starting transaction SLG1 and specifying object /TMCSL/MANIFEST and subobject /TMCSL/CLEANUP. This is the default behavior, which can be overwritten in a custom implementation of the Post Processing Framework agent class.

Details of cleanup execution are displayed on the Tracking tab in the manifest ocean booking along with a list of the bills of lading validated during the cleanup.

Related Information

Manifest Document Submission [page 342]Manifest Document Activities [page 339]Validations [page 42]


5.3.8 Manifest Document Submission

Manifest document submission is the process of sending manifest information to the requesting authority, which is represented in the manifest as a business partner.

Submission is executed as a normal document activity generated in the manifest freight booking based on the manifest profile, but it sets the submission status of the document. This is the default behavior, which can be overwritten in a custom implementation of the Post Processing Framework agent class.

Details of submission are displayed on the Tracking tab in the manifest ocean booking, along with the list of the bills of lading that were sent during submission.

Related Information

Manifest Document Activities [page 339]

5.3.8.1 Manifest Information Tab in Bills of Lading

A manifest document for a particular authority may require new or different information compared with the original bill of lading information. In this case, a different shipper, notify party, consignee, ship-to party, export references, and other information can be entered on the Manifest Information tab.

The information from this tab can then be used for filing to the specific authorities.

Related Information

Bills of Lading [page 273]

5.3.9 Bookings and Bills of Lading in Manifest Documents

All the bookings and bills of lading that passed the trigger rules and were included in the respective manifest document are listed on the BL/Bookings tab in the Document Details section of the manifest ocean booking

For each of the manifest documents, the following details are provided:

● Submission statuses: an overview of the current state of the bills of lading within a particular document● Response statuses: the status of responses from authorities● Cargo details: all the cargo (containers, packages, and so on) belonging to the selected bill of lading● Filing reference history: all the IDs assigned by the authorities to the respective bill of lading and received

from them (authorities) as a response to the submission


Documentation

Related Information

Submission Statuses [page 343]Manifest Responses [page 346]Manifest Response Statuses [page 347]

5.3.9.1 Submission Statuses

Bills of ladings (B/L) within a particular manifest document can have various submission statuses.

An overview of these statuses is provided in the following table:

Status Description

Submission status Shows whether the B/L has already been submitted. This status should be updated after each submission from the corresponding PPF action (API provided).

Cleanup status Shows whether the B/L has already been validated, and if yes – the outcome of this validation. This status should be updated after each cleanup from the corresponding PPF action (API provided).

Amendment status Shows whether an important B/L attribute was changed or a B/L was added or removed after already being included in the submission. This status can be Critical or Not Critical, which may change the timeline and content for the next amendment submission of the document.

Amendment operation Shows why an amendment is required, for example, an important attribute of the B/L was changed, or the B/L itself was created or canceled after submission to the authority.

Related Information

Bookings and Bills of Lading in Manifest Documents [page 342]


5.3.9.2 Adding Bills of Lading to Manifest Documents Manually

Add a bill of lading (B/L) or booking to a manifest document manually if it did not pass the trigger rule for inclusion in document submission.

Context

Consider a Military declaration document that has a trigger rule defining that only Military bookings are relevant. In such as case, if you want to include Commercial bookings, you would have to add them manually. This is because commercial bookings assigned to the voyage and manifest would not pass the trigger rule and therefore would not be automatically included in the document

Procedure

1. In SAP NetWeaver Business Client, choose Manifest Change Manifest .2. Specify the ID of the manifest containing the manifest documents for which the B/Ls are to be included.3. Under Document Details, choose the BL/Bookings tab.4. Select the B/L you want to add and choose Add B/L.5. Save your changes.

Results

You have added the selected B/Ls to the manifest documents.

Related Information

Removing Bills of Lading from Manifest Documents Manually [page 345]


Documentation

5.3.9.3 Removing Bills of Lading from Manifest Documents Manually

Remove a bill of lading or booking from manifest document submission manually if it was added to the particular manifest (voyage) by mistake.

Procedure

1. In SAP NetWeaver Business Client, choose Manifest Change Manifest .2. Specify the ID of the manifest containing the manifest documents for which the B/Ls are to be removed.3. Under Document Details, choose the BL/Bookings tab.4. Select the B/L you want to remove and choose Remove B/L.

NoteIf you remove a B/L by mistake, you can undo this action by choosing Undo Remove.

5. Save your changes.

Results

You have removed the selected B/Ls from the manifest document.

Related Information

Adding Bills of Lading to Manifest Documents Manually [page 344]

5.3.10 Manifest Document Tracking

Manifest document tracking is the process of recording the execution of all manifest activities, including submissions and cleanups. This is realized by a Post Processing Framework agent class that implements a special call at the end of the trigger execution.

The tracking information is shown in four group boxes in the manifest ocean booking:

● Submission: All of the activities executed, including the time of execution, activity type, and reference ID assigned, are listed here.

● Submission Details: The objects included in the selected activity, for example, the bills of lading validated or submitted, are listed here.


● Response: Any responses to the submission (responses are mapped to submissions by reference ID), including the execution status and the time when the response was received and saved in the system, are listed here.

● Response Details: All of the information about the selected response is listed here, including:○ Object for which the response was sent (such as document, B/L, container, and vessel)○ Response code received○ Status of execution of the response class assigned to this code○ Filing reference assigned to the object by the response sender

Related Information

Manifest Responses [page 346]Processing of Manifest Responses [page 347]Manifest Response Statuses [page 347]

5.3.11 Manifest Responses

Manifest responses for submitted manifests may be expected from authorities (for example, customs) based on the information in the manifest profile. Multiple types of responses can be received for a single manifest transmission, and are then processed based on manifest profile rules.

The response might acknowledge the submitted manifest, or reject it. The response action class then carries out the relevant action required, for example:

● Changes the submission status of the manifest document● Sets a specific response status for the manifest document, bill of lading, container, or event vessel (for

example, Do Not Load or Discharge)● Performs a specific action that is realized in the response action class assigned to the special response

code

Related Information

Processing of Manifest Responses [page 347]Responses [page 45]Manifest Document Submission [page 342]


Documentation

5.3.11.1 Manifest Response Statuses

The manifest response status for manifest documents can have the following values:

Status Description

On Hold The load, discharge, or release operation is on hold until a further response is received.

Cleared A hold response was cleared (canceled) by an authority by means of a Clear response.

Authorized Someone who is authorized to make such a decisions Cleared the hold from the authority.

No Response No response was received for the object.

Not Required A response for this status is not expected for the current document type according to the settings in Customizing for

SAP Transportation Management under Container

Shipping Liners Order to Cash Booking and

Documentation Manifest Maintain Manifest Settings .

Not Relevant

Related Information

Manifest Responses [page 346]Processing of Manifest Responses [page 347]

5.3.11.2 Processing of Manifest Responses

Manifest responses are processed by a special Application Programming Interface and can be received at four different levels: bill of lading, container, document, and Vessel Voyage Port Call (VVPC).

For example, an authority may put a load on hold for some containers, the complete bill of ladling, or even a full vessel (VVPC level).

The API groups the responses by response code and subsequently calls the response action classes assigned to this code in the manifest profile. It then saves the result of execution in the manifest, which later appears on the Tracking tab. The load, discharge, and release responses are processed at the level they are received and then aggregated to the upper level based on the default aggregation logic, which can be customized using the available BAdIs. The responses are also aggregated for individual bills of lading from different documents and ports, and the aggregated bill of lading status is displayed in the bill of lading on the Statuses tab.


For example, if at least one bill of lading is put on hold for load, then the whole document is put on hold for load, and even the whole vessel for this port. Once the issue is resolved and the status at bill of lading level is changed, for example, to Cleared, then the higher-level statuses at document and port level are also cleared.

Related Information

Responses [page 45]Manifest Response Statuses [page 347]Manifest Document Submission [page 342]

5.3.12 Assignment of Booking to Manifest

When a manifest ocean freight booking is confirmed, a booking is assigned to it. This assignment confirms the intention of the customer to ship the cargo, and reserves the capacity of the vessel.

Confirmation is done in two steps:

1. The corresponding manifest freight booking is found based on the vessel name and voyage number information indicated in each booking stage, and the manifest freight information is added to the stages. At this point, the manifest is not updated, but a background trigger TOR_UPDATE_FOLLOW_UP is created for update at a later time.

2. The background trigger created in the first step is executed asynchronously with report /SCMTMS/PROCESS_TRIGGER_BGD, which is scheduled as a periodic job, as described in SAP Note 1747234 . This updates the manifest ocean freight booking with new cargo items from the assigned booking, and the capacity is reserved accordingly.

Additionally, if changes are made to a stage (for example, the vessel or voyage is updated), the assignment logic is called again. The booking is then unassigned from the old manifest ocean freight booking and is assigned to the new one.

Related Information

Trigger Rules [page 29]

5.3.12.1 Changes to Assigned Booking

After the booking has been assigned to the manifest, the system executes the background logic of the manifest trigger rules check and amendment check every time the booking is saved.

If important booking attributes have been changed, it can lead to bookings being included in or excluded from the manifest documents. In such as case, the system checks all of the trigger rules of all documents of all manifest freight bookings to which the current booking is assigned, and pushes the changes to the manifest


Documentation

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/1747234

documents. If the manifest document has been submitted, but the booking is included or excluded afterwards, then the manifest document is assigned the amendment status Critical amendment required.

A similar check is performed with key attributes of the booking for those manifest documents that have already been submitted. If a key attribute is changed for submitted bookings, the amendment status of the corresponding manifest document changes to Required or Critical required, based on the criticality attribute of the key element in the manifest profile.

Related Information

Trigger Rules [page 29]Amendments [page 47]

5.3.13 Manifest Plan

The manifest plan is a list of all manifest documents per port and vessel containing this booking, along with scheduled and actual cleanup and submission dates, various statuses, and other information. Besides the planned and actual manifesting information, the filing history of the booking for the particular manifest document is also shown in the form of responses.

The manifest plan is created when the booking has been confirmed and assigned to the manifest ocean freight bookings, and the trigger rules for all the manifest documents have been checked. It is updated every time the booking is saved, based on the amended booking attributes.

Related Information

Manifest Document Cleanup [page 341]Manifest Document Submission [page 342]

5.4 Delivery Orders

A delivery order is import documentation ordering the release of cargo to another party after it has arrived at the port of delivery or the destination terminal.

The delivery order permits the direct delivery of cargo to a customer (consignee or freight owner) or to another party acting on behalf of the customer and in possession of the bill of lading.


Related Information

Creation of Delivery Orders [page 350]

5.4.1 Creation of Delivery Orders

A delivery order (DO) can be created for individual bills of lading, for individual containers within a bill of lading, and for individual items (mixed cargo) within a bill of lading. It is based on the standard freight order in SAP Transportation Management.

The different scenarios for creating delivery orders are summarized in the following table:

Scenario Description

Creation of DO at bill of lading level Creation of a delivery order for all containers, break bulk cargo, and roll-on roll-off cargo within a bill of lading

Creation of DO at container level Creation of a delivery order for individual or multiple containers within a bill of lading

Creation of DO for mixed cargo Creation of a delivery order for different types of items within a bill of lading:

● Containers● Roll-on roll-off cargo● Break bulk cargo

In addition, delivery orders can be created for individual or multiple containers based on the following:

● Common automatic house bill of lading number for all containers● Common manual house bill of lading number for all containers● Vessel voyage port call

Related Information

Bills of Lading [page 273]Creating Delivery Orders at Bill of Lading Level [page 351]Creating Delivery Orders at Container Level [page 352]Creating Delivery Orders for B/Ls with Automatic HBL Assignment [page 353]Creating Delivery Orders for B/Ls with Manual HBL Assignment [page 355]Creating Delivery Orders at Vessel Voyage Port Call Level [page 356]


Documentation

5.4.1.1 Creating Delivery Orders at Bill of Lading Level

Create a delivery order (DO) at bill of lading level when you want the delivery order to contain all containers, break bulk cargo, and roll-on roll-off cargo of the bill of lading.

Prerequisites

● The bill of lading exists with at least one of the following:○ Container○ Roll-on roll-off cargo item○ Break bulk cargo item.

● The freight order types have been configured in Customizing for SAP Transportation Management under Transportation Management Freight Order Management Freight Order Define Freight Order

Types .● The stage type for the delivery order has been defined in Customizing for SAP Transportation Management

under Transportation Management Forwarding Order Management Define Stage Types .● The transportation modes for stage types have been configured in Customizing for SAP Transportation

Management under Transportation Management Forwarding Order Management Define Allowed Transportation Modes for Stage Types .

● The stage type sequence has been defined in Customizing for SAP Transportation Management under Transportation Management Forwarding Order Management Define Stage Type Sequence for

Movement Types .● The document type assignment for stage types has been configured in Customizing for SAP Transportation

Management under Transportation Management Forwarding Order Management Forwarding OrderDefine Default Freight Document Types for Stages .

Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Change Bill of Lading .2. Specify the bill of lading number and choose Continue.3. In the Delivery Order group box on the General Data tab, enter the following data required for delivery order

creation:

○ PIN Number (if applicable) – number given by carrier or terminal for security reasons○ PIN Expiry Date (if applicable) – date when PIN number expires○ DO Expiry Date – date when DO expires

4. In the toolbar, choose Create DO.


Results

The delivery order is created and visible on the Document Flow tab in the bill of lading.

Related Information


5.4.1.2 Creating Delivery Orders at Container Level

Create a delivery order (DO) at container level for individual or multiple containers of a bill of lading.

Prerequisites

● The bill of lading exists with at least one container.● The freight order types have been configured in Customizing for SAP Transportation Management under

Transportation Management Freight Order Management Freight Order Define Freight Order Types .

● The stage type for the delivery order has been defined in Customizing for SAP Transportation Management under Transportation Management Forwarding Order Management Define Stage Types .

● The transportation modes for stage types have been configured in Customizing for SAP Transportation Management under Transportation Management Forwarding Order Management Define Allowed Transportation Modes for Stage Types .




Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Change Bill of Lading .2. Specify the bill of lading number and choose Continue.3. Go to Items group box and select single or multiple containers for which you want to create a delivery

order.


Documentation

4. In the Delivery Order Information group box, specify the following data required for delivery order creation:

○ PIN Number (if applicable): number given by carrier or terminal for security reasons○ PIN Expiry Date (if applicable): date when PIN number will expire○ DO Expiry Date: date when DO will expire○ Last Free Date: last date after which additional penalties will be charged for container storage

5. In the Items tree toolbar, choose Merged DO for Selected Containers and select one the following options:

Option Description

Merged DO for Selected Container Creates one delivery order for the selected containers based on the latest deliver order information.

Individual DO for Selected Container Creates individual delivery orders for each container. In this case, the Delivery Order Information tab must be fil-led-in for each container.

Results

The delivery orders are created and visible on the Document Flow tab in the bill of lading.

Related Information


5.4.1.3 Creating Delivery Orders for B/Ls with Automatic HBL Assignment

Create delivery orders for individual or multiple containers of a bill of lading based on the common automatically assigned house bill of lading (HBL) for all containers.

Prerequisites

● The bill of lading exists with at least one container.● The HBL classification in the bill of lading is set to automatic HBL assignment at container level● The house bill of lading number is prefilled on the HBL tab of at least one container.● Freight order types have been configured in Customizing for SAP Transportation Management under








Procedure


order.4. In the Delivery Order Information group box, specify the data required for delivery order creation:

○ PIN Number (if applicable): number given by carrier or terminal for security reasons○ PIN Expiry Date (if applicable): date when PIN number will expire○ DO Expiry Date: date when DO will expire○ Last Free Date: last date after which additional penalties will be charged for container storage

5. In the Items tree toolbar, choose Merged DO for Selected Containers.6. Then select Create DO for HBL to create one delivery order for selected container and all containers with

the same HBL number.

Results

The delivery orders are created and visible on the Document Flow tab in the bill of lading.

Related Information



Documentation

5.4.1.4 Creating Delivery Orders for B/Ls with Manual HBL Assignment

Create delivery orders for individual or multiple containers of a bill of lading based on the common manually assigned house bill of lading (HBL) for all containers.

Prerequisites

● The bill of lading exists with at least one container.● The HBL classification in the bill of lading is set to manual HBL assignment at container level.● The HBLs have been created on the House Bill of Lading tab of the B/L, and items have been assigned to

the HBLs.● The freight order types have been configured in Customizing for SAP Transportation Management under







Procedure


order.4. In the Delivery Order Information group box, specify the following data for delivery order creation:

○ PIN Number (if applicable): number given by carrier or terminal for security reasons○ PIN Expiry Date (if applicable): date when PIN number will expire○ DO Expiry Date: date when DO expires○ Last Free Date: last date after which additional penalties will be charged for container storage

5. Choose the House Bill of Lading tab in the B/L header.


6. Select the house bill of lading for which you want to create delivery orders.7. Choose Create DO.

Results

The individual delivery orders are created for each HBL and include all containers assigned to this HBL. The delivery orders are visible on the Document Flow tab in the bill of lading.

Related Information


5.4.1.5 Creating Delivery Orders at Vessel Voyage Port Call Level

You can create delivery orders for a particular vessel voyage port call using a special Application Programming Interface (API) called within a report.

Context

Usually when a ship arrives at a port, delivery orders need to be created for all bills of lading that belong to one customer, and that need to be unloaded at the port.

Procedure

1. Start transaction SE38 and execute report /TMCSL/DO_MASS_CREATION.

2. On the initial screen, specify either the consignee ID or the delivery order numbers (or both).3. Execute the report.4. In the table of B/Ls, select the B/Ls and choose Create on VVPC.

Results

The report creates a delivery order for the selected B/Ls according to the required creation level of the delivery order, which is configured in the customer’s partner and location profile.


Documentation

Related Information

Bills of Lading [page 273]Partner and Location Profiles [page 51]

5.4.2 Mass Creation of Delivery Orders

A special Application Programming Interface (API) provides functionality for mass creation of delivery orders. It allows you to create delivery orders for one or more bills of lading (B/Ls) at the level you require.

Mass creation of delivery orders is possible at the following levels:

● Bill of lading● Container● Vessel voyage port call (VVPC)

The API is called using the report /TMCSL/DO_MASS_CREATION. For more information, see the associated report documentation in the system.

Related Information

Creating Delivery Orders at Vessel Voyage Port Call Level [page 356]

5.4.3 Creating Delivery Orders for Part-Load Bills of Lading

You can create a delivery order (DO) for part-load bills of lading (B/Ls). In a part-load scenario, the DO is created from the part-load B/L and not from the equipment booking.

Prerequisites

● An equipment booking exists with at least two part-load bills of lading.● The DO expiry date has been maintained in the equipment booking to ensure that multiple DOs for part-

load B/Ls that share one container have the same expiry date.

NoteThe DO expiry date, PIN, and PIN expiry date are not visible in the part-load B/Ls.

● The freight order types have been configured in Customizing for SAP Transportation Management under Transportation Management Freight Order Management Freight Order Define Freight Order

Types .







Procedure

1. In SAP NetWeaver Business Client, choose Bill of Lading Change Bill of Lading .2. Specify the bill of lading number of the part-load B/L and choose Continue.3. In the toolbar, choose Create DO.

Results

The delivery order is created and visible on the Document Flow tab in the part-load bill of lading.

Related Information


5.4.4 Canceling Delivery Orders

You can cancel a delivery order that was created by mistake, for the wrong consignee, or at the wrong level.

Prerequisites

The delivery order to be canceled exists.


Documentation

Procedure

1. In SAP NetWeaver Business Client, choose Delivery Change Delivery Order .2. Specify the number of the delivery order you want cancel and then choose Continue.3. Choose Cancel DO in the toolbar.4. In the dialog box that opens, choose OK.

Results

You have canceled the delivery order.

Related Information

Creation of Delivery Orders [page 350]Voiding Delivery Orders [page 359]

5.4.5 Voiding Delivery Orders

You can void a delivery order after it has been issued, for example, if the authority has instructed you to hold the deliver order or if the delivery order was wrongly issued. The cargo will not be shipped to the consignee if the DO is void.

Prerequisites

● The delivery order has been created, released, and issued.● The container pickup date on the bill of lading is blank.

Procedure

1. In SAP NetWeaver Business Client, choose Delivery Change Delivery Order .2. Specify the number of the delivery order you want to void and then choose Continue.3. Choose Void DO in the toolbar.4. In the confirmation dialog box, choose OK.


Results

You have voided the delivery order, but it is still linked to the bill of lading.

Related Information

Creation of Delivery Orders [page 350]

5.4.6 Delivery Order Statuses

The following tables list the different statuses that are relevant for delivery order (DO) processing, together with their possible status values.

DO Life Cycle Status

Status Status Description

Created The DO was created.

This status is independent of the bill of lading (B/L) cargo release status.

Released The DO was released.

The DO can be released when the B/L cargo release status is Released.

Canceled The DO was canceled.

Void The DO was voided.

This status can only be set after the DO has been issued.


Documentation

DO Issued Status


Issued The DO was issued.

Only released DOs can be issued by way of output management.

Not Issued The DO has not been issued.

When a DO is voided, its status changes from Issued to Not Issued.

Bill of Lading Cargo Release Status


Hold The B/L cargo is on hold.

This means at least one of the cargo release checks failed.

Released The B/L cargo was released.

This status is set after all of the cargo release checks have been passed successfully. If demurrage has been generated, the cargo release status is set to Released by the external system only after the customer has paid the demurrage. The cargo release status is displayed in the B/L.

Related Information

Delivery Order Status Dependencies [page 362]Delivery Order Processing [page 363]


5.4.6.1 Delivery Order Status Dependencies

The following table describes the different states in the delivery order (DO) process flow along with their associated status values:

State Description Cargo Release Status

DO Life Cycle Status DO Issued Status

1 ● Payment outstanding● Customs not cleared● Original bill of lading not surren

dered● Vessel not arrived

Hold Null (does not exist) Null (does not exist)

2 ● Payment outstanding● Customs not cleared● Original bill of lading not surren

dered● Vessel arrived

Hold Created Not Issued

3 ● Payment complete● Customs cleared● Original bill of lading surrendered● Vessel arrived● Additional data provided

Released Released Not Issued

4 ● Payment complete● Customs cleared● Original bill of lading surrendered● Vessel arrived● Additional data provided● DO issued to consignee,● Consignee collects cargo● Cargo pickup date updated on BL

Released Released Issued

5 ● Payment complete● Customs cleared● Original bill of lading surrendered● Vessel arrived● Additional data provided● DO issued to consignee● Consignee fails to collect con

tainer before DO expiry date● DO void

Hold Void Not Issued


Documentation

State Description Cargo Release Status

DO Life Cycle Status DO Issued Status

6 ● Payment complete● Customs cleared● Original bill of lading surrendered● Vessel arrived● Additional data provided● DO issued to consignee● Consignee fails to collect con

tainer before DO expiry date● Consignee pays demurrage, gets

new DO and new expiry date● Cargo collected; cargo pickup

date updated on bill of lading

Released Released Issued

Related Information

Delivery Order Statuses [page 360]

5.4.7 Delivery Order Processing

Delivery order (DO) processing and the corresponding status updates are described below:

1. A delivery order is created, resulting in the following statuses:○ The DO life cycle status is set to Created.○ The DO issued status is set to Not Issued.

NoteIf the bill of lading cargo has already been released at the time the DO is created, the DO life cycle status is set directly to Released.

2. The bill of lading cargo is released, after which the B/L cargo release status changes from Hold to Released.3. After release of the B/L cargo, the DO life cycle status changes from Created to Released.

NoteNote: This status change is triggered by an Application Programming Interface (API) that is called from within B/L processing.

4. The delivery order is sent out using standard output management. The DO issued status now changes from Not Issued to Issued.


NoteThis status change is triggered by an Application Programming Interface (API) that is called from within output management.

5. If the delivery order is subsequently voided, the statuses are updated as follows:○ The DO life cycle status changes from Released to Void.○ The B/L cargo release status changes from Released to Hold.○ The DO issued status changes from Issued to Not Issued.

6. The B/L cargo is then released again, resulting in the following status changes:○ The B/L cargo release status changes from Hold to Released.○ The DO life cycle status changes from Void to Released.

7. Finally, the delivery order is sent out again using standard output management, after which the DO issued status changes from Not Issued to Issued.

NoteThe DO issued status is set by the implementation team after output generation in the Post Processing Framework. The API only updates the status. The B/L cargo release status is read from the B/L, and is only displayed and not stored in the delivery order itself.

Related Information

Delivery Order Statuses [page 360]Delivery Order Status Dependencies [page 362]

5.4.8 Issuing of Delivery Orders

The sending or issuing or delivery orders (DOs) is the process of granting customers the right to receive the containers at the place of delivery.

A delivery order can only be issued if both the cargo release status in the bill of lading and the DO life cycle status are Released. After a DO is sent or issued, the DO issued status changes from Not Issued to Issued. This logic is part of the Application Programming Interface (API) /TMCSL/CL_DO_COMMON_HELPER=>API_SEND_DO, which updates the issued status of the document. The API may also trigger an output Post Processing Framework (PPF) action that is to be executed (which is part of the PPF setup).

The delivery order can be sent (issued) to the customer by e-mail or fax, or by hand as a printed copy. Delivery orders can be sent, printed, and e-mailed using the Generate button on the standard Output Management tab. Previewing of delivery orders is also handled by standard output management.


Documentation

Related Information

For more information about standard output management, see SAP Library for your SAP Transportation Management release on SAP Help Portal at https://help.sap.com/transportationmanagement. Under Application Help, open SAP Library, choose SAP Transportation Management (SAP TM) Basic Functionsor search for Output Management.

5.5 Release Orders

A release order is a document that is sent to the depot to instruct the depot to release containers. Empty provisioning transportation units (TUs) can be assigned to the release order, whereby an empty provisioning TU can be linked to only one active release order.

NoteThe release order does not serve as a purchase document to order the services from the depot. Furthermore, other functionality such as charge calculation or invoicing cannot be carried out from the release order.

Related Information

Release Order Validation [page 366]Determination of Release Order Amendment or Creation [page 366]Validation of Empty Provisioning Locations [page 367]Creating Release Orders at Booking Level [page 368]Creating Release Orders at TU Level [page 369]Release Order Status [page 370]Release Order Cancellation [page 373]Release Order Expiration [page 373]Issuing Release Orders [page 375]Creation of Release Orders for Merged Bookings [page 376]Creation of Release Orders for Split Bookings [page 377]Release Orders for Carrier Haulage [page 378]Using the Release Order Worklist [page 379]Keep Determined Depot Indicator [page 380]



5.5.1 Release Order Validation

Release order validation refers to the logic and rules that apply when release orders are created.

Release order validation comprises the following logic:

● Individual release orders are created for each booking. One release order only holds containers from one booking.

● For one booking, multiple release orders can be created. For example, if there are multiple release locations or if release orders are created at transportation unit (TU) level.

● When release orders are created and subsequently assigned TUs, a provisioning TU can only be assigned if it is not already assigned to a different release order.

NoteIf a release order has been canceled, the TU can be assigned to a new release order. This is handled as part of the release order update process.

● When release orders are created, the booking status is checked. Release orders can be created only if the booking status is Confirmed or Completed, otherwise the following error message appears: Release order cannot be created. Invalid booking status.

Related Information

Determination of Release Order Amendment or Creation [page 366]Validation of Empty Provisioning Locations [page 367]

5.5.2 Determination of Release Order Amendment or Creation

Determination of release order amendment or creation is a validation rule that controls whether a new release order is created or an existing release order is amended. For this purpose, a Business Add-In has been provided in Customizing for SAP Transportation Management under Container Shipping Liners Order to CashBusiness Add-Ins Booking BAdI: Determination of RO Amendment or Creation .

NoteA sample implementation is provided to save a user parameter that specifies whether the rule is Cancel & Replace (amend) or not (create new).


Documentation

Related Information

Release Order Validation [page 366]

5.5.3 Validation of Empty Provisioning Locations

Validation of empty provisioning locations is required to determine whether the source location of the empty provisioning transportation unit (TU) is valid when a release order is created and assigned transportation units.

Valid empty provisioning location types can be defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and documentation Booking Basic SettingsDefine Valid Empty Provisioning Location Type . The source location of the empty provisioning TU is checked

for one of the following location types:

● Depot● Terminal● Ramp● Trucker Yard● Customer Pool● Leasing Company Depot

The following rules apply to release orders when empty provisioning locations are validated:

● If the empty provisioning location type is invalid, creation of the release order is stopped and the following message appears upon saving: Release Order creation failed. Location for TU1234567 invalid.

NoteIf there are at least two containers and one has valid depot location and the other does not, then the release order is created for the container with the valid location.

● If empty provisioning is not flagged (and subsequently a provisioning TU that is not empty is created), the following message appears when release order creation is triggered from the booking: Release order creation not possible. No empty provisioning requested.

● If the source location of the empty provisioning TU is not maintained, creation of the release order is stopped and the following message appears upon saving: Release order cannot be created. Source location for TU123456 not maintained.

● If the requested pickup date of the empty provisioning TU is not maintained, creation of the release order is stopped and the following message appears upon saving: Release order cannot be created. Pickup date for TU123456 not maintained.

Related Information

Creating Release Orders at Booking Level [page 368]


Creating Release Orders at TU Level [page 369]

5.5.4 Creating Release Orders at Booking Level

Create release orders at booking header level to include all necessary header data along with item information for empty provisioning containers (such as POL, POD, dangerous goods, clause, handling instructions, and so on) into the release order. All containers from the same depot are collected in one release order.

Prerequisites

● The booking types have been defined in Customizing for SAP Transportation Management under Transportation Management Forwarding Order Management Forwarding Order Define Forwarding

Order Types .● The release order types have been defined in Customizing for SAP Transportation Management under

Transportation Management Freight Order Management Service Order Define Service Order Types

● The default release order type for booking types has been maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for Booking Type Define Basic Setting for Booking Document Type .

● You have the required authorization to create release orders.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Display Booking , and then open a confirmed booking with empty provisioning equipment for which the equipment availability check (EAC) has been executed.

2. In the header toolbar, choose Follow Up Create Release Order .

Results

Release orders are created successfully for each depot and all of the containers belonging to the respective depot are collected in the release order. The release orders are also displayed in the document flow of this booking.

You can display the release order through the document flow. The release order contains all of the necessary header information and item information. The booking can also be found in the document flow of the release order.


Documentation

Related Information


5.5.5 Creating Release Orders at TU Level

Create release orders at transportation unit (TU) level (booking item level) to include all necessary header data along with item information for the empty provisioning container (such as POL, POD, dangerous goods, clause, handling instruction, and so on) into the release order. For multiple items with one common depot, one common release order is created. Otherwise individual release orders are created for each location.

Prerequisites



Transportation Management Freight Order Management Service Order Define Service Order Types .

● The default release order type for the booking types has been maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for Booking Type Define Basic Settings for Booking Type .


Procedure

1. In SAP NetWeaver Business Client, choose Booking Booking Display Booking , and then open a confirmed booking with empty provisioning equipment for which the equipment availability check (EAC) has been executed.

2. In the Itemssection, highlight one or multiple items and choose Merged RO for Selected Containers to create the release order.

Results

Release orders are created successfully for each depot and all the containers belonging to this depot are collected in this release order. The release orders are also displayed in the document flow of this booking.


You can display the release orders through the document flow. The release order contains all of the necessary header information and item information. The booking can also be found in the document flow of the release order.

Related Information


5.5.6 Release Order Status

The release order status is used to track the state of release orders.

The following table contains a description of the different release order statuses:

Release Order Status Description

New Initial status set when a release order is created.

Issued Status set when the issue action is executed.

NoteWhen a release order is issued, a check is run to determine whether the expiry date is not earlier than the current date or is in the future. If the expiry date has passed, the release order can be issued.

Canceled Status set when a release order is canceled.

NoteIf a container has already been gated out, the status Canceled is not reached. The containers that have not yet been gated out are removed from the release order and the status Reissue Required is set.


Documentation

Release Order Status Description

Reissue Required Status set when a release order is updated (for example, when pickup times are changed or containers and quantities are added or deleted), or when certain fields in the booking are changed.

NoteWhen the release order is then reissued, the status changes to Issued.

Completed Status set when all containers on the release order have a recorded gate-out status. The status is not reset if a return move is recorded for one of the containers.

Expired Status set when the expiry date has been reached but not all containers have been gated out. After the pickup time is updated or when a container is deleted, the status is changed to Reissue Required.

In addition, the Expired status can also be set when the release order is saved and the check determines that the release order has expired.

Related Information

Reissue Required: Field Changes [page 371]Release Order Expiration [page 373]Issuing Release Orders [page 375]Release Order Cancellation [page 373]

5.5.6.1 Reissue Required: Field Changes

If a release order has already been created, changes to certain fields in the booking cause the release order status to be set to Reissue Required.

The table below contains an overview of which fields at which level (header or item) of the booking trigger a reissue requirement for a release order:

Field Level of Booking

Cargo Receipt Mode Header


Field Level of Booking

Means of transport (Empty provisioning TU) Header

Booking Party Header

Vessel name (Load vessel only) Header

Voyage number (Load vessel only) Header

Expiry Date Header

Logistics Comments Header

Clauses Header

Genset Required (Y/N) Item

Size/type Item

Container number (if already mentioned) Item

Requested Pickup Date Item

Flag NOR Item

Reefer temperature Item

Ventilation: % Item

Humidity sensor: Y/N; if Y: Dehumidity % Item

Grade Item

Quantity Item

Cargo weight Item

If OOG: cargo dimension (on booking) Item

Dangerous Goods Indicator Item

Carrier (in case of carrier haulage) Item

Earliest planned pickup date (in case of carrier haulage) Item

Related Information

Release Order Status [page 370]


Documentation

5.5.7 Release Order Cancellation

Release order cancellation can be required when empty provisioning source locations change and when empty provisioning transportation units (TU) need to be unassigned from a release order. Deleting a line item from the booking is possible only if the container hasn't been gated out. Once a TU is deleted, the TU is removed from the release order. If no more items exist, the release order is canceled automatically.

When a release order is canceled, containers that have not yet been gated out are unassigned from the release order. If one container has already been gated out, it remains in the release order. After the other TUs have been unassigned, the release order status is set to Completed.

If a booking is canceled, a release order is automatically canceled. In cases where the release order has already been completed (all of the containers have been gated out), the release order status remains Completed. In the case of partial gate-out, those contains that have not been gated out are removed from the release order.

Related Information

Booking Cancellation [page 200]

5.5.8 Release Order Expiration

Release order expiration applies when the expiry date for the release order has been reached but not all containers have been gated out. A release order is then assigned the status Expired. After the pickup time is updated or a container is deleted, the release order status is changed to Reissue Required. In addition, when a release order is saved, the status is checked and the status Expired is set.

An expiry date is calculated per release order at header level of the document and takes into account a validity period with a tolerance value. The validity tolerance is based either on a globally defined tolerance or is customer specific. The expiry date is valid for the whole release order.

Once a release order expires, the status of the corresponding booking is set to Pending Confirmation.

Related Information

Calculation of Release Order Expiry Date [page 374]


5.5.8.1 Calculation of Release Order Expiry Date

Calculation of release order expiry date is carried out automatically based on the latest release date defined at item level or a customer-specific expiry period (if available). If a customer-specific value is not defined, a global value for the validity period is used based on location and equipment size type.

The release order expiry date is equal to the last release date defined for the items in the release order plus the global release order validity period or the customer-specific validity period, The latest release date defined at the item level is the pickup date on the Empty Provisioning tab.

The customer-specific and global release order validity period values per country and equipment (only Dry, Special, and Reefer) are stored on the Shipper/Consignee tab of the partner and location profile (PLP) based on the booking party. The container type is mapped to the release order validity based on the resource class defined in the Customizing settings for the transportation unit (TU) group.

The following rules are applied to determine whether the expiry date is calculated based on customer-specific or global values:

Scenario Customer-Specific Validity Maintained?

Value Used to Determine Expiry Date

Customer (booking party) is in the same country as the source location of the booking

Yes Customer-specific value

No Global value

Customer (booking party) is not in the same country as the source location of the booking

Yes Global value

No

NoteIn case of carrier haulage (cargo receipt mode Door), only global values are applicable based on location data in the booking. If the release order contains multiple containers (of different types), the longest expiry date is taken.

Related Information

Issuing Release Orders [page 375]Release Order Validation [page 366]


Documentation

5.5.9 Issuing Release Orders

Issue release orders to release empty containers from the depot.

Prerequisites



Transportation Management Freight Order Management Service Order Define Service Order Types .

● The default release order type for the booking types has been maintained in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Booking and Documentation Booking Settings for Booking Type Define Basic Settings for Booking Type .


Procedure

1. In SAP NetWeaver Business Client, choose Logistics Release Order Change Booking and then open a release order.

2. In the header toolbar, choose Issue RO.

Results

The status of the relevant release orders is updated to Issued and the Issue Date field is filled. If the release order has already expired, an error message appears to indicate the reason. Once the release order is issued, a technical STOP_FIX field is set for all of the containers within the release order to prevent replanning. As a result, these containers are not considered for planning until they return to the depot.

Related Information

Release Order Expiration [page 373]


5.5.10 Creation of Release Orders for Merged Bookings

Creation of release orders for merged bookings is required if a container merged into another booking has not yet been gated out from the depot.

When bookings are merged, a check is carried out to determine whether the containers merged to a new or an existing booking have already been gated out. If not, the merged containers are unassigned from the original release order and a new release order is created for the booking into which the containers were merged. If a container has already been gated out from the depot, the container is not unassigned from the release order.

Related Information

Example: Release Orders for Merged Bookings [page 376]

5.5.10.1 Example: Release Orders for Merged Bookings

The following table illustrates how release orders are handled when bookings are merged in different scenarios.

For each scenario below, the following applies:

● Two bookings are to be merged into one confirmed booking.● Each of the bookings has one container for which a release order has already been created.

Scenario Result

The merged containers have the same depot and no containers have been gated out.

● The container quantity changes from 1 to 3.● The second and third containers are merged into the

first release order.● The second and third release orders are canceled.

The first and second containers merged have the same depot and no containers have been gated out.

● The container quantity changes from 1 to 2.● The second container is merged into the first release or

der.● The second release order is canceled.● The third release order is linked to the merged booking.

The merged containers have the same depot and all containers have been gated out.

● The first release order remains unchanged.● The second and third release orders are linked to the

merged booking.

The merged containers have the same depot and only the first container has been gated out.

● The container quantity changes from 1 to 3.● The second and third containers are merged into the

first release order.● The second and third release orders are canceled.


Documentation

Related Information

Booking Consolidation [page 187]Release Order Validation [page 366]

5.5.11 Creation of Release Orders for Split Bookings

Creation of release orders for split bookings is required when containers are split to a new or existing booking and these containers have not yet been gated out.

When bookings are split, a check is carried out to determine whether the containers split to a new or an existing booking have already been gated out. If not, the containers are unassigned from the original release order and a new release order is created for the new booking. If a container has already been gated out from the depot, the containers is not unassigned from the original release order.

Related Information

Example: Release Orders for Split Bookings [page 377]

5.5.11.1 Example: Release Orders for Split Bookings

The following table illustrates how release orders are handled when bookings are split in different scenarios.

For each scenario below, the following applies:

● Two of three containers in a booking are to be split to a new booking.● Release orders have already been created for the containers.

Scenario Result

One release order has been created for all three containers and none of the containers have been gated out.

● The container quantity in the original release order changes from 3 to 1.

● The second and third containers are removed from this release order.

● A new release order is created for the second container.● A new release order is created for the third container.


Scenario Result

One release order has been created for the first and second containers, and one release order for the third container. None have been gated out.

● The container quantity in the first release order changes from 2 to 1.

● The second container is removed from the first release order.

● A new release order is created for the second container.● The release order for the third container remains but is

linked to the new booking.

One release order has been created for all three containers and all containers have been gated out.

● The release order remains unchanged.● A release order is not created for the second container.● A release order is not created for the third container.

One release order has been created for all three containers and the first container has been gated out.

● The container quantity in the original release order changes from 3 to 1.

● The second and third containers are removed from this release order.

● A new release order is created for the second container.● A new release order is created for the third container.

Related Information

Creation of Release Orders for Split Bookings [page 377]

5.5.12 Release Orders for Carrier Haulage

Note the following information with regard to release orders for carrier haulage:

● The carrier stored in the actual route of the booking (empty provisioning stage) is propagated to the item level in the release order.

● If the carrier changes, the release order status is set to Reissue Required.● If the cargo receipt mode is Door, the earliest planned pickup date of the actual route provisioning stage

(estimated time of departure) is displayed in the release order header. In case of changes (to pickup date, resource ID, container type, and so on), the release order status is set to Reissue Required. At item level, the individual planned pickup date is displayed.

Related Information

Release Orders [page 365]


Documentation

5.5.13 Using the Release Order Worklist

Use the release order worklist to search for bookings and transportation units (TUs) for which you want to create release orders or perform other release order operations.

Prerequisites

You have been assigned personal object worklist (POWL) type /TMCSL/POWL_TYPE_TRQ_RO_ALL_EP in transaction POWL_COCKPIT.

Procedure

1. In SAP NetWeaver Business Client, choose Logistics Worklist Overview Release Order Cargo UnitsShow Quick Criteria Maintenance .

2. Specify the required search criteria, for example:○ To view bookings and relevant TUs with any provision depot, specify the location in the Provision Depot

field.○ To view bookings and relevant TUs within any period, specify the time in the Pickup Date from field

(defaulted with current date) field.3. Choose Apply. All of the bookings and TUs that fulfill the condition are displayed in the list.4. Choose Hide Quick Criteria Maintenance.5. Select the relevant items and choose from the following options:

Option Result

Display TU The TU is displayed in a dialog box.

Create RO for booking A release order is created for this booking per depot for the booking items.

Creation and Issuing of RO for Booking A release order is created and issued for this booking per depot for the booking items.

Create RO for TU A release order is created for these TUs per depot for the booking items.

Creation and Issuing of RO for TU A release order is created and issued for these TUs per depot for the booking items.


Option Result

Issue RO The release is order is issued.

NoteIn this case, you select an item for which the release order was already created.

Results

The release orders operations are carried out accordingly.

Related Information

Creating Release Orders at Booking Level [page 368]Creating Release Orders at TU Level [page 369]Issuing Release Orders [page 375]

5.5.14 Keep Determined Depot Indicator

The Keep Determined Depot indicator is set on the Empty Provisioning tab of the booking item when a release order is created for a transportation unit (TU). It indicates that the depot has already been determined, and therefore the determination logic will be skipped for this booking item.

The Keep Determined Depot indicator is cleared if values of any of the following fields are changed:

● Booking Source Location (Header)● Booking Destination Location (Header)● Cargo Receipt Mode (Header)● Equipment Type (Item)● Equipment Grade (Item)● Preferred City/Depot Provisioning (Item)● Preferred City/Depot Return (Item)● Genset Required (Item)● Change in Instruction (for Instruction Set Logistics)

NoteFor header level changes, the Keep Determined Depot indicator is cleared for all containers. For item level changes, the Keep Determined Depot indicator is cleared for the individual container. In addition, the initial depot determination is skipped if Keep Determined Depot is set.


Documentation

In addition, if any of the above field values are changed, the booking status changes from Confirmed to Pending Confirmation.

Related Information

Creating Release Orders at Booking Level [page 368]Creating Release Orders at TU Level [page 369]Initial Depot Determination [page 239]


6 Invoice Preparation

Invoice preparation covers three main processes in the SAP Transportation Management system.

These processes are the following ones:

● Processing of payment information is entered for charge elements within a booking or bill of lading● Creation of forwarding settlement documents● Preparation of the required information for transferring of the forwarding settlement documents to

external modules such as convergent charging (CC) and convergent invoicing (CI)

To simplify integration processes with external modules such as CC and CI in the invoice preparation area, two main services (classes) have been provided:

● Inbound service /TMCSL/CL_CFIR_INBOUND_PROCESS● Outbound service /TMCSL/CL_CFIR_OUTBOUND_PROC

6.1 Charge Element Information

Several different agencies all over the world can be responsible for invoicing charges from the same booking or bill of lading, which is why it is vital to split these processes between the agencies. To ensure that invoicing takes place smoothly for the different agencies, the Place of Payment (POP) attribute was introduced at item charge element level.

The POP is linked by way of a partner and location profile (PLP) to a responsible agent, which finally determines relevance of the particular charge element to the user during a settlement process. The user, ideally linked to a business partner, can invoice only those charges where it is the responsible agent.

The charge elements in SAP Transportation Management have been enriched with new attributes, which can be divided into the following two groups:

● Payment information that can be maintained at item charge element level and is represented by the following fields:○ Settlement Terms○ Place of Payment○ Bill-To Party

● Other information that cannot be maintained at item charge element level and is purely for informational purposes:○ Invoice status○ Invoicing block○ Responsible agent○ Requested invoice amount (and currency)○ Invoiced invoice amount (and currency)○ Payment status (one for booking and one for forwarding settlement document)○ Invoice number


Invoice Preparation

○ Local and carrier charge

6.1.1 Settlement Terms

The settlement terms value for charge elements in a booking or billing of lading indicates whether the payment type is prepaid or collect. By default, the settlement terms value is taken from the booking header.

Related Information

Updating Settlement Terms [page 383]

6.1.1.1 Updating Settlement Terms

You can update the settlement terms value for an existing charge element in a booking or bill of lading. If you change a value manually, the updated settlement terms value is not overwritten by the default determination logic when a new charge calculation is carried out.

Prerequisites

● The charges have been calculated for the booking or bill of lading.● A valid set of charge elements exists.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Change Booking .2. Specify the booking number containing the target set of charge elements and choose Continue.3. Go to the Charges tab and update the settlement terms value for the target charge element.4. Save your entries.

Results

You have updated the settlement terms value for the item charge element.

SAP Transportation Management, Order to Cash for Container Shipping LinersInvoice Preparation P U B L I C 383

6.1.2 Place of Payment

The place of payment (POP) is a location that is maintained as an attribute of an existing charge element in a booking or bill of lading.

By default, the POP is determined as follows:

● For prepaid charges, the POP for the booking agent is used in the charge element:

NoteThe booking agent is a business partner, and its POP is defined within a corresponding partner and location profile for the particular business partner, which represents a particular booking agent on the Charge Calculation tab.

● For collect charges, the POP for the port of discharge is used in the charge element.

Only an authorized POP can be used in a charge element. This means that the Authorized Place of Payment indicator must be set in a partner and location profile for the particular location that represents a particular POP on the Charge Calculation tab.

Related Information

Updating the Place of Payment [page 384]

6.1.2.1 Updating the Place of Payment

You can update a place of payment (POP) value, which is the location maintained for an existing charge element in a booking or a bill of lading.

Prerequisites

● The charges have been calculated for the booking or bill of lading.● A valid set of charge elements exists.● A partner and location profile has been created for the POP as the location that you want to use.● The Authorized Place of Payment checkbox has been selected on the Charge Calculation tab.

Context

If you change the value manually, note the following system behavior:


Invoice Preparation

● The POP value is not overwritten by the default determination logic when a new charge calculation is carried out.

● The POP value is updated if the settlement terms value is changed.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Change Booking .2. Specify the booking number containing the target set of charge elements and choose Continue.3. Go to the Charges tab and update the value of the POP for the target charge element.4. Save your entries.

Results

You have updated the place of payment value for the item charge element.

Related Information

Place of Payment [page 384]

6.1.3 Bill-To Party

The bill-to party value for an existing charge element in a booking or bill of lading is a business partner. In the current solution, there is no default logic that determines the bill-to party value.

Related Information

Updating the Bill-To Party [page 386]


6.1.3.1 Updating the Bill-To Party

You can update a bill-to party value for an existing charge element in a booking or bill of lading. A manually maintained bill-to party value is not overwritten – neither after a new charge calculation is carried out nor after a Settlement Terms value is changed.

Prerequisites

● The charges have been calculated for the booking or bill of lading.● A valid set of charge elements exists.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Change Booking .2. Specify the booking number containing the target set of charge elements and choose Continue.3. Go to the Charges tab and update the value of the bill-to party for the target charge element.4. Save your entries.

Results

You have updated the bill-to party value for the item charge element.

Related Information

Bill-To Party [page 385]

6.1.4 Responsible Agent

The responsible agent in an item charge element is the business partner responsible for invoicing the charge element.

The responsible agent is determined either from a place of payment or from a booking agent, and is maintained in a partner and location profile (PLP) for a particular location or business partner.

When the responsible agent is determined, the system first searches for a place of payment in the PLP for a particular location. If a place of payment is not found, the responsible agent is determined from the booking agent, that is, from the PLP of the business partner representing the booking agent.


Invoice Preparation

Related Information

Updating the Responsible Agent [page 387]

6.1.4.1 Updating the Responsible Agent

You can update the responsible agent in an item charge element.

Prerequisites

● The charges have been calculated for the booking or bill of lading.● A valid set of charge elements exists.● A partner and location profile (PLP) exists for the location you want to use as a place of payment within the

charge elements.

Procedure


2. Specify the PLP ID that represents a location for the target place of payment and choose Continue.3. Go to the Charge Calculation tab and enter the responsible agent in the Invoicing Agent for Freight Charges

field.4. Save your entries.

5. In SAP NetWeaver Business Client, choose Booking Change Booking .6. Specify the booking number containing the target set of charge elements and choose Continue.7. Go to the Charges tab and update the value of the place of payment for the target charge element.

NoteIf you want to update a responsible agent, but a place of payment cannot be updated because it already exists, then a new charge calculation must be performed.


Results

The responsible agent value for the item charge element is updated after the place of payment has been changed in the PLP.


6.1.5 Invoice Status

The invoice status shows the current state of the item charge element in an invoicing process. It indicates whether a particular charge element has already been invoiced, has to be invoiced, or is not invoicing relevant at all.

The invoice status cannot be changed directly on the screen, but it is updated automatically, for example:

● After creation of a forwarding settlement document (FWSD).● After changes to the rate amount for a particular charge element

The following table provides an overview of the invoice statuses and their meaning:

Invoice Status Meaning

To be Invoiced The charge element has an amount that can be invoiced, irrespective of whether relevant FWSDs exist.

Invoice Requested The charge element has no amount that can be invoiced and relevant FWSDs have been created.

Fully Invoiced The charge element has no amount that can be invoiced and relevant FWSDs have been created. In addition, the corresponding charge elements have been invoiced to the customer from these FWSDs.

No Charge The charge element has no amount that can be invoiced and no relevant FWSDs exist.

Not Relevant The charge element is not relevant for the invoicing process.

6.1.5.1 Changes to Invoice Status

The invoice status of charge elements is updated when certain actions are performed.

An overview of actions and how they influence the invoice status is provided in the following table:

Original Status New Status Action That Triggers Status Change

To Be Invoiced Invoice Requested A final invoice request is created for a charge element.

The bill-to party or settlement terms, or both, are changed to the combination for which a forwarding settlement document exists.


Invoice Preparation

Original Status New Status Action That Triggers Status Change

Invoice Requested To Be Invoiced The rate amount for a charge element is changed.

The bill-to party or settlement terms, or both, are changed to the combination for which a forwarding settlement document does not exist.

Invoice Requested Fully Invoiced The charge elements have been invoiced to the customer from the forwarding settlement documents.

Any value Not Relevant The booking shipping type is changed from full container load to equipment, and the charge element is irrelevant for the process according to the Customizing settings.

Related Information

Invoice Status [page 388]

6.1.6 Requested Invoice Amount

The requested invoice amount is the total requested amount for a particular charge element with the invoice status Invoice Requested.

This amount is the sum of all relevant charge element amounts of the corresponding settlement documents. The amount is always calculated based on a combination of settlement terms and bill-to party, and applies for all non-statistical charges.

The requested invoice amount cannot be changed directly on the screen. When you create a final invoice request, the requested invoice amount is updated for the relevant charge elements in the system automatically.


6.1.7 Invoiced Invoice Amount

The invoiced invoice amount is calculated for item charge elements in bookings only when the amount invoiced to the customer has been updated in the settlement document sent to the convergent charging and convergent invoicing modules.

Related Information

Calculation of Invoiced Invoice Amount [page 390]

6.1.7.1 Calculation of Invoiced Invoice Amount

The invoiced amount is calculated for item charge elements in bookings.

The invoiced amount is calculated as follows:

1. A settlement document is created from a booking.2. When the settlement document is saved, it is automatically sent to the convergent charging (CC) and

convergent invoicing (CI) modules.3. The CC and CI modules send the payment details to the customer based on the received settlement

document, after which, the amount invoiced to the customer is updated in the settlement document.4. The amount is updated in the settlement document in SAP Transportation Management.5. The invoiced invoice amount is calculated in the booking.

The amount is always calculated based on a combination of settlement terms and bill-to party, and applies for all nonstatistical charges.

Related Information

Invoiced Invoice Amount [page 390]

6.1.8 Payment Status

The payment status in bookings shows aggregated payment information collected from all relevant settlement documents. In turn, the payment information in the settlement documents is updated from the convergent


Invoice Preparation

charging and convergent invoicing modules after the modules have received appropriate payment information from the customer.

Related Information

Determination of Payment Status [page 391]

6.1.8.1 Determination of Payment Status

Determination of the payment status applies only for nonstatistical charges.

The payment status in bookings is determined as follows:

1. A settlement document is created from a booking.2. When the settlement document is saved, it is automatically sent to the convergent charging (CC) and

convergent invoicing (CI) modules.3. The CC and CI modules send the payment details to the customer based on the received settlement

document.4. The customer makes or rejects a payment and the CC and CI modules receive this information.5. The CC and CI modules update the relevant settlement document with payment details from the customer.6. The payment status is propagated to the settlement document in SAP Transportation Management from

the CC and CI modules.7. The aggregated payment status is determined in the booking after the relevant information is updated

within a settlement document.

6.2 Forwarding Settlement Documents

When you prepare invoices in SAP Transportation Management, one of your main tasks is to create forwarding settlements documents (FWSDs).

These documents are created based on a unique combination of the settlement terms and bill-to party attributes from the charge elements that are relevant to you as the responsible agent. The combinations vary according to the FWSD type, and only one FWSD is created for each combination of these attributes.

There are two main types of FWSD, as follows:

● Final invoice request (FIR)This type of forwarding settlement document takes into account all existing FIRs to ensure that delta amounts are calculated correctly. An FIR is sent to the customer for a payment

● Proforma invoice request (PIR)This type of settlement document is created without taking into account all existing settlement documents. Only the final amount of the current charge element in the booking is taken into account, and any delta amount calculations are ignored. A PIR is not sent to the customer for payment.


Related Information

Creating Final Invoice Requests [page 392]Creating Proforma Invoice Requests [page 393]

6.2.1 Creating Final Invoice Requests

Create a final invoice request (FIR) for a unique combination of settlement terms and bill-to party.

Prerequisites

● The charges have been calculated for the booking or bill of lading.● A valid set of charge elements exists.● At least one charge element exists that meets the following criteria:

○ All payment information has been maintained.○ The invoice status is To Be Invoiced.○ You are the responsible agent for this charge element.○ The Invoicing Block indicator is not selected.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Display Booking2. Specify the booking number containing the target set of charge elements and choose Continue.

3. Choose Follow Up Create Final Invoice Request .4. In the dialog box that opens, select the combination of settlement terms and bill-to party required for

creating the invoice.5. Generate the final invoice request with or without previewing it first:

Option Description

With preview Select the Preview checkbox, choose OK, and save your document in the new window.

Without preview Choose OK to confirm the dialog box.

Results

You have created the final invoice request, which is sent to the customer for payment.


Invoice Preparation

6.2.2 Creating Proforma Invoice Requests

Create a proforma invoice request (PIR) for a unique combination of settlement terms and bill-to party.

Prerequisites


○ All payment information has been maintained.○ You are the responsible agent.○ The Invoicing Block indicator is not selected.

● Any existing (or new) settlement types have been selected as proforma-relevant in Customizing for Container Shipping Liners under Order to Cash Invoicing and Finance Integration Define Forwarding Settlement Document Types .

● The relevance of the proforma settlement document type to your booking type has been maintained in Customizing for Container Shipping Liners under Order to Cash Invoicing and Finance IntegrationAssign FWO Type with Settlement Type (Proforma) .

Procedure

1. In SAP NetWeaver Business Client, choose Booking Display Booking2. Specify the booking number containing the target set of charge elements and choose Continue.

3. Choose Follow Up Create Proforma Invoice Request .4. In the dialog box that opens, select the combination of settlement terms and bill-to party required for

creating the invoice.5. Generate the proforma invoice request with or without previewing it first:

Option Description

With preview Select the Preview checkbox, choose OK, and save your document in the new window.

Without preview Choose OK to confirm the dialog box.

Results

You have created the proforma invoice request.


6.3 Negative Forwarding Settlement Document

After a forwarding settlement document has been created for a particular charge element, it may sometimes be necessary to change such fields as Settlement Terms, or Bill-To Party, or both for this charge element.

In this case, the document previously created has to be withdrawn when the new settlement document is created for a new combination of settlement terms and bill-to party. For this purpose, a negative forwarding settlement document is created, which applies only for final invoice requests.

Related Information

Creating a Negative Forwarding Settlement Document [page 394]

6.3.1 Creating a Negative Forwarding Settlement Document

Create a negative forwarding settlement document (FWSD) to withdraw a previous settlement document in cases where the combination of settlement terms and bill-to party is to be changed.

Prerequisites


○ All payment information has been maintained.○ The invoice status is Invoice Requested.○ You are the responsible agent for this charge element.○ The Invoicing Block indicator is not selected.

Procedure

1. In SAP NetWeaver Business Client, choose Booking Change Booking .2. Specify the booking number containing the target set of charge elements and choose Continue.3. Change the Settlement Terms or Bill-To Party value, or both, for the charge element with the invoice status

Invoice Requested.

4. Choose Follow Up Create Final Invoice Request .5. In the dialog box that opens, select the combination of settlement terms and bill-to party required for

creating the invoice.


Invoice Preparation

6. Select the Preview checkbox and then choose OK.7. In the new window that opens, save the created documents.

Results

● A forwarding settlement document for the newly maintained combination of settlement terms and bill-to party is created.

● A negative forwarding settlement document is generated for the previous combination of the same fields.

6.4 Part-Load Scenario

In a part-load scenario, multiple part-load bookings are assigned to one equipment booking. The equipment and part-load bookings must have the same set of charge elements. Thus it is vital to avoid double settlement of the same charge elements.

For this reason and in accordance with the settings defined in Customizing for SAP Transportation Management under Container Shipping Liners Order to Cash Basic Settings Define Charge Type Attributes for Order to Cash, charge elements are processed on the equipment and part-load booking sides, based on their calculation and invoice levels, as follows:

● If both calculation and invoice levels are in the equipment booking, then such charge elements are completely removed from the part-load booking.

● If both calculation and invoice levels are in the part-load booking, then such charge elements are completely removed from the equipment booking.

● If the calculation level is in the equipment booking and the invoice level in the part-load booking (referred to as distribution), then such charge elements are completely removed from the part-load booking if they are not pulled charges. Charge elements to be distributed from the equipment booking are retained, but payment information is not editable and is empty, apart from the Settlement Terms field, which influences the distribution method of the charge element.


Important Disclaimers and Legal Information

HyperlinksSome links are classified by an icon and/or a mouseover text. These links provide additional information.About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any

damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental FeaturesExperimental 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 CodeAny 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.

Gender-Related LanguageWe try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.


Important Disclaimers and Legal Information

SAP Transportation Management, Order to Cash for Container Shipping LinersImportant Disclaimers and Legal Information P U B L I C 397

go.sap.com/registration/contact.html

© 2018 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. 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.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

https://www.sap.com/about/legal/trademark.html

SAP Transportation Management, Order to Cash for … · order-to-cash process for container...

Documents

Transcript of SAP Transportation Management, Order to Cash for … · order-to-cash process for container...