dod d - defense technical information center · dod d implementation ... 6.0.2 6.2.2 general...

AD-A246 614

Department'~ of

Defense DTICS ELECTE

FEB 26 199211

DoD DImplementationGuidelines forElectronic DataInterchange(EDI)

[ Ths document has been approved

for pblic release and sale; itslu e II

distlibution is unlimited. V

December 1991

922 292-0464224 0 76 IIIHfll~iimIEI

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDELINES

This document was produced by the Logistics Management Institute forDefense Logistics Agency under Contract MDA903-90-C-0006 with theDepartment of Defense. Permission to quote or reproduce any part of thisdocument - except for Government purposes - must be obtained from theDepartment of Defense Executive Agent for Electronic Commerce/ElectronicData Interchange/Protection of Logistics Unclassified/Sensitive Systems.

EXECUTIVE AGENT FOR EC/EDI/PLUSDefense Logistics Agency

Cameron StationAlexandria, VA 22304-6100

911101

DEPARTMENT OF DEFENSE

IMPLEMENTATION GUIDENES

PREFACE

The implementation guidelines presented in Volumes I and IIwere developed by the Department of Defense (DoD) for newparticipants in the electronic data interchange (EDI) program andfor documenting DoD's EDI data requirements.

Volume I contains Chapters 1-9. Those chapters describe thebackground, scope, and main issues that need to be consideredwhen implementing EDI.

Volume II contains Chapter 10 only; it establishes a baselineof DoD's conventions for implementing the American NationalStandards Institute (ANSI) Accredited Standards Committee(ASC) X12 uniform standards for electronic interchange ofbusiness transactions. This baseline is not all-encompassing.Functional analysts may need to supplement the conventionsto further clarify their use in a specific functional applicationsuch as the use of the 810 Invoice for progress payments oruse of the 856 Ship Notice/Manifest for the transfer or saleof an aviation fuel product. This type of supplement, calledan application-specific convention, is permitted. Implementorsshould check with the Executive Agent, their trade association,or trading partners to see if the conventions shown here are beingsupplemented or customized for their specific application.

In the application-specific convention, data segments and dataelements must comply with the conventions as defined in theguidelines. If the convention does not meet your needs, youcan request a convention be changed to include your specificdata requirements. Chapter 5, Maintenance, explains where to

SFosend your comments and how to make changes to the conven-Accesion For j tions by submitting data maintenance requests.NTIS CPA.&I

D C TA -]To determine whether an application-specific convention exists,D .aC ot ,:ed you should contact the DoD Executive Agent for EDI at theSJ

address below:

........... DoD Executive Agent for EDIBy.......... Defense Logistics AgencyD.t ib'tio:4 ATTN: DLA-ZIE. ., t - Cameron Station

Alexandria, VA 22304-6100/ Avaii a..!iCf

1st 120 iii

911220 Wi


iv 911220

DEPARTMENT OF DUBISE

IMPLEMENTATION GUIDENES

ACKNOWLEDGMENTS

The Department of Defense would like to thank the followingorganizations and their member companies for their assistance indeveloping the DoD Implementation Guidelines for ED!.

Accredited Standards Committee X12

Aerospace Industries Association

American Iron and Steel Institute

American Petroleum Institute

Automotive Industry Action Group

National Automated Clearinghouse Association

Data Interchange Standards Association

Electronic Data Interchange Association

Uniform Code Council, Inc.

911023 v

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDWLNES

vi 911023

DEPARTMENT OF DEF NSE

IMPLEMENTATION GUIDELINES

TABLE OF CONTENTS

VOLUME I

PREFACE iii

ACKNOWLEDGMENTS v

1.0 INTRODUCTION 1.0.1

1.1 PURPOSE OF THE GUIDELINES .... 1.0.1

1.2 SCOPE ................. 1.0.11.2.1 Adoption .... ............... 1.0.11.2.2 Waivers ..................... 1.0.2

1.3 RESPONSIBLE ENTITY ........... 1.0.2

1.4 INTRODUCTION TO EDI .......... 1.0.21.4.1 What Is EDI? .... ............ 1.0.21.4.2 What Is New About EDI? ......... 1.0.21.4.3 Who Creates These Standards? . . . .. . 1.0.31.4.4 What Resources Do I Need? ....... 1.0.31.4.5 What Third-Party Services Are

Available? .... .............. 1.0.41.4.6 What Are the Benefits? .......... 1.0.41.4.7 How Do I Get Started? ........ 1.0.7

1.5 HOW TO USE THE IMPLEMENTATIONGUIDELINES .................. 1.0.11

1.5.1 Guidelines, Standards,and Conventions ... .......... 1.0.11

1.5.2 Page Numbering ... .......... 1.0.121.5.3 Documentation of Industry

Conventions ................ 1.0.12

2.0 BUSINESS ISSUES 2.0.1

2.1 IMPLEMENTATION CONSIDERATIONS . 2.0.12.1.1 Staffing Requirements ........... 2.0.12.1.2 Implementation Checklist ......... 2.0.2

2.2 TIMING OF TRANSACTIONS ....... 2.0.5

2.3 MODES OF OPERATION .......... 2.0.5

2.4 SECURITY .... ............... 2.0.5

2.5 RECOVERY PROCEDURES ......... 2.0.62.5.1 Recovery Procedure Considerations . . 2.0.72.5.2 Disaster Recovery Considerations . . . 2.0.7

2.6 AUDIT CONSIDERATIONS ......... 2.0.72.6.1 Confidentiality ................ 2.0.8

911113 Vii


2.6.2 Integrity .... ............... 2.0.82.6.3 Authenticity .................. 2.0.9

3.0 LEGAL CONSIDERATIONS 3.0.1

3.1 INTRODUCTION ................ 3.0.1

3.2 FEDERAL LAW AND REGULATIONS.. 3.0.2

3.3 RECORD KEEPING AND EVIDENTIARYMATTERS ..................... 3.0.6

3.4 FREEDOM OF INFORMATION ACT . . 3.0.8

3.5 MATERIAL INSPECTION AND RECEIVINGREPORT (DD FORM 250) ......... 3.0.10

3.6 TRADING PARTNER AGREEMENTS . 3.0.11

3.7 THIRD-PARTY SERVICE PROVIDERAGREEMENTS ................ 3.0.13

4.0 SYSTEM ARCHITECTURE ANDENVIRONMENT 4.0.1

4.1 SYSTEM ARCHITECTURE OF THEDoD STANDARD SYSTEM ........ 4.0.1

4.1.1 Overview ............... 4.0.14.1.2 The Lawrence Livermore National

Laboratory Intelligent Gateway ..... .4.0.34.1.3 CALS Integration .............. 4.0.54.1.4 Trusted Systems/Computer Security

Integration .... .............. 4.0.64.1.5 Integrated Network Strategy ....... 4.0.84.1.6 EDI VAN Integration .......... 4.0.104.1.7 Procurement Bulletin Board

Integration .... ............. 4.0.10

4.2 SYSTEM ARCHITECTURES USED INPRIVATE INDUSTRY ........... 4.0.13

4.3 APPLICATION INTEGRATION .... 4.0.14

4.4 TRANSLATION ................ 4.0.14

5.0 MAINTENANCE 5.0.1

5.1 MAINTAINING GUIDELINES ....... 5.0.15.1.1 Development and Maintenance of DoD)

Conventions .................. 5.0.15.1.2 The Defense Logistics Standard

Systems (DLSS) and DefenseTransportation EDI ............. 5.0.2

5.2 MAINTAINING X12 STANDARDS.... 5.0.2

vim 911113


5.3 VERSION/RELEASE TIMING ........ 5.0.3

5.4 PROPOSED CHANGES ........... 5.0.4

6.0 COMMUNICATIONS 6.0.1

6.1 INTRODUCTION ................ 6.0.16.1.1 EDI Communications Network

Alternatives .... ............. 6.0.16.1.2 DoD Long-Haul Telecommunications

Guidance .... ............... 6.0.2

6.2 PROTOCOLS .... .............. 6.0.26.2.1 The Government Open Systems

Interconnection Profile .......... 6.0.26.2.2 General Services Administration's

FTS 2000 .................. 6.0.2

6.3 POINT-TO-POINT (DEDICATED)NETWORKS .................. 6.0.3

6.3.1 Impact of Government Open SystemsInterconnection Profile ........... 6.0.3

6.3.2 Impact of FTS 2000 ............ 6.0.4

6.4 THIRD-PARTY SERVICES (SWITCHEDNETWORKS AND VALUE-ADDEDSERVICES) .... ............... 6.0.4

6.4.1 Impact of Government Open SystemInterconnection Profile .. ........ 6.0.5

6.4.2 Impact of FTS 2000 ............ 6.0.56.4.3 Network Value-Added Services . . . 6.0.6

6.5 NETWORK INTERCONNECTIONS . . . 6.0.7

7.0 DoD BUSINESS MODELS 7.0.1

7.1 GENERAL BUSINESS MODEL ..... 7.0.1

7.2 SMALL BUSINESS MODEL(to be published) ................ 7.0.1

7.3 ORDERING SUPPLIES OR SERVICES . . 7.0.17.3.1 Indefinite Delivery Contracts ....... 7.0.17.3.2 Individual Purchases ............. 7.0.1

7.4 COMPUTER-AIDED ACQUISITIONAND LOGISTIC SUPPORT (CALS) . . . 7.0.5

7.5 ELECTRONIC FUNDS TRANSFERCORPORATE TRADE EXCHANGERULES .... ................. 7.0.5

7.5.1 Payment Information Process ....... 7.0.77.5.2 Potential Benefits of EFT/EDI ...... 7.0.77.5.3 Implementation Issues .......... 7.0.107.5.4 How to Get Started ........... 7.0.10

911113 ix

DEPARTMENT OF DBENSEIMPLEMENTATION GUIDE.NES

8.0 GLOSSARY 8.0.1

8.1 X12 GLOSSARY ................ 8.0.1

8.2 DoD GLOSSARY ... ........... 8.0.10

9.0 FORMS AND DOCUMENTS 9.0.1

VOLUME II

10.0 DoD CONVENTIONS FOR USINGASC X12 TRANSACTION SETS 10.0.1

10.1 INTRODUCTION ... ........... 10.0.1

10.2 CONTROL SEGMENTS .......... 10.0.110.2.1 Description of Use ... ......... 10.0.210.2.2 Control Segment Specifications. . . . 10.0.2

10.3 LARGE CODE LISTS MAINTAINED BYASC X12 (to be published) ......... 10.0.6

10.4 CODE LISTS NOT MAINTAINED BYASC X12 (to be published) ......... 10.0.6

10.5 DATA ELEMENT CROSS-REFERENCEMATRIX .... ............... 10.0.6

10.6 DATA SEGMENT CROSS-REFERENCEMATRIX ..... .............. 10.0.15

10.7 DoDIINDUSTRY CONVENTIONS . . 10.0.15

Note: The following sections represent the transactionsthat have been developed for this ImplementationGuidelines.

10.7.10 DoD Convention for Using the 810 Invoice

10.7.20 DoD Convention for Using the820 Payment Order/Remittance Advice

10.7.40 DoD Convention for Using the840 Request for Quotation

10.7.43 DoD Convention for Using the843 Response to Request for Quotation

10.7.50 DoD Convention for Using the850 Purchase Order

10.7.55 DoD Convention for Using the855 Purchase Order Acknowledgment

10.7.56 DoD Convention for Using the856 Ship Notice/Manifest

x 911113


10.7.61 DoD Convention for Using the861 Receiving Advice

10.7.63 DoD Convention for Using the863 Report of Test Results

10.7.97 DoD Convention for Using the997 Functional Acknowledgment

911113 xi


xii 911113

DEPARTMENT Of DEFENSE


10.0 DoD CONVENTIONS FORUSING ASC X12TRANSACTION SETS

This chapter defines the DoD transaction set conventions. Itincludes the instructions for implementing the control structureand definitions of the usage indicators and applicable codes.

10.1 INTRODUCTIONThe power of the ASC X12 standard is in its building blockconcept, which standardizes the essential elements of businesstransactions. It is analogous to a "standard bill of materials andthe construction specifications," which gives the architectflexibility in what can be designed with standardized materialsand procedures. The EDI system designer, like the architect,uses the ASC X12 standards to build business transactions thatare often different because of their function and yet utilize theASC X12 standards. The "bill of materials and the constructionspecification" of ASC X12 are the standards found in thepublished technical documentation.

ASC X12.3 - The Data Element Dictionary specifies the dataelements used in the construction of the segments that comprisethe transaction sets developed by ASC X12.

ASC X12.5 - The Interchange Control Structure provides theinterchange control segment (also called an envelope) of a headerand trailer for the electronic interchange through a data trans-mission; it also provide a structure to acknowledge the receiptand processing of the envelope.

ASC X12.6 - The Application Control Structure defines the basiccontrol structures, syntax rules, and semantics of EDI.

ASC X12.22 - The Data Segment Directory provides the defini-tions and specifications of the segments used in the constructionof transaction sets developed by ASC X12.

The DoD conventions in Section 10.7 conform to the abovestandards and each transaction set is a complete document to theextent possible. For further clarification of acronyms, abbrevia-tions, and codes, refer to ASC X12 published technical documen-tation. Contact the DoD EDI Executive Agent for copies or theData Interchange Standards Association, Inc., Suite 355, 1800Diagonal Road, Alexandria, VA 22314.

10.2 CONTROL SEGMENTSIn addition to the communication control structure, the EDI structureprovides the standards user with multiple levels of control to ensuredata integrity. It does so by using header and trailer control

911115 10.0.1


segments designed to identify uniquely the start and end of theinterchange functional groups and transaction sets. The relation-ship of these control segments is shown in Figure 10.2-1. ControlSegment specifications are defined in Section 10.7.

10.2.1 Description of UseThe interchange header and trailer segments surround one ormore functional groups or interchange-related control segmentsand perform the following functions:

* Define the data element separators and data segment ter-

minators

* Identify the sender and receiver

* Provide control information

" Allow for authorization and security information.

The Interchange Acknowledgment Segment is used to acknowl-edge one interchange header and trailer envelope where theenvelope surrounds one or more functional groups. (No acknowl-edgment -,t. made for the interchange acknowledgment.) The flowof the original interchange and the corresponding acknowledgmentare shown in Figure 10.2-2.

The interchange control number value in the acknowledgment(TAI segment) is the same as that for the ISA segment that isbeing acknowledged. The control number serves as a link be-tween the interchange header and trailer and the acknowledgmentof that header and trailer.

The interchange acknowledgment does not report any status onthe functional groups contained in the interchange and is separatefrom the communication system's error procedures.

The preparer of the interchange header and trailer indicates thelevel of acknowledgment in Data Element 113, AcknowledgmentRequested. If an acknowledgment is requested, then the recipientmust return an acknowledgment. If not requested, none should begiven.

The interchange acknowledgment control segments are placedafter the interchange header and before the first functional groupor before the interchange trailer if there are no functional groups.

10.2.2 Control Segment Specifications

10.2.2.1 Interchange Control Header (ISA)Purpose. To start to identify an interchange of one or morefunctional groups and interchange-related control segments. Theactual values of the data element separator and the segmentterminator for this interchange are set by the interchange controlheader. For a particular interchange, the value at the fourth

10.0.2 911115


Communications Transport ProtocolISA / Interchange Control Header

GS / Functional Group Header

ST /Transaction Set Header

Detail Segments 1(e.g.. Purchase Order)

0SE Transaction Set Trailer UST //Transaction Set Header : _) -

~ C

Detail Segments "(e.g., Purchase Order) C C

SE Transaction Set Trailer _

0 -dGE Functional Group Trailer z

2 EGS Functional Group Header 0

a 0ST / Transaction Set Header 18S Detail egments 0~J(e.g., Receiving Advice) 0

SE Transaction Set Trailer C

GE Functional Group Trailer

lEA Interchange.Control Trailer

Communications Transport Protocol

Figure 10.2-1. Hierarchical Structure

InterchangeControl

and Data

Acknowledgmentfor

This Interchange

Figure 10.2-2. Flow of Original Interchange and Corresponding Acknowledgment

911115 10.0.3

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDEJNES

character position is the data element separator and the value ofthe last character position is the value of the segment terminator.

Record Layout. The record layout is shown in the followingtabulation:

Data Name Length Desc Field EntryInterchange 3/3 A ISAcontrol header

Data element 1/1 AN Agreed uponseparator special character

that separates alldata elements

Authorized infor- 2/2 ID 00

mation qualifier

Authorized 10/10 AN Blank fillinformation

Security 2/2 ID 01informationqualifier

Security 10/10 AN "An agreed uponinformation password"

Interchange ID 2/2 ID ZZ - mutuallyqualifier defined

Interchange sender 15/15 ID DoDAACID

Interchange ID 2/2 ID ZZ - mutuallyqualifier defined

Interchange 15/15 ID 'An agreed uponreceiver ID ID'

Interchange date 6/6 DT YYMMDD

Interchange time 414 TM HHMM

Interchange III ID U - ASC X12control standard

Interchange 5/5 ID 00203control version no.

Interchange 9/9 NO Assigned by sendercontrol no.

Acknowledgment 1/1 ID 0 - norequested 1 W yes

Test indicator 1/1 ID T - test dataP = productiondata

Subelement III AN <separator

Note: Desc = description; A = alphabetic data; AN = al-phabetic and numeric data; ID = identifier; DT = date; TM =time; NO - number; DoDAAC = Department of DefenseActivity Address Code

10.0.4 91111s

DEPARTMENT OF DEFN4SEIMPLEMENTATION GUIDEUNES

10.2.2.2 Functional Group Header (GS)Purpose. To start and identify a group of related transactionsets and provide control and application identifiation information.


Data Name Length Desc Field EntryFunctional Group 2/2 A GSheader

Functional ID 2/2 ID Functional ID codecode

FA - FunctionalacknowledgmentIN - InvoiceinformationPO - PurchaseorderPR - Purchaseorder acknowl-edgmentRA - Paymentorder/remittanceRC - ReceivingadviceRQ - Request forquotationsRR - Response torequest forquotationRT - Report oftest resultsSH - Ship notice/manifeat

Application 2/12 AN DoDAACsender's code

Application 12/12 AN 'An agreed uponreceiver ID"

Group date 6/6 DT YYMMDD

Group time 4/4 TM HHMM

Group control 119 NO Sequential numbernumber assigned by sender

Responsible 1/2 ID X - ASC X12agency code

Version/rel ind. 1/12 ID 002003DoDOID code

10.2.2.3 Transaction SetsTransaction sets of the same type are "functionally grouped"and their formats are described in Section 10.7.

10.2.2.4 Functional Group Trailer (GE)Purpose. To define the end of a functionally related group oftransaction sets.

911116 10.0.6

DEPARTME'T OF DEFISEIMPLEMENTATION OUIDEJNES


Data Name Length DESC Field EntryFunctional group 2/2 A GEtrailer

Number of 1/6 NO Total count ofincluded sets transaction sets in

functional group

Group control 119 NO Same as enterednumber in functional

group header

10.2.2.5 Interchange Control Trailer UlEA)Purpose. To define the end of an interchange of one or morefunctional groups an interchange related control segments.


Data Name Length DESC Field Entryinterchange 313 A lEAcontrol trailer

Number of 1/15 NO Number of GSincluded groups segments

Interchange 9/9 NO Same as enteredcontrol no. in interchange

control header

10.3 LARGE CODE LISTS MAINTAINEDBY ASC X12(to be published)

10.4 CODE LISTS NOT MAINTAINEDBY ASC X12(to be published)

10.5 DATA ELEMENT CROSS-REFERENCEMATRIXThis section contains a data element matrix that cross-referencesDoD specific data elements to the ASC X12 standard elementsand shows usage across multiple transaction sets. This matrixis provided to assist implementors in mapping consistently acrossall transactions. The matrix in Table 10.5-1 is sorted alphabeti-cally. Table 10.5-2 is sorted by transaction set.

10.0.6 911115

DWA1"IT OF DIFOIEPLMdW4TATOIN GUWUMIN

TABLE 10.5-1DoD COMMON NAME CROSS-REFERENCED TO DATA ELEMENT NUMBER

(Alphabetical Order)

For DOD item Description Use Reference Additional qualifiers

in Transaction Set # DE SC and DE # (if Value Equals for Ref DESC)

DoD Item Description TasQ Rf DE # Standard Data Name Value Ref DESCSet DESCI

ABA Number 820 Q BPS10 507 DFI ID 01 - ABA SPS09Acceptance Point - Destination 856 ITA03 560 SpecialI Service Code IM - Inso at Destination ITA03Acceptance Point - Origin 85S6 ITA03 560 1Special Service Code 10 - Insp at Origin ITA03Address Overflow (for Ship to) 850 N102 93 Name ST - Shipto N101Administered by 850 N102 93 Name 01 - Outside Insp Agency N101Advice Code 850 MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01Advice Code 840 MAN02 87 Marks and Numbers L - Line Item Only MAN01Advice Code 850 MAN02 87 Marks and Numbers L - Line item Only MAN01Advice Code 840 1MAN021 87 Marks and Numbers PS - Premarked by Buyer MAN01CAGE & Part Number 840 1REF02 1127 Reference Number MF - Manuf act's Part # REFOICAGE Code of Consionee 850 SCH05 93 Name ST - Shipto SCH04Call Number 863 1PRF02 1328 Release Number ___________

Call/Order Number 861 1PRF02 1328 Release Number ___________

Call/Order Number 810 BIGOS 328 1Release Number ___________

CLIN (Contract Line item 856 LIN01 350 AssignedNumber) Identification________

CLIN 861 LIN01 350 Assigned

Contract Modification Number 856 PRF03 327 Change Order

Contract Number 810 81G04 324 Purchase Order

Contract Number 850 -BEGO3 324* Purchase Order SA - Stand-Alone Order BEGO2

Contract Number 850 BEGO3 324 Purchase Order___________________ Number________

Contract Number 850 BEGO3 324 Purchase Order SS - Supply/Service Ord. BEGO2________________Number

Contract Number 850 BEGO3 324 Purchase Order IN - Information Copy BEGO2____________________ Number ________

Contract Number 850 BEG03 324 Purchase Order RL - Release-Blanket BEGO2_____________________Number Order ____

Contract Number 850 BEGO3 324 Purchase Order SD - BiddingBE2___________________ ~Number ___________

Contract PlIN/SPIIN 820~ REF02 127 Reference Number GC - Govt Contract # REF01Contracting officer Name 850 PER02 93 Name BD - Buyer Name/Deot PER01Contractor Acct * (at Financial 820 BPS1 1 508 Account Numberinstitution) ____________ ______________ _____

Data Segments -Total 820 SE01 96 Number of IncludedSegments

DIC (Data information Code) 850 MAN02 87 Marks and Numbers PBI - Premarked by Buyer MAN0lDIC 850 MAN02 87 Marks and Numbers L - Line Item Only MAN01DIC 840 MAN02 87 Marks ana Numbers L - Line Item Only MANOI-DIC 840 MAN02 87 Marks and Numbers PS - Premarked by Buyer MAN01Distribution Code 840 MANO2 87 Marks and Numbers L - Line Item OnlyMA lDistribution Code 840 MAN02? 87 Marks and Numbers ,PB - Premarked by Buyer MAN01

NoteS ABA . American Banicers Association, CAGE . Commercial anid Government Entity; DFi - Depository Financial institution; OoOAAc . Department of DefenseActivity Address Code; OSSN x Disbursing Station Symbol Number: ELIN - Element Line item Number; FOB a Free on Board. PIN a Procurement instrument identificationNumber, PQA - Place of Quality Assurance; SPuN u supplemental PuN

911115 10.0.7

DEPAWMW4T OF DWMdIPILMINTATI101 GUM11111111

TABLE 10.5-1DoD COMMON NAME CROSS-REFERENCED TO DATA ELEMENT NUMBER (Continued)


For DoD Item Description Use Reference Additional Qualifiersin Transaction Set # DESC and DE # (if Value Equals for Ref DESC)

DoD Item Description TasQ Rf DE # Standard Data Name value Ref DESCSet OESCI

Distribution Code 850 MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01Distribution Code 850 MAN02 87 Marks and Numbers- -L - Line Item Only MAN01DoDAAC of Consignee 850 1SCHOS 93 1Name ST - Ship to SCH04ELIN 856 LIN01 350 Assigned

_____________________I Identification ____________ ____

Except as Noted (in Block 22 of 863 NTE02 3 Free-form MessageDD Form 250) 1________________________

Except as Noted (in Block 22 of 861 NTE02 3 Free-form MessageDD Form 250) ___________________ ____

Existing Contract Number (Use 850 P0101 350 AssignedCLIN) identification ___________

Facility (If Different than 850 N102 93 Name MP - Manufacturing N101Contractor's Address) __________Plant ____

FOB Destination 843 Q F0B01 146 Shipment Method of PP - FOB Destination F0B01____________________________Pay ___________

FOB Origin 843 Q F0801 146 Shipment Method of PC - FOSBOrigin F0801_____________________________Pay____________

FOB Point 850 FO803 352 Description ZZ - Mutually Defined F0802Fund Class Code 850 MAN02 87 Marks and Numbers L - Line Item Only MAN01Fund Class 2ode 840 1MAN02 87 Marks and Numbers L - Line Item Only MAN01Fund Class Code 840 MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01Fund Class Code 850 MAN02 87 Marks and Num bers PB - Premarked by Buyer MAN01Government Contract Number 810 BIG04 324 Purchase Order

Number _________

Issue Date for Purchase Order 850 BEGOS 323 Purchase Order Date(YYMMDD)_____ ___

Issue Priority Designator 85 1 MAN02 87 1Marks and Numbers L. - Line Item Only MAN01Issue Priority Designator 850 1MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01Issue Priority Designator 840 MANO2 87 Marks and Numbers PB - Premarked by Buyer MANOIissue Priority Designator 840 MAN02 87 Marks and Numbers L - Line Item Only MAN01Issued by 850 N102 93 Name BY - Buying Party N101Long-Line Accounting Data 810 REFO2 127 Reference Number __________

Long-Line Accounting Data 850 REF03 352 -Description AT - Appropriation # REF01Long-Line Acct. Data (overflow) 810 REF03 352 Description ___________

Mail to 850 1N102 93 Name ST - Party ToBe Billed N101Manufacturer's Number 840 REF03 352 Description MF - Manufact's Part# REF01Modification Number 810 91G06 327 Change Order

Sequence Number ___________

Modification Number 861 PRF03 327 Change Order__________________________ Sequence Number ___________

Name and Address 850 N102 93 Name SE - Selling Party N101Name/Location of PQA 850 F0803 352 Description DE - Destination F0B02Responsibility & Acceptance _____________

Number of Shipping Containers 856 TD1 02 80 Ladino Quantity ____________

Offer 850 01 DTMO01 374 Date/Time Qualif ier 98 - Bid DTMO1Offered Quantity 843 CTP04 380 Quantity___________Offered Unit of issue 843: CTP05 355 Unit of Measure ___________

Offered Unit Price 843 CTP03 212 Unit Price QTE - Quote Price CTP02Order Number 863 PRF02 28 ees ubr_0_________

Notes AGA - American Banicers Association; CAGE - Commerciai and Government Entity; DFi- Depository Financiai institution; OOAAC . Department of DefenseActivitir Address Code; OSSN a Disbursing Station Symnbol Number: ELIN - Eiement Line Item Numier; FOB - Free on Boa0rd; MIN - Procurement instrument ifentificationNumber; POA a Place of Quaiity Assurance; SPuIN a Supplemental PIN

10.0.3 911115S

OPAIRTMINT OF DW11MdUPLUMUNTATION GUDE34

TABLE 10.5-1DoD COMMON NAME CROSS- REFERENCED TO DATA ELEMENT NUMBER (Continued)


For DOD item Description Use Reference Additional Qualifiersin Transaction Set # DESC and DE # (if Value Equals for Ref DESC)

DOD Item Description TasQ Rf DE # Standard Data Name Value Ref DESCSet DESCI

Orderingq Officer Name. 850 - PER02 93 Name BD - Buyer Name/Dept PER01Originator Number 820 ST02 329 Transaction Set

__________________________ Control #___________Pack Quantity - As Requested 843 1NTE02 3 Free Form Messagie V-tyARequested NTE02Pack Quantity - Different 843 1NTE02 3 Free Form Message N - Qty Different NTE02Payment Will Be Made by 850 1N102 93 Name PR - Payer N101PIIN 863 1PRF06 367 Contract Number ___________ ____

PIIN/SPIIN 820 1REF02 127 Reference Number GC - Govt Contract REF01PQA Location (FOB - 850 F0B03 352 Description DE - Destination F0802Destination) I_____________________ _________________________

PQA Location (FOB = Origin) 850 1FOB03 352 Description OR - Origin F0802PQA Responsibility & Acceptance 850 F0B03 352 Description OR - Origin F0802- Name/Loc__________Price Breaks 810 TDS02 390 Amt Subj to Terms

Discount_____________Price Quote 850_ 02 DTMO 1 374 Date/Time Qualifier 98 - Bid DTMVO 1Processing Cycle Date 820 BPS12 1513 Effective Date __________

Progress Payment Recoupment 820 Q RMT09 426 Adjustment Reason AA - Mutually Defined RMT09ICode___________

Progress Payment Recoupment 820 RMT08 782 Monetary AmountAmount ________ _________

Purchase Order Number 850 BEG03 324 Purchase Order SA - Stand-Alone Order BEGO2Number ___________

Purchase Order Number 850 BEGO3 324 Purchase Order RL - Release-Blanket BEGO2_____________________Number Order ____

Purchase Order Number 850 BEGO3 324 Purchase Order IN - information Copy BEG02___________________ ~Number ___________

Purchase Order Numnber 850 BEGO3 324 Purchase Order BD - Bidding BEG02____________________ ~Number_________ ___

Purchase Order Number 850 BEG03 324 Purchase Order SS - Supply/Service Ord. BEGO2____________________ ~Number_________ ___

Purchase Order Number 850 BEGO3 324 Purchase Order___________________ Number________

Quantity Invoiced Value 810 CTT02 1347 Hash Totals____________Quantity Ordered (sum of value) 850 CTT02 347 Hash Totals ___________

Quotation Line Number 843 P0 101 350 AssignedIdentification ______________

Required Delivery Date 840 DTM02 373 Date 002 - Delivery Requested DTMOI1Required Delivery Date 850 _ MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01Required Delivery Date 850 MAN02 87 Marks and Numbers L - Line Item Only MAN01Required Delivery Date 840 MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01Required Delivery Date 840 MAN02 87 Marks and Numbers L - Line Item Only MANOIRequisition Line Number 840 P0101 350 Assigned

Identification _______________

Requisition Number 850 MAN02 87 Marks and Numbers PB - Premarked by Buyer MANO'Requisition Number 840 tMANO2 87 Marks and Numbers L - Line item Only MANO 1Requisition Number 850 MAN02 87 Marks and Numbers L - Line Item Only MAN01lRequisition Number 840 - AN2 87 Marks and Numbers PB - Premarked by Buyer MANOI

Notes- ABA = American Banicers AssociatiOn. CAGE *Commerciai and Government EntitV. OFi - Depository Financial institution, DoDAAC 2 Department of DefenseACtwtV Address Code, DSSN . Disbursing Station Svmbol Number: ELIN - Element Line item Number; FOB . Free on Board. MIN . Procurement instrument identificationNumber, PDA - Place of Ouality Assurance; SPIIFJ - Supplemental PuIN

91111510.0.9

DWPARIMdBT OF OEWMdUPI.W4TATIOU MND




DOD Item Description TasQ Rf DE # Standard Data Name value Ref DESCSet DESC

Results Acceptable 863 BTRO1 353 Transaction Set 06 - Result Acceptable BTRO1Purpose Code___________

Results Not Acceptable 863 STR0l 353 Transaction Set 12 - Result Not BTRO1________________I____ Purpose Code Acceptable ____

Sending Organization (DSSN) 820 N102 93 Name ZZ - Mutually Defined N101Sequence Number 856 HL01 628 Heirarchical Number ____________ ____

Shipto 850 N102 93 Name ST - Ship to N101Shipment Number 820 REF02 127 Reference Number SI -Shipper's ID# REFOlShipper's Identification Number 861 BRA01 127 Reference Number

Signal Code 840 MAN02 87 1Marks and Numbers L - Line Item Only MAN01SgaCoe850 MAN02 87 1Marks and Numbers POB - Premarked by Buyer MAN01

Signal Code 840 MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01Signal Code 850 MAN02 87 Marks and Numbers L - Line Item Only MAN01________________ 863 PRF02 328 Release Number ____

_______________ 850 BEG04 328 Release Number RL - Release BEGO2________________ 820 REF02 127 Reference Number GC - Govt Contract # REF01Sum of Value of Quantities 850 CTT02 347 Hash TotalsOrdered_________Supplemental Address 840 MAN02 87 Marks and Numbers P8 - Premarked by Buyer MANOl1Supplemental Address 840 MAN02 87 Marks and Numbers L - Line Item Only MAN01Supplemental Address 850 MAN02 87 Marks and Numbers L - Line Item Only MAN01Supplemental Address 850 1MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01Total Data Segments 820 SE01 96 Number of Included

___________________________Segments___________

Total Number of Shipping 856 TD102 80 Lading QuantityContainers _________

Transportation Priority 850 MAN02 87 Marks and Numbers L - Line Item Only MAN01Transportation Priority 840 -MAN02 87 Marks and Numbers L - Line Item Only MAN01-Transportation Priority 840 1MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01Transportation Priority 850 MAN02 87 Marks and Numbers PB - Piremarked by Buyer MAN01Type of Business = Small 850 N102 93 Name 21 - Small Business N101Business__________Type of Business - Small 850 N102 93 Name 27 - Small Disadvantaged N101Disadvantaged__________Type of Business - Woman 850 N102 93 Name 25 - Women Owned, N101Owned - Large Large ____

Type of Business = Woman 850 N102 93 Name 24 - Women Owned, N101lOwned - Small Small_____Unit of Measure(lf Different 810 IT302 355 U nit of Measure Codefrom Shipped/invoiced)__________Value of Quantities Invoiced 810 CTT02 347 Hash Totals ___________

Value of Quantities Ordered 850 CTT02 347 Hash TotalsfSum)- -_________

Volume Discounts 810 -_7 75O2 390 Amt Subj to Termsn Discount

Noraz ABA.= American BaneKers Association; CAGE - Commerciai and Government Entity. OFi - Depository Financiai institution, DAAc - Department of DefenseActivity Address code; DSSN -DOisbursmng Station Symbol Number; ELIN -Eiement Line Item Number. FOS * Free on Board. PION a Procurement instrument identificationNumber; POA a Place of Quaiity Assurance, SPOON z Supplementai PION.

10.0.10 311116

DEPARTMENT OF DIW4IM

IMPLOqdUTATION GUIRilN

TABLE 10.5-2

DoD COMMON NAME CROSS-REFERENCED TO DATA ELEMENT NUMBER(By Transaction Set Order)

For DoD Item Description Use Reference Additional Qualifiersin Transaction Set # DESC and DE # (If Value Equals for Ref DESC)

Trans RefDoD Item Description Q DE # Standard Data Name Value Ref DESCSet DESC

Call/Order Number 810 BIGOS 328 Release Number

Contract Number 810 BIG04 324 Purchase OrderI_ Number

Government Contract Number 810 BIG04 324 Purchase OrderI_ Number

Long-Line Accounting Data 810 REF02 127 Reference NumberLong-Line Acct'g Data (overflow) 810 REF03 352 DescriptionModification Number 810 BIG06 327 Change Order

Sequence NumberPrice Breaks 810 TDS02 390 Amt Subj to Terms

DiscountQuantity Invoiced Value 810 CTT02 347 Hash TotalsUnit of Measure(If Different 810 IT302 355 Unit of Measure Codefrom Shipped/Invoiced)

Value of Quantities Invoiced 810 CTT02 347 Hash TotalsVolume Discounts 810 TDS02 390 Amt Subj to Terms

Discount

ABA Number 820 BPS10 507 DIF ID # 01 - ABA SPS09Contract PIIN/SPIIN 820 REF02 127 Reference Number GC - Govt Contract# REF01Contractor Acct # (at Financial 820 8PS11 508 Account NumberInstitution)Data Segments - Total 820 SE01 96 Number of Included

SegmentsOriginator Number 820 ST02 329 Transaction Set

Control #PIIN/SPIIN 820 REF02 127 Reference Number GC - Govt Contract # REF01Processing Cycle Date 820 BPS12 513 Effective DateProgress Payment Recoupment 820 Q RMT09 426 Adjustment Reason AA - Mutually Defined RMT09

Code

Progress Payment Recoupment 820 RMT08 782 Monetary AmountAmountSending Organization (DSSN) 820 N102 93 Name ZZ - Mutually Defined NI0Shipment Number 820 REF02 127 Reference Number SI - Shipper's ID # REF01SPIIN 820 REF02 127 Reference Number GC - Govt Contract # REF01Total Data Segments 820 SE01 96 Number of Included

Segments

Advice Code 840 MAN02 87 Marksand Numbers PB - Premarked by Buyer MAN0Advice Code 840 MAN02 87 Marks and Numbers L - Line Item Only MAN01CAGE & Part Number 840 REF02 127 Reference Number MF - Manufact's Part# REF01DIC 840 MAN02 87 Marksand Numbers PB - Premarked by Buyer MAN0DIC 840 MAN02 87 Marks and Numbers L - Line Item Only MAN01Distribution Code 840 MAN02 87 Marks and Numbers L - Line Item Only MAN01Distribution Code 840 MAN02 87 Marksand Numbers PB - Premarked by Buyer MAN01Fund ClassCode 840 MAN02 87 Marks and Numbers PB - Premarked by Buyer MA,01Fund Class Code 840 MAN02 87 Marks and Numbers L - Line Item Only MAN31Issue Priority Designator 840 MAN02 87 Marks and Numbers L - Line Item Only MAN01Issue Priority Designator 840 MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01Manufacturer's Number 840 REF03 352 Description MF - Manufact'sPart# REF01Required Delivery Date 840 MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01

Note ELIN - Element Line item Number

911116 10.0.11

DPAINTMT OF DHWWI111111141111TATMO QUNU 11111U


(By Transaction Set Order)

For DoD item Description Use Reference Additional Qualifiersin Transaction Set # DESC and DE # (if Value Equals for Ref DE SC)

000 Item Description TasQ ef DE # Standard Data Name value Ref DESCSet DESCI

Required Delivery Date 840 - DTM02 373 Date 002 - Delivery Requested DTMO IRequired Delivery Date 840 MAN02 87 Marks and Numbers L - Line item only MAN01Requisition Line Number 840 P0101 350 Assigned

____________________________________Identification_______________

Requisition Number 840 1MAN02 87 Marks and Numbers L - Line item Only MANO IRecuisition Number 840 1MAN02 87 Marks and Numbers PS - Premarked by Buyer MAN01Signal Code 840 1MAN02 87 Marks and Numbers L- - Line item Only MAN01ISignal Code 840 1MAN02 87 Marks and Numbers PB - Premarked by Buyer MANO 1Supplemental Address 840 1MAN02 -87 Marks and Numbers PB - Premarked by Buyer MAN01Supplemental Address 840 MAN02 87 Mar ks and Numbers L - Line item Only MANOITransportation Priority 840 MAN02 87 Marks and Numbers L - Line itemn Only MANOITransportation Priority 840 MAN02 87 Marks and Numbers PB - Premarked by Buyer MANO IFOB Destination 843 Q F01301 146 Shipment Method of PP - FOB3 Dest FO0B01

______________________I Pay ____________

FOB Origin 843 Q FOBOI 146 Shipment Method of PC - FOB Origin FOB01______________________________Pa ____________

Offered Quantity 843 CTP04 380 Quantit__________Offered Unit of Issue 843 CTPOS 355 U nit of Measure _________

Offered Unit Price 843 CTP03 212 Unit Price OTE - Quote Price CTP02Pack Quantitv - As Reautsted 843 NTE02 3 Free Form Message V - Oty as Reauested NTE02Pack Ouantity - Different 843 NTE02 -3 Free Form Messa N - Oty Different NTE02Quotation Line Number 843 P0101 350 Assigned

Identification

AddressOverflow (for Shio to) 850O N102 93 Name ST - Ship to IN101Administered By 850 N 102 93 Name 0f1- Outside Insp Aatncv N101Advice Code 850 MAN02 87 Marks and Numbers L. - Line Item Only MANOIAdvice Code 850 MAN02 87 Marks and Numbers PS - Premarked by Buyer MAN01CAGE Code of Consignee 850 SCHOS 93 Name ST - Ship to SCH04Contract Number 850 BEG03 324 Purchase Order SS - Supply/Service Ord. BEGO2

______________________I Number _________

Contract Number 850 BEGO3 324 Purchase Order IN - Information Copy BEGO2________________Number

Contract Number 850 BEGO3 324 Purchase Order SA - Stand-Alone Order BEG02________________Number

Contract Number 8S0 BEGO3 324 Purchase Order BD - Bidding BEGO2___________________ Number________

Contract Number 850 BEG03 324 Purchase Order RI - Release-Blanket BEGO?____________________Number Order

Contract Number 850 BEG03 324 Purchase Order______________________ Number _________

Contracting Officer Name ___0 PER02 93 Name BD - Buyer Namne/Dept PEROIDIC 850 MAN02 87 Marks and Numbers L - Line Item Only MANO'DIC 850 MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN01

Distribution Code 850 MAN02 87 Marks and Numbers PS - Premarked by Buyer MAN01Distribution Code 850 MAN02 87 Marks and Numbers I - Lime item Only MANOI_DoOAAC of Consignee 850 SC1405 93 Name IST - Ship to SCH04Existing Contract Number (Use 850 P0101 350 AssignedCLIN) Identification ___________

Facility (If Diff Than Contractor's 850 N102 93 Name MP - Manufacturing N101Address) _________Plant ____

FOB Point 850 F0B03 352 Description ZZ - Mutually Defined F0802Fujnd ClassCod 850 MAN02 87 Marks and Numbers L - Lin'e item Only MANQI_Fund Class Code 1850 11MAN02 87 Marks and Numbers PB - Premarked by Buyer MAN0'

Noe U ELI.fYmet Line ilem Pdunnfhr

10.0.12 311115

DEPARTMOIT OF DEVII&E1111111LMOTATIONI GUNMEB




DoD Item Description TasQ Ref OE Standard Data Name Value Ref DESCSet DESCIIssue Date for Purchase Order 850 - BEGOS 323 P 0. Date(YYMMDD) _______

!ssue Priority Designator 850 MAN02 87 Marks and Numbers L - Line itern only MAN0".Issue Driority Designator 850 MAN02 87 Marks and Numoers PS - Premarked by Buye' MANOIIssued by 850 N 102 93 Name BY - Buying Party N101LonQ-Line Accounting Data 850 REF03 352 Description AT - Appropriation * REF01Mail to 850 Nb10 93 Name ST - Party ToBe Billed N101Name and Address 850 %4102 93 Name SE - Selling Party N101Name/Location of PQA 850 F0803 352 Description _DE - Destination F0S02Responsibility & Acceptance I__ _________ ___________

Offer 850 Of DTMO1 374 Date/Tirne Qualifier 98 - Bid DTMOIOrdering Officer Name 850 - ER02 93 Name BD - Buyer Name/Dept PER01Payment willI Be Made by 850 _N102 93 Name PR - Payer N101PQA Location (FOB - 850 F0803 352 Description DE - Destination F0OB02Destination)__________POA Location (FOB - Origin) 85 OC503 3S2 Description OR - Origin F0802PQA Responsibility & Acceptance 850 F0803 352 Description OR - Origin F0802- Name/Location I_________ I__________

Price Quote 850 DTMO1 374 Date/Time Oualiie 98 - BidDM0urasOdeNubr850 BEGO3 324 Purchase Order IN - information Copy BEG02

__________________ Number________

Purchase Order Number 850 BEGO3 324 Purchase Order SS - Supply/Service Ord BEG02_______________________ Number _________

Purchase Order Number 850 BEGO3 324 Purchase Order SA - Stand-Alone Order BEG02______________________ Number_________

Purchase Order Number 850 BEG03 324 Purchase Order ED - Bidding BEG02___________________Number

Purchase Order Number 850 BEG03 324 Purchase OrderNumber

Purchase Order Number 850 BEGO3 324 Purchase Order RL - Release-Blanket BEG02Number Order

Quantity Ordered (Sum of Value) 850 CTT02 347 Hash TotalsRequired Delivery Date 850 MAN02 87 Markcsand Numbers PS - Premarced by Buyer MANOIReguired Delivery Date 850 MANO2 87 marks and Number$ L - Line Item Only MAN01Requisition Number 850 MAN02 87 Marks and Numbers L Line item Only MAAN01Requisition Number 850 MAN02 87 Marks and Numbers PS - Premarked by Buyer MANDISh,0to 850 W102 93 Name ST - Ship to N101

Signai Code 850 MAN02 87 Marks and Numbers L - Line Item Only NAAN01S4natCoce 0150 1MANO?1 87 Markcsand Numbers PB - Premarced by Buye' MAANOISPIIN 850 BEGO4 1328 Release Number RL -Release BEGO2Sum of vaiue of Quantities 850 CTT02 347 Hash TotalsOrdered_____________________SuppieeitaAddress 850 MAN02 87 Marks and Numbers Pe - Premarlced by Su Cr AN01SuPPleinenta, Address 850 MAN02 87 1Marksmand Numbers L - Line Item Only NMANOITransoortat on Priority 850 MAN02 87 1Marks and Numbers L - Line item Only MANO ITransportat on Priority 850 1 M %ANO2 87 1Martisanid Numbers PB3 - PromarKed byBuyer NAAN01Type of Business - Small 850 N102 93 Name 21 - Small Business N101Business__________ ____________

Type of Business - Small 850 N102 93 Name 27 - Smnall Disadvantaged N101Disadvantaged_______________________Type of Busines . Woman 850 N102 93 Name 25 - Women Owned. N1011Owned - Large _________Large ____

Type of Business a Woman 80 N102 93 Name 24 - Women Owned, N101Owned - Smal _________ Small_____

hillS10.0.13

DEPARtTMENT OF 05D11111114WMPIL.IEdTATION GUD.INES



For DOD Item Description Use Reference Additional Qualifiersin Transaction Set # DESC and DE # (If Value Equals for Ref DESC)

DoD Item Description TasQ Rf DE # Standard Data Name Value Ref DESCSet DESC

Value of Quantities Ordered 850 - CTT02 347 Hash Totals-(sum)____________

Acceptance Point - Destination 856 1ITA03 1560 Special Service Code im - insp at Destination ITA03Acceptance Point - Origin 856 IITA03 1560 SpecialI Service Code 10 - insp at Origin ITA03CLIN 856 LIN01l 350 Assigned

_______________________I Identification ___________________

Contract Modification Number 856 PRF03 327 Change Order__________________II Sequence Number _______________

ELIN 856 LIN01 350 Assigned_______________________I Identification ___________________

Number of Shipping Containers 856 1TD102 80 Ladino Quantity ___________ ____

Sequence Number 856 HL01 628 Heirarchical Number _______________

Total Number of Shipping 856 TD102 80 Lading QuantityContainers

Call/Order Number 861 PRF02 328 Release NumberCLIN 861 LIN0l 350 Assigned

identification ___________________

Except as Noted (in Block 22 of 861 NTE02 3 Free-Form MessageDD Form 250) __________

Modification Number 861 PRF03 327 Change Order__________________________ Sequence Number _______________

Shipper's identification Number 861 BRA01 127 Reference Number(S ID)_________________

Call Number 863 PRF02 328 Release Number_____Except As Noted (in Block 22 of 863 NTE02 3 Free-Form MessageDO Form 250) _________ __________

Order Number 863 PRF02 -328 Release Number ____

PuIN 863 PRF06 367 Contract Number ___________ ____

Results Acceptable 863 BTRO1 353 Transaction Set 06 - Result Acceptable 8TRO1_________________________ Purpose Code___________ ____

Results Not Acceptable 863 BTRO1 353 Transaction Set 12 - Result Not BTRO1___________________I Purpose Code Acceptable ____

SPIIN 863 1PRF02 1328 1Release Number ____________ ____

11110f ELiN E e~ent line tenm Number

10.0.14 311115


IMPLEMENTATION GUIDEJNES

10.6 DATA SEGMENT CROSS-REFERENCEMATRIXThe data segment matrix in this section cross-references specificsegments across the various ASC X12 standards (see Table 10.6-1).This matrix should assist implementors in consistently mappingusage in all transactions.

10.7 DoD/INDUSTRY CONVENTIONS

911115 10.0.15

DEPARTMENT OF DB:MSEIMP.IEMENTATION GUIDu.I[

TABLE 10.6-1

DATA SEGMENT CROSS-REFERENCE MATRIX

Segment Segment name 810 820 840 843 350 855 856 861 863 997ID

AK1 Functional Group Response Header XAK2 Transaction Set Response Header XAK3 Data Segment Note XAK4 Data Element Note XAKS Transaction Set Response XAK9 Functional Group Response Trailer XAMT Monetary Amount XBAK Beginning Seg for Purchase Order Ack xBEG Beginning Seg for Purchase Order XBIG Beginning Seg for Invoice XBPS Beginning Seg - Pint Order/Remit Advice XBQR Beginning Seg - Response to RFQ XBQT Beginning Seg for RFQ XBRA Beginning Seg for Receiving Advice XBSN Beginning Seg for Ship Notice xBTR Beginning Seg for Test Results XCID Characteristics/Class ID XCTP Pricing Information XCTT Transaction Totals X X X X X X XCUR Currency X XDTM Date/Time Reference X X X X X X X XFOB FOB Related Instructions X X X X XHL Hierarchical Level XITI Baseline Item Data (Invoice) XIT3 Additional Item Data XITA Allowance. Charge or Service X XITD Terms/Deferred Terms of Sale X XLE Loop Trailer XLIN Item Identification Detail X X XLS Loop Header XMAN Marks and Numbers X X XMEA Measurements X XN1 Name X X X X X X X XN2 Additional Name Information X X X X X X xN3 Address Information X X X X X X XN4 Geographic Location X X X X X xNTE Note/Special Instructions X X X X X X XPER Admin Communications Contact X X X X X X XPID Product/Item Description x X XPKG Marking, Packaging, Loading X XPO1 Purchase Order Baseline Item Data X X XP03 Additional Item Detail XP04 Item Physical Details XPRF Purchase Order Reference x XPWK Paperwork X

10.0.16 011115

DEPARTMENT OF 0:dSE

IMPLEMENTATION OUDUES

TABLE 10.6-1

DATA SEGMENT CROSS-REFERENCE MATRIX (Continued)

SegmentSD Segment name 810 820 840 843 850 855 856 861 863 997ID

RCD Receiving Conditions XREF Reference Numbers X X X X X X X XRMT Remittance Advice XSCH Line Item Schedule XSDQ Destination Quantity XSE Transaction Set Trailer X X X X X X X X XSNi Item Detail (Shipment) X XST Transaction Set Header X X X X X X X X X XTAX Sales Tax Reference XTol Carrier Details (Quantity and Weight) XTD3 Carrier Details (Equipment) XTD4 Carrier Details (Spec Handling/Haz Mat'l) XTD5 Carrier Details (Route Seq/Transit Time) XTDS Total Monetary Value Summary XUIT Unit Detail X

3i11111 10.0.17


10.0.18 911115


10.7.10 DoD Convention for Using the 810 InvoiceThis section provides the format and establishes the data contentsof the DoD 810 Transaction Set Convention. The invoice trans-action set provides for customary and established business andindustry practice relative to the billing for goods and servicesprovided.

10.7.10.1 IntroductionSee Section 10.1

10.7.10.2 Control SegmentsSee Section 10.2

10.7.10.3 Large Code Lists Maintained By ASC X12See Section 10.3

10.7.10.4 Code Lists Not Maintained By ASC X12See Section 10.4

10.7.10.5 Data Element Cross-Reference MatrixSee Section 10.5

10.7.10.6 Data Segment Cross-Reference MatrixSee Section 10.6

10.7.10.7 810.002003DoDO Convention

911115 810.002003.DoDO - Cover


S IO.002003.DODO - Coww 911115


ASC X12.2 Transaction Set 810Invoice (Version 002003)

Segment Hierarchy

Table 1 - Header Area

Seag ReqIndustry ID Name Des Use Loop

USE ST Transaction Set Header M 1

USE BIG Beginning Segment for Invoice M 1

USE NTE Note/Special Instruction F 100

USE CUR Currency 0 1

USE REF Reference Numbers 0 12

USE PER Administrative Communications Contact 0 3

USE N1 Name 0 1 N1\200

USE N2 Additional Name Information 0 2

USE N3 Address Information 0 2

USE N4 Geographic Location 0 1



USE lTD Terms of Sale/Deferred Terms of Sale 0 5

USE DTM Date/Time Reference 0 10

USE FOB F.O.B. Related Instructions 0 1

PID Product/Item Description 0 200

MEA Measurements 0 40

PWK Paperwork 0 25

PKG Marking, Packaging, Loading 0 25

Table 2 - Detail Area

Seg ReqID Name Des Use Loop

USE ITI Baseline Item Data (Invoice) 0 1 IT1\200000

CUR Currency 0 1USE IT3 Additional Item Data 0 5

TXI Tax Information 0 10

CTP Pricing Information 0 25

USE PID Product/Item Description 0 1000

USE MEA Measurements 0 40

PWK Paperwork 0 25


911223 810.002003.DoDO - 1

DEPARTMENT OF DBSEIMPLEMENTATION GUIDELINES

1T4 Item Physical Details 0 1

ITA Allowancc, Charge or Service 0 1 ITA\10


171D Terms of Sale/Deferred Terms of Sale 0 2

REF Reference Numbers 0 12

PER Administrative Communications Contact 0 5

N1 Name 0 1 N1\200

N2 Additional Name Information 0 2

N3 Address Information 0 2N4 Geographic Location 0 1



SDC Destination Quantity 0 500

DTM Date/Time Reference 0 10

CAD Carrier Detail 0 1

Table 3 - Summary Area


TD8 Total Monetary Value Summary M 1


CAD Carrier Detail 0 1

188 Invoice Shipment Summary 0 5

USE CTT Transaction Totals M 1USE SE Transaction Set Trailer M 1

81O.002003.DoDO - 2 911223


DoD Model Transaction 810Invoice

Segment Hierarchy


Sag ReqPage No. ID Name Des Use Loop

5 ST Transaction Set Header M 1

6 BIG Beginning Segment for Invoice M 1

8 NTE Note/Special Instruction F 100

9 CUR Currency 0 1

13 REF Reference Numbers 0 12

15 PER Administrative Communications Contact 0 3

17 N1 Name 0 1 N1\200

19 N2 Additional Name Information 0 2

20 N3 Address Information 0 2

21 N4 Geographic Location 0 1



26 ITD Terms of Sale/Deferred Terms of Sale 0 5

28 DTM Date/Time Reference 0 10

29 FOB F.O.B. Related Instructions 0 1



31 IT1 Baseline Item Data (Invoice) 0 1 IT1\200000

35 IT3 Additional Item Data 0 5

36 PID Productlltem Description 0 1000

38 MEA Measurements 0 40


Sag ReqID Name Des Use Loop

40 TDS Total Monetary Value Summary M 1

41 CTT Transaction Totals M 1

42 SE Transaction Set Trailer M 1

911223 810.002003.DoDO - 3


810.00200300.DoDO - 4 911223

DEPARTMENT OF D=I ISEIMPLEMENTATION GUIDELNES

Segment: ST Transaction Set Header

Table: A

Sequence: 2Usage: M

Max Use: 1Loop: 0

Purpose: To indicate the start of a transaction set andto assign a control number

Comment: A. The transaction set identifier (ST01) isintended for use by the translationroutines of the interchange partners toselect the appropriate transaction setdefinition (e.g., 810 selects the invoicetransaction set).

Data Element SummaryRef. DataDes. Eement Name Attributes

ST01 143 Transaction Set Identifier Code M ID 3/3Code uniquely identifying a Transaction Set.

Transaction Set ID Code[001 A *1 Code Definition

810 Invoice

ST02 329 Transaction Set Control Number M AN 4/9Identifying control number assigned by the originatorfor a Transaction Set. Also see: Data InterchangeControl Number (28.)

Transaction Set ControlNumber

[002 A

911218 810.002003.DoDO - 5


Segment: BIG Beginning Segment for InvoiceTable: A

Sequence: 3Usage: M

Max Use: 1Loop: 0

Purpose: To indicate the beginning of an invoicetransaction set and to transmit identifyingnumbers and dates.

Comment: A. BIG07 is used only to further define thetype of invoice when needed.

Data Element Summary

Ref. DataDes. Element Name Attributes

BIG01 245 Invoice Date M DT 6/6Invoice Issue Date.

Invoice Date[003 A I

BIG02 76 Invoice Number M AN 1/22Identifying number assigned by issuer.

Invoice Number[004 A I

BIG03 323 Purchase Order Date 0 DT 6/6

Required BIG04 324 Purchase Order Number 0 AN 1/22Identifying number for Purchase Order assigned bythe orderer/purchaser.

Purchase Order Number[005 A ] <

This element carries the Govern-ment contract number. Contrac-

tors when dealing with theirvendors will use code 'CT' with

the 'REF' segment.BIG05 328 Release Number 0 AN 1/30

Number identifying a release against a PurchaseOrder previously placed by the parties involved inthe transaction.

Release Number[006 A I

This element carries the celllordernumber.

810.002003.DoDO - 6 911218

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDEUES

BIG06 327 Change Order Sequence Number 0 AN 1/8Number assigned by the orderer identifying aspecific change or revision to a previously trans-mitted transaction set.

Change Order SequenceNumber

[007 A I

This element carries the modifica-tion number.

BIG07 640 Transaction Type Code 0 ID 2/2Code specifying the type of transaction.

Transaction Type Code[008 A ° Code Definition

CI Consolidated InvoiceCo CorrectedCR Credit MemoD03 Standard Invoice*DO1 Progress Bill'D02 Cost Voucher*DR Debit MemoDU DuplicateFB Final BillMC Material Credit InvoicePB Partial BillPR Product (or Service)RE Rebill

911218 eo.002003.DoDo - 7

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDELNES

Segment: NTE Note/Special Instruction

Table: A

Sequence: 4

Usage: F

Max Use: 100Loop: 0

Purpose: To transmit information in a free-form for-mat, if necessary, for comment or special in-struction

Comment: A. The NTE segment permits free-form in-formation/data which, under ANSI X12standard implementations, is not machineprocessable. The use of the "NTE"segment should therefore be avoided, ifat all possible, in an automated environ-ment.

Data Element SummaryRef. DataDos. Element Name Attributes

NTEO1 363 Note Reference Code 0 ID 3/3Code identifying the functional area or purpose forwhich the note applies. Also see: Free Form Mes-sage (3).

Note Reference Code[009 A °] Code Definition

INV Invoice Instruction

NTE02 3 Free Form Message M AN 1/60Free-form text.

Free-Form Message[010A

810.002003.DoDO - 8 911210


Segment: CUR CurrencyTable: A

Sequence: 5Usage: 0

Max Use: 1Loop: 0

Purpose: To specify the currency (dollars, pounds,francs, etc.) used in a transaction

Comment: A. See X12 dictionary.

Syntax Notes: 01 If CUR08 is present, then CUR07 is re-quired.

02 If CUR09 is present, then CUR07 is re-quired.

03 If CURl is present, then CURIO is re-quired.





08 If CURl8 is present, then CUR16 is re-quired.





CUR01 98 Entity Identifier Code M ID 212Code identifying an organizational entity or a physi-cal location.

911218 810.002003.Do)0 - 9


Entity Identification Code[011 A *] Code Definition

PE Payee

PR Payer

CUR02 100 Currency Code M ID 3/3Code (Standard ISO) for country in whose currencythe charges are specified.

Currency Code[012 A I

CUR03 280 Exchange Rate 0 R 4/6Value to be used as a multiplier conversion factor toconvert monetary value from one currency toanother.

Exchange Rate[013A

CUR04 98 Entity Identifier Code 0 ID 2/2Code identifying an organizational entity or a physi-cal location.

Entity Identification Code[014 A ] Code Definition

PE Payee

PR Payer

CUR05 100 Currency Code 0 ID 3/3Code (Standard ISO) for country in whose currencythe charges are specified.

Currency Code[015 A ° Code Definition

PE PayeePR Payer

CUR06 669 Currency Market/Exchange Code 0 ID 3/3Code identifying the market upon which the curren-cy exchange rate is based.

Currency/Market ExchangeCode

[016A

Not used by DoD.

CUR07 374 Date/Time Qualifier C ID 3/3Code specifying type of date or time, or both dateand time.

810.002003.DoDO - 10 911218


Date/Time Qualifier[017 A *] Code Definition

007 Effective

CURO 373 Date 0 DT 6/6Date (YYMMDD).

Date[018A

CUR09 337 Time 0 TM 4/4

CURIO 374 Date/Time Qualifier C ID 3/3Code specifying type of date or time, or both dateand time.

Date/Time Qualifier[019 A °] Code Definition

036 Expiration

CURl1 373 Date 0 DT 616

Date (YYMMDD).Date

[020 A I

CUR12 337 Time 0 TM 4/4

CUR13 374 Date/Time Qualifier C ID 3/3

CUR14 373 Date 0 DT 6/6

CUR15 337 Time 0 TM 4/4


CUR17 373 Date 0 DT 6/6

CUR18 337 Time 0 TM 4/4


CUR20 373 Date 0 DT 6/6

911218 810.002003.DoDO - 11

DEPARTMENT OF DEFMEIMPLEMENTATION QUIDELNES

CUR21 337 Time 0 TM 4/4

810.002003.DoDO - 12 911218


Segment: REF Reference NumbersTable: A

Sequence: 6Usage: 0

Max Use: 12Loop: 0

Purpose: To transmit identifying numbers

Syntax Notes: 01 At least one of REF02 or REF03 mustbe present.

Data Element SummaryRef. DataDes. Element Name Attributes

REF01 128 Reference Number Qualifier M ID 2/2Code qualifying the Reference Number.

Reference Number Qualifier[021 A *]

A. The "shipment chargeable'code applies to Navy Appropria-tion 17X4911. B. Applies when

codes '2T' or "7T' are includedin Appropriation Data. C. Addition-

al codes which are authorizedwhen contained trading partner

agreements are CO, DC, EQ, GC,IA, MS. RX, SE, WS, AM, CT, JB,

01, and RS. Code DefinitionBL Government Bill of Lading NumberBM Bill of Lading NumberCJ Clause NumberD01 Shipment Chargeable to Navy Appropriation*D02 Navy Transaction Type Code (TC)"D03 Long-line Accounting Data*Sl Shipper's Identifying Number for ShipmentTG TG Transportation Control Number (TCN)

REF02 127 Reference Number C AN 1/30Reference number or identification number asdefined for a particular Transaction Set, or asspecified by the Reference Number Qualifier. Alsosee Reference Number Qualifier, (128).

Reference Number[022 A I

REF03 352 Description C AN 1/80A free-form description to clarify the related data ele-ments and their content.

911218 810.002003.DoDO - 13

DEPARTMENT OF DEFESEIMPLEMENTATION GUIDELINES

Description[023 AI

The long-line accounting data willnormnally be carried in REFO2. In

those cases where the data ex-ceed 30 characters in length, use

RtEF03 to carry all of the data.

81O.002003.DoDO - 14 911218

DEPARTMENT OF DEFENSEIMPLEMENTATION OUIDWJNES

Segment: PER Administrative CommunicationsContact

Table: ASequence: 7

Usage: 0

Max Use: 3Loop: 0

Purpose: To identify a person or office to whom ad-ministrative communications should bedirected

Comment: A. This segment is used to specify who isto be contacted on various conditions re-lated to the transaction. The term "Com-munication" in the title and purposerelates to interpersonal communications,not network or telecommunications con-tacts.

Syntax Notes: 01 If PER03 is present, then PER04 is re-quired.


PER01 366 Contact Function Code M ID 2/2Code identifying the major duty or responsibility ofthe person or group named.

Contact Function Code[024 A *1

Additional codes authorized foruse when contained trading

partner agreements are AR, AP,90, and OC. Code Definition

IC Information Contact

PER02 93 Name 0 AN 1/35Free form name.

Name[025 A I

PER03 365 Communication Number Oualifier 0 ID 2/2Code identifying the type of communication number.

911218 810.002003.DoOO - 15

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDBJNES

Communication NumberQualifier

[026 A *] Code DefinitionDOI AU*D02 Defense Data Network (DDN)"EM Electronic MailFX FacsinileIT International Telephone

PS Packet SwitchingTE TelephoneTL TelexTM TelemailTX TWX

PER04 364 Communication Number C AN 7/21Complete communications number including countryor area code when applicable. Also see: Com-munications Number Qualifier (365).

Communication Number[027 A I

PER05 326 Request Reference Number 0 AN 1/45

810.002003.DoDO - 16 911218


Segment: N1 NameTable: A

Sequence: 8Usage: 0

Max Use: 1Loop: 0

Purpose: To identify a party by type of organization,name and code

Comment: A. This segment, used alone, provides themost efficient method of providing or-ganizational identification. To obtainthis efficiency the "ID Code" (N104)must provide a key to the table main-tained by the transaction processingparty.

Syntax Notes: 01 At least one of N102 or N103 must bepresent.

02 If either N103 or N104 is present, thenthe other is required.



N101 98 Entity Identifier Code M ID 2/2Code identifying an organizational entity or a physi-cal location.

Entity ID Code[028 A *1 Code Definition

DO1 31 Administered By'FR Message FromPE Payee

PR Payer

RI Remit ToST Ship FromTO Message To

N102 93 Name C AN 1/35Free form name.

Name[029 A I

N103 66 Identification Code Qualifier C ID 1/2Code designating the system/method of code struc-ture used for Identification Code (67).

911218 810.002003.DoDO - 17

DEPARTMENT OF DEFENSEIMPLEMENTATION alUDEUNES

ID Code Qualifier(030 A I

When N101 is code 31. TO. orRM. use code 10. When N101 is

code FR. PG. or SF, use code M2.

N104 67 Identification Code C ID 2/17Code identifying a party.

ID Code[031 A I

S1O.002003.DoDO - 18 911218


Segment: N2 Additional Name Information

Table: A

Sequence: 9

Usage: 0

Max Use: 2

Loop: 0

Purpose: To specify additional names or those longerthan 35 characters in length


N201 93 Name M AN 1/35Free form name.

Name[032 A I

N202 93 Name 0 AN 1/35

Free form name.Name

[033 A I

911218 810.002003.DoDO - 19

DEPARTMENT OF DWENSEIMPLEMENTATION GUIDELINES

Segment: N3 Address InformationTable: A

Sequence: 10Usage: 0

Max Use: 2Loop: 0

Purpose: To specify the location of the named party


N301 166 Address Information M AN 1/35Free-form field for address information.

Address[034 A I

N302 166 Address Information 0 AN 1/35Free-form field for address information.

Address[035 A I

810.002003.DoO0 - 20 911218


Segment: N4 Geographic LocationTable: A


Max Use: 1Loop: 0

Purpose: To specify the geographic place of thenamed party

Comment: A. A combination of either N401 throughN404 (or N405 and N406) may be ade-quate to specify a location.

B. N402 is required only if city name(N401) is in the USA or Canada.


02 If N401 is present, then N402 is re-quired.


Data Element SummaryRef. DataDes. Bement Name Attribute

N401 19 City Name C AN 2119Free-form text for city name.

City Name[036 A I

N402 156 State or Province Code C ID " 2/2Code (Standard State/Province) defined by ap-propriate governmental agencies.

State/Province Code[037 A I

N403 116 Postal Code 0 ID 5/9Code defining international postal zone code exclud-ing punctuation and blanks (zip code for UnitedStates).

Postal Code(038 A I

N404 26 Country Code 0 ID 2/2Code identifying the country.

911218 810.002003.DoO0 - 21


Country Code[039 A I

A translation table will be requiredto convert those standard codesused by ANSI to those used by

DoD, N405 309 Location Qualifier 0 ID 1/2

Code identifying type of Location Identifier (310)used.

Location Qualifier(040 A I

N406 310 Location Identifier C AN 1/25Code which identifies a specific geographic location.

Location Identifier[041 A I

810.002003.DoDO - 22 911218

DEPARTMENT OF DEFEISEIMPLEMENTATION GUIDEINES



Max Use: 12Loop: 0

Purpose: To transmit identifying numbersSyntax Notes: 01 At least one of REF02 or REF03 must

be present.

Data Element SummaryRef. DataDe. Element Name Attributes


Reference Number Qualifier[042 A *]



REF03 352 Description C AN 1/80

911218 810.002003.DoO0 - 23

DEPARTMENT OF DEFEiSEIMPLEMENTATION GUIDB.INES


Table: ASequence: 13

Usage: 0Max Use: 3

Loop: 0




Data Element SummaryRef. DataDee. Eement Name Attributes

PER01 366 Contact Function Code M ID 212Code identifying the major duty or responsibility ofthe person or group named.

Contact Function Code1044 A *]

Additional codes authorized foruse when contained in trading

partner agreements are AR, AP,BD. and OC. Code Definition



Name1045 A I

PER03 365 Communication Number Qualifier 0 ID 2/2Code identifying the type of communication number.

810.002003.DoDO - 24 911218

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDE.INES


[046 A "] Code Definition

DOI AU*D02 Defense Data Network (DDN)

PER04 364 Communication Number C AN 7121

Complete communications number including countryor area code when applicable. Also see: Com-munications Number Qualifier (365).



911218 810.002003.DoO0 - 25


Segment: lTD Terms of Sale/Deferred Termsof Sale


Usage: 0Max Use: 5

Loop: 0

Purpose: To specify terms of sale.

Comment: A. If ITD01 equals 04 - ITD10 is requiredand either ITD11 or ITD12 is required.If ITD01 equals 05 - ITD06 or ITDO7 isrequired. If 1TD01 does not equal 04 or05 - ITD03 or ITD08 is required.

Syntax Notes: 01 If ITDO3 is present, then at least one ofITD04, ITD05, ITDI3 is required.

02 If ITDO8 is present, then at least one ofITDO4, or ITDO5 is required.

03 If ITDO9 is present, then ITD10 is re-quired.

Data Element SummaryRef. DataDes. Bement Name Attributes

ITD01 336 Terms Type Code 0 ID 2/2Code identifying type of payment terms.

Terms Type Code[048 A I

ITDO2 333 Terms Basis Date Code M ID 112Code identifying the beginning of the terms period.

Terms Basis Date Code[049 A I

Any applicable code can be used.

ITDO3 338 Terms Discount Percent C R 1/6Terms discount percentage, expressed as a percent,available to the purchaser if an invoice is paid on orbefore the Terms Discount Due Date.

Terms Discount Percent[050 A I

ITDO4 370 Terms Discount Due Date C DT 6/6Date payment is due if discount is to be earned.

810.002003.DoDO - 26 911218

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDJ.NES

Terms Discount Due Date[051 A I

ITDO5 351 Terms Discount Days Due C NO 1/3Number of days in the terms discount period bywhich payment is due if terms discount is earned.

Terms Discount Days Due[052 A I

ITDO6 446 Terms Net Due Date C DT 6/6

ITDO7 386 Terms Net Days C NO 1/3Number of days until total invoice amount is due(discount not applicable).

Terms Net Days[053 A I

ITDO8 362 Terms Discount Amount C N2 1/10Total amount of terms discount.

Terms Discount Amount[054 A I

Used so that rounding-offmethodology will not be a factor.

ITDO9 388 Terms Deferred Due Date 0 DT 6/6

ITD10 389 Deferred Amount Due C N2 1/10

ITD1 1 342 Percent of Invoice Payable C R 1/5

ITD12 352 Description C AN 1/80

ITD13 765 Day of Month C NO 1/2

The numeric value of the day of the month between1 and the maximum day of the month being refer-enced.

Day of Month[055 A I

911218 810.002003.DoDO - 27


Segment: DTM Date/Time ReferenceTable: A

Sequence: 15

Usage: 0Max Use: 10

Loop: 0

Purpose: To specify pertinent dates and timesSyntax Notes: 01 At least one of DTM02 or DTM03 must

be present.

Data Element SummaryRef. DataDee. Element Name Attributes

DTM01 374 Date/Time Qualifier M ID 3/3Code specifying type of date or time, or both dateand time.

Date/Time Qualifier[056 A *1

Transaction creation date will becarried in the "GS" segment of

the envelope. Code Definition007 Effective Date011 Shipped

DTM02 373 Date C DT 6/6Date (YYMMDD).

Date[057 A I

DTM03 337 Time C TM 4/4

DTM04 623 Time Zone Qualifier 0 ID 2/2

810.002003.DoDO - 28 911218


Segment: FOB F.O.B. Related InstructionsTable: A


Max Use: 1Loop: 0

Purpose: To specify transportation instructions relat-ing to shipment

Comment: A. FOBOI indicates which party will paythe carrier.

B. FOB02 is the code specifying transporta-tion responsibility location.

C. FOB06 is the code specifying title pas-sage location.

Syntax Notes: 01 If FOB03 is present, then FOB02 is re-quired.

02 If FOB04 is present, then FOB05 is re-quired.



FOB01 146 Shipment Method of Payment M ID 2/2Code identifying payment terms for transportationcharges.

Shipment Method ofPayment

1058 A *] Code DefinitionDOI Paid by Seiler*D02 Paid by Buyer*

FOB02 309 Location Qualifier C ID 1/2Code identifying type of Location Identifier (310)used.

Location Qualifier[059 A "] Code Definition

DE Destination

OR Origin

911218 810.002003.DoDO - 29

DEPARTMENT OF DWBESEIMPLEMENTATION GUIDBNES

FOB03 352 Description 0 AN 1/80

FOB04 334 Transportation Terms Qualifier 0 ID 2/2Code

FOB05 335 Transportation Terms Code C ID 3/6

FOB06 309 Location Qualifier C ID 1/2


e10.002003.DoDO - 30 911218

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDEINES

Segment: IT1 Baseline Item Data (Invoice)

Table: B

Sequence: 22

Usage: 0Max Use: 1

Loop: 0

Purpose: To specify the basic and most frequentlyused line item data for the invoice and re-lated transactions.

Comment: A. Element 235/234 combinations should beinterpreted to include products and/orservices. See the Data Dictionary for acomplete list of IDs.

B. IT101 is the purchase order line itemidentification.

C. IT106 through IT125 provides for ten(10) different product/service IDs foreach item. For example: Case, Color,Drawing No., UPC No., ISBN No.,Model No., SKU.

Syntax Notes: 01 If 1T106 is present, then I107 is re-quired.

02 If 1708 is present, then 1 109 is re-quired.

03 If 17110 is present, then IT111 is re-quired.

04 If fI12 is present, then IT113 is re-quired.

05 If IT114 is present, then IT115 is re-quired.

06 If ITI16 is present, then ff117 is re-quired.

07 If f1lI8 is present, then IT119 is re-quired.

08 If ff120 is present, then f121 is re-quired.

09 If ff122 is present, then IT123 is re-quired.

911218 810.002003.DoDO - 31


10 If IT124 is present, then IT125 is re-quired.


IT101 350 Assigned Identification 0 AN 1/6Alphanumeric number assigned for differentiationwithin a transaction set.

Assigned Identification[060 B I

IT102 358 Quantity Invoiced M R 1/10Number of units invoiced (supplier units).

Quantity Invoiced[061 B I

IT103 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit measurement.

Unit of Measure Code[062 B I

DoD uses DoD Manual 5000.12-M. IT301/302 can be used for an

alternative unit of measure.

IT104 212 Unit Price M R 1/14Price per unit of product, service, commodity, etc.

Unit Price[063 B I

The extended amount of each lineitem and the total amount of thecontract are to be calculated by

application program.

IT105 639 Basis of Unit Price Code 0 ID 2/2Code identifying the type of unit price for an item.

Basis Unit Price Code1064 B I

IT106 235 Product/Service ID Qualifier 0 ID 2/2Code identifying the type/source of the descriptivenumber used in Product/Service ID (234).

Product/Service ID Qualifier[065 B *] Code Definition

CN Commodity NameFS Federal Stock Classification and/or NSNPN Company Part Number

IT107 234 Product/Service ID C AN 1/30

810.002003.D.DO - 32 911218


IT108 235 Product/Service ID Qualifier 0 ID 2/2Code identifying the type/source of the descriptivenumber used in Product/Service ID (234).

Product/Service ID Qualifier[066 B I

IT109 234 Product/Service ID C AN 1/30Identifying number for a product or service.

Product/Service ID[067 B I

Data elements IT1 10 throughIT1 25 will be used as necessary.

ITI 10 235 Product/Service ID Qualifier 0 ID 2/2

ITI 11 234 Product/Service ID C AN 1/30

IT1 12 235 Product/Service ID Qualifier 0 ID 2/2

ITi 13 234 Product/Service ID C AN 1130

IT1 14 235 Product/Service ID Qualifier 0 ID 2/2

IT1 15 234 Product/Service ID C AN 1/30

ITI 16 235 ProductlService ID Qualifier 0 ID 2/2


IT118 235 Product/Service ID Qualifier 0 ID 212


IT120 235 Product/Service ID Qualifier 0 ID 2/2



911218 a10.002003.DoDO - 33

DEPARTMENT OF DBEENSE




IT125 234 Product/Service ID C AN 1130

810.002003.DoDO - 34 911218

DEPARTMENT OF DEFBISEIMPLEMENTATION GUIDEWNES

Segment: IT3 Additional Item DataTable: B


Max Use: 5Loop: 0

Purpose: To specify additional item details relating tovariations between ordered and shippedquantities, or to specify alternate units ofmeasures and ... (See X12 Dictionary.)

Syntax Notes: 01 If IT301 is present, then IT302 is re-quired.

02 At least one of IT301, 1T303, IT304, or1T305 must be present.


IT301 382 Number of Units Shipped C R 1/10Numeric value of units shipped in manufacturer'sshipping units for a line item or transaction set.Also see: Unit of Measurement Code (355).

Number of Units Shipped[068 B I

IT302 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit measurement.


Use when contract unit ofmeasure differs from shipped or in-

voiced unit of measure.IT303 368 Shipment/Order Status Code C ID 2/2

IT304 383 Quantity Difference C R 1/9

IT305 371 Change Reason Code C ID 2/2

911218 810.002003.DoDO - 35


Segment: PID Product/Item Description

Table: BSequence: 28

Usage: 0Max Use: 1000

Loop: 0

Purpose: To describe a product in coded or free-formformat

Comment: A. Use PID03 to indicate the organizationthat publishes the code list beingreferred to.

B. PID04 should be used for industry-specific product description codes.

C. Use PID06 when necessary to refer tothe product surface or layer beingdescribed in the segment.

Syntax Notes: 01 If PID03 is present, then PID04 is re-quired.

02 At least one of PID04 or PID05 must bepresent.

Data Element SummaryRef. DataDo. Element Name Attributes

PID01 349 Item Description Type M ID 1/1Code indicating the format of a description.

Item Description Type[070 B I

PID02 750 Product Characteristic Code 0 ID 2/3Code specifying the product characteristic beingdescribed.

Produce/ProcessCharacteristic Code

[071 B I

PID03 348 Item Description Qualifier 0 ID 2/2Code identifying agency responsible for the codeused.

Item Description Qualifier[072 B I

PID04 751 Product Description Code C ID 1/12

810.002003.DoDO - 36 911218


A code from an industry code list which providesspecific data about a product characteristic. Alsosee: Item Description Qualifier (348).

Product Description Code[073 B I

PID05 352 Description C AN 1/80A free-form description to clarify the related data ele-ments and their content.

Description[074 B I

PID06 752 Surface/LayerlPosition Code 0 ID 2/2

911218 810.002003.DoDo - 37

DEPARTMENT OF DEFISEIMPLEMENTATION GUIDELINES

Segment: MEA Measurements

Table: B


Max Use: 40Loop: 0

Purpose: To specify physical measurements, includingdimensions, tolerances, weights and counts.

Comment: A. When citing dimensional tolerances, anymeasurement requiring a sign (+ or -),or any measurement where a positive(+) value cannot be assumed use MEA05 as the negative (-) value and MEA06as the positive (+) value.

Syntax Notes: 01 If MEA07 is used MEA03 is required.

02 Either MEA08 or MEA03 may be used,but not both.

03 Either MEA03 or MEA05 or MEA06 orMEA08 is required.

04 If either MEA03, MEA05 or MEA06 isused, MEA04 is required.


MEA01 737 Measurement Reference ID Code 0 ID 2/2Code specifying the application of physical measure-ment cited.

Measurement Reference IDCode

[075 B I

MEA02 738 Measurement Qualifier 0 ID 1/3Code identifying the type of measurement.

Measurement Qualifier[076 B I

MEA03 739 Measurement Value C R 1/10The value of the measurement.

Measurement Value[077 B I

810.002003.DoDo - 38 911218


MEA04 355 Unit of Measurement Code C ID 2/2

Code identifying the basic unit measurement.Unit of Measure Code

[078 B I

MEA05 740 Range Minimum C R 1/10The value specifying the minimum of the measure-ment range.

Range Minimum1079 B I

Use for variation in quantity.

MEA06 741 Range Maximum C R 1/10The value specifying the maximum of the measure-ment range.

Range Maximum[080 B I

Use for variation in quantity.

MEA07 935 Measurement Significance Code 0 ID 2/2

MEA08 936 Measurement Attribute Code C ID 2/2

MEA09 752 Surface/Layer/Position Code 0 ID 2/2

911218 810.002003.DoO0 - 39


Segment: TDS Total Monetary Value Summary

Table: C

Sequence: 50Usage: M

Max Use: 1Loop: 0

Purpose: To specify the total invoice discounts andamounts

Comment: A. TDS02 is required if the dollar valuesubject to discount is not equal to thedollar value of TDSO1.


TDS01 361 Total Invoice Amount M N2 1/10

Amount of invoice (including charges, less allow-ances) before terms discount (if discount applicable).

Total Invoice Amount[081 C I

TDS02 390 Amount Subject to Terms C N2 1/10DiscountAmount upon which the terms discount amount is cal-culated.

Amount Subject to TermsDiscount[082 C I

This can be used for price breaksor volume discounts.

TDS03 391 Discounted Amount Due 0 N2 1/10

Amount of invoice due if paid by terms discount duedate (total invoice or installment amount less cashdiscount.)

Discounted Amount Due[083 C I

Also can be used to eliminateissue of rounding off amounts.

TDS04 362 Terms Discount Amount 0 N2 1/10

Total amount of terms discount.Terms Discount Amount

[084 C I

See note under TDS03.

810.002003.DoDO - 40 911218


Segment: CTT Transaction Totals

Table: C

Sequence: 56

Usage: M

Max Use: 1Loop: 0

Purpose: To transmit a hash total for a specific ele-ment in the transaction set

Syntax Notes: 01 If CTT03 is present, then CTT04 is re-quired.

02 If CTT05 is present, then CTT06 is re-quired.


CTT01 354 Number of Line Items M NO 1/6Total number of line items in the transaction set.

Number of Line Items[085 C I

An accumulation of the total num-ber of IT1 segments.

CTT02 347 Hash Total 0 R 1/10Sum of values of the specific data element. (See ex-ample in X12 002003.)

Hash Total[086 C I

CTT02 is the sum of the value ofquantities invoiced (IT102) for

the total number of IT1 segments.

CTT03 81 Weight 0 R 1/8

CTT04 355 Unit of Measurement Code C ID 2/2

CTT05 183 Volume 0 R 1/8


CTT07 352 Description 0 AN 1/80

911218 810.002003.DoDO - 41


Segment: SE Transaction Set Trailer

Table: C


Max Use: 1Loop: 0

Purpose: To indicate the end of the transaction setand provide the count of the transmitted seg-ments (including the beginning (ST) and end-ing (SE) ... (See X12 Dictionary.)

Comment: A. SE is the last segment of each transac-tion set.


SE01 96 Number of Included Segments M NO 1/6Total number of segments included in a transactionset including ST and SE segments.

Number of IncludedSegments[087 C I

SE02 329 Transaction Set Control Number M AN 4/9Identifying control number assigned by the originatorfor a Transaction Set. Also see: Data InterchangeControl Number (28.)


[088 C I

This is the same number that ap-pears in ST02.

810.002003.DoDO - 42 911218

al 0

r. ESE

C M

.0E

a . 0V U 0

C.)c)

00

E 0 E E >o0>

°S

aC E* =CC

aa

E E > - .

-- 0 N -

0 _o C0: C - >

0t w OM, omw > j cc

o 0

V_ N v_ to N to cc 8 o

m U N-

07 81 .02 0 D 0 43

0 0 O 0 O ~ w mj w

z z in u 0 4

o4 N4 CV) V) 4) tv) M4 M0 In) (4 ) -

0 d( (0 NC - C

CE (0 m iZ 2

InD

ID E

.... 0 N0 -D 0) 0 a- C '20 0 0 '- - -

.0 > 0raE EE CUu

9121 81.003DD U3

>.1-0C V

Ub" V

0!0

r 0 0 00da Zo o CC2r .E Q-. Ccu

CL U) .0 CL ~ C *0=

E-2E P 0.- )O

0'D 0 ~ 0 0"o ~ .

IsE 0 Oda 0 UC

C C-0U0 C 0 C - C 'o 0

.0 0 >. U E .

> E. c c -UC>000.V 0.0 00 m

w =0 *02 :Ev0C0.0 0.0 0 mw00u

'a C- - 26

ID *0 PS U Lo "a 0- 0E =6 o a o a

:0. >. > , .>r-A

4c r. 4 SS0

L D SU S w - 01 02 q

oo m co mn M4 04P dI ~

.0 1

w 0 0

in U) 9n Cf ) L) wC 0Nf

.a 0

-r ID- s.0S

Ca mu (3 (3 0 0 0

S1O.002003.DoDO - 44 911217

o C4

0 z

00-

0 0 *C Ma

Q 0C 0 0> -o

z- -

w z A00 a 0

00e

0 E 5 0a 00(

o I I . I~ I I

> 0 C.. II-0 LI I

to to 6)L 4;

0 00 0 0 0

o IL IL ~ ~ )U m w- C

8 0,N coG 00 0o 0) 0 DQ

IN N 4 4 44 V4 4 4 4

E E

0 0

w

00j 0E

E0 0zE EE0 C ;

0121 01.003DD - 45

0 .

Va

00 E

0*

00

0 c CL 00 L) o

00 >V 0

-C a

0 0>O 0- 00

0 ;; UfN C D 4 C) r o ( -F

- C1

0 a 0o. C 0 2L L r w C a --us U - 0£su L U Lw 0 z z L L A n. 0

0 0 V m

a E

a- 44 -DA

0 00

o~ 0 - 0 0 0 0 0 000

% 0 0a'.00 0 0 0 0 0Z Ug . 0 m0

000 0012

C. I -E -o a z a--- 1

0-0Z 0 00

81.003DD -0 0 0 0 91121

C0

.0 -0

CE L

C4a00

00

Cl E

c C4

.0t

z0C L--

0 a.0

0 0-

0

>00

01D0> - -V

>D m CL'r

E~3 E ~00 oU Lot

R - C Coc 00 wa ccE Z n

> 00 00 U . CLO

10. -OV Mc )I n I

0L 0 00 0.0 0G 0U0.u. 0 0 ;7 ; ;u.U : :

LL U. - -CLI

0 00 40 ZWZ 494C 4 C4 C ) U)c o

o4 C- E4 (4 C4 04 Cl N 14 44 Cl N N

tClo a CD CO to C3 -o co co

OD00 0 00 00000o 0

C0 .

0i IDD ( 1 0 (a a 00 0 =e 00 0

0a> 0

in -

C 00 0 0. 0 L

0 00

0121 81.003DD -047-

oil

*0C) >

a aoE

S s5V 0

.0 .0 or -iPU

o0.

UT 0..

94 0, 0- Co UW)~~ 0nm m c n0I

FC C9 N. m. r.M0mm

v U) 0 0 0 0 0 00 0 < < ) wt

Iml U u U .. .0

I2 CL C

U ~

oLE 0 0 a aU 0

o I- U) LI

- 0' PS M) z) U 0-(

0 0 0 00 0 E E0~ ~~ ~~~~ 0E ( (U L) U )I

go~ 0 K: K:i - I

81.003.a,-48911

3

CE4

U)

E

0 0.

C4

cc.0

Ez

ulU

zU

2 -

9127o0020.oO-4

81O.002003.DoDO - 50 911217


10.7.20 DoD Convention for Using the 820 PaymentOrder/Remittance AdviceThis section provides the format and establishes the data contentsof the DoD 820 Transaction Set Convention. The paymentorder/remittance advice transaction set is used as addenda recordsin the implementation of Electronic Funds Transfer (EFT) andprovides advice to payee by the payor on the application of theEFT payment.




10.7.20.4 Code List Not Maintained By ASC X12See Section 10.4



10.7.20.7 820.O02003DoDO Convention

9109(w 820.002003.DoDO - Cove


620.OO?003.DoOO - Covw 910o0s


ASC X12.4 Transaction Set 820Remittance/Payment Advice (Version 002003)

Segment Hierarchy


Seg ReqIndustry ID Name Des Use Loop


USE BPS Beginning Segment for Payment M 1Order/Remittance Advice

NTE Note/Special Instruction F 100

CUR Currency 0 1

USE REF Reference Numbers M 5

USE DTM Date/Time Reference M 10

NI Name 0 1 N1\200


N3 Address Information 0 2

N4 Geographic Location 0 1





USE LS Loop Header M 1

USE N5 Car Ordered M 1 N5\10000

USE RMT Remittance Advice M 1 RMT\10000

CUR Currency 0 1USE REF Reference Numbers 0 5


USE LE Loop Trailer M 1



USE SE Transaction Set Trailer M 1

911223 820.002003.DoDO - 1


820.002003.DoDO - 2 911223


DoD Model Transaction Set 820Remittance/Payment Advice

Segment Hierarchy




6 BPS Beginning Segment for Payment M 1Order/Remittance Advice

9 REF Reference Numbers M 5

10 DTM Date/Time Reference M 10



11 LS Loop Header M 1

12 Ni Name M 1 Nl%10000

13 RMT Remittance Advice M I RMT\I0000

15 REF Reference Numbers 0 5 I]16 LE Loop Trailer M 1




911223 820.002003.DoO0 - 3


320.002003.DoOO - 4 311223



Table: A

Sequence: 10

Usage: M

Max Use: 1Loop: 0





Transaction Set ID[001 A ] Code Definition

820 X 12.4 RemittancelPayment Notice


Transaction Set Control No.[002 A I

Number assigned by theoriginator. Sequentially assigned

within each functional group.

911217 820.002003.DoDO - 5


Segment: BPS Beginning Segment for PaymentOrder/Remittance Advice

Table: A

Sequence: 20

Usage: M

Max Use: 1

Loop: 0Purpose: To (1) indicate the beginning of a payment

order/remittance advice transaction set andtotal payment amount and (2) to enable re-lated transfer of ... (See X12 Dictionary.)

Comment: A. BPS02 is the total currency amount ofall items being paid in this transaction.

B. When using this transaction set to ini-tiate a payment, BPS04, BPS05, BPS07,BPS09, BPSIO, BPS11, and BPS12 maybe required, depending upon the conven-tions issued by the specific banking chan-nel being used. BPS04 and BPS05relate to the originating DepositoryFinancial Institution (DFI).

C. BPS06 is the account number of the send-ing company to be debited or creditedwith payment.

D. BPS09 and BPS10 relate to the receivingDFI.

E. BPS1 1 is the account number of thereceiving company to be debited orcredited with the payment.

F. BPS13 is conditional on the ability ofthe receiving depository financial institu-tion (RDFI) to furnish the actual settle-ment date, and shali be left blank(omitted) by the originating company.


BPS01 591 Payment Method Code M ID 3/3Code used to designate the actual funds transfermethod.

820.002003.DoDO - 6 911217


Payment Method Code[003 A *] Code Definition

ADC ACH Demand Credit

BPS02 782 Amount M R 1/15Monetary amount.

Monetary Amount[004 A I

BPS03 305 Transaction Handling Code M ID 1/1Code designating the action to be taken by ail parties.

Transaction Handling Code[005 A I Code Definition

X Make Payment and Send Remittance Advice

BPS04 506 (DFI) ID Number Qualifier C ID 2/2

BPS05 507 (DFI) Identification Number C AN 3/12

BPS06 508 Account Number 0 AN 1/35

BPS07 509 Originating Company ID Number C AN10110

BPS08 510 Originating Company 0 AN 9/9Supplemental Code

Required BPS09 506 (DFI) ID Number Qualifier C ID 2/2

Code identifying the type of identification number ofDepository Financial Institution (DFI).

DIF ID No. Qualifier[006A *] <

Including check digits (9 digits). Code Definition01 ABA Transit Routing No.

Required BPS10 507 (DFI) Identification Number C AN 3/12

Depository Financial Institution (DFI) identificationnumber.

DIF ID No.[007 A I <

ABA Number with check digit offinancial institution receiving the

deposit.

911217 820.002003.DoDO - 7


Required BPS 11 508 Account Number C AN 1/35Account number assigned.

Account No.[008 A I <

Contractor's account number atfinancial institution.

BPS12 513 Effective Entry Date C DT 6/6

Date the originating company intends for the transac-tion to be settled.

Effective Date[009 A I

Processing cycle date.

Required BPS13 727 Settlement Date C DT 6/6

The date the transaction is actually settled. This fieldis to be used only by the RDFI. It must be leftblank by the originating company.

Settlement Date[010A I <

Enter spaces-actual settlementdate will be provided by financial

institution.

320.002003.DoD0 - 8 911217


Segment: REF Reference Numbers


Usage: MMax Use: 5

Loop: 0Purpose: To transmit identifying numbers




Reference No. Qualifier[011 A ] Code Definition

GC Government Contract No.


Reference No.[012A

Enter the contract PIIN/SPIIN.


911217 820.002003.DoOO - 9

DEPARTMENT OF DEENSEIMPLEMENTATION GUIDELINES



Max Use: 10Loop: 0


be present.



Date/Time Qualifier[013 A *1 Code Definition

007 Effective


Date[014 A I

(YYMMDD)


DTM04 623 Time Zone Qualifier 0 ID 212

820.002003.DoDO - 10 911217


Segment: LS Loop Header

Table: B

Sequence: 10

Usage: M

Max Use: 1

Loop: 0Purpose: To indicate that the next segment begins a

loop

Comment: A. LS is a control segment. (See X12 dic-tionary for further explanation.)


LS01 447 Loop Identifier Code M ID 1/4Code identifying loop within the transaction setwhich is bounded by the related "LS" and "LE" seg-ments (corresponding "LS" and "LE" segments musthave the same value for Loop Identifier). (See X12Dictionary.)

Loop ID Code

[015 A *1 Code Definition

N1 Loop ID Number

911217 820.002003.DoDO - 11


Segment: N1 Name

Table: B

Sequence: 20

Usage: M

Max Use: 1Loop: N1





Data Element SummaryRef. Data

Des. Element Name Attributes

N101 98 Entity Id Code M ID 2/2Code identifying an organizational entity or a physi-cal location.

Entity ID Code[016 A ] Code Definition

ZZ Mutually Defined


Name[017 A I

Sending organizations (DSSN).

N103 66 ID Code Qualifier C ID 1/2

N104 67 ID Code C ID 2/17

820.002003.DoDO - 12 911217


Segment: RMT Remittance AdviceTable: B


Max Use: 1Loop: 0

Purpose: To indicate the detail on items.Comment: A. Parties using this segment should agree

on the content of RMTO1 and RMT02prior to initiating transaction communica-tion.

B. RMT03 may also be used to specify theamount paid when different from theamount invoiced.

C. RMT08 is any amount being deductedfrom or added to a particular invoice orline item for reasons other than paymentdiscount (e.g., damaged goods, shortshipment, tax, penalty or late charge pay-ment).


Ref. DataDes. Eement Name Attributes

RMTO1 128 Reference Number Qualifier M ID 2/2Code qualifying the Reference Number.

Reference No. Qualifier(018 A *] Code Definition

IV Seller Invoice No.

RMT02 127 Reference Number M AN 1/30

RMT03 782 Amount 0 R 1/15

Required RMT04 777 Total Invoice Amount 0 R 1/15Amount of invoice (including charges, less allow-ances) before terms discount (if discount applicable).

Total Invoice Amount[019A I <

Total amount of invoice.

911217 20.002003.DDO - 13


RMT05 778 Amount Subject to Terms 0 R 1/15Discount

RMT06 779 Discounted Amount Due 0 R 1/15Amount of invoice due if paid by terms discount duedate (Total Invoice Amount less Terms DiscountAmount).

Discount Amount Due[020 A I

Total invoice amount less termsdiscount amount. Enter * if not

taken.RMT07 780 Discount Amount 0 R 1/15

RMT08 782 Amount 0 R 1/15Monetary amount.


Enter amount deducted as aprogress payment recoupment. If

none enter '.RMT09 426 Adjustment Reason Code 0 ID 2/2

Code indicating reason for adjustment to invoice orpayment.

Adjustment Reason Code1022 A 'I

Progress Payment Recoupment.Enter I if RMT08 = . Code Definition

ZZ Mutually Defined

RMT10 352 Description 0 AN 1/80

820.002003.DoDO - 14 911217


Segment: REF Reference NumbersTable: B


Max Use: 5Loop: 0


be present.

Data Element SummaryRef. DateDe. Element Name Attribute.


Reference No. Qualifier[023 A °1 Code Definition

SI Shipper's Identifying Number for Shipment


Reference No.[024 A I

Use shipment number.


911217 e20.002003.DoO0 - 15

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDEUNES

Segment: LE Loop TrailerTable: B

Sequence: 70

Usage: MMax Use: 1

Loop: 0Purpose: To indicate that the loop immediately preced-

ing this segment is completeComment: A. (See X12 dictionary for further explana-

tion.)


LEO1 447 Loop Identifier Code M ID 1/4Code identifying loop within the transaction setwhich is bounded by the related "IS" and "LE" seg-ments (corresponding "LS" and "LE" segments musthave the same value for Loop Identifier). (See X12Dictionary)

Loop ID Code[025 A I Code Definition

N1 Loop ID Number

820.002003.DoDO - 16 911217



Table: C


Max Use: 1Loop: 0



Data Element SummaryRef. DataDee. Eement Name Attributes


Number of IncludedSegments[026 A I

Total data segments.


Transaction Set Control No.[027 A I

Same number as assigned to ST02.

911217 820.002003.DoDO - 17

DEPARTMENT OP DEFENSEIMPLEMENTATION OUIDELNES

820.002003.DoOO - 18 911217

U U*Co WO 0o 0O

6 -0

.2 >

0 c0

0

C

00 0 0C 0Eo t 2>C -00 z0-.

V c 0 0 .0

on 0 = 00 - Cc. .E- 'E 00

0 E

D L CL LU

~ .0

> X0 02j0

co to P )U )P - m-v

-~~ NC C4 - C-4 0 0 0V 0

0 U) .0. U. U.on U) w w In co coc

0 0 0 0z.S0 0 0~ 0 a C 0

0

0- 0a 0

0 MO

00 C) 4 00 r_

a0 0 !2 Q44 a a 0

312- 8200) 02- 3D .- - 19

E EwU C.

0

Eo

- 060

ECC

o Ez :E 0

0 Eto 0. *9

.2 0 0 C00 Cfl

0 Eo 0 V 0. e-1 0 -

E cm14, 0 o 0

.0 0c E E CLE 00 EE

0 6.. E

L 0 0 L0 a - *.

Go .0 0 N ~ co0It Go .lo co04N

... NI0 0 0 C1

U. 0 L.

0 - 0 0 0

C 0

Vf 0-00

0 A0

0 0 0 0 IUN

.J 2-J0 E

00i &0 0 0lr 0 0002 0 00

820.00 0D 20 9100120170 U



10.7.40 DoD Convention for Using the 840 Request forQuotationThis section provides the format and establishes the data contentsof the DoD 840 Transaction Set Convention. The request forquotation transaction set provides potential buyers with the abilityto solicit price, delivery schedule, and other items from potentialsellers of goods and services.



10.7.40.3 Large Code Lists Maintained By ASC X 12See Section 10.3




10.7.40.7 840.O02003DoDO Convention

910905 840.002003.DoDO - Cover


840.002003.DoDO - Cove, 910906'


ASC X12.7 Transaction Set 840Request for Quotation (Version 002003)

Segment Hierarchy


Sag ReqIndustry ID Name Des Use Loop


USE BOT Beginning Segment for Request For QuoteM 1


CUR Currency 0 1



TAX Sales Tax Reference 0 3

USE FOB F.O.B. Relpted Instructions 0 1

88 Special Services 0 25

CSH Header Sale Condition 0 1

ITA Allowance, Charge or Service 0 10

USE lTD Terms of Sale/Deferred Terms of Sale 0 5

DIS Discount Detail 0 20


LDT Lead Time 0 12

SHH General Schedule 0 5

PRN Product ID Numbers 0 5



PWK Paperwork 0 25


TDI Carrier Details (Quantity and Weight) 0 2

TD5 Carrier Details (Routing Sequence/Transit 0 12Time)

TD3 Carrier Details (Equipment) 0 12

TD4 Carrier Details (Special 0 5Handling/Hazardous Materials)

USE MAN Marks and Numbers 0 10

N9 Reference Number 0 1 N9\1000

MSG Mesage Text 0 1000

USE NI Name 0 1 N1\200





911223 840.002003.DoDO - 1



FOB F.O.B. Related Instructions 0 1

TD1 Carrier Details (Quantity and Weight) 0 2

TD5 Carrier Details (Routing Sequence/Transit 0 1 2'ime)






USE P01 Purchase Order Baseline Item Data M ?O1\100000

CUR Currency 0 1

P03 Additional Item Detail 0 25



PWK Paperwork 0 25

USE PKG Marking, Packaging, Loading 0 25

P04 Item Physical Details 0 1



SSS Special Services 0 25


ITS Conditions of Sale 0 1

ITD Terms of Sale/Deferred Terms of Sale 0 2




SDQ Destination Quantity 0 50


LDT Lead Time 0 12

SCH Line Item Schedule 0 104






SLN Subline Item Detail 0 1 SLN\100o

I IPID Product/Item Description 0 1000

840.002003.Dao0 - 2 911223



MSG Mesage Text 0 1000 MSG\

N1 Name 0 1 N1\200









TD3 Carrier Details (Equipment) 0 1 2





USE CTT Transaction Totals M 1


911223 840.002003.DoO0 - 3


840.002003.0DO - 4 91122n


DoD Model Transaction Set 840Request for Quotation

Segment Hierarchy


Seg ReqPage No. ID Name Des Use Loop


8 BOT Beginning Segment for Request For QuoteM 1





16 ITD Terms of Sale/Deferred Terms of Sale 0 5

is MAN Marks and Numbers 0 1OMSG

19 N1 Name 0 1 Nlk 200





23 PO1 Purchase Order Baseline Item Data M 1 P01\100000

27 PlID Product/Item Description 0 1000

29 PKG Marking, Packaging, Loading 0 25


32 MAN Marks and Numbers 0 10





911223 840.002003.DoDO -5

DEPARTMENT OF DEF~EEIMPLEMENTATION GUIDELINES

940.002003.DoDO - 6 911223


Segment: ST Transaction Set HeaderTable: A

Sequence: 2Usage: M

Max Use: 1Loop: 0





Transaction Set ID Code[001 A *] Code Definition

840 Request For Quotation



[002 A I

911217 840.002003.DoD0 - 7


Segment: BQT Beginning Segment for RequestFor Quote

Table: A

Sequence: 3

Usage: M

Max Use: 1Loop: 0

Purpose: To indicate the beginning of a request for aquote transaction set and to transmit identify-ing numbers and dates

Syntax Notes: 01 If BQT05 is present, then BQT04 is re-quired.


BQT01 353 Transaction Set Purpose Code M ID 2/2Code identifying purpose of transaction set.

Transaction Set PurposeCode

[003 A °] Code Definition00 Original01 Cancellation04 Change

BQT02 586 Request for Quote Reference M AN 1/45NumberNumber assigned by the purchaser to identify his re-quest for quote.

Request for Quote ReferenceNumber

1004 A I

Example, two-position FY. five-position BPA number. and four-

position call number.BQT03 652 Request Quotation Control Date M DT 6/6

Date to be used for reference purposes in an RFQand a response to RFQ.

Request Quotation ControlDate

[005 A )

Required BQT04 374 Date/Time Qualifier C ID 3/3Code specifying type of date or time, or both dateand time.

840.002003.DoO0 - 8 911217

DEPARTMENT OF DEFESEIMPLEMENTATION GUIDEUES


Date that the response must bereceived by the buyer. Code Definition

106 Required By99 Bid Open (Date Bids Will Be Opened)

Required BQT05 373 Date 0 DT 6/6Date (YYMMDD).

Date[007A I <

BQT06 92 Purchase Order Type Code 0 ID 2/2

Required BQT07 960 Request for Quote Type Code 0 ID 2/2Code specifying the type of request for quote.

RFQ Type Code1008 A ]1 < Code Definition

01 Request for Quote02 Solicitation for Offer03 Invitation for Bid04 Request for Proposal05 Sealed Bid

911217 S40.002003.DaoO - 9


Segment: NTE Note/Special InstructionTable: A

Sequence: 4Usage: 0

Max Use: 100Loop: 0




NTE01 363 Note Reference Code 0 ID 313Code identifying the functional area or purpose forwhich the note applies. Also see: Free Form Mes-sage (3).

Note Reference Code[009 A *1 Code Definition

DEL DeliveryGEN Entire Transaction SetLIN Line ItemQUT Quotation InstructionTRA TransportationWHI Warehouse Instruction

NTE02 3 Free Form Message M AN 1160

Free-form text.Free-form Message

[010A I

NTE should only be used for excep-tions. Usually requires manual

processing unless pro-establishedagreements are made. Examples:

OUT - provisioning statement, donot substitute, must furnish exact

quantity and unit of issue re-quested. DEL - establish limit on

acceptable delivery time afteraward.

840.002003.DoDO - 10 911217



Sequence: 6Usage: M

Max Use: 12Loop: 0


be present.



Reference Number Qualifier[011 A *] Code Definition

MF Manufacturer's Pan NumberNS National Stock NumberRQ Purchase Requisition Number

REF02 127 Reference Number C AN 1130Reference number or identification number asdefined for a particular Transaction Set, or asspecified by the Reference Number Qualifier. Alsosee Reference Number Qualifier, (128).


For code "MF" enter CAGE andpart number.

REF03 352 Description C AN 1180A free-form description to clarify the related data ele-ments and their content.

Description[013 A I

For code 'MF" entermanufacturer's number.

911217 840.002003.DoDO - 11

DEPARTMENT OF DWIISEIMPLEMENTATION GUIDEJINES


Table: ASequence: 7

Usage: MMax Use: 3

Loop: 0







Contact Function Code[014 A *1 Code Definition

BD Buyer Name or DepartmentCW Confirm WithHM Hazardous Material Contact

Required PER02 93 Name 0 AN 1/35Free form name.

Name[015A I <

Required PER03 365 Communication Number Qualifier 0 ID 2/2Code identifying the type of communication number.

840.002003.DoDO - 12 911217

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIUELNES


[016 A °1 < Code DefinitionAU AUTOVONEM Electronic MailFT Federal Telecom SystemFX FacsimilePS Packet SwitchingTE TelephoneTX TWX

Required PER04 364 Communication Number C AN 7/21Complete communications number including countryor area code when applicable. Also see: Com-munications Number Qualifier (365).

Communication Number[017A I <

PER05 326 Request Reference Number 0 AN 1145

911217 $40.002003.DoO0 - 13


Segment: FOB F.O.B. Related Instructions

Table: A

Sequence: 9Usage: M

Max Use: 1Loop: 0


Comment: A. FOB01 indicates which party will paythe carrier.






Data Element SummaryRef. DateDe. Element Name Attributes

FOB01 146 Shipment Method of Payment M ID 2/2

Code identifying payment terms for transportationcharges.

Shipment Method of Pay(018 A *1

*ZZ' must be agreed upon tomean "Paid by Buyer." Code Definition

PP Prepaid by SellerZZ Mutually Defined

FOB02 309 Location Qualifier C ID 112Code identifying type of Location Identifier (310)used.

840.002003.DoOO - 14 911217


Location Qualifier[019 A *] Code Definition

DE DestinationOR OriginZZ Mutually Defined

FOB03 352 Description 0 AN 1180A free-form description to clarify the related data ele-ments and their content.

Description[020 A I





911217 840.002003.DoDO - 15


Segment: ITD Terms of Sale/Deferred Termsof Sale


Usage: 0Max Use: 5

Loop: 0

Purpose: To specify terms of sale.

Comment: A. If ITD01 equals 04 - ITDl0 is requiredand either ITD11 or ITD12 is required.If ITD01 equals 05 - ITDO6 or ITD07is required. If ITD01 does not equal04 or 05 - ITD03 or ITDO8 is required.

Syntax Nntes: 01 If ITDO3 is present, then at least one ofITD04, ITD05, ITD13 is required.

02 If ITDO8 is present, then -t least one ofITD04, or ITD05 is required.

03 If ITD09 is present, then ITDIO is re-quired.

Data Element SummaryRef. DataDes. Element Name Attributee

ITDO1 336 Terms Type Code 0 ID 2/2Code identifying type of payment terms.

Terms Type Code[021 A °1 Code Definition

08 Basic Discount

ITDO2 333 Terms Basis Date Code M ID 112Code identifying the beginning of the terms period.

Terms Basis Date Code[022 A *1 Code Definition

02 Delivery Date03 Invoice Date05 Invoice Receipt Date

ITDO3 338 Terms Discount Percent C R 1/6Terms discount percentage, expressed as a percent,available to the purchaser if an invoice is paid on orbefore the Terms Discount Due Date.

840.002003.DoDO - 16 911217

DEPARTMENT OF DEENSEIMPLEMENTATION GUIDENES

Terms Discount[023 A I

ITDO4 370 Terms Discount Due Date C DT 6/6Date payment is due if discount is to be earned.


ITDO5 351 Terms Discount Days Due C NO 1/3Number of days in the terms discount period bywhich payment is due if terms discount is earned.



ITDO7 386 Terms Net Days C NO 1/3

ITDO8 362 Terms Discount Amount C N2 1/10


ITD10 389 Deferred Amount Due C N2 1110




911217 840.002003.DoDO - 17


Segment: MAN Marks and NumbersTable: A


Max Use: 10Loop: 0

Purpose: To indicate identifying marks and numbersfor shipping containers

Data Element SummaryRef. DataDes. Element Name Attributse

MAN01 88 Marks and Numbers Qualifier M ID 1/2Code specifying the application or source of Marksand Numbers (87).

Marks and Numbers Qualifier[026 A "1

Use of these codes indicates.mark for' instructions in addition

to the "ship to." Code DefinitionL Line Item OnlyPB Premarked by Buyer

MAN02 87 Marks and Numbers M AN 1/45Marks and numbers used to identify a shipment orparts of a shipment. Also see: Marks and NumbersQualifier (88).

Marks and Numbers[027 A I

Examples, Mark for RequisitionNumber, DIC, Signal Code, Sup-plemental Address, Issue Priority

Designator. Distribution Code, Re-quired Delivery Date, Advice

Code, Fund Class Code, Transpor-tation Priority.

840.002003.DoDO - 18 911217

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDUNES


Sequence: 37

Usage: MMax Use: 1

Loop: N1


Comment: A. This segment, used alone, provides themost efficient method of providing or-ganizational identification. To obtainthis efficiency the "ID Code" (NI04)must provide a key to the table main-tained by the transaction processingparty.



Data Element SummaryRef. DataDes. Eement Name Attributse

N101 98 Entity Identifier Code M ID 212Code identifying an organizational entity or a physi-cal location.

Entity ID Code[028 A *1

"ZZ" also means 'mark for.' Code DefinitionRC Mail ToST Freight ToZZ Mutually Defined


Name(029 A I

N103 66 Identification Code Qualifier C ID 112Code designating the system/method of code struc-ture used for Identification Code (67).

911217 840.002003.DoDO - 19

DEPARTMENT OF DWENSEIMPLEMENTATION GUIDEUNES

ID Code Qualifier[030 A *1 Code Definition

10 Department of Defense Activity Address Code


ID Code[031 A I

840.002003.DeoDO - 20 911217

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDElNES


Table: A


Max Use: 2Loop: 0



N201 93 Name M AN 1135Free form name.

Name[032 A I

N202 93 Name 0 AN 1/35Free form name.

Name[033 A I

911217 840.002003.DoDO - 21




Max Use: 2Loop: 0




Address[034 A I


Address(035 A I

840.002003.DEO0 - 22 911217

DEPARTMENT OF DEIFiSEIMPLEMENTATION GUIDEJNES

Segment: P01 Purchase Order Baseline ItemData


Usage: 0Max Use: 1

Loop: 0Purpose: To specify basic and most frequently used

purchase order line item dataComment: A. See the Data Dictionary for a complete

list of IDs.

B. P01 is the line item identification

C. P0106 through P0125 provide for ten(10) different product/service IDs pereach item. For example: Case, Color,Drawing No., UPC No., ISBN No.,Mode 1 No., SKU.

Syntax Notes: 01 If P0105 is present, then P0104 is re-quired.

02 If P0106 is present, then P0107 is re-quired.




06 If PO 14 is present, then P015 is re-quired.

07 If PO1 16 is present, then P0117 is re-quired.

08 If P018 is present, then POl9 is re-quired.


911217 840.002003.DoDO - 23





P0101 350 Assigned Identification 0 AN 1/6Alphanumeric number assigned for differentiationwithin a transaction set.

Assigned Identification[036 A I

Req. line number.

P0102 330 Quantity Ordered M R 1/9

Quantity ordered.Quantity Ordered

[037 A I

P0103 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit measuremenL

Unit of Measure Code[038 A I

Some codes must be mutuallyagreed upon. DoD Manual

5000.12 M and ASC X12 diction-ary must be reconciled. Use

'ZZ" for conflicting codes.P0104 212 Unit Price C R 1/14

P0105 639 Basis of Unit Price Code 0 ID 2/2

P0106 235 Product/Service ID Qualifier 0 ID 2/2

Code identifying the type/source (f the descriptivenumber used in Product/Service ID (234).

Product/Service ID Qualifier[039 A "] Code Definition

BP Buyer's Part NumberFS Federal Stock Classification or NSNIN Buyer's Item NumberMG Manufacturer's Part NumberND National Drug Code (NDC)

840.002003.DoOO - 24 911217


P0107 234 Product/Service ID C AN 1/30Identifying number for a product or service.

Product/Service ID[040 A I


P0109 234 Product/Service ID C AN 1/30







P0116 235 Product/Service ID Qualifier 0 ID 212









911217 840.002003.DoDO - 25



840.002003.DoDO - 26 911217

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDElNES


Table: B


Max Use: 1000Loop: 0









Item Description Type[041 A ] Code Definition

F Free FormS Structured (From Industry Code List)X Semi-structured (Code end Text)

PID02 750 Product Characteristic Code 0 ID 2/3

PID03 348 Item Description Qualifier 0 ID 2/2


911217 840.002003.DoDO - 27


PID05 352 Description C AN 1/80

A free-form description to clarify the related data ele-ments and their content.

Description[042 A °]

PID06 752 Surface/LayerlPosition Code 0 ID 212

340.002003.DoDO - 28 911217


Segment: PKG Marking, Packaging, Loading

Table: B


Max Use: 25Loop: 0

Purpose: To describe marking, packaging, loadingand unl(ading requirements.

Comment: A. Use MEA (Measurements) segment todefine dimensions, tolerances, weights,counts, physical restrictions, etc.

B. Use PKG03 to indicate the organizationthat publishes the code list beingreferred to.

C. PKGO4 should be used for industry-specific packaging description codes.

D. Special marking or tagging data can begiven in PKGO5 (Description).

Syntax Notes: 01 If PKGO3 is present, then PKGO4 is re-quired.

02 At least one of PKGO4 or PKGO5 mustbe present.

Data Element SummaryRef. DataDos. Bement Name Attributes

PKGO1 349 Item Description Type M ID 1/1Code indicating the format of a description.

Item Description Type[043 A *1 Code Definition

F Free formS Structured (From Industry Code Ust)X Semi-structured (Code and Text)

PKG02 753 Packaging Characteristic Code 0 ID 115Code specifying the marking, packaging, loadingand related characteristics being described.

911217 840.002003.DoDO - 29

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDENES

Packaging CharacteristicCode

[044 A *1 Code Definition36 Package Specifications

PKGO3 348 Item Description Qualifier 0 ID 2/2

PKGO4 754 Packaging Description Code C ID 1/R

PKGO5 352 Description C AN 1 /80A free-form description to clarify the related data ele-ments and their content.

Description[045 A I

840.002003.DoDO - 30 911217


Segment: DTM Date/Time ReferenceTable: B


Max Use: 10Loop: 0


be present.




002 Delivery Requested


Date[047 A I

Required delivery date.



911217 840.002003.DoOO - 31


Segment: MAN Marks and Numbers

Table: B

Sequence: 84

Usage: MMax Use: 10

Loop: 0




Marks and Numbers Qualifier[048 A *]

Use of these codes indicates.mark for' instructions in addition

to the "ship to.' Code Definition

L Una Item OnlyPB Premarked by Buyer



840.002003.DoDO - 32 911217


Segment: CTT Transaction TotalsTable: C


Max Use: 1Loop: 0


Syntax Notes: 01 If CTT03 is present, then CI'T04 is re-quired.

02 If CTT05 is present, then CTI06 is re-quired.



Number of Line Items[050 A I

CTT02 347 Hash Total 0 R 1/10






911217 840.002003.DoDO - 33


Segment: SE Transaction Set TrailerTable: C


Max Use: 1Loop: 0



Data Element SummaryRef. DataDe. Eement Name Attributes



SE02 329 Transaction Set Control Number M AN 49Identifying control number assigned by the originatorfor a Transaction Set. Also see: Data InterchangeControl Number (28.)


[052 A I

40.002003.DO0 - 34 911217

a aa a a

.0 ~ 0

E E a0 c E

4~ 60cm

-C,

FA~~ 10" a-0. .

ox --. E

r- E~ *rCE = 0 -D

0 .FAr .0

0=D -. E jF~ ~~~~ .0*- U U h.q

L 0 0i C :t0 - J 3

> .r 00oE~ 9L C 0-0a 2 .2 - !ECLm

La a 0L ZV2 -0 2 0 ZE .!*0C~ ro.- ~.

4~~: o.r~2 I000 c 0 1.-c I Cc U) muwZ .2

> W 000-0 00000 a0 M0 zc

(D N- fe) .) MC 1%-('

-'i 000 0 0 0 00LL. I- L- 0 00 0I

coco m co z z

00

0.d I'4 V ~ ~) W CV) CV)

0 00 0 a-

0 a

aD E

CC

I 0 -LW

0121 -4-000 D - 35

CEEcS

.0 0

CC

0

E E

0 a ca E

bL . z -0S C 0

>1 a 2L 1.2.2

0..0

0cl U) LUULNL g )> co uC jL L9 . LN 00P 0

k N E0 .E V 6 4 I N * 4

us n 0 ) 0 N 0 ta 00 N M

N CO) C-) - N V~

uO uE.U *U Ujw

ow~~a~I 0O 0 000

O 0 0. 0) 0 24 2 0004

to IL N

00 0 0 0 0

z CZ 0 . *

a .2SI- SS 0 1 q m

o 06

0 0 E E . US

a a

0 c 2w u 0 u 0 W 0

I- * 02 0 oD - U911

alli

2 0 LL

co C

ou. S

00

g ti -6 x

E00-

UU

E

0 *. 0*I0 .0 EC

E~ W E- 'r I rl0.0 0. 0

E XC I 0

40O 0 4E0

wE

-c 0

2, co ml co P. -a 0 0 0m LG~ o 0 0c 0 0 0 0 - - -o

S4 0~ -00

tb cm 94 V) 0 2 0 ) 0 05 U 10

040 04 V ) ) V0 ) 0 ) 0

2

Cc Cc

C, " -Lz z z zZ-14K - S z

9121 84.003oC3

.2a2

0

;E

ow >~

&L c - 0 Sc.) E .2CLI

- Eo 79LL 0-u C

-. I C3 I~ Lt- -w

> E .. z .w 0 --

-V C4 a-0 m m .m ogo V

o~a .2 * --

u-. le ~ < A F

cc a IL IL K aL CL IL 0 0

N C1

ca co co w M 0 s 0 0 C1 0 0

00

U -o Cc

o IcanSn 0 0 0 - i 4

a~. .2 a a

00 co1 0 c 0

to E ECL Z

"0.000030ODO 38 1121


10.7.43 DoD Convention for Using the 843 Response toRequest for QuotationThis section provides the format and establishes the data contentsof the DoD 843 Transaction Set Convention. The response torequest for quotation (RFQ) transaction set provides potentialbuyers with price, delivery schedule, and other terms frompotential sellers of goods and services.




10.7.43.4 Code List Not Maintained By ASC X 12See Section 10.4




911115 843.002003.DoDO - Cover

DEPARTMENT OF OWEONSEIMPLEMENTATION GUVLNYEB

U43.002003.DoDO - Cover 911115

DEPARTMENT OF DEFENSEIMPLEMENTATION GUiELINES

ASC X12.8 Transaction Set 843Response to Request for Quotation

(Version 002003)Segment Hierarchy




USE BIR Beginning Segment for Response to M 1Request For Quote


CUR Currency 0 1


PER Administrative Communications Contact 0 3TAX Sales Tax Reference 0 3






ITO Terms of Sale/Deferred Terms of Sale 0 5



LDT Lead Time 0 12



Pl) Product/Item Description 0 200


PWK Paperwork 0 25



TD5 Carrier Details (Routing Sequence/Tranit 0 12Time)


TD4 Carrier Details (Special 0 5Hendling/Hazardous Materials)

MAN Marks and Numbers 0 10


MSG Message Text 0 1000

911223 843.002003.DoDO - 1










TDS Carrier Details (Routing Sequence/Transit 0 12Time)






USE P01 Purchase Order Baseline Item Data 0 1 PO1\100000

CUR Currency 0 1

USE P03 Additional Item Detail 0 25

USE CTP Pricing Information 0 25


MEA Measurementa 0 40

PWK Paperwork 0 25







ITO Conditions of Sale 0 1





SDO Destination Quantity 0 50


LDT Lead Time 0 12

843.002003.DoDO - 2 911223

DEPARTMENT OF DEFENSEIMPLEMENTATION GUI0EL3NES







CST Coat Analysis 0 1 CST100


CUR Currency 0 1


SLN Subline Item Detail 0 1 SLN\1000


CST Cost Analysis 0 1 CST100


CUR Currency 0 1




N1 Name 0 1 N1\200












911223 843.002003.DoOO -3

DEPARTMENT OP DEIMSEIMPLEMENTATION GUMELNES



USE CTT Transaction Totals M1

USE SE Transaction Set TrailerM1

$43.002003.DoDO - 4 911223


DoD Model Transaction Set 843Response to Request for Quotation

Segment Hierarchy




a BOR Beginning Segment for Response to M 1Request For Quote




13 NI Name 0 1 N1\200







21 P01 Purchase Order Baseline Item Data 0 1 P011100000

24 P03 Additional Item Detail 0 25

26 CTP Pricing Information 0 25







911223 643.002003DoDO - 5


943.002003.DoOO - 6 911223

DEPARTMENT OF DOISEIMPLEMENTATION GUIDELINES


Sequence: 2

Usage: M

Max Use: 1

Loop: 0


Comment: A. The transaction set identifier (ST0I) isintended for use by the translationroutines of the interchange partners toselect the appropriate transaction setdefinition (e.g., 810 selects the invoicetransaction set).



Transaction Set ID Code[001 A *1 Code Definition

843 Response to Request for Quotation



[002 A I

911217 843.002003.DaOO - 7

DEPARTMENT OF DEIENSEIMPLEMENTATION GUV.UNES

Segment: BQR Beginning Segment for Responseto Request For Quote

Table: ASequence: 3

Usage: MMax Use: 1

Loop: 0

Purpose: To indicate the beginning of a response torequest for quote transaction set and totransmit identifying numbers and dates

Syntax Notes: 01 If BQR05 is present, then BQR04 is re-quired.


BQR01 353 Transaction Set Purpose Code M ID 2/2Code identifying purpose of transaction set.


[003 A *1 Code Definition00 Original01 Cancellation04 Change

BQR02 586 Request for Quote Reference M AN 1/45NumberNumber assigned by the purchaser to identify his re-quest for quote.

Request for Quote Reference[004 A I

Two-position FY, five-position BPANumber and four-position call num-

ber from BQT02 in 840 Transac-tion Set.

BQR03 652 Request Quotation Control Date M DT 6/6

Date to be used for reference purposes in an RFQand a response to RFQ.

Request Quote Control Date[005 A I

Date from 9CT03 of 840 Transac-tion Set.

BQR04 374 Date/Time Qualifier C ID 3/3

BQR05 373 Date 0 DT 6/6

843.002003.DoDO - 8 911217

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDELIES

BGR06 587 Acknowledgment Type 0 ID 2/2

911217 843.002003.DoDO - 9

DEPARTMENT OF DEFB SEIMPLEMENTATION GUIDELINES


Sequence: 4Usage: 0

Max Use: 100Loop: 0


Comment: A. The NTE segment permits free-form in-formation/data which,under ANSI X12standard implementations, is not machineprocessable. The use of the "NTE"segment should therefore be avoided, ifat all possible, in an automated environ-ment.


NTE01 363 Note Reference Code 0 ID 3/3Code identifying the functional area or purpose forwhich the note applies. Also see: Free Form Mes-sage (3).

Note Reference Code[006 A °1 Code Definition

CHG ChangeDEL DeliveryGEN Entire Transaction SetINV Invoice InstructionsLIN Line ItemOUT Quotation InstructionsSPH Special HandlingTRA TransportationWHI Warehouse InstructionZzf Mutually Defined


Free-form Message[007 A I

'Y' equals pack quantity as re-quested and 'N" equals pack quan-

tity is different.

843.002003.DoO0 - 10 911217



Table: A

Sequence: 6Usage: M

Max Use: 12Loop: 0





Reference Number Qualifier(008 A *1 Code Definition

RQ Purchase Requisition Nunber



REF03 352 Description C AN 1180

911217 843.002003.DoDO - 11

DEPARTMENT OF D:MSEIMPLEMENTATION GUIDELNES



Max Use: 10Loop: 0


be present.

Data Element SummaryRef. DataDe. Eement Name Attibute

DTMO1 374 Date/Time Qualifier M ID 3/3Code specifying type of date or time, or both dateand time.

Date/Time Qualifier1010 A *1 Code Definition

001 Cancel After This Date and Time

036 Expiration DatelTime098 Bid (Effective)

DTM02 373 Date C DT 616Date (YYMMDD).

Date[011 A I



643.002003.DoO0 - 12 911217



Sequence: 137

Usage: M

Max Use: 1Loop: 0





Data Element SummaryRef. DataDes. Elment Name Attributes


Entity ID Code[012 A °1 Code Definition

SE Selling Party


Name1013A

N103 66 Identification Code Qualifier C ID 112Code designating the system/method of code struc-ture used for Identification Code (67).

ID Code Qualifier1014 A °] Code Definition

1 Dun and Bradstreet (Credit Reporting)


911217 843.002003.DoDO - 13

DEPARTMENT OF DEESE04PLEMENTATION GUIDELINES

ID Code1015 A I

643.002003.DoDO - 14 911217




Usage: MMax Use: 2

Loop: 0




Name[016 A I

N202 93 Name 0 AN 1135Free form name.

Name[017 A I

911217 843.002003.DoDO - 15




Max Use: 2Loop: 0


Data Element SummaryRet. DataDes. Element Name Attributes


Address[018A


Address1019A

843.002003.DODO - 16 911217


Segment: N4 Geographic Location


Usage: CMax Use: 1

Loop: 0








N401 19 City Name C AN 2/19Free-form text for city name.

City Name[020 A I

N402 156 State or Province Code C ID ' 2/2Code (Standard State/Province) defined by ap-propriate governmental agencies.



Postal Code[022 A I

N404 26 Country Code 0 ID 2/2

N405 309 Location Qualifier 0 ID 1/2

911217 843.002003.DoDO - 17


N406 310 Location Identifier C AN 1/25

843.002003.DDO - 18 911217




Usage: M

Max Use: 3Loop: 0


Comment: A. This segment is used to specify who isto be contacted on various conditions re-lated to the transaction. The term 'Com-munication" in the title and purposerelates to interpersonal communications,not network or telecommunications con-tacts.



PER01 366 Contact Function Code M ID 2/2

Code identifying the major duty or responsibility ofthe person or group named.

Contact Function Code(023 A "] Code Definition

SU Supplier Contact


Name[024 A I



(025 A *] Code DefinitionEM Electronic MailFX FacsimilePS Packet SwitchingTE TelephoneTL Telex

911217 843.002003.DoDO - 19





843.002003.DoDO - 20 911217


Segment: P01 Purchase Order Baseline ItemData


Usage: 0Max Use: 1


purchase order line item dataComment: A. See the Data Dictionary for a complete

list of IDs.

B. PO1 is the line item identification

C. P0106 through PO125 provide for ten(10) different product/service IDs pereach item. For example: Case, Color,Drawing No., UPC No., ISBN No.,Mode I No., SKU.




04 If P01 10 is present, then POIII is re-quired.


06 If P0114 is present, then POl1S is re-quired.





911217 843.002003.DDO - 21




P0101 350 Assigned Identification 0 AN 116Alphanumeric number assigned for differentiationwithin a transaction set.


Request for quotation line number.

P0102 330 Quantity Ordered M R 1/9Quantity ordered.

Quantity Ordered[028 A I

P0103 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit measurement.

Unit of Measure Code(029 A I

The 5000.12M and ASC X12 dic-tionary must be reconciled. Use

"ZZ' for conflicting codes.P0104 212 Unit Price C R 1/14

Price per unit of product, service, commodity, etc.Unit Price[030 A I



Code identifying the type/source of the descriptivenumber used in Product/Service ID (234).

Product/Service ID Qualifier[031 A °] Code Definition

VP Vendor's (Seller's) Pert Number


Product/Service ID[032 A I



$43.002003.DoDO - 22 911217


















911217 843.002003.Do0O - 23


Segment: P03 Additional Item Detail

Table: B

Sequence: 241

Usage: MMax Use: 25

Loop: 0

Purpose: To specify additional item related data in-volving variations in normal price/quantitystructure.

Comment: A. Some examples of price/quantity varia-tions are: price in different units fromthe PO1 segment, price changes by date,or price changes by quantity (break andlevel).

B. P0307 defines the unit of measure forP0306.

Syntax Notes: 01 If P0304 is present, then at least one ofP0303 or P0305 must be present.


P0301 371 Change Reason Code M ID 2/2Code specifying the reason for price or quantitychange.

Change Reason Code[033 A *] Code Definition

AQ Alternate Quantity and Unit of MeasureQT Quantity Price Break

P0302 373 Date 0 DT 6/6Date (YYMMDD).

Date1034 A ]

P0303 236 Price Qualifier 0 ID 3/3Code identifying pricing specification.

Price Qualifier Code[035 A *1 Code Definition

PBQ Unit Price Beginning Quantity

P0304 212 Unit Price C R 1/14Price per unit of product, service, commodity, etc.

Unit Price[036 A I

943.002003.DoO0 - 24 911217



P0306 380 Quantity M R 1/10Numeric value of Quantity. Also see: Unit of Meas-urement Code (355).

Quantity[037 A I

P0307 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit measurement.


P0308 352 Description 0 AN 1/80

911217 843.002003.DoDO - 25

DEPARTMENT OF DIENSEIMPLEMENTATION GUIDELNES

Segment: CTP Pricing Information

Table: B


Max Use: 25Loop: 0

Purpose: To specify pricing information

Syntax Notes: 01 If CTP02 is present, then CTP03 is re-quired.

02 If CTP04 is present, then CTP05 is re-quired.


Data Element SummaryRef. DataDes. Element Name Attribute

Required CTP01 687 Class of Trade Code 0 ID 2/2Code indicating class of trade.

Class of Trade Code[039 A *1 < Code Definition

DI DistributorMF ManufacturerOE OEMWH Wholesaler

Required CTP02 236 Price Qualifier 0 ID 313Code identifying pricing specification.

Price Qualifier Code[040 A *I < Code Definition

QTE Quote Price

CTP03 212 Unit Price C R 1/14Price per unit of product, service, commodity, etc.

Unit Price[041 A I

Offered unit price.

Required CTP04 380 Quantity 0 R 1110Numeric value of Quantity. Also see: Unit of Meas-

urement Code (355).

843.002003.DoDO - 26 911217

DEPARTMENT OF DEBISEIMPLEMENTATION GUIDBLINES

Quantity

[042 A I <

Offered quantity.

CTP05 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit measurement.


Offered unit of issue. The5000.12M and ASC X12 diction-

ary must be reconciled. Use 'ZZ'for conflicting codes.

CTP06 648 Price Multiplier Qualifier 0 ID 3/3

CTP07 649 Multiplier C R 1/10

911217 843.002003.DoO0 - 27


Segment: FOB F.O.B. Related InstructionsTable: B


Max Use: 1Loop: 0










Shipment Method of Pay[044 A *

'PP" equals FOB destination and'PC" equals FOB origin. Code Definition

PC Prepaid but Charged to CustomerPP Prepaid (by Seller)




843.002003.DoDO - 28 911217




F0807 352 Description 0 AN 1/80

911217 S43.002003.DoDO - 29




Max Use: 10Loop: 0

Purpose: To specify pertinent dates and times

Syntax Notes: 01 At least one of DTM02 or DTM03 mustbe present.




001 Cancel After This Date or Time036 Expiration Date/Time098 Bid (Effective)


Date[046 A I



843.002003.DoDO - 30 911217



Table: CSequence: 395

Usage: M

Max Use: 1Loop: 0




Data Element SummaryRef. DataDec. Eement Name Attributes


Number of Line Items1047 A I


Hash Total[048 A I


CTT04 355 Unit of Measurement Code C ID. 2/2




911217 843.002003.DoDO - 31


Segment: SE Transaction Set TrailerTable: C


Max Use: 1Loop: 0








[050 A I

i43.002003.DoO0 - 32 911217

9o z

0

0.W

oo cc*c

iC

02

LL 0

47 a c a

> 0 Z.

0 0 - c.4

C~C CIE0

0 o OVo o

-0 0 10CL .60

0r S 000 U C) -U : a nP(L3SA (

m 0j z >- Z 1-I o0a -j IL 0 000 5 0

0> -O 0

4 m -) mo 0oNM o

w V N Lf co0 tof 1 G ) t

0f) 0) 0) 0

o0 0 N 00*2r cc 0 0 ,CL 0i LL.

41 r -4 mUJ 0D 0ID 44

0c 0c 4 10 4 0 4 A. 4

0) 0 0

-N 0 0 S 0 0E

ui r- r- z z

o0 0 0 0l

Ix z -Z -. Z0 0

9 027830203oO-3

10

C4

0 r

0 0 IS0.uE

EO 0

CL 0 .0

U) LL

4K x o.i-i

0N V) -tF 4M W0

ON cc 0 NeON C40 C 4 94 4

OO

o~ .c(A 0 c0 0 C0 00 0

0 0

0 LL.w - 0. 0

o ~0- ~V 0 0 0 f4C ~z - < V) a. - N 0 u IN 04 -

64.000DD - 34 9100 1

0

C 0

10

0*

U 1

0 04

0_ 0 ELCI So - I-LFa aj x

0 a- CL 0 00. I .I

.. , a~ U-U.j D

oc w 0LC)0

> AL o aC A 0

m r 4 0 U - (D 04 0 n0m tt- m~ % 0 w-. tv -0 -)n v IoO C14 CO OD N- ;;~ A. o V l

0 *0 0 0 0 .20. CL A. -- U.0-

Net l e L 0 UuDa0

LU -p (a f% 0

a~~C aLU I CA

0000

WW0 0 0 0'ED - I-IA.~ ~~ ~ A. A . A . . .)C)UL.00 U U £

9121 84.-00 - 3S

I

ci

I

C

SM

~1

SMo

NaSMgo

U

a

aK

0

z.5

0U

0t0

~cUUI.- CUa

643.002003D00 - 36 311217

DEPARTMENT OF DEF=NSE


10.7.50 DoD Convention for Using the 850 PurchaseOrderThis section provides the format and establishes the data contentsof the DoD 850 Transaction Set Convention. The purchase ordertransaction set provides for customary and established businessand industry practices relative to the placement of purchaseorder for goods and services. This transaction set should notbe used to convey purchase order change or purchase orderacknowledgment information.








911218 650.002003.DoDO - Cove

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDEUINES

SSO.002003.DoOO - COve, 911213


ASC X12.1 Transaction Set 850Purchase Order (Version 002003)

Segment Hierarchy


Sog ReqIndustry ID Name Des Use Loop


USE BEG Beginning Segment for Purchase Order M 1


USE CUR Currency 0 1








USE rT) Terms of Sale/Deferred Terms of Sale 0 5


LDT Lead Time 0 12



PiD Product/item Description 0 200


PWK Paperwork 0 25







N9 Reference Number 0 1 N91000







USE PER Administrative Communications Contact 0 3911219 850.002003.DoO0 - 1

DEPARTMENT OF DEFEISEIMPLEMENTATION GUIDEIJNES

USE FOB F.O.B. Related Instrnction 0 1


USE TD5 Carrier Details (Routing Sequence/Transit 0 12Time)






USE P01 Purchase Order Baseline Item Data M 1 PO01\100000

CUR Currency 0 1


USE CTP Pricing Information 0 25



PWK Paperwork 0 25






USE ITA Allowance, Charge or Service 0 10






IT3 Additional Item Data 0 5


LDT Lead Time 0 12

USE SCH Line Item Schedule 0 104

TD1 Carrier Details (Quantity and Weight) 0 1USE TD5 Carrier Details (Routing Sequence/Transit 0 12

Time)




AMT Monetary Amount 0 1

USE SLN Subline Item Detail 01 SLN\1000

650.002003.DoDO - 2 911219




USE N9 Reference Number 0 1 N9\1000

USE MSG Message Text 0 1000
















USE AMT Monetary Amount 0 1


911219 850.002003.DoO0 - 3


35O.002003.DoDO - 4 911219


DoD Model Transaction Set 850Purchase Order

Segment Hierarchy




8 BEG Beginning Segment for Purchase Order M I


11 CUR Currency 0 1



18 FOB F.O.E. Related Instructions 0 1

20 FTD Terms of Sale/Deferred Terms of Sale 0 5


23 N1 Name 0 1 N1\200







Seg Req

ID Name Des Use Loop

34 PO Purchase Order Baseline Item Data M 1 P01\100000

38 CTP Pricing Information 0 25

40 PID Product/Item Description 0 1000



45 ITA Allowance, Charge or Service 0 10



50 SCH Line Item Schedule 0 104

52 TD5 Carrier Details (Routing Sequence/Transit 0 12Time)


911219 850.002003.DoDO - 6


55 SLN Subline Item Detail 0 1 SLN\1000


61 N9 Reference Number 0 1 N9\1000

62 MSG Message Text 0 1000

63 N1 Name 0 1 N1\200








71 AMT Monetary Amount 0 1 AMT\

72 SE Transaction Set Trailer 1

860.002003.DeO0 - 6 911219



Table: ASequence: 2

Usage: MMax Use: I

Loop: 0

Purpose: To indicate the start of a transaction set andto assign a control number -





850 X12.1 Purchase Order



[002 A I

911218 850.002003.DoDO - 7


Segment: BEG Beginning Segment for PurchaseOrder

Table: ASequence: 3

Usage: MMax Use: 1

Loop: 0

Purpose: To indicate the beginning of the purchaseorder transaction set and transmit identifyingnumbers and dates.


BEGO1 353 Transaction Set Purpose Code M ID 2/2Code identifying purpose of transaction set.


[003 A *] Code Definition

00 Original01 Cancellation04 Change05 Replace06 Confirmation (Award)07 Duplicate08 StatusZZ Mutually Defined

BEG02 92 Purchase Order Type Code M ID 2/2

Code specifying the type of Purchase Order.P.O. Type Code

[004 A °]

See Block 16, DD Form 1155. Code Definition

BD BiddingIN Information CopyRL Release (Blanket Order)SA Stand-alone OrderSS Supply or Service Order

BEG03 324 Purchase Order Number M AN 1/22Identifying number for Purchase Order assigned bythe orderer/purchaser.

P.O. Number[005 A I

PIIN. Enter contract or purchaseorder number. Block 1, DD 1155.

850.002003.DoDO - 8 911218


BEGO4 328 Release Number 0 AN 1/30Number identifying a release against a PurchaseOrder previously placed by the parties involved inthe transaction.


Enter SPUN if BEG02 equals RL.Block 2, DD 1155.

BEG05 323 Purchase Order Date M DT 6/6Date assigned by the purchaser to Purchase Order.

P.O. Date(007 A I

P.O. issue date (YYMMDD). Block3, DD 1155.

BEG06 326 Request Reference Number 0 AN 1/45

BEG07 367 Contract Number 0 AN 1/30

Contract number.Contract Number

[008 A I

Either the contract/purchaseorder/BOA No. Block 1 of DD

1155.BEGO8 587 Acknowledgment Type 0 ID 2/2

Code specifying the type of acknowledgment.Acknowl. Type

[009 A I Code DefinitionAK Acknowledge-No Detail or ChangeNA No Acknowledgment Needed

911218 SO.002003.DoDO - 9

m Im mmmiimmllllIlililIlllill miD MID a I I I I II



Sequence: 4Usage: F

Max Use: 100Loop: 0


Comment: A. The NTE segment permits free-form in-formation/data which,under ANSI X12standard implementations, is not machineprocessable. The use of the "NTE" seg-ment should therefore be avoided, if atall possible, in an automated environ-ment.

Data Element SummaryRef. DataDeso. Element Name Attributes


Note Reference Code[010 A *1

The use of notes must be coor-dinated with the receiver of the

'850' since notes are for humansnot computers. The telephone cell

or E-mail is a better alternative.NTE02 3 Free Form Message M AN 1/60

Free-form text.Free-Form Message

[011 A I

6S0.002003.DoDO - 10 911218


Segment: CUR CurrencyTable: A

Sequence: 5Usage: 0

Max Use: 1Loop: 0

Purpose: To specify the currency (dollars, pounds,francs, etc.) used in a transaction

Comment: A. See X12 dictionary.

Syntax Notes: 01 If CUR08 is present, then CUR07 is re-quired.


03 If CUR11 is present, then CURIO is re-quired.

04 If CUR12 is present, then CURIO is re-quired.



07 If CURl? is present, then CUR16 is re-quired.

08 If CURl8 is present, then CUR16 is re-quired.



Data Element SummaryRef. DataDe. Elment Name Attribute

CUR01 98 Entity Identifier Code M ID 2/2Code identifying an organizational entity or a physi-cal location.

911218 850.002003.DoDO - 11



BY Buying Party (Purchaser)SE Selling Party

CUR02 100 Currency Code M ID 3/3Code (Standard ISO) for country in whose currencythe charges are specified.

Currency Code(013 A I

CUR03 280 Exchange Rate 0 R 4/6Value to be used as a multiplier conversion factor toconvert monetary value from one currency toanother.

Exchange Rate[014 A I

CUR04 98 Entity Identifier Code 0 ID 2/2Code identifying an organizational entity or a physi-cal location.

Entity ID Code[015 A I

CUR05 100 Currency Code 0 ID 3/3Code (Standard ISO) for country in whose currencythe charges are specified.

Currency Code[016 A I

CUR06 669 Currency Market/Exchange Code 0 ID 3/3

CUR07 374 Date/Time Qualifier C ID 3/3Code specifying type of date or time, or both dateand time.

Date/Time Qualifier[017 A 1 Code Definition

007 Effective036 Expiration

CUR08 373 Date 0 DT 6/6Date (YYMMDD).

Date[018 A I

CUR09 337 Time 0 TM 4/4


850.002003.DoDO - 12 911218


CURl 1 373 Date 0 DT 6/6

CUR12 337 Time 0 TM 4/4


CUR14 373 Date 0 DT 6/6

CUR15 337 Time 0 TM 4/4


CUR17 373 Date 0 DT 6/6

CUR18 337 Time 0 TM 4/4


CUR20 373 Date 0 DT 6/6

CUR21 337 Time 0 TM 4/4

911 218 85O.002003.DoDO - 13



Sequence: 6Usage: 0

Max Use: 12Loop: 0





Reference Qualifier No.[019 A °1

Reference Number Qualifier, Refer-ence Number and Description are

used to provide data found on DDForm 1155 in: Block 16 "your ref-

erence,' Block 17 "accountingdata.' Block 5 'certification.' Code Definition

AT Appropriation No.BD Bid No.CR Customer Reference No.DS Defense Priorities Allocation System PriorityHM Hazardous Material ContactPR Price Quote No.RQ Purchase Requisition No.TA Traffic AdministratorTN Transaction Reference No.ZZ Mutually Defined (FAR/DFARS Para No.)


Reference No.[020 A I

Block 5, 7, or 17, DD 1155.


85O.002003.DoDO - 14 91121e

DEPARTMENT OF DEFENSEIMPLEMENTATION OUIDELINES

Description[021 A I

When REF01 is code 'AT' REF03will carry the long-line accounting

data. Block 17, DO 1155.

911218 OSO.002003.DoDO - 15



Table: ASequence: 7

Usage: 0Max Use: 3

Loop: 0Purpose: To identify a person or office to whom ad-

ministrative communications should bedirected



Data Element SummaryRef. DataDos. Eoment Name Attributse


Contact Function Code[022 A *1

A. Use 'CD' for Block 6. B. Use*SU' for Block 9. C. Use code

BD* for the name of contract-ing/ordering officer (Block 24).Other contacts are not on DO

Form 1155 but may be useful. Code DefinitionBD Buyer Name or DepartmentCD Contract ContactHM Hazardous Material ContactSU Supplier ContactTA Traffic Administrator


Name1023 A I


850.002003.DADO - 16 911218


Communication No. Qualifier[024 A * Code Definition

AU AUTOVON

TE Telephone


Communication No.(025 A I


911218 650.002003.DoDO - 17

DEPARTMENT Of DEPdSEIMPLEMENTATION GUIDELINES


Sequence: 9Usage: 0

Max Use: 1Loop: 0


Comment: A. FOBOI indicates which party will paythe carer.






Data Element SummaryRef. DateDee. Eement Name Attributes



[026 A *1Use FOB segment here when FOBapplies to entire order. For excep-tions, add a FOB segment to N1

loop. Code DefinitionPP Prepaid by Buyer

ZZ Mutually Defined (Paid by Buyer)


850.002003.DoDO - 18 911218

DEPARTMENT OF DE ENSEIMPLEMENTATION GUIDELVES

Location Qualifier[027 A °]

Use 'ZZ when FOB is 'other'(Block 8. DD Form 1155). Code Definition


FOB03 352 Description 0 AN 1180A free-form description to clarify the related data ele-ments and their content.

Description[028 A I

Enter location of PGA and accep-tance (e.g., DPRO Boeing, Seattle,

WA) for codes "DE' and "OR.'Use FOB point when -77- is in

F0602.FOB04 334 Transportation Terms Qualifier 0 ID 2/2

Code


F0806 309 Location Qualifier C ID 1/2


911218 850.002003.DoDO - 19


Segment: lTD Terms of SaleDeferred Termsof Sale


Usage: 0Max Use: 5

Loop: 0Purpose: To specify terms of sale.

Comment: A. If ITD01 equals 04 - ITDIO is requiredand either ITDll or ITD12 is required.If ITD01 equals 05 - ITDO6 or ITDO7is required. If ITDOI does not equal 04or 05 - ITD03 or ITDO8 is required.

Syntax Notes: 01 If ITDO3 is present, then at least one ofITDO4, ITDO5, ITD13 is required.

02 If ITDO8 is present, then at least one ofITD04, or ITDO5 is required.

03 If ITDO9 is present, then ITDIO is re-quired.


ITDO1 336 Terms Type Code 0 ID 2/2Code identifying type of payment terms.

Terms Type Code[029 A *]

Segment is not sent if discountnot offered. Code Definition

08 Basic Discount Offered

ITDO2 333 Terms Basis Date Code M ID 1/2Code identifying the beginning of the terms period.

Terms Basis Date Code[030 A *]

Use codes "3" or "5" unlessspecified otherwise in the con-

tract. Code Definition3 Invoice Date5 Invoice Receipt Date

SEO.002003.DoDO - 20 911218

DEPARTMENT OF DIEFENSEIMPLEMENTATION GUIDELINES

ITDO3 338 Terms Discount Percent C R 1/6

Terms discount percentage, expressed as a percent,available to the purchaser if an invoice is paid on orbefore the Terms Discount Due Date.

Terms Discount[031 A I

See Block 12, DD Form 1155.

ITDO4 370 Terms Discount Due Date C DT 6/6

Date payment is due if discount is to be earned.


ITDO5 351 Terms Discount Days Due C NO 113

Number of days in the terms discount period bywhich payment is due if terms discount is earned.



ITDO7 386 Terms Net Days C NO 113

Number of days until total invoice amount is due(discount not applicable).

Terms Net Days[034 A I

ITDO8 362 Terms Discount Amount C N2 1/10

Total amount of terms discount.Terms Discount Amount

1035 A I


ITD10 389 Deferred Amount Due C N2 1/10




Description[036 A I


911218 850.O02003.DoDO - 21

I I I II 1




Max Use: 10Loop: 0


be present.




Also use *98" for offers on pricequotes. Code Definition

150 Performance Start151 Performance Stop36 Expiration73 Delivery Date92 Contract Effective93 Contract Expiration98 Bid (effective)


Date[038 A I



850.002003.DoDO - 22 911213




Max Use: 1Loop: 0





Data Element SummaryRef. DataD*. Elment Name Attributes


911218 850.002003.DoDO - 23


Entity ID[039 A *1

A. Use code 'by' for "issued by'Block 6, DD Form 1155. B. Use

code "O1 for administered byBlock 7. C. Use Code "SE' for

.name and address.' D. Use code"BT' for mail to Block 13. E. Use"ST' for ship to, Block 14. F. Use

'PR' for payment will be madeby, Block 15. G. Use "MP' whenfacility, Block 9 is different from

the contractor's address. H. Oneof codes "21,' "24,' or '25' will

be sent to indicate the type ofseller's business, see Block 11 or

use "SE" if none apply. Code Definition21 Small Business24 Women-Owned Business. Small25 Women-Owned Business, Large27 Small Disadvantage BusinessBT Party to Be Billed for Other FreightBY Buying PartyMP Manufacturing Plant01 Outside Inspection AgencyPE Remit ToPR Payer

SE Selling PartyST Ship To


Name[040 A I

N103 66 Identification Code Qualifier C ID 1/2

Code designating the system/method of code struc-ture used for Identification Code (67).

ID Code Qualifier[041 A ]

A. When N101 is code "BT' or'BY' or 01' or 'PR' use code'10." B. When N101 is code

'SE' or '21 or '27 or '24' or"25" use code 'M2.' C. When

N101 is code 'ST' use eithercode 10' or 'M2.' D. Use'01 ' when CAGE code is not

available. Code Definition01 Dun and Bradstreet (Credit Report) (DUNS)10 Department of Defense Activity Address CodeM2 Contractor and Government Entity Code (CAGE)

S50.002003.DoDO - 24 911218



ID Code[042 AI

911219 85O.002003.Dobo - 2

DEPARTMENT OF DEFESEIMPLEMENTATION GUIDELINES

Segment: N2 Additional Name InformationTable: A


Max Use: 2Loop: 0


Data Element SummaryRef. DataDes. Element Name Attributes.

N201 93 Name M AN 1135Free form name.

Name[043 A I


Name[044 A I

86.002003.DoDO - 26 911218

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDEIJNES

Segment: N3 Address Information

Table: A


Max Use: 2Loop: 0




Address[045 A I


Address[046 A I

911218 850.002003.DoDO - 27

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDJNES



Max Use: 1

Loop: 0









City Name[047 A I

N402 156 State or Province Code C ID 2/2Code (Standard State/Province) defined by ap-propriate governmental agencies.

State/Prov. Code[048 A I


Postal Code[049 A I



$60.002003.DoDO - 28 911218

mmm • In In m nn n nunuuunulmlnnui • m0li111• 1

DEPARTMENT OF DWENSEIMPLEMENTATION GUIDWUNES

N405 309 Location Qualifier 0 ID 1/2Code identifying type of Location Identifier (310)used.

Location Qualifier[051 A I


Location Identification[052 A I

91121S 85O.002003.DDO - 29

DEPARTMENT OF DWEINSEIMPLEMENTATION GUIDEJi .:S



Usage: 0Max Use: 3

Loop: 0






Contact Function Code[053 A *l

A. Use "CD for Block 6 informa-tion. B. Use 'SU" for Block 9 in-

formation. Code DefinitionCD Contract ContactSU Supplier Contact

PER02 93 Name 0 AN 1135Free form name.

Name(054 A I

PER03 365 Communication Number Qualifier 0 ID 212Code identifying the type of communication number.


[055 A I

PER04 364 Communication Number C AN 7/21

050.002003.DoOO - 30 911218

DEPARTMENT OF DEFENSEIMPLEMENTATION4 QUIDEINES


911218 85O.002003.DoDO - 31




Max Use: 1Loop: 0


Comment: A. FOBO indicates which party will paythe carrier.


C. FOB06 is the code specifying tide pas-sage location.




Data Element SummaryRef. DataDes. Element Name Attributs


Shipment Method of Pay[056 A +] Code Definition

PP Prepaid (by Seller)ZZ Mutually Defined (Paid by Buyer)


Location Qualifier[057 A *1 Code Definition

CA CatalogCT ContractDE DestinationES EstimatedOR OriginOT Quote

80.002003.DoDO - 32 911218


FOB03 352 Description 0 AN 1/80A free-form description to clarify the related data ele-ments and their content.

Description[058 A I

Enter name/location of PQA respon-sibility and acceptance.





911218 850.002003.DoDO - 33


Segment: PO1 Purchase Order Baseline ItemData

Table: B

Sequence: 235

Usage: MMax Use: 1


purchase order line item data

Comment: A. See the Data Dictionary for a completelist of IDs.

B. P0101 is the line item identification

C. P0106 through P0125 provide for ten

(10) different product/service IDs pereach item. For example: Case, Color,Drawing No., UPC No., ISBN No.,Model No., SKU.







07 If PO1 16 is present, then P0117 is re-quired.




8U0.002003.DoDO - 34 911218




Required P0101 350 Assigned Identification 0 AN 1/6Alphanumeric number assigned for differentiationwithin a transaction set.

Assigned Identification[059 A ] <

Use CLIN for existing contracts; ifnone, assign a number.

P0102 330 Quantity Ordered M R 1/9Quantity ordered.

Quantity Ordered[060 A I

Required P0103 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit measurement.

Unit of Measure[061 A ] <

Some codes must be mutuallyagreed upon. DoD Manual

5000.12-M and ASC X12 Diction-ary must be reconciled. Use "ZZ"

for conflicting codes.P0104 212 Unit Price C R 1/14

Price per unit of product, service, commodity, etc.Unit Price[062 A I

P0105 639 Basis of Unit Price Code 0 ID 2/2Code identifying the type of unit price for an item.

Basis Unit Price Code[063 A *1 Code Definition

CA CatalogCT ContractES EstimatedQT Quote

P0106 235 Product/Service ID Qualifier 0 ID 2/2Code identifying the type/source of the descriptivenumber used in Product/Service ID (234).

911218 850.002003.DoDO - 35


Prod/Serv ID Qualifier[064 A *] Code Definition

CE Class of Contract CodeFS Federal Stock Class. or National Stock No.PD Part NumberPG Packaging Spec. No.VP Vendor's Part No.


Prod/Serv ID[065 A I


PO109 234 Product/Service ID C AN 1/30








P0117 234 Product/Service ID C AN 1130





850.002003.DoO - 36 911218



P0123 234 ProductlServicelID C AN 1/30



911218 850.002003.DOD0 - 37


Segment: CTP Pricing InformationTable: B


Max Use: 25Loop: 0

Purpose: To specify pricing informationSyntax Notes: 01 If CTPO2 is present, then CTP03 is re-

quired.

02 If CTPO4 is present, then CTPO5 is re-quired.



CTP01 687 Class of Trade Code 0 ID 2/2

Code indicating class of trade.Class of Trade Code

1066 A *]Use for trade discount. Code Definition

GV Government

CTP02 236 Price Qualifier 0 ID 313Code identifying pricing specification.

Price Qualifier Code[067 A °] Code Definition

CON Contract PriceDPR Discount PriceUCP Unit Cost Price

CTP03 212 Unit Price C R 1/14Price per unit of product, service, commodity, etc.

Unit Price[068 A I

CTP04 380 Quantity 0 R 1/10Numeric value of Quantity. Also see: Unit of Meas-urement Code (355).

Quantity[069 A I

850.002003.DoO0 - 38 911218


CTP05 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit measurement.

Unit of Measurement Code[070 A I

DoD manual 5000.1 2M and ASCX 12 dictionary must be recon-ciled. Use 'ZZ" for conflicting

codes.CTP06 648 Price Multiplier Qualifier 0 ID 313

Code indicating the type of price multiplier.Price Multiplier Qualifier

[071 A ] Code DefinitionDIS Discount Multiplier

CTP07 649 Multiplier C R 1/10Value, identified by price multiplier qualifier, to be

used to multiply price to obtain a new value.Multiplier[072 A I

911218 850.002003.DoDO - 39





Loop: 0Purpose: To describe a product in coded or fre-form

formatComment: A. Use PID03 to indicate the organization

that publishes the code list beingreferred to.





Data Element SummaryRef. DataDee. Eement Name Attribute


Item Description Type[073 A ] Code Definition

F Free FormS Structured



Item Description Qualifier[074 A "] Code Definition

AB Assigned by BuyerAS Assigned by Seller

860.002003.DoDO - 40 911219



A code from an industry code list which providesspecific data about a product characteristic. Alsosee: Item Description Qualifier (348).

Product Description Code[075 A I

PID05 352 Description C AN 1/80


Description[076 A I

Nomenclature or short servicedescription.

PID06 752 Surface/Layer/Position Code 0 ID 2/2

911218 850.002003.DoDO - 41


Segment: PKG Marking, Packaging, LoadingTable: B


Max Use: 25Loop: 0

Purpose: To describe marking, packaging, loadingand unloading requirements.




D. Special marking or tagging data can begiven in PKGO5 (Description).

Syntax Notes: 01 If PKG03 is present, then PKGO4 is re-quired.

02 At least one of PKGO4 or PKGO5 mustbe present.

Data Element SummaryRef. DataDes. Elment Name Attributes


Item Description Type1077 A "1 Code Definition

F Free FormS Structured

PKG02 753 Packaging Characteristic Code 0 ID 1/5Code specifying the marking, packaging, loadingand related characteristics being described.


[078 A °] Code Definition34 Product Marking35 Type of Package37 Package Protection

860.002003.DoDO - 42 911218


PKG03 348 Item Description Qualifier 0 ID 212Code identifying agency responsible for the codeused.

Item Description Qualifier[079 A *] Code Definition

AB Assigned by BuyerAS Assigned by Seller

PKGO4 754 Packaging Description Code C ID 1/7A code from an industry code list which providesspecific data about the marking, packaging or load-ing and unloading of a product. Also see: ItemDescription Qualifier (348).

Packaging Description Code[080 A I

PKGO5 352 Description C AN 1/80A free-form description to clarify the related data ele-ments and their content.

Description[081 A I

911218 850.002003.DoDO - 43




Max Use: 12Loop: 0


be present.


REFO 128 Reference Number Qualifier M ID 2/2Code qualifying the Reference Number.

Reference Number Qualifier[082 A I Code Definition

AT Appropriation Number




Description[084 A I

When REF01 is 'AT' REF03 willcarry long-line accounting data

Block 17.

S50.002003.DoDO - 911218

DEPARTMENT OF DEBISEIMPLEMENTATION GUIDEUNES

Segment: ITA Allowance, Charge or ServiceTable: B


Max Use: 10Loop: 0

Purpose: To specify allowances, charges or services

Comment: A. ITA12 is the quantity of free goods.

Syntax Notes: 01 If ITA02 is present, then at least one ofITA03, or ITA13 is required.

02 Only one of ITA06, ITA07, or ITA08must be present.

03 If ITAO8 is present, then ITA09 is re-quired.

04 If ITAIO is present, then rTAll is re-quired.

Data Element SummaryRef. DataDes. lement Name Attributes

ITA01 248 Allowance or Charge Indicator M ID 1/1Code which indicates an allowance or charge for theservice specified.

Allowance/Charge Ind.1085 A "I

Use code "A' to express a varia-tion in quantity percent over the

quantity.. Use code "C" to ex-press a variation in quantity

specified. Code DefinitionA Allowance

C ChargeN No Charge or Allowance

ITA02 559 Agency Qualifier Code 0 ID 2/2

ITA03 560 Special Services Code C ID 2/10

ITA04 331 Allowance or Charge Method of M ID 2/2Handling CodeCode indicating method of handling for an allowanceor charge.

911218 850.002003.DoDO - 46

DEPARTMENT OF DEFENSEIMPLEMENTATION GUDE.NES

Method of Handling Code[086 A *]

Code "02" indicates that theGovernment will reduce the in-

voice at the unit price, fordecreased OTY when they arewithin the UNDER variation al-

lowed, unless the invoice reflectsa correct amount. Code '06" indi-cates that if the OTY is within the

OVER variation allowed, the ap-plicable amount will be added to

the invoice, unless invoice amountis correct. Code Definition

02 Off Invoice06 Charge to be Paid by Customer

ITA05 341 Allowance or Charge Number 0 AN 1116

ITA06 359 Allowance or Charge Rate C R 1/9

ITA07 360 Allowance or Charge Total C N2 1/9Amount

ITA08 378 Allowance/ Charge Percent C ID 1/1QualifierCode indicating on what basis allowance or chargepercent is calculated.

All/Change Percent Qualifier[087 A *1 Code Definition

06 Base Price Amount

ITA09 332 Allowance or Charge Percent C R 116Allowance or charge expressed as a percent.

Allowance/Change Percent[088 A I

ITA10 339 Allowance or Charge Quantity 0 R 1/10

ITA1 1 355 Unit of Measurement Code C ID 2/2

ITA12 380 Quantity 0 R 1/10

ITA13 352 Description C AN 1/80

ITA14 150 Special Charge Code 0 ID 3/3

850.002003.DoDO - 46 911218

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDB.INES



Max Use: 1Loop: 0


Comment: A. FOBO indicates which party will paythe carrier.






Data Element Summary.Ref. DataDes. Element Name Attributes



[089 A "] Code DefinitionPP Prepaid by SellerZZ Mutually Defined (Paid by Buyer)


911218 850.002003.DoDO - 47


Location Qualifier[090 A *]

Use "ZZ' when FOB is "other"Block 8. Code Definition



Description[091 A I

Enter location of PQA and accep-tance (e.g., DCMO Boeing, Seat-tle, Washington) for codes 'DE"and 'OR.' Use FOB point when

"ZZ" is in FOB02.





860.002003.DoDO - 48 911218




Max Use: 10Loop: 0


be present.


Ref. DataDees. Element Name Attributes


Date/Time Qualifier[092 A 1 Code Definition

150 Performance Start

151 Performance Stop36 Expiration

73 Delivery Date92 Contract Effective93 Contract Expiration98 Bid (effective)


Date[093 A ")



011219 e5o.002003.DoDO - 49

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDWJNES

Segment: SCH Line Item ScheduleTable: B

Sequence: 272

Usage: 0

Max Use: 104

Loop: 0

Purpose: To specify the data for scheduling a specificline item.

Comment: A. SCH06 specifies the interpretation to beused for SCH07 and SCHO8.

Syntax Notes: 01 If SCH04 is present, then SCHOS is re-quired.

02 If SCHOI0 is used, then SCH09 is re-quired.

Data Element SummaryRef. DateDes. Element Name Attributes

SCH01 380 Quantity M R 1/10Numeric value of Quantity. Also see: Unit of Meas-urement Code (355).

Quantity[094 A I

SCH02 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit measurement.


DoD uses DoD 5000.12-M for unitof measure code. Some of thesecodes conflict with ASC X12 DE355. Use 'ZZ-Mutually Defined'for these conflicting codes after

reaching agreement with your trad-ing partner on use.

SCH03 352 Description 0 AN 1/80

SCH04 98 Entity Identifier Code 0 ID 212Code identifying an organizational entity or a physi-cal location.


ST Ship to

SCH05 93 Name C AN 1/35

Free form name.

850.002003.DoDO - 50 911218

DEPARTMENT OF DEFISEIMPLEMENTATION GUIDELNES

Name[097 A I

Use 'CAGE' code or 'DoDAAC"of the consignee. If additional

name/address information required,use NI loop within P01 loop.

SCH06 374 Date/Time Qualifier M ID 3/3Code specifying type of date or time, or both dateand time.

Date/Time Qualifier[098 A *] Code Definition

002 Delivery Requested

SCH07 373 Date M DT 6/6Date (YYMMDD).

Date[099 A I

SCH08 337 Time 0 TM 4/4

SCH09 374 Date/Time Qualifier 0 ID 3/3

SCH10 373 Date C DT 6/6

SCH11 337 Time 0 TM 4/4

911218 850.002003.DoO0 - 51

DEPARTMENT OF DEFENSEIMPLEMENTATION GUiD.NES

Segment: TD5 Carrier Details (Routing Se-quence/Transit Time)


Usage: 0Max Use: 12

Loop: 0

Purpose: To specify the carrier, sequence of routingand to provide transit time information

Comment: A. When specifying a routing sequence tobe used for the shipment movement inlieu of specifying each carrier within themovement: use TD502 to identify theparty responsible for defining the routingsequence; use TD503 to identify the ac-tual routing sequence, specified by theparty identified in TD502.

Syntax Notes: 01 At least one of TD502, TD504, orTD505 must be present.

02 If TD502 is present, then TD503 is re-quired.




TD501 133 Routing Sequence Code 0 ID 1/2

TD502 66 Identification Code Qualifier C ID 1/2

TD503 67 Identification Code C ID 2/17

TD504 91 Transportation Method Code C ID 112Code specifying the method of transportation forthe shipment.

850.002003.DoDO - 52 911218


Transportation Method Code[100 A *] Code Definition

A AirB BargeBU BusD Parcel PostM MotorR RailS OceanZZ Mutually Defined

TD505 387 Routing C AN 1/35

TD506 368 Shipment/Order Status Code 0 ID 2/2

TD507 309 Location Qualifier 0 ID 1/2

TD508 310 Location Identifier C AN 1/25

TD509 731 Transit Direction Code 0 ID 2/2

TD510 732 Transit Time Direction Qualifier 0 ID 212

TD511 733 Transit Time C R 1/4

911218 850.002003.DoDO - 63


Segment: MAN Marks and NumbersTable: B


Max Use: 10Loop: 0


Data Element SummaryRef. DataDe. Element Name Attribute.


Marks and Nos. Qualifier[101 A °]

Use of these codes indicatesmark for' instructions in addition

to the "ship to.' Code DefinitionL Una Item OnlyPB Premarked by Buyer



850.002003.DoDO - 64 911218


Segment: SLN Subline Item Detail

Table: B

Sequence: 290

Usage: 0Max Use: 1

Loop: SLNPurpose: To specify product subline detail item data


B. SLN01 is the identifying number for thesubline item. It is related to (but notnecessarily equivalent to) the baselineitem number. Example: 1.1 or IAmight be used as a subline number to re-late to baseline number 1.

C. SLN02 is the identifying number for thesubline level. The subline level isanalogous to the level code used in a billof materials.

D. SLN03 through SLN28 provide foreleven (11) different productlservice IDsfor each item. For example: Case,Color, Drawing No., UPC No., ISBNNo., Model No., SKU.

Syntax Notes: 01 If SLN06 is present, then SLN08 is re-quired.

02 SLN07 is present, then SLN06 is re-quired.

03 If SLN09 is present, then SLNIO is re-quired.

04 If SLNI1 is present, then SLN12 is re-quired.

05 If SLN13 is present, then SLN14 is re-quired.




911216 8SO.002003.DoDO - 5

DEPARTMENT OF DEENSEIMPLEMENTATION GUIDW.NES






SLN01 350 Assigned Identification M AN 1/6Alphanumeric number assigned for differentiationwithin a transaction set.


SLN02 350 Assigned Identification 0 AN 1/6

SLN03 661 Configuration Code M ID 1/1Code indicating the relationship of the subline itemto the baseline item.

Configuration Code[104 A *1 Code Definition

A AddedD DeleteI Included

SLN04 380 Quantity M R 1/10Numeric value of Quantity. Also see: Unit of Meas-urement Code (355).

Quantity[105 A I

SLN05 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit measuremenL

Unit of Measurement Code[106 A I

DoD manual 5000.12M and ASCX12 dictionary must be recon-ciled. Use "ZZ' for conflicting

codes.SLN06 212 Unit Price C R 1/14

Price per unit of product, service, commodity, etc.

850.002003.DoDO - 56 911218


Unit Price[107 A I

SLN07 639 Basis of Unit Price Code 0 ID 2/2

SLN08 662 Subline Price Change Code ID C ID 1/1Code indicating the relationship of the subline itemunit price to the baseline item unit price.

Subline Price Change Code ID[108 A *] Code Definition

A AddedD DeleteI Included

SLN09 235 Product/Service ID Qualifier 0 ID 2/2

SLN10 234 Product/Service ID C AN 1/30

SN1 1 235 Product/Service ID Qualifier 0 ID 2/2












911218 850.002003.DoDO - 57

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDELIES







650.002003.DoDO - 58 91 1218


Segment: PID Product/Item DescriptionTable: B


Max Use: 1000Loop: 0



B. PIDO4 should be used for industry-specific product description codes.






Item Description Type[109 A *1 Code Definition

F Free formS Structured



Item Description Qualifier[110 A *] Code Definition

AB Assinged by BuyerAS Assigned by Seller

911218 850.002003.DoDO - 59


PID04 751 Product Description Code C ID 1112A code from an industry code list which providesspecific data about a product characteristic. Alsosee: Item Description Qualifier (348).

Produce Description Code[111 A I


Description[112 A I


850.002003.DoDO - 80 911218

DEPARTMENT OF DEENSEIMPLEMENTATION GUIDELNES

Segment: N9 Reference NumberTable: B


Max Use: 1Loop: N9

Purpose: To transmit identifying numbers and descrip-tive information as specified by the refer-ence number qualifier


Data Element SummaryRef. DataDes. Bement Name Attributes

N901 128 Reference Number Qualifier M ID 2/2Code qualifying the Reference Number.


LI Una Item Identifier

N902 127 Reference Number C AN 1/30Reference number or identification number asdefined for a particular Transaction Set, or asspecified by the Reference Number Qualifier. Alsosee Reference Number Qualifier, (128).

Reference Number[114A I

N903 369 Free-form Description C AN 1/45

N904 373 Date 0 DT 6/6

N905 337 Time 0 TM 4/4

911218 850.002003.DoDO - 61

DEPARTMENT OF DWENWSEIMPLEMENTATION GUIDINES

Segment: MSG Message TextTable: B


Max Use: 1000Loop:

Purpose: To provide a free form format that wouldallow the transmission of text information.

Comment: A. MSGO2 is not related to the specificcharacteristics of a printer, but identifiestop of page, advance a line, etc.

Data Element SummaryRef. DataDes. Element Name Attribut

MSGO1 933 Free-Form Message Text M ANI /264Free-form message text.

Free Form Message Text[115 A

MSG02 934 Printer Carriage Control Code 0 ID 2/2

MSG03 363 Note Reference Code 0 ID 3/3

850.002003.DoDO - 62 911218

DEPARTMENT OF DEFENSEIMPLEMENTATION QUIDEWNES

Segment: N1 NameTable: B


Max Use: 1Loop: N1







Entity ID Code[116 A °]

Use "ST', ship to when code inSCH04 is not adequate to express

the complete address. Code DefinitionST Party to be Billed for Other Than FreightEN End UserST Ship To


Name[117A I


911218 850.002003.DoDO - 63

DEPARTMENT OF DEENSEIMPLEMENTATION GUIDELIJNES

ID Code Qualifier[119 A ] Code Definition

10 Department of Defense Activity Address Code92 Assigned by BuyerDO Contractor and Government Entity Code*


ID Code[118A I

850.002003.DoDO - 64 911219

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDEMNES



Usage: 0Max Use: 2

Loop: 0Purpose: To specify additional names or those longer

than 35 characters in length



N201 93 Name M AN 1/35


Name[120A

911218 850.002003.DoO - 65


Segment: N3 Address InformationTable: B


Max Use: 2Loop: 0


Data Element SummaryRef. DataDes.. Element Name Attributes


Address[121 A I


Address[122 A

850.002003.DoDO - 66 911218


Segment: N4 Geographic LocationTable: B

Sequence: 330

Usage: 0Max Use: 1

Loop: 0Purpose: To specify the geographic place of the

named partyComment: A. A combination of either N401 through

N404 (or N405 and N406) may be ade-quate to specify a location.







City Name1123 A I


State/Prov Code1124A


Postal Code[125 A I


Country Code[126A

911210 850.002003.DoDO - 67






650.002003.DoDO - 68 911218




Max Use: 12Loop: 0






AT Appropriation Nunber




Description[131 A I

When REF01 is "AT' REF03 willcarry the long-line accounting data.

911218 850.002003.DoDO - 69



Table: C

Sequence: 382

Usage: M

Max Use: ILoop: 0







Number of PO1 segments. Code Definition

TT Total Transaction Amount


Hash Totals[133 A I

The sum of the value of quantitiesordered (PO102) for each P01 seg-

ment.CTT03 81 Weight 0 R 1/8





850.002003.DoDO - 70 911213

DEPARTMENT OF DEBINSEIMPLEMENTATION GUIDELINES

Segment: AMT Monetary AmountTable: C


Max Use: 1Loop:

Purpose: To indicate the total monetary amount.Comment: A. If AMT is used in the detail area of

transaction set 850, 855, 860 or 865,AMT02 will indicate total line amount.If AMT is used in the summary area oftransaction set 850, 855, 860 or 865,AMT02 will indicate total transactionamount.


AMT01 522 Amount Qualifier Code M ID 112Code to qualify amount

Amount Qualifier Code[134 A I Code Definition

TT Total Transaction Amount

AMT02 782 Amount M R 1/15Monetary amount.


911218 850.002003.DoDO - 71

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDW.NES


Table: CSequence: 395

Usage: M

Max Use: 1Loop: 0





Number of Incl. Seg.[136 A I



[137A I

850.002003.DoDO - 72 911218

- S

3 01

O ID 0

0 _ 5 0>

0 z E0 C. C

00

0 W 0o 0lo T*C 0 "0

00

E. a" C

0 Ac Eo0 0 ~

-- = Z. -

0 - 0670 'R 0 0.

0~ 0 )

o u 0 3 0.

Ad Z' U) _r*00 Lo to CO Dh2 e c * z -) V-

1 a. * 0 AL "00 xC. 0 0. u a u

.- aca.; oa. C

-C

> 0o O OO O 0 0 0 0

C) 0 qt C.)C C

In 4 0 0 0 0 0 0 0 Z

cc ind co CI In woc

C1 C1 O .)c . c)C) q

o, lo

COLE 0 0

an~~ an a 0Ea

9121 8C.000 D - 7

E CcLL 6

. 0 0

E r0

z Z . 00 co

.2

E 5

C.. 0

co .4 t O'st0. ~ LL 0* ~ ~Z 0 a 0- 0

a, 20 2 X .0 X

*~t -oC6 0

0- 0 0 - 0 o.

cr.E CC r CL U C

or E ** a .CIL Ifl 0e "a 0~S .In 0

>l .2- 0 £0

w0 .20 cc

000

0E 0 0 0 0 0 0 0 '

>- Lu N WcoI 0 0 . 0 c00 o u 0 1 cc I.. io I

B. 0 U) 0i U) U) N) I ) (

z m) :) IA D Us. 1

v to In o #a La w w 0 0 0

0 6

u cc *z

mu 0E .2a O

0. C. & '

L L CUu - w

850.0020030oD0 - 74 911219

inn 0 ;E

-0Lo CL

c!t 0 0

U~00 C -

aE aa gOi -.

rn CUC

0 co0 E 0LIDLL CD

IU

CO 0~~ 000LS CL U.

o U 0 0

CL -. 6 0 E' 0 C(2~~~ a- ~ 0 .

a. "a C40oMZE ON 0

C. 0 0 A Cz 0U EuolU9 iUo. 40 Z m~ - 0 c. 0 EO~> 2e (A C0

'E.0U 0 LujU

Z 00

Q- '

> to ~ CL N OON

(0~~ M La0 - a(

40 Lf V CD C4

LL 00 0 0 o ook u L 0 0 0 0

N N .

44 444 4 4 4

= C4

0 -. 00u

Zo go !t 0Ul 0 . 0

D -

C 1~4c 0.

u U) ID n- ~ 01 ID

911218 650OO2003DoOO - 75

le aIL0 -r _.

.0 .0 a -0

E ~~.a LL0.6L

L EC 0

ran 0. W -,

-L 1> 200 .2o-

a =3 IIr. -= CL 0 .. uo 0 0 0* U*~o a.-

W.g. 0 06 0 0 -0 a >- CL

uj~ ~ ~ usa r n L 5 . r

4.)~n Ce LneU ,0 0. .j20W6 a Un

(n a a _ o 0O

E' E* , .5 0

4 00

to 0) N coNVo CO () A5 (5) (5)h5

M) V an N- w 44IL0 0 0 0 0 0-

ww 0 0 0 0 0 ~

- CL

1- 4 a 86

85000203D DO - 7 9121

Ur CL

owe00

, ,

C4 0

W 0 0 E

00 - 0u

0- zoa 06 0 J00

* UL .2

E v U.- -M

V 0> O..N0

W 0) a =0 0)0 T0 40 U -0404

N 0 0 N - ) )

(w 4 - >.S A

oc 0) 0) 0) 0). ) 0 ) 0) 0 ) 0

ca

C c 0 0 6 r )~i

w

Ra

oc0 N eD CL N>-0- U (n CL N

91 121 0 4OOOD 03Do - 7

c 3

~~ a 0~

o 00

* CCL

0.C',

0~0

0.0-) 0-9

C 0

ti * -0 >

c <U-U t> 0

to C4 0 nle PC9 00 C* Y

8 ~ !?0 0N l0A 000 0 0 0 22L EL L AL I

o4 N gLl. U) to- )II* V_ " m 0 0

coC ca ra0.0c 0.0

U~-

MA0 CZL C.. C-0.Dt CC

0()000DD -n 78 911218

30 IS

CE 0 0

E Ci

0 .0 0

0. LLccm o CDic

(A .2 0)0)

uu.co U) I*w D

> LL()L

40 co C.) VE Nov

U. .- R. LL U- L

IN* t V~ qt v t It V V

cc CD3 CD co c C a o CI c

0 .2 >C >0. NO C

o~. S 00.

2 0! cc z

CL CIS E' E-

; t,IL c c

9121 85l) 20I3oDO 79I

60

06,6C

.E 1-0

00

2 > 00

aL 0 C 0 >-* 01 0

0 C

I M E

P is a. ~< a£. 0 a0 c cNo ~ U

06. § 3: .2 C -D 0.

~~20 * i .0m E* I' 0..

-I 0 X"U 00 0 ,. CON 0 o IDM . AL

a0 (0 5 0 4 0U .P.C > (0(0 ( -0 (0 (0(0L

cc . Ee Ec -Z

0 0L

* .C 0 4 S = 0 It0

4c N N n. N N W P4

>4 U U 00 U UL U1 U 0 N UC t

U)~V M inS N(

m C

a 0 0

00~ 0 v I

P. fh C £

- 0 C

C6 -

0 0

850.OO2003DoDO -980 911216

0

wa-c 0

00

04~ -0-0c

0 0

- S E0w wE >

1 0 0- Sw

~0. 0.0c0E :E

X~a. "awo -s 0 060

W0~ -FCCC C 2 1C

U) 0 oc c jI

0. Ln V w0wEM 4M w cw

Cl-

o 000 0 0 0 0 0 #0 0

o 0 0 0 0 a 0

U) U) U) U) 0) C -U U) U)j

C4 Nl Nl Cl 0 0 0

ro r- r- - o0

V c

-0 0 0* 0

V0a V

00

U0 1*U . 0

91121 85000203DoD - 8

0.11

= .o ro c

CV u

EE

J. 0E0

1

to0

.0.00 V

V .20.0 CO

20 c 0 0 C

-C c ei

U) 10 a*

C) U) 0 0

U) to U) z z -

Cm M-. 0)N C

cado co c w n m...- o co r m n c t

to 00

aCO>6

wLL - .0

t) V

OS.0203l D 82 In 011210. Z 2 22 2 2

o Cc0

C0c I00

0 C7w 0;

P 0 E.0 IL

o3 E a

U -) 0

CLC

% 4 0 0 . -vN I

N0 m- It O (a M4Z; 0

U.0 00usujOV O - LU L C~ - 0

z 2 e .2 I- I-

0 0 O

0. e0 U e Wa

9121 85.000DD --

S5O.OO2003DoDO - 84 911218


10.7.55 DoD Convention for Using the 855 PurchaseOrder AcknowledgmentThis section provides the format and establishes the data contentsof the DoD 855 Transaction Set Convention. The purchase orderacknowledgment transaction set provides for customary and es-tablished business and industry practice relative to a seller'sacknowledgment of a buyer's purchase order.

10.7.55.1 IntroductionSee Section 10. 1







910906 855.002003.DoDO - Cove

DEPARTMENT OF DEFESEIMPLEMENTATION OUCIDEIES

855.002003.DoOO - Cove 910o9o

DEPARTMENT OF DBEISEIMPLEMENTATION GUIDELNES

ASC X12.9 Transaction 855Purchase Order Acknowledgment

(Version 002003)Segment Hierarchy




USE BAK Beginning Segment for Purchase Order M 1Acknowledgment

NTE Note/Special Instruction F 100

CUR Currency 0 1











LDT Lead Time 0 12

8HH General Schedule 0 5


PID Product/item Description 0 200

MEA Mesurements 0 40

PWK Paperwork 0 25








MSG Message Text 0 1000 MSG\

Ni Name 0 1 N1\200


911219 855.002003.DoO0 - 1




REF Reference Numbers 0 1 2



TD Carrier Details (Quantity and Weight) 0 2







PO1 Purchase Order Baseline Item Data 0 1 P01\100000

CUR Currency 0 1





PWK Paperwork 0 25













LDT Lead Time 0 12





86.002003.DoDO - 2 911219



ACK Line Item Acknowledgment 0 1 ACK\104



AMT Monetary Amount 0 1 AMT\




ACK Line Item Acknowledgment 0 104


MSG Message Text 0 1000 MSG\

N1 Name 0 1 N1\200















AMT Monetary Amount 0 1 AMT\


911219 855.002003.DoDO - 3

DEPARTMENT OF DEFENSEIMPLEMENTATION OUCDEUNES

955.002003.DoOO - 4 911219

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDE)INES

DoD Model Transaction Set 855Purchase Order Acknowledgment

Segment Hierarchy




a BAK Beginning Segment for Purchase Order M 1Acknowledgment





911219 855.002003.DoDO - S

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDWLNES

S.002003.DO - 6 911213



Level: AUsage: M

Max Use: 1Loop: 0






855 X1 2.9 Purchase Order Acknowledgment


Trans. Set Control No.[002 A I

911219 855.002003.DoOO - 7


Segment: BAK Beginning Segment for PurchaseOrder Acknowledgment

Level: AUsage: M

Max Use: 1Loop: 0

Purpose: To indicate the beginnin- of the purchaseorder acknowledgment transaction set andtransmit identifying numbers and dates.

Comment: A. BAK09 is the seller's order number.


BAK01 353 Transaction Set Purpose Code M ID 2/2Code identifying purpose of transaction set.

Trans. Set Purpose Code[003 A *] Code Definition

00 Original03 Delete04 Change

BAK02 587 Acknowledgment Type M ID 2/2Code specifying the type of acknowledgment.

Acknowl. Type[004 A *] Code Definition

AK Acknowledgment No Detail or ChangeRJ Rejected-No Detail

BAK03 324 Purchase Order Number M AN 1/22Identifying number for Purchase Order assigned bythe orderer/purchaser.

P. 0. Number[005 A I

Use PIIN from 850. Ref. Des.BEG03 No.

BAK04 323 Purchase Order Date M DT 6/6Date assigned by the purchaser to Purchase Order.

P. 0. Date1006 A )

Use 850. Ref. Des. BEGOS Date.

856.002003.DoDO - 8 911219


BAK05 328 Release Number 0 AN 1/30Number identifying a release against a PurchaseOrder previously placed by the parties involved inthe transaction.


Use 850. Ref. Des. BEG04 No.

BAK06 326 Request Reference Number 0 AN 1/45

BAK07 367 Contract Number 0 AN 1/30

Contract number.Contract Number

(008 A I

Use 850. Ref. Des. BEG06 No.

BAK08 127 Reference Number 0 AN 1/30

BAK09 588 Acknowledgment Date 0 DT 6/6Date assigned by the sender to the acknowledgment.

Ack Date[009 A I

911219 855.002003.CoDO - 9


Segment: CTT Transaction TotalsLevel: C

Usage: MMax Use: 1

Loop: 0Purpose: To transmit a hash total for a specific ele-

ment in the transaction set

Syntax Notes: If CTT03 is present, then CTT04 is required.If CTT05 is present, then CTT06 is required.

Data Element SummaryRef. DataDee. Element Name Attribute

CTTO1 354 Number of Line Items M NO 1/6Total number of line items in the transaction set.



CTT03 81 Weight 0 R 118





856.002003.DoDO - 10 911219


Segment: SE Transaction Set TrailerLevel: C

Usage: MMax Use: 1

Loop: 0Purpose: To indicate the end of the transaction set

and provide the count of the transmitted seg-ments (including the beginning (ST) and en-ding (SE) ... (See X12 Dictionary.)




Number of Incl. Seg.1011 A I


Trans. Set Control No.[012 A I

911219 855.002003.DoDO - 11


S55.002003.DoDO - 12 911213

a

6z

z z

E 0 0a 0 U 0

0 0

Po 0 E ~is 0 0

> *D

0 1 Z 0D

S o I -0- _ 6x o ; c

aR- O

>) co 00

coU ) M .

N U4) V W) F'

N C 0 0 0 0 0 0 0 0 -

4c -C -(4 44 C I- ujU)( U) Go o 0o o 0 0o 0 V ) #A

.C14 ii C4 C') Co) 4o) 0) ) M C.) m) V)

4 ' C 'C C 4 4 4 U U LU

> E

c- Cc 'r-

SC SU. 0

C ~ A. . U4 Z Z ..

911219 OS6.002003.DO 13

655.002003000O - 14 111219


10.7.56 DoD Convention for Using the 856 ShipNotice/ManifestThis section provides the format and establishes the data contentsof the DoD 856 Transaction Set Convention. The shipnotice/manifest transaction set lists the contents of a shipment ofgoods as well as additional information, product description,physical characteristics, type of packaging, marking, carrierinformation, and configuration of goods within the transportationequipment.

The sender of this transaction is the organization responsible fordetailing and communicating the contents of a shipment, orshipments to one or more receivers of the transaction set.








910906 856.002003.DoDO - Cov~


856.002003.DoDO - Cover 910906


ASC X12.10 Transaction Set 856Ship Notice/Manifest (Version 002003)

Segment Hierarchy




USE BSN Beginning Segment for Ship Notice M 1





USE HL Hierarchical Level M 1 HL\200000

USE UN Item Identification Detail 0 1

USE SN1 Item Detail (Shipment) 0 1

USE SLN Subline Item Detail 0 100

USE PRF Purchase Order Reference 0 1

USE P04 Item Physical Details 0 1


USE MEA Measurements 0 40

USE PWK Paperwork 0 25


USE TD1 Carrier Details (Quantity and Weight) 0 20

USE TD5 Carrier Details (Routing Sequence/Transit 0 1 2Time)

USE TD3 Carrier Details (Equipment) 0 12

USE TD4 Carrier Details (Special 0 5Handling/Hazardous Materials)



CLD Load Detail 0 1 CLD\200





NI Name 0 IN1\200

911219 856.002003.DoDO - 1

DEPARTMENT OF DEENSEIMPLEMENTATION GUIOENES







USE SDQ Destination Quantity 0 50

ETD Excess Transportation Detail 0 1

CUR Currency 0 1

USE ITA Allowance, Charge or Service 0 10





856.002003.DoDO - 2 911219


DoD Model Transaction Set 856Ship Notice/Manifest

Segment Hierarchy

Table 1 -Header Area



6 BSN Beginning Segment for Ship Notice M 1





10 HL Hierarchical Level M 1 HL\200000

12 UN Item Identification Detail 0 1

16 SNI Item Detail (Shipment) 0 1

18 PRF Purchase Order Reference 0 1

20 P04 Item Physical Details 0 1


25 MEA Measurements 0 40

27 PWK Paperwork 0 25


31 TD1 Carrier Details (Quantity and Weight) 0 20

33 TD5 Carrier Details (Routing Sequence/Transit 0 12Time)

36 TD3 Carrier Details (Equipment) 0 12

38 TD4 Carrier Details (Special 0 5Handling/Hazardous Materials)



41 NI Name 0 1 N1k200






911220 856.002003.DoDO - 3


51 SDC1 Destination Quantity 0 50

54 ITA Allowance, Charge or Service 0 10





856.002003.DoDO - 4 911220



Sequence: 2Usage: M

Max Use: 1Loop: 0


Comment: A. The transaction set identifier (STOI) isintended for use by the translationroutines of the interchange partners toselect the appropriate transaction setdefinition (e.g., 810 selects the invoicetransaction set).



Transaction Set ID Code[001 A ] Code Definition

856 Ship Notice/lManifest

ST02 329 Transaction Set-Control Number M AN 4/9Identifying control number assigned by the originatorfor a Transaction Set. Also see: Data InterchangeControl Number (28.)


[002 A ]

911220 856.002003.DoDO - 5


Segment: BSN Beginning Segment for ShipNotice

Table: A

Sequence: 3

Usage: M

Max Use: 1Loop: 0

Purpose: To transmit identifying numbers, dates andother basic data relating to the transaction set

Comment: A. BSN03 is the date the shipment transac-tion set is created.

B. BSNO4 is the time the shipment transac-tion set is created.


BSNO1 353 Transaction Set Purpose Code M ID 2/2Code identifying purpose of transaction set.


(003 A *I

Because of errors or omissions, itmay be necessary to retransmit

this transaction. The retransmis-sion, containing mandatory and

corrected data elements, will betrar mitted to all recipients of the

origi I transaction affected by thec..ange. New codes needed to

support some of MILSCAP Appen-dix A22 and the shipment perfor-

mance notification transaction. Code Definition

00 Original01 Cancellation05 Replace06 Confirmation07 Duplicate14 Advance NotificationDO1 Request for a Corrected Transaction'D02 Phyically Completed*D03 Second Follow-up*D04 Corrected Transaction Verified by ...

BSN02 396 Shipment Identification M AN 2/30A unique control number assigned by the originalshipper to identify a specific shipment.

Shipment Identifier1004 A I

866.002003.DoDO - 6 911220


BSN03 373 Date M DT 6/6Date (YYMMDD).

Date[005 A I

This time will be generated by sys-tem software.

BSN04 337 Time M TM 4/4Time expressed in 24-hour clock time (HHMM)(Time range: 0000 though 2359).

Time[006 A I

911220 856.002003.DoDO - 7


Segment: NTE Note/Special Instruction

Table: ASequence: 4

Usage: FMax Use: 100

Loop: 0


Comment: A. The NTE segment permits free-form in-formation/data which,under ANSI X12standard implementations, is not machineprocessable. The use of the "NTE"segment should therefore be avoided, ifat all possible, in an automated environ-ment.



Note Reference Code[007 A *] Code Definition

GEN Entire Transaction Set


Free-Form Message[008 A I

In addition to other potential useof this segment, it will be used to

provide explanations required bycodes which may be used in a

now segment developed to sup-port various contract conditions.The 'NTE" segment will be used

for this purpose only when noother alternative method is avail-

able within the 856 transactionset, e.g., when shipment is made

without an NSN at the directionof the contracting officer, use

NTE02 to enter authority for theshipment.

8S6.002003.DoD0 - 8 911220



Sequence: 5Usage: 0

Max Use: 10Loop: 0

Purpose: To specify pertinent dates and times

Syntax Notes: 01 At least one of DTM02 or DTM03 mustbe present.




Date/Time Qualifier[009 A "]

Code 011 is the date shipped (thedate shipment was released to car-

rier) or the date performed. (com-pleted), if a service is being

described. Code 017 is the es-timated date of delivery or perfor-

mance. Use code D01 when theactual shipment is not known. Code Definition

011 Shipped017 Estimated DeliveryD01 Estimated Shipment Date*


Date[010 A I



911220 856.002003.DoDO - 9


Segment: HL Hierarchical Level

Table: B

Sequence: 7Usage: M

Max Use: 1Loop: 0

Purpose: To identify dependencies among and the con-tent of hierarchically related groups of datasegments.

Comment: A. The HL Segment is used to identifylevels of detail information using aHierarchical Structure, such as relatingline item data to shipment data, andpackaging data to line item data.

B. HL02 identifies the Hierarchical IDNumber of the HL segment to which thecurrent HL segment is subordinate.

C. HL03 indicates the context of the seriesof segments following the current HLsegment up to the next occurrence of anHL segment in the transaction. For ex-ample, HL03 is used to indicate that sub-sequent segments in the HL loop form alogical grouping of data referring to ship-ment, order or item level information.

D. HL04 indicates whether or not there aresubordinate (or child) HL segments re-lated to the current HL segment.

E. The HL segment defines a top-down/left-right ordered structure. HL01 C#HL01shall contain a unique alphanumeric num-ber for each occurrence of the HL seg-ment in the transaction set. For exampleHLOl could be used to indicate the num-ber of occurrences of the HL segment,in which case the value of HL01 wouldbe "1" for the initial HL segment, andwould be incremented by one in eachsubsequent HL segment within the trans-action.

856.002003.DoD0 - 10 911220



HL01 628 Hierarchical ID Number M AN 1/12A unique number assigned by the sender to identifya particular data segment in a hierarchical structure.

Hierarchical Number[011 B I

Sequence number.

HL02 734 Hierarchical Parent ID Number 0 AN 1/12Identification number of the next higher hierarchicaldata segment that the data segment being describedis subordinated to.

Hierarchial Parent ID[012 B I

Not used the first time, but usedthe second and subsequent times.

HL03 735 Hierarchical Level Code M ID 1/2Code defining the characteristic of a level in a hierar-chical structure.

Hierarchial Level Code(013 B "] Code Definition

I Item0 OrderP Pack (Carton)Q SubpackS ShipmentT Tare (Pellet)

HL04 736 Hierarchical Child Code 0 ID 1/1Code indicating if there are subordinate hierarchicalchild data segments to the level being described.

Hierarchical Child Code[014 B I

911220 856.002003.DoDO - 11


Segment: LIN Item Identification DetailTable: B

Sequence: 8Usage: 0

Max Use: 1Loop: 0

Purpose: To specify basic item identification data.


B. LINO1 is the line item identification(DM Number 266388)

C. LIN02 through LIN31 provide for fif-teen (15) different product/service IDsfor each item. For Example: Case,Color, Drawing No., UPC No., ISBNNo., Model No., SKU.

Syntax Notes: 01 If LIN04 is present, then LINOS is re-quired.

02 If LIN06 is present, then LIN07 is re-quired.


04 If LIN1O is present, then LINll is re-quired.



07 If LINI6 is present, then LINI7 is re-quired.





856.002003.DoDO - 12 911220




1 4 If LIN30 is present, then LIN31 is re-quired.


LIN01 350 Assigned Identification 0 AN 1/6Alphanumeric number assigned for differentiationwithin a transaction set.

Assigned Identification[015 B I

A. This element carres the CLINor ELIN. B. If less than 4 digits,system software will prefix with

zeros to achieve 4 digits, e.g.,0001. C. The HL loop must cycle

for every different number carriedin LIN01. In this way every CLIN

or ELIN will be picked-up in thetransaction.

LIN02 235 Product/Service ID Qualifier M ID 2/2Code identifying the type/source of the descriptivenumber used in Product/Service ID (234).

Product/Service ID Qualifier[016 B ] Code Definition

D01 MILSTRIP Document NumberFS Federal Stock Class. and/or National Stock No.SV Service RenderedVP Vendor's (Seller's) Part Number

LIN03 234 Product/Service ID M AN 1/30Identifying number for a product or service.

Product/Service ID[017 B I

Data elements LINO4-31 may beused to convey additional item

identification data. They may alsocarry other explanations ratherthan create a new 'NTE' or a

new segment.LIN04 235 Product/Service ID Qualifier 0 ID 2/2

LIN05 234 Product/Service ID C AN 1/30

911220 856.002003.DoDO - 13


LIN06 235 Product/Service ID Qualifier 0 ID 2/2




LIN1O 235 Product/Service ID Qualifier 0 ID 2/2

LIN1 1 234 Product/Service ID C AN 1/30


LIN 13 234 Product/Service ID C AN 1/30









LIN22 235 Product/Service ID Qualifier 0 ID 212



656.002003.DoDO - 14 911220






L1N29 234 Product/Service ID C AN 1/30



911220 856.002003.DoDO - 15


Segment: SN 1 Item Detail (Shipment)


Usage: 0Max Use: 1

Loop: 0

Purpose: To specify line item detail relative to ship-ment

Comment: A. SNIO is the ship notice line item iden-tification (DM Number 268388).

B. SN103 defines the unit of measurementfor both SN102 and SN104.

Syntax Notes: 01 If SN105 is present, then SN106 is re-quired.


SN101 350 Assigned Identification 0 AN 1/6

SN102 382 Number of Units Shipped M R 1/10Numeric value of units shipped in manufacturer'sshipping units for a line item or transaction set.Also see: Unit of Measurement Code (355).

Number of Unit Shipped[0181 B

A. If MILSTRIP is shown, quantityshipped and UOM are recorded

against each requisition number,not item number. For final ship-ment of a line item where varia-tion in quantity clause conditionexists, preparer shall enter a "Z'

following the last digit of the quan-tity shipped for that line or

prepare a corrected transaction ad-ding the 'Z.' B. If a replacement

shipment, enter "A, "B," etc.,below last digit of quantity. 'Zo is

not used on underrun when finalline item is replaced.

SN103 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit measurement.

85e.002003.DoDo - 16 911220



DoD uses DoD manual 5000.12-M. A second unit of measure

data element should be added tohandle the situation where one iscited for reasons other than pay-ment. Some codes conflict with

ASC X12, use "ZZ.' Mutuallydefined for those codes.

SN104 646 Quantity Shipped to Date 0 R 119

SN105 330 Quantity Ordered 0 R 1/9

SN106 355 Unit of Measurement Code C ID 2/2

SN107 728 Returnable Container Load 0 ID 1/2Make-Up Code

SNI08 668 Line Item Status Code 0 ID 2/2

911220 856.002003.DoDO - 17


Segment: PRF Purchase Order Reference

Table: B


Max Use: 1Loop: 0

Purpose: To provide reference to a specific purchaseorder


PRF01 324 Purchase Order Number M AN 1/22Identifying number for Purchase Order assigned bythe orderer/purchaser.

Purchase Order Number[020 B I

A schedule against which an orderhas been placed, even when

placed on a non-DoD schedule.

PRF02 328 Release Number 0 AN 1/30Number identifying a release against a PurchaseOrder previously placed by the parties involved inthe transaction.

Release Number[021 B 1

A. Will contain the call/order num-ber, and an amendment number ifappropriate. B. When shipping in-

structions are furnished bytelephone or message, they should

be confirmed by a contractmodification within 5 days. If

shipment is made prior to receiptof a confirming modification, the

six-digit modification serial numberor the two-digit call/order modifica-

tion indicator will be entered inPRF03 or PRF02 as appropriate.These numbers will be provided

by contracting officer.PRF03 327 Change Order Sequence Number 0 AN 1/8

Number assigned by the orderer identifying aspecific change or revision to a previously trans-mitted transaction set.


[022 B]

Will contain the contract modifica-tion number.

856.002003.DoDO - 18 911220


PRF04 323 Purchase Order Date 0 DT 6/6

PRF05 350 Assigned Identification 0 AN 1/6

PRF06 367 Contract Number 0 AN 1/30Contract number.

Contract Number[023 B I

This data element carries the con-tract number, P1IN. The SPIN will

be carried in data element PRFO2as appropriate.

911220 856.002003.DoO0 - 19


Segment: P04 Item Physical Details

Table: B

Sequence: 13

Usage: 0

Max Use: 1Loop: 0

Purpose: To specify the physical qualities, packaging,weights and dimensions relating to the item.

Comment: A. P0403 - The "Unit of Measure Code"(Element #355) in this segment positionis for purposes of defining the pack(PO401)/size (PO402) measure which in-dicates the quantity in the inner packunit. Example: If the carton contains 2412-ounce packages, it would bedescribed as follows: Element 356 =

24; Element 357 = 12; Element 355 =

oz.

B. P0416 defines the unit of measure forP0413, P0414, and P0415.


02 If P0406 is present, then at least one ofP0407 or P0408 is required.


04 If P0416 is present, then at least one ofP0413, P0414 or P0415 is required.


Ref. DataDes. Bement Name Attributes

P0401 356 Pack 0 NO 1/6Number of inner pack units per outer pack unit.Also see: Size (357), Unit of Measurement Code(355).

Pack[024 B I

P0402 357 Size O R 1/8Size of supplier units in pack. Also see: Pack(356), Unit of Measurement Code (355).

Size1025 B I

856.002003.DoDO - 20 911220


P0403 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit measurement.


See comment SN103.

P0404 352 Description 0 AN 1/80

P0405 103 Packaging Code 0 ID 5/5Code identifying the type of packaging. Part 1.Packaging form. Part 2. Packaging Material.

Packaging Code[027 B I

P0406 187 Weight Qualifier 0 ID 1/2Code defining the type of weight.

Weight Quailfier[028 B )

P0407 384 Gross Weight per Pack C R 1/9Numeric value of gross weight per pack. Also see:Unit of Measurement Code (355).

Gross Weight Per Pack[029 B I



P0409 352 Description 0 AN 1180

P0410 385 Gross Volume per Pack 0 R 1/9Numeric value of gross volume per pack. Also see:Unit of Measurement Code (355).

Gross Volume Per Pack[031 B I


Unit of Measuure Code[032 B I

P0412 352 Description 0 AN 1180

911220 856.002003.DoDO - 21


P0413 82 Length 0 R 1/6Largest horizontal dimension of an object measuredwhen the object is in the upright position. Alsosee: Measurement Unit Qualifier (90), Unit of Meas-urement Code (355).

Length[033 B I

See comment SN103.

P0414 189 Width 0 R 1/8Shortest measurement of the two horizontal dimen-sions measured with the object in the upright posi-tion. Also see: Measurement Unit Qualifier (90),Unit of Measurement Code (355).

Width[034 B I

P0415 65 Height 0 R 116Vertical dimension of an object measured when theobject is in the upright position.

Height[035 B I



See comment SN103.

856.002003.DoDO - 22 911220



Table: B


Max Use: 200Loop: 0









Item Description Type[037 B *1 Code Definition

F Free Form


PID03 348 Item Description Qualifier 0 ID 2/2



911220 856.002003.DoDO - 23


Description[038 B I

When LIN02 is code "SV," PID05may carry an additional free-formdescription of the DoD contracted

services, if necessary. It mayalso be used for an explanation of

a contract condition, in lieu ofusing the 'NTE' segment.


856.002003.DoDO - 24 911220


Segment: MEA MeasurementsTable: B


Max Use: 40Loop: 0

Purpose: To specify physical measurements, includingdimensions, tolerances, weights and counts.

Comment: A. When citing dimensional tolerances, anymeasurement requiring a sign (+ or -),or any measurement where a positive(+) value cannot be assumed use

MEA05 as the negative (-) value andMEA06 as the positive (+) value.

Syntax Notes: 01 If MEA07 is used MEA03 is required.

02 Either MEA08 or MEA03 may be used,but not both.

03 Either MEA03 or MEA05 or MEA06 orMEA08 is required.

04 If either MEA03, MEA05 or MEA06 isused, MEA04 is required.

Data Element SummaryRef. Data

De. Element Name Attributes

MEA01 737 Measurement Reference ID Code 0 ID 2/2Code specifying the application of physical measure-ment cited.

Measurement Reference IDCode

[039 B *1

For all DCMC-administered con-tracts and FMS/MAP shipments ex-

cept contracts containing the'Fast Pay' clause. Code Definition

WT Weights

MEA02 738 Measurement Qualifier 0 ID 1/3Code identifying the type of measurement.

911220 856.002003.DoDO - 25


Measurement Qualifier1040 B *1

See block 16, DD Form 250, forall DCMC-administered contractsexcept those containing the Fast

Pay clause and for FMS/MAP ship-ments. Code Definition

G Gross Weight

MEA03 739 Measurement Value C R 1/10The value of the measurement.

Measurement Value[041 B I

MEA04 355 Unit of Measurement Code C ID 212Code identifying the basic unit measurement.

Unit of Measure Code[042 B *] Code Definition

PG Pounds Gross

MEA05 740 Range Minimum C R 1/10

MEA06 741 Range Maximum C R 1110

MEA07 935 Measurement Significance Code 0 ID 2/2

MEA08 936 Measurement Attribute Code C ID 2/2

MEA09 752 Surface/Layer/Position Code 0 ID 2/2

856.002003.DoDO - 26 911220


Segment: PWK PaperworkTable: B


Max Use: 25Loop: 0

Purpose: To specify the type and transmission ofpaperwork relating to product or order.

Comment: A. PWK05 and PWK06 may be used toidentify the addressee by a code number.

B. PWK07 may be used to indicate specialinformation to be shown on the specifiedreport.

Syntax Notes: 01 If either PWK05 or PWK06 is present,then the other is required.


PWK01 755 Report Type Code M ID 2/2Code indicating the title and/or contents of a docu-ment or report.

Report Type Code[043 B *1

Use when additional paperworkwill have to accompany the ship-

ment, or will have to follow underseparate cover. Code Definition

MR Material Inspection and Receiving ReportSN Shipping Notice

PWK02 756 Report Transmission Code M ID 2/2Code defining timing and transmission method bywhich reports are to be sent.

Report Transaction Code[044 B I

PWK03 757 Report Copies Needed 0 NO 1/2The number of copies of a report that should be sentto the addressee.

Report Copies Needed[045 B I

PWK04 98 Entity Identifier Code 0 ID 2/2

911220 856.002003.DoDO - 27

DEPARTMENT OF DEFENSEIMPLEMENTATION OUIDELNES

Code identifying an organizational entity or a physi-cal location.

Entity ID Code[046 B *] Code Definition

PG Prime Contractor

PWK05 66 Identification Code Qualifier C ID 1/2Code designating the system/method of code struc-ture used for Identification Code (67).

ID Code Qualifier(047 B *] Code Definition

33 Commercial Contractor and Govt. Entity Code

PWK06 67 Identification Code C ID 2/17Code identifying a party.

Identification Code[048 B I

PWK07 352 Description 0 AN 1/80A free-form description to clarify the related data ele-ments and their content.

Description1049 B I

856.002003.Do00 - 28 911220


Segment: PKG Marking, Packaging, Loading


Usage: 0Max Use: 25

Loop: 0Purpose: To describe marking, packaging, loading

and unloading requirements.




D. Special marking or tagging data can begiven in PKG05 (Description).

Syntax Notes: 01 If PKG03 is present, then PKGO4 is re-quired.

02 At least one of PKG04 or PKGO5 mustbe present.




Item Description Code[050 B * Code Definition

F Free Form

PKG02 753 Packaging Characteristic Code 0 ID 1/5Code specifying the marking, packaging, loadingand related characteristics being described.


[051 B I

PKG03 348 Item Description Qualifier 0 ID 2/2Code identifying agency responsible for the codeused.

911220 856.002003.DoDO - 29


Item Description Qualifier[052 B I

PKGO4 754 Packaging Description Code C ID 1/7A code from an industry code list which providesspecific data about the marking, packaging or load-ing and unloading of a product. Also see: ItemDescription Qualifier (348).

Packaging Description Code[053 B I

PKGO5 352 Description C AN 1/80A free-form description to clarify the related data ele-ments and their content.

Description[054 B I

856.002003.DoDO - 30 911220


Segment: TD1 Carrier Details (Quantity andWeight)


Usage: 0Max Use: 20

Loop: 0Purpose: To specify the transportation details relative

to commodity, weight and quantity.Syntax Notes: 01 If TD101 is present, then TD102 is re-

quired.

02 If TD103 is present, then TDI04 is re-quired.

03 If TD106 is present, then TD107, andTD108 are required.


TD101 103 Packaging Code 0 ID 5/5Code identifying the type of packaging. Part 1.Packaging form. Part 2. Packaging Material.

Packaging Code[055 B I

TD102 80 Lading Quantity C NO 1/7Number of units (pieces) of the lading commodity.Also see: Unit of Measurement Code (355.)

Lading Quantity[056 B I

This segment carries the total num-ber of shipping containers.

TD103 23 Commodity Code Qualifier 0 ID 1/1Code identifying the commodity coding system usedfor Commodity Code.

Commodity Code Qualifier[057 B I

TD104 22 Commodity Code C ID 1/10Code describing a commodity or group of com-modities. See Data Element 23.

Commodity Code1058 B I

911220 856.002003.DoDO - 31


TD105 79 Lading Description 0 AN 1/25Description of an item as required for rating and bill-ing purposes.

Lading Description[059 B I

TD106 187 Weight Qualifier 0 ID 112Code defining the type of weight.

Weight Qualifier[060 B I

TD107 81 Weight C R 1/8Numeric value of weight. Also see: WeightQualifier (187), Weight Unit Qualifier (188), Unit ofMeasurement Code (355.)

Weight1061 B I

TD108 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit measurement.


856.002003.DoDO - 32 911220


Segment: TD5 Carrier Details (Routing Se-quence/Transit Time)

Table: B


Max Use: 12Loop: 0

Purpose: To specify the carrier, sequence of routingand to provide transit time information

Comment: A. When specifying a routing sequence tobe used for the shipment movement inlieu of specifying each carrier within themovement: use TD502 to identify theparty responsible for defining the routingsequence; use TD503 to identify the ac-tual routing sequence, specified by theparty identified in TD502.

Syntax Notes: 01 At least one of TD502, TD504, orTD505 must be present.




Data Element SummaryRef. DataDes. Eement Name Attribute

TD501 133 Routing Sequence Code 0 ID 1/2Code describing the relationship of a carrier to aspecific shipment movement.

Routing Sequence Code[063 B I

TD502 66 Identification Code Qualifier C ID 1/2Code designating the system/method of code struc-ture used for Identification Code (67).

ID Code Qualifier[064 B ] Code Definition

M2 Contractor and Government Entity Code (CAGE)

911220 856.002003.DoDo - 33


TD503 67 Identification Code C ID 2/17Code identifying a party.

Identification Code[065 B I

TD504 91 Transportation Method Code C ID 112Code specifying the method of transportation forthe shipment.

Transportation Method Code[066 B °1

Codes found in DFARS Appendix I-302 must be converted into cor-responding ANSI codes for dataelement 91. At least 7 DFARScodes (6, 7, U, D, R, T, and N)

do not have equivalents in ANSI.These codes were added as codes

6, 7, AQ, DW. ED, FA, and LA.Code "ZZ* is defined as 'not ap-

plicable for this transaction.' Code Definition

A AirAC Air CharterAE Air ExpressAQ Quicktrans*B BargeBU BusC ConsolidationCE Customer Pickup/Customer's Expense0 Parcel Post01 6 Military Official Mail (MOM)*002 7 Express Ma'l*D03 DW Driveaway, Truckaway, Towawey*004 ED European Distribution System/PacificD05 FA Air Freight Forwarder'D06 LA Logairg007 RC Rail. Less than Carload COFC*DOS Y Military Intratheater Airlift Service*E Expedited TruckH Customer PickupI Common Irregular CarderJ Motor

L Contract CarrerLT Less Than Trailer Load (LT)0 Containerized OceanP Private Carriera Conventional OceanR RailS OceanSR Supplier TruckT Best Way (Shippers Options)U Private Parcel ServiceW Inland WaterwayX Intermodal (Piggyback)ZZ Mutually Defined

Se.002003.DoDO - 34 911220


TD505 387 Routing C AN 1/35Free-form description of the routing or requestedrouting for shipment, or the originating carrier'sidentity.

Routing[067 B I

TD506 368 Shipment/Order Status Code 0 ID 2/2Code indicating the status of an order or shipment.

Ship/Order Status Code[068 B °] Code Definition

DO1 Component Missing'D02 Missing Components Furnished*D03 Quantity Increase*D04 Quantity Decrease*D05 Replacement Shipment*D06 Shipped and Held in Bond at KRT's Plant*D07 Shipped and Held as GFP"DO8 Shipped or Performed as Indicated'DO9 Underrun Quantity*

TD507 309 Location Qualifier 0 ID 1/2Code identifying type of Location Identifier (310)used.

Location Qualifier[069 B I

TD508 310 Location Identifier C AN 1/25Code which identifies a specific geographic location.

Location Identification[070 B I

TD509 731 Transit Direction Code 0 ID 2/2The point of origin and point of direction.

Transit Direct Code[071 B I

TD510 732 Transit Time Direction Qualifier 0 ID 2/2Code specifying the value of time used to measurethe transit time.

Transit Time Direct Qualifier[072 B I

TD511 733 Transit Time C R 1/4The numeric amount of transit time.

Transit Time[073 B I

911220 856.002003.DoDO - 35


Segment: TD3 Carrier Details (Equipment)


Usage: 0Max Use: 12

Loop: 0

Purpose: To specify transportation details relating tothe equipment used by the carrier.

Syntax Notes: 01 If TD302 is present, then TD303 is re-quired.

02 If TD304 is present, then TD305 andTD306 are required.


TD301 40 Equipment Description Code M ID 2/2Code identifying type of equipment used for ship-ment.

Equipment Description Code[074 B I

TD302 206 Equipment Initial 0 AN 1/4Prefix or alpha part of an equipment unit's identify-ing number.

Equipment Initial[075 B I

TD303 207 Equipment Number C AN 1/10Sequencing or serial part of an equipment unit's iden-tifying number (pure numeric form for equipmentnumber is preferred).

Equipment Number[076 B I

TD304 187 Weight Qualifier 0 ID 1/2Code defining the type of weight.

Weight Qualifier[077 B 1

TD305 81 Weight C R 1/8Numeric value of weight. Also see: WeightQualifier (187), Weight Unit Qualifier (188), Unit ofMeasurement Code (355.)

Weight[078 B 1

856.002003.DoDO - 36 911220


TD306 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit measurement.

Unit of Measure Code[079 BI

See comment SN1O3.

TD307 102 Ownership Code 0 ID 1/1Code indicating the relationship of equipment to car-rier.

Ownership Code[080 BI

911 220 856.002003.DcDO - 37

DEPARTMENT OF DBENSEIMPLEMENTATION GUIDEUNES

Segment: TD4 Carrier Details (Special Han-dling/Hazardous Materials)

Table: B


Max Use: 5Loop: 0

Purpose: To specify transportation special handling re-quirements and hazardous materials informa-tion

Syntax Notes: 01 At least one of TD401 or TD404 mustbe present.


Data Element SummaryRef. DataDee. Eement Name Attrbutes

TD401 152 Special Handling Code C ID 2/3Code specifying special transportation handling in-structions.

Special Handling Code[081 B °1 Code Definition

DO1 Environment Control Urnits*

TD402 208 Hazardous Material Code 0 ID 1/1QualifierCode which qualifies the Hazardous Material ClassCode (209).

Hazardous Material CodeQualifier

[082 B I

TD403 209 Hazardous Material Class Code C ID 2/4Code specifying the kind of hazard for a material.(Code source specified in code set for DE208)

Hazardous Material Class1083 B I

TD404 352 Description C AN 1/80A free-form description to clarify the related data ele-ments and their content.

Description[084 B I

856.002003.DoDO - 38 911220



Sequence: 22


Loop: 0






Reference Number Qualifier[085 B *]

A. Code 'BL" is for the GBL.Code 'BM" is for the commercialbill of lading number. B. When

code 'TG' is used, also use codeDO1 in segment REF to indicatethat a TCN is assigned to each

line item. Code DefinitionBL Government Bill of LadingBM Bill of Lading NumberDO1 Overflow, Additional, or Supplementary

Number*D02 Terminal Release Order Number'D03 MIPR Number*D04 AERNO Number*MA Ship NoticelManifest NumberSl Shipper's Identifying Number for ShipmentTG Transportation Control Number (TCN)


Reference Number[086 B I


Description[087 B I

911220 856.002003.DODO - 39


Segment: MAN Marks and NumbersTable: B


Max Use: 10Loop: 0




Marks and Numbers Qualifier[088 B I


Marks and Number[089 B I

Use to carry additional 'mark for"data that cannot be carried in the

N1-N4 segments.

856.002003.DoDO - 40 911220

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDE.IES

Segment: N1 Name


Usage: 0

Max Use: 1Loop: 0







Entity ID Code[090 B "]

A. Use code 'SF" when: 1. Dif-ferent from the Prime Contractor,

code 'PG.' 2. Performance ofservicefitems does not require

delivery of items upon completionof services; delivery covers perfor-

mance at multiple locations. Ifsame as Prime Contractor, do not

transmit the segment. B. Usecode '33* when different than

'Ship To" address. Use N2-N4 toexpand information. "MAN' maybe used to augment "mark for.' Code Definition

001 31 Administered By*D02 33 Mark For"PG Prime ContractorPN Party to Receive Shipment NoticePR Payer (Payment By)SF Ship FromST Ship To

911220 856.002003.DoDO - 41



Name[091 B I

N103 66 Identificatior Code Qualifier C ID 112Code designating the system/method of code struc-ture used for Identification Code (67).

ID Code Qualifier[092 B °]

When N101 is code '31," '33,''ST,* or 'TO,' use code "10."

When N101 is code "FR,' 'PG,'or 'SF," use code "M2." Code Definition

10 Department of Defense Activity Address CodeD01 M2 Contractor and Government Entity Code*D02 Military Assistance Program Address Code*D03 Receiver's Code*

N104 67 Identification Code C ID 2/17

Code identifying a party.ID Code

[093 B I

856.002003.DoDO - 42 911220

DEPARTMENT OF DEFENSEIMPLEMENTAiON GUIDELINES



Usage: 0Max Use: 2

Loop: 0Purpose: To specify additional names or those longer

than 35 characters in length



Name[094 B I


Name[095 BI

911220O 856.002003.DoDO - 43

DEPARTMENT OF DEFISEIMPLEMENTATION GUIDELNES

Segment: N3 Address InformationTable: B


Max Use: 2Loop: 0




Address[096 B I

N302 166 Address Information 0 AN 1135Free-form field for address information.

Address[097 B I

856.002003.DoD0 - 44 911220

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDE.INES



Usage: 0Max Use: 1

Loop: 0









City Name[099 B I

N402 156 State or Province Code C ID 212Code (Standard State/Province) defmed by ap-propriate governmental agencies.

State/Province Code1100 B I


Postal Code[101 B I


Country Code(102 B 1

911220 856.002003.DoDO - 45



Location Qualifier[103 B I


Location Identifier[104B

856.002003.DoD0 - 46 911220




Usage: 0Max Use: 3

Loop: 0


Comment: A. This segment is used to specify who isto be contacted on various conditions re-lated to the transaction. The term -Com-munications" in the title and purposerelates to interpersonal communications,not network or telecommunications con-tacts.



PER01 366 Contact Function Code M ID 212Code identifying the major duty or responsibility ofthe person or group named.

Contact Function Code[105 B "] Code Definition



Name[106 B I


911220 856.002003.DoDO - 47



[107 B *1 Code Definition

DOI AU*D02 Defense Data Network (DDN)*EM Electronic MailFX FacsimileIT International TelephonePS Packet SwitchingTE TelephoneTL TelexTM TelemailTX TWX

PER04 364 Communication Number C AN 7/21Complete communication number including countryor area code when applicable. Also see: Com-munication Number Qualifier (365).

Communication Number[108 B I


856.002003.DoDO - 48 911220




Max Use: 1Loop: 0




C. FOBO6 is the code specifying title pas-sage location.


02 If FOB04 is present, then FOBG5 is re-quired.


Data Element SummaryRef, DataDoe. Element Name Attributes



[109 B *1 Code DefinitionDF Defined by the Buyer and Seller


911220 856.002003.DoDO - 49


Location Qualifier[110 B *]

Code 'OR' Origin equates toDFARS code 'S.' and code 'DE'

destination equates to DFARScode "D.' Code Definition

DE DestinationDO1 Or Other*OR OriginPP Pool Point


Description[111 B I





856.002003.DoDO - 50 911220

,,,eK


Segment: SDQ Destination QuantityTable: B


Max Use: 50Loop: 0

Purpose: To specify destination and quantity detail.Comment: A. SDQ02 is used only if different than pre-

viously defined in the transaction set.Syntax Notes: 01 If SDQ05 is present, then SDQ06 must

be present.

02 If SDQ07 is present, then SDQ08 mustbe present.

03 If SDQ09 is present, then SDQIO mustbe present.

04 If SDQ1l is present, then SDQ12 mustbe present.







SDQ01 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit measurement.


See comment SN103. 66 Identification Code Qualifier 0 ID 1/2Code designating the system/method of code struc-ture used for Identification Code (67).

ID Code Qualifier(113B 1 _

911220 856.002003.DoDO - 51


SDQO03 67 Identification Code M ID 2/17Code identifying a party.

ID Code[1141B 1

SDQ04 380 Quantity M R 1/10Numeric value of Quantity. Also see: Unit of Meas-urement Code (355).

Quantity[115B B

Quantity shipped. Use SDQ05through SDQ31 as necessary.

SDQ05 67 Identification Code 0 ID 2/17

SDQ06 380 Quantity C R 1/10





SDQ1 1 67 Identification Code 0 ID 2/17



SDQ14 380 Quantity C R 1110

SDQ1 5 67 Identification Code 0 ID 2/17





SSS.002003.DoDO - 52 911220





911220 856.002003.Daoo - 53


Segment: ITA Allowance, Charge or ServiceTable: B


Max Use: 10Loop: 0

Purpose: To specify allowances, charges or services

Comment: A. ITA12 is the quantity of free goods.

Syntax Notes: 01 If ITA02 is present, then at least one ofITA03, or ITA13 is required.

02 Only one of ITA06, ITA07, or ITA08must be present.

03 If ITA08 is present, then ITA09 is re-quired.

04 If ITAI0 is present, then ITAI 1 is re-quired.

Data Element SummaryRef. DataDe. Bement Name Attribute

ITA01 248 Allowance or Charge Indicator M ID 1/1

Code which indicates an allowance or charge for theservice specified.

Allowance/Charge Indicator[116 B "] Code Definition

N No Allowance or Charge

ITA02 559 Agency Qualifier Code 0 ID 2/2

ITA03 560 Special Services Code C ID 2/10Code identifying the special service.

Special Service Code[117 B *I

This data element describes the ac-ceptance point. When code "IM'is used, acceptance is at destina-

tion. When code '10' is used, ac-ceptance is at origin. Code Definition

IM Inspection at Destination10 Inspection at Origin

856.002003.DoDO - 54 911220


ITA04 331 Allowance or Charge Method of M ID 2/2Handling CodeCode indicating method of habdling for an allowanceor charge.

Method of Handling Code[118 B °1 Code Definition

07 Optional

ITA05 341 Allowance or Charge Number 0 AN 1/16

ITA06 359 Allowance or Charge Rate C R 1/9

ITA07 360 Allowance or Charge Total C N2 1/9Amount

ITA08 378 Allowance/ Charge Percent C ID 1/1

Qualifier

ITA09 332 Allowance or Charge Percent C R 1/6

ITA10 339 Allowance or Charge Quantity 0 R 1/10

ITA11 355 Unit of Measurement Code C ID 2/2

ITA12 380 Quantity 0 R 1/10

ITA13 352 Description C AN 1/80

ITA14 .150 Special Charge Code 0 ID 3/3

911220 e56.002003.DoDO - 55




Max Use: 1Loop: 0






Number of Line Items[119 C I

Total number 'HL' segments.


Hash Total[120C

Hash total of data elementsSN102.



CTO5 183 Volume 0 R 1/8



856.002003.DoDO - 56 911220



Table: C


Max Use: 1Loop: 0

Purpose: To indicate the end of the transaction setand provide the count of the transmitted seg-ments (including the beginning (ST) and end-ding (SE) ... (See X12 Dictionary.)





Number of IncludedSegments1121 C I



[122 C I

911220 856.002003.DoDO - 57


856.002003.DoDO - 58 911220

0 0 C

Or - - 00

C0-

.0.0-0 0

> - O0U- 0~ -

E .c >Z

aioo

0 . E 3.egz

:i21 1111 20 2. c3- 0Q Ow 0s. Z

0 f>A 3 E.2V r aE00 0

0~ C.= o

0. ~o LO 'O 4 )Eu 0 11:Z

.2 0 w x20 E

*- 00 0 0, 1% 0 O=.2 002 0 0 03 0 c0

-6 0 0 00WW 2- -- Efl 7c O

-2 E) - 20 U' -E v OE2e

4c Cl U)ol 0 0 0 0 Uz

It 4 44 444)r mc

.0 00

W U ZU 0 0 01- 1-

0 0

0 0

9 u ?L 0

* C9

.2 .2 0

cc0

91 21 85- I-20- UDoD - 59

E 49

CL V

D E

CL V 0 - -3. 0 .2

0o -D

02 E 0

*t w'E 0

0* 30 C?

0.~A .E.2~0. a0

0 *C3

E 0.0 'a.0

0 0 =.E

. .. . . .. .

0. 0 >0 C L*>E 00 0 CL a U-U.U

.=2 eq C. 0 0

.2. 0 0 x 1. OC

R5 o U) N-~~*

0-o

.CoIn 00 .

000

a.

2''a.'.0 2

sw A0A

9 .0003D O - 0 91121

= 0 .

>eac c -. : c0 .0 = - u i.

'A 0o0 V. 0 o. . C 0: =E

CA- ce -- -'A CL E A

-.0 c

.0 ; -. oz 4i>.~C . -..0>.~C me a ;. 0 ; 6 0

T 'E- - .. 0 0 .C0 0 E E

L0 _Z -2 .

, c0 0 "20 CL IM

r.~ 26c.6 1 EeC E 0rnCa'E a

0-Cs C -.

.2o EE V _0t .C .

muc ID =CCo2 C- E 70 x 0 - a:

oo U)0

* m C.m-(4

z U. Lcc j U 0 IL IL

0 0A S0 a 4N

At ( cc go

V zSS

* .

0 0

91 21 8--0 0 3D D -C1

EE 00.C- - -

ECc

@3lLI .

-" a. @ 3a

.2~.o

= -U) 0 0

I' U ) * i o

w' U-U Ln 0) co co on G n 0 o W r

0 c 0 0o- Q .

to 4t0.ua . *

0

4 1 ! ! • lt I tI

IL 0. IL I I a. I. IL II AI 9I II AI9 9

N -U m) ") U)

m " mm m r I

ID A

0- - eelM a 0 0 0 0 0 0 0 . 00

-6.003DD - -2 91-12-19-

0

f CL

00

0.

E EO4 00

LL 0

z E0

000 C

0 U).0 I - C0 c 0

0 . 0 a) -CL 0. c z o

o:! 3.0 0.0 (9LL 0 00 0 0)wu

S 0Lco ~0E

a~~ 0 C~co*

m m Q~ m 0n I ) 9 o P ) l O l n L

0( ) 0e. U6 0 -w

IL I : it 3 v v ha- LI I L C L 0 I L I . I

a0.e 0 e . m u.

W -CD I D I 0 I D 4 ID ID D 0

ID 0l( -C ( D I

0a. a. a . a . a . a . a . I

00OID ID .2I 0I D I D D I

4~~C ID 0

5_ t t t >' 0 ID S N S 5 0 m4 I

9121 0 0 0 0 o 0 0 000.o -3

ac

CL

.C,

00 E

> 'E

0 E

00

L)

OC ~C4U) m

a C

SUS

400

CL.

o '4 r~d I'- 40 P co (0 o

U.,020.DD - 64 911219U

l* C

CC=2 -

M.0N

*. Vc

00 => .- U:. 0

CL 3 U- -

.. 0

UC Z 0

E c. '2 CI -0aCt

0 ) 0j u

0w - r-YE r? 7

C C

U > C-0 S t 2*;IS0 C C

X E E O= 0 0

i u 9X j cr2: % E0jZ -~ =. -Z

IE0C

0 Un0) 0lb 2 U

91298C020.oO-6

U.-

A!. o

ID 0

C4 VD o. 0

m 5- N r- v 1 4t

E0. 0 0 0 0

m 0* 0 00

000000000.2 .2 00 0

mu0 ~ 0 0 0 - 1 1 0 0 10bo~~~ E- r-N N - 0.- .

0 ~ 4 Z 0 a 0 0 4 -10 U) 1 0 1 r ) (~ ~ * * ~

2 .2- 1 A ax a. . N N N N

*a a a 1 5 a; .a S. a7 ar a a

U) ai - t u u i0 U

856.0203.DoO -66 9121

CC

60 .2EE a-

0 -E

0 0

.00 E cE *E a E -.a a C *

zo 'D z 0r E E,

C > itCz~ E s VIO 2

EE =.0 00-Z Zz~. E >n C E

C -

E 0 > EC ~ U C

0.0 E -- E.2

0- E

ou 0 0 0 0mu Cl 15C - a;4-

- 0 2 2.cc z CL r

WW I o a. 0. X- ('0

laC

4c 00 -0 0 0w l

o~~c mCV000 0 o

; C

W 0U L

N N 0

In co .0 (a a

.0 .0 .0E EE

2 2

Z.z C *0 *0

C C ~

911219 OSS.002003.D.oO - 67

60

V 0

9 L

aa

LL

00

a o

r. S!0

U 6 E

m0.N. ID

> -000

too 4z 0D 0 am to

40 M

aC. 0) m CO) or

M -e U) 0 0 *

om LM uo U-

CL C S

-0000

D ~ ~ o) U c 0 )

- I0 0. 0 0

go zzz IL zzz2a

o 5.003DD - ) 08 0911219 (4 . (4

C 00

,61

C

0. o

OIL)

_L T

*0L 00

U cc E Eo ~ ..

z .2~ C.

F U.0* r. Cl0-

.0 E CO E0~ 0 ~ Og.

U.C~ a0 IDO 0~I-"D .20

Cc c0*- 0 UC 0.

CO 000U

IL I0 .200 0oDIn SN I 00 0 " s .

AI 4 0 In In z E 4 ( 0 I

-. t 0 4r 00 0 0 0 -

a0 0 ) L 0 N) w * fa 0 o v o A

co m m 0 0 m ev An m * m a 0o

0 0 a I I

U U U IA5 U 0 0 00

LD U 0 o D I- a) 0 d C4 N0) V) V) C., m~ tv) V) m- V) m~ It9-

Z E

*U0 *e .

0 US-

00

2* aI 000CE -

0 U E 5

za z .*0 In .. CL0( n

911219 856.002003.D@oO - 69

856.002003.DoDO - 70 911219


IMPLEMENTATION GUIDEUNES

10.7.61 DoD Convention for Using the 861 Receiving Ad-viceThis section provides the format and establishes the data contentsof the DoD 861 Transaction Set Convention. The receivingadvice transaction set provides for customary and establishedbusiness and industry practice relative to the notification of areceipt of goods and services.




10.7.61.4 Code List Not Maintained By ASC X1 2See Section 10.4




910909 861.002003.DoDO - Cover


861.002003.DoDO - Cover 910909


ASC X12.12 Transaction Set 861Receiving Advice (Version 002003)

Segment Hierarchy




USE BRA Beginning Segment for Receiving Advice M 1


CUR Currency 0 1



USE DTM Date/Time Reference M 10

USE PRF Purchase Order Reference 0 25














USE RCD Receiving Conditions 0 1 RCD\200000

USE SNI Item Detail (Shipment) 0 1

CUR Currency 0 1

USE UN Item Identification Detail 0 100





911220 861.O02003.DoDO - 1

DEPARTMENT OF DBNSEIMPLEMENTATION GUIDBJNES




PRF Purchase Order Reference 0 25



NI Name 0 1 N1\200







TD1 Carrier Details (Quantity and Weight) 0 20TD5 Carrier Details (Routing Sequence/Transit 0 12

Time)







USE CTT Transaction Totals 0 1

USE SE Transaction Set Trailer M I

861.002003.DoDO - 2 911220


DoD Model Transaction 861Receiving Advice

Segment Hierarchy




6 BRA Beginning Segment for Receiving Advice M 1




12 DTM Date/Time Reference M 10

13 PRF Purchase Order Reference 0 25

14 N1 Name 0 1 N1\200






19 RCD Receiving Conditions 0 1 RCD\200000

22 SN1 Item Detail (Shipment) 0 1

24 UN Item Identification Detail 0 100



28 C'n Transaction Totals 0 1


911220 861.002003.DoDO - 3

DEPARTMENT OF DEFENSEIMPLEMENTATION GIDELINES

861 .002003.DODO - 4 911220



Sequence: 2Usage: M

Max Use: 1Loop: 0






861 Receiving Advice



[002 A I

911220 861.002003.DoO0 - 5

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDINES

Segment: BRA Beginning Segment for Receiv-ing Advice

Table: A

Sequence: 3Usage: M

Max Use: 1

Loop: 0Purpose: To indicate the beginning of a receiving ad-

vice transaction set and to transmit identify-ing number and date.

Data Element SummaryRef. DataDe. Element Name Attributee

BRA01 127 Reference Number M AN 1/30Reference number or identification number asdefined for a particular Transaction Set, or asspecified by the Reference Number Qualifier. Alsosee Reference Number Qualifier, (128).


BRA01 is the shipper's identifica-tion number (SID).

BRA02 373 Date M DT 6/6Date (YYMMDD).

Date[004 A I

Date received as prescribed inblock 22 of the DD Form 250.

BRA03 353 Transaction Set Purpose Code M ID 2/2Code identifying purpose of transaction set.


[005 A *] Code Definition

00 Original01 Cancellation13 Request (Reply to a Previous Request)14 Advance Notification (Interim Reply)18 Reissue (Corrected Transaction)

BRA04 962 Receiving Advice Type Code M ID 1/1Code specifying type of receiving advice.

861.002003.DoDO - 6 911220


Receiving Advice Type Code[006 A *1 Code Definition

DO1 In Receipt of an Acceptance Alert*D02 Not in Receipt of an Acceptance Alert

911220 861.002003.DoDO - 7



Sequence: 4Usage: F

Max Use: 100Loop: 0





Note Reference Code[007 A °]


Free-Form Message[008 A I

Use when needed to comply withthe 'except as noted' requirementin block 22 of the DD Form 250.

861.002003.DoDO - 8 911220



Table: A

Sequence: 6Usage: 0

Max Use: 12Loop: 0


be present.

Data Element SummaryRet. DataDes. Element Name Attributes


Reference Number Qualifier[009 A *1 Code Definition

BL Government Bill of Lading NumberBN Bill of Lading NumberTG Transportation Control Number (TCN)




911220 961.002003.DoDO - 9

DEPARTMENT OF DEEBNSEIMPLEMENTATION GUIDELNES


Table: ASequence: 7

Usage: 0

Max Use: 3Loop: 0


Comment: A. This segment is used to specify who isto be contacted on various conditions re-lated to the transaction. The term "Com-munications" in the title and purposerelates to interpersonal communications,not network or telecommunications con-tacts.




Contact Number Code[011 A *]


Name[012 A I


861.002003.DoDO - 10 911220



[013 A ]1 Code DefinitionAU AUTOVON001 ON Defense Data Network (DDN)*EM Electronic MailFX FacsirnuleIT International TelephonePS Packet SwitchingTE TelephoneTL TelexTM TelernailTX TWX

PER04 364 Communication Number C AN 7/21Complete communication number including countryor area code when applicable. Also see: Com-munication Number Qualifier (365).

Communication Number[014 AI


911220 861.002003.DoDO - 11



Sequence: 8Usage: M

Max Use: 10Loop: 0


be present.



Date/Time Qualifier[015 A *]

DTM02 373 Date C DT 616Date (YYMMDD).

Date1016A



861.002003.DoDO - 12 911220


Segment: PRF Purchase Order Reference

Table: ASequence: 9

Usage: 0Max Use: 25

Loop: 0

Purpose: To provide reference to a specific purchaseorder


PRF01 324 Purchase Order Number M AN 1/22Identifying number for Purchase Order assigned bythe orderer/purchaser.

Purchase Order Number[017A

PRF02 328 Release Number 0 AN 1/30Number identifying a release against a PurchaseOrder previously placed by the parties involved inthe transaction.


This is the call/order number.

PRF03 327 Change Order Sequence Number 0 AN 1/8Number assigned by the orderer identifying aspecific change or revision to a previously trans-mitted transaction set.


[019A

This is the modification number.

PRF04 323 Purchase Order Date 0 DT 6/6

PRF05 350 Assigned Identification 0 AN 1/6

PRF06 367 Contract Number 0 AN 1/30Contract number.

Contract Number[020 A ]

911220 961.002003.DoDO - 13




Max Use: 1Loop: 0







Entity Code[021 A *]


Name[022 A I


ID Code Qualifier[023 A *J


ID Code[024 A I

861.002003.DoDO - 14 911220


Segment: N2 Additional Name InformationTable: A


Max Use: 2Loop: 0


Data Element SummaryRef. DataDes. Element Name Attributee


Name[025 A I


Name[026 A ]

911220 861.002003.DoDO - 15

DEPARTMENT OF DEFBNSEIMPLEMENTATION GUIDELINES



Max Use: 2Loop: 0




Address[027 A I

N302 166 Address Information 0 AN 1135Free-form field for address information.

Address[028 A I

661.002003.DoDO - 16 911220




Max Use: 1Loop: 0









City Name[029 A I



N403 116 Postal Code 0 ID 519Code defining international postal zone code exclud-ing punctuation and blanks (zip code for UnitedStates).

Postal Code[031 A I


911220 e6.002003.DoDO - 17


Country Code1032 A I

N405 309 Location Qualifier 0 ID 112Code identifying type of Location Identifier (310)used.


N406 310 Location Identifier C AN 1125Code which identifies a specific geographic location.

Location Identifier(034 A ]

961.002003.DoDO - 18 911220


Segment: RCD Receiving ConditionsTable: B

Sequence: 22

Usage: 0

Max Use: 1Loop: 0

Purpose: To report receiving conditions and specifycontested quantities

Comment: A. See the Data Dictionary for a completelist of receiving condition IDs.

B. RCD01 is the receiving advice line itemidentification.

C. RCDO6 through RCD20 provide for five(5) different quantities whose conditionupon receipt is under question.

Syntax Notes: 01 At least one of RCD02, RCDO4, orRCDO6 must be present.

02 If RCDO2 is present, then RCD03 is re-quired.

03 If RCDO4 is present, then RCDO5 is re-quired.

04 If RCDO6 is present, then RCD07, andRCDO8 are required.

05 If RCDO9 is present, then RCDI0, andRCDI l are required.

06 If RCD12 is present, then RCD13, andRCD14 must be present.

07 If RCD15 is present, then RCD16, andRCD17 are required.

08 If RCD18 is present, then RCD19, andRCD20 are required.

911220 861.002003.DoDO - 19



RCDO1 350 Assigned Identification 0 AN 1/6Alphanumeric number assigned for differentiationwithin a transaction set.

Assigned Identification(035 A I

RCD01 carries the CLIN.

RCD02 663 Quantity Units Received C R 119Number of units received.

Quantity of Units Received[036 A I

RCD03 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit measurement.


RCDO4 664 Quantity Units Returned C R 1/9

RCD05 355 Unit of Measurement Code C ID 2/2

RCD06 667 Quantity in Question C R 1/9Number of units contested because of physical condi-tion or status of units.

Quantity in Question[038 A I

RCD07 355 Unit of Measurement Code C ID 2/2Code identifying the basic unit measurement.

Unit of Measure Code(039 A I

DoD uses DoD Manual 500.1 2-Mand some codes are in conflict

with ASC X12 DE355. Use "ZZmutually defined' after agreementwith trading partners for codes in

conflict.RCDO8 412 Receiving Condition Code C ID 2/2

Code designating physical condition or status ofunits received in a specific shipment.

861.002003.DoDO - 20 911220

DEPARTMENT OF DEFENSEIMPLEMENTATiON GUIDELINES

Receiving Condition Code[040 A *1

Data elements RCD09 through

RCD20 are used as required. Code Definition01 Damaged Product or Container02 Quantity Short03 Quantity Over04 Quality Problem05 Incorrect Product06 Good ConditionD01 Documentation Precludes Acceptance*D02 Misdirected*D03 Inadequate Technical Data*D04 Undelivered*

RCDO9 667 Quantity in Question 0 R 1/9

RCD1O 355 Unit of Measurement Code C ID 2/2

RCD11 412 Receiving Condition Code C ID 2/2

RCD12 667 Quantity in Question 0 R 1/9








RCD20 412 Receiving Condition Code C ID 212

911220 861.002003.DoDO - 21


Segment: SN1 Item Detail (Shipment)

Table: B

Sequence: 23

Usage: 0

Max Use: 1Loop: 0

Purpose: To specify line item detail relative to ship-ment

Comment: A. SNIO is the ship notice line item iden-tification (DM Number 268388).

B. SN103 defines the unit of measurementfor both SN102 and SN104.

Syntax Notes: 01 If SN105 is present, then SN106 is re-quired.

Data Element SummaryRef. DataDe. Bement Name Attributes

SN101 350 Assigned Identification 0 AN 1/6Alphanumeric number assigned for differentiationwithin a transaction set.


SN102 382 Number of Units Shipped M R 1/10Numeric value of units shipped in manufacturer'sshipping units for a line item or transaction set.Also see: Unit of Measurement Code (355).

Number of Units Shipped(042 A I

SN103 355 Unit of Measurement Code M ID 2/2Code identifying the basic unit measurement.


DoD uses DoD Manual 5000.12-Mand some codes are in conflict

with ASC X 12 DE355* Use 'ZZmutually defined' after agreementwith trading partners for codes in

conflict.SN104 646 Quantity Shipped to Date 0 R 1/9

SNI05 330 Quantity Ordered 0 R 1/9

861.002003.DoDO - 22 911220


SN 106 355 Unit of Measurement Code C ID 212

SN107 728 Returnable Container Load 0 ID 112Make-Up Code

SN108 668 Line Item Status Code 0 ID 2/2

911220 861 .002003.D*DO - 23


Segment: LIN Item Identification Detail

Table: B


Max Use: 100Loop: 0

Purpose: To specify basic item identification data.


B. LINO is the line item identification(DM Number 266388)

C. LIN02 through LIN31 provide for fif-teen (15) different product/service IDsfor each item. For Example: Case,Color, Drawing No., UPC No., ISBNNo., Model No., SKU.

Syntax Notes: 01 If LIN04 is present, then LIN05 is re-quired.



04 If LIN10 is present, then LINi 1 is re-quired.







861.002003.DoDO - 24 911220









LIN01 is the contract CLIN.


Product/ServiceIdentification Qualifier

[045 A *1 Code DefinitionCN Commodity NameFS Federal Stock Classification and/or NSNPN Company Part Number


Product/Service Identification(046 A I





911220 861.002003.DoDO - 25















LIN21 234 Product/Service ID C AN 1130






861 .002003.DoDO - 26 911220







911220 861 .O02003.DoDO - 27



Sequence: 51

Usage: 0Max Use: 1

Loop: 0Purpose: To transmit a hash total for a specific ele-

ment in the transaction setSyntax Notes: 01 If CTT03 is present, then CTT04 is re-

quired.



cTr01 354 Number of Line Items M NO 1/6Total number of line items in the transaction set.


CTT01 is the accumulation of thenumber of "RCD' segments.





CTTO6 355 Unit of Measurement Code C ID 2/2


861.002003.DoDO - 28 911220



Table: C


Max Use: 1Loop: 0








[049 A I

This is the same number as ap-pears in ST02.

911220 861.002003.DO0 - 29


661.002003.DoOO - 30 911220

E !60L 0

a 0_0 U0 -

* U.

.00

00

* t- CL Q

.! c- 2.2 r.- toEz

S *0. S.C V

:0.0 * W 2 .0> 10 10 -2 c0 r

z 0 1)2- 0 20. > E.F

0 0 E. .2

So. C CLC0

C

0 U .~ Sw 4(w

-N

0 - V 00 00Z> 00 - -- 00 UU o I-

w 4 N f0U a 014 N 4

N m - C - C -)N , 0 0 0 0 0 0 0

0 9 C4 C4 iL . w c

fa U) Uo 2.2ot IxI

IL N N mW m V 0 0 f

A4 4 4 4c 4 4 44

0 V

0 -D

.0 C

z E0 .~ 0

22 U0.c 0 Cc

I) - 0Z I

9122 $0.000 D - 31

UE

z E

00 E

- .2

* OC T5 A=2 0 c

-0 0 0 a0o-C

iU.

>2

0 00 00 - N M C4 N N

-z .

4D~... - - - - --

o~~~ - -. - - - -. .- -. - -

A. A- 00 0 i. A .A

a a

*o E.00

0.0 a0 .0 i C"

z u A 2 WE* zz- <uU

961.0200DO- - 2a112

E EE E c-

- IDN

ix t

*J 0 8w co

0 E c Eo

> 0 c o * -E 00E .3

IL to 0E L8

cc *0 -u * ,a OEo!

00OooZ 0

M 0 0 0 O) P N ) 0n N to0 - U w (a w 0 am w La U(4 0 4) 00 " to " V AM to

N (" o 0 K co N M'Lo 0 8a e 8 89 8 00

52 ! i0 0 00 0 0 . -2Z 2 Z 222 wwww

NS P. N N. ('1 4 ('1 i N C4 N 0 0 oIL- - - .- Of4 4 4 N' ('4 NC 4 ('4

0A0

22 c* u . u .2

C3 'I!USO i- I

C c;p1 .9 C

o 0 00 o * 2E6o . .0 Z.. (C z

911220 361 .002003Da00 - 33

oil

C400

E

CCzU

-.

ft.0

E z

0 CL

a .0

>. U .a

% in q*

0 0 0C

.1 0 U

to. -n U)C1

a -

0. z

C0E E

.000.3

4 z~z

961.00200 01aO.3 91

DEPARTMENT OF DEFMSE

IMPLEMENTATION GUIDWNES

10.7.63 DoD Convention for Using the 863 Report of TestResultsThis section provides the format and establishes the data contentsof the DoD 863 Transaction Set Convention. The report of testresults transaction set can be used to transmit the results of testsperformed to satisfy a specified product or process requirement.This includes, but is not limited to, test data such as inspections,certifications, and statistical process control measurements.







10.7.63.7 863.002003DoD0 Convention

910909 963.002003.DoDO - Cover

DEPARTMENT OF DEFENSEIMPLEMENTATION QUIDELNES

363.002003.DoDO - Cover 910909

DEPARTMENT OF DEMUSEIMPLEMENTATION GUIMr INJES

ASC X12.41 Transaction Set 863Report of Test Results (Version 002003)

Segment Hierarchy




USE BTR Beginning Segment for Test Results M I


USE REF Reference Numbers 0 12USE DTM Date/Time Reference 0 10



USE NI Name 0 1 Nlk20

USE N2 Additional Name Information 0 2USE N3 Address Information 0 2

USE N4 Geographic Location 0 1REF Reference Numbers 0 12



Sao ReqID Name Des Use Loop

USE LIN Item Identification Detail 0 1 LIN1100

PID Product/Item Description 0 1000MEA Measuirements 0 20

DTM Daterrme Reference 0 10REF Reference Numbers 0 1000

USE CC Characteristic/Class ID M 1 CID%200

USE UNT Characteristic/Class ID 0 1

TMD Test Method 0 1PS0 Physical Sample Description 0 > 1SPS Sampling Parameters for Summary 0I

StatisticsMBA Measurements 0 s0



911 220 863.002003.DoDO - I


LX Sequential Number 0 1 LX\1

MEA Measurements 0 1 MEA\1000



STA Statistics 0 1 STA\100






863.002003.DoDO - 2 911220

DEPARTMENT OF DEMESEIMPLEMENTATION GUIDELIES

DoD Model Transaction 863Report of Test Results

Segment Hierarchy




6 BTR Beginning Segment for Test Results M 1


9 REF Reference Numbers 0 1 210 DTM Date/Time Reference 0 10

11 NI Name 0 1 N1\20







19 UIN htem Identification Detail 0 1 LIN\1 00

23 CID Characteristic/Class ID 1CI\0

25 UIT Unit Detail 1


Sag ReqIDName Des Use Loop


911220 863.0020030.DoDO -3


663.0020030.DoDO - 4 911220



Sequence: 1Usage: M

Max Use: 1Loop:





Transaction Set ID Code[001 A ] Code Definition

863 Report of Test Results



[002 A I

911220 863.002003.DoDO - 6


Segment: BTR Beginning Segment for TestResults

Table: ASequence: 2

Usage: MMax Use: 1

Loop:Purpose: To indicate the beginning of a test results

transaction set.Comment: A. If BTR01 equals 01, 02, 03, 04, 05, 18

or 19, then BTRO6 is required to iden-tify the original test report referencenumber transmitted.

B. BTR02 is the date that this transactionset was created by the sending party.

C. BTR03 is the time that this transactionset was created by the sending party.

D. BTRO5 specifies test results report refer-ence number created by the sendingparty.


BTR01 353 Transaction Set Purpose Code M ID 2/2Code identifying purpose of transaction set.


[003 A *I

A. Use code 06 when resultswere acceptable. B. Use code

12 when results were not accept-able. Code Definition

06 Confirmation12 Not Processed

BTR02 373 Date M DT 6/6Date (YYMMDD).

Date[004 A I

BTR03 337 Time 0 TM 4/4

863.002003.DoDO - 6 911220


BTRO4 755 Report Type Code 0 ID 2/2Code indicating the title and/or contents of a docu-ment or report.

Report Type Code[005 A *1 Code Definition

D01 Origin Inspection*002 Origin Acceptance*D03 Origin Inspection and Acceptance*004 Destination Inspection*D05 Destination Acceptance*D06 Destination Inspection and Acceptance*

BTR05 127 Reference Number 0 AN 1/30

BTR06 127 Reference Number 0 AN 1/30

911220 863.002003.DoDO - 7



Sequence: 10Usage: F

Max Use: 100Loop:





Note Reference Code[006 A *] Code Definition

GEN Entire Transaction Set


Free-Form Message[007 A )

Use when needed to comply withthe "except as noted' requirementin Block 21 of the DD Form 250.

U3.002003.DoDO - 8 911220

DEPARTMENT OF DEFI SEIMPLEMENTATION GUIDELINES



Max Use: 12

Loop:Purpose: To transmit identifying numbers




Reference Number Qualifier[008 A °1 Code Definition

BL Government Bill of Lading NumberCO Customer Order NumberCT Contract NumberSI Shipper's ID Number for Shipment (SID)TG Transportation Control Number (TCN)



REF03 352 Description C AN 1180

911220 863.002003.DoDO - 9




Max Use: 10Loop:


be present.




011 Shipped097 Transaction Creation


Date[011 A I



863.002003.DoDO - 10 911220

DEPARTMENT OF DEFINSEIMPLEMENTATION GUIDELINES


Sequence: 60

Usage: 0

Max Use: 1Loop: N1







Entity ID Code[012 A *] Code Definition

DO1 31 Administered By*PA Party to Receive Inspection ReportPG Prime Contractor

ST Ship To

N102 93 Name C AN 1135Free form name.

Name1013 A I


911220 863.002003.DoDO - 11

DEPARTMENT OF DEFENSEIMPLEMENTATION GuiDELINES

ID Code Qualifier[014 A *1

When N101 is code DOI or PA,use code 10. When N101 is codeST, use code 10, DO1, or D02 as

appropriate. When N101 is codePG, use code D02. Code Definition

10 Department of Defense Activity Address CodeD01 M1 Military Assistance Program Address*D02 M2 Contractor end Government Entity Code*

N104 67 Identification Code C ID 2/17

Code identifying a party.ID Code

[015A

863.002003.DoDO - 12 911220



Table: A


Max Use: 2Loop:




Name[016 A I


Name[017 A I

911220 863.002003.DoDO - 13




Max Use: 2Loop:




Address[018 A I


Address[019A

863.002003.DOO - 14 911220




Usage: 0

Max Use: 1Loop:








N401 19 City Name C AN 2/19

Free-form text for city name.City Name[020 A I

N402 156 State or Province Code C ID 212Code (Standard State/Province) defined by ap-propriate governmental agencies.



Postal Code[022 A ]


911220 303.002003.DoDO - 15

DEPARTMENT OF DEFIESEIMPLEMENTATION GUIDELNES





Location Identifier[025 A I

863.002003.DoDO - 16 911220



Table: A


Max Use: 3Loop:







Contact Function Code[026 A ] Code Definition

QA Quality Assurance Contact


Name1027 A I


911220 863.002003.DOO - 17

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIELENES


[028 A *1 Code Def initionAU AUTOVONDOI DN Defense Data Network*EM Electronic MailFX FacsimileIT International TelephonePS Packet SwitchingTE TelephoneTL TelexTM TelemnailTX TWX

PER04 364 Communication Number C AN 7121Complete communications number including countryor area code when applicable. Also see: Com-munications Number Qualifier (365).



863.002003.DaoO - 18 911220


Segment: LIN Item Identification DetailTable: B


Max Use: 1Loop: LIN

Purpose: To specify basic item identification data.Comment: A. See the Data Dictionary for a complete

list of IDs.

B. LNO is the line item identification(DM Number 266388)

C. LIN02 through UN31 provide for fif-teen (15) different product/service IDsfor each item. For Example: Case,Color, Drawing No., UPC No., ISBNNo., Model No., SKU.

Syntax Notes: 01 If LIN04 is present, then LIN05 is re-quired.



04 If LIN10 is present, then LINIl is re-quired.



07 If IJN16 is present, then LINI7 is re-quired.

08 If LINIS is present, then LIN19 is re-quired.



911220 863.002003.DoOO - 19

DEPARTMENT OF DEBIiSEIMPLEMENTATION GUIDELINES









Product/ServiceIdentification Qualifier

[031 A *1 Code DefinitionCN Commodity NameFS Federal Stock Classification and/or NSNPN Company Part Number


Product/Service Identification[032 A I

LIN04 through LIN31 can be usedas appropriate.





863.002003.DoDO - 20 911220

DEPARTMENT OF DEFENSEIMPLEMENTATION GUID.NES




















911220 863.002003.DoDO - 21







S63.002003.DoDO - 22 911220

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDIUNES

Segment: CID Characteristic/Class IDTable: B


Max Use: 1Loop: CID

Purpose: To specify the general class or specific char-acteristic on which test results are beingreported.

Syntax Notes: 01 If CID03 or CID04 is used the other isrequired.

02 Either CID01 or CID02 or CID04 is re-quired.


CID01 738 Measurement Qualifier C ID 1/3Code identifying the type of measurement.

Measurement Qualifier[033 A I

CID02 750 Product Characteristic Code C ID 2/3Code specifying the product characteristic beingdescribed.

Product/ProcessCharacteristic Code

[034 A ° Code Definition08 ProductDO1 Service"

CID03 348 Item Description Qualifier C ID 2/2Code identifying agency responsible for the codeused.

Item Description Qualifier(035 A I

CID04 751 Product Description Code C ID 1/12A code from an industry code list which providesspecific data about a product characteristic. Alsosee: Item Description Qualifier (348).

Product Description Code[036 A 1

911220 863.002003.DoDO - 23


CID05 352 Description 0 AN 1180A free-form description to clarify the related data ele-ments and their content.

Description[037 AI

663.002003.DoDO - 24 911I220

DEPARTMENT OF DEMUSEIMPLEMENTATION OUIDEMES

Segment: UIT Unit DetailTable: B


Max Use: 1Loop:

Purpose: To specify item unit data


UIT0l 355 Unit of Measure Code M ID 2/2Code identifyig the basic unit measurement.


The DoD uses DoD Manual5000.1 2-M and some codes con-

flict with ASC X1 2 DE355. Afteragreement with your trading

partner on conflicting codes, use'ZZ mutually defined.'

UITO2 212 Unit Price C R 1/4

UITO3 639 Basis Unit Price Code 0 ID 2/2

911 220 863.002003.DoDO - 25

DEPARTMENT OF DEENSEIMPLEMENTATION GUIDEJNES


Table: C


Max Use: 1Loop:








[040 A I

This is the same number as ap-pears in ST02.

S63.002003.DoO0 - 26 911220

ID x00

0=CLIOD LL

CLC '

0 .0 .

.0 r-0c_ ,S

U.C : .2 .

- 22>.o 0L .2 = .

-. ~ E0 .0 a0 0L o.. .5<E E c

0 j0.

SL CL C c --' 10 O * 2 01 E

0 2**. 40 t. -0 0~Ca 0 E O 0

E - O*a 0 CL

0 c Cl a CL~a -*

CU. - U . 0B~ .i a5a C C o~ 070

0 o 0 0000 I- CO UEg 00 .00C00 V

w P. in .ES. co (* C4'-PM. m- N'a. a.mC r

C4 It C4 - 0C4 .4

40 40. 00 2

N0 * 0 0 U7 0 0 0 r-04o 0 0 t 0 0 U LL 40

Cl0 0 0 0 Cl 0 0 -C4 N. C4C 4 9) V 40 0o

4c 4c 4c 440 4C -C 0 0

49 A( 4 44 44 44 4 4

w- ~I'1 I S - S 0 0 '

*E

2 U6 OZ

E EU) 0 )

* 0 L Z 0

.o .2 ID

z EE L3

a. c

a ~ I Z U. 011c a 0 L

911220 $63.002003DoD0 -27

£0V

-o

0 IL

as 0

D200E oe

Ea . 0>U V

o~c .2 0

40 CL00(: 0~ )2z cI0C. * * 0 - 0

E z 0 20. >0 0 E

1Zc

CL4 Z

4~~~~L I0 LOX .wa

-00 n 4wun..a.iii-I

ao oo omg 0g

M 00" "000

le a 2 2 2 2 2 Z Z 2 zZ 2 IL A. 0.. 0. M.

0 00% r 0 0 - -

0 0% 0 0 0 N A 0M

go - -D

4 4 4 4 4444 4 4 4 44 4

LL 00

0 E c14 0

I- E E 2E

0 a -

a LO z z cL 2 2

863.OO2003DODO - 28 9112

ID90 0o *'i

N = .0S E-

0.0

'.

W 'S

0' 0 O

> U -. AL0

3 z Cu 0-1 *-= uw S

r C

- or

0zD c

E!~Ee6 C

4 Cuu~a. c

91z2 8z 0 02000 oD2-2

S63.002003DoD0 - 30 311220


IMPLEMENTATION GUIDEUNES

10.7.97 DoD Convention for Using the 997 FunctionalAcknowledgmentThis section provides the format and establishes the data contentsof the DoD 997 Transaction Set Convention. The functionalacknowledgment transaction set defines the control structures fora set of acknowledgments to indicate the results of the syntacticalanalysis of the electronic transmission. The analysis does notcover the semantic meaning of the information.








910909 997.002003.DoDO - Cover


997.002003.DoDO - Cover 910909


ASC X12.20 Transaction Set 997Functional Acknowledgment (Version 002003)

Segment Hierarchy




USE AKI Functional Group Response Header M 1

USE AK2 Transaction Set Response Header 0 1 AK2\999999

USE AK3 Data Segment Note 0 1 AK3\999999

USE AK4 Data Element Note 0 99

USE AK5 Transaction Set Response Trailer 0 1

USE AK9 Functional Group Response Trailer M 1


911223 997.002003.DoDO - 1

DEPARTMENT OF DEISEIMPLEMENTATION GUIDELINES

997.002003.DoDO - 2 911223

DEPARTMENT OF DEMUSEIMPLEMENTATION GUIDELINES

DoD Model Transaction Set 997Functional Acknowledgment

Segment Hierarchy




6 AKi Functional Group Response Header M 1

7 AK2 Transaction Set Response Header 0 1 AK2k999999

a AK3 Data Segment Note 0 1 AK3k999999

10 AK4 Data Element Note 0 99

11 AK5 Transaction Set Response Trailer 0 1

13 AK9 Functional Group Response Trailer M 1


911223 997.002003.DoDO - 3

DEPARTMENT OF DEFENSEIMPLEMENTATION GUIDEUINES

fl7.002003.DoOO - 4 911223


Segment: ST Transaction Set HeaderTable: X

Sequence: 2Usage: M

Max Use: 1Loop: 0


Comment: A. The transaction set identifier (STOI) isintended for use by the translationroutines of the interchange partners toselect the appropriate transaction setdefinition (e.g., 810 selects the invoicetransaction set).


Required ST01 143 Transaction Set Identifier Code M ID 3/3Code uniquely identifying a Transaction Set.

Transaction Set ID Code[001 A *] < Code Definition

997 X12.20 Functional Acknowledgment

ST02 329 Transaction Set Control Number M AN 419Identifying control number assigned by the originatorfor a Transaction Set. Also see: Data InterchangeControl Number (28.)

Transaction Set Controlf002 A I

911217 997.002003.DoDO - 5

DEPARTMENT OF DWEiSEIMPLEMENTATION GUIDENES

Segment: AKI Functional Group ResponseHeader

Table: X

Sequence: 3

Usage: M

Max Use: 1Loop: 0

Purpose: To start acknowledgment of a functionalgroup.

Comment: A. AK102 is the data interchange controlnumber found in the GS segment in thefunctional group being acknowledged.


AK101 479 Functional Identifier Code M ID 2/2Code identifying a group of application related Trans-action Sets.

Functional ID Code[003 A I

This is the functional group ID ofthe group that is being acknowl-edged, e.g., if a Purchase Order

group is being acknowledged, thevalue would be PO from GS01 in

the original transmission.

AK102 28 Data Interchange Control Number M NO 119Assigned number originated and maintained by thesender.

Group Control Number[004 A I

Control number assigned to theoriginal group transmission. GS08

in the original transmission.

997.002003.DoDO - 6 911217


Segment: AK2 Transaction Set Response Header

Table: X

Sequence: 4

Usage: 0

Max Use: 1Loop: AK2

Purpose: To start acknowledgment of a single transac-tion set.

Comment: A. AK202 is the transaction set control num-ber found in the ST segment in the trans-action set being acknowledged.


AK201 143 Transaction Set Identifier Code M ID 3/3Code uniquely identifying a Transaction Set.

Transaction Set ID Code[005 A I

This is the transaction set ID ofthe transaction being acknowl-

edged, e.g., Purchase order wouldbe "850." ST01 in the original

transmission.

AK202 329 Transaction Set Control Number M AN 4/9Identifying control number assigned by the originatorfor a Transaction Set. Also see: Data InterchangeControl Number (28.)


[006 A I

This is the control number as-signed to the transaction set being

acknowledged. ST02 in theoriginal transmission.

911217 997.002003.DoDO - 7

DEPARTMENT OF DWENSEIMPLEMENTATION GUIDEJNES

Segment: AK3 Data Segment NoteTable: X

Sequence: 5Usage: 0

Max Use: 1Loop: AK3

Purpose: To report errors in a data segment and toidentify the location of the data segment.


AK301 721 Segment ID Code M ID 2/3Code defining the segment ID of the data segment inerror. See Segment Directory.

Segment ID Code[007 A I

AK302 719 Segment Position in Transaction M NO 1/6SetThe numerical count position of this data segmentfrom the start of the transaction set: the transactionset header is count position 1.

Segment Position inTransaction Set

[008 A I

AK303 447 Loop Identifier Code 0 ID 1/4Code identifying loop within the transaction setwhich is bounded by the related "LS" and "LE" seg-ments (corresponding "LS" and "LE" segments musthave the same value for Loop Identifier). (See X12Dictionary.)

Loop ID Code[009 A I

AK304 720 Segment Syntax Error Code 0 ID 113Code indicating error found based on the syntax edit-ing of a segment.

Segment Syntax Error Code[010 A °1 Code Definition

1 Unrecognized Segment ID2 Unexpected Segment3 Mandatory Segment Missing

AK305 720 Segment Syntax Error Code 0 ID 1/3Code indicating error found based on the syntax edit-ing of a segment.

997.002003.DoDO - 8 911217

DEPARTMENT OF DEENSEIMPLEMENTATION GUIDELNES

Segment Syntax Error Code[011 A I

The code values for AK304 willbe the same for the remaining

data element 720.AK306 720 Segment Syntax Error Code 0 ID 113

Code indicating error found based on the syntax edit-ing of a segment.

Segment Syntax Error Code[012A


Segment Syntax Error Code[013 A I


Segment Syntax Error Code[014A

911217 997.002003.DoDO - 9


Segment: AK4 Data Element NoteTable: X

Sequence: 6Usage: 0

Max Use: 99Loop: 0

Purpose: To report errors in a data element and toidentify the location of the data element.

Data Element SummaryRef. DataDes. lement Name Attribute.

AK401 722 Element Position in Segment M NO 1/2This is used to indicate the relative position of thedata element in error in this data segment. The countstarts with 1 for the data element immediately follow-ing the segment ID. This value is 0 for an error inthe segment ID.

Element Position in Segment1015 A I

AK402 725 Data Element Reference Number 0 NO 1/4This is the reference number used to locate the dataelement in the dictionary.

Data Element ReferenceNumber

[016 A I

AK403 723 Data Element Syntax Error Code M ID 1/3Code indicating the error found after syntax edits ofa data element.

Data Element Syntax ErrorCode

[017 A *1 Code Definition1 Mandatory Data Element Missing

2 Conditional Required Data Bement Missing3 Too Many Elements4 Data Element Too Short5 Data Element Too Long6 Invalid Character in Data Element7 Invalid Code Value

AK404 724 Copy of Bad Data Element 0 AN 1199This is a copy of the data element in error.

Copy of Bad Data Element[018A

997.002003.DoO0 - 10 911217


Segment: AK5 Transaction Set Response Trailer

Table: XSequence: 7

Usage: 0Max Use: 1

Loop: 0Purpose: To acknowledge acceptance or rejection and

to report errors in a transaction set.


AK501 717 Transaction Set M ID 1/1Acknowledgment CodeCode indicating accept or reject condition based onthe syntax editing of the transaction set.

Transaction SetAcknowlegment Code

[019 A *] Code DefinitionA AcceptedE Accepted but Errors Were NotedR Rejected

AK502 718 Transaction Set Syntax Error 0 ID 1/3CodeCode indicating error found based on the syntax edit-ing of a transaction set.

Transaction Set Note Code[020 A *] Code Definition

1 Transaction Set (TS) Not Supported2 Transaction Set Trailer Missing3 TS Crtl. No. in Header & Trailer Do Not Match4 Number of Included Sag. Does Not Match

Actual5 One or More Segments in Error

AK503 718 Transaction Set Syntax Error 0 ID 113CodeCode indicating error found based on the syntax edit-ing of a transaction set.

Transaction Set Note Code1021 A I

Codes values for AK502 will bethe same for the remaining data

element 718.

911217 997.002003.DoDO - 11



Transaction Set Note Code[022 A I





997.002003.DOO - 12 911217


Segment: AK9 Functional Group ResponseTrailer

Table: XSequence: 8

Usage: MMax Use: 1

Loop: 0

Purpose: To acknowledge acceptance or rejection of afunctional group and report the number ofincluded transaction sets from the originaltrailer, the ... (See X12 Dictionary.)

Comment: A. If AK901 is "A" or "E", then the trans-mitted functional group is accepted. IfAK901 is "R", then the transmittedgroup is rejected.


AK901 715 Functional Group Acknowledge M ID 1/1CodeCode indicating accept or reject condition based onthe syntax editing of the functional group.

Functional GroupAcknowledge Code

[025 A *] Code DefinitionA AcceptedE Accepted but Errors FoundP At Least One Transaction Set Was RejectedR Rejected

AK902 97 Number of Transaction Sets M NO 1/6IncludedTotal number of transaction sets included in thefunctional group or interchange (transmission)group terminated by the trailer containing this dataelement.

Number of Transaction SetsIncluded

[026 A I

AK903 123 Number of Received Transaction M NO 1/6SetsNumber of Transaction Sets received.

Number of Received Sets[027 A I

911217 997.002003.DoDO - 13

DEPARTMENT OF DEIFISEIMPLEMENTATION GUIDELINES

AK904 2 Number of Accepted M NO 1/6Transaction SetsNumber of accepted Transaction Sets in a FunctionalGroup.

Number of Accepted Sets[028 A I

AK905 716 Functional Group Syntax Error 0 ID 1/3CodeCode indicating error found based on the syntax edit-ing of the functional group header and/or trailer.

Functional Group SyntaxError Code[029 A *] Code Definition

1 Functional Group Not Supported2 Functional Group Version Not Supported3 Functional Group Trailer Missing4 Data Interchange Control No. in Functional5 Number of Included TS Does Not Match

AK906 716 Functional Group Syntax Error 0 ID 1/3CodeCode indicating error found based on the syntax edit-ing of the functional group header and/or trailer.

Functional Group SyntaxError Code

[030 A I

Code values for AK05 will be thesame for the remaining data ele-

ment 716.AK907 716 Functional Group Syntax Error 0 ID 113

CodeCode indicating error found based on the syntax edit-ing of the functional group header and/or trailer.


[031 A I

AK908 716 Functional Group Syntax Error 0 ID .1/3CodeCode indicating error found based on the syntax edit-ing of the functional group header and/or trailer.


[032 A I

AK909 716 Functional Group Syntax Error 0 ID 113CodeCode indicating error found based on the syntax edit-ing of the functional group header and/or trailer.

997.002003.DoDO - 14 911217



[033 A I

911217 997.002003.DoD0 - 16


Segment: SE Transaction Set TrailerTable: X

Sequence: 9Usage: M

Max Use: 1Loop: 0








(035 A I

Must be equal to the number inST02.

997.002003.DoDO - 16 911217

8O c C

SO--- c AU)a.

0.2

E6 E

-0~ .?

76 0

.0 0,0

CE 00 _ u.4

0 tm 2m 0a 00 OE

6 -

0 0 _ .xc

z 0 Va-

655 r5C6

0 60£ ~ 0 006

00~~C 0 0 U

Ch 0 0-g 0C1 0N aD60 N - 06 14C4 4N O Z N NN P

0 0 0 0 00 4

o* 04 CO -o Ln U) qni

N N-DU) ~ Io C 0 0 0 0

0 -N U U 10 LU eu) )

4 .2XX X x x X

c c

.- j0 i, 9c .0 Cc U U U)

z C ;t

* 6 C L E

9121 99.000 D - 17

E

C, a

t ~ Z

z 0 0L n-!g -a . <..!

0~ *z.0 ~ 2 U.E V 0 U - S

0 We -6 SIn .-- cnc

-> .to-0 05 n555z aa - fan 5

> OE OE.- 0

.0 c V..0C L. L CL 0

(3 0090 > >..owm -

44nar 4w4 44~& 44wNfi

o0 N r N N N N ;z ;z ;z Nz Nz ; -

co N P -q 4 eq m) v -(D C4 .)0 ~ O0 0 F) 0 0 a 0 0 0 0m. It It U) U n In an Ln M-0 0

LU he v ~ ~~~ Ne lel e N be ele e

DC 4 4 w 4D 41 4o 4Go4 4 40

x x X X ) x x xx x x x x X x

in to P% a %

44 44 4 . 4 44 44N

So .0

Ei -u uu

S (3S 0Cc

IE .E * aa 0 (0 0) 4

E c r c E. E

A O 0 0 0 0 t 0 , 0 0

997.002003D D- - 18- 91121

oE

E C

0 a

o 00 oL

0~z > it

>*C C.- CV

2-

F co - - .0

2

m C C40)LL L . z

> C4 M V U0

Eo4 ;7, to 9

Uf) EDPs o9 0o 00 0 0 0 -0L ) 0) 0)0) 0) m 0 0

< U

0A. Go cc cc o o 0) 0

4 x x x X C X ~Cx

ae

4 4 4 4 O4

us aA o txi E ' ') E)x x x x 2 2m8

V c 0

o~ a 00- a -

E rE 2

9121 - - -03o - 19

fl7.002003000O - 20 911217

Form ApprovedREPORT DOCUMENTATION PAGE OPMNo.0704-0188

Sb for th colection of information is estimatd to avorage I hour par responm. inciudig the time for reviewing istucdons. u sg data souresgng. ad ma n the data neded .nd reviewing the codtlon of infornation Sad conmmn regarding this I nstint or an othr aspact of this coaectiou of

formation, induding suggastiom for reduang this burdin. to Washington Hodqurts Services. Diroctor e for Information Oprations and let 121S Jeffeson Davis Highway. Suft1 M. Arlington. VA 222024302. and to the Office of infonrmation an Regulatory Affairs Office of Managemen and Budget. Washington. OC 20M.

1. AGENCY USE ONLY (Leave Blank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVERED

Dec91 Final

4. TITLE AND SUBTITLE S. FUNDING NUMBERS

DoD Implementation Guidelines for Electronic Data Intrchange (EDI). Volume H C MDA903-90-C-0006PE 0902198D

6. AUTHOR(S)Morey M. Henderson, Ann P. Lewis

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) B. PERFORMING ORGANIZATIONLogistics Management Institute REPORT NUMBER6400 Goldsboro Road LM[-DL001-01R1Bethesda. MD 20817-6886

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING/MONITORING

DoD Ezecutive Agent for EC/EDI/PLUS AGENCY REPORT NUMBERDefense Logistics AgencyDLA.ZIE, Cameron StationAleandria VA, 22304

11. SUPPLEMENTARY NOTESPrepared in cooperation with Data Interchange Standards Association, the Secretariat and administrative arm o the Accredited StandardsCommittee X12.

12a. DISTRIBUTION/AVAILABILITY STATEMENT 12b. DISTRIBUTION CODEA. Approved for public release; distribution unlimited

13. ABSTRACT (Maximum200 words)

The implementation guidelines are presented in two volumes, developed by the Department of Defense (DoD). for new participants in theelectronic data interchange (EDO program and for documenting DoD's EDI data requirement.

Volume I contain. Chapter. 1-9. Thorn chapter. describe the background, eope, and main issues that need to be considered whenimplementing EDL

Volume 11 contain. Chapter 10 only; it establishes a baseline of DoDs conventions for implementing the American National StandardsInstitute, Accredited Standards Committee X12 uniform standards for electronic interchange ofbusiness transactions. Included are conventionsfor ASC X12 standard invoice, payment order/remittance advice, request for quotation, reaponse to request for quotation, purchase order,purchase order acknowledgment, ship notic.(manifest, receiving advice, report of teat results and functional acknowledgment.

14. SUIUECTTERMS 15. NUMBER OF PAGESElectronic Data Intrchange; EDI; DoD EDI Guidelines; Electronic Commerce; ANSI X12; X12; electronic 446standards- electronic busine standards; computer-to-computer exchange of data; electronic documents;electronic record; electronic funds transfer; procurement automation; paperless environment; 16. PRICE CODEimplementation guideines

17. SECURITY CLASSIFICATION 18. SECURITY CLASSIFICATION 18. SECURITY CLASSIFICATION 20. LIMITATION OF ABSTRACTOF REPORT OF THIS PAGE OF ABSTRACTUnclassified Undasified Unclassified

NSN 7540-41-2B0-SS00 Standard Form 298. (Rev. 2 49)Preecnbad by ANSI St 239-15

dod d - defense technical information center · dod d implementation ... 6.0.2 6.2.2 general...

Documents