Flexport
/
Vessel Schedule and Itinerary (Ocean) (Carrier)
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Flexport. Contact Flexport for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Flexport logo

X12 323 Vessel Schedule and Itinerary (Ocean) (Carrier)

X12 Release 4010
Flexport Docs

This Draft Standard for Trial Use contains the format and establishes the data contents of the Vessel Schedule and Itinerary (Ocean) Transaction Set (323) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide all the information necessary for an ocean carrier to communicate the schedule and itinerary of an ocean vessel to interested parties.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/flexport/vessel-schedule-and-itinerary-ocean-carrier/01GGCWNJN4468TKBV10G0GW9KN
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
V1
020
Vessel Identification
Max use 1
Required
K1
030
Remarks
Max use 2
Optional
R4 Loop
SE
070
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

SO
Ocean Shipment Information (304, 306, 309, 311, 317, 319, 321, 322, 323, 324, 325, 350, 352, 353, 354, 355, 356, 357, 358, 361)
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).
323
Vessel Schedule and Itinerary (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

V1
020
Heading > V1

Vessel Identification

RequiredMax use 1

To provide vessel details and voyage number

Example
At least one of Vessel Code (V1-01) or Vessel Name (V1-02) is required
If Vessel Code Qualifier (V1-08) is present, then Vessel Code (V1-01) is required
V1-01
597
Vessel Code
Optional
Identifier (ID)
Min 1Max 8

Code identifying vessel

V1-02
182
Vessel Name
Optional
String (AN)
Min 2Max 28

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

V1-03
26
Country Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the country

  • V103 is the code identifying the country in which the ship (vessel) is registered.
V1-04
55
Flight/Voyage Number
Optional
String (AN)
Min 2Max 10

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

V1-05
140
Standard Carrier Alpha Code
Optional
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • V105 identifies the ocean carrier.
V1-06
249
Vessel Requirement Code
Optional
Identifier (ID)
Min 1Max 1

Code specifying options for satisfying vessel requirements

V1-07
854
Vessel Type Code
Optional
Identifier (ID)
Min 2Max 2

Code to determine type of vessel

V1-08
897
Vessel Code Qualifier
Optional
Identifier (ID)

Code specifying vessel code source

L
Lloyd's Register of Shipping
V1-09
91
Transportation Method/Type Code
Optional
Identifier (ID)

Code specifying the method or type of transportation for the shipment

A
Air
AC
Air Charter
AE
Air Express
AF
Air Freight
B
Barge
C
Consolidation
E
Expedited Truck
L
Contract Carrier
O
Containerized Ocean
Q
Conventional Ocean
R
Rail
RR
Roadrailer
S
Ocean
SB
Shipper Agent
SC
Shipper Agent (Truck)
SR
Supplier Truck
VE
Vessel, Ocean
W
Inland Waterway
X
Intermodal (Piggyback)
ZZ
Mutually defined
K1
030
Heading > K1

Remarks

OptionalMax use 2

To transmit information in a free-form format for comment or special instruction

Example
K1-01
61
Free-Form Message
Required
String (AN)
Min 1Max 30

Free-form information

R4 Loop
RequiredMax >1
R4
040
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)
I
Interim Point (Operational)
L
Port of Loading (Operational)
O
Origin (Operational)
R
Place of Receipt (Contractual)
T
Transshipment Port (Contractual)
R4-02
309
Location Qualifier
Optional
Identifier (ID)

Code identifying type of location

D
Census Schedule D
K
Census Schedule K
UN
United Nations Location Code (UNLOCODE)
ZZ
Mutually Defined
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)
Min 2Max 3

Code identifying the country

R4-06
174
Terminal Name
Optional
String (AN)
Min 2Max 30

Free-form field for terminal name

R4-07
113
Pier Number
Optional
String (AN)
Min 1Max 4

Identifying number for the pier

R4-08
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

Code (Standard State/Province) as defined by appropriate government agency

DTM
050
Heading > R4 Loop > DTM

Date/Time Reference

OptionalMax use 15

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

311
Latest Receiving Date/Cutoff Date
369
Estimated Departure Date
370
Actual Departure Date
371
Estimated Arrival Date
372
Actual Arrival Date
649
Document Due
ZZZ
Mutually Defined
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

V9
060
Heading > R4 Loop > V9

Event Detail

RequiredMax use 5

To specify information about a specific event

Example
V9-01
304
Event Code
Required
Identifier (ID)

Code identifying the event about which a report is made

AAD
Actual Arrival at POD
ARD
Actual Arrival Date at Final Destination
EAD
Estimated Arrival Date
EDD
Estimated Departure Date
ZZZ
Mutually Defined
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • V903 is the event date.
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)

  • V904 is the event time.
V9-14
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

  • V914 is the quantity of the fuel in gallons.
R4 Loop end
SE
070
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

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.