ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 315 — Status Details (Ocean)

The 315 transmits the detailed status of an ocean shipment between carrier and shipper / consignee: voyage milestones, terminal events, dates.

Purpose

The 315 documents the events of an ocean shipment: empty container loaded at origin, FCL gated in at origin port, loaded on vessel, ETA at discharge port, discharged, gated out, delivered. It serves as a supply-chain visibility instrument for BCOs (Beneficial Cargo Owners).

It complements the 322 (Terminal Operations) which covers terminal activity, and the 324 (Ocean ASN). Acknowledged by 997; it is frequently broadcast at each critical event.

Envelope structure

The 315 travels within the three X12 envelope levels (ISA/IEA, GS/GE with functional group QO, and ST/SE). Didactic example in release 004010:

x12 example-315.x12 
ISA*00*          *00*          *ZZ*OCEANCARRIER  *ZZ*BCOIMPORTER    *260514*1400*U*00401*000000315*0*P*>~
GS*QO*OCEANCARRIER*BCOIMPORTER*20260514*1400*1*X*004010~
ST*315*0001~
B4*N*1*VL*20260514*1330*PACIFIC*ECT~
N9*BM*BL-2026-LAX-0098~
N9*EQ*MSCU4501230~
Q2*MV PACIFIC*US*20260520*USLAX~
R4*L*UN*USLAX*LOS ANGELES PORT*US~
SG*ETA*20260520~
SE*9*0001~
GE*1*1~
IEA*1*000000315~

Common segments

  • Header — ST, B4 (Beginning Segment for Inquiry or Reply).
  • Reference — N9*BM (BL), N9*EQ (Equipment / Container).
  • Vessel — Q2 (Status Details — Vessel name, registration, ETA, port).
  • Location — R4 (Port or Terminal), SG (Special Service event).
  • Status code — Q201 inside Q2 (AE = Departed, AF = Discharged, AR = Loaded, X1 = ETA).
  • Summary — SE.

Common pitfalls

  • Moving ETA: ETA evolves with weather, congestion, transhipment; an initial 315 ETA cannot be considered reliable D-7 — always refresh.
  • UN/LOCODE port: use official UN/LOCODE (USLAX, NLRTM, CNSHA); home-grown codes break BCO automation tools.
  • Multiple containers: a BL can cover several containers; a 315 carrying only some containers gives a partial picture — always broadcast all containers on each event.

Documentation

The code 315 and the name Status Details (Ocean) are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.