Transcription

214 Transportation CarrierShipment Status MessageX12/V4010/214: 214 Transportation Carrier Shipment Status MessageVersion: 1.6 FinalAuthor:Company:Publication:Modified:Notes:CIT Carrier ConnectivityC.H. Robinson3/26/20203/26/2020Added case count andpallet count in AT8

3/26/2020Transportation Carrier Shipment Status Message - 214Table of Contents214. . .Transportation Carrier Shipment Status Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 1ISA. . .Interchange Control Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 4GS. . .Functional Group Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 6ST. . .Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 8. . .B10 Beginning Segment for Transportation Carrier Shipment Status Message . . . . . . . . . . . . . . . . . . . . . . . . . . PH 9L11. .Business Instructions and Reference Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 10. .MAN Marks and Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 11. .0100 Loop Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 12N1. .Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 13N3. .Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 14N4. .Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 15. .G62 Date/Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 16. .0100 Loop Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 17N1. .Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 18N3. .Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 19N4. .Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 20. .G62 Date/Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 21. .0200 Loop Assigned Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 22LX. .Assigned Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 23. .0205 Loop Shipment Status Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 24. .AT7 Shipment Status Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 25. .MS1 Equipment, Shipment, or Real Property Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 27. .MS2 Equipment or Container Owner and Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 29L11. .Business Instructions and Reference Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 30L11. .Business Instructions and Reference Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 31L11. .Business Instructions and Reference Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 32Q7. .Lading Exception Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 33. .AT8 Shipment Weight, Packaging and Quantity Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 34SE. .Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 35GE. .Functional Group Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 36IEA. .Interchange Control Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 37CHRLTLX12-214.ecsi

3/26/2020Transportation Carrier Shipment Status Message - 214214Transportation Carrier Shipment StatusMessageFunctional Group QMPurpose: This Draft Standard for Trial Use contains the format and establishes the data contents of theTransportation Carrier Shipment Status Message Transaction Set (214) for use within the context of an ElectronicData Interchange (EDI) environment. This transaction set can be used by a transportation carrier to provideshippers, consignees, and their agents with the status of shipments in terms of dates, times, locations, route,identifying numbers, and conveyance.Not Defined:PosIdSegment NameReqMax Use010020ISAGSSTB10MMMM1111Must useMust useUsedMust use030L11O300Used035MANInterchange Control HeaderFunctional Group HeaderTransaction Set HeaderBeginning Segment forTransportation CarrierShipment Status MessageBusiness Instructions andReference NumberMarks and NumbersO1NameAddress InformationGeographic LocationDate/TimeMOOO1211LOOP ID - 0100050070080100N1N3N4G62N1N3N4G62MOOO1211LOOP ID - UsedUsedUsedUsed1Assigned NumberM1LOOP ID - 0205140143UsageN0/050LN0/0501NameAddress InformationGeographic LocationDate/TimeNotesC0/0352LOOP ID - 0100050070080100RepeatMust use2Shipment Status DetailsEquipment, Shipment, orReal Property LocationEquipment or ContainerOwner and TypeBusiness Instructions andReference NumberBusiness Instructions andReference NumberBusiness Instructions andReference NumberLading Exception CodeShipment Weight,Packaging and QuantityOM11Must useMust edUsed1

3/26/2020Transportation Carrier Shipment Status Message - 214PosId610SEGEIEASegment NameDataTransaction Set TrailerFunctional Group TrailerInterchange Control TrailerReqMax UseMMM111RepeatNotesUsageUsedMust useMust useNotes:0/050L0/0500/050L0/050OptionalTo identify a party by type of organization, name, and code.OptionalTo identify a party by type of organization, name, and code.Comments:0/035This is required if you are shipping a temperature controlled load for C.H. Robinson or when C.H.Robinson is the Shippers Agent for a customer.Transaction Notes:APPLICATION NOTES1. LTL Carrier SpecThis EDI 214 Load Status Message implementation guide pertains to Less Than Load (LTL) shipmentsfrom LTL carriers. This spec is NOT for Truckload carriers.2. Functional Acknowledgments.Please notify CH Robinson if you do not wish to receive 997 functional acknowledgements for the 214's.3. ErrorsCH Robinson will not be responsible for correcting data sent to us. CH Robinson will send 997functional acknowledgements, indicating the EDI syntax acceptance status of the received 214.4. Inbound 214 Load Status Events- Pickup or Delivery Event - Actual Dates and Times applicable to a pickup or delivery location of ashipment.X3 - Arrived at Pickup LocationAF - Departed Pickup LocationX1 - Arrived at Delivery LocationCD - Departed Delivery Location (delivery complete)- Check Call Event 'In Transit' - This is the actual date and time of a truck at a specified location enroute to a pickup or a delivery. This location will not be a pickup or a delivery location.X6- En Route to Location- See code list for additional codes.5. Timing- C.H. Robinson would like to recieve In-Transit updates every 15 minutes- C.H. Robinson needs to receive 214 status updates as close to the actual event as possible. Ideallywithin 15 minutes of the event.CHRLTLX12-214.ecs2

3/26/2020Transportation Carrier Shipment Status Message - 214C.H. Robinson Inbound 214 Structure:·A 214 load status report to C.H. Robinson should report a status(s) for one and only one location.For example, three 214's would be required to report a status(s) for each stop of a 3-stop load. A single214 may contain 2 statuses in separate AT7 Loops for the same location. However, C.H. Robinsonprefers only one status per 214.·Maximum of one LX Loop per 214 with a maximum of 2 AT7 loops in the LX.·CH Robinson needs to receive 214 status updates within one hour of the event 152*XXXXL11*5896152*AGL11*CHRW123456*OWN1*SH*BAW PLASTICS INCORPORATEDN3*CENTURY III BUSINESS CTR*2148 CENTURY DRIVEN4*JEFFERSON HILLS*PA*15025G62*86*20050812N1*CN*FINISH LINEN3*3308 N MITTOEFFER 08**CA*21SE*20*481810001CHRLTLX12-214.ecs3

3/26/2020Transportation Carrier Shipment Status Message - 214ISA Interchange Control HeaderPos:Max: 1Not Defined - MandatoryLoop: N/AElements: 16User Option (Usage): Must usePurpose: To start and identify an interchange of zero or more functional groups and interchange-related controlsegmentsElement Summary:RefIdElement NameISA01I01Authorization Information QualifierReqTypeMin/MaxUsageMID2/2Must useDescription: Code to identify the type of information in the Authorization InformationAll valid standard codes are used. (Total Codes: 7)ISA02I02Authorization InformationMAN10/10Must useDescription: Information used for additional identification or authorization of theinterchange sender or the data in the interchange; the type of information is set by theAuthorization Information Qualifier (I01)ISA03I03Security Information QualifierMID2/2Must useDescription: Code to identify the type of information in the Security InformationAll valid standard codes are used. (Total Codes: 2)ISA04I04Security InformationMAN10/10Must useDescription: This is used for identifying the security information about the interchangesender or the data in the interchange; the type of information is set by the SecurityInformation Qualifier (I03)ISA05I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designatethe sender or receiver ID element being qualifiedAll valid standard codes are used. (Total Codes: 38)ISA06I06Interchange Sender IDMAN15/15Must useDescription: Identification code published by the sender for other parties to use as thereceiver ID to route data to them; the sender always codes this value in the sender IDelementISA07I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designatethe sender or receiver ID element being qualifiedCodeList Summary (Total Codes: 38, Included: 1)Code Name02ISA08I07SCAC (Standard Carrier Alpha Code)Interchange Receiver IDMAN15/15Must useDescription: Identification code published by the receiver of the data; When sending, it isused by the sender as their sending ID, thus other parties sending to them will use this as areceiving ID to route data to themElement Notes:CHRLTLX12-214.ecs4

3/26/2020RefTransportation Carrier Shipment Status Message - 214IdElement NameReqTypeMin/MaxUsageMDT6/6Must useMTM4/4Must useMID1/1Must useTest ID RBTWTESTProduction ID RBTWISA09I08Interchange DateDescription: Date of the interchangeISA10I09Interchange TimeDescription: Time of the interchangeISA11I10Interchange Control StandardsIdentifierDescription: Code to identify the agency responsible for the control standard used by themessage that is enclosed by the interchange header and trailerAll valid standard codes are used. (Total Codes: 1)ISA12I11Interchange Control Version NumberMID5/5Must useDescription: Code specifying the version number of the interchange control segmentsCodeList Summary (Total Codes: 14, Included: 3)Code Name00400 Standard Issued as ANSI X12.5-199700401 Draft Standards for Trial Use Approved for Publication by ASC X12 ProceduresReview Board through October 199700402 Draft Standards for Trial Use Approved for Publication by ASC X12 ProceduresReview Board through October 1998ISA13I12Interchange Control NumberMN09/9Must useDescription: A control number assigned by the interchange senderISA14I13Acknowledgment RequestedMID1/1Must useDescription: Code sent by the sender to request an interchange acknowledgment (TA1)All valid standard codes are used. (Total Codes: 2)ISA15I14Usage IndicatorMID1/1Must useDescription: Code to indicate whether data enclosed by this interchange envelope is test,production or informationAll valid standard codes are used. (Total Codes: 3)ISA16I15Component Element SeparatorM1/1Must useDescription: Type is not applicable; the component element separator is a delimiter andnot a data element; this field provides the delimiter used to separate component dataelements within a composite data structure; this value must be different than the dataelement separator and the segment terminatorCHRLTLX12-214.ecs5

3/26/2020Transportation Carrier Shipment Status Message - 214Pos:GS Functional Group HeaderMax: 1Not Defined - MandatoryLoop: N/AElements: 8User Option (Usage): Must usePurpose: To indicate the beginning of a functional group and to provide control informationElement Summary:RefIdElement NameGS01479Functional Identifier CodeReqTypeMin/MaxUsageMID2/2Must useDescription: Code identifying a group of application related transaction setsCodeList Summary (Total Codes: 240, Included: 1)Code NameQMGS02142Transportation Carrier Shipment Status Message (214)Application Sender's CodeMAN2/15Must useDescription: Code identifying party sending transmission; codes agreed to by tradingpartnersGS03124Application Receiver's CodeMAN2/15Must useDescription: Code identifying party receiving transmission; codes agreed to by tradingpartnersElement Notes:Test ID RBTWTESTProduction ID RBTWGS04373DateMDT8/8Must useTM4/8Must useDescription: Date expressed as CCYYMMDDGS05337TimeMDescription: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H hours (00-23), M minutes (00-59), S integerseconds (00-59) and DD decimal seconds; decimal seconds are expressed as follows: D tenths (0-9) and DD hundredths (00-99)GS0628Group Control NumberMN01/9Must useDescription: Assigned number originated and maintained by the senderGS07455Responsible Agency CodeMID1/2Must useDescription: Code identifying the issuer of the standard; this code is used in conjunctionwith Data Element 480All valid standard codes are used. (Total Codes: 2)GS08480Version / Release / Industry IdentifierCodeMAN1/12Must useDescription: Code indicating the version, release, subrelease, and industry identifier of theEDI standard being used, including the GS and GE segments; if code in DE455 in GSsegment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are therelease and subrelease, level of the version; and positions 7-12 are the industry or tradeassociation identifiers (optionally assigned by user); if code in DE455 in GS segment is T,CHRLTLX12-214.ecs6

3/26/2020RefTransportation Carrier Shipment Status Message - 214IdElement Namethen other formats are allowedReqTypeMin/MaxUsageCodeList Summary (Total Codes: 39, Included: 1)CodeName004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Boardthrough October 1997Semantics: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 theassociated functional group trailer, GE02.Comments:1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection ofsimilar transaction sets enclosed by a functional group header and a functional group trailer.CHRLTLX12-214.ecs7

3/26/2020Transportation Carrier Shipment Status Message - 214Pos: 010ST Transaction Set HeaderMax: 1Not Defined - MandatoryLoop: N/AElements: 2User Option (Usage): UsedPurpose: To indicate the start of a transaction set and to assign a control numberElement Summary:RefIdElement NameST01143Transaction Set Identifier CodeReqTypeMin/MaxUsageMID3/3Must use4/9Must useDescription: Code uniquely identifying a Transaction SetCodeList Summary (Total Codes: 298, Included: 1)Code Name214ST02329Transportation Carrier Shipment Status MessageTransaction Set Control NumberMANDescription: Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setCHRLTLX12-214.ecs8

3/26/2020Transportation Carrier Shipment Status Message - 214Pos: 020B10 Beginning Segment forMax: 1Not Defined - MandatoryTransportation CarrierShipment Status MessageLoop: N/AElements: 7User Option (Usage): Must usePurpose: To transmit identifying numbers and other basic data relating to the transaction setElement Summary:RefIdElement NameB1001127Reference IdentificationReqTypeMin/MaxUsageXAN1/30Must useDescription: Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierElement Notes: Carrier Assigned Pro NumberB1002145Shipment Identification NumberOAN1/30UsedDescription: Identification number assigned to the shipment by the shipper that uniquelyidentifies the shipment from origin to ultimate destination and is not subject to modification;(Does not contain blanks or special characters)Element Notes: C.H. Robinson Load NumberB1003140Standard Carrier Alpha CodeMID2/4Must useON01/3UsedID2/3Not used1/30Not usedDescription: Standard C