You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
CONTAINERISED SEA CARGO REPORTING<br />
When an FCL OBOL cargo report is submitted <strong>to</strong> the ICS, the ICS will find all HBOL cargo<br />
reports for the same vessel/voyage/container (either FCL, FCX or LCL). If the OBOL<br />
numbers on the OBOL cargo report and HBOL cargo report(s) is the same, then the ICS will<br />
link these documents normally. If the OBOL numbers are different, the ICS will append the<br />
OBOL number from the OBOL cargo report <strong>to</strong> the HBOL cargo report and link these<br />
documents.<br />
Industry will still be required <strong>to</strong> continue <strong>to</strong> report the OBOL numbers provided on commercial<br />
documentation.<br />
<strong>Cargo</strong> reports may be amended or withdrawn, but unique cargo identifiers such as vessel Id,<br />
voyage number, OBOL number and HBOL number cannot be amended. If any unique cargo<br />
identifiers are required <strong>to</strong> be amended, the cargo report must be withdrawn and a new report<br />
submitted.<br />
Amendments <strong>to</strong>, or withdrawals of, HBOL cargo reports via EDI will be accepted only if the<br />
reported or derived OBOL number is quoted within the message.<br />
To clarify the matching process, there are a number of principles that will be applied when<br />
deriving an OBOL number for an HBOL cargo report:<br />
• If two or more OBOL cargo reports with the same vessel/voyage/container exist in the<br />
ICS when a matching HBOL cargo report is submitted, the HBOL cargo report will be<br />
linked <strong>to</strong> the OBOL cargo report that was submitted first;<br />
• If the linking of the HBOL cargo report <strong>to</strong> the OBOL cargo report will result in an<br />
impossible situation, such as an FCL HBOL cargo report becoming the child of an<br />
LCL HBOL cargo report, only the OBOL will only be derived for the HBOL cargo<br />
report that was submitted first; and<br />
• An OBOL cargo report will not be linked <strong>to</strong> an HBOL cargo report with the same<br />
vessel/voyage/container if the transit indica<strong>to</strong>rs on the two documents are different<br />
(i.e., one cargo report is for transit cargo and the other is for import cargo).<br />
SCENARIOS<br />
Scenario 1 (below) shows the system behaviour when:<br />
• The freight forwarder reports one HBOL cargo report for an FCL container using an<br />
inaccurate OBOL number;<br />
• The shipping company reports one OBOL cargo report for the FCL container<br />
consigned <strong>to</strong> the freight forwarder;<br />
• There is no underbond move required as the container is <strong>to</strong> be delivered from the<br />
wharf.<br />
Scenario 2 (below) shows the system behaviour when:<br />
• The freight forwarder reports one HBOL cargo report for an FCL container using an<br />
inaccurate OBOL number;<br />
• The shipping company reports one OBOL cargo report for the FCL container<br />
consigned <strong>to</strong> the freight forwarder, mistakenly quoting the incorrect OBOL number, so<br />
the OBOL cargo report is withdrawn, corrected and resubmitted;<br />
• There is no underbond move required as the container is <strong>to</strong> be delivered from the<br />
wharf.