CEVA
/
Status Details (Ocean) (From Sample)
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from CEVA. Contact CEVA for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
CEVA logo

X12 315 Status Details (Ocean) (From Sample)

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Status Details (Ocean) Transaction Set (315) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary to report status or event details for selected shipments or containers. It is intended to accommodate the details for one status or event associated with many shipments or containers, as well as more than one status or event for one shipment or container.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Sample 1
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/ceva/status-details-ocean-from-sample/01HYNQ9TBG4ZD8PNSDX6GGQZ35
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
B4
020
Beginning Segment for Inquiry or Reply
Max use 1
Required
N9
030
Reference Identification Bill of Lading Number
Max use 30
Optional
N9
030
Reference Identification Consignee's Order Number
Max use 1
Required
N9
030
Reference Identification Forwarder's/Agent's Reference Number
Max use 1
Optional
Q2
040
Status Details (Ocean)
Max use 1
Optional
R4 Loop
SE
090
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

QO
Ocean Shipment Status Information (313, 315)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
315
Status Details (Ocean)
ST-02
329
Transaction Set Control Number
Required
Numeric (N0)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

B4
020
Heading > B4

Beginning Segment for Inquiry or Reply

RequiredMax use 1

To transmit identifying numbers, dates, and other basic data relating to the transaction set

Example
If either Equipment Initial (B4-07) or Equipment Number (B4-08) is present, then the other is required
B4-03
157
Shipment Status Code
Optional
Identifier (ID)

Code indicating the status of a shipment

C
Estimated To Depart Terminal Location
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • B404 is the date of last reported status of cargo.
B4-05
161
Status Time
Optional
Time (TM)
HHMM format

Time (HHMM) of last reported status of cargo

B4-06
159
Status Location
Required
String (AN)
Min 3Max 5

Air shipment: Airport code for last reported status for a shipment; (Note: If the shipment is in-flight, the status location is the origin airport for this flight) Ground transportation: Code of carrier's terminal

B4-07
206
Equipment Initial
Required
String (AN)
Min 1Max 4

Prefix or alphabetic part of an equipment unit's identifying number

B4-08
207
Equipment Number
Optional
String (AN)
Min 1Max 10

Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)

B4-09
578
Equipment Status Code
Optional
Identifier (ID)

Code indicating status of equipment

L
Load
B4-10
24
Equipment Type
Optional
Identifier (ID)
Min 4Max 4

Code identifying equipment type

N9
030
Heading > N9

Reference Identification Bill of Lading Number

OptionalMax use 30

To transmit identifying information as specified by the Reference Identification Qualifier

Example
Variants (all may be used)
N9Reference Identification Consignee's Order NumberN9Reference Identification Forwarder's/Agent's Reference Number
At least one of Reference Identification (N9-02) or Free-form Description (N9-03) is required
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

BM
Bill of Lading Number
N9-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N9-03
369
Free-form Description
Optional
String (AN)
Min 1Max 45

Free-form descriptive text

N9
030
Heading > N9

Reference Identification Consignee's Order Number

RequiredMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

Example
At least one of Reference Identification (N9-02) or Free-form Description (N9-03) is required
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

CG
Consignee's Order Number
N9-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N9-03
369
Free-form Description
Optional
String (AN)
Min 1Max 45

Free-form descriptive text

N9
030
Heading > N9

Reference Identification Forwarder's/Agent's Reference Number

OptionalMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

Example
At least one of Reference Identification (N9-02) or Free-form Description (N9-03) is required
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

FN
Forwarder's/Agent's Reference Number
N9-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N9-03
369
Free-form Description
Optional
String (AN)
Min 1Max 45

Free-form descriptive text

Q2
040
Heading > Q2

Status Details (Ocean)

OptionalMax use 1

To transmit identifying information relative to identification of vessel, transportation dates, lading quantity, weight, and cube

Example
If either Weight (Q2-07), Weight Qualifier (Q2-08) or Weight Unit Code (Q2-16) are present, then the others are required
If Reference Identification Qualifier (Q2-10) is present, then Reference Identification (Q2-11) is required
If either Volume (Q2-14) or Volume Unit Qualifier (Q2-15) is present, then the other is required
Q2-01
597
Vessel Code
Optional
Identifier (ID)
Min 1Max 8

Code identifying vessel

Q2-06
80
Lading Quantity
Optional
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

Q2-07
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

Q2-08
187
Weight Qualifier
Optional
Identifier (ID)

Code defining the type of weight

G
Gross Weight
Q2-09
55
Flight/Voyage Number
Optional
String (AN)
Min 2Max 10

Identifying designator for the particular flight or voyage on which the cargo travels

Q2-10
128
Reference Identification Qualifier
Optional
Identifier (ID)

Code qualifying the Reference Identification

SCA
Standard Carrier Alpha Code (SCAC)
Q2-11
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Q2-12
897
Vessel Code Qualifier
Optional
Identifier (ID)

Code specifying vessel code source

L
Lloyd's Register of Shipping
Q2-13
182
Vessel Name
Optional
String (AN)
Min 2Max 28

Name of ship as documented in "Lloyd's Register of Ships"

Q2-14
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

Q2-15
184
Volume Unit Qualifier
Optional
Identifier (ID)

Code identifying the volume unit

X
Cubic Meters
Q2-16
188
Weight Unit Code
Optional
Identifier (ID)

Code specifying the weight unit

K
Kilograms
R4 Loop
RequiredMax 20
R4
060
Heading > R4 Loop > R4

Port or Terminal

RequiredMax use 1

Contractual or operational port or point relevant to the movement of the cargo

Example
If either Location Qualifier (R4-02) or Location Identifier (R4-03) is present, then the other is required
R4-01
115
Port or Terminal Function Code
Required
Identifier (ID)

Code defining function performed at the port or terminal with respect to a shipment

D
Port of Discharge (Operational)
E
Place of Delivery (Contractual)
L
Port of Loading (Operational)
R
Place of Receipt (Contractual)
R4-02
309
Location Qualifier
Optional
Identifier (ID)

Code identifying type of location

UN
United Nations Location Code (UNLOCODE)
R4-03
310
Location Identifier
Optional
String (AN)
Min 1Max 30

Code which identifies a specific location

R4-04
114
Port Name
Optional
String (AN)
Min 2Max 24

Free-form name for the place at which an offshore carrier originates or terminates (by transshipment or otherwise) its actual ocean carriage of property

R4-05
26
Country Code
Optional
Identifier (ID)

Code identifying the country

CA
Canada
CN
China
US
United States of America (the)
DTM
070
Heading > R4 Loop > DTM

Date/Time Reference Estimated Arrival Date

OptionalMax use 1

To specify pertinent dates and times

Example
At least one of Date (DTM-02) or Time (DTM-03) is required
If Time Code (DTM-04) is present, then Time (DTM-03) is required
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

371
Estimated Arrival Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Optional
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

DTM-04
623
Time Code
Optional
Identifier (ID)

Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow

LT
Local Time
DTM
070
Heading > R4 Loop > DTM

Date/Time Reference Estimated Departure Date

OptionalMax use 15

To specify pertinent dates and times

Example
At least one of Date (DTM-02) or Time (DTM-03) is required
If Time Code (DTM-04) is present, then Time (DTM-03) is required
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

369
Estimated Departure Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Optional
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

DTM-04
623
Time Code
Optional
Identifier (ID)

Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow

LT
Local Time
R4 Loop end
SE
090
Heading > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N0)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Heading end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Sample 1

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240524*1635*U*00401*000000001*0*T*>~
GS*QO*SENDERGS*RECEIVERGS*20240524*163524*000000001*X*004010~
ST*315*23870001~
B4***C*20240603*0200*CNSHA*XXXX*5549724*L*0000~
N9*CG*15763648*Shipment Identification~
N9*FN*SZVB79205*Housebill Number~
N9*BM*XXXXSHA240506102*Bill of Lading Number~
Q2*9455870*****306*5355*G*101E*SCA*XXXX*L*YM MUTUALITY*23.05*X*K~
R4*D*UN*CAPRR*PRINCE RUPERT*CA~
R4*E*UN*USIND*INDIANAPOLIS*US~
DTM*371*20240614*1800*LT~
R4*L*UN*CNSHA*SHANGHAI*CN~
DTM*369*20240603*0200*LT~
R4*R*UN*CNSHA*SHANGHAI*CN~
SE*13*23870001~
GE*1*000000001~
IEA*1*000000001~

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.