Transcription
DepartmentofDefenseDoDTransportationElectronic DataInterchange (EDI)ConventionASC X12 Transaction Set 858Freight Government Bill ofLading Shipment Information(Version 003050)DRAFTMarch 1997961101
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONFREIGHT GOVERNMENT BILL OF LADING SHIPMENT rtationElectronic DataInterchange (EDI)ConventionASC X12 Transaction Set 858Freight Government Bill ofLading Shipment Information(Version 003050)DRAFTTechnical Secretariat for DTEDIDefense Logistics Management Standards OfficeFort Belvoir, VA 22060-6221961101ii
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.00305010.0 DoD 858 CONVENTIONASC X12 Transaction Set 858Shipment Information (Version 003050)Formatting Government Bill of Lading information using theX12.18 Transaction Set 858 Shipment Information970321DRAFT10.0
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050(Blank Page)10.0.0DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050ContentsFormatting Government Bill of Lading information using theX12.18 Transaction Set 858 Shipment Information (Version003050).10.i Introduction10.1 Reserved10.2 Control Segments10.3 Reserved10.4 Reserved10.5 Data Element Cross-Reference Matrix10.6 Reserved10.7 DoD Conventions10.A Blank Government Bill of Lading10.B Empty10.C Examples - 858 Shipment Information for the GBL(Form 1103)10.D Tables - Looping Logic for Cross-Reference DataGroups10.F Additional Government Code Lists10.X Change Summary Report for Section 10.5970321DRAFT10.0.1
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050(Blank Page)10.0.2DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.00305010.i INTRODUCTIONThis is an Electronic Data Interchange (EDI) systems design document that describes the standard or "convention" the Departmentof Defense (DoD) uses to process a Government Bill of Lading(Standard Form 1103) using the ASC X12.18 Transaction Set 858Shipment Information (003050). It contains information for thedesign of interface computer programs that link systems applicationcomputer programs with an EDI translator computer program.To obtain information about the use of this implementation convention, contact the:United States Transportation CommandJ4-LT508 Scott DriveScott Air Force Base, IL 62225-7001To obtain DoD conventions or ASC X12 guidance or to recommendDoD conventions or ASC X12 maintenance, contact the:Defense Logistics Management Standards OfficeAttn: DLMSO (Room 1655), HQ DLA8725 John J Kingman Rd., Suite 2533Ft. Belvoir, VA 22060-6221Who Needs to Use This DocumentComputer programmers can use this document to relate the data inan EDI transaction with data requirements from their specificapplication database. Conversely, programmers can identify wheretheir applications data requirements should be carried in an EDItransaction.Why Use a ConventionThere are more ways to complete an EDI transaction than thereare ways to fill out a blank form. A convention defines the rulesfor filling in or "populating" an EDI transaction with a specificdata set. Following a convention ensures the integrity of data thatis produced and processed by EDI capable computer systems.ContentsFour sections are included in this document.970321 Section 10.2, Control Segments, identifies the specific datarequirements for formatting the EDI interchange control segments needed to send and receive EDI transactions. Section 10.5, Application Mapping Matrix, lists the DoD’s datarequirements and specifies where each data element should becarried in the transaction set. This section can be used to mapan existing application database into the transaction set.DRAFT10.i
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTION10.iiGOVERNMENT BILL OF LADING858.A.003050 Section 10.7, DoD Conventions, lists the layout of the targettransaction set by segment and data element. Identified alongside each transaction set data element is the application mapping data element from Section 10.5. This section can be usedto interpret segments and data elements of a populated transaction set. Appendices may contain examples of populated transactionsets, DoD code lists, and other items that serve as referencesfor software developers.DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.00305010.2 Control SegmentsOverviewThis chapter describes the EDI control segments (interchange control and functional group segments). The control segment information was derived from the ASC X12 Standards Draft Version 3Release 5 (003050).PurposeThis chapter identifies the specific data requirements for formattingthe EDI control segments when transmitting and receiving EDItransactions. The format and data content of the control segmentsare usually managed by EDI translation software. The data requirements described herein should be used to set control segmentformats when installing or initializing translation software fortransmission and reception of EDI transactions.ContentsTwo items are included in this chapter. Table 10.2-1, Interchange Control Segment Hierarchy, identifies the control segments in their order of occurrence in anEDI communications interchange. Table 10.2-2, DoD Convention ASC X12 Control Segments,presents a detailed description of the DoD’s data conventionsfor formatting EDI standard control segments. All segmentsidentified in Table 10.2-1 are broken down and described bytheir discrete data elements.Special InstructionsAny unique eight-bit (byte) character could serve as data elementseparator, segment terminator, or subelement separator, providedeach character is disjoint from all data elements within an interchange and that these do not conflict with telecommunicationsprotocols necessary to the transmission of the interchange. Thefollowing recommended values conform with information published in Electronic Data Interchange, X12 Standards, Version 3,Release 5, Interchange Control Structures, Section 4.3 DelimiterSpecifications.Data Element SeparatorWhile the data element separator is graphically displayed as anasterisk (*) in ASC X12 documentation, it is the value employedin the fourth byte of an interchange envelope that actually assignsthe separator that the translators will use throughout an interchange.970321DRAFT10.2.1
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050ASC X12 recommends the ASCII character with hexadecimal value"1D" for use as the data element separator (gs).Segment TerminatorLikewise, the control envelope establishes the byte value used forsegment termination within an interchange. ASC X12 documentation usually portrays this as a new line (n/l) character, but the actualsegment terminator for an interchange will be the byte valueoccurring immediately following the ISA16 segment.ASC X12 recommends the ASCII character with hexadecimal value"1C" for use as the segment (fs) terminator.Subelement SeparatorThe ISA segment provides a discrete element (ISA16) for definingthe subelement separator within an interchange. Although designated as reserved for future expansion in Version 3, Release 5, avalue in ISA16 is required.ASC X12 recommends the ASCII character with hexadecimal value"1F" for use as the subelement separation (us) character.10.2.2DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050Interchange Control EnvelopeControl SegmentsIndustryPos SegNo. IDNameReqDesUseUSE10ISAInterchange Control HeaderM1USE20GSFunctional Group HeaderM1Loop Grouped Transactions 970321USE30GEFunctional Group TrailerM1USE40IEAInterchange Control TrailerM1DRAFT10.2.5
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050(Blank Page)10.2.6DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050TABLE 10.2-2DoD Convention ASC X12 Control Segments970321DRAFT10.2.7
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050(BLANK PAGE)10.2.8DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF terchange Control HeaderMTo start and identify an interchange of one ormore functional groups and interchange-related control segments.The interchange control number value in thisheader must match the value in the same dataelement in the corresponding interchange control trailer.Data Element SummaryRef.Des.ISA01DataElement NameI01AttributesAuthorization InformationM ID2/2QualifierCode to identify the type of information in the authorization information.Authorization Qualifier[001 ]CodeDefinition00No Authorization Information Present.ISA02I02Authorization InformationM AN 10/10Information used for additional identification orauthorization of the sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier.ISA03I03Security Information QualifierM ID2/2Code to identify the type of information in the security information.Authorization Info[002 ]If no authorization information isagreed to by the trading partners, fillfield with zeroes.Security Qualifier[003 ]ISA04970321I04CodeDefinition00No Security Information Present.Security InformationM AN 10/10This is used for identifying the security informationabout the sender or the data in the interchange. Thetype of information is set by the SecurityInformation Qualifier.DRAFT10.2.9
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050Security Info[004 ]If no security information is agreedto by the trading partners, fill fieldwith zeroes.ISA05I05Interchange ID QualifierM ID2/2Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified.ISA06I06Interchange Sender’s IDM AN 15/15Identification code published by the sender for otherparties to use as the receiver ID to route data to them.The sender always codes this number in the sender IDelement.ISA07I05Interchange ID QualifierM ID2/2Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified.ISA08I07Interchange Receiver’s IDM AN 15/15Identification code published by the receiver of thedata. When sending, it is used by the sender as theirsending ID, thus other parties sending to them will usethis as a receiving ID to route data to them.Sender Qualifier[005 ]Use authorized X12 code list.Sender ID[006 ]DoD activities use Departmentof Defense Activity Address Code(DoDAAC) or other code coordinatedwith the Defense Transportation EDIProgram Administrator. Non-DoDactivities use identification code qualified by ISA05 and coordinated withvalue-added network (VAN).Interchange Qualifier[007 ]Use authorized X12 code list.10.2.10DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050Receiver ID[008 ]DoD activities use Departmentof Defense Activity Address Code(DoDAAC) or other code coordinatedwith the DefenseTransportation EDIProgramAdministrator. Non-DoDactivities use identification code qualified by ISA07 and coordinated withvalue-added network (VAN).ISA09I08Interchange DateDate of the interchange.M DT6/6ISA10I09Interchange TimeTime of the interchange.M TM4/4ISA11I10Interchange Control StandardsM ID1/1IdentifierCode to identify the agency responsible for the controlstandard used by the message that is enclosed by theinterchange header and trailer.Date[009 ]Date assigned by translationsoftware.Time[010 ]Time, expressed in HHMM format,assigned by translation software.Standards ID[011 ]ISA12I11CodeDefinitionUU.S. EDI Community of ASC X12, TDCC, andUCSInterchange Control VersionM ID5/5NumberThis version number covers the interchange controlsegments.Version ID[012 ]Version/release of control segment, as defined or agreed upon bythe trading partners.970321DRAFTCodeDefinition00305Draft Standard for Trial Use Approved forPublication by ASC X12 Procedures ReviewBoard Through October 199410.2.11
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050ISA13I12Interchange Control NumberM N09/9This number uniquely identifies the interchange datato the sender. It is assigned by the sender. Togetherwith the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that thesender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.ISA14I13Acknowledgment RequestedM ID1/1Code sent by the sender to request an interchange acknowledgement.Interchange Control Number[013 ]Number assigned by translationsoftware.Acknowledgment Request[014 ]Code value agreed upon by tradingpartners.ISA15I14CodeDefinition01No Acknowledgment RequestedInterchange Acknowledgement RequestedTest IndicatorM ID1/1Code to indicate whether data enclosed by this interchange envelope is test or production.Test Indicator[015 ]Code value agreed upon by tradingparters.ISA16I15CodeDefinitionPTProduction DataTest DataSubelement SeparatorM AN 1/1This is a field reserved for future expansion in separating data element subgroups. (In the interest of a migration to international standards, this must bedifferent from the data element separator).Subelement Separator[016 ]ASC X12 recommends the ASCIIcharacter with hexadecimal value"1F" for use as the subelementseparation character.10.2.12DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF ntax Notes:GSFunctional Group HeaderMTo indicate the beginning of a functionalgroup and to provide control information.00 A functional group of related transactionsets, within the scope of X12 standards,consists of a collection of similar transaction sets enclosed by a functional groupheader and a functional group trailer.04 GS04 is the Group Date.05 GS05 is the Group Time.06 The data interchange control numberGS06 in this header must be identical tothe same data element in the associatedFunctional Group Trailer GE02.Data Element SummaryRef.Des.GS01DataElement Name479AttributesFunctional ID CodeM ID2/2Code identifying a group of application related Transaction Sets.Functional ID[020 ]CodeDefinitionSI858 - Shipment InformationGS02142Application Sender’s CodeM AN 2/15Code identifying party sending transmission. Codesagreed to by trading partners.GS03124Application Receiver’s CodeM AN 2/15Code identifying party receiving transmission. Codesagreed to by trading partners.Sender’s Code[021]DoD activities use Departmentof Defense ActivityAddress Code(DoDAAC). Non-DoD activities useidentification code assigned by DoDactivity. Recommend for increasedsecurity that non-DoD code differfrom that used in ISA06.970321DRAFT10.2.13
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050Receiver’s Code[022]DoD activities use Departmentof Defense ActivityAddress Code(DoDAAC). Non-DoD activities useidentification code assigned by DoDactivity. Recommend for increasedsecurity that non-DoD code differfrom that used in ISA08.GS04373DateDate (YYMMDD).M DT6/6GS05337TimeM TM 4/6Time expressed in 24 hour clock time (HHMMSS)(Time range: 000000 through 235959).GS0628Group Control NumberM N01/9Assigned number originated and maintained by thesender.GS07455Responsible Agency CodeM ID1/2Code used in conjunction with Data Element 480 toidentify the issuer of the standard.Date[023]Date assigned by translationsoftware.Time[024 ]Time, expressed in HHMM format,assigned by translation software.Group Control Number[025 ]Number assigned by translationsoftware.Agency Code[026 ]Indicates that an ANSI X12 standardis being d Standards Committee X12Version/Release/Industry IdM AN 1/12CodeCode indicating the version, release, subrelease and industry identifier of the EDI standard being used (seeX12 Dictionary).DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050Version/Release[027 ]Version/release for transactions inthe functional group. See X12Dictionary for source code list.970321DRAFTCodeDefinition003050Draft Standard Approved for Publication by ASCX12 Procedures Review through October 1994.10.2.15
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050Segment:Usage:GEFunctional Group TrailerMPurpose:To indicate the end of a functional group andto provide control information.Comment:00 The use of identical data interchangecontrol numbers in the associated functional group header and trailer is assignedto maximize functional group integrity.The control number is the same as thatused in the corresponding header.02 The data interchange control numberGE02 in this trailer must be identical tothe same data element in the associatedFunctional Group Header GS06.Syntax Notes:Data Element SummaryRef.Des.DataElement NameAttributesGE0197Number of Included SetsM N01/6Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element.GE0228Group Control NumberM N01/9Assigned number originated and maintained by thesender.Number of Segments[028 ]Number assigned by translationsoftware.Group Control Number[029 ]Number assigned by the translationsoftware. This control numbermatches the control number thatoccurs in GS06.10.2.16DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF erchange Control TrailerMTo define the end of an interchangeof one or more functional groups andinterchange-related control segments.The interchange control number in this trailermust match the value in the same data elementin the corresponding interchange header.Data Element SummaryRef.Des.DataElement NameAttributesIEA01I16Number of Included FunctionalM N01/5GroupsA count of the number of functional groups includedin a transmission.IEA02I12Interchange Control NumberM N09/9This number uniquely identifies the interchange datato the sender. It is assigned by the sender. Togetherwith the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that thesender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.Functional Group Count[040 ]Number assigned by translationsoftware.Interchange Control Number[041 ]Number assigned by translationsoftware. This number matches thenumber that occurs in ISA13.970321DRAFT10.2.17
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050(Blank Page)10.2.18DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.00305010.5 APPLICATIONMAPPING MATRIXOverviewThis chapter lists the data element cross-reference for DoD ASCX12.18 Transaction Set 858 Shipment Invormation (003050). Wederived the application mapping cross-reference from the following: Review of the rules in the Defense Traffic Management Regulations (DTMR). Analysis of ASC X12.18 Transaction Set 858 Shipment Information Transaction Set (Version 003050). Analysis of sample paper GBLs. Comments submitted by Defense activities and commercialcarriers involved in the DoD’s EDI program in transportation.PurposeThis chapter identifies the specific data in an application and theircorresponding EDI mapping into the Transaction Set 858. Theresultant application mapping matrix can be used to identify dataelements from an existing application database. If no applicationexists, the mapping matrix provides enough information to developa database design to automate the application. With an applicationin place, the matrix will expedite mapping of the database into acommercial EDI translation package. All trading partners who planto exchange the 858 with DoD can use this application mappingmatrix to develop their database/EDI translator interface program.ContentsTable 10.5-1, Application Mapping Matrix, lists all discrete dataelements required for the bill of lading, corresponding segments,and data element numbers for the ASC X12.18 Transaction Set 858Shipment Information.970321DRAFT10.5.1
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050(Blank Page)10.5.2DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050TABLE 10.5-1APPLICATION MAPPING MATRIXData Requirement for Generating U.S. GovernmentBills of Lading (Standard Form 1103) using theASC X12.18 Transaction Set 858 Shipment Information.How To Read This TableTable 10.5-1 cross-references discrete Government Bill of Ladingdata requirements to the corresponding segment and data elementsof the Transaction Set 858. The following definitions explain howTable 10.5-1 is organized. Understanding the information in thistable requires familiarity with EDI standards.Government ReferencesThe first three columns on the left in Table 10.5-1 identify thespecific bill of lading data element. DATA NAME: Lists individual data elements required tocomplete a Government Bill of Lading. Users should identifythese elements with a data name in their internal data basesystems. INDEX: Three entries may appear in this column and representvarious levels of indexing used to sort the data names in adata dictionary. DATA GRP: This column contains a numeric value which isused to classify data elements to a functional area of a businesstransaction set. See Special Instructions below for furtherexplanation.EDI ReferencesThe remaining seven columns identify the detailed mapping of eachdata name into Transaction Set 858. Use of these references isexplained below in "How To Use This Table".970321 TBL: The table area of the transaction set where the data aremapped. 1 header, 2 detail, 3 summary. POS: The sequential position of a specific segment within thetable area of the transaction set. REF DES: The alphanumeric characters identify a transactionset segment; the two numeric characters in the column identifya data element position in the segment.DRAFT10.5.3
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050 DE #: The EDI data element number that appears at thatposition in the segment. DoD REQ (Segment): The M designator indicates mandatoryusage for a segment. Unless specifically stated, the C (Conditional) designator should be interpreted as "if available." DoD REQ (Element): The mandatory (M) designator for anelement applies only if the segment is used. Unless specifically stated, the C designator should be interpreted as "ifavailable." VALUE: The recommended code value(s) that should be used. DoD CONVENTIONS NOTES: Additional information aboutthe data as they apply to DoD use. CHANGE NOTE: This note summarizes a change made to thedata element since the last publication of the convention document. In addition, the requester of the change is noted at theend of the change note. PICTURE CLAUSE: {This information may be included infuture publications. It may be used to further standardizeand/or clarify the format of data generated by trading partnerapplication systems.}How To Use This TableThis table traces a data element to a specific data element in theEDI transaction set convention Table 10.7-3.1. Select any data element from the DATA NAME list.2. Identify the TBL, POS, and REF DES for that DATA NAME.3. Go to Table 10.7-2, DoD Segment Hierarchy.4. Find the TBL (Table 1 header, etc.) in the hierarchy.5. Locate the segment that corresponds to the POS and the REFDES. (NOTE: Where the POS does not appear in some hierarchytables, use the segment ID identified by the alphanumeric characters in the REF DES.)6. In the left-hand column, identify the page number of the segmentID.7. Turn to that page number in Table 10.7-3.8. In Table 10.7-3, find the REF DES from step 2 under the Ref.Des. column to the right of the double vertical lines on the page.9. You have now traced a data element from Table 10.5-1 to Table10.7-3.10.5.4DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050From Table 10.5-1, the DATA NAME along with its INDEX andthe DoD CONVENTION appear in the left-hand column of Table10.7-3. The EDI standard definition of the data element appearsin the right-hand column of the page.Each DATA NAME from Table 10.5-1 can be traced to the transaction set in this manner.NOTE: To reference from Table 10.7-3 back to Table 10.5-1, usethe INDEX as a look-up key.Special Instructions970321 The electronic Government Bill of Lading (GBL) is dividedinto 535 data elements. In Table 10.5-1, each data element isidentified by a unique index. This document attempts to separate the 535 data elements intological groups. Two hundred thirty one (231) of these dataare carried in the 858, Table 2 - Detail Area, within the LXsegment loop. (See Appendix C for examples.) The groups willprovide for a more structured and therefore more readableTransaction Set 858. Data carried in the X12 format must be identified by "qualifier" codes. Usually, these codes must be generated by theinterface software between the application data base and thetranslator. Data Groups (Data Grp) identify related data. The groups aredescribed below: Data Group 10 - Header Information. Elements in thisgroup, with few exceptions, appear only once on a paperGBL. They occur in the header area of the transactionset. Data Group 60 - Equipment Information. Use this groupaccording to the type of shipment (e.g., Load or Less thanLoad). Repeat this group for each piece of equipmentfurnished by the carrier. Additionally, classify equipmentordered and shipper owned equipment under this group.Definitions of Primary Equipment, Secondary Equipment,and Shipper Owned Equipment must be followed whenimplementing this data group. See Appendix C examplesfor a detailed explanation of equipment definitions. Data Group 70 - Address Information. Repeat this groupfor each address. Data Group 71 - Destination Address Information. Data Group 72 - Origin Address Information. Data Group 73 - Consignee Address Information.DRAFT10.5.5
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTION10.5.6GOVERNMENT BILL OF LADING858.A.003050 Data Group 74 - Shipper Address Information. Data Group 75 - Diversion or Reconsignment AddressInformation. Data Group 76 - Transfer Point Address Information. Data Group 77 - Invoice Address Information. Data Group 78 - Issuing Officer Address Information. Data Group 79 - FOB Point Address Information. Data Group 80 - Stop-off Information. Repeat this groupfor each shipment stop-off, including destination. Neverinclude the origin address in this group. Data Group 100 - Commodity Header Information. As ageneral rule, use this group once for each line item. Data Group 120 - Commodity Detail Information. Thisgroup can repeat under group 100. Repeat this group foreach type pack under a line item. Data Group 190 - HAZMAT Information. This group mayoccur once for each group 100. Data Group 200 - Shipment Weight Information. Repeatthis group for each weight classification, i.e. net, tare,pallet, etc. Data Group 300 - Accessorial/Protective Service Information. Repeat this group for each service furnished for theshipment. Data Group 301 - Fuel Surcharge Information. Data Group 400 - Commodity Summary Information. Repeat this group for each commodity type in the shipment. Data Group 500 - Quality Control Information. Use thisgroup once per GBL. Data Group 990 GBL Totals Information. Use this grouponce per GBL. DoD recommends attributes for many data elements. Theseattributes were obtained from the Electronic Operatin Instructions for Defense Shipping Activities (May 1994), MilitaryTraffic Management Command. Each occurrence of a segment is identified by a separate dataelement (segment header). This will become standard practicefor all conventions that address version 003050 and higher.DRAFT970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONGOVERNMENT BILL OF LADING858.A.003050 970321Changes since the last publication date (950215) are underlined. In addition, Appendix X contains a summary of allchanges.DRAFT10.5.7
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONDoD INFORMATIONIndexDGData NameNotes and Codes858 Freight GBL858.A.003050X12 SEGMENT l Pos DesUseRpt LvID110 ST SEGMENTM210 Transaction Set Identifier CodeMMX12 ELEMENT INFORMATIONRefDesDE #(Simple)Attributes110ID 3/31101ST01143MAN 9/91101ST02329M AN 4/9130(Composite)Attributes1ID3/3858 - X12.18 Shipment Information310 Transaction Set Control NumberM410 BX SEGMENTM510 Transaction Set Purpose CodeMID 2/21301BX01353MID2/2MID 1/21301BX0291MID1/2MID 2/21301BX03146MID2/2OAN 8/81301BX04145M AN 1/30M100 - Original01 - Cancellation04 - Change14 - Advance Notification20 - Final Transmission610 Transportation Method Code (Mode Code)See Section 6.0 for appropriate code values.710 Method of PaymentCC - CollectCD - Collect on DeliveryPP - Prepaid (by Seller)810 GBL NumberShould always be included in DoD shipment information for a GBLtransaction. First position is type alpha, followed by seven positionsof numeric. Carry either original or most recent GBL number here.Carry other alternate bill of lading numbers in the N9 where theGBL number appears. Note: Do not use any punctuation or specialcharacters.4.4FINAL DRAFT19970321
DEPARTMENT OF DEFENSETRANSPORTATION EDI CONVENTIONDoD INFORMATIONIndex9DGData NameNotes and Codes10 Transportation Company Tendered To (SCAC)858 Freight GBL858.A.003050X12 SEGMENT l Pos DesUse
TRANSPORTATION EDI CONVENTION 858.A.003050 10.i INTRODUCTION This is an Electronic Data Interchange (EDI) systems design docu-ment that describes the standard or "convention" the Department of Defense (DoD) uses to process a Government Bill of Lading (Standard Form 1103) using the ASC X12.18 Transaction Set 858 Shipment Information (003050).
