315 Status Details (Ocean)

Functional Group ID=

QO

Introduction:
This Standard contains the format and establishes the data contents of the Status Details (Ocean) Transaction Set
(315) for use within the context of the CSAV 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.
Pos.
No.

Seg.
ID

Name

Req.
Des.

M
M
M
M
M

001
002
010
020
030
040
050

ISA
GS
ST
B4
N9
Q2
SG

Interchange Control Header

Functional Group Header
Transaction Set Header
Beginning Segment for Inquiry or Reply
Reference Identification
Status Details (Ocean)
Shipment Status

M
M
M
M
M
O
O

1
1
1
1
30
1
1

060
070

R4
DTM

LOOP ID - R4
Port or Terminal
Date/Time Reference

M
O

1
15

M
M
M

090
091
092

SE
GE
IEA

Transaction Set Trailer

Functional Group Trailer
Interchange Control Trailer

M
M
M

1
1
1

315 (004010)

Max.Use

Loop
Repeat

Notes and
Comments

20

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:

ISA Interchange Control Header

001
Mandatory
1
To start and identify an interchange of zero or more functional groups and interchangerelated control segments

Syntax Notes:
Semantic Notes:
Comments:

Ref.
Des.
ISA01

ISA02

ISA03

ISA04

ISA05

ISA06

ISA07

ISA08

ISA09

ISA10

ISA11

ISA12

315 (004010)

Data Element Summary

Data
Element Name
Attributes
I01
Authorization Information Qualifier
M ID 2/2
Code to identify the type of information in the Authorization Information
Set to '00' No Authorization information present
I02
Authorization Information
M AN 10/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)
Set to 10 empty spaces
I03
Security Information Qualifier
M ID 2/2
Code to identify the type of information in the Security Information
Set to '00' No Security information present
I04
Security Information
M AN 10/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)
Set to 10 empty spaces
I05
Interchange ID Qualifier
M ID 2/2
Qualifier to designate the system/method of code structure used to designate
the sender or receiver ID element being qualified
Set to 'ZZ' Mutually defined
I06
Interchange Sender ID
M AN 15/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
Follow Interchange Sender ID_TEST with empty spaces to fill 15 characters
I05
Interchange ID Qualifier
M ID 2/2
Qualifier to designate the system/method of code structure used to designate
the sender or receiver ID element being qualified
Set to 'ZZ' Mutually defined
I07
Interchange Receiver ID
M AN 15/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
Set to TradingPartner Code followed by 8 empty spaces
I08
Interchange Date
M DT 6/6
Date of the interchange
I09
Interchange Time
M TM 4/4
Time of the interchange
I10
Interchange Control Standards Identifier
M ID 1/1
Code to identify the agency responsible for the control standard used by the
message that is enclosed by the interchange header and trailer
Set to 'U' U.S. EDI Community of ASC X12, TDCC, and UCS
I11
Interchange Control Version Number
M ID 5/5
2

August 29, 2001

ISA13

I12

ISA14

I13

ISA15

I14

ISA16

I15

315 (004010)

This version number covers the interchange control segments

Set to '00401' Draft Standards approved for publication by ASC X12
Interchange Control Number
M N0 9/9
A control number assigned by the interchange sender
Acknowledgment Requested
M ID 1/1
Code sent by the sender to request an interchange acknowledgment (TA1)
Set to '0' No Acknowledgement requested
Usage Indicator
M ID 1/1
Code to indicate whether data enclosed by this interchange envelope is test,
production or information
Set to 'T' Test
Component Element Separator
M AN 1/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
Set to '>'

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:

Comments:

Ref.
Des.
GS01

GS02

GS03

GS04

GS05

GS06

GS07

GS08

315 (004010)

GS Functional Group Header

002
Mandatory
1
To indicate the beginning of a functional group and to provide control information
1
2
3
1

GS04 is the group date.

GS05 is the group time.
The data interchange control number GS06 in this header must be identical to the
same data element in the associated functional group trailer, GE02.
A functional group of related transaction sets, within the scope of X12 standards,
consists of a collection of similar transaction sets enclosed by a functional group
header and a functional group trailer.

Data Element Summary

Data
Element Name
Attributes
479
Functional Identifier Code
M ID 2/2
Code identifying a group of application related transaction sets
Set to 'QO' Ocean Shipment Status Information (313, 315)
142
Application Sender's Code
M AN 2/15
Code identifying party sending transmission; codes agreed to by trading
partners
124
Application Receiver's Code
M AN 2/15
Code identifying party receiving transmission; codes agreed to by trading
partners
Set to Trading Partner code
373
Date
M DT 8/8
Date expressed as CCYYMMDD
337
Time
M TM 4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or
HHMMSSD, or HHMMSSDD.
28
Group Control Number
M N0 1/9
Assigned number originated and maintained by the sender
455
Responsible Agency Code
M ID 1/2
Code used in conjunction with Data Element 480 to identify the issuer of the
standard
Set to 'X' Accredited Standards Committee X12
480
Version / Release / Industry Identifier Code
M AN 1/12
Code indicating the version, release, subrelease, and industry identifier of the
EDI standard being used.
Set to '004010'

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:

ST Transaction Set Header

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

The transaction set identifier (ST01) is used by the translation routines of the
interchange partners to select the appropriate transaction set definition (e.g., 810
selects the Invoice Transaction Set).

Comments:

Ref.
Des.
ST01

ST02

315 (004010)

Data Element Summary

Data
Element Name
Attributes
143
Transaction Set Identifier Code
M ID 3/3
Code uniquely identifying a Transaction Set
Set to '315'
329
Transaction Set Control Number
M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:

Ref.
Des.
B403

B404
B405
B406

315 (004010)

B4 Beginning Segment for Inquiry or Reply

020
Mandatory
1
To transmit identifying numbers, dates, and other basic data relating to the transaction set
1 If either B407 or B408 is present, then the other is required.
2 If either B411 or B412 is present, then the other is required.
1 B404 is the date of last reported status of cargo.
Status Code needs to be agree with CSAV. Not always are present worldwide.
Data Element Summary
Data
Element Name
Attributes
157
Shipment Status Code
M ID 1/2
Code indicating the status of a shipment
UV (Unloaded from Vessel)
EE (Empty Equipment Dispatched)
I (In - Gate)
OA (Out - Gate)
AE (Loaded on Vessel)
AE (Loaded on Vessel)
CO (Cargo Received at Contractual Place of Receipt)
VD (Vessel Departure)
AV (Available for Delivery)
CT (Customs Released)
CR (Carrier Release)
VA (Vessel Arrival) * Not implemented by Csav yet
VD (Vessel Departure) * Not implemented by Csav yet
373
Date
M DT 8/8
Event Date expressed as CCYYMMDD
161
Status Time
M TM 4/4
Event Time (HHMM) of last reported status of cargo
159
Status Location
M AN 3/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 - UNLOCODE can also be
placed in the B411 field and corresponding UNLOCODE Qualifier can be
placed in B412
Event Location Code (UNLOCODE, Schedule D or K Code, Carrier defined
Location Code)

B407

206

B408

207

B409

578

B411

310

Equipment Initial
C AN 1/4
Prefix or alphabetic part of an equipment unit's identifying number
Container Prefix
Equipment Number
C AN 1/10
Sequencing or serial part of an equipment unit's identifying number (pure
numeric form for equipment number is preferred)
Container Number (We would prefer to have the container number placed in
the N901).
Equipment Status Code
M ID 1/2
Code indicating status of equipment
L (Load)
E (Empty)
Location Identifier
M AN 1/30
6

August 29, 2001

B412

315 (004010)

309

Code which identifies a specific location

Event City Name or UNLOCODE
Location Qualifier
Code identifying type of location
CI (City Name qualifier), or UNLOCODE Qualifier

ID 1/2

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

315 (004010)

Ref.
Des.
N901

N9 Reference Identification
030
Mandatory
30
To transmit identifying information as specified by the Reference Identification Qualifier
1 At least one of N902 or N903 is required.
Data Element Summary
Data
Element Name
Attributes
128
Reference Identification Qualifier
M ID 2/3
Code qualifying the Reference Identification - 3 N901s are required (BN or
BM, 4F, EQ)
BN (Booking Number Qualifier)
4F (Carrier-Assigned Shipper Number Qualifier)
ZZ (Mutually Defined Qualifier) *Note: Can also come from ISA05*
BM (Bill of Lading Number Qualifier)
EQ Equipment Number

N902

127

N903

369

Reference Identification
C AN 1/30
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier - 3 N902s are required
(Booking number or Bill of Lading Number, Customer ID, Equipment
Number)
If N901 = BN then this field should be set to the Booking Number
If N901 = 4F then this field should be set to the Customer ID
If N901 = ZZ then this field should be set to the Carrier *Note: Can also come
from ISA06*
If N901 = BM then this field should be set to the Bill of Lading Number
If N901 = EQ then this field should be set to the Equipment Number
Free Form Description
C AN 1/45

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:

Q2 Status Details (Ocean)

040
Optional
1
To transmit identifying information relative to identification of vessel, transportation
dates, lading quantity, weight, and cube
1 If any of Q207 Q208 or Q216 is present, then all are required.
2 If Q210 is present, then Q211 is required.
3 If either Q214 or Q215 is present, then the other is required.
1 Q202 is the code identifying the country in which the ship (vessel) is registered.
2 Q203 is the required pier date.
3 Q204 is the date of departure of the vessel.
4 Q205 is the date the shipment was unloaded from the vessel.

Comments:

Ref.
Des.
Q201
Q202
Q209

Q210
Q211
Q212

Q213

315 (004010)

Data Element Summary

Data
Element Name
Attributes
597
Vessel Code
O ID 1/8
Vessel Lloyds code
26
Country Code
O ID 2/3
ISO Country Code (2 digit) of Vessel Registry
55
Flight/Voyage Number
O AN 2/10
Identifying designator for the particular flight or voyage on which the cargo
travels
Voyage Number
128
Reference Identification Qualifier
O ID 2/3
ZZ (Mutually Defined Qualifier)
127
Reference Identification
C AN 1/30
897
Vessel Code Qualifier
O ID 1/1
Code specifying vessel code source
L (Lloyd's Register of Shipping Qualifier)
Z (Mutually Defined Qualifier)
182
Vessel Name
O AN 2/28
Name of ship as documented in "Lloyd's Register of Ships"
Vessel Name

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Comments:

Ref.
Des.
SG01
SG02

315 (004010)

SG Shipment Status
050
Optional
1
To convey the status of a shipment
Included only on Carrier Releases
Data Element Summary
Data
Element Name
157
Shipment Status Code
CR (Carrier Release)
641
Status Reason Code
A65 (Customs Release)

10

Attributes
C ID 1/2
C

ID 3/3

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Ref.
Des.
R401

R402
R403
R404
R405
R408

315 (004010)

R4 Port or Terminal
060
R4

Mandatory

Mandatory
1
Contractual or operational port or point relevant to the movement of the cargo
If either R402 or R403 is present, then the other is required.
R401 is a required field. minimum of 4 R4s (R, L, D, E).
Data Element Summary
Data
Element Name
Attributes
115
Port or Terminal Function Code
M ID 1/1
Code defining function performed at the port or terminal with respect to a
shipment - A minimum of 4 R401s are required (R, L, D, E) to process the
message.
D (Port of Discharge)
E (Place of Delivery)
I (Interim Port)
L (Port of Loading)
R (Place of Receipt)
309
Location Qualifier
C ID 1/2
Location Code Qualifier identifies type of location
310
Location Identifier
M AN 1/30
Location Code (UNLOCODE, Schedule D or K Code, Carrier-defined
Location Code)
114
Port Name
O AN 2/24
City or Port Name free form name for the place at which an offshore carrier
originates or terminates its actual ocean carriage of property
26
Country Code
O ID 2/3
Country Code (2 Digit ISO)
156
State or Province Code
O ID 2/2
State Code as defined by appropriate government agency

11

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:

DTM Date/Time Reference

070
R4

Mandatory

Optional
15
To specify pertinent dates and times
1 At least one of DTM02 DTM03 or DTM05 is required.
2 If DTM04 is present, then DTM03 is required.
3 If either DTM05 or DTM06 is present, then the other is required.

Semantic Notes:
Comments:

Ref.
Des.
DTM01
DTM02
DTM03
DTM04
DTM05
DTM06

315 (004010)

Data Element Summary

Data
Element Name
Attributes
374
Date/Time Qualifier
M ID 3/3
Code specifying type of date or time, or both date and time
Set to '140' - Actual
373
Date
C DT 8/8
Event Date expressed as (CCYYMMDD)
337
Time
C TM 4/8
Event Time expressed as (HHMM)
623
Time Code
O ID 2/2
Time Zone Code code identifying the time
1250
Date Time Period Format Qualifier
C ID 2/3
Set to 'D8' - Date Expressed in Format CCYYMMDD Qualifier
1251
Date Time Period
C AN 1/35
Expression of a date, a time, or range of dates, times or dates and times

12

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Ref.
Des.
SE01

SE02

315 (004010)

SE Transaction Set Trailer

090
Mandatory
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)
1

SE is the last segment of each transaction set.

Data Element Summary

Data
Element Name
Attributes
96
Number of Included Segments
M N0 1/10
Number of Segments included in a transaction set including ST and SE
segments
329
Transaction Set Control Number
M AN 4/9
A unique Control Number used within the transaction set functional group
assigned by the originator for a transaction set

13

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:

Ref.
Des.
GE01

GE02

315 (004010)

GE Functional Group Trailer

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

The data interchange control number GE02 in this trailer must be identical to the
same data element in the associated functional group header, GS06.
The use of identical data interchange control numbers in the associated functional
group header and trailer is designed to maximize functional group integrity. The
control number is the same as that used in the corresponding header.

Data Element Summary

Data
Element Name
Attributes
97
Number of Transaction Sets Included
M N0 1/6
Total number of transaction sets included in the functional group or interchange
(transmission) group terminated by the trailer containing this data element
28
Group Control Number
M N0 1/9
Assigned number originated and maintained by the sender

14

August 29, 2001

Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:

IEA Interchange Control Trailer

092
Mandatory
1
To define the end of an interchange of zero or more functional groups and interchangerelated control segments

Syntax Notes:
Semantic Notes:
Comments:

Ref.
Des.
IEA01

IEA02

315 (004010)

Data Element Summary

Data
Element Name
Attributes
I16
Number of Included Functional Groups
M N0 1/5
A count of the number of functional groups included in an interchange
I12
Interchange Control Number
M N0 9/9
A control number assigned by the interchange sender

15

August 29, 2001