CEVA
/
Reservation (Booking Request) (Ocean) (From Sample)
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from CEVA. Contact CEVA for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
CEVA logo

X12 300 Reservation (Booking Request) (Ocean) (From Sample)

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 sample
  • Sample 1
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/ceva/reservation-booking-request-ocean-from-sample/01HYNNS841T8FK6EVACZNNAZ2S
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
Y1
050
Space Reservation Request
Max use 1
Required
Y2 Loop
N9
069
Reference Identification
Max use 100
Optional
N1 Loop Consignee
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

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

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).
300
Reservation (Booking Request) (Ocean)
ST-02
329
Transaction Set Control Number
Required
Numeric (N0)
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-01
140
Standard Carrier Alpha Code
Optional
Identifier (ID)
Min 2Max 4

Standard Carrier Alpha Code

  • B101 is the Standard Carrier Alpha Code (SCAC) of the carrier sending the EDI transmission.
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
Optional
Identifier (ID)

Code identifying action on reservation or offering

N
New
Y1
050
Heading > Y1

Space Reservation Request

RequiredMax use 1

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

Example
If either Date (Y1-02) or Date/Time Qualifier (Y1-09) is present, then the other is required
Y1-01
135
Sailing/Flight Date Estimated
Optional
Date (DT)
CCYYMMDD format

Date for reservation expressed in format CCYYMMDD

Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • Y102 is the date the shipment for which space reservation is requested to be available at the origin.
Y1-08
375
Tariff Service Code
Optional
Identifier (ID)

Code specifying the types of services for rating purposes

DD
Door-to-Door
Y1-09
374
Date/Time Qualifier
Optional
Identifier (ID)

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

063
Do Not Deliver After
Y2 Loop
OptionalMax 10
Y2
060
Heading > Y2 Loop > Y2

Container Details

RequiredMax use 1

To specify container information and transportation service to be used

Example
Y2-01
95
Number of Containers
Required
Numeric (N0)
Min 1Max 4

Number of shipping containers

Y2-04
24
Equipment Type
Required
Identifier (ID)
Min 4Max 4

Code identifying equipment type

Y2 Loop end
N9
069
Heading > N9

Reference Identification

OptionalMax use 100

To transmit identifying information as specified by the Reference Identification Qualifier

Example
N9-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

Usage notes

CG variant is a required unique number for CEVA.

CG
Consignee's Order Number
PK
Packing List Number
PT
Purchase Option Agreement
ZZ
Mutually Defined
N9-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

N1 Loop Consignee
RequiredMax 10
Variants (all may be used)
N1 Loop Shipper
N1
080
Heading > N1 Loop Consignee > N1

Name

RequiredMax use 1

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

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

CN
Consignee
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

ZZ
Mutually Defined
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
N3
100
Heading > N1 Loop Consignee > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N4
110
Heading > N1 Loop Consignee > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Optional
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

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

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Optional
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Optional
Identifier (ID)

Code identifying the country

CHN
China
USA
United States of America (the)
N1 Loop Consignee end
N1 Loop Shipper
RequiredMax 1
Variants (all may be used)
N1 Loop Consignee
N1
080
Heading > N1 Loop Shipper > N1

Name

RequiredMax use 1

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

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

SH
Shipper
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

ZZ
Mutually Defined
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
N3
100
Heading > N1 Loop Shipper > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N4
110
Heading > N1 Loop Shipper > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Optional
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

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

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Optional
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Optional
Identifier (ID)

Code identifying the country

CHN
China
USA
United States of America (the)
N1 Loop Shipper end
R4 Loop
RequiredMax 20
R4
130
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)
L
Port of Loading (Operational)
R
Place of Receipt (Contractual)
R4-02
309
Location Qualifier
Optional
Identifier (ID)

Code identifying type of location

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 Loop end
Heading end

Detail

LX Loop
RequiredMax 999
LX
010
Detail > LX Loop > LX

Assigned Number

RequiredMax use 1

To reference a line number in a transaction set

Example
LX-01
554
Assigned Number
Required
Numeric (N0)
Min 1Max 6

Number assigned for differentiation within a transaction set

L0
040
Detail > LX Loop > L0

Line Item - Quantity and Weight

OptionalMax use 1

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

Example
If either Weight (L0-04) or Weight Qualifier (L0-05) is present, then the other is required
If Weight Unit Code (L0-11) is present, then Weight (L0-04) is required
If either Volume (L0-06) or Volume Unit Qualifier (L0-07) is present, then the other is required
If either Lading Quantity (L0-08) or Packaging Form Code (L0-09) is present, then the other is required
L0-04
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

L0-05
187
Weight Qualifier
Optional
Identifier (ID)

Code defining the type of weight

G
Gross Weight
L0-06
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

L0-07
184
Volume Unit Qualifier
Optional
Identifier (ID)

Code identifying the volume unit

X
Cubic Meters
L0-08
80
Lading Quantity
Optional
Numeric (N0)
Min 1Max 7

Number of units (pieces) of the lading commodity

  • L008 is the number of handling units of the line item tendered to the carrier.
L0-09
211
Packaging Form Code
Optional
Identifier (ID)

Code for packaging form of the lading quantity

PCS
Pieces
L0-11
188
Weight Unit Code
Optional
Identifier (ID)

Code specifying the weight unit

K
Kilograms
LX Loop end
Detail 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 (N0)
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

EDI Samples

Sample 1

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240524*1627*U*00401*000000001*0*T*>~
GS*RO*SENDERGS*RECEIVERGS*20240524*162742*000000001*X*004010~
ST*300*0095~
B1*SCAC*15763648**N~
Y1*20240528*20240715******DD*063~
Y2*1***40GP~
N9*PK*4170042169 4170041928 41700419~
N9*CG*15763648~
N9*PT*FCL~
N9*ZZ*FCA~
N1*SH*Altek Biotechnology Co., Ltd.*ZZ*1000012694~
N3*NO.77, 3RD MAIN STREET, KUNSHAN FREE TRADE ZONE~
N4*Kun-Shan**215301*CHN~
N1*CN*Care Inc Indianapolis*ZZ*1000582366~
N3*Building W5 Warehouse, 9115 Hague Road~
N4*Indianapolis*IN*46250*USA~
R4*R*ZZ*1000012694*Altek Biotechnology Co.~
R4*L*UN*CNSHA*Port of Shanghai~
R4*D*UN*USIND*Port of Indianapolis~
R4*E*ZZ*1000582366*Care Inc I~
LX*1~
L0****315*G*1.36*X*17*PCS**K~
SE*21*0095~
GE*1*000000001~
IEA*1*000000001~

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.