972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Transportation

EDI 109 Vessel Content Details

The X12 document used to report event details and status for one or more containers bound for a port.

Sent by
Ocean carrier, terminal or port community system
Received by
Port authority, terminal or other interested party
Standard
ANSI ASC X12

What is an EDI 109?

The EDI 109 Vessel Content Details is the ANSI X12 transaction set that provides the information needed to report event details for a shipment and the status of one or more containers bound for a port. It can carry one status or event for many containers, or several statuses or events for one shipment.

Ports and terminals plan their operations around what is arriving on each vessel. Reporting the containers and their status in one structured message lets them prepare yard space, labor and onward transport, and gives other parties a consistent picture of the vessel's content before it berths.

How the EDI 109 worksDiagram of the EDI 109 Vessel Content Details. Ocean carrier, terminal or port community system sends it to port authority, terminal or other interested party. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B4 (Beginning Segment for Inquiry or Reply) and the required R4 loop with R4 (Port or Terminal). 1 optional loops are listed by their first segment.How the EDI 109 worksVessel Content Details: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 109SENDEROcean carrier, terminalor port communitysystemRECEIVERPort authority,terminal or otherinterested party997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code VEGS … GETransaction set 109ST … SEHEADINGB4Beginning Segment for Inquiry or ReplyRequired loop R4 · repeats up to 20R4Port or Terminal+ 1 optional loop, starting with:N9Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 109. Your trading partner's implementation guide adds its own requirements.
How the EDI 109 worksDiagram of the EDI 109 Vessel Content Details. Ocean carrier, terminal or port community system sends it to port authority, terminal or other interested party. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B4 (Beginning Segment for Inquiry or Reply) and the required R4 loop with R4 (Port or Terminal). 1 optional loops are listed by their first segment.How the EDI 109 worksVessel Content Details: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 109SENDEROcean carrier,terminal or portcommunitysystemRECEIVERPort authority,terminal or otherinterested party997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code VE (GS … GE)Transaction set 109 (ST … SE)HEADINGB4Beginning Segment for Inquiryor ReplyRequired loop R4 · repeats up to20R4Port or Terminal+ 1 optional loop, starting with:N9Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 109. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 109, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 109 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Reporting containers on a vessel bound for a port
  • Reporting one event for many containers at once
  • Reporting several events for one shipment

Where it fits in the document flow

This document 109 Vessel Content Details
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 109 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • B4
  • R4
  • N9
  • SE

Practical example

The 109 in practice

A vessel is two days from a port. The carrier sends the terminal a 109 listing the containers to be discharged there, each with its status, such as full or empty and any holds, and the event of loading at the previous port. The terminal uses the details to plan yard positions and gate appointments.

Implementation

Implementation considerations for the 109

  • Identify containers and the vessel call consistently with other messages.
  • Agree which events and statuses are reported.
  • Send details early enough for terminal planning.
  • Reconcile with stowage and discharge data.

How ECOM helps

Automate the 109 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related transportation documents

All 80 transportation documents

Need help with the EDI 109?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us