Mediterranean Shipping Company (MSC)
/
Reservation (Booking Request) (Ocean)
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Mediterranean Shipping Company (MSC). Contact Mediterranean Shipping Company (MSC) for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Mediterranean Shipping Company (MSC) logo

X12 300 Reservation (Booking Request) (Ocean)

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Reservation (Booking Request) (Ocean) Transaction Set (300) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a shipper or a forwarder to reserve space, containers and equipment for transport by ocean vessel.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
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
G61
025
Contact
Max use 3
Required
Y1
050
Space Reservation Request
Max use 1
Required
Y2 Loop
N9
069
Reference Identification
Max use 100
Optional
N1 Loop
W09
150
Equipment and Temperature
Max use 1
Optional
H3
160
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
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
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
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
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
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
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
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
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
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
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
Min 2Max 15

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

GS-03
124
Application Receiver's Code
Required
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
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
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

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

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).
300
Reservation (Booking Request) (Ocean)
ST-02
329
Transaction Set Control Number
Required
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

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

G61
025

Contact

RequiredMax use 3

To identify a person or office to whom communications should be directed

Example
G61-01
366
Contact Function Code
Required
Min 2Max 2

Code identifying the major duty or responsibility of the person or group named

G61-02
93
Name
Required
Min 1Max 60

Free-form name

Y1
050

Space Reservation Request

RequiredMax use 1

To specify information used to make a reservation for space on an ocean vessel

Example
Y2 Loop
OptionalMax >1
Y2
060

Container Details

RequiredMax use 1

To specify container information and transportation service to be used

Example
Y2-01
95
Number of Containers
Required
Min 1Max 4

Number of shipping containers

Y2-04
24
Equipment Type
Required
Min 4Max 4

Code identifying equipment type

N9
069

Reference Identification

OptionalMax use 100

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
Min 2Max 3

Code qualifying the Reference Identification

N1 Loop
RequiredMax >1
N1
080

Name

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required
Min 2Max 3

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

N3
100

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
Min 1Max 55

Address information

N4
110

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
G61
120

Contact

OptionalMax use 3

To identify a person or office to whom communications should be directed

Example
G61-01
366
Contact Function Code
Required
Min 2Max 2

Code identifying the major duty or responsibility of the person or group named

G61-02
93
Name
Required
Min 1Max 60

Free-form name

R4 Loop
RequiredMax >1
R4
130

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
Min 1Max 1

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

DTM
140

Date/Time Reference

OptionalMax use 15

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Min 3Max 3

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

W09
150

Equipment and Temperature

OptionalMax use 1

To relate equipment type and required temperatures

Example
W09-01
40
Equipment Description Code
Required
Min 2Max 2

Code identifying type of equipment used for shipment

H3
160

Special Handling Instructions

OptionalMax use 6

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

Example

Detail

LX Loop
RequiredMax >1
LX
010

Assigned Number

RequiredMax use 1

To reference a line number in a transaction set

Example
LX-01
554
Assigned Number
Required
Min 1Max 6

Number assigned for differentiation within a transaction set

N7
020

Equipment Details

OptionalMax use 1

To identify the equipment

Example
N7-02
207
Equipment Number
Required
Min 1Max 10

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

W09
021

Equipment and Temperature

OptionalMax use 1

To relate equipment type and required temperatures

Example
W09-01
40
Equipment Description Code
Required
Min 2Max 2

Code identifying type of equipment used for shipment

DTM
030

Date/Time Reference

OptionalMax use 1

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Min 3Max 3

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

L0
040

Line Item - Quantity and Weight

RequiredMax use 1

To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data

Example
L5
050

Description, Marks and Numbers

RequiredMax use 1

To specify the line item in terms of description, quantity, packaging, and marks and numbers

Example
L4
060

Measurement

OptionalMax use 1

To describe physical dimensions and quantities

Example
L4-01
82
Length
Required
Min 1Max 8

Largest horizontal dimension of an object measured when the object is in the upright position

L4-02
189
Width
Required
Min 1Max 8

Shorter measurement of the two horizontal dimensions measured with the object in the upright position

L4-03
65
Height
Required
Min 1Max 8

Vertical dimension of an object measured when the object is in the upright position

L4-04
90
Measurement Unit Qualifier
Required
Min 1Max 1

Code specifying the linear dimensional unit

H1 Loop
RequiredMax >1
H1
070

Hazardous Material

RequiredMax use 1

To specify information relative to hazardous material

Example
H1-01
62
Hazardous Material Code
Required
Min 4Max 10

Code relating to hazardous material code qualifier for regulated hazardous materials

H2
080

Additional Hazardous Material Description

OptionalMax use 10

To specify free-form hazardous material descriptive data in addition to the information provided in the H1 segment

Example
H2-01
64
Hazardous Material Description
Required
Min 2Max 30

Material name, special instructions, and phone number if any

V1
090

Vessel Identification

OptionalMax use 2

To provide vessel details and voyage number

Example
K1
110

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
Min 1Max 30

Free-form information

Summary

SE
010

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
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
Min 4Max 9

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

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
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
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
Min 1Max 5

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

IEA-02
I12
Interchange Control Number
Required
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.