Revised 11/15/17 Booking Confirmation EDI 301. Booking Confirmation. ANSI X Revised 11/15/17

Transcription

1 EDI 301 Booking Confirmation ANSI X Revised 11/15/17 Contact Information: EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

2 Table of Contents 301 Reservation (Booking Request) (Ocean)... 3 ISA Interchange Control Header GS Functional Group Header... 6 ST Transaction Set Header... 7 B1 Beginning Segment for Booking or Pick-up/Delivery... 8 G61 Contact... 9 Y3 Space Confirmation Y4 Loop Y Y4 Container Release N9 Reference Identification N1 Loop N N1 Name N4 Geographic Location R4 Loop R R4 Port or Terminal DTM Date/Time Reference LX Loop LX LX Assigned Number L0 Line Item - Quantity and Weight L5 Description, Marks and Numbers V1 Vessel Identification V9 Event Detail...25 SE Transaction Set Trailer GE Functional Group Trailer IEA Interchange Control Trailer Sample Data...29 EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

3 301 Confirmation (Ocean) Functional Group=RO This Draft Standard for Trial Use contains the format and establishes the data contents of the Confirmation (Ocean) Transaction Set (301) for within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be d 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. Not Defined: Pos Id Segment Name Req Max Use Repeat Notes Usage ISA Interchange Control Header M 1 Must GS Functional Group Header M 1 Must Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage 010 ST Transaction Set Header M 1 Must 020 B1 Beginning Segment for Booking or Pickup/Delivery M 1 Must 025 G61 Contact O 3 Used 030 Y6 Authentication O 2 Used 040 Y3 Space Confirmation M 1 Must LOOP ID - Y Y4 Container Release O 1 Used 054 N9 Reference Identification O 100 Used LOOP ID - N N1 Name O 1 Used 070 N2 Additional Name Information O 1 Used 080 N3 Address Information O 2 Used 090 N4 Geographic Location O 1 Used 100 G61 Contact O 3 Used LOOP ID - R R4 Port or Terminal M 1 Must 120 DTM Date/Time Reference O 15 Used Detail: Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - LX LX Assigned Number M 1 Must 020 N7 Equipment Details O 1 Used 021 W09 Equipment and Temperature O 1 Used 030 K1 Remarks O 10 Used 040 L0 Line Item - Quantity and Weight O 1 Used 050 L5 Description, Marks and Numbers O 1 Used LOOP ID - H H1 Hazardous Material M 1 Must 080 H2 Additional Hazardous O 10 Used 080 V1 Vessel Identification O 2 Used 090 V9 Event Detail O 10 Used Summary: Pos Id Segment Name Req Max Use Repeat Notes Usage 010 SE Transaction Set Trailer M 1 Must Not Defined: Pos Id Segment Name Req Max Use Repeat Notes Usage GE Functional Group Trailer M 1 Must IEA Interchange Control Trailer M 1 Must EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

4 ISA Interchange Control Header Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 16 User Option (Usage): Must To start and identify an interchange of zero or more functional groups and interchange-related control segments ISA01 I01 Authorization Information Qualifier M ID 2/2 Must Description: Code identifying the type of information in the Authorization Information Code Name 00 No Authorization Information Present (No Meaningful Information in I02) ISA02 I02 Authorization Information M AN 10/10 Must Description: Information d 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) ISA03 I03 Security Information Qualifier M ID 2/2 Must Description: Code identifying the type of information in the Security Information Code Name 00 No Security Information Present (No Meaningful Information in I04) ISA04 I04 Security Information M AN 10/10 Must Description: This is d 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) ISA05 I05 Interchange ID Qualifier M ID 2/2 Must Description: Code indicating the system/method of code structure d to designate the sender or receiver ID element being qualified Code Name ZZ Mutually Defined ISA06 I06 Interchange Sender ID M AN 15/15 Must Description: Identification code published by the sender for other parties to as the receiver ID to route data to them; the sender always codes this value in the sender ID element ISA07 I05 Interchange ID Qualifier M ID 2/2 Must Description: Code indicating the system/method of code structure d to designate the sender or receiver ID element being qualified Code Name 14 Duns Plus Suffix ISA08 I07 Interchange Receiver ID M AN 15/15 Must Description: Identification code published by the receiver of the data; When sending, it is d by the sender as their sending ID, thus other parties sending to them will this as a receiving ID to route data to them Interchange Date M DT 6/6 Must ISA09 I08 Description: Date of the interchange ISA10 I09 Interchange Time M TM 4/4 Must Description: Time of the interchange ISA11 I65 Repetition Separator M AN 1/1 Must Description: Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter d to separate repeated occurrences of a simple EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

5 data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 I11 Interchange Control Version Number M ID 5/5 Must Description: Code specifying the version number of the interchange control segments Code Name Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997 ISA13 I12 Interchange Control Number M N0 9/9 Must Description: A control number assigned by the interchange sender ISA14 I13 Acknowledgment Requested M ID 1/1 Must Description: Code indicating sender's request for an interchange acknowledgment All valid standard codes are d. ISA15 I14 Interchange Usage Indicator M ID 1/1 Must Description: Code indicating whether data enclosed by this interchange envelope is test, production or information All valid standard codes are d. ISA16 I15 Component Element Separator M AN 1/1 Must Description: Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter d to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator Example: ISA ZZ SMLU ZZ YOUR SENDER ID U P >~ EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

6 GS Functional Group Header Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 8 User Option (Usage): Must To indicate the beginning of a functional group and to provide control information GS Functional Identifier Code M ID 2/2 Must Description: Code identifying a group of application related transaction sets GS Application Sender's Code M AN 2/15 Must Description: Code identifying party sending transmission; codes agreed to by trading partners GS Application Receiver's Code M AN 2/15 Must Description: Code identifying party receiving transmission; codes agreed to by trading partners GS Date M DT 8/8 Must Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year GS Time M TM 4/8 Must Description: 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) GS06 28 Group Control Number M N0 1/9 Must Description: Assigned number originated and maintained by the sender GS Responsible Agency Code M ID 1/2 Must Description: Code identifying the issuer of the standard; this code is d in conjunction with Data Element 480 Code Name X Accredited Standards Committee X12 GS Version / Release / Industry Identifier Code M AN 1/12 Must Description: Code indicating the version, release, subrelease, and industry identifier of the EDI standard being d, 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 r); if code in DE455 in GS segment is T, then other formats are allowed Code Name Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997 Example: GS RO SMLU YOUR SENDER ID X ~ Semantics: 1. GS04 is the group date. 2. GS05 is the group time. 3. The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. Comments: 1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

7 ST Transaction Set Header Pos: 010 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must To indicate the start of a transaction set and to assign a control number ST Transaction Set Identifier Code M ID 3/3 Must Description: Code uniquely identifying a Transaction Set Code Name 301 Confirmation (Ocean) ST Transaction Set Control Number M AN 4/9 Must Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Example: ST ~ Semantics: 1. The transaction set identifier (ST01) d by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 301 Booking Confirmation Transaction Set). EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

8 B1 Beginning Segment for Booking or Pick-up/Delivery Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 4 User Option (Usage): Must To transmit identifying numbers, dates, and other basic data relating to the transaction set B Standard Carrier Alpha Code O ID 2/4 Used Description: Standard Carrier Alpha Code B Shipment Identification Number M AN 1/30 Must Description: 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) B Date O DT 8/8 Used Description: Date expressed as CCYYMMDD B Reservation Action Code O ID 1/1 Used Description: Code identifying action on reservation or offering All valid standard codes are d. Example: B1 SMLU A~ Semantics: 1. B101 is the Standard Carrier Alpha Code (SCAC) of the carrier sending the EDI transmission. 2. B103 is the booking date accepted by the carrier. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

9 G61 Contact Pos: 100 Max: 3 Heading - Optional Loop: N1 Elements: 4 User Option (Usage): Used To identify a person or office to whom communications should be directed G Contact Function Code M ID 2/2 Must Description: Code identifying the major duty or responsibility of the person or group named. All valid standard codes are d. G Name M AN 1/60 Must Description: Free-form name G Communication Number Qualifier X ID 2/2 Used Description: Code identifying the type of communication number All valid standard codes are d. G Communication Number X AN 1/80 Used Description: Complete communications number including country or area code when applicable Example: G61 IC America INC TE ~ Syntax Rules: 1. P If either G6103 or G6104 is present, then the other is required. Comments: 1. G6103 qualifies G6104. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

10 Y3 Space Confirmation Pos: 040 Max: 1 Heading - Mandatory Loop: N/A Elements: 9 User Option (Usage): Must To specify confirmation information for space booking including numbers, dates, and load time Y Booking Number M AN 1/17 Must Description: Number assigned by the carrier for space reservation Y Standard Carrier Alpha Code O ID 2/4 Used Description: Standard Carrier Alpha Code Y Date O/Z DT 8/8 Used Description: Date expressed as CYYMMDD Y Date O/Z DT 8/8 Used Description: Date expressed as CYYMMDD Y Standard Point Location Code O ID 6/9 Used Description: Code (Standard Point Location) defined by NMFTA point development group as the official code assigned to a city or point (for ratemaking purposes) within a city. Y Pier Name O AN 2/14 Used Description: Free-form name of the pier Y Date O/Z DT 8/8 Used Description: Date expressed as CYYMMDD Y Time X/Z TM 4/8 Used Description: 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) Y Tariff Service Code Description: Code specifying the types of services for rating purposes Code DD DP HH HP PD PH PM PP Name Door-to-Door Door-to-Pier Ho-to-Ho Ho-to-Pier Pier-to-Door Pier-to-Ho Pier-to-Motor Pier-to-Pier O ID 2/2 Used Example: Y3 HOU A SMLU DP~ Syntax Rules: 1. C If Y309 is present, then Y308 is required. Semantics: 1. Y303 is the date of departure of the vessel. 2. Y304 is the estimated arrival date at the port of discharge. 3. Y307 is the required pier date. 4. Y308 is the load time. 5. Y311 is the time zone which the time reflects. Comments: 1. 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'. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

11 Loop Y4 Pos: 050 Repeat: 10 Optional Loop: Y4 Elements: N/A To transmit information relative to containers available for release Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 050 Y4 Container Release O 1 Used 054 N9 Extended reference Information O 100 Used EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

12 Y4 Container Release Pos: 050 Max: 1 Heading - Optional Loop: Y4 Elements: 7 User Option (Usage): Used To transmit information relative to containers available for release Y Booking Number O AN 1/17 Used Description: Number assigned by the carrier for space reservation Y Booking Number O AN 1/17 Used Description: Number assigned by the carrier for space reservation Y Date O DT 8/8 Used Description: Date expressed as CCYYMMDD Y Standard Point Location Code O ID 6/9 Used Description: Code (Standard Point Location) defined by NMFTA point development group as the official code assigned to a city or point (for ratemaking purposes) within a city Y Number of Containers O N0 1/4 Used Description: Number of shipping containers Y Equipment Type O ID 4/4 Used Description: Code identifying equipment type Y Standard Carrier Alpha Code O ID 2/4 Used Description: Standard Carrier Alpha Code Example: Y ~ Syntax Rules: 1. P If either Y408 or Y409 is present, then the other is required. Semantics: 1. Y401 is d for the first booking number and Y402 for the last booking number in a range of numbers. If only one booking number is d, Y402 is omitted. 2. Y403 is the date of container availability for pickup. 3. Y404 is the Standard Point Location Code (SPLC) of the container pick-up location. 4. Y407 identifies the carrier to whom containers will be released, if known. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

13 N9 Reference Identification Pos: 054 Max: 100 Heading - Optional Loop: N/A Elements: 3 User Option (Usage): Used To transmit identifying information as specified by the Reference Identification Qualifier N Reference Identification Qualifier M ID 2/3 Must Description: Code qualifying the Reference Identification All valid standard codes are d. N Reference Identification X AN 1/30 Used Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier N Free-form Description X AN 1/45 Used Description: Free-form descriptive text Example: N9 BN HOU A~ N9 FN ~ N9 PO ~ N9 SI ~ Syntax Rules: 1. R At least one of N902 or N903 is required. 2. C If N906 is present, then N905 is required. Semantics: 1. N906 reflects the time zone which the time reflects. 2. N907 contains data relating to the value cited in N902. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

14 Loop N1 Pos: 060 Repeat: 4 Optional Loop: N1 Elements: N/A To identify a party by type of organization, name, and code Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 060 N1 Name O 1 Used 090 N4 Geographic Location O 1 Used EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

15 N1 Name Pos: 060 Max: 1 Heading - Optional Loop: N1 Elements: 4 User Option (Usage): Used To identify a party by type of organization, name, and code N Entity Identifier Code M ID 2/3 Must Description: Code identifying an organizational entity, a physical location, property or an individual All valid standard codes are d. N Name X AN 1/60 Used Description: Free-form name N Identification Code Qualifier X ID 1/2 Used Description: Code designating the system/method of code structure d for Identification Code (67) All valid standard codes are d. N Identification Code X AN 2/80 Used Description: Code identifying a party or other code All valid standard codes are d. Example: N1 SH AMERICA INC ~ EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

16 N4 Geographic Location Pos: 090 Max: 1 Heading - Optional Loop: N1 Elements: 6 User Option (Usage): Used To specify the geographic place of the named party N City Name O AN 2/30 Used Description: Free-form text for city name N State or Province Code O ID 2/2 Used Description: Code (Standard State/Province) as defined by appropriate government agency N Postal Code O ID 3/15 Used Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N Country Code O ID 2/3 Used Description: Code identifying the country N Location Qualifier X ID 1/2 Used Description: Code identifying type of location N Location Identifier O AN 1/30 Used Description: Code which identifies a specific location Example: N4 ORLANDO FL ~ Syntax Rules: 1. C If N406 is present, then N405 is required. Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2. N402 is required only if city name (N401) is in the U.S. or Canada. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

17 Loop R4 Pos: 110 Repeat: 20 Mandatory Loop: R4 Elements: N/A Contractual or operational port or point relevant to the movement of the cargo Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 110 R4 Port or Terminal M 1 Must 120 DTM Date/Time Reference O 15 Used EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

18 R4 Port or Terminal Pos: 110 Max: 1 Heading - Mandatory Loop: R4 Elements: 8 User Option (Usage): Must Contractual or operational port or point relevant to the movement of the cargo R Port or Terminal Function Code M ID 1/1 Must Description: Code defining function performed at the port or terminal with respect to a shipment All valid standard codes are d. R Location Qualifier X ID 1/2 Used Description: Code identifying type of location R Location Identifier X AN 1/30 Used Description: Code which identifies a specific location R Port Name O AN 2/24 Used Description: Free-form name for the place at which an offshore carrier originates or terminates (by transshipment or otherwise) its actual ocean carriage of property R Country Code O ID 2/3 Used Description: Code identifying the country R Terminal Name O AN 2/30 Used Description: Free-form field for terminal name R Pier Number O AN 1/4 Used Description: Identifying number for the pier R State or Province Code O ID 2/2 Used Description: Code (Standard State/Province) as defined by appropriate government agency Example: R4 R UN USHOU HOUSTON US TX~ R4 E UN GTGUA GUATEMALA CITY GT~ R4 L UN USHOU HOUSTON US TX~ Syntax Rules: 1. P If either R402 or R403 is present, then the other is required. Comments: 1. R4 is required for each port to be identified. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

19 DTM Date/Time Reference Pos: 120 Max: 15 Heading - Optional Loop: R4 Elements: 4 User Option (Usage): Used To specify pertinent dates and times DTM Date/Time Qualifier M ID 3/3 Must Description: Code specifying type of date or time, or both date and time All valid standard codes are d. DTM Date X DT 8/8 Used Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year. DTM Time X TM 4/8 Used Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where HH = hours (00-23), MM = minutes (00-59), SS = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) DTM Time Code O ID 2/2 Used Description: Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a + or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and - are substituted by P and M in the codes that follow. Example: DTM LT~ Syntax Rules: 1. R At least one of DTM02, DTM03 or DTM05 is required. 2. C If DTM04 is present, then DTM03 is required. 3. P If either DTM05 or DTM06 is present, then the other is required. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

20 Loop LX Pos: 010 Repeat: 999 Mandatory Loop: LX Elements: N/A To reference a line number in a transaction set Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 010 LX Assigned Number M 1 Must 040 L0 Line Item - Quantity and Weight O 1 Used 050 L5 Description, Marks and Numbers O 1 Used EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

21 LX Assigned Number Pos: 010 Max: 1 Detail - Mandatory Loop: LX Elements: 1 User Option (Usage): Must To reference a line number in a transaction set LX Assigned Number M N0 1/6 Must Description: Number assigned for differentiation within a transaction set Example: LX 1~ EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

22 L0 Line Item - Quantity and Weight Pos: 040 Max: 1 Detail - Optional Loop: LX Elements: 11 User Option (Usage): Used To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data L Lading Line Item Number O N0 1/3 Used Description: Sequential line number for a lading item L Billed/Rated-as Quantity X R 1/11 Used Description: Basis for rating (miles, value, volume, etc.); Note: Weight may be defined by either data element 220 or 81 L Billed/Rated-as Qualifier X ID 2/2 Used Description: Code identifying the type of quantity or value on which the rate or item pricing is based. All valid standard codes are d L Weight X R 1/10 Used Description: Numeric value of weight L Weight Qualifier X ID 1/2 Used Description: Code defining the type of weight. All valid standard codes are d L Volume X R 1/8 Used Description: Value of volumetric measure L Volume Unit Qualifier X ID 1/1 Used Description: Code identifying the volume unit. All valid standard codes are d L Lading Quantity X N0 1/7 Used Description: Number of units (pieces) of the lading commodity L Packaging Form Code X ID 3/3 Used Description: Code for packaging form of the lading quantity. All valid standard codes are d. L Weight Unit Code O ID 1/1 Used Description: Code specifying the weight unit. All valid standard codes are d L Type of Service Code O ID 2/2 Used Description: Code specifying extent of transportation service requested Example: L0 1~ Syntax Rules: 1. P If either L002 or L003 is present, then the other is required. 2. P If either L004 or L005 is present, then the other is required. 3. P If either L006 or L007 is present, then the other is required. 4. P If either L008 or L009 is present, then the other is required. 5. C If L011 is present, then L004 is required. 6. P If either L013 or L015 is present, then the other is required. Semantics: 1. L008 is the number of handling units of the line item tendered to the carrier. 2. L013 can only be d if the code in L009 is PLT, SKD, or SLP. 3. L015 designates whether the carrier will be required to verify the number of units contained on a pallet, slip sheet or skid. Code "Y" indicates that the carrier will be required to verify. Code "N" indicates that the carrier will not be required to verify. Comments: 1. L013 is d to convey the total number of boxes, cartons, or pieces contained on a pallet, skid, or slip sheet for the line item. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

23 L5 Description, Marks and Numbers Pos: 050 Max: 1 Detail - Optional Loop: LX Elements: 4 User Option (Usage): Used To specify the line item in terms of description, quantity, packaging, and marks and numbers L Lading Line Item Number O N0 1/3 Used Description: Sequential line number for a lading item L Lading Description O AN 1/50 Used Description: Description of an item as required for rating and billing purposes L Commodity Code X AN 1/30 Used Description: Code describing a commodity or group of commodities L Commodity Code Qualifier X ID 1/1 Used Description: Code identifying the commodity coding system d for Commodity Code All valid standard codes are d. Example: L5 1 PLASTIC RESIN~ Syntax Rules: 1. P If either L503 or L504 is present, then the other is required. 2. C If L507 is present, then L506 is required. 3. P If either L508 or L509 is present, then the other is required. Comments: 1. L502 may be d to send quantity information as part of the product description. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

24 V1 Vessel Identification Pos: 080 Max: 2 Detail - Optional Loop: N/A Elements: 6 User Option (Usage): Used To provide vessel details and voyage number V Vessel Code X ID 1/8 Used Description: Code identifying vessel V Vessel Name X AN 2/28 Used Description: Name of ship as documented in "Lloyd's Register of Ships" V Country Code O ID 2/3 Used Description: Code identifying the country V Flight/Voyage Number O AN 2/10 Used Description: Identifying designator for the particular flight or voyage on which the cargo travels V Standard Carrier Alpha Code O ID 2/4 Used Description: Code identifying the country V Vessel Code Qualifier O ID 1/1 Used Description: Code specifying vessel code source All valid standard codes are d. Example: V EMS TRADER PT SMLU L~ Syntax Rules: 1. R At least one of V101 or V102 is required. 2. C If V108 is present, then V101 is required. Semantics: 1. V103 is the code identifying the country in which the ship (vessel) is registered. 2. V105 identifies the ocean carrier. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

25 V9 Event Detail Pos: 090 Max: 10 Detail - Optional Loop: N/A Elements: 4 User Option (Usage): Used To specify information about a specific event V Event Code M ID 3/3 Must Description: Code identifying the event about which a report is made All valid standard codes are d. V Event O AN 1/25 Used Description: Free-form description of event V Date O DT 8/8 Used Description: Date expressed as CCYYMMDD V Time X TM 4/8 Used Description: 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) Example: V9 ACC ACCEPTED ~ Syntax Rules: 1. P If either V910 or V911 is present, then the other is required. 2. C If V913 is present, then V904 is required. 3. C If V915 is present, then V909 is required. Semantics: 1. V903 is the event date. 2. V904 is the event time. 3. V909 is the Standard Point Location Code (SPLC) of the event shown in the V V910 is the length of the time delay expressed in hours. 5. V913 reflects the time zone which the event time reflects. 6. V914 is the quantity of the fuel in gallons. 7. V915 is the Standard Point Location Code (SPLC) of the secondary point of the delay indicated in the V V916 is the total number of rail cars associated with the event code in V V917 is the total number of loaded cars associated with the event code in V V918 is the total number of empty cars associated with the event code in V V919 is the total Gross Tons of the cars identified in V916. Includes the gross weight of the loads and the tare weight of the empties. 12. V920 is the total outside foot length of the cars identified in V916, rounded off to the nearest foot. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

26 SE Transaction Set Trailer Pos: 010 Max: 1 Summary - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) SE01 96 Number of Included Segments M N0 1/10 Must Description: Total number of segments included in a transaction set including ST and SE segments SE Transaction Set Control Number M AN 4/9 Must Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Example: SE ~ Comments: 1. SE is the last segment of each transaction set. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

27 GE Functional Group Trailer Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must To indicate the end of a functional group and to provide control information GE01 97 Number of Transaction Sets Included M N0 1/6 Must Description: Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element GE02 28 Group Control Number M N0 1/9 Must Description: Assigned number originated and maintained by the sender Example: GE ~ Semantics: 1. The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06. Comments: 1. The of identical data interchange control numbers in the associated functional group header and trailer is designed to maximize functional group integrity. The control number is the same as that d in the corresponding header. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

28 IEA Interchange Control Trailer Pos: Max: 1 Not Defined - Mandatory Loop: N/A Elements: 2 User Option (Usage): Must To define the end of an interchange of zero or more functional groups and interchange-related control segments IEA01 I16 Number of Included Functional Groups M N0 1/5 Must Description: A count of the number of functional groups included in an interchange IEA02 I12 Interchange Control Number M N0 9/9 Must Description: A control number assigned by the interchange sender Example: IEA ~ EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM

29 Sample Data: ST ~ B1 SMLU A~ G61 IC America INC TE ~ Y3 HOU A SMLU DP~ Y ~ N9 BN HOU A~ N9 FN ~ N9 PO ~ N9 SI ~ N1 SH AMERICA INC ~ N4 ORLANDO FL ~ R4 R UN USHOU HOUSTON US TX~ R4 E UN GTGUA GUATEMALA CITY GT~ R4 L UN USHOU HOUSTON US TX~ DTM LT~ DTM LT~ R4 D UN GTSTC PUERTO SANTO TOMAS DE CA GT~ DTM LT~ LX 1~ L0 1~ L5 1 PLASTIC RESIN~ V EMS TRADER PT SMLU L~ V9 ACC ACCEPTED ~ SE ~ Please note Bookings for Hazardous Materials are accepted on a provisional basis subject to Seaboard Marine review and approval. EDI-301v Documentation/Transaction Sets/Mapping/ANSI/X12/ 301 VGM