315 Status Details (Ocean)
Hamburg Sud · X12 004010
Hamburg Sud’s published 315 specification, rendered as an interactive guide. Expand any segment to see its elements, data types, lengths and accepted codes — then validate your own document against it below.
Specification
8 of 8 segments
HEADING
ST
Transaction Set Header ST
pos 010
Optional
max —
B4
Beginning Segment For Inquiry Or Reply B4
Example Syntax
B4***VD*20160526*2245**HASU*431617*L*45G1*DEHAM*UN*0~
B4***VD*20160526*2245**HASU*431617*L*45G1*JACKSONVILLE, FL,
US*CI*0~
pos 020
Required
max —
N9
Reference Identification N9
Example Syntax
N9*BN*6PHLSA1234~
N9*IB*82564523**20160523*224521*LT~
pos 030
Required
max 30
Q2
Status Details Ocean Q2
Example Syntax
Q2*9449160*DE*******371S***L*CAP SAN MARCO~
pos 040
Optional
max —
R4 Looprequired
R4
Port Or Terminal R4
Example Syntax
R4*L*UN*DEHAM*Hamburg*DE~
R4*I*CI*N/A*CSX NORTHWEST OHIO RAMP~
pos 060
Required
max —
DTM
Actualvariant 1 of 2
Example Syntax
DTM*139*20160526*224529
pos 070
Optional
max 15
DTM
Estimatedvariant 2 of 2
Example Syntax
DTM*139*20160526*224529
pos 070
Optional
max 15
SE
Transaction Set Trailer SE
pos 090
Optional
max —
Validate a 315
Paste or upload a document and check it against Hamburg Sud’s published rules — segment order and repetition, required elements, field lengths, data types and accepted codes. Nothing is stored.
Go live on Hamburg Sud’s 315 in days, not months
Weredi maps this guide to your ERP, runs the test cycle with Hamburg Sud, and keeps the spec current as it changes.