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 315 Status Details (Ocean)

The X12 document ocean carriers and terminals use to report status events for shipments and containers, such as gate-in, loaded and discharged.

Sent by
Ocean carrier or terminal
Received by
Shipper, forwarder, consignee or other interested party
Standard
ANSI ASC X12
EDIFACT equivalent
IFTSTA

What is an EDI 315?

The EDI 315 Status Details (Ocean) is the ANSI X12 transaction set used to report status or event details for selected shipments or containers. One 315 can report one event for many shipments or containers, or several events for a single shipment or container.

Typical events include an empty container released, gate-in at the port, loaded on the vessel, vessel departure and arrival, discharge and gate-out at destination. Shippers and consignees use 315 events to track international shipments, plan inland transport and warn customers of delays.

How the EDI 315 worksDiagram of the EDI 315 Status Details (Ocean). Ocean carrier or terminal sends it to shipper, forwarder, consignee or other interested party. It usually follows 301. 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). 0 optional loops are listed by their first segment.How the EDI 315 worksStatus Details (Ocean): who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS301Confirmation (Ocean)EDI 315SENDEROcean carrier orterminalRECEIVERShipper, forwarder,consignee 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 QOGS … GETransaction set 315ST … SEHEADINGB4Beginning Segment for Inquiry or ReplyRequired loop R4 · repeats up to 20R4Port or TerminalBlue 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 315. Your trading partner's implementation guide adds its own requirements.
How the EDI 315 worksDiagram of the EDI 315 Status Details (Ocean). Ocean carrier or terminal sends it to shipper, forwarder, consignee or other interested party. It usually follows 301. 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). 0 optional loops are listed by their first segment.How the EDI 315 worksStatus Details (Ocean): who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS301Confirmation (Ocean)EDI 315SENDEROcean carrier orterminalRECEIVERShipper,forwarder,consignee orother interestedparty997 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 QO (GS … GE)Transaction set 315 (ST … SE)HEADINGB4Beginning Segment for Inquiryor ReplyRequired loop R4 · repeats up to20R4Port or TerminalBlue 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 315. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 315, 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 315 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

  • Tracking containers from origin port to destination
  • Planning inland pickup after discharge
  • Measuring carrier transit times and delays

Where it fits in the document flow

Usually follows 301 Confirmation (Ocean)
This document 315 Status Details (Ocean)
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 315 (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
  • SE

Practical example

The 315 in practice

An importer tracks containers of electronics from Shanghai to Los Angeles. As events occur, the carrier sends 315 messages: loaded on vessel, vessel departed, vessel arrived and discharged. When the discharge event arrives, the importer's system books a drayage pickup and updates the expected arrival at its warehouse.

Implementation

Implementation considerations for the 315

  • Map event codes to your own milestones, because carriers may report the same event differently.
  • Handle events that arrive late or out of order without overwriting newer status.
  • Link containers to purchase orders so status can be shared with planners and customers.

How ECOM helps

Automate the 315 with ECOM

Industry

Trucking and Transportation

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

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

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 315?

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

Request a Demo Contact us