NAT'L INST. OF STAND & TECH R.I.C.

A111D5

NI$T

PUBLICATIONS

Special Publication 881-24

QC

100

.157

NO.881-24

1997

i

*

•kMikihlililkM

lllllllllll lllllllllll

ill inn

Nisr

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 869

Order Status Inquiry

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology

NIST Special Publication 881-24

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 869

Order Status Inquiry

Implementation Convention

Electronic Commerce Acquisition Program Management Office

Standard Management Committee - Secretariat

National Institute of Standards and Technology

Gaithersburg, MD 20899-0001

Editor: Dr. Jean-Philippe Favreau

May 1997

U.S. DEPARTMENT OF COMMERCE

William M. Daley, Secretary

Technology Administration

Mary L. Good, Under Secretary for Technology

National Institute of Standards and Technology

Robert E. Hebner, Acting Director
Reports on Information Technology

The National Institute of Standards and Technology (NIST)'s Information Technology Laboratory (ITL)

develops standards and guidelines, provides technical assistance, and conducts research for computers

and resources. As part of the overall federal effort to establish a single face to industry for conducting

electronic commerce, ITL has been designated as the organization responsible for coordinating the

development of Federal Implementation Conventions (ICs) for Electronic Data Interchange (EDI). ICs are

defined by functional-area experts who create and select options from standard EDI Transaction Sets to

yield the implementations to be used for practical EDI. These ICs are made available to federal agencies

and industry by electronic means and this Special Publication Series.

National Institute of Standards and Technology Special Publication 881-24

Natl. Inst. Stand. Technol. Spec. Publ. 881-24, 19 pages (May 1997)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1997

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
869 Order Status Inquiry

Functional Group ID=

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Inquiry

Transaction Set (869) for use within the context of an Electronic Data Interchange (EDI) environment. The

transaction set can be used to request all pertinent information relative to an entire purchase order, selected line

items on a purchase order, or selected products/services on a purchase order. Inquiry can also be made for all or a

selected portion of the customer's ordered items, all or a selected portion of the customer's unshipped items, or all or a selected portion of the customer's shipped items.

Notes:

This transaction set is used by a contract administration office (includes procurement contracting officers who

have retained administration ofa contract) to request delivery statusfrom a contractor.

Heading:

Must Use

Pos. No. 010

ID

ST

Must Use 020 BSI

N/U 030 NTE

Detail:

Pos. No.Seg.

E>

Must Use 010 HL

N/U 020 PRF

030 DTM

040 REF

050 LIN

N/U 060 PID

N/U 070 MEA

N/U 080 QTY

N/U 090 AT

N/U 100 GF

110 Nl

N/U 120 N2

N/U 130 N3

N/U 140 N4

N/U 150 REF

160 PER

Name

Transaction Set Header

Beginning Segment for Order Status Inquiry

Note/Special Instruction

Name

Req.

Pes. M

M

O

Req.

Des.

Max.Use

1

1

100

Loop

Repeat

Notes and

Comments

Max.Use

Loop

Repeat

Notes and

Comments

mmmi

Hierarchical Level

Purchase Order Reference

Date/Time Reference

Reference Numbers

Item Identification

Product/Item Description

Measurements

Quantity

Financial Accounting

Furnished Goods and Services

Additional Name Information

Address Information

Geographic Location

Reference Numbers

Administrative Communications Contact

M 1 O 1 O 10 O >1

O >1

O 1000

O 40

O 1 O >1 O 1

x>::v>>:>^x>-:^v-:^:V-:;

:

:

: : :^: ::

: :

; :':'>:->: :

: O "l

O 2 O 2 O 1 O 12 O 3

LOOPEB-LM

003050FED00A January 13, 1997
869 - Order Status Inquiry

N/U

N/U

170

180

LM

LQ

Code Source Information

Industry Code

Summary:

Pos. Seg. No. ID

N/U 010 CTT

Must Use 020 SE

Name

Transaction Totals

Transaction Set Trailer

O

M

1

>1

Req.

Pes. OMaXjUse

Loop

Repeat

Notes and

Comments

nl M

Transaction Set Notes

1. CTT01 is the number of HL segments.

003050FEDOOA 2 January 13, 1997
869 - Order Status Inquiry

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ST Transaction Set Header

010

Heading

Mandatory

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

1 The transaction set identifier (STO 1) used by the translation routines of the

interchange partners to select the appropriate transaction set definition (e.g., 810

selects the Invoice Transaction Set).

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use ST01 143 Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

869 X12. 1 1 Order Status Inquiry

Must Use ST02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set This unique control number is assigned by the originator ofthe transaction

set or by the originator's application program. This same number is carried

in SE02.

003050FED00A 3 January 13, 1997
869 - Order Status inquiry

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

BSI Beginning Segment for Order Status Inquiry

020

Heading

Mandatory

1To indicate the beginning of an order status inquiry and provide the type of customer

status inquiry

1 BSI01 status inquiry reference number.

2 BSI02 is date of the inquiry.

3 BSI06 is time of the inquiry

Data Element Summary

Ref.

Pes.

Must Use BSI01

Must Use BSI02

Must Use BSI03

Data

Element

127

373

847

Name Attributes

Reference Number M AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

Use to identify a unique number assigned to this transaction set to reference

in other transaction sets, e.g., 870 Order Status Report, 824 Application

Advice, etc. Date M DT 6/6

Date (YYMMDD)

Use to identify the date ofthis transaction set. Order/Item Code M ID 1/2

Code identifying a group of orders and items

Use to identify the extent ofthe inquiry.

AO All orders - items with changed status

1. Use to indicate a status report is being requested

for all items that have previously been reported with

changed delivery status on all award instruments that are notphysically complete.

2. When used, unless additional parametersfor the

content ofthe report are identified by use of

hierarchical level codes in HL03 ofthe 2/HU010 loop,

the hierarchical level can be limited to the Address

Level (code V). CA All Orders - All Items

1. Use to indicate a status report is being requested

for every item on all award instruments that are not

physically complete.

2. When used, unless additional parametersfor the

content ofthe report are identified by use of

hierarchical level codes in HL03 ofthe 2/HL/010 loop,

the hierarchical level can be limited to the Address

Level (code V).

CO All Orders - Unshipped Items

1. Use to indicate a status report is being requested

for all unshipped items on all award instruments that are notphysically complete.

003050FED00A 4 January 13, 1997
869 - Order Status Inquiry

2. When used, unless additional parametersfor the

content ofthe report are identified by use of

hierarchical level codes in HL03 ofthe 2/HL/010 loop,

the hierarchical level can be limited to the Address

Level (code V).

PA Selected Orders - All Items

1. Use to indicate a status report is being requested

for all items in specified orders.

2. Additional parametersfor the content ofthe report

(e.g., by ship-to location, by delivery date, etc.) can be

identified by use ofthe appropriate hierarchical level

code in HL03 ofthe 2/HL/010 loop. Ifno additional

parameters are specified, the hierarchical level can be

limited to the Address Level (code V), the Award

Instrument Level (code IB) and, ifapplicable, the

Delivery Order, Call, or Release Level (code 0).

PO Selected Orders - Unshipped Items

1. Use to indicate a status report is being requested

for all unshipped items in specified orders.

2. Additional parametersfor the content ofthe report

(e.g., by ship-to location, by delivery date, etc.) can be

identified by use ofthe appropriate hierarchical level

code in HL03 ofthe 2/HL/010 loop. Ifno additional

parameters are specified, the hierarchical level can be

limited to the Address Level (code V), the Award

Instrument Level (code IB) and, ifapplicable, the

Delivery Order, Call, or Release Level (code 0).

PP Selected Orders - Selected Items

1. Use to indicate a status report is being requested

for specific items on specific orders.

2. Additional parametersfor the content ofthe report

(e.g., by ship-to location, by delivery date, etc.) can be

identified by use ofthe appropriate hierarchical level

code in HL03 ofthe 2/HL/010 loop. Ifno additional

parameters are specified, the hierarchical level can be

limited to the Address Level (code V), the Award

Instrument Level (code IB) and, ifapplicable, the

Delivery Order, Call, or Release Level (code 0).

BSI07 353 Transaction Set Purpose Code O ID 2/2

Code identifying purpose of transaction set 00 Original

Use to indicate an original inquiry.

01 Cancellation

Use to indicate the cancellation ofa previously

transmitted inquiry.

003050FED00A 5 January 13, 1997
869 - Order Status Inquiry

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

HL Hierarchical Level

010

HL

Detail

Mandatory

1To identify dependencies among and the content of hierarchically related groups of data

segments

1 The HL segment defines a top-down/left-right ordered structure. 2 HL01 shall contain a unique alphanumeric number for each occurrence of the HL

segment in the transaction set. For example, HL01 could 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 segment within the transaction.

3 HL02 identifies the hierarchical ID number of the HL segment to which the current

HL segment is subordinate.

4 HL03 indicates the context of the series of segments following the current HL

segment up to the next occurrence of an HL segment in the transaction. For

example, HL03 is used to indicate that subsequent segments in the HL loop form a

logical grouping of data referring to shipment, order, or item-level information.

5 HL04 indicates whether or not there are subordinate (or child) HL segments related

to the current HL segment.

1. This segment is used to identify the level at which the report is being requested. For

example, when BSI03 is code CA, the report can be limited to all orders issued by a

specified buying activity (code B) to be delivered on a specified date (code C). Or when

BSI03 is code PP, the report can be limited to specific award instruments (code IB), or

specific delivery orders (code O) issued against those award instruments.

2. Ifa report requires status on specific CLINS, SUBCLINS or ELINSfor a specified

award instrument, delivery order, or exhibit, the applicable CLIN, SUBCUN, or ELIN

is identified in the LIN segment.

3. Thefirst HL segment must always contain code Vin HL03.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use HL01 628 Hierarchical ID Number M AN 1/12

A unique number assigned by the sender to identify a particular data segment

in a hierarchical structure Use to identify a unique andprogressive number assigned by the originator of

the transaction set starting with the number 1. HL02 734 Hierarchical Parent ID Number O AN 1/12

Identification number of the next higher hierarchical data segment that the

data segment being described is subordinate to Use to identify data identified in a previous HL loop to which the data in the

current HL loop is subordinate. This is a number cited in HL01. For

example, the third HL loop at the delivery order level (code O) may be

subordinate to the second HL loop at the award instrument level (code IB),

therefore, the number 2 would be cited. Ifan HL loop is not subordinate to another HL loop, this data element is left blank.

Must Use HL03 735 Hierarchical Level Code M ID 1/2

Code defining the characteristic of a level in a hierarchical structure

I. Use to identify the level at which the data is to be reported.

003050FED00A 6 January 13, 1997
869 - Order Status Inquiry

21

25

B

C

D

IB

IC

O

PA

S

V

003050FED00A

Information Receiver

Use to indicate the party to receive the requested

report ifdifferent than the inquiring party. This code

is a stand alone hierarchical level , i.e., it has no

subordinate levels. Subgroup

Use to indicate a hierarchical levelfor requested data

applicable to a specified subcontractor.

Buyer's Location

Use to indicate a hierarchical levelfor requested data

associated with award instruments issued by a specific

buying activity.

Date

Use to indicate a hierarchical levelfor requested data

applicable to a specified delivery date or range of

dates.

Product Description

Use to indicate a hierarchical levelfor requested data

identified by a product description, e.g., NSN,

manufacturer part number, etc. , or by a type of

service.

Contract

1. Use to indicate a hierarchical levelfor requested

data applicable to a specified award instrument, e.g., contract, basic contract, purchase order, basic

ordering agreement, etc.

2. Use only when BSI03 is code PA, PO, or PP.

Contract Data Requirements List (CDRL)

1. Use to indicate a hierarchical levelfor requested

data applicable to a Contract Data Requirements List

(CDPL).

2. Use only when BSI03 is code PP.

Order

1. Use to indicate a hierarchical levelfor requested

data applicable to a specified delivery order, call or

release.

2. Use only when BSI03 is code PA, PO, or PP.

Primary Ao^ministrator

Use to indicate a hierarchical levelfor requested data

associated with award instruments administered by a

specified contract administration office.

Shipment

Use to indicate a hierarchical levelfor requested data

applicable to a specified ship-to location.

Address Information

Use ofthis code is REQUIRED to indicate the identity

and address ofthe party to whom the request is being

submitted (the selling party) and the party requesting

the report (the inquiring party). This code is a stand

alone hierarchical level , i.e., it has no subordinate

levels. When used, in addition to HL01 and HL03 in

this segment, the DTMsegment can be used to specify

the date the report is required and the Nl loop is used

7 January 13, 1997
869 - Order Status Inquiry to identify the parties.

HL04 736 Hierarchical Child Code O ID 1/1

Code indicating whether if there are hierarchical child data segments

subordinate to the level being described.

Use to identify whether or not there are subordinate hierarchical levels to follow.

0 No Subordinate HL Segment in This Hierarchical

Structure.

1 Additional Subordinate HL Data Segment in This

Hierarchical Structure.

003050FEDOOA 8 January 13, 1997
869 - Order Status Inquiry

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use DTM01

DTM02

DTM05

DTM06

DTM07

DTM Date/Time Reference

030

HL

Detail

Optional

10

To specify pertinent dates and times

1 At least one of DTM02 DTM03 or DTM06 is required.

2 If either DTM06 or DTM07 is present, then the other is required.

1. When HL03 is code C, use this segment to identify the Required Delivery Date or range ofdates that are to be the basis ofthe requested report. Ifmultiple reports are requestedfor different delivery dates or ranges ofdates, repeat this segment citing the

applicable delivery date or range ofdatesfor each report.

2. Use also to identify the reply datefor the requested information.

Data

Element

374

Data Element Summary

Name

Date/Time Qualifier

Code specifying type of date or time, or both date and time

Attributes

M ID 3/3

501

996

373

624

1250

Date

Date (YYMMDD)

Century

Expected Reply

Use to indicate the date a reply is requested.

Required Delivery

When HL03 is code C, use to indicate the specific

delivery date(s) ofthe itemsfor -which the report is

requested.

X DT 6/6

O NO 2/2

The first two characters in the designation of the year (CCYY)

Date Time Period Format Qualifier X ID 2/3

Code indicating the date format, time format, or date and time format

1. When HL03 is code C, use, ifapplicable, to identify a range ofdates to which the inquiry applies.

2. The requested range may be both past andfuture dates.

RD6

RD8

1251 Date Time Period

Range of Dates Expressed in Format YYMMDDYYMMDD

Range of Dates Expressed in Format CCYYMMDDCCYYMMDD

X AN 1/35

Expression of a date, a time, or range of dates, times or dates and times

003050FED00A 9 January 13, 1997
869 - Order Status Inquiry

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

REF Reference Numbers

040

HL

Detail

Optional

>1

To specify identifying numbers.

1 At least one of REF02 or REF03 is required.

When HL03 is code IB, IC, or O, use to identify reference numbers applicable to these

hierarchical levels.

Ref.

Pes.

Must Use REF01

REF02

Data

Element

128

127

Data Element Summary

Name

Reference Number Qualifier

Code qualifying the Reference Number.

CT

Attributes

M ID 2/2

Contract Number

When HL03 is code IB, use to indicate the number of

an award instrument.

DO Delivery Order Number

When HL03 is code O, use to indicate a delivery order,

call or release.

GO Exhibit Identifier

When HL03 is code IC, use to indicate the exhibit

identifier letter. Reference Number X AN 1/30

Reference number or identification number as defined for a particular

Transaction Set, or as specified by the Reference Number Qualifier.

003050FEDOOA 10 January 13, 1997
869 - Order Status Inquiry

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

LIN Item Identification

050

HL

Detail

Optional

>1

To specify basic item identification data

12

3

4

5

6

7

8

9

10

11

12

13

14

11

2

If either LIN04 or LIN05

If either LIN06 or LIN07

If either LIN08 or LIN09

If either LDSflO orLDSfll

If either LIN12 orLIN13

If either LIN14 orLIN15

If either LIN16 orLIN17

IfeitherLIN18orLrN19

If either LIN20 orLIN21

If either LIN22 orLIN23

If either LIN24 orLIN25

If either LIN26 or LIN27

If either LIN28 or LIN29

If either LIN30 or LIN31

s present, then the other is required,

s present, then the other is required,

s present, then the other is required,

s present, then the other is required,

s present, then the other is required,

s present, then the other is required,

s present, then the other is required,

s present, then the other is required,

s present, then the other is required,

s present, then the other is required,

s present, then the other is required,

s present, then the other is required,

s present, then the other is required.

is present, then the other is required.

LIN01 is the line item identification

See the Data Dictionary for a complete list of ID's. LIN02 through LIN3 1 provide for fifteen (15) different product/service ID's for each

item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No.,

SKU.

1. When HL03 is code D, use this segment to provide a codified description ofthe

productfor which the report is being requested. Ifreports by multiple products are being requested, repeat this segmentfor each product using the codes listed in LIN02.

2. When BSJ03 is code PP, use to identify the selected item(s) for which status is requested.

Ref.

Pes.

LIN01

Must Use LIN02

Data

Element

350

235

Data Element Summary

Name Attributes

Assigned Identification O AN 1/11

Alphanumeric characters assigned for differentiation within a transaction set When HL03 is code D and multiple reports by product are requested, use to assign a number to differentiate between the product reports. For example, if a report by a specific NSNwas requested, L1N01 would cite the number 1. If

another reportfor a product with a different NSNwas requested, LIN01 would

cite the number 2. Ifa third reportfor a product identified by a

manufacturer's part number was requested, LIN01 would cite the number 3. Product/Service ID Qualifier M ID 2/2

Code identifying the type/source of the descriptive number used in

Product/Service ID (234)

CN Commodity Name

FS National Stock Number

The NSN shall be transmitted without dashes.

MG Manufacturer's Part Number

When used, LIN04/05 must be used with LIN04 citing

either code MFor ZB.

003050FED00A 11 January 13, 1997
869 - Order Status Inquiry

Must Use LIN03

LIN04

LIN05

Nl National Drug Code in 4-4-2 Format

N2 National Drug Code in 5-3-2 Format

N3 National Drug Code in 5-4-1 Format

N4 National Drug Code in 5-4-2 Format

ND National Drug Code (NDC)

PD Part Number Description

Use to indicate the plain text description ofan item

that cannot be identified by a number.

SV Service Rendered

ZZ Mutually Defined

When BSI03 is code PP andHLOS is code IB, 1C, or O, use to indicate the CLIN, SUBCUN, or ELJN, as

applicable, for which status is requested.

234 Product/Service ID M AN 1/40

Identifying number for a product or service

235 Product/Service ED Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in

Product/Service ID (234)

1. When LIN02 cites code MG, cite either code MFor ZB to identify the

manufacturer.

2. The use ofcode MFis preferred over code ZB as the method to identify the

manufacturer ofa part number.

MF Manufacturer

When used, cite the DUNSnumber ofthe manufacturer

in the following data element.

ZB Commercial and Government Entity (CAGE) Code

Use to indicate a manufacturer who can be identified

by a CAGE code.

234 Product/Service ID X AN 1/40

Identifying number for a product or service

003050FED00A 12 January 13, 1997
869 - Order Status Inquiry

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

110

Nl

Detail

Optional

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

1 At least one of N102 or N103 is required.

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

1 This segment, used alone, provides the most efficient method of providing

organizational identification. To obtain this efficiency the "ID Code" (N104) must

provide a key to the table maintained by the transaction processing party.

2 N105 and N106 further define the type of entity in N101

.

When HL03 is code V, 2 iterations ofthis Nl loop are REQUIRED, citing codes E8 and

SEinNlOL

Data Element Summary

Must Use

Ref.

Pes.

N101

N103

Data

Element

98

66

Name Attributes

Entity Identifier Code M ID 2/2

Code identifying an organizational entity, a physical location, or an individual

28 Subcontractor

When HL03 is code 25, use to indicate a subcontractor.

BY Buying Party (Purchaser)

When HL03 is code B, use to indicate the buying office.

C4 Contract Administration Office

When HL03 is code PA, use to indicate the contract

administration office.

E8 Inquiring Party

When HL03 is code V, use to indicate the party

requesting the information.

SE Selling Party

When HL03 is code V, use to indicate the party to whom the request is being sent. ST Ship To

When HL03 is code S, use to indicate the ship-to

location.

Zl Parry to Receive Status

When HL03 is code 21, use to indicate the party to whom the report is to be submitted ifdifferent than the

inquiring party.

Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification

Code (67)

While the federal EDIprogram uses the DUNS number, other government

users ofthis implementation convention may require the use ofother and

additional numbersfor a transition period in order to cross reference existing

data bases.

1 D-U-N-S Number, Dun & Bradstreet

Use ofthe DUNs and DUNs +4 number is preferred

over other codes to identify an entity.

003050FEDOOA 13 January 13, 1997
869 - Order Status Inquiry

N104 67

9 D-U-N-S+4, D-U-N-S Number with Four Character

Suffix

Use ofthe DUNs and DUNs +4 number is preferred over other codes to identify an entity.

10 Department of Defense Activity Address Code

(DODAAC)

Use to indicate a Department ofDefense or Civilian

AgencyActivity Address Code.

33 Commercial and Government Entity (CAGE)

Identification Code X AN 2/20

Code identifying a party or other code

003050FED00A 14 January 13, 1997
869 - Order Status Inquiry

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

PER Administrative Communications Contact

160

Nl

Detail

Optional

3

To identify a person or office to whom administrative communications should be

directed

1 If either PER03 or PER04 is present, then the other is required.

2 If either PER05 or PER06 is present, then the other is required.

3 If either PER07 or PER08 is present, then the other is required.

Use this segment to provide names, communication numbers and titles ofindividuals

associated with the entity cited in the same Nl loop.

Data Element Summary

Ref.

Pes.

Must Use PER01

PER02

PER03

PER04

PER05

Data

Element

366

93

365

364

365

Name Attributes

M ID 2/2

003050FED00A

Contact Function Code

Code identifying the major duty or responsibility of the person or group

named

AC Administrative Contracting Officer

BD Buyer Name or Department

IC Information Contact

PC Purchasing Contracting Officer (PCO)

SU Supplier Contact

When Ml01 is code SE, use to indicate the party at the

selling organization to whom this inquiry should be

directed.

Name O AN 1/35

Free-form name

Use to identify the name ofa point ofcontact. Last name, followed byfirst

name, is preferred. Ifthe whole name is longer than 35 characters, the use of

initialsfor the first name is recommended. PER09 may be used to cite the

party's title or office symbol number.

Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

AU Defense Switched Network

EM Electronic Mail

FX Facsimile

TE Telephone

Use to indicate commercial telephone number. Include

the area code.

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

All numbers, other than those associated with code EM, shall be transmitted as a continuous number with no extraneous characters.

Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

Use to identify a second communications numberfor the party cited in

PER02. For example, ifPER03/04 cites a telephone number, PER05/06 can

be used to cite a FAXnumber.

15 January 13, 1997
869 - Order Status Inquiry

PER06 364

PER07 365

PER08 364

PER09 443

AU Defense Switched Network

EM Electronic Mail

EX Telephone Extension

Use only ifPER03 is used citing codeAU or TE.

FX Facsimile

TE Telephone

Use to indicate commercial telephone number. Include

the area code.

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

All numbers, other than those associated with code EM, shall be transmitted as a continuous number with no extraneous characters.

Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

Use to identify a third communications numberfor the party cited in PER02.

AU Defense Switched Network

EM Electronic Mail

EX Telephone Extension

Use only ifPER05 is used citing code AU or TE.

FX Facsimile

TE Telephone

Use to indicate commercial telephone number. Include

the area code.

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

All numbers, other than those associated with code EM, shall be transmitted as a continuous number with no extraneous characters.

Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number

Use, ifnecessary, to provide the title or an office symbol number ofthe party

cited in PER02.

003050FED00A 16 January 13, 1997
869 - Order Status Inquiry

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

020

Summary

Mandatory

1To indicate the end of the transaction set and provide the count of the transmitted

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

SE is the last segment of each transaction set.

Data Element Summary

Ref. Data

Pes. Element Name Attributes

Must Use SE01 96 Number of Included Segments M NO 1/10

Total number of segments included in a transaction set including ST and SE

segments

Must Use SE02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Cite the same number carried in ST02.

003050FED00A 17 January 13, 1997

Technical Publications

Periodical

Journal of Research of the National Institute of Standards and Technology—Reports NIST research

and development in those disciplines of the physical and engineering sciences in which the Institute is

active. These include physics, chemistry, engineering, mathematics, and computer sciences. Papers cover a broad range of subjects, with major emphasis on measurement methodology and the basic technology

underlying standardization. Also included from time to time are survey articles on topics closely related to the Institute's technical and scientific programs. Issued six times a year.

Nonperiodicals

Monographs—Major contributions to the technical literature on various subjects related to the

Institute's scientific and technical activities. Handbooks—Recommended codes of engineering and industrial practice (including safety codes) developed in cooperation with interested industries, professional organizations, and regulatory bodies.

Special Publications—Include proceedings of conferences sponsored by NIST, NIST annual reports, and

other special publications appropriate to this grouping such as wall charts, pocket cards, and bibliographies.

National Standard Reference Data Series—Provides quantitative data on the physical and chemical

properties of materials, compiled from the world's literature and critically evaluated. Developed under a worldwide program coordinated by NIST under the authority of the National Standard Data Act (Public

Law 90-396). NOTE: The Journal of Physical and Chemical Reference Data (JPCRD) is published

bimonthly for NIST by the American Chemical Society (ACS) and the American Institute of Physics (AIP).

Subscriptions, reprints, and supplements are available from ACS, 1155 Sixteenth St., NW, Washington, DC

20056.

Building Science Series—Disseminates technical information developed at the Institute on building

materials, components, systems, and whole structures. The series presents research results, test methods, and

performance criteria related to the structural and environmental functions and the durability and safety

characteristics of building elements and systems.

Technical Notes—Studies or reports which are complete in themselves but restrictive in their treatment of

a subject. Analogous to monographs but not so comprehensive in scope or definitive in treatment of the

subject area. Often serve as a vehicle for final reports of work performed at NIST under the sponsorship of

other government agencies.

Voluntary Product Standards—Developed under procedures published by the Department of Commerce

in Part 10, Title 15, of the Code of Federal Regulations. The standards establish nationally recognized

requirements for products, and provide all concerned interests with a basis for common understanding of

the characteristics of the products. NIST administers this program in support of the efforts of private-sector

standardizing organizations.

Order the following NIST publications—FIPS and NISTIRs—from the National Technical Information

Service, Springfield, VA 22161.

Federal Information Processing Standards Publications (FIPS PUB)—Publications in this series

collectively constitute the Federal Information Processing Standards Register. The Register serves as the

official source of information in the Federal Government regarding standards issued by NIST pursuant to the Federal Property and Administrative Services Act of 1949 as amended, Public Law 89-306 (79 Stat.

1 127), and as implemented by Executive Order 1 1717 (38 FR 12315, dated May 11, 1973) and Part 6 of

Title 15 CFR (Code of Federal Regulations).

NIST Interagency Reports (NISTIR)—A special series of interim or final reports on work performed by

NIST for outside sponsors (both government and nongovernment). In general, initial distribution is handled

by the sponsor; public distribution is by the National Technical Information Service, Springfield, VA 22161,

in paper copy or microfiche form.
BSoUO c/5

*- '-5

C1<|—

<L>

—

Q § . o P z

OS

on

00o3 o eo o L cU u

c 1

'I

£

.2 >. O £