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

X12 315 Status Details (Ocean)

X12 Release 3050

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
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/ford/status-details-ocean/01GY076JMSSR0V61FWYKJFFE77
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
Connecting Carrier
Max use 30
Required
N9
030
Shipper's Identifying Number for Shipment (SID)
Max use 30
Required
Q2
040
Status Details (Ocean)
Max use 1
Required
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)
Min 5Max 5

This version number covers the interchange control segments.

00200
Standard Issued as ANSI X12.5-1987
00201
Draft Standard for Trial Use Approved by ASC X12 Through August 1988
00204
Draft Standard for Trial Use Approved by ASC X12 Through May 1989
00300
Standard Issued as ANSI X12.5-1992
00301
Draft Standard for Trial Use Approved for Publication by ASC X12 Procedures Review Board Through October 1990
00302
Draft Standard for Trial Use Approved for Publication by ASC X12 Procedures Review Board Through October 1991
00303
Draft Standard for Trial Use Approved for Publication by ASC X12 Procedures Review Board Through October 1992
00304
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1993
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
Test Indicator
Required
Identifier (ID)
Min 1Max 1

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

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

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)
YYMMDD format

Date (YYMMDD).

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.

003050
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1994

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
X12.122 Status Details (Ocean)
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
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

Usage notes

Example: B4~~~A

Example
B4-03
157
Status Code
Optional
Identifier (ID)

Code indicating the status of a shipment

A
Arrived

Shipment has arrived at the location specified.

P
Departed Terminal Location

Shipment has left the carrier's terminal or other control point.

N9
030
Heading > N9

Connecting Carrier

RequiredMax use 30

To transmit identifying numbers and descriptive information as specified by the reference number qualifier

Usage notes

Example: N9ZCABCD

Example
Variants (all may be used)
N9Shipper's Identifying Number for Shipment (SID)
N9-01
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

ZC
Connecting Carrier
N9-02
127
Reference Number
Optional
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

N9
030
Heading > N9

Shipper's Identifying Number for Shipment (SID)

RequiredMax use 30

To transmit identifying numbers and descriptive information as specified by the reference number qualifier

Usage notes

Example: N9SI442995.128154

Example
Variants (all may be used)
N9Connecting Carrier
N9-01
128
Reference Number Qualifier
Required
Identifier (ID)

Code qualifying the Reference Number.

SI
Shipper's Identifying Number for Shipment (SID)

A unique number (to the shipper) assigned by the shipper to identify the shipment.

N9-02
127
Reference Number
Optional
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

Q2
040
Heading > Q2

Status Details (Ocean)

RequiredMax use 1

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

Usage notes

Example: Q2~~~~~~~~~~AW~9360534912

Example
Q2-10
128
Reference Number Qualifier
Optional
Identifier (ID)

Code qualifying the Reference Number.

AW
Air Waybill Number
Q2-11
127
Reference Number
Optional
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

R4 Loop
RequiredMax >1
R4
060
Heading > R4 Loop > R4

Port

RequiredMax use 1

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

Usage notes

Example: R4D~~~SAN SALVADORSV

Example
R4-01
115
Port Function Code
Required
Identifier (ID)

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

D
Port of Discharge (Operational)
L
Port of Loading (Operational)
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)
Min 2Max 3

Code identifying the country.

DTM
070
Heading > R4 Loop > DTM

Actual Port of Entry

RequiredMax use 15

To specify pertinent dates and times

Usage notes

Example: DTM057030529~1442

Example
Variants (all may be used)
DTMShipped
At least one of Date (DTM-02) or 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.

057
Actual Port of Entry
Optional
Date (DT)
YYMMDD format

Date (YYMMDD).

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
070
Heading > R4 Loop > DTM

Shipped

RequiredMax use 15

To specify pertinent dates and times

Usage notes

Example: DTM011030529~1943

Example
Variants (all may be used)
DTMActual Port of Entry
At least one of Date (DTM-02) or 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.

011
Shipped
Optional
Date (DT)
YYMMDD format

Date (YYMMDD).

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)

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 (N)
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

B4***A~
N9*SI*442995.128154~
N9*ZC*ABCD~
Q2**********AW*9360534912~
R4*D***SAN SALVADOR*SV~
DTM*011*030529*1943~
DTM*057*030529*1442~

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.