CSX
/
Intermodal container yard equipment booking
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from CSX. Contact CSX for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
CSX logo

X12 301 Intermodal container yard equipment booking

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Confirmation (Ocean) Transaction Set (301) 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 confirm space, container, and equipment availability in response to the Reservation (Booking Request) (Ocean) Transaction Set (300); or to notify other parties such as terminal operators or other ocean carriers.

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/csx/intermodal-container-yard-equipment-booking/01GTHGD3CN511YK8709XM0ZE8Z
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
B1
020
Beginning Segment for Booking or Pick-up/Delivery
Max use 1
Required
Y3
040
Space Confirmation
Max use 1
Required
Y4 Loop
R4 Loop
H3
140
Special Handling Instructions
Max use 6
Optional
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

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

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

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

02
SCAC (Standard Carrier Alpha Code)
ZZ
Mutually Defined
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

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

02
SCAC (Standard Carrier Alpha Code)
ZZ
Mutually Defined
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
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required

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

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

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

0
No 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

Code identifying a group of application related transaction sets

RO
Ocean Booking Information (300, 301,303)
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

GS-04
373
Date
Required
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
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

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

X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required

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

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).
301
Confirmation (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

B1
020
Heading > B1

Beginning Segment for Booking or Pick-up/Delivery

RequiredMax use 1

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

Example
B1-02
145
Shipment Identification Number
Required
String (AN)
Min 1Max 30

Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters)

B1-04
558
Reservation Action Code
Required

Code identifying action on reservation or offering

N
New
R
Delete
U
Change
Y3
040
Heading > Y3

Space Confirmation

RequiredMax use 1

To specify confirmation information for space booking including numbers, dates, and load time

Example
Y3-01
13
Booking Number
Required
String (AN)
Min 1Max 14

Number assigned by the carrier for space reservation

  • If space is available, all of the conditional data elements in segment Y3 are required. If the requested space is not available, Y301 is the booking number 'decline'.
Usage notes

CSX max length for the Booking Number is 14 bytes.

Y4 Loop
OptionalMax >1
Y4
050
Heading > Y4 Loop > Y4

Container Release

RequiredMax use 1

To transmit information relative to containers available for release

Example
Y4-01
13
Booking Number
Required
String (AN)
Min 1Max 17

Number assigned by the carrier for space reservation

  • Y401 is used for the first booking number and Y402 for the last booking number in a range of numbers. If only one booking number is used, Y402 is omitted.
Y4-02
13
Booking Number
Required
String (AN)
Min 1Max 17

Number assigned by the carrier for space reservation

Y4-03
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

  • Y403 is the date of container availability for pickup.
Usage notes

Pickup Date

Y4-05
95
Number of Containers
Required
Numeric (N0)
Min 1Max 4

Number of shipping containers

Y4-06
24
Equipment Type
Required
Identifier (ID)
Min 4Max 4

Code identifying equipment type

Usage notes

Must contain the AAR Car type. CSX does not process ISO codes.

Y4-07
140
Standard Carrier Alpha Code
Required
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • Y407 identifies the carrier to whom containers will be released, if known.
Y4 Loop end
N1
060
Heading > N1 Loop - Origin Drayman > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required

Code identifying an organizational entity, a physical location, property or an individual

OR
Origin Drayman
N1-02
93
Name
Optional
String (AN)
Min 1Max 30

Free-form name

N1 Loop - Origin Drayman end
N1 Loop - Shipper
OptionalMax >1
Variants (all may be used)
N1 Loop - Origin Drayman
N1
060
Heading > N1 Loop - Shipper > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
N1-01
98
Entity Identifier Code
Required

Code identifying an organizational entity, a physical location, property or an individual

SH
Shipper
N1-02
93
Name
Optional
String (AN)
Min 1Max 30

Free-form name

N1 Loop - Shipper end
R4 Loop
RequiredMax >1
R4
110
Heading > R4 Loop > R4

Port or Terminal

RequiredMax use 1

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

Example
R4-01
115
Port or Terminal Function Code
Required

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

5
Activity Location (Operational)
R4-02
309
Location Qualifier
Required

Code identifying type of location

SL
U.S. SPLC
R4-03
310
Location Identifier
Required
String (AN)
Min 1Max 30

Code which identifies a specific location

Usage notes

Must contain the CSX SPLC for the terminal where you are sending the booking. CSX can provide a SPLC list if needed.

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

Usage notes

CSX recommends you send the Name of the terminal for the Booking.

DTM
120
Heading > R4 Loop > DTM

Date/Time Reference

OptionalMax use 15

To specify pertinent dates and times

Usage notes

Segment is optional, current date and time will default if not passed within this segment

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

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

DTM-02
373
Date
Optional
CCYYMMDD format

Date expressed as CCYYMMDD

DTM-03
337
Time
Optional
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
H3
140
Heading > H3

Special Handling Instructions

OptionalMax use 6

To specify special handling instructions in coded or free-form format

Example
Only one of Special Handling Code (H3-01) or Special Handling Description (H3-02) may be present
H3-01
152
Special Handling Code
Optional
Identifier (ID)
Min 2Max 3

Code specifying special transportation handling instructions

H3-02
153
Special Handling Description
Optional
String (AN)
Min 2Max 30

Free-form additional description of special handling instructions to appear on printed bill if special handling code is not adequate

Heading end

Summary

SE
010
Summary > 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

Summary 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.