AlllOS 13iaTt.

PUBLICATIONS

4

Hlllillililli()iiiiiliili<ikililillbll H

t

Nisr

X

100

.U57

NO.881-23

1997

Special Publication 881-23

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 870

Order Status Report

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology

NIST Special Publication 881-23

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 870

Order Status Report

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

Techncriogy 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-23

Natl. Inst. Stand. Technol. Spec. Publ. 881-23, 28 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
870 Order Status Report

Functional Group ID=RS

Introduction:

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

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

transaction set can be used to report on the current status of a requirement forecast, an entire purchase order, selected

line items on a purchase order, selected products/services on a purchase order, or purchase orders for a specific

customer in their entirety or on a selection basis. The transaction set can also be used to report on the current status of single or multiple requisitions. The report format allows for the inclusion of "reasons" relative to the status. This

transaction set may also be used to update the supplier's scheduled shipment or delivery dates. This transaction set can result from either an inquiiy or a prearranged schedule agreed to by the trading partners.

Notes:

1. Contractors use this transaction set to respond to a delivery status inquiry or to generate a revised delivery

forecast.

2. When permitted by an award instrument, this transaction set may be used by contractors to satisfy a CDRL

requirement to submit delivery status reports

3. This transaction set may not be used in lieu ofan 865 transaction set to request a change to the delivery

requirements ofan award instrument.

Heading:

Pos. Seg. Req. Loop Notes and

No. ID Name Des. Max.Use Repeat Comments

Must Use 010 ST Transaction Set Header M 1

Must Use 020 BSR Beginning Segment for Order Status Report M 1 N/U 040 REF Reference Numbers O 12 N/U 042 TD3 Carrier Details (Equipment) O 1 NAJ 043 TD4 Carrier Details (Special Handling, or O 1 Hazardous Materials, or Both)

N/U 044 TD5 Carrier Details (Routing Sequence/Transit O 1 Time)

Must Use 050 Nl

^^^^^^^>^>^^^^.•.'.•^.•.•^^^^^^>^^^^^-•^^^^x^.•^^^^^Iw^^A^^^^ Name o 1 N/U 060 N2 Additional Name Information o 2 N/U 070 N3 Address Information o 2

N/U 080 N4 Geographic Location o 1 N/U 090 REF Reference Numbers 0 12

100 PER Administrative Conununications Contact o 3

N/U 105 PWK Paperworic o 1

N/U 110 DTM Date/Time Reference o 10

N/U 120 LM Code Source Information ^^^^^

0 1 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

N/U 130 LQ Industry Code M 100

Detail:

003050FED00A January 13, 1997
870 - Order Status Report

Pos. No.Seg.

IB Name

Req.

Des. Max.Use ^^^^^^

Loop

Repeat

Notes and

Comments

Must Use 010 HL Hierarchical Level

\ •. -. > '

1 N/U 020 PRF Purchase Order Reference

LOCfiPm-iSR

o 1 m

030 ISR Item Status Report 1 N/U 040 PID Product/Item Description o 6

N/U 050 QTY Quantity o 4

060 REF lit 17

N/U 070 PER Administrative Communications Contact O 3

080 DTM Date/Time Reference o 10 N/U 086 CS Contract Summary

IOCS' ID-Ni

o 3 nl

090 Nl

:'Xv:':-:*:o:-:':-:-:-:-:vXv:v:;X^^^ Name o 1 N/U 100 N2 Additional Name Information o 2

N/U 110 N3 Address Information o 2

N/U 120 N4 Geographic Location o 1 N/U 130 REF Reference Numbers o 12 N/U 140 PER Administrative Communications Contact o 3

LOOPID-IAt ^ «p 16

144 LM Code Source Information o 1

."bSV^.V.'.V.V.'.W.WA.VJVJV.WAV. V

Must Use 145 LQ Industry Code M 100

150 POl Baseline Item Data i

'"' , - i,m

N/U 155 CUR Currency o 1 N/U 160 SLN Subline Item Detail o 100

N/U 170 P03 Additional Item Detail o 1

N/U 180 PID Product/Item Description o 1000

N/U 190 MEA Measurements o 40

N/U 200 PKG Maricing, Packaging, Loading o 25

210 ISR Item Status Report O 1

N/U 220 PID Product/Item Description o 6

230 QTY Quantity o 4

NAJ 240 DTM Date/Time Reference o 10 N/U 250 Nl Name o 1 NAJ 251 N2 Additional Name Information o 2

N/U 252 N3 Address Information o 2

N/U 253 N4 Geographic Location o

N/U 260 TDl Carrier Details (Quantity and Weight) 0

IN/ U

N/U 280

TTJS 1 LfJ

TD3

Time)

Carrier Details (Equipment)

o

o

N/U \

N/U

290

300

704

REF

Carrier Details ^Soecial Handling or Hazardous Materials, or Both)

Reference Numbers

o

o 12

N/U 310 SAC Service, Promotion, Allowance, or Charge

Information o 25

003050FEDOOA 2 January 13, 1997
870 - Order Status Report

320 LM

Must Use 330 LQ

N/U 340 LX

NAJ 350 REF

N/U 360 Nl

N/U 370 DTM

N/U 380 LM

N/U 390 LQ

Summary:

N/U

Pos. No. 010

Seg.

ID

CTT

Must Use 020 SE

Code Source Infonnation

Industry Code

Assigned Number

Reference Numbers

Name

Date/Time Reference

Code Source Informauon

Industry Code

Name

Transaction Totals

Transaction Set Trailer

O

M

1

100

o

o

o

o

1

>1

1

10

n2

O

M

1

100

Req.

Pes. O

M

Mm.Usc

1

1

Loop

Repeat

Notes and

Comments

n3

Transaction Set Notes

1. Use is limited to intra-organizational transactions.

2. The LX loop conveys serial number, lot nmnber, and inventory data.

3. The number of line items (CTTO 1) is the accumulation of the number of HL segments. If used, hash total

(CTT02) is the sum of the value of quantities ordered (PO102) for each POl segment

003050FED00A 3 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

ST Transaction Set Header

010

Heading

Mandatoiy

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 STOl 143 Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

870 X12.23 Order Status Report

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

Identifying control number that must be unique within the transaction set fimctional 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 4 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

BSR Beginning Segment for Order Status Report

020

Comments:

Heading

Mandatory

1To indicate the beginning of an Order Status Report.

1 BSR03 indicates a status report document number assigned by the sender.

2 BSR04 indicates the date of this report from the sender.

3 BSR07 indicates the time of this report from the sender.

4 BSR08 indicates a status report docimient number assigned by the inquirer.

5 BSR09 indicates the date this report was requested from the sender by the inquirer.

6 BSRIO indicates the time this report was requested from the sender by the inquirer.

Ref.

Pes.

Must Use BSROl

Must Use BSR02

Data

Element

850

847

Data Element Summary

Name Attributes

Status Report Code M D) 1/2

Code indicating the reason for sending the report

1 Response to an Order Status Inquiry (869)

2 Prearranged Schedule or Agreement

Use to indicate this report is being submitted as a CDRL deliverable as required by an award instrument

3 Unsolicited Report

Use to indicate a contractor initiated Order Status

Report.

Order/Item Code M ID 1/2

Code identifying a group of orders and items

1. Use to identify the extent ofthe delivery information being provided

2. When BSROl is code 1, cite the same code carried in BSI03 ofthe 869

transaction set.

AO All orders - items with changed status Use to indicate a status report is providedfor all items

that have previously been reported with changed

delivery status on all award instruments that are not

physically complete.

CA All Orders - All Items

7. Use to indicate a status report is providedfor every

item on all award instruments that are notphysically

complete.

CO

PA

PO

All Orders - Unshipped Items

Use to indicate a status report is providedfor all unshipped items on all award instruments that are not

physically complete.

Selected Orders - All Items

Use to indicate a status report is providedfor all items

in specified orders.

Selected Orders - Unshipped Items

00305OFEDO0A 5 January 13, 1997
870 - Order Status Report

Use to indicate a status report is providedfor all

| unshipped items in specified orders. \

I PP Selected Orders - Selected Items

Use to indicate a status report is providedfor identified

j items in specified orders.

Must Use BSR03 127 Reference Number M AN 1/30

Reference number or identification nmnber 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., 824 Application Advice.

Must Use BSR04

BSR08

BSRll

373 Date M DT 6/6

Date (YYMMDD)

Use to identify the date ofthis transaction set

127 Reference Number O AN 1/30

Reference number or identification number as defined for a particular

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

When BSROl is code 1, use to identify the unique reference number ofthe 869

Order Status Inquiry transaction set to which this transaction set is responding. This is the same number carried in BSIOl ofthe 869 transaction

set. 353 Transaction Set Purpose Code O ID 2/2

Code identifying purpose of transaction set 00

01

07

Original

Use to indicate an original report.

Cancellation

Use to indicate the cancellation ofapreviously

transmitted 870 transaction set. DupUcate

Use to indicate a duplicate transmission ofan original

report.

003O5OFEDO0A 6 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

050

Nl

Heading

Optional (Must Use)

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 fiulher define the type of entity in NlOl.

At least two iterations ofthis Nl loop are REQUIRED, citing codes FR and TO in NlOl.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use NlOl 98 Entity Identifier Code M ID 2/2

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

E8 Inquiring Party

Use to indicate the party who initiated a request (869

transaction set) for the reportprovided, ifother than

the TO party.

FR Message From

Use to indicate the originator ofthe transaction set. TO Message To

Use to indicate the recipient ofthe transaction set

N103 66 Identification Code Qualifier X ID 1/2

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

Code (67)

While thefederal EDIprogram uses the DUNSnumber, 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.

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)

N104 67 Identification Code X AN 2/20

Code identifying a party or other code

003050FED00A 7 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

PER Administrative Communications Contact

100

Nl

Heading

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.

Ref.

Pes,

Must Use PEROl

PER02

PER03

PER04

PER05

Data

Element

366

93

Data Element Summary

365

364

365

Name Attributes

Contact Function Code M ID 2/2

Code identifying the major duty or responsibihty of the person or group named

IC Information Contact

Name O AN 1/35

Free-form name

Use to identify the name ofapoint ofcontact Last name, followed byfirst

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

initialsfor thefirst 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 a commercial telephone number.

Include the area code.

Communication Number X AN 1/80

Complete communications number including cotmtiy or area code when

appUcable

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 nimiber

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 cited a FAXnumber.

AU

EM

EX

FX

TE

Defense Switched Network

Electronic Mail

Telephone Extension

Use only ifPEROS is used citing codeAU or TE.

Facsimile

Telephone

Use to indicate a commercial telephone number.

003050FED00A 8 January 13, 1997
870 - Order Status Rqrait

PER06 364

PER07 365

PER08 364

PER09 443

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.

Conmiunication 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 ifPEROS is used citing code AUor TE.

FX Facsimile

TE Telephone

Use to indicate a 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 office symbol number ofthe party cited

in PER02.

003050FED00A 9 January 13, 1997
870 - Order Status Report

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 HLOl shall contain a imique alphanumeric number for each occurrence of the HL

segment in the transaction set For example, HLOl could be used to indicate the

number of occurrences of the HL segment, in which case the value of HLOl would

be " 1

" for the initial HL segment and would be incremented by one in each

subsequent HL segment within the transactioa

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 transactioa For example,

HL03 is tised to indicate that subsequent segments in the HL loop form a logical

grouping of data refening 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 data level within a Delivery Status Report and the

dependencies among various levels.

2. For example, ifthe report was being submitted at the award instrument level, HL03

would contain code IB, the award instrument number being reported would be identified

in the 2/REF/060 segment the citing code CT in KEFOl and the applicable status would

be provided in the 2/ISR/030 segment.

3. Ifthe report went down to the CUN/SUBCUN/EUN level, these would be identified

in the POl segment in POlOl and the status applicable to the CUN/SUBCUN/EUN

would be provided in the 2/ISR/210 loop.

Ref.

Pes.

Must Use HLOl

Data

Element

628

HL02 734

Data Element Summary

Name Attributes

Hierarchical m Number M AN 1/12

A imique 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. Hierarchical Parent D) Number O AN 1/12

Identification niunber of the next higher hierarchical data segment that the data

segment being described is subordinate to Use to identify aprevious HL segment to which the current HL segment is

subordinate. This is a number cited in HLOl. For example, the second HL

segment may be subordinate to thefirst HL segment, therefore, the number 1 would be cited; or the sixth HL segment may be subordinate to thefourth HL

segment, therefore, the number 4 would be cited. Ifan HL segment is not

subordinate to another HL segment, this data element is left blank.

Must Use HL03 735 Hierarchical Level Code M n> 1/2

003050FED00A 10 January 13, 1997
870 - Order Status Report

Code defining the characteristic of a level in a hierarchical structure Use to identify the data level ofthe report.

25 Subgroup

Use to indicate a hierarchical levelfor data applicable

to a specified subcontractor.

B Buyer's Location

1. Use to indicate a hierarchical levelfor data

associated with award instruments issued by a specific

buying activity.

2. Use ofthis code is only necessary ifa report by

multiple buying offices was requested.

C Date

1. Use to indicate a hierarchical levelfor data

applicable to a specified delivery date

2. Use ofthis code is only necessary ifa report by

multiple delivery dates or multiple delivery date ranges

was requested

D Product Description

Use to indicate a hierarchical levelfor data identified

by a product description, e.g., NSN, manufacturer part

number, etc. , or by a type ofservice.

2. Use ofthis code is only necessary ifa report by

multiple product descriptions was requested. Identify

the product being reported in the POl segment.

Contract

Use to indicate a hierarchical levelfor data applicable

to specified award instrument, e.g., contract, basic

contract, purchase order, basic ordering agreement,

etc. Contract Data Requirements List (CDRL)

Use to indicate a hierarchical levelfor data applicable

to a specified exhibit.

Order

Use to indicate a hierarchical levelfor data applicable

to a specified delivery order, call, or release.

Primary Administrator

Use to indicate a hierarchical levelfor data associated

with award instruments administered by a specified

contract administration office.

2. Use ofthis code is only necessary ifa report by

multiple contract administration offices was requested.

S Shipment

7. Use to indicate a hierarchical levelfor data

applicable to a specified delivery location.

2. Use ofthis code is only necessary ifa report by

multiple delivery locations was requested.

HL04 736 Hierarchical ChUd 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.

IB

IC

O

PA

003050FEDO0A 11 January 13, 1997
870 - Order Status Report

0 No Subordinate HL Segment in This Hierarchical

Structure.

1 Additional Subordinate HL Data Segment in This

Hierarchical Structure.

003050FED00A 12 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

ISR Item Status Report

030

ISR

Detail

Optional

1To specify detailed purchase order/item status

1 If ISRO1 specifies a date, ISR02 is required.

Use this segment to provide the delivery status applicable to all ofthe items in an award

instrument. Ifthe status varies by item, use the 2/ISR/210 segment.

Must Use

Ref.

Pes.

ISROl

Data Element Summary

Data

Element

368

Name Attributes

ISR02 373

Shipment/Order Status Code M ID 2/2

Code indicating the status of an order or shipment or the disposition of any

difference between the quantity ordered and the quantity shipped for a line

item or transaction

Use to identify the status ofthe award instrument or exhibit Where additional

information regarding a delayed delivery or shipment is necessary, use the

2/LQ/145 segment to provide the information in a codifiedform.

CL

ED

ID

IN

NY

SH

UN

Complete

Use to indicate the completion ofa service. Cite the

completion date in ISR02.

Expect to Ship By (Date)

Use to indicate the date on -which the contractor expects

to ship the items. Ifthe shipment date is a changefrom

the date required to meet the contractual delivery date,

cite a reasonfor this change in the 2/LQ/145 segment

citing code 12 in LQOl.

InsufQcient Information

Use to indicate the contractor has no record ofthe

award instrument cited in REFOl/02.

In Process

Use to indicate delivery will be made in accordance

with the award instrument schedule.

No Shipping Schedule

Use to indicate no shipping schedule can be provided

due to reasons provided in the 2/LQ/145 citing code 14

in LQOl.

Shipped (Date)

Cite the shipment date in ISR02. Ifmore than one

shipment was made, cite the last shipment date. If

applicable, provide additional information in the

2/LQ/145 segment citing code 14 in LQOl.

Unavailable

Use to indicate the contractor will not perform the

award instrument cited in REFOl/02.

Date O DT 6/6

Date (YYMMDD)

When applicable, use to identify a date associated with a code cited in ISROl.

003050FEDOOA 13 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

REF Reference Numbers

060

HL

Detail

Optional

12

To specify identifying numbers.

1 At least one of REF02 or REF03 is required.

When HL03 is code IB, IC, or O, use this segment to identify the number ofthe award

instrument number; exhibit reference; or the delivery order, call or release.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use REFOl 128 Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

CT Contract Number

When HL03 is code IB, use to indicate the number ofan 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 letter assigned to a Contract Data Requirements List (CDRL)

that requires a contract deliverable being provided in

this transaction set.

REF02 127 Reference Number X AN 1/30

Reference nimiber or identification number as defined for a particular

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

003050FEDOOA 14 January 13, 1997
870 - Order Status Rqjort

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Conunents:

Notes:

DTM Date/Time Reference

080

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 delivery dates or range ofdates

applicable to the report.

2. Each DTMsegment that identifies a specific delivery date or range ofdates, must be

associated with a specific HL segment that cites code C in HL03.

3. Ifthe 869 transaction set requested statusfor a single delivery date or range ofdates,

this segment is not used.

Ref.

Pes.

Must Use DTMOl

DTM02

DTM05

DTM06

DTM07

Data

Element

374

373

624

1250

Attributes

M ID 3/3

Data Element Summary

Name

Date/Time Qualifier

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

996 Required Delivery

Use to indicate the specific delivery date applicable to the report.

Date X DT 6/6

Date (YYMMDD)

Century 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. Use to identify a range ofdates to which the report applies.

2. The 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 15 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Nl Name

090

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 efBcient 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 NIO 1. U^en HL03 is code S, use this segment to identify the ship-to location applicable to the

report.

Ref.

Pes.

Must Use NlOl

N103

Data

Element

98

66

N104 67

Data Element Summary

Name Attributes

Entity Identifier Code M ID 2/2

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

ST Ship To

Identification Code Qualifier X ID 1/2

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

Code (67)

While thefederal EDIprogram uses the DUNSnumber, 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.

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 16 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

LM Code Source Information

144

LM

Detail

Optional

1To transmit standard code list identification information

1 LM02 identifies the applicable industry code list source information.

Use this loop to identify coded data applicable to a delivery date or shipment date that

applies to all ofthe line items in the award instrument When the coded data varies by

line item, use the 2/LW320 loop.

Must Use

Ref.

Pes.

LMOl

LM02

Data

Element

559

822

Attributes

M ID 2/2

Data Element Summary

Name

Agency Qualifier Code

Code identifying the agency assigning the code values

Use any code.

Refer to 003050 Data Element Dictionary for acceptable code values.

Source Subqualifier O AN 1/15

A reference that indicates the table or text maintained by the Source Qualifier

When LQOl is code ZZ, identify the code list that contains the code cited in

LQ02.

003050FED00A 17 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

LQ Industry Code

145

LM

Detail

Mandatory

100

Code to transmit standard industry codes

1 If LQO1 is present, then LQ02 is required

Use this segment to provide coded data that provides the reasonfor a delivery date or shipment date cited in ISR02 or to other codes cited in ISROl.

Ref.

Pes,

LQOl

LQ02

Data

Element

1270

1271

Attributes

O ID 1/3

Data Element Summary

Name

Code List Qualifier Code

Code identifying a specific industry code list

12 Reason for Contract Delivery Date Revision Code

When ISROl is code ED, use to indicate the reasonfor

the revised delivery date.

14 Contract Shipment Advice Code

When ISROl is code NYor SH, use, ifapplicable, to indicate additional information regarding a shipment.

7Z Mutually Defined

Use to indicate that a code list is identified in LM02.

Industry Code X AN 1/20

Code indicating a code from a specific industry code list Use to cite a code that is contained in a code source list applicable to the

qualifier code cited in LQOl or when LQOl is code ZZ, in a code source list cited in LM02.

»

003050FEDOOA 18 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

POl

Semantic Notes:

Comments:

Baseline Item Data

150

POl

Detail

Optional

1To speciiy basic and most frequently used line item data

1 If PO103 is present, then PO102 is required.

2 If PO105 is present, then PO104 is required.

3 If either PO106 or PO107 is present, then the other is required.

4 If either PO108 or PO109 is present, then the other is required.

5 If either POl 10 or POl 11 is present, then the other is required.

6 If either PO1 1 2 or PO1 1 3 is present, then the other is required.

7 If either POl 14 or P0115 is present, then the other is required.

8 If either POl 16 or POl 17 is present, then the other is required.

9 If either P0118orP0119is present, then the other is required.

10 If either PO120 or P0121 is present, then the other is required.

11 If either P0122 or P0123 is present, then the other is required.

12 If either POl24 or POl25 is present, then the other is required.

1 See the Data Dictionary for a complete list of ID's. 2 PO101 is the line item identification.

3 PO106 through P0125 provide for ten (10) diEferent product/service ID's per each

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

SKU.

Notes: 1. When HL03 is code IB, IC, or O, use this loop to provide delivery statusfor a CLIN,

SUBCUN, or EUNapplicable to an award instrument; delivery order, call, release; or

exhibit. Only POl01 shall be used Status applicable to the CLIN, SUBCUNor EUN

will be provided in the 2/ISR/2I0 loop.

2. When HL03 is code D, use this segment to identify the product to which the report

applies. Only POl06/07/08/09 may be used

Ref.

Pes.

POlOl

PO106

Data

Element

350

235

Data Element Summary

Name Attributes

Assigned Identification O AN 1/11

Alphanumeric characters assigned for differentiation within a transaction set

I. Use only when HL03 is code IB, IC, or O, to identify the CLIN, SUBCUN,

or EUN.

Product/Service ID Qualifier X ID 2/2

Code identifying the type/soiu"ce of the descriptive number used in

Product/Service ID (234)

When HL03 is code D, use to identify the product to which the report applies.

CN Commodity Name

Use to indicate the commodity name. FS National Stock Number

MG Manufacturer's Part Number

When used, POl08/09 must be used with POl 08 citing

either code MFor 73.

Nl National Drug Code in 4-4-2 Format

N2 National Drug Code in 5-3-2 Format

003050FED00A 19 January 13, 1997
870 - Order Status Report

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.

PO107 234 Product/Service ID X AN 1/40

Identifying number for a product or service

PO108 235 Product/Service ID QualiHer X ID 2/2

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

Product/Service ID (234)

1. When POl06 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 thefollowing data element

ZB Commercial and Government Entity (CAGE) Code

Use to indicate a manufacturer who can be identified by a CAGE code.

PO109 234 Product/Service ID X AN 1/40

Identifying nimiber for a product or service

003050FED00A 20 January 13, 1997
870 - Order Status Report

Segment: ISR Item Status Report

Position: 210

Loop: ISR

Level: Detail

Usage: Optional

Max Use: 1 Purpose: To specify detailed purchase order/item status Syntax Notes:

Semantic Notes: 1 If ISROl specifies a date, ISR02 is required.

Comments:

Notes: Use this segment when the delivery status varies by item within an award instrument. If

the delivery status is the samefor all ofthe items in an award instrument, use the

2/IRS/030 segment

Data Element Summary

Ref. Data

Des, Element Name Attributes

Must Use ISROl 368 Shipment/Order Status Code M ID 2/2

Code indicating the status of an order or shipment or the disposition of any

difference between the quantity ordered and the quantity shipped for a line

item or transaction

CL Complete

Use to indicate the completion ofa service. Cite the

completion date in ISR02.

CP Partial Shipment on (Date), Considered No Backorder

Use to indicate a shipment ofa quantity less than the

contract quantity and that the contractor considers the

order complete. Identify the shipment quantity in the

2/QTY/230 segment and ifapplicable, provide

additional information in the 2/LQ/330 segment citing

code 14 in LQOl. Cite the shipment date in ISR02.

ED Expect to Ship By (Date)

Use to indicate the date on which the contractor expects

to ship the item. Ifthe shipment date is a changefrom

the date required to meet the contractual delivery date,

cite a reasonfor this change in the 2/LQ/330 segment

citing code 12 in LQOl.

IN In Process

Use to indicate delivery will be made in accordance

with the award instrument schedule.

NY No Shipping Schedule

Use to indicate no shipping schedule can be provided

due to reasons provided in the 2/LQ/330 segment citing

code 14 in LQOl.

PR Partial Shipment

Use to indicate a shipment ofa quantity less than the

contract quantity. When used, identify the quantity of

the partial shipment in the 2/QTY/230 segment and if

applicable, provide additional information in the

2/LQ/330 segment citing code 14 in LQOl. Cite the

shipment date in ISR02.

SH Shipped (Date)

Cite the shipment date in ISR02. Ifmore than one

shipment was made, cite the last shipment date. If

applicable, provide additional information in the

2/LQ/330 segment citing code 14 in LQOl.

003050FED00A 21 Januaiy 13, 1997
870 - Order Status Rq)ort

ISR02 373 Date O DT 6/6

Date (YYMMDD)

Mien applicable, use to provide a date applicable to a code cited in ISROl.

003050FED00A 22 January 13, 1997
870 - Order Status Rqrart

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Must Use

Ref.

Pes.

QTYOl

Must Use QTY02

QTY03

QTY Quantity

230

ISR

Detail

Optional

4

To specify quantity information

When ISROl is code CP or PR, use to identify the quantity shipped and the portion ofthe

shipped quantity that was inspected and accepted by the government.

Data

Element

673

Attributes

M ID 2/2

380

355

Data Element Summary

Name

Quantity Qualifier

Code specifying the type of quantity

39 Shipped Quantity

QA Quantity Approved

Use to indicate the quantity ofthe shipment that was

inspected and accepted by the government

Quantity M R 1/15

Niuneric value of quantity

Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or maimer in

which a measivement has been taken

Refer to 003050 Data Element Dictionary for acceptable code values.

003050FED00A 23 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref.

Pes.

Must Use LMOl

LM02

LM Code Source Information

320

LM

Detail

Optional

1To transmit standard code list identification information

1 LM02 identifies the applicable industry code list soiu-ce information.

Use this loop to provided coded data applicable to the delivery date or shipment date of

the item cited in POIOI.

Data Element Summary

Data

Element Name Attributes

559 Agency Qualifier Code M ID 2/2

Code identilying the agency assigning the code values

Use any code.

Refer to 003050 Data Element Dictionary for acceptable code values.

822 Source Subqualifier O AN 1/15

A reference that indicates the table or text maintained by the Source Qualifier

When LQOl is code ZZ, identify the code list that contains the code cited in

LQ02.

O03O5OFEDO0A 24 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

LQ Industry Code

330

LM

Detail

Mandatory

100

Code to transmit standard industry codes

1 If LQOl is present, then LQ02 is required.

Use this loop to provide coded data that provides the reasonfor a delivery date or a

shipment datefor the item cited in POlOl orfor coded data applicable to codes in

ISROl.

Ref.

Pes.

LQOl

LQ02

Data

Element

1270

1271

Data Element Summary

Name Attributes

Code List Qualifier Code O ID 1/3

Code identifying a specific industry code list 12 Reason for Contract Delivery Date Revision Code

When ISROl is code ED, use to indicate the reasonfor

the revised delivery date.

14 Contract Shipment Advice Code

When ISROl is code CP, NY, PR, or SH, use, if

applicable, to indicate additional information

regarding a shipment.

ZZ Mutually Defined

Use to indicate that a code list is identified in LM02.

Industry Code X AN 1/20

Code indicating a code firom a specific industry code list Use to cite a code that is contained in a code source list applicable to the

qualifier code cited in LQOl or when LQOl is code ZZ, in a code source list cited in LM02.

003050FEDOOA 25 January 13, 1997
870 - Order Status Report

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Syntax Notes:

Semantic Notes:

Comments:

SE Transaction Set Trailer

020

Summary

Mandatoiy

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

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

1 SE is the last segment of each transaction set.

Data Element Summary

Ref. Data

Des. Element Name Attributes

Must Use SEOl 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 fimctional group assigned by the originator for a transaction set Cite the same number carried in ST02.

003050FED00A 26 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-^om 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. 1127), and as implemented by Executive Order 11717 (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.
c

- >2 .2 >^ B §

O £