AD-A 2 6 3 352iiiili/; tlll!/ i Iltl/!,D ra ft

Department

Defense DTICSELECT.-SAPR2

61993

DoD E

Electronic DataInterchange (EDI)ConventionASC X 12 Transaction Set 869Order Status Inquiry(Version 003020)

DL203LN10

December 1992 -pproved for public releaS|"

BASELINE AS OF: 21 DECEMBER 1992 93-08763

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRYEDI CONVENTION 869.003020

DraftDepartmentof

~I Defense

DoDElectronic DataInterchange (EDI)ConventionASC X 12 Transaction Set 869Order Status Inquiry(Version 003020)

Thi decurnew was prepated by th I a0ko Mhapfi= , gLawit for the 'ea Lap gs e nc~py underTask DL2•S•. The tak wa pinsion underCanmea MDAW3.O.C.-40 with the Department ofDelwme. Pawmdadon to quse or mrpdu any put d ths docun-n mcept for Govermemt pu pm nwabe obtJned omie the DKpsmrsmt of Deiens Emetuw Apgsre Eforummn Carmmmn/Elaronbc DataInendnpPrJPmtedcln of tLAgw Undsmofed/smfllw sys•l n

Executive Agent for EC/EDI/PLUSDefense Logistics AgencyCameron StationAlexandria, VA 22304-6100

RA-ELINE AS OF: 21 DECEMBER 19S2

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRYEDI CONVENTION 8sSA03020

10.0 DoD EDI CONVENTION

ASC X12 TRANSACTON SET 869ORDER STATUS INQUIRY(VERSION 003020)

FORMATTING THE ORDER STATUS INOUIRYFOR THE DEFENSE LOGISTICS AGENCYUSING THE ASC X12 TRANSACTION SET 869.

Accesion ForNTIS CRA&I

DTIC TABUnannounced EJustification

By ............................... ..--Dist ibution I

Availability Codes

Avail andIorDist Special

BASEIJNE AS OF: 21 DECEMBER 1I2 W12I

DEPARTIUET OF DEFENSE ORDER STATUS NWOMYEDI COMENTION 888.00302

{BLANK PAGE}

M"A. 9ASEUNE AS of: 21 DECI1MER Im

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRY

EDI CONVENTION Im.o0300

Contents

FORMATTING THE ORDER STATUS INQUIRY FOR THEDEFENSE LOGISTICS AGENCY USING THE ASC X12 TRANS-ACTION SET 869 ORDER STATUS INQUIRY.

10.1 Introduction

10.1 Reserved

10.2 Control Segments

10.3 Reserved

10.4 Reserved

10.5 Reserved

10.6 Reserved

10.7 DoD Conventions

IOA Reserved

10.B Reserved

10.C Example - Order Status Inquiry From Vendors toDefense Logistics Agency Using ASC X12 869

10.D Reserved

10.E Reserved

10.F Reserved

BASEUNE AS OF: 21 DECEMBER 192 10A..3

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRYEos COWVENTION ue3o0o

{BLANK PAGE}

10.0.4 ASELNE AS OF: M1 DECE.MER 1IM

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRY

EW CONVENTION m86oo9 m

10.i INTRODUCTION

This is an Electronic Data Interchange (EDI) systems designdocument that describes the standard or oconvention" theDefense Logistics Agency will use to permit vendors to requestorder status data using the ASC X12 Transaction Set 869 OrderStatus Inquiry (003020). It contains information for the designof interface computer programs that serve to link systems ap-plication computer programs and an EDI translator computerprogram.

Who Needs to Use This DocumentComputer programmers can use this document to identify thedata in a populated EDI transaction with data requirements oftheir specific application database. Conversely, programmerscan identify where their applications data requirement shouldbe carried in an EDI transaction.

Why Use a ConventionThere are more ways to populate an EDI transaction than thereare ways to fill out a blank form. A convention defines the rulesfor filling in or "populating" an EDI transaction with a specificdata set. Following a convention ensures the integrity of datathat is produced and processed by EDI capable computer sys-tems.

ContentsFour sections are included in this document.

"* Section 10.2, Control Segments, identifies the specific datarequirements for formatting the EDI interchange controlsegments when sending and receiving EDI transactions.

"* Section 10.7, DoD Conventions, lists the layout of the targettransaction set by segment and data element. This sectioncan be used to interpret segments and data elements of apopulated transaction set.

"* Appendices contain examples of populated transaction sets,trading partner data element matrix, and other items thatserve as references for software developers.

BASEUNE AS OF: 21 DECEMBER 192 101.1

DEPARTMENT OF DEFENS OfDER STATUS INOUIRYEDI CONVENTION L302

1BLANK PAGE)

10.12 BASELINE "SOF: 21 DECENMME ION

DEPARTMENT OP DEFEME ORE STATUS INOMIOYEM DCONVEN7WN SA03

10.2 Control Segments

OverviewThis chapter describes the Electronic Data Interchange (EDI)control segments (interchange control segments and functionalgroup segments). The control segment information was derivedfrom the ASC X12 Standards Version 3 Release 2 (003020).

PurposeThis chapter identifies specific data requirement for formattingthe EDI control segments when transmitting and receiving EDItransactions. The format and data content of the control seg-ments is usually managed by EDI translation software. The datarequirement described herein should be used to set controlsegment format when installing or initializing translationsoftware for transmission and reception of EDI transaction.

ContentsTwo items are included in this chapter.

"* Table 10.2-1, Interchange Control Segment Hierarchydescribes the control segments in their order of occurrencein an EDI communications interchange.

" Table 10.2-2, DoD Convention ASC X12 Control Segmentsis a detailed description of the Department of Defense dataconventions for formatting EDI standard control segments.All segments identified in Table 10.2-1 are broken down anddescribed by their discrete data elements.

BASELINE AS OF: 21 DECEMBUR 1S 10M1

DEPARTMENT OF DEFENSE ORDER STATUS UOUSYEDm CONVENTION J3

{BLANK PAGE)

10..2 MASELNE AS OF: 21 DECEMIEM 1910

DEPA ENT OF DEFENSE ORDER STATUS INQUIRY

EDI CONVENTION uss2

TABLE 10.2-1

Control Segment Hierarchy

BASELIE AS OF: 21 DECEMBER I M 10.L3

DEPARMMENT OF DEFENSE ORDER STATUS INQUIRYED CONVENTION

{BLANK PAGE}

10.2.4 BASEUNE AS OF: 21 DECEMBER 136

DEPARTMENT Of DEFENSE ORDER STATUS INOUIAYEWO CONVENTION 09.003020

Interchange Control EnvelopeControl Segments

No. 10 Nome Des use LOo

USE 10 ISA Interchange Control Header M 1

USE 20 OS Functional Group Header M I

* Grouped Transactions

USE 30 GE Functional Group Trailer M I

USE 40 lEA Interchange Control Trailer M I

MSELNE AS OF: tJ DECEMMER Iom 10.6"

DEPARTMENT OF DEFENSE ORDER STATUS UGOURYEDI CONVENImON 86SANO3

BLANK PAGE}

10.,?4 14M.SEUNE AS OF: M DEM•ER Oig

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRY506 CONVENTION .mAoem

TABLE 10.2-2

DoD Convention

ASC X12 Control Segments

ASEULNE AS OF: 21 DECEMBER Ion 10A.7

DEPARTMENIT Of DEFENSE ORDE STATUS MNOWNYmmI cowaami 04BAm32

f{BLANK PAGE}

1.2.8 DMIKUE AS OF: 21 DECEME I M

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRYED! CONVENTION GGSA03

Segment: ISA Interchange Control Header

Usage: MPurpose: To start and identify an interchange of one

or more functional groups and interchange-related control segments. The actual valuesof the data element separator and the seg-ment terminator for this interchange areset by the interchange control header. Fora particular interchange, the value at thefourth character position is the data ele-ment separator, and the value of the lastcharacter position is the value of the seg-ment terminator.

Note: The interchange control number value in thisheader must match the value in the samedata element in the corresponding inter-change control trailer.

Data Element SummaryaL Data

Des. Eleenw Nama Atefiuls

ISA01 101 Authorization Information M ID 2/2QualifierCode to identify the type of information in theAuthorization Information.

Authorization InformationQualifier

(001 ] Code Definition0o No Auidwtafion bnfom~tion Prmant

ISA02 102 Authorization Information M AN 10/10Information used for additional identification orauthorization of the sender or the data in the inter-change. The type of information is set by theAuthorization Information Qualifier.

Authorization Infomation[002 1

I no authodialon informatlon Isageed to by trading paimtre, fill

field with blanks.

ISA03 103 Security Information Qualifier M ID 2/2Code to identify the type of information in theSecurity Information.

BASELINE AS OF: 21 DECEMBER 192 10,2"

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRYEDI CONVENTION m9O32

Security information Ou-WIr[003 1 Code Definition

01 Paswed

ISA04 104 Security Infomatlon M AN 10/10This is used for ideting the security informationabout the sender or the data in the interchange.The type of information is set by the Security Intor-mation Qualifier.

Scurly Irformaton(004 1

An are•ed upon pasowod. If nocrlft InformagIon I agred to by

Usdling parther, fill field with blaans.

ISAOS 105 Interchange Id Oualfie U ID 2.2Qualifier to designate the system/method of codestructure used to ecsig*ate the sender I) elementbeing qualified.

Interchange Id Qualifier[005 1 Code Definition

zz Mubaly Defned.

ISA0O 106 Interchange Sender Id M AN 15/15Identification code published by the sender forother parties to use as the receiver ID to route datato them. The sender always codes this number inthe sender ID element.

Interchanoe Sender Id(006 1

DoD SCtVIte u" Departmen ofDoWn, Ac"ty ddrem Code(DoDAoC) or oth aode om.

dnated with the value.added net-work (VAN). Non-DoD sacvti umn

Identiflcation code qulified byWM106 ard coaordinalld with the VAN.

ISA07 105 Interchange Id Qualifiw M ID 2/2

Code to identy the type of information in theAuthorization Information.

10.2.10 BASEUNE AS OF: 21 DECEMBER IU

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRYEDI CONVENTION 810O3

interchange Id Qualifier1007 j Code Definition

zz Mutually Defined.

ISA08 107 Interchange Receiver Id M AN 15/15Identification code published by the receiver of thedata. When sending. it is used by the sender astheir sending ID, thus other parties sending to themwill use this as a receiving ID to route data to them.

Interchange Receiver Id(008 1

DoD activities use Department ofDefene Activity Addres Code(DoDAC) or other code coor-

dinated with the value-added net-work (VAN). Non-DOD activities use

identification code qualified byISO5 and coordinated with the VAN.

ISA09 108 Interchange Date M DT 6/6

Date of the interchange.Interchange Date

[0091Assigned by translation sothware.

YyMMOD

ISA10 109 Interchange Time M TM 4/4

Time of the interchange.Interchange Time

010 3Assigned by translation software.

HHMM

SAIEUNE AS OF: 21 DECEMBER 1992 102.11

DEPARTMENT OF.DEFENSE ORDER STATUS INQUIRYEW0 CONVENTION 869AO32

ISAI1 110 Interchange Control Standards M ID 1/1Identifier

Code to identify the agency responsible for the con-trol standard used by the message that is enclosedby the interchange header and trailer.

Interchange Control StandardsIdentifier

[O0l IISA12 Ill Interchange Control Version M ID 5/5

NumberThis version number covers the interchange controlsegments.

Interchange Control VersionNumber

[012 1Version ID as defined or agreedupon by the trading parters.

Code DefinitionO3N Draft Swindard for TdaI Use Approved lor

Pubicato by ASC X12 Procedures rAviWBoard Through Ocoe r10

ISA13 112 Interchange Control Number U NO 9/9This number uniquely identifies the interchangedata to the sender. It is assigned by the sender.Together with the sender IM it uniquely identifiesthe interchange data to the receiver. It is suggestedthat te sender, receiver, and all third parties beable to maintain an audit trail of interchanges usingthis number.

Interchange Control Number[013 1

ISA14 113 Acknowledgement Requested U ID 1/1Code seat by the sender to request an interchangeacknowledgemenL

Acknowledgement Requested[014 ]

0 - no; I - yes

102.12 BASEUNE AS OF: 21 DECEMBER te2

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRYEDt CONVENTION 8O6.020G

ISA15 114 Test Indicator M ID 1/1Code to indicate whether data enclosed by this inter-change envelope is test or production.

Test Indicator1015 3

AsWgned by translation oftware.Code DefinitionP Production DataT Test Dta

ISA16 115 Subelement Separator M AN 1/1This is a field reserved for future expansion inseparating data element subgroups. (In the interestof a migration to international standards, this mustbe different from the data element separator).

Subelernent Separator1016 j

Use charawt•e .C.

BASEUNE AS OF: 21 DECEMBER 1962 10..13

DEPARTMENT OF DEFENSE ORDER STATUS INGUIRY

Segment: GS Functional Group HeaderUsage: M

Purpose: To indicate the beginning of a functionalgroup and to provide control information

Comment: A. A functional group of related transac-tion sets, within the scope of X12 stand-ards, consists of a collection of similartransaction sets enclosed by a function-al group header and a functional grouptrailer.

Syntax NotW: 01 The data interchange control number(GS06) in this header must be identicalto the same data element in the as-sociated Functional Group Trailer(GO•2).

Data Element Summary

De& Ehamei 1Na-e Atbmfee

GS01 479 Funtional Id Code U ID 212Code identifyn a group of application relatedTransaction Sets.

Functional Id Code[020 ] Code Definition

RS an - Ordw Sot"m Iormanstin

Chocm the Gode vake aprpdafsIo tho Informatdn contnt of the

funaloni goup. See X12 Oodonarykwr scum@e code etL

GS02 142 Application Sender's Code U ID 2112Code identifying party sending transmission. Codesagreed to by trading partners.

Applkc•on Sender's Code[0211

OoD acidvW use Deparnment ofDefonA*** Addeee Code

PoDDM). Non-WoD acOiWee urnkieificaton code amelgned by DOD

-cf. Recommend fRw koeeeedseudly tOW n=n-D3D code 0Uffe

from •hin wed n In&WM.

GS03 124 Application Receiver's Code U ID 2/12Code identifying party receiing transmission. Codes

10.2.14 SASEUKE AS OF: 21 DECEMI 1IS0

DEPARTMdENT OF DEFENSE ORDER STATUS INQUIRYEID CONVENTION 08SS302

agreed to by trading partners.Application Receivers Code

DeD ac"vites use Depsrtment ofDefense Activity Address Code

(DoDAAC). Non-DoO activities usidentfifcation code assigned by DoD

activity. Recommend for Iceasedsecurity that non-DoD code differ

from mat used In ISM".

GS04 29 Group Date U DT Qd6Date sender generated a functional group of transac-tion sets.

Group Date[023]

DAsIgned by translation softwars.

GSO6 30 Group Time M TM 4/4Time (HHMM) when the sender generated a func-tional group of transaction sets (local time atsender's location).

Group Time(024 ]

Assigned by translation ftware.

GSO6 28 Group Control Number M NO 1/0Assigned number originated and maintained by thesender.

Group Control Number1025 1

Assigned by translation software.

GS07 455 Responsible Agency Code M ID 1/2Code used in conjunction with Data Element 480 toidcni th issuer of the standard.

Responsible Agency Code1026 1

Indicaes that an ANSI X12 standardis being tranmItled.

Code DefinitionX Accredited Standards Cmmitine X12

BASEUNE AS OF: 21 DECEMBER 92 1l02.15

DEPARTMENT OF DEFENSE ORDER STATUS iNQUIRYEDm CONVENTION SGSA..

GS08 480 Version/Release/Industry ld M ID 1/12CodeCode indicating the versio, release, subrelease andindustry identifier of the EDI standard being used.(See X12 Dictionary)Version/Relessedndustry Id

Code(027 1

CoO value agreed to by trdingpuiwm See MX2 D0konay for

sume oode kLCode DefinitionOU.- Daft Srwnt APprved By' ASC X12 Throug

June 1991

10.2.1 BASEUNE AS OF: 21 DECEMBER IOM

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRYE.• CONVENTION 6C32

Segment: GE Functional Group TrailerUsage: M

Purpose: To indicate the end of a functional groupand to provide control information

Comment: A. The use of identical data interchangecontrol numbers in the associated func-tional group header and trailer isdesigned to maximize functional groupintegrity. The control number is thesame as that used in the correspondingheader.

Syntax Notes: 01 The data interchange control number(GE02) in this trailer must be identicalto the same data element in the as-sociated Functional Group Header(GS06).

Data Element SummaryPAL Drm H

GEO0 07 Number of Included Sets M NO 1/6Total number of transaction sets included in thefunctional group or interchange (transmission)group terminated by the trailer containin this dataelement.

Number of Segments[028 1

AeiNed by go#wktan cmlosoftware.

GE02 23 Group Control Number M NO 1/9Assigned number originated and maintained by thesender.

Group Control Number[029 1

ADsined by 2w tVWnslsoneoftwam. TNs contMol numbw mus

msah to control number of #wprcedn GSM onol numbw.

ISIAENE AS OF: 21 DECEMBER 190 10.2.17

DEPARTMENT OF DEFENSE ORDER STATUS iNQUIRYEDI CONVENTION asOA0020

segrmnet lEA Interchange Control TrailerUsage: M

PupoSe: To define the end of an interchange of oeor more functional groups and interchangerelated control segments.

Note: The interchange control number in thistrailer must match the value in the same dataelement in the corresponding interchangeheader.

Data Element SummaryROL DDew Earemw Name A1WIWWa

lEA01 116 Number of Included Functional M NO 1/5GroupsA count of the number of functional groups in-cluded in a tra--sision,

Number of IncludedFunctional Groups

[0401signed by mlwadon softwar.

IEA02 112 Interchange Control Number U NO 9/9This number uniquely identifies the interchangedata to the sender. It is asigned by the sender.Together with the sender ID it uniquely identithe interchange data to the receiver. It is suggestedthat the sender, receiver, and all third parties beable to maintain an audit trail of interchanges usingthis number.

Intechange Control Number[041]

Assigned by Iuakwon sftwor.This numbew must miath Oe numn-

ber Vat occurs a ISMAl&

I0.2.1i BASELINE AS OF: 21 DECEMUER In

• d .

AME OF DFENSE ORDER STATUS IIUINRY

10.7 DoD CONVENTIONS

OverviewThis chapter is the convention for the ASC X12 Transaction Set869 (Version 003020) as used by the Defense Logistics Agencyto permit vendors to request data used by contracting officerswhen making contract award determinations.

PurposeThis chapter contains all necessary information for a DoD trad-ing partner to map and translate a Transaction Set 869. Alltrading partners who plan to exchange the Transaction Set 869can use this document as a reference for the development oftheir EDI database/translator interface program.

ContentsOne table is included in this chapter.

e Table 10.7-1, ASC X12 Transaction Set 869 Segment Hierar-chy describes the 869 segments as they appear in the ASCX12 Standards Dictionary. The DoD Conventions that fol-low are a detailed description of the Department of Defenseconventions for transmitting Transaction Set 869. All seg-ments identified as used in the Segment Hierarchy aredetailed in Table 10.7-1 by segment, position, and codevalue.

B INE AS OF: 21 DECIMUER I M 10.7.1

DEPARTMENT OF DEFENSE 01R STATUS IIUINYE .cONVENTI.N ASOO:030

{BLANK PAGE)

10.7.2 BASELNE AS OF: 31 DECEMUEISO

DEPARTMENT OF DEFENSE ORDER STATUS IQUiRY

EID CONVENTION mSOL32

TABLE 10.7-1

SEGMENT HIERARCHY

ASC X12 TRANSACTION SET 869ORDER STATUS INQUIRY (Version 003020)

MSELINE AS OF: 21 DECEMEIIR IM 10.73

DEPARTMENT OF DEFENSE ORDER STATUS DRUMEN CONVENTION SSOLO320

{BLANK PAGE}

10.7A mSEUN/ AS OF: 21 DECEMBER 19U

$69 -AUTOMATED BEST VALUE MODEL INQUIRYANSI ASC X12 VERSIO/RELEASE 003020

869 Order Status InquiryThis standard provides the format and establishes the data contents of anorder status inquiry transaction set. The order status inquiry transaction setprovides the ability to request all pertinent information relative to an entirepurchase order. selected line items on a purchase order, or selectedproducts/services on a purchase order. Inquiry can also be made for all or aselected portion of the customer's ordered items, all or a selected portion ofthe customer's unshipped items, or all or a selected portion of the customer'sshipped items.

Table 1PAGE# M& P SEG. 10 NAME RE DES. MAX USE LOOP REPEAT

3 010 ST Transaction Set Header M 14 020 BSI Beginning Segment for Order Status Inquiry M 1N/U 030 NTE Note/Special Instruction 0 100

Table 2PAGE| P05. $EQ10.1 NAME REQ. DE. MAX USE LOOP REPEAT

UwO I -HL l0005 010 HL Hierarchical Level M IN/U 020 PRF Purchase Order Reference 0 1N/U 030 DTM Date/Time Reference 0 10

N/U 040 REF Reference Numbers 0 12

LOOP IDNIV . 2007 050 N1 Name 0 1N/U 060 N2 Additional Name Information 0 2N/U 070 N3 Address Information 0 2N/U 080 N4 Geographic Location 0 1N/U 090 REF Reference Numbers 0 12N/U 100 PER Administrative Communications Contact 0 3N/U 110 LIN Item Identification 0 1N/U 120 PID Product/Item Description 0 1000N/U 130 MEA Measurements 0 40

DC14. DECEMBER 28 1992

869 AUTOMATED BEST VALUE MODEL INQUIRYANSI ASC X12 VERSIWORELEASE 003020

Table 3PACE@ POFM -. O "M I*& OM MAX USE

LOWP IAT

a 010 CTT Transaction Totals M 1

9 020 SE Transaction Set Trailer M I

NOTE:"3/010 CTTO1 is the number of HL segments.

oC4 . DECEMBER 26 IM 2

See . AUTOMATED BEST VALUE MODEL INQUIRYST -TRANSACTION SET HEADER ANSI ASC X12 VERSIOW/RELEASE 003020

Segment: ST Transaction Set HeaderLevel: Header

Loop:Mandatory Usage: Mandatory

Max Use: I

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

Comment: The transaction set identifier (ST01) is intended for use by the translationroutines of the interchange partners to select the appropriate transactionset definition (e.g., 810 selects the invoice transaction set).

Data Element SummaryMP. DATADE&L ELINSIT NK ATUTUM

Mandatory ST01 143 Transaction Set Identifier Code M ID 313Code uniquely identifying a Transaction Set.

869 X1 2.11 Order Status Inquiry

Mandatory ST02 320 Transaction Set Control Number M AN 4A9Identifying control number assigned by the originator for a transaction set.

3 DC14 • DECEMBER 211992

* AUTOMATED BEST VALUE MODEL INUIRYANSI ASC X12 VERSIONRELEASE 003020 BSJ. BEGINNING SEGMENT FOR ORDER STATUS INQUIRY

Segment: BSI Beginning Segment for Order Status InquiryLevel: Header

Loop:Mandatory Usage: Mandatory

Max Use: 1

Purpose: To indicate the beginning of an order status inquiry and to provide thetype of customer status inquiry.

Comments: 1. BSI01 is a status inquiry reference number.2. BSI02 is date of the inquiry.

3. BSI06 is time of the inquiry.

Data Element SummaryOW. DATA

Mandatory BSI01 127 Reference Number M AN 1/30Reference number or identification number as defined for a particularTransaction Set, or as specified by the Reference Number Oualifier.

Implementation Note:A unique number assigned by the originator oftthe transaction set. This number is different fron the controlnumber carried in ST02.

Mandatory BSI02 373 Date M DT SDate (YYMMDD).

Mandatory 5S103 847 Order/Rtem Code M ID 1/2Code identifying a group of orders and items.

CA All Orders - All Items

Code Value knplementatlon Note:Use code "CA" to indicate ao current diserqxncy status is being requested.

Not Used BSI04 848 Product/Date Code 0 ID 1/2

Not Used BSI05 849 Location Code 0 ID 1/2

Not Used BSIO 337 Time 0 TM 44

DC14 - DECEMBER 28 192 4

669 • AUTOMATED BEST VALUE MODEL INQUIRYHL. HIERARCHICAL LEVEL ANSI ASC X12 VERSION/RELEASE 003020

segment: HL Hierarchical LevelLevel: Detail

Loop: HL Repeat: 1000Mandatory Usage: Mandatory

Max Use: 1

Purpose: To identify dependencies among and the content of hierarchically relatedgroups of data segments.

Comments: 1. The HL Segment is used to identify levels of detail information using aHierarchical Structure, such as relating line item data to shipment data,and packaging data to line item data.

2. The HL segment defines a top-down/left-right ordered structure.

3. HL01 shall contain a unique alphanumeric number for eachoccurrence of the HL segment in the transaction set. For example HL01could be used to indicate the number of occurrences of the HL segment,in which case the value of HL01 would be "1" for the initial HL segment,and would be incremented by one in each subsequent HL segmentwithin the transaction.

4. HL02 identifies the Hierarchical ID Number of the HL segment towhich the current HL segment is subordinate.

5. HL03 indicates the context of the series of segments following thecurrent HL segment up to the next occurrence of an HL segment in thetransaction. For example, HL03 is used to indicate that subsequentsegments in the HL loop form a logical grouping of data referring toshipment, order or item level information.

6. HL04 indicates whether or not there are subordinate (or child) HLsegments related to the current HL segment.

Data Element SummarylF. "AIaima. mim ND at"maml

Mandatory HL01 628 Hierarchical ID Number M AN 1)12A unique number assigned by the sender to identify a particular data segment ina hierarchical structure.

Implementation Note:The first iteration of the "ILL" loop will carry the number "I". Each subsequent iteration of the "HL" loop willcarry a progressively higher number. (e.g., 2,3.4. etc.).

Optional HL02 734 Hierarchical Parent ID Number 0 AN 1/12Identification number of the next higher hierarchical data segment that the datasegment being descnrbed is subordinate to.

Implementation Note:This data element is not used in the first iteration of the "HLL" loop. In the second and subsequent iterations ofthe "IlL" loop, HL02 will carry the hierarchical ID number contained in the parent HLOI data element.

Mandatory HL03 735 Hierarchical Level Code M ID 1/2Code defining the characteristic of a level in a hierarchical structure.

5 4. DECEMBER 281992

869 . AUTOMATED BEST VALUE MODEL INQUIRY

ANSI ASC X12 VERSION/RELEASE 003020 HL • HIERARCHICAL LEVEL

0 OrderCode Value Implemrentation Note:Use code "0" to indicate discrepancy status is being requested at the contractiorder level.

Not Used HL04 736 Hierarchical Child Code 0 ID 111

MC14 DECEMBER 26192 6

$69 -AUTOMATED BEST VALUE MODEL INQUIRY

NI- NAME ANSi ASC X12 VERSION/RELEASE 003020

Segment: NI NameLevel: Detail

Loop: N1 Repeat: 200Optional Usage: Optional

Max Use: 1

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

Syntax: 1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comment: This segment, used alone, provides the most efficient method ofproviding organizational identification. To obtain this efficiency the "IDCode" (N104) must provide a key to the table maintained by thetransaction processing party.

Data Element SummaryI". DATA

Mandatory N101 98 Entity Identifier Code M ID 2/2Code identifying an organizational entity.or a physical location.

FR Message From

Code Value Implementation Note:Use code "FR" to indicate the message is from the pary identyied in data element N104.

Not Used N102 93 Name C AN 1/35

Conditional N103 66 Identification Code Qualifier C ID 1/2Code designating the system/method of code strudure used for IdentificationCode (67).

33 Commercial and Government Entity (CAGE)

Code Value Implementation Note:When RIO)! is code "FR" use code "33" to indicate the information in data element N104 is the"CAGE" code of the party sending the message.

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

Implementation Note:The actual CAGE code.

7 0C14. DECEMBER 28 1IM2

e69- AUTOMATED BEST VALUE MODEL INQUIRYANSI ASC X12 VERSION/RELEASE 003020 CTT . TRANSACTION TOTALS

Segment: CTT Transaction TotalsLevel: Summary

Loop:MUadatory Usage: Mandatory

Max Use: 1Purpose: To transmit a hash total for a specific element in the transaction set

Syntax: 1. C0304 - If CTT03 is present, then CTT04 is required.2. C0506 - If CTT05 is present, then CTT06 is required.

Comment: This segment is intended to provide hash totals to validate transactioncompleteness and correctness.

Data Element SummaryIM. DATA

RMg WAR War ¶iUn

Mandatory CTTO1 354 Number of Line Items M NO 1/8Total number of line items in the transaction set.

Implementation Note:CTTOI crries ghe totat number of afl the "HL segments usd in the transaction.

Not Used CTT02 347 Hash Total 0 R 1/10

Not Used CTrO3 S1 Weight 0 R 1/8Not Used CTT04 356 Unit of Measurement Code C ID 212

Not Used CTros 183 Volume 0 R 1/8Not Used CTTOs 3S5 Unit of Measurement Code C ID 212Not Used C"r07 352 Description 0 AN 1180

DC14 • DECEMRER 283192 8

S6U. AUTOMATED BEST VALUE MODEL INQUIRYSE TRANSACTION SET TRAILER ANSI ASC X12 VERSION/RELEASE 003020

Segment: SE Transaction Set TrailerLevel: Summary

Loop:Mandatory Usage: Mandatory

Max Use: IPurpose: To indicate the end of the transaction set and provide the count of the

transmitted segments (including the beginning (ST) and ending (SE)segments).

Comment: SE is the last segment of each transaction set.

Data Element SummaryRiP. DATA0M t•%,ur H ArIVADrM

Mandatory SEOI 96 Number of Included Segments M NO 1/6Total number of segments included in a transaction set including ST and SEsegments.

Implementation Note:'EOI carries the total number of segments in the transaction set including the "ST" and "SE" segments.

Mandatory 5E02 329 Transaction Set Control Number M AN 4/9Identifying control number assigned by the originator for a transaction set.

hIplementation Note:SE02 carries the same unique control number as the one in ST02.

9DC14 DECEMBER 28 192

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRYEDI CONVENTION 69A.OO3O2

10.C Example - X12 Transaction Set 869Order Status Inquiry

This appendi'x contains an example of Transaction Set 869 as itis used by the Defense Logistics Agency to permit vendors torequest data used by contracting officers when making contractaward decisions.

MIASUNE AS OF: 21 DECEMBER 192 i0.C.1

DEPARMENT OF DEFENSE ORDUM STATUS INCKMYEla • COVETONLO0302

{BLANK PAGE}

.0.G.2 lSASEJIE AS OF: M1 DECEMSER IurM

DEPARTMENT OF DEFENSE ORDER STATUS INQUIRYEDI CONVENTION WA3

Example - ORDER STATUS INQUIRY (869) TRANSACTION SET

ASC X12 EDI SYNTAX ORDER STATUS INQUIRY DATA

ST*869*0001 nil The transaction set Is an Order Status Inquiry(number S69) with a transaction set control numberassigned by the originator of 0001.

BSI*3MOO1*9211O1*CA niA The originator of the tauactlon set assigned it aunique number of 3M1001; the transaction is datedNovember 1, 1992; It Is a csntractae's request forinforuatiou contained in hin tile.

HL*1*O ni The first Iteration of the hierarchical smet (aftthe number 't) ks at the order level (use code "0").

N1*FR**33rB712 n/i This transaction set Is coming from (use code I'W)a DLA contractor whose CAGE code (mse code 03nIs 13712.

CITT I A In this transaction set there Is one Iteration of tdo*HL loop.

SE*60001 0/ In this transaction. which ame transaction met con-Vrol number 0001, theie are 6 segments, Includingthe *W and *SE segmentis.

NOTES: ALLý NUMBERS ARE NO7TIONAL AND USED FOR ILLUSTRATION PURPOSES ONLY.

The example is mapped to ASC X12 standards, version 3, release 2

An asterisk is used as the data element delimiter; the expression 'n/i indicates end of the segment.

BASELINE AS OF: 21 DECEMIER 1I3M 1LC.3

DEPARTMENT OF DEFENSE ORDE STATUlS INQUIRYEDO CONVENTION 08OA0302

{BLANK PAGE)

IOaCA MASEUNE AS OF: 21 DECENSE ISO

L REPORT DOCUMENTATION PAGE OPM No. 0704-0188Public reportng burdm for this collection of information is estimated to average 1 hour per response, including the time for revewing insttuctions, searching existing data sourcesgathering. and maintaining the data needed. and vwiewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection ofIniformatiofl. including suggestions for reducing this burden, to Washington Headquarters Services. Directorate for infor•aison Operations and Reports. 121S J*ffer Oavis Highway. Suite1". Arlinglton. VA 22202-4302. and to the Office of Information and Regulatory Affairs. Office of Management and Budget Washington. DC 20503.

1. AGENCY USE ONLY (Leave Blank) 2. REPORT DATE 3. REPORT TYPE AND DATES COVERED

December 1992 Draft

4. TITLE AND SUBTITLE 5. FUNDING NUMBERS

DoD Electronic Data Interchange (EDI) Convention C MDA9O3-90-C-0006ASC X12 Transaction Set 869 Order Status Inquiry (Version 003020) PE 0902198D

6. AUTHOR(S)Stephen LusterRichard ModrowskiWilliam T. James

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) 8. PERFORMING ORGANIZATION

Logistics Management Institute REPORT NUMBER

6400 Goldsboro Road LMI-DL203-LN1OBethesda, MD 20817-5886

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSORING/MONITORING

DoD Executive Agent for EC/EDI/PLUS AGENCY REPORT NUMBER

Defense Logistics AgencyDLA-ZIE, Cameron StationAlexandria. VA 22304

11. SUPPLEMENTARY NOTES

12a. DISTRIBUTION/AVAILABILITY STATEMENT 12b. DISTRIBUTION CODE

13. ABSTRACT (Maximum 200 words)

This is an Electronic Data Interchange (EDI) systems design document that describes the standard or "convention" the Defense LogisticsAgency will use to accept a vendor's request for order status date using the ASC X12 Transaction Set 869 Order Status Inquiry 1003020).

14. SUBJECT TERMS 15. NUMBER OF PAGES

Electronic Data Interchange; EDI; DoD EDI Convention: Electronic Commerce; ANSI X12; X12; electronic 42standards; electronic business standards; computer-to-computer exchange of data; electronic documents; 16. PRICE CODEelectronic records; paperless environment; conventions

17. SECURITY CLASSIFICATION 18. SECURITY CLASSIFICATION 19. SECURITY CLASSIFICATION 20. LIMITATION OF ABSTRACTOF REPORT OF THIS PAGE OF ABSTRACT ULUnclassified Unclassified Unclassified

NSN 7540-01-280-5500 Standard Form 298, (Rev. 2-89)Prescribed by ANSI Std. 23•-I