Ocean freight moves goods between ports using carrier services. In SAP Transportation Management, a freight booking can record the shipper's planned ocean transport arrangement and the carrier's confirmation or rejection. Booking a container, delivering it to a terminal and completing a voyage are distinct events that require separate evidence.
Start with the shipment and its owners
A single export shipment can involve factory dispatch, a road carrier, port operations, an ocean shipping line and destination distribution. The shipper, consignee and forwarder may have different contractual roles. Confirm who arranges each leg, who prepares documentation and which party carries the commercial risk before choosing how to model the transport.
The booking is a commercial commitment
SAP Help describes sea freight bookings with shipper, consignee, carrier, cargo details and optional transportation charge calculation. The planner can send a request to the shipping line, whose response may confirm or reject the booking. A carrier acceptance is important, but it does not show that a container crossed the gate, loaded on the intended vessel or arrived at its destination.
Port cut-offs can change a delivery promise
Cargo-ready time, documentation cut-off, terminal gate-in cut-off, expected departure and destination arrival are separate milestones. Suppose two containers of automotive parts are reserved on a weekly sailing. A missing export document may cause them to miss that departure despite completed packing. The planner must arrange a later sailing, agree updated timing and advise downstream teams. A changed screen status without operational evidence solves nothing.
Follow execution beyond the ocean leg
Inland pickup, container handover, vessel departure, discharge and final delivery can be owned by different parties. Freight bookings coordinate transport planning while other systems and actors provide actual movement events. Customs clearance, dangerous-goods compliance and marine-insurance decisions require qualified processes beyond ordinary booking entry.
How carrier collaboration fits
SAP Business Network for Logistics documentation describes booking requests and carrier responses sent between the ordering party and the carrier. The availability and configuration of such integration depend on the organization's landscape and the parties involved. A rejected booking may reflect missing capacity, route constraints or incorrect shipment information; investigate the response rather than changing values to make it disappear.
Consultant questions
Ask whether cargo was available, which booking was confirmed, which cut-offs applied, whether the container entered the terminal, and whether final inland delivery was arranged. Separate planning status from real-world execution, and commercial responsibility from physical custody. This distinction prevents a scheduling issue from being mistaken for a product defect.
Related Knowledge
dangerous goods controls · outbound delivery process · warehouse tasks. Return to SAP TM.