Transcription
ANSI ASC X12MOTOR CARRIERDELIVERY TRAILER MANIFEST (212)VERSION 004010YRC Freight Inc.10990 Roe AvenueOverland Park, KS 66211www.yrcfreight.com1Last Reviewed 10/29/13
Dear YRC Freight Customer:Thank you for your interest in trading delivery trailer manifests with YRC Freight.implementation guide you requested.This is the 212We look forward to working with you to implement the EDItransaction set 212. If you have any questions about the 212 or any other EDI issues, please feel free tocontact EDIhelp@yrcfreightcom.2Last Reviewed 10/29/13
PrefacePurpose and ScopeThe purpose of this guide is to provide YRC Freight trading partners the necessary information to acceptDelivery Trailer Manifests, via EDI, from YRC Freight. The material presented here covers the 212transaction set of Version 004 Release 010 of the ANSI ASC X12 standard.American National Standards Institute Accredited Standards Committee X12YRC Freight uses ANSI ASC X12 standard-format transaction sets for the exchange of electronicdocuments with its EDI trading partners.YRC Freight is a leader in the use of EDI in the transportation industry and firmly supports the use of ANSIASC X12 standards in EDI trading-partner relationships. The use of such standards cultivates a commonlanguage between trading partners and expedites EDI setup. A well-developed EDI system providesnumerous possibilities for expanding the business relationship.3Last Reviewed 10/29/13
PREFACE3Purpose and Scope3ANSI ASC X123REFERENCE MATERIAL7ASCX12 Publications7ATA Publications7ELECTRONIC DATA INTERCHANGE (EDI)8Communications8The Structure of an Electronic Transmission8Transaction Structure9NOTATION CONVENTIONS10Segment Requirements10Element Requirements10Data Types10Data Element Reference Number11TRANSACTION SET 21212Header Segments12Detail Segments13212 BUSINESS EXAMPLE14SEGMENT DEFINITIONS17ISA Interchange Control Header17IEA Interchange Control Trailer19GS Functional Group Header20ST Starting Segment21ATA - Beginning Segment for the Motor Carrier Delivery Trailer Manifest224Last Reviewed 10/29/13
B2A Set Purpose23L11 Business Instructions and Reference Number24N1 Name25N2 Additional Name Information26N3 Address Information27N4 Geographic Location28G61 Contact29G62 Date/Time30L11 Business Instructions and Reference Number31AT7 Shipment Status Details32G62 Date/Time34MS1 Equipment, Shipment or Real property Location35MS2 Equipment or Container Owner and Type36M7 Seal Numbers37AT9 Trailer or Container Dimension and Weight38LX Assigned Number39L11 Business Instructions and Reference Number40BLR Transportation Carrier Identification41MAN Marks and Numbers42AT8 Shipment Weight, Packaging and Quantity Data43G62 Date/Time44TSD Trailer Shipment Details45SPO Shipment Purchase Order Detail46SDQ Destination Quantity47N1 Name49N2 Additional Name Information50N3 Address Information51N4 Geographic Location525Last Reviewed 10/29/13
L11 Business Instructions and Reference Number53SE Transaction Set Trailer546Last Reviewed 10/29/13
REFERENCE MATERIALASCX12 PublicationsElectronic Data Interchange X12 Standards, reflecting Version 004 Release 010 (004010), datedDecember 1997. This publication is available from DISA, 1800 Diagonal Road, Suite 200, Alexandria, VA22314,(703)548-7005, WWW.DISA.ORG.ATA PublicationsAmerican Trucking Association’s Motor Carrier Industry Guide to Electronic Data InterchangeImplementation and Conventions, reflecting Version 004 Release 010 (004010), dated May 1998. Thispublication is available from the American Trucking Association’s Information Technology Council, 2200Mill Road, Alexandria, VA 22314.7Last Reviewed 10/29/13
Electronic Data Interchange (EDI)CommunicationsYRC Freight Inc. has developed a communication network that provides the ability to transmit EDItransactions directly to EDI Trading Partners, the method YRC Freight prefers; however, if you prefer touse a third-party Value Added Network, YRC Freight prefers Descartes.The Structure of an Electronic TransmissionTransmission StructureAn EDI transmission consists of one or more “envelopes,” which identify the sender and receiver of thetransaction set. ISA and IEA segments mark the beginning and the end of an envelope, respectively. Inthe envelope, the transaction sets are organized into one or more functional groups bounded by a GS anda GE segment. Figure 1 illustrates the format of an EDI transmission.Communication ProtocolISAInterchange HeaderGSGroup HeaderSTTran HeaderTran DetailSETran TrailerGEGroup TrailerGSGroup HeaderSTTran HeaderTran DetailSETran TrailerGEGroup TrailerIEAInterchange TrailerCommunication ProtocolFigure 1: Transmission Structure8Last Reviewed 10/29/13
Transaction StructureEDI transaction sets consist of a group of segments (records) arranged in a specific order. Mosttransactions have header-level segments and detail-level segments. Repeated sets of segments, referredto as loops, may also be included.Each segment begins with a segment identifier and ends with a segment terminator. The segmentterminator is a special character sender and receiver agree on to define the end of a segment. The mostcommonly used segment terminator is the hexadecimal ‘15’ in EBCDIC (Extended Binary Coded DecimalInterchange Code) or ‘85’ in ASCII (American Standard Code for Information Exchange).An element separator delimits data elements (fields) in a segment. The element separator is a specialcharacter that sender and receiver agree on. The most commonly used element separator is an asterisk(*), a hexadecimal ‘5C’ for EBCDIC or hexadecimal ‘2A’ for ASCII.STTransaction HeaderHeader SegmentsDetail SegmentsSummary SegmentsSETransaction TrailerFigure 2: Transaction Structure9Last Reviewed 10/29/13
Notation ConventionsSegment Requirements (M) MANDATORY: The segment must be transmitted. (O) OPTIONAL: The segment may be transmitted if needed.Element Requirements (M) MANDATORY: The data element must be transmitted. (O) OPTIONAL: The data element may be transmitted if needed. (X) RELATIONAL: The data element's existence or absence is related to the existence or absence ofanother data element. The relationship is explained by a note after the segment definition. An alphabeticcode may also explain the relational condition. (Z) SEMANTIC: Refer to the Semantic note(s) for this data element. (C) CONDITIONAL: The data element must be transmitted under certain conditions. (P) PAIRED or MULTIPLE: If any element is transmitted, then all must be transmitted. (R) REQUIRED: At least one of the data elements specified must be transmitted. (E) EXCLUSIVE: Not more than one of the data elements specified can be transmitted. (L) LIST CONDITIONAL: If the first data element specified is transmitted, then at least one of the othersmust be transmitted. Any or all elements not specified as the first may be transmitted with the first dataelement. Each data element has a minimum and maximum length requirement. In a mandatory numeric data element, the minimum characters, as defined in the data dictionary, mustbe transmitted even if the value is zero.Data Types AN: Alphanumeric data elements containing the numerals 0–9, the characters A–Z and any specialcharacters except asterisk (*), the greater-than sign ( ) and the characters with a hexadecimal value of‘40’ or less. These characters are control characters and should not be used for data. The contents areleft-justified. Trailing spaces should be suppressed unless necessary to satisfy a minimum-lengthrequirement. R: (Real) numeric data containing the numerals 0–9 and a decimal point in the proper position. Thedecimal point is optional for integer values but required for fractional values. A leading or - sign may beused. The minus sign must be used for negative values. Nn: Numeric data containing the numerals 0–9, and an implied decimal point. The 'N' indicates that theelement contains a numeric value, and the 'n' indicates the number of decimal places to the right of theimplied decimal point. The actual decimal point is not transmitted. A leading or - sign may be used. Theminus sign must be used for negative values. Leading zeroes should be suppressed unless they arenecessary to satisfy a minimum number of digits required by the data element specification. For a dataelement defined as N4 with a minimum length of 4, the value 0.0001 would be transmitted as ‘0001’. Foran N4 data element with a minimum length of 1, the value 0.0001 would be transmitted ‘1’. ID: A data element identifier from a pre-defined list of values maintained by ASC X12. DT: Numeric date in the form YYYYMMDD. TM: Numeric time in the form HHMM. Time is represented in 24-hour clock format.10Last Reviewed 10/29/13
Data Element Reference NumberThe Data Element Reference Number is a unique identifier used to help find data-element definitions inthe applicable standards manual.11Last Reviewed 10/29/13
Transaction Set 212 Motor Carrier Delivery Trailer ManifestThis transaction set can be used to allow motor carriers to provide consignees or otherinterested parties information about the contents of a trailer that contains multiple shipmentsand that has been tendered for delivery. It is not to be used to provide the recipient datarelative to a full-truckload shipment.Table ransaction Set HeaderBeginning SegmentSet PurposeBusiness Instructions and Reference NumberNameAdditional Name InformationAddress InformationGeographic LocationContactDate/TimeBusiness Instructions and Reference NumberMMMOOOOOOOO11130011211110AT7G62MS1Shipment Status DetailsDate/TimeEquipment LocationMOO151MS2M7AT9Equipment or Container Owner and TypeSeal NumbersTrailer or Container Dimension and WeightOOO11112Last Reviewed 0001001015001500150015001600160016011
Table QAssigned NumberBusiness Instructions & Reference NumberTransportation Carrier IdentificationMarks and NumbersShipment Weight, Packaging and QuantityDataDate/TimeTrailer Shipment DetailsShipment Purchase-Order DetailDestination 0NameAdditional Name InformationAddress InformationGeographic LocationBusiness Instructions & Reference NumberOOOOO1121502200220022002200220Transaction Set TrailerM1NOTES:1/050Loop 0100 provides the location where the carrier will deliver the trailer.1/120The AT7 segment provides the status of all the shipments on the trailer.2/010Loop 0200 provides the specific details concerning all the shipments included in the manifest. Therewill be one iteration of loop 0200 for each shipment contained in the manifest. The most-common wayto identify the shipments is by the PRO number that the carrier assigns.2/030The BLR segment shall be used only when the carrier delivering the freight is not the carrier thatpicked up the freight. The pick-up carrier shall be identified by its Standard Carrier Alpha Code(SCAC).2/070The only codes that can be used in the in transaction set 212 TSD segment TSD02 include: 1 indicates the shipment is in the third quarter of the trailer; 2 - indicates the shipment is in the secondquarter of the trailer; 3 - indicates the shipment is in the third quarter of the trailer; 4 - indicates theshipment is in the fourth quarter of the trailer (closest to the rear door of the trailer).2/100Loop 0220 shall be used only to provide the shipper’s identification if the carrier has not provided thatinformation in a previous shipment-status message.13Last Reviewed 10/29/13
212 Business ExampleI SA* 00** 00** 02* RDWY* 01* 012345678* 130526* 0532* U* 00400* 000001499* 0* P*GS* TM * RDWY* 012345678* 20130526* 0532* 1499* X* 004010ST* 212* 014990001ATA* RDWY* 981221234123302* 20130526ATA02 (981221234123302) IS THE DELIVERY TRAILER MANIFEST NUMBERB2A* 0000 IS THE ORIGINAL TRAILER MANIFEST05 IS AN ENTIRE REPLACEMENTSU IS AN UPDATE OF THE STATUSB2A02 IS NOT USED BY MOTOR CARRIERSN1* ST* RETAI LER* 94* 0456THE SHIP-TO LOOP OCCURS ONCE PER TRANSACTIONN3* 333 GORDON BLVDN4* TI FTON* OH* 43194AT7* AV* NS* * * 20130526* 0248* ETAV IS AVAILABLE FOR DELIVERYG62* CL* 20130526G6202 (20130526) IS THE DATE THE DELIVERY TRAILER WAS ORIGINALLY CLOSEDCL IS CLOSEDG62* 17* 20130526* 1330* ETG6202 (20130526) IS THE ESTIMATED DATE AND TIME OF ARRIVAL17 IS ESTIMATED DELIVERY DATEM S2* RDWY* 12345* TLM 7* 1234AAT9* 2800* * * G* L* 22000LX* 1L11* CN* 2736255693CN IS CARRIER'S REFERENCE NUMBER (PRO NUMBER)L11* BM * 766707BABM IS BILL OF LADING NUMBERBLR* SCACTHIS SEGMENT IS OPTIONAL AND IDENTIFIES THE PREVIOUS CARRIERAT8* B* L* 2002* * 3B IS BILLED WEIGHTG IS GROSS WEIGHTL IS POUNDS14Last Reviewed 10/29/13
212 Business Example (cont’d.)N IS ACTUAL NET WEIGHTAT804 IS CARTON COUNTAT805 (3) IS PALLET COUNTAT804 & AT805 ARE HANDLING UNITSG62* 86* 20130521TSD* 1SPO* 1590770904* 088* CT* 55* L* 635SPO02 IS DEPARTMENT NUMBERSDQ* CT* 92* 2333* 22SDQ03 IS STORE NUMBERSDQ04 IS CARTON COUNTN1* SF* SHI PPER 1N3* 1398 GARY AVEN4* HOUSTON* TX* 77020LX* 2L11* CN* 133625564XL11* BM * 1357AT8* B* L* 200* * 3G62* 86* 20130520TSD* 2SPO* 12312345* * CT* 5* L* 135N1* SF* VENDORN3* 555 YOUI NG STN4* M ANCEST* AZ* 85020LX* 3L11* CN* 8336222222L11* BM * HA898AT8* B* L* 400* 33G62* 86* 2013052215Last Reviewed 10/29/13
212 Business Example (cont’d.)TSD* 3SPO* TT0909* * CT* 115* L* 1588N1* SF* ALLI DI STRI BUTI ON CENTERN3* 33 S CLEVELAND AVEN4* M OGADOR* OH* 44588SE* 0000000045* 014990001GE* 000001* 000001499I EA* 00001* 00000149916Last Reviewed 10/29/13
Segment DefinitionsISA Interchange Control HeaderLevel:Loop:Usage:Max Use:Purpose:Control SegmentExample:ISA*00*MandatoryOneTo begin and identify an interchange of zero or more functional groups and interchange-relatedcontrol 0000522*0*P* Data Element 03I0304I0405I0506I0607I0508I0709I08Authorization Information QualifierCode to identify the type of information in the Authorization Info.00 - No Authorization information presentAuthorization InformationInformation used for additional identification or authorization ofthe interchange sender or the data in the interchange.This field should be spacesSecurity Information QualifierCode to identify the type of information in the Securityinformation.00 - No Security InformationSecurity InformationThis is used to identify security information about theinterchange sender or the data in the interchange.This field should be spacesInterchange ID QualifierQualifier to designate the system/method of code structureused to designate the sender or receiver ID element beingqualified.01 - Duns Number02 - SCACZZ - Mutually DefinedInterchange Sender IDUnique identification code the sender publishes for other partiesto use as the receiver ID to route data to them; the senderalways codes this value in the sender ID element.Interchange ID QualifierQualifier to designate the system/method of code structureused to designate the sender or receiver ID element beingqualified.01 - Duns NumberInterchange Receiver IDUnique identification code the date receiver publishes.Interchange DateCreation date of the interchange (YYMMDD).17Last Reviewed MID2/2MAN15/15MDT6/6
10I0911I1012I1113I1214I1315I1416I15Interchange TimeCreation time of the interchange (HHMM).Interchange Control Standards IdentifierCode to identify the agency responsible for the control standardused by the message that is enclosed by the interchangeheader and trailer.U - USAInterchange Control Version NumberThis version number covers the interchange control segments.00400 - Standards issued as ANSI X12.5-1997Interchange Control NumberA control number assigned by the interchange sender.Must match IEA02Acknowledgment RequestedCode the sender sends to request an interchangeacknowledgment (TA1).0 - No TA1 requestedTest IndicatorCode to indicate whether data enclosed is test or production.T - TestP - ProductionComponent Element SeparatorType is not applicable; the component element separator is adelimiter and not a data element; this field provides the delimiterused to separate component data elements in a composite datastructure; this value must be different from the data elementseparator and the segment terminator.18Last Reviewed 10/29/13MTM4/4MID1/1MID5/5MN09/9MID1/1MID1/1M1/1
IEA Interchange Control TrailerLevel:Loop:Usage:Max Use:Purpose:Control SegmentExample:IEA*1*000000522MandatoryOneTo define the end of an interchange; used with the ISA segment.Data Element Number of included Functional Groups.Interchange Control Number19Last Reviewed 10/29/13MMN0N01/59/9
GS Functional Group HeaderLevel:Loop:Usage:Max Use:Purpose:Control SegmentSemantic:010203GS04 is the group dateGS05 is the group timeThe date interchange control number GS06 in this header must be identical to thesame data element in the associated functional group trailer, GE02.Comment:01A functional group of related transaction sets, in the scope of X12 standards, consistsof a collection of similar transaction sets enclosed by a functional group header and afunctional group trailer.Example:MandatoryOneTo indicate the beginning of a functional group and to provide control X*004010Data Element 03124043730533706280745508480Functional Identifier CodeCode identifying a group of application-related transaction sets.TM - Motor Carrier Delivery Trailer ManifestApplication Sender’s CodeCode identifying party sending transmission; codes that bothtrading partners agreed to.Application Receiver’s CodeCode identifying party receiving transmission; codes that bothtrading partners agreed to.DateDate (YYYYMMDD)TimeTime (HHMM)Group Control NumberAssigned number the sender originates and maintains.Responsible Agency CodeCode used in conjunction with data element 480 to identify thestandard issuer.X - Accredited Standards Committee X12Version / Release / Industry Identifier CodeCode indicating the version, release, subrelease and industryidentifier of the EDI standard being used.20Last Reviewed /2MAN1/12
ST Starting SegmentLevel:Loop:Usage:Max Use:Purpose:HeaderSemantic:01The transaction set identifier (ST01) the interchange partners translation routines useto select the appropriate transaction-set definition.Comment:01A functional group of related transaction sets, in the scope of X12 standards, enclosedby a functional group header and a functional group trailer.Example:MandatoryOneTo indicate the beginning of a transaction set and to assign a control number.ST*212*000010001Data Element Transaction Set Identifier CodeCode uniquely identifying a Transaction set.212 - Motor Carrier Delivery Trailer ManifestTransaction Set Control NumberIdentifying control number that must be unique in thetransaction set functional group that the originator assigns for atransaction set.This number is composed of the one- to five-digit datainterchange control number (five low-order digits from dataelement 28 from the associated functional header) subscriptedwith a four-digit serial number beginning with 0001, whichindicates the transaction set’s position in the transmittedfunctional group. The sender assigns the subscripted, four-digitserial number sequentially and increments the number by one.21Last Reviewed 10/29/13MID3/3MAN4/9
ATA Beginning Segment for the Motor Carrier Delivery Trailer ManifestLevel:Loop:Usage:Max Use:Purpose:HeaderSemantic:01MandatoryOneTo transmit identifying numbers and other basic data related to the transaction set0203Example:ATA01 is the Standard Carrier Alpha Code (SCAC) of the carrier that is deliveri
Oct 29, 2013 · Electronic Data Interchange X12 Standards, reflecting Version 004 Release 010 (004010), dated December 1997. This publication is available from DISA, 1800 Diagonal Road, Sui
