Transcription
Ryder Transportation EDIElectronic Data InterchangeEDI 997Functional AcknowledgementVersion 004010Document: Version: 2.2Document Date: May 10, 2011
Ryder Transportation Management2997 Functional Acknowledgement Transaction Set– IntroductionRyder uses the EDI 997 in response to the EDI 204 as a first line confirmation that thecarrier has received and processed the EDI 204. Ryder reconciles all EDI 997’s and mayreassign a load if an EDI 997 is not sent in response.Ryder will send an EDI 997 in response to all transactions sent to Ryder, the EDI 990 andEDI 214. Ryder requires the carrier to monitor and reconcile the EDI 997’s and contactthe Ryder EDI group in the event that an EDI 997 is not received within 24 hours.Ryder Enterprise Production Version 2.2EDI Standard Version 004010May 10, 2011
Ryder Transportation Management3997 Sample 0909*0714*U*00401*000002731*0*P*: 5398*X*004010 ST*997*453980001 AK1*SM*10145398 AK2*204*10145398 AK5*A AK9*A*1*1*1 SE*6*453980001 GE*1*10145398 IEA*1*000002731 Ryder Enterprise Production Version 2.2EDI Standard Version 004010May 10, 2011
Ryder Transportation Management4997 Functional AcknowledgmentFunctional Group ID FAIntroduction:This Draft Standard for Trial Use contains the format and establishes the data contents of the FunctionalAcknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI)environment. The transaction set can be used to define the control structures for a set of acknowledgmentsto indicate the results of the syntactical analysis of the electronically encoded documents. The encodeddocuments are the transaction sets, which are grouped in functional groups, used in defining transactionsfor business data interchange. This standard does not cover the semantic meaning of the informationencoded in the transaction sets.Pos.No.Seg.IDNameReq.Des.010STTransaction Set HeaderM1020AK1Functional Group Response HeaderM1030AK2O1040AK3Data Segment NoteO1050AK4Data Element NoteO99060AK5Transaction Set Response TrailerM1070AK9Functional Group Response TrailerM1080SETransaction Set TrailerM1Max.UseLOOP ID - AK2Transaction Set Response HeaderLoopRepeatNotes andComments99LOOP ID - AK399c1Transaction Set Comments1.The data segments of this standard are used to report the results of the syntactical analysis of thefunctional groups of transaction sets; they report the extent to which the syntax complies with thestandards for transaction sets and functional groups. They do not report on the semantic meaning ofthe transaction sets (for example, on the ability of the receiver to comply with the request of thesender).Ryder Enterprise Production Version 2.2EDI Standard Version 004010May 10, 2011
Ryder Transportation ManagementSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:5ST Transaction Set Header010Mandatory1To indicate the start of a transaction set and to assign a control number1The transaction set identifier (ST01) is used by the translation routines ofthe interchange partners to select the appropriate transaction set definition(e.g., 810 selects the Invoice Transaction Set).Comments:Ref.Des.AttributesST01ST02Data Element SummaryDataElement Name143329Transaction Set Identifier CodeM ID 3/3Code uniquely identifying a Transaction SetEDI 997's Are Required In Response To All EDI 204's. The 997 is expectedwithin 1 hour from the time Ryder creates the EDI 204.997Functional AcknowledgmentTransaction Set Control NumberM AN 4/9Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setRyder Enterprise Production Version 2.2EDI Standard Version 004010May 10, 2011
Ryder Transportation ManagementSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:6AK1 Functional Group Response Header020Mandatory1To start acknowledgment of a functional group12AK101 is the functional ID found in the GS segment (GS01) in thefunctional group being acknowledged.AK102 is the functional group control number found in the GS segment inthe functional group being Data Element SummaryDataElement Name47928Functional Identifier CodeMCode identifying a group of application related transaction setsSMMotor Carrier Load Tender (204)Group Control NumberMAssigned number originated and maintained by the senderRyder Enterprise Production Version 2.2EDI Standard Version 004010ID 2/2N0 1/9May 10, 2011
Ryder Transportation ManagementSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:7AK2 Transaction Set Response Header030AK2OptionalOptional1To start acknowledgment of a single transaction set12AK201 is the transaction set ID found in the ST segment (ST01) in thetransaction set being acknowledged.AK202 is the transaction set control number found in the ST segment in thetransaction set being Data Element SummaryDataElement Name143329Transaction Set Identifier CodeM ID 3/3Code uniquely identifying a Transaction Set997Functional AcknowledgmentTransaction Set Control NumberM AN 4/9Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setRyder Enterprise Production Version 2.2EDI Standard Version 004010May 10, 2011
Ryder Transportation ManagementSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Ref.Des.AttributesAK3018AK3 Data Segment Note040AK3OptionalOptional1To report errors in a data segment and identify the location of the data segmentData Element SummaryDataElement Name721AK302719AK303447AK304720Segment ID CodeM ID 2/3Code defining the segment ID of the data segment in error (See Appendix A Number 77)Segment Position in Transaction SetM N0 1/6The numerical count position of this data segment from the start of thetransaction set: the transaction set header is count position 1Loop Identifier CodeO AN 1/6The loop ID number given on the transaction set diagram is the value for thisdata element in segments LS and LESegment Syntax Error CodeO ID 1/3Code indicating error found based on the syntax editing of a segmentRyder Enterprise Production Version 2.2EDI Standard Version 004010May 10, 2011
Ryder Transportation ManagementSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:9AK4 Data Element Note050AK3OptionalOptional99To report errors in a data element or composite data structure and identify thelocation of the data element1In no case shall a value be used for AK404 that would generate a syntaxerror, e.g., an invalid character.Comments:Ref.Des.AttributesAK401Data Element SummaryDataElement 4Position in SegmentMCode indicating the relative position of a simple data element, or the relativeposition of a composite data structure combined with the relative position ofthe component data element within the composite data structure, in error; thecount starts with 1 for the simple data element or composite data structureimmediately following the segment IDElement Position in SegmentM N0 1/2This is used to indicate the relative position of a simple data element, or therelative position of a composite data structure with the relative position of thecomponent within the composite data structure, in error; in the data segmentthe count starts with 1 for the simple data element or composite data structureimmediately following the segment IDComponent Data Element Position in CompositeO N0 1/2To identify the component data element position within the composite that is inerrorData Element Reference NumberO N0 1/4Reference number used to locate the data element in the Data ElementDictionaryData Element Syntax Error CodeM ID 1/3Code indicating the error found after syntax edits of a data element1Mandatory data element missing3Too many data elements.4Data element too short.5Data element too long.6Invalid character in data element.7Invalid code value.8Invalid Date9Invalid TimeCopy of Bad Data ElementO AN 1/99This is a copy of the data element in errorRyder Enterprise Production Version 2.2EDI Standard Version 004010May 10, 2011
Ryder Transportation ManagementSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Ref.Des.AttributesAK50110AK5 Transaction Set Response Trailer060AK2OptionalMandatory1To acknowledge acceptance or rejection and report errors in a transaction setData Element SummaryDataElement Name717AK502718AK503718Transaction Set Acknowledgment CodeM ID 1/1Code indicating accept or reject condition based on the syntax editing of thetransaction setAAcceptedEAccepted But Errors Were NotedRRejectedTransaction Set Syntax Error CodeO ID 1/3Code indicating error found based on the syntax editing of a transaction set2Transaction Set Trailer Missing3Transaction Set Control Number in Header and Trailer DoNot Match4Number of Included Segments Does Not Match ActualCount6Missing or Invalid Transaction Set Identifier7Missing or Invalid Transaction Set Control NumberTransaction Set Syntax Error CodeO ID 1/3Code indicating error found based on the syntax editing of a transaction set2Transaction Set Trailer Missing3Transaction Set Control Number in Header and Trailer DoNot Match4Number of Included Segments Does Not Match ActualCount6Missing or Invalid Transaction Set Identifier7Missing or Invalid Transaction Set Control NumberRyder Enterprise Production Version 2.2EDI Standard Version 004010May 10, 2011
Ryder Transportation ManagementSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Ref.Des.AttributesAK90111AK9 Functional Group Response Trailer070Mandatory1To acknowledge acceptance or rejection of a functional group and report thenumber of included transaction sets from the original trailer, the accepted sets,and the received sets in this functional group1If AK901 contains the value "A" or "E", then the transmitted functionalgroup is accepted.Data Element SummaryDataElement Name715AK90297AK903123AK9042AK905716Functional Group Acknowledge CodeM ID 1/1Code indicating accept or reject condition based on the syntax editing of thefunctional groupAAcceptedEAccepted, But Errors Were Noted.RRejectedNumber of Transaction Sets IncludedM N0 1/6Total number of transaction sets included in the functional group orinterchange (transmission) group terminated by the trailer containing this dataelementNumber of Received Transaction SetsM N0 1/6Number of Transaction Sets receivedNumber of Accepted Transaction SetsM N0 1/6Number of accepted Transaction Sets in a Functional GroupFunctional Group Syntax Error CodeO ID 1/3Code indicating error found based on the syntax editing of the functional groupheader and/or trailer3Functional Group Trailer Missing4Group Control Number in the Functional Group Headerand Trailer Do Not Agree5Number of Included Transaction Sets Does Not MatchActual Count6Group Control Number Violates SyntaxRyder Enterprise Production Version 2.2EDI Standard Version 004010May 10, 2011
Ryder Transportation ManagementSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Ref.Des.AttributesSE01SE0212SE Transaction Set Trailer080Mandatory1To indicate the end of the transaction set and provide the count of thetransmitted segments (including the beginning (ST) and ending (SE) segments)1SE is the last segment of each transaction set.Data Element SummaryDataElement Name96329Number of Included SegmentsM N0 1/10Total number of segments included in a transaction set including ST and SEsegmentsTransaction Set Control NumberM AN 4/9Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setRyder Enterprise Production Version 2.2EDI Standard Version 004010May 10, 2011
EDI 997's Are Required In Response To All EDI 204's. The 997 is expected within 1 hour from the time Ryder creates the EDI 204. 997 Functional Acknowledgment 329 Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
