CSX EDI 824 Application Advice Version: 005030



Similar documents
Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010

214 Transportation Carrier Shipment Status Message

824 Application Advice

EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X Draft

ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message

810 Invoice ANSI ASC X12 Version 4010

ANSI X12 version Text Message

810 Invoice Revised 01/26/15

VERSION: ANSI X

ANSI X12 version Advance Ship Notice

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

DoD Transportation Electronic Data Interchange (EDI) Convention

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION

Customer EDI Guidelines United States 810 Invoice

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET

ANSI X12 version Remittance Advice

810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

Implementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS S

CSXT EDI 404 Rail Carrier Shipment Information (Bill of Lading) v005010

214 Transportation Carrier Shipment Status Message - LTL

Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN)

999 Implementation Acknowledgment. Version: 1.0 Draft

Transaction Set Application Advice

EDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel)

997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.

ANSI X12 version Planning Schedule with Release Capability

322 TERMINAL OPERATIONS AND INTERMODAL RAMP ACTIVITY

3/31/08 ALTRA INDUSTRIAL MOTION Invoice Inbound 810 X Page 1 Created by Ralph Lenoir

ADOBE ANSI X Version: 1.0

KANSAS CITY SOUTHERN EDI On-Boarding Guide

Note: The following information is required on all Merchandise Invoices:

944 Warehouse Stock Transfer Receipt Advice. X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice

Invoice. Transaction Set (810) (Outbound from TI)

997 Functional Acknowledgment

AMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS

Portland General Electric Implementation Standard

856 Advance Ship Notice Supplier Implementation Guide November 2015

810 Invoice ANSI X.12 Version 5010

X12 Implementation. Guidelines. For. Transfer Version (996o)

Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira

Electronic Data Interchange

ANSI X Product Transfer and Resale Report

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.

ANSI ASC X12 SHIPMENT STATUS (214) VERSION

BORGWARNER IMPLEMENTATION GUIDELINE FOR V PLANNING SCHEDULE

856 Ship Notice/Manifest - R US CANADA

CVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X

Implementation Guideline

Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT IT1 Baseline Item Data M PID Product / Item Description M

Implementation Guide to. Application Advice - Freight Bill EDI 824. In Response to CN Invoices. December 31, 2010

945 Warehouse Shipping Advice

CREDIT CARD BULK PROVIDER REQUIREMENTS

Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010

The information in this document will be common for all X12N implementation guides.

84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION August 21, 2007

Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)

Canada Customs emanifest Program Q & A

Mazda North American Operations EDI Supplier Documentation October 20, 2015

ASN. HDMA Electronic Data Interchange (EDI) Guidelines for the 856 Advance Ship Notice to Support Implementation of DSCSA

LOOP ID - N N9 Reference Identification O MSG Message Text O 1000

EDI GUIDELINES INVOICE 810 VERSION 4010

DLMS Supplement to Federal IC 996H GENCOMM / XML ADC 416 DoD M

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET

WPS Health Solutions

Electronic Data Interchange

DRS Defect Report Inbound 322. DRS Defect Report from Trading partner to Chassis.Com IB 322 Implementation Guide Prepared by Advent Inc for OCEMA

Purpose of the 270/271 Health Care Eligibility Benefit Inquiry and Response

856 Advanced Shipping Notices (ASN)

ASC X12 Finance Subcommittee. Consumer Service Provider (CSP) Billing and Payment Guide

MV-STAR. I/O Reference Guide

To indicate the beginning of an invoice transaction set and to transmit identifying numbers and dates. BIG^ ^12345^ ^ ^

Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy

Commonwealth of Kentucky Department of Revenue

Bill of Lading Number REF Reference Identification M AN 1/30 MustUse

ANSI X12 ASN 856 Version

Unified Grocers 820 EFT Specifications Remittance Advice Document Structure

404 RAIL CARRIER SHIPMENT INFORMATION (BILL OF LADING) 997 FUNCTIONAL ACKNOWLEDGEMENT

CVS/Caremark. Implementation Guide. 852 Product Activity Data Warehouse Movement. Version X

Dart Container Corporation. EDI 810 Outbound Invoice Version 4010

NEXCOM EDI 753 / 754 Supplier Shipping Instructions

Implementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS S Supplier

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

State of Tennessee Department of Revenue

810 Invoice. Introduction: Heading: Functional Group ID=IN

As a service to Suppliers preferring to transact via EDI, Ariba SN accepts the ANSI X Ship Notice / Manifest document.

State of Nebraska. Motor Fuels Division. EDI Implementation Guide. Revised May ANSI ASC X12 V.4030

ORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version /2011 Page 1

BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010

Supply Chain Merchandise Logistics E-Commerce Purchase Order

FEDEX EDI INVOICING 210 INVOICE DETAIL 820 PAYMENT ORDER/REMITTANCE ADVICE VERSION Implementation Guide. New Customer Version

HIPAA EDI Companion Guide for 835 Electronic Remittance Advice

820 ANSI X12 Version

RANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010

The Kansas City Southern Railway Company

PURCHASE ORDER RESPONSE

EDI Compliance Report

Transcription:

CSX EDI 824 Application Advice Version: 005030 Questions about the CSX EDI 284 Implementation Guide should be directed to: 877-SHIPCSX option 2, prompt 2 Monday Friday: 7:00 AM 6:00 PM Publication: September 2007 824 v 005030.ecs 1

Table of Contents 824 Application Advice...3 ST Transaction Set Header...4 BGN Beginning Segment...5 OTI Loop OTI...6 OTI Original Transaction Identification...7 REF Reference Information...9 DTM Date/Time Reference... 10 TED Loop TED... 11 TED Technical Error Description... 12 SE Transaction Set Trailer... 15 824 v 005030.ecs 2

824 Application Advice Functional Group=AG Purpose: This X12 Transaction Set contains the format and establishes the data contents of the Application Advice Transaction Set (824) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the ability to report the results of an application system's data content edits of transaction sets. The results of editing transaction sets can be reported at the functional group and transaction set level, in either coded or free-form format. It is designed to accommodate the business need of reporting the acceptance, rejection or acceptance with change of any transaction set. The Application Advice should not be used in place of a transaction set designed as a specific response to another transaction set (e.g., purchase order acknowledgment sent in response to a purchase order). Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage 0100 ST Transaction Set Header M 1 Must use 0200 BGN Beginning Segment M 1 Must use Detail: Pos Id Segment Name Req Max Use Repeat Notes Usage LOOP ID - OTI >1 0100 OTI Original Transaction M 1 Must use Identification 0200 REF Reference Information O 12 Must use 0300 DTM Date/Time Reference O 2 Dependent LOOP ID - TED >1 0700 TED Technical Error Description O 1 Must use 0900 SE Transaction Set Trailer M 1 Must use 824 v 005030.ecs 3

ST Transaction Set Header Pos: 0100 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 Purpose: To indicate the start of a transaction set and to assign a control number. Element Summary: Ref Id Element Name Req Type Min/Max Usage ST01 143 Transaction Set Identifier Code M ID 3/3 Must use Description: Code uniquely identifying a Transaction Set. Code Name 824 Application Advice ST02 329 Transaction Set Control Number M AN 4/9 Must use Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. Semantics: 1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). 2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition. When used, this implementation convention reference takes precedence over the implementation reference specified in the GS08. 824 v 005030.ecs 4

BGN Beginning Segment Pos: 0200 Max: 1 Heading - Mandatory Loop: N/A Elements: 4 Purpose: To indicate the beginning of a transaction set. Element Summary: Ref Id Element Name Req Type Min/Max Usage BGN01 353 Transaction Set Purpose Code M ID 2/2 Must use Description: Code identifying purpose of transaction set. Code Name 00 Original BGN02 127 Reference Identification M AN 1/3 Must use Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier. User Note 1: Transaction set (DE 143) code being acknowledged - 404 or 998. BGN03 373 Date M DT 8/8 Must use Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year. User Note 1: Current Date. BGN04 337 Time X TM 4/8 Must use 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). User Note 1: Current Time. Semantics: 1. BGN02 is the transaction set reference number. 2. BGN03 is the transaction set date. 3. BGN04 is the transaction set time. 824 v 005030.ecs 5

Loop OTI Pos: 0100 Repeat: >1 Mandatory Loop: OTI Elements: N/A Purpose: To identify the edited transaction set and the level at which the results of the edit are reported, and to indicate the accepted, rejected, or accepted-with-change edit result. Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 0100 OTI Original Transaction Identification M 1 Must use 0200 REF Reference Information O 12 Must use 0300 DTM Date/Time Reference O 2 Dependent 0700 Loop TED O >1 Must use User Note 1: The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this application acknowledgment. 824 v 005030.ecs 6

OTI Original Transaction Identification Pos: 0100 Max: 1 Detail - Mandatory Loop: OTI Elements: 7 Purpose: To identify the edited transaction set and the level at which the results of the edit are reported, and to indicate the accepted, rejected, or accepted-with-change edit result. Element Summary: Ref Id Element Name Req Type Min/Max Usage OTI01 110 Application Acknowledgment Code M ID 1/2 Must use Description: Code indicating the application system edit results of the business data. Code TA TC TE TR Name Transaction Set Accept Transaction Set Accept with Data Content Change Transaction Set Accept with Error Transaction Set Reject OTI02 128 Reference Identification Qualifier M ID 2/3 Must use Description: Code qualifying the Reference Identification. Code BM Name Bill of Lading Number OTI03 127 Reference Identification M AN 1/15 Must use Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier. OTI06 373 Date O DT 8/8 Used Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year. OTI07 337 Time O 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). OTI08 28 Group Control Number X N0 1/9 Used Description: Assigned number originated and maintained by the sender User Note 1: Can be sent if requested. OTI09 329 Transaction Set Control Number O AN 4/9 Used Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set User Note 1: Can be sent if requested. Semantics: 1. OTI03 is the primary reference identification or number used to uniquely identify the original transaction set. Comments: 1. OTI02 contains the qualifier identifying the business transaction from the original business application, and OTI03 will contain the original business application identification. User Note 1: The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this 824 v 005030.ecs 7

application acknowledgment. 824 v 005030.ecs 8

REF Reference Information Pos: 0200 Max: 12 Detail - Optional Loop: OTI Elements: 2 Purpose: To specify identifying information. Element Summary: Ref Id Element Name Req Type Min/Max Usage REF01 128 Reference Identification Qualifier M ID 2/3 Must use Description: Code qualifying the Reference Identification. Code EQ WY Name Equipment Number Waybill Number REF02 127 Reference Identification X AN 1/10 Must use Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier. User Note 1: If REF01 is EQ, then the first four positions are used for the equipment initial and the next 6 positions are for the equipment number. Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required. User Note 1: The REF segment allows for the provision of secondary reference identification or numbers required to uniquely identify the original transaction set. The primary reference identification or number should be provided in elements OTI02-03. 824 v 005030.ecs 9

DTM Date/Time Reference Pos: 0300 Max: 2 Detail - Optional Loop: OTI Elements: 3 User Option (Usage): Dependent Purpose: To specify pertinent dates and times. Element Summary: Ref Id Element Name Req Type Min/Max Usage DTM01 374 Date/Time Qualifier M ID 3/3 Must use Description: Code specifying type of date or time, or both date and time. Code Name 097 Transaction Creation DTM02 373 Date X DT 8/8 Must use Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year. User Note 1: Waybill create date. DTM03 337 Time X TM 4/8 Must use 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). User Note 1: Waybill create time. Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required. User Note 1: Sent on Original 824s only. User Note 2: The DTM segment allows for the provision of date, time, or date and time information required to uniquely identify the original transaction set. 824 v 005030.ecs 10

Loop TED Pos: 0700 Repeat: >1 Optional Loop: TED Elements: N/A Purpose: To identify the error and, if feasible, the erroneous segment, or data element, or both Loop Summary: Pos Id Segment Name Req Max Use Repeat Usage 0700 TED Technical Error Description O 1 Must use 824 v 005030.ecs 11

TED Technical Error Description Pos: 0700 Max: 1 Detail - Optional Loop: TED Elements: 2 Purpose: To identify the error and, if feasible, the erroneous segment, or data element, or both. Element Summary: Ref Id Element Name Req Type Min/Max Usage TED01 647 Application Error Condition Code M ID 1/3 Must use Description: Code indicating application error condition. Code Name 003 Duplicate Billing 004 Invalid Commodity Code 005 Route Error 006 Duplicate 024 Other Unlisted Reason ZZZ Mutually Defined TED02 3 Free-form Message O AN 1/60 Must use Description: Free-form text. User Note 1: Alpha Reject Reason. Required if Application Error Code (TED01) is 024 or ZZZ. User Note 2: Original 824s: 003 DUPLICATE BILL OF LADING 004 INVALID STCC CODE 005 INVALID ROUTE 006 DUPLICATE EQUIPMENT ON BOL 024 INVALID ORIGIN CITY/STATE. 024 INVALID DESTINATION CITY/STATE 024 EQUIP ON BOL NOT IN INVENTORY 024 INVALID/MISSING HAZARD DATA 024 CONTRACT/TARIFF INVALID 024 INTERMODAL PLAN NUMBER INVALID 024 MULTI-TYPE INVALID 024 SHIPPER INVOICE NUMBER INVALID 024 BILL OF LADING NUMBER INVALID 024 CONSIGNEE AT LOCATION INVALID 024 CARE OF PARTY INVALID ---- 024 SHIPPER INVALID/MISSPELLED 024 CONSIGNEE INVALID/MISSPELLED 024 FREIGHT PAYOR INVALID 024 MEXICAN CUSTOMS BROKER REQUIRD 024 FREIGHT FORWARDER REQUIRED User Note 3: ZZZ Descriptions: CANNOT CHANGE EQUIPMENT ID.MUST USE VOID AND ISSUE NEW BOL NO MATCHING WAYBILL FOUND.NEW WB CREATE FROM CHANGE REQUEST CANNOT CHANGE ORIGIN AUDIT.MUST USE VOID AND ISSUE NEW BOL NO MATCHING WAYBILL FOUND.UNABLE TO PROCESS VOID REQUEST PRIOR TO GATE.CORRECTION PROCESSED VOID PROCESSED EQUIPMENT RECEIVED BY CSXI VOID CANNOT BE PROCESSED CORRECTION NOT PROCESSED.POST GATE AND UNAUTHORIZED CHANGE CORRECTION NOT PROCESSED.PRE GATE AND UNAUTHORIZED CHANGE POST GATE.CORRECTION PROCESSED.SPECIFIC FIELDS UPDATED CORRECTION NOT PROCESSED.SHIPMENT ARRIVED AT DESTINATION 824 v 005030.ecs 12

VOID CANNOT BE PROCESSED DUE TO W/B STATUS POST GATE NO CHANGES DETECTED CORRECTION VOIDED CORR PROCESSED.ORIGINAL HAZMAT STCC RETAINED SHIPMENT STATUS CAN NOT BE DETERMINED CORR REJECTED FAILED HAZMAT SIGNATURE CERTIFICATION NOT AUTHORIZED FOR HAZMAT EDI N3 SHIPPER ADDRESS MISSING FOR CANADIAN HAZMAT SECOND 404 RECEIVED VOIDED AS TRUE DUP SECOND 404 PROCESSED WITH BOL NUMBER UPDATE N4 SHIPPER LOCATION MISSING FOR CANADIAN HAZMAT N4 CONSIGNEE LOCATION MISSING FOR CANAD IAN HAZMAT N4 CARE OF LOCATION MISSING FOR CANADIAN HAZMAT N4 SHIPPER STATE/PROVINCE NOT CANADIAN FOR CANADIAN HAZMAT N4 CONSIGNEE STATE/PROVINCE NOT CANADIAN FOR CAN HAZMAT N4 CARE OF STATE/PROVINCE NOT CANADIAN FOR CANADIAN HAZMAT LH106 UNIT OF MEASURE NOT METRIC FOR CANADIAN HAZMAT LHF POISON INHAL HAZARD ZONE NOT PRESENTFOR CANADIAN HAZMAT N3 CONSIGNEE ADDRESS MISSING FOR CANADIAN HAZMAT N3 CARE OF ADDRESS MISSING FOR CANADIAN HAZMAT N1 MISSING SHIPPER INFORMATION N1 MISSING CONSIGNEE OR CARE OF ZC1 NOT PROCESSED CANNOT CHANGE BOL NUM ZC1 NOT PROCESSED CANNOT CHANGE ORIGIN ZC1 BOL NUM DOES NOT MATCH N9 BOL NUM CONTROL TEMPERATURE IS REQUIRED EMERGENCY TEMPERATURE IS REQUIRED SERVICE NOT OFFERED IN THIS LANE COFC SERVICE NOT OFFERED IN THIS LANE TOFC SERVICE NOT OFFERED IN THIS LANE SERVICE NOT OFFERED IN THIS LANE FOR EQUIPMENT PROGRAM SERVICE NOT OFFERED IN THIS LANE FOR EQUIPMENT PROGRAM N1 NOTIFY PARTY MISSING FOR INTERMODAL SHIPMENT ORDER OF MUST OCCUR WITH N1 NOTIFY PARTY FOR SHIPPER'S ORDER CORRECTION CANNOT BE PROCESSED DUE TO S/O STATUS RAIL CARRIER REJECTED THE CORRECTION RAIL CARRIER REJECTED THE VOID CUSTOMER IS NOT EDI V&C PARTICIPANT BOL NUMBER IS NOT MATCHED. UNABLE TO PROCESS VOID REQUEST BOL DOES NOT MEET CRITERIA FOR WATER CARRIER MOVE RULE 11 SERVICE NOT ALLOWED IN GIVEN LANE INTERLINE PRICED SERVICE NOT ALLOWED IN GIVEN LANE SERVICE IS NOT OFFERED IN THIS LANE FOR EQUIPMENT PROGRAM TOFC SERVICE IS NOT OFFERED IN THIS LANE COFC SERVICE IS NOT OFFERED IN THIS LANE STAX, NACS, AND/OR RAIL TRAILER TRAFFIC NOT ALLOWED IN LANE DOMESTIC TRAFFIC NOT ALLOWED IN GIVEN LANE PRIVATE EQUIPMENT NOT ALLOWED IN GIVEN LANE INTERNATIONAL TRAFFIC NOT ALLOWED IN GIVEN LANE GIVEN EQUIPMENT LENGTH NOT ALLOWED IN THIS LANE GIVEN AGREEMENT NOT ALLOWED IN THIS LANE MEXICAN CUSTOMS BROKER IS MANDATORY FOR MEXICAN DESTINATIONS FREIGHT FORWARDER IS MANDATORY FOR MEXICAN DESTINATIONS CUSTOMS BROKER XQ IS MANDATORY FOR CANADIAN DESTINATIONS IMPORTER IS MANDATORY FOR CANADIAN DESTINATIONS INVALID/MISSING REFERENCE NUMBER QUALI FIER CUSTOMS NUMBER MUST BE OF MAX 15 CHARS REFERENCE QUALIFIER REQUIRED IF NUMBER IS SENT REFERENCE NUMBER REQUIRED IF QUALIFIER IS SENT CHANGE FROM HAZ TO NON-HAZ MUST BE VOID /REBILL HAZ EQP POST GATE. ONLY NON-HAZ CHANGES APPLIED INVALID EMBARGO PURMIT NUMBER INVALID YEAR IN EMBARGO NUMBER 824 v 005030.ecs 13

INVALID SCAC IN EMBARGO NUMBER EMBARGO PERMIT NUMBER IS REQUIRED WHEN EMBARGO NO IS ENTERED EMBARGO NO IS REQUIRED WHEN EMBARGO PERMIT NO IS ENTERED HAZARDOUS SHIPPER IS REQUIRED SHIPPER CITY IS REQUIRED SHIPPER STATE IS REQUIRED SHIPPER ADDRESS IS REQUIRED HAZARDOUS CONSIGNEE IS REQUIRED CONSIGNEE CITY IS REQUIRED CONSIGNEE STATE REQUIRED CONSIGNEE ADDRESS IS REQUIRED SHIPPER ADDRESS REQUIRED CONSIGNEE ADDRESS REQUIRED CARE OFF PARTY ADDRESS REQUIRED ULTIMATE CONSIGNEE ADDRESS REQUIRED BENEFICIAL OWNER ADDRESS REQURED IMPORTER ADDRESS REQUIRED DO NOT USE FAK AS STCC DESC IF TRANSBORDER NO MATCHING DATA CORR REJECTED CONTROL TEMPERATURE IS NOT APPLICABLE EMERGENCY TEMPERATURE IS NOT APPLICABLE Comments: 1. If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.). 824 v 005030.ecs 14

SE Transaction Set Trailer Pos: 0900 Max: 1 Detail - Mandatory Loop: N/A Elements: 2 Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments). Element Summary: Ref Id Element Name Req Type Min/Max Usage SE01 96 Number of Included Segments M N0 1/10 Must use Description: Total number of segments included in a transaction set including ST and SE segments. SE02 329 Transaction Set Control Number M AN 4/9 Must use Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. Comments: 1. SE is the last segment of each transaction set. 824 v 005030.ecs 15