PUBLICATIONS

NIST Special Publication 881-56

1

iinmini^S

HI 11

Federal Implementation Guideline

for Electronic Data Interchange

30

ASC X12 003050 Transaction Set 855

Purchase Order Acknowledgment

(Revision 1)

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology

.881-56

58
rhe National Institute of Standards and Technology was established in 1988 by Congress to "assist industry in the development of technology . . . needed to improve product quality, to modernize manufacturing processes,

to ensure product reliability . . . and to facilitate rapid commercialization ... of products based on new scientific discoveries." NIST, originally founded as the National Bureau of Standards in 1901, works to strengthen U.S. industry's

competitiveness; advance science and engineering; and improve public health, safety, and the environment. One

of the agency's basic functions is to develop, maintain, and retain custody of the national standards of

measurement, and provide the means and methods for comparing standards used in science, engineering,

manufacturing, commerce, industry, and education with the standards adopted or recognized by the Federal Government.

As an agency of the U.S. Commerce Department's Technology Administration, NIST conducts basic and

applied research in the physical sciences and engineering, and develops measurement techniques, test methods, standards, and related services. The Institute does generic and precompetitive work on new and

advanced technologies. NIST's research facilities are located at Gaithersburg, MD 20899, and at Boulder, CO 80303.

Major technical operating units and their principal activities are listed below. For more information contact the Publications and Program Inquiries Desk, 301-975-3058.

Office of the Director

• National Quality Program

• International and Academic Affairs

Technology Services

• Standards Services

• Technology Partnerships

• Measurement Services

• Technology Innovation

• Information Services Advanced Technology Program

• Economic Assessment

• Information Technology and Applications

• Chemical and Biomedical Technology

• Materials and Manufacturing Technology

• Electronics and Photonics Technology

Manufacturing Extension Partnership

Program

• Regional Programs

• National Programs

• Program Development

Electronics and Electrical Engineering

Laboratory

• Microelectronics

• Law Enforcement Standards

• Electricity

• Semiconductor Electronics

• Electromagnetic Fields'

• Electromagnetic Technology'

• Optoelectronics'

Chemical Science and Technology

Laboratory

• Biotechnology

• Physical and Chemical Properties"

• Analytical Chemistry

• Process Measurements

• Surface and Microanalysis Science

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Optical Technology

• Ionizing Radiation

• Time and Frequency'

• Quantum Physics'

Materials Science and Engineering

Laboratory

• Intelligent Processing of Materials

• Ceramics

• Materials Reliability'

• Polymers

• Metallurgy

• NIST Center for Neutron Research

Manufacturing Engineering

Laboratory

• Precision Engineering

• Automated Production Technology

• Intelligent Systems

• Fabrication Technology

• Manufacturing Systems Integration

Building and Fire Research

Laboratory

• Structures

• Building Materials

• Building Environment

• Fire Safety Engineering

• Fire Science

Information Technology Laboratory

• Mathematical and Computational Sciences^

• Advanced Network Technologies

• Computer Security

• Information Access and User Interfaces

• High Performance Systems and Services

• Distributed Computing and Information Services

• Software Diagnostics and Conformance Testing

'At Boulder. CO 80303. ^Some elements at Boulder. CO.
NIST Special Publication 881-56

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 855

Purchase Order Acknowledgment

(Revision 1)

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

January 1998

U.S. DEPARTMENT OF COMMERCE

William M. Daley, Secretary

Technology Administration

Gary R. Bachula, Acting Under Secretary for Technology

National Institute of Standards and Technology

Raymond G. Kammer, 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-56

Natl. Inst. Stand. Technol. Spec. Publ. 881-56, 37 pages (Jan. 1998)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1998

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
855 Purchase Order Acknowledgment

Functional Group ID=

Introduction:

This Draft Standard for Trial Use contains the format and estabHshes the data contents of the Purchase Order

Acknowledgment Transaction Set (855) for use within the context of an Electronic Data Interchange (EDI)

environment. The transaction set can be used to provide for customary and established business and industry

practice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used as notification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise as prearranged in their partnership.

Notes:

1. This transaction set is usedforpurchase orders and delivery orders against basic contracts and Federal

Supply Schedules, to indicate acceptance; rejection, with or without detail; or acknowledgment, with detail and

with or without change.

When BEG07 in the 850 transaction set is not transmitted, an 855 transaction set should not be usedfor

acknowledgment

When BEGO7 in the 850 transaction set is code AC, BAK02 can contain code AC, AD, RF, or RJ. When BEG07 in the 850 transaction set is code AK, BAK02 can contain code AK, RF, or RJ. When BEG07 in the 850 transaction set is code AD, BAK02 can contain code AD, RF, or RJ. When BEG07 in the 850 transaction set is code AT, BAK02 can contain code AT, RF, or RJ.

2. When BAK02 is code AD, transmit all segments, data elements and codes that were contained in the

applicable 850 transaction set and that are available in this 855 transaction set. Also transmit the Nl loop using

codes BYand SE.

3. When BAK02 is code AC, transmit the change information using the appropriate segment, data element or code and also transmit all other unchanged segments, data elements and codes contained in the corresponding

segments in the applicable 850 transaction set. Also transmit the Nl loop using codes BY and SE.

4. When BAK02 is either code AK, ATor RJ, transmit the mandatory and required segments and data elements. Also transmit the Nl loop using codes BYand SE.

5. When BAK02 is code RF, transmit the mandatory and required segments and data elements. Also transmit

the N9 loop and the Nl loop using codes BYand SE.

Heading:

Pos. Seg. Req. Loop Notes and

No. ID Name Pes. Max.Use Repeat Comments

Must Use 010 ST Transaction Set Header M 1 Must Use 020 BAK Beginning Segment for Purchase Order M 1 Acknowledgment

Not Used 030 NTE Note/Special Instruction F ICQ Not Used 040 CUR Currency O 1 Not Used 050 REF Reference Numbers O >1

060 PER Administrative Communications Contact O 3 Not Used 070 TAX Tax Reference O >1 080 FOB F.O.B, Related Instructions O >l

Not Used 090 CTP Pricing Information O >1

003050F855 1 08 April 1997
855 - Purchase Order Acknowledgment

Not Used 095 PAM Period Amount O 10 Not Used 110 CSH Header Sale Condition 0 I LOOP ID -SAC 25 Not Used 120 SAC Service, Promotion, Allowance, or Charge 0 1 Information Not useu L UK Currency 1

1

130 ITD Terms of Sale/Deferred Terms of Sale o 5 Not Used 140 DIS Discount Detail 0 20 Not Used 145 INC Installment Information 0 1 Not Used 150 DTM Date/Time Reference 0 10 Not Used 160 LDT Lead Time o 12 Not Used 180 LIN Item Identification 0 5 nl Not Used 185 SI Service Characteristic Identification 0 2 Not Used 190 PID Product/Item Description 0 200

Not Used 200 MEA Measurements 0 40

Not Used 210 PWK Paperwork 0 25

Not Used 220 PKG Marking, Packaging, Loading 0 25

Not Used 230 TDI Carrier Details (Quantity and Weight) 0 2

Not Used 240 TD5 Carrier Details (Routing Sequence/Transit 0 12 Time) Not Used 250 TD3 Carrier Details (Equipment) 0 12 Not Used 260 TD4 Carrier Details (Special Handling, or 0 5 Hazardous Materials, or Both) Not Used 270 MAN Marks and Numbers 0 10

275 TXI idA iiiiuiiiiaiiuii o >] LOOP ID - N9 1000 280 N9 o 1 290 MSG 0 1000

|LOOP ID - Nl 200

300 Nl Name o

'

I

'

310 N2 Additional Name Information 0 2 320 N3 Address Information 0 2 330 N4 Geographic Location 0 1 Not Used 335 NX2 Real Estate Property ID Component 0 3 Not Used 340 REF Reference Numbers 0 12 350 PER Administrative Communications Contact 0 >1

Not Used 360 FOB F.O.B. Related Instructions 0 1 Not Used 370 TDI Carrier Details (Quantity and Weight) o 2 Not Used 380 TD5 Carrier Details (Routing Sequence/Transit 0 12 Time) Not Used 390 TD3 Carrier Details (Equipment) 0 12 Not Used 400 TD4 Carrier Details (Special Handling, or 0 5 Hazardous Materials, or Both) Not t Jsed 410 PKG 0 25 Not Used 420 MSG Message Text 0 >1

Detail:

Pos. Seg. Req. Loop Notes and

No. ID Name Pes. Max. Use Repeat Comments

LOOP ID - POl 100000 010 POl Baseline Item Data O I n2

003050F855 1 2 08 April 1997
855 - Purchase Order Acknowledgment

Not Used 018 SI Service Characteristic Identification 0 5 Not Used 020 CUR Currency 0 1 Not Used 030 P03 Additional Item Detail 0 25 Not Used 040 CTP Pricing Information 0 >1 Not Used 045 PAM Period Amount 0 10 Not Used 049 MEA Measurements 0 40 LOOP ID - PID 1000 050 FID Product/Item Description 0 1 Not Used 060 MEA Measurements 0 10

Not Used 070 PWK Paperwork 0 25 Not Used 090 P04 Item Physical Details 0 >1 Not Used 100 REF Reference Numbers 0 >1 Not Used 110 PER Administrative Communications Contact 0 3 LOOP ID - SAC 25 Not Used

Not Used

130

135

SAC

CUR

Service, Promotion, Allowance, or Charge

Information Currency

0

0

1

1

Not Used 140 IT8 Conditions of Sale 0 1 Not Used 150 ITD Terms of Sale/Deferred Terms of Sale 0 2 Not Used 160 DIS Discount Detail 0 20 Not Used 165 INC Installment Information 0 1 Not Used 170 TAX Tax Reference 0 >1

Not Used 180 FOB F.O.B. Related Instructions 0 >1 Not Used 190 SDQ Destination Quantity 0 500 Not Used 200 DIM Date/Time Reference 0 10 Not Used 210 LDT Lead Time 0 12 Not Used 230 TDl Carrier Details (Quantity and Weight) 0 1 Not Used

Not Used

240

250

TD5

TD3

Carrier Details (Routing Sequence/Transit

Time)

Carrier Details (Equipment)

0

0

12

12

Not Used 260 TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both) 0 5

LOOP ID - ACK 104

270 ACK Line Item Acknowledgment 0 1 Not Used 280 DTM Date/Time Reference 0

Not Used 290 MAN Marks and Numbers 0 10 Not Used 300 AMT Monetary Amount 0 1 n3 Not Used 302 TXI Tax Information 0 >] LOOP ID - PKG 200

Not Used 303 PKG Marking, Packaging, Loading 0

Not Used 305 MEA Measurements 0 >1

LOOP ID - SCH 200

310 SCH Line Item Schedule 0 1 n4 Not Used 315 TDl Carrier Details (Quantity and Weight) 0 2 Not Used

Not Used

320

330

TD5

TD3

Carrier Details (Routing Sequence/Transit

Time)

Carrier Details (Equipment)

0

0

12

12 Not Used 340 TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both) 0 5

LOOP ID - N9 1000

003050F855 1 3 08 April 1997
855 - Purchase Order Acknowledgment

350 N9 Reference Number 0 1 360 MSG Message Text 0 1000 LOOP ID -Nl 200

Not Used 370 Nl Name 0 1 Not Used 380 N2 Additional Name Information 0 2

Not Used 390 N3 Address Information 0 2 Not Used 400 N4 Geographic Location 0 1 Not Used 405 NX2 Real Estate Property ID Component 0 3 Not Used 410 REF Reference Numbers 0 12 Not Used 420 PER Administrative Communications Contact 0 3 Not Used 430 FOB F.O.B. Related Instructions 0 I Not Used 435 SCH Line Item Schedule 0 200

Not usea xr^ 1 1 U

Carrier Details (Quantity and Weight) Z Not Used 450 TD5 Carrier Details (Routing Sequence/Transit 0 12 Time) Not Used 460 TD3 Carrier Details (Equipment) 0 12 Not Used 470 TD4 Carrier Details (Special Handling, or 0 5 Hazardous Materials, or Both) Not Used 480 PKG Marking, Packaging, Loading 0 25 LOOP ID - SLN 1000 Not Used 490 SLN Subline Item Detail 0 1 Not Used 500 SI Service Characteristic Identification 0 5 Not Used 510 FID Product/Item Description 0 1000

INOL UatU /AUUILlUllal ILCIII L/CLall

522 CTP rlPriPino IL'lllg ill InfnrmatinTi WJi 1 1 laLlLf 1

0 25 Not Used 523 RAM Period Amount 0 10 Not Used 530 ACK Line Item Acknowledgment 0 104 LOOP ID - SAC 10 Not Used 540 SAC Service, Promotion, Allowance, or Charge 0 1 Information Not Used 545 CUR Currency 0 1

550 DTM Datp/Ximp Rpfprpnrp 0 10 Not Used 554 P04 Item Physical Details 0 1 Not Used 557 TAX Tax Reference 0 3 LOOP ID -Nl 10 Not Used 560 Nl Name 0 1 Not Used 570 N2 Additional Name Information o 2 Not Used 580 N3 Address Information 0 2

INOl UScG Dy\j Geographic Location \j 1

Not Used 600 NX2 Real Estate Property ID Component 0 3 Not Used 610 REF Reference Numbers 0 12 Not Used 620 PER Administrative Communications Contact 0 3

Summary:

Pos. Seg. Req. Loop Notes and

No. ID Name Pes. Max.Use Repeat Comments

Must Use 010 CTT Transaction Totals M 1 n5 Not Used 020 AMI Monetary Amount 0 1 n6 Must Use 030 SE Transaction Set Trailer M 1

003050F855 1 4 08 April 1997
855 - Purchase Order Acknowledgment

Transaction Set Notes

1 . If segment LEST is used, do not use LINO 1

.

2. PO102 is required.

3. If AMT is used in the detail area, then AMTOl will = 1 and AMT02 will indicate total line amount as calculated by the sender.

4. The SCH segment is used to specify various quantities of items ordered that are to be scheduled. When this segment is used the unit of measurement code (SCH02) should always be identical to the unit of

measurement code in the associated POl segment (PO103) and the sum of values of quantity (SCHOl) should

always equal the quantity ordered (POl 02) in the POl segment.

5. The number of line items (CTTOl) is the accumulation of the number of POl segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each POl segment.

6. If AMT is used in the summary area, then AMTOl will = TT and AMT02 will indicate total transaction amoimt as calculated by the sender.

003050F855 1 5 08 April 1997
855 - Purchase Order Acknowledgment

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 (STOl) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810

selects the Invoice Transaction Set).

Ref. Pes. Must Use STOl

Must Use ST02

Data

Element

143

329

Data Element Summary

Name Attributes

Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set 855 XI 2.9 Purchase Order Acknowledgment

Transaction Set Control Number M AN 4/9

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

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

in SE02.

003050F855 1 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes: Semantic Notes:

Comments:

BAK Beginning Segment for Purchase Order Acknowledgment

020

Heading

Mandatory

1To indicate the beginning of the Purchase Order Acknowledgment Transaction Set and

transmit identifying numbers and dates

1 BAK04 is the date assigned by the purchaser to purchase order. 2 BAK08 is the seller's order number.

3 BAK09 is the date assigned by the sender to the acknowledgment.

Ref. Pes. Must Use BAKOl

Must Use BAKOl

Data

Element

353

587

Data Element Summary

Name Attributes

Transaction Set Purpose Code M ID 2/2

Code identifying purpose of transaction set 00 Original

Use to indicate an original submission ofan 855

transaction set. 07 Duplicate

Use to indicate a re-transmission ofa previously

transmitted 855 transaction set. Acknowledgment Type M ID 2/2

Code specifying the type of acknowledgment

AC

AD

AK

AT

RF

Acknowledge - With Detail and Change

Use to indicate an order is being acknowledged with

detail and changes. The changes may include the

rejection ofone or more line items. Use this code only

ifBEGO? in the applicable 850 transaction set was

code AC.

Acknowledge - With Detail, No Change

Use to indicate the order is being acknowledged with

detail and no change. Use this code only when

BEG07 in the applicable 850 transaction set was code

AC or AD.

Acknowledge - No Detail or Change

Vse to indicate the order is being acknowledged *

without detail or change. Use this code only when

BEG07 in the applicable 850 transaction set was code

AK.

Accepted

Use to indicate acceptance ofa purchase order. Use

this code only ifBEGO? in the applicable 850

transaction set was code A T. Reject with Exception Detail Only

Use to indicate a rejection (with reasons) ofa purchase order. When used, provide the reasons in the

N9 loop using code 55 in N901. Do not use this code

ifthe order is being accepted but one or more line items are being rejected. Use code ACfor this purpose.

003050F855 1 7 08 April 1997
855 - Purchase Order Acknowledgment

Must Use BAK03

Must Use BAK04

BAK05

Not Used BAK06

BAK07

BAK08

RJ Rejected - No Detail Use to indicate the rejection (without reasons) ofa purchase order. Do not use this code ifthe order is being accepted but one or more line items are being

rejected. Use code ACfor this purpose. 324 Purchase Order Number M AN 1/22

Identifying number for Purchase Order assigned by the orderer/purchaser 'Use to identify the purchase order number to which this transaction set

applies. Cite the numberfrom BEG03 ofthe applicable 850 transaction set. 373 Date M DT 6/6 Date (YYMMDD)

•XJse to identify the effective date ofthe award instrument to which this transaction set applies. Cite the numberfrom BEG05 ofthe applicable 850

transaction set 328 Release Number O AN 1/30

Number identifying a release against a Purchase Order previously placed by

the parties involved in the transaction Use to identify the number ofa release, call or delivery order against a basic

award instrument to which this transaction set applies. Cite the number

from BEG04 ofthe applicable 850 transaction seL 326 Request Reference Number O AN 1/45

Reference number or RFQ number to use to identify a particular transaction set and query (additional reference number or description which can be used with

contract number)

367 Contract Number O AN 1/30 Contract number

Use to identify' the Small Business Administration (SBA) contract number

for an 8a Set-Aside.

Ill 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.

/. Use to indicate the Seller's order number

2. When BAK02 is code AC, AD, or A T, use to identify the number assigned

by the selling party to the buying party 's purchase order. This number is used to facilitate references in future communications.

BAK09 373 Date O DT 6/6 Date (YYMMDD)

'^se to identify the date this 855 transaction set was transmitted.

003050F855 1 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes: Comments:

Notes:

PER Administrative Communications Contact

060

Heading

Optional

3To 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 when BAK02 is code AC, AD, or RJ.

Ref. Pes. Must Use PEROl

PER02

PER03

PER04

Not Used PER05

Not Used PER06

Not Used PER07

Not Used PER08

PER09

Data

Element

366

93

365

364

365

364

365

364

443

Data Element Summary

Name Attributes

Contact Function Code M ID 2/2

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

OC Order Contact OD Order Department

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 ofinitials for thefirst name is recommended. PER09 may be used to cite the

party's title. Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

FX Facsimile

TE Telephone

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

1. Cite the area code and commercial telephone orfacsimile number ofthe

party identified in PER02.

2. All numbers 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

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number

Use to identify the title ofthe party cited in PER02.

003050F855 1 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes:

FOB F.O.B. Related Instructions

Comments:

Notes:

Ref.

Pes. Must Use FOBOl

Not Used FOB02

Not Used FOB03

Not Used FOB04

080

Heading

Optional

>1

To specify transportation instructions relating to shipment

1 If FOB03 is present, then FOB02 is required. 2 If FOB04 is present, then FOB05 is required.

3 If FOB07 is present, then FOB06 is required.

4 If FOB08 is present, then FOB09 is required.

1 FOBOl indicates which party will pay the carrier. 2 FOB02 is the code specifying transportation responsibility location. 3 FOB06 is the code specifying the title passage location. 4 FOB08 is the code specifying the point at which the risk of loss transfers. This may

be different than the location specified in FOB02/FOB03 and FOB06/FOB07.

1. Use this segment when BAK02 is code AC or AD.

2. When BAK02 is code AD, transmit the same information as contained in the

applicable 850 transaction set.

3. When BAK02 is code AC, use to identify a change in the shipment method of

payment specified in the 850 transaction set, if applicable. Otherwise, transmit the

^ftme information contained in the applicable 850 transaction set.

Data

Element

146

309

352

334

Data Element Summary

Name Attributes

Shipment Method of Payment M ID 2/2

Code identifying payment terms for tiansportation charges

BP Paid by Buyer

The buyer agrees to the transportation payment term

requiring the buyer to pay transportation charges to a specified location (origin or destination location)

Use to indicate a Government Bill ofLading (GBL)

will be issued. PE Prepaid and Summary Bill Use when transportation charges are to be prepaid by

the seller, are not included in the unit price, and are to be invoiced periodically.

PP Prepaid (by Seller) Use to indicate that transportation charges are not

included in the unit price but areprepaid and are to be

added as a separate item on this instrument's invoice. PS Paid by Seller The seller agrees to the transportation payment term

requiring the seller to pay transportation charges to a specified location (origin or destination location)

Use to indicate transportation charges are included in the unit price.

Location Qualifier X ID 1/2

Code identifying type of location Description O AN 1/80

A free-form description to clarify the related data elements and their content Transportation Terms Qualifier Code O ID 2/2

003050F855 1 10 08 April 1997
855 - Purchase Order Acknowledgment

Not Used FOB05

Not Used FOB06

Not Used FOB07

Not Used FOB08

Not Used FOB09

Code identifying the source of the transportation terms 335 Transportation Terms Code X ID 3/3

Code identifying the trade terms which apply to the shipment transportation

responsibility

309 Location Qualifier X ID 1/2 Code identifying type of location 352 Description O AN 1/80

A free-form description to clarify the related data elements and their content 54 Risk of Loss Qualifier O ID 2/2

Code specifying where responsibility for risk of loss passes 352 Description X AN 1/80

A free-form description to clarify the related data elements and their content

003050F855 1 11 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes:

Comments:

Notes:

Ref. Pes. Not Used ITDOl

Not Used ITD02

ITD03

Not Used ITD04

ITD05

Not Used ITD06

ITD07

Not Used ITD08

Not Used ITD09

Not Used ITDIO

Not Used ITDll

Not Used ITD12

Not Used ITD13

ITD Terms of Sale/Deferred Terms of Sale

130

Heading

Optional

5To specify terms of sale

1 If ITD03 is present, then at least one of ITD04 ITD05 or ITD 1 3 is required.

2 If ITD08 IS present, then at least one of ITD04 ITD05 or ITD 1 3 is required.

3 If ITD09 is present, then at least one of ITD 1 0 or ITD 1 1 is required.

1 ITD 15 is the percentage applied to a base amount used to determine a late payment

charge.

1 If the code in ITDOl is "04", then ITD07 or ITD09 is required and either ITDIO or ITDl 1 is requu-ed; if the code in ITDOl is "05", then ITD06 or ITD07 is required.

1. Use this segment when BAK02 is code AC or AD.

2. When BAK02 is code AD, transmit the same information as contained in the

applicable 850 transaction set.

3. When BAK02 is code AC, use to identify a different discount than specified in the

applicable 850 transaction set. Otherwise, transmit the same information as contained ^the applicable 850 transaction set.

Data Element Summary

Data

Element

336

333

338

Attributes

O ID 2/2

O ID 1/2

370

351

446

386

362

388

389

342

352

765

Name

Terms Type Code

Code identifying type of payment terms Terms Basis Date Code

Code identifying the beginning of the terms period

Terms Discount Percent O R 1/6

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

Cite 4.25% as 4.25; cite 3% as 3 (note: leading and trailing zeros are

suppressed)

, Terms Discount Due Date X DT 6/6 Date payment is due if discount is to be earned

Terms Discount Days Due X NO 1/3

Number of days in the terms discount period by which payment is due if terms

discount is earned

Terms Net Due Date O DT 6/6 Date when total invoice amount becomes due

Terms Net Days O NO 1/3

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

Terms Discount Amount O N2 1/10

Total amount of terms discount

Terms Deferred Due Date

Date deferred payment or percent of invoice payable is due

Deferred Amount Due

Deferred amount due for payment

Percent of Invoice Payable

Amount of invoice payable expressed in percent

Description

A free-form description to clarify the related data elements and their content Day of Month X NO 1/2

O DT 6/6

X N2 1/10

X R 1/5

O AN 1/80

003050F855 1 12 08 April 1997
855 - Purchase Order Acknowledgment

The numeric value of the day of the month between 1 and the maximum day of

the month being referenced Not Used TTDU 107 Payment Method Code O ID 1/1 Code identifying type of payment procedures

Not Used ITD15 954 Percent O R 1/10

Percentage expressed as a decimal

003050F855 1 13 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes: Comments:

Notes:

N9 Reference Number

280

N9

Heading

Optional

1To transmit identifying numbers and descriptive information as specified by the reference number qualifier

1 At least one of N902 or N903 is required. 2 If N906 is present, then N905 is required.

1 N906 reflects the time zone which the time reflects.

When BAK02 is code RF, use to provide reasonsfor rejection ofa purchase order.

Ref. Pes. Must Use N901

Not Used N902

N903

Not Used N904

Not Used N905

Not Used N906

Data

Element

128

127

369

373

337

623

Data Element Summary

Name Attributes

Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

55 Sequence Number

Use to indicate reasonsfor the rejection are being

provided. Cite the word "Reason " in N903 and state the reasons in thefollowing MSG segment

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.

Free-form Description X AN 1/45

Free-form descriptive text This data element may only contain the word "Reason ". Date O DT 6/6 Date (YYMMDD)

Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 860 1, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

003050F855 1 14 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes: Semantic Notes: Comments:

Notes:

Ref. Pes. Must Use MSGOl

Not Used MSG02

MSG Message Text 290

N9

Heading

Optional

1000

To provide a free form format that would allow the transmission of text information.

1 MSG02 is not related to the specific characteristics of a printer, but identifies top of

page, advance a line, etc. Use this segment to provide the reasonsfor a rejection ofa purchase order.

Data Element Summary

Data

Element Name Attributes

933 Free-Form Message Text M AN 1/264

Free-form message text 934 Printer Carriage Control Code O ID 2/2

A field to be used for the control of the line feed of the receiving printer

003050F855 1 15 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes: Comments:

Notes:

Nl Name

300

Nl

Heading

Optional

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

1 At least one of N1 02 or N1 03 is required. 2 If either N1 03 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 N1 05 and N1 06 further define the type of entity in N 1 0 1

1. Wheneverpossible, address information should be transmitted using code values

contained in a combination ofthe NlOl, N103/04 data elements. Use N102 and the

N2-N4 segments only when it is necessary to transmit thefull address. For example, if a vendor can be identified by a DUNs number, it is not necessary to transmit the

vendor'sfull address since the relationship between the DUNs number and the

vendor's address can be established by accessing a data base in which the information

is stored, having been put there at the time the vendor electronically registered as a

federal government trading partner.

2. When BAK02 is code AD, transmit the same information as contained in the

applicable 850 transaction set.

3. At least 2 iterations ofthis segment are required with NlOl citing code

BYandSE.

Must Use

Ref. Pes. NlOl

N102

N103

Data

Element

98

93

66

Data Element Summary

Name Attributes

Entity Identifier Code M ID 2/2

Code identifying an organizational entity, a physical location, or an individual BY Buying Party (Purchaser)

SE Selling Party

ST Ship To

Use only when BAK02 is code AC or AD,

Name X AN 1/35

Free-form name

Use only ifBAK02 is code AC or AD.

Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67)

Hltile thefederal 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

fxisting data bases to new procurement actions.

1 D-U-N-S Number, Dun & Bradstreet Use ofthe DUNS or DUNS+4 number is preferred

over other codes to identify an entity.

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

Suffix

Use ofthe DUNS or DUNS+4 number is preferred

over other codes to identify an entity.

003050F855 1 16 08 April 1997
855 - Purchase Order Acknowledgment

10 Department of Defense Activity Address Code

(DODAAC)

Use to indicate either a Department ofDefense

Activity Address Code or a Civilian Agency Activity

Address Code.

21 Health Industry I.D. Number (HIN)

JJse only when BAK02 is code AC or AD.

33 Commercial and Government Entity (CAGE)

Use to indicate vendors with CAGE codes. 67 Identification Code X AN 2/20

Code identifying a party or other code

706 Entity Relationship Code O ID 2/2

Code describing entity relationship

98 Entity Identifier Code O ID 2/2

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

003050F855_1 17 08 April 1997

N104

Not Used N105

Not Used N106
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes: Semantic Notes: Comments:

Notes:

N2 Additional Name Information

310

Nl

Heading

Optional

2To specify additional names or those longer than 35 characters in length

1. This segment is not necessary when the cited party can be identified by a code value

in NlOl/03/04.

2. Use only ifBAK02 is code AC or AD.

3. When BAK02 is code AD, transmit the same information as contained in the

applicable 850 transaction set

Ref. Pes. Must Use N201

N202

Data Element Summary

Data

Element Name

93 Name

Free-form name

93 Name

Free-form name

Attributes

M AN 1/35

O AN 1/35

003050F855 1 18 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes: Semantic Notes: Comments:

Notes:

N3 Address Information

320

Nl

Heading

Optional

2To specify the location of the named party

1. This segment is not necessary when the cited party can be identified by a code value

in NlOl/03/04.

2. UseonlyifBAK02 iscodeACorAD.

3. When BAK02 is code AD, transmit the same information as contained in the

applicable 850 transaction set.

Ref. Pes. Must Use N301

N302

Data Element Summary

Data

Element Name

166 Address Information

Address information

166 Address Information

Address information

Attributes

M AN 1/35

O AN 1/35

003050F855 I 19 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes: Semantic Notes: Comments:

Notes:

N4 Geographic Location

330

Nl

Heading

Optional

1To specify the geographic place of the named party

1 If N406 is present, then N405 is required.

1 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2 N402 is required only if city name (N401) is in the USA or Canada.

1. This segment is not necessary when the cited party can be identified by a code value

in NlOl/03/04.

Ref. Pes. N401

N402

N403

N404

Not Used N405

Not Used N406

2. Use only ifBAK02 is code AC or AD.

3. When BAK02 is code AD, transmit the same information as contained in the

gffplicable 850 transaction set.

Data Element Summary

Data

Element Name

19

Attributes

City Name O AN 2/30

Free-form text for city name

156 State or Province Code O ID 2/2

Code (Standard State/Province) as defined by appropriate govenmient agency

116 Postal Code O ID 3/11

Code defining international postal zone code excluding punctuation and blanks

(zip code for United States)

26 Country Code O ID 2/3

Code identifying the country

309 Location Qualifier X ID 1/2

Code identifying type of location 310 Location Identifier O AN 1/30

Code which identifies a specific location

003050F855 1 20 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes: Comments:

Notes:

PER Administrative Communications Contact

350

Nl

Heading

Optional

>1

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 when BAK02 is code A T, RF, or RJ.

Must Use

Ref. Pes. PEROl

PER02

PER03

PER04

Data

Element

366

93

365

364

Data Element Summary

Name Attributes

Contact Function Code M ID 2/2

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

AA Authorized Representative

Use to indicate the person authorized to transmit this transaction set Use this code only when BAK02 is AT,RForRJ.

IC Information Contact Name O AN 1/35

Free-form name

Use to identify the name ofa point of contact. Last name, followed byfirst name, is preferred. Ifthe whole name is longer than 35 characters, the use ofinitials for the first name is recommended PER09 may be used to cite the

party's title. Communication Number Qualifier X ID 2/2

Code identifying the type of communication number

EM Electronic Mail

FX Facsimile

TE Telephone

Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

1. When PER03 is TE, cite the area code and commercial telephone

number.

2. All numbers, other than those associated with code EM, shall be

transmitted as a continuous number with no extraneous characters. PER05 365 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 the commercial telephone number,

PER05/06 can be used to cite an electronic mail number.

EM

EX

FX

TE

Electronic Mail

Telephone Extension

Use only ifPER03 is used citing code tE.

Facsimile

Telephone

003050F855 1 21 08 April 1997
855 - Purchase Order Acknowledgment

PER06 364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

L When PER05 is TE, cite the area code and commercial telephone

'number.

2. AH numbers, other than those associated with code EM, shall be

Ifransmitted as a continuous number with no extraneous characters. PER07 365 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.

EM Electronic Mail

EX Telephone Extension

Use only ifPEROS is used citing code TE. FX Facsimile

TE Telephone

PER08 364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable

1. When PER07 is TE, cite the area code and commercial telephone

number.

2. All numbers, other than those associated with code EM, shall be

transmitted as a continuous number with no extraneous characters. PER09 443 Contact Inquiry Reference O AN 1/20

Additional reference number or description to clarify a contact number

Use to identify the title ofthe party cited in PER02,

003050F855 22 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

POl Baseline Item Data

Semantic Notes: Comments:

Notes:

Ref. Pes. POlOl

PO102

PO103

PO104

010

POl

Detail Optional

1To specify basic and most frequently used line item data

123

4

5

6

78

9

10

1112

123

If POl 03 is present, then POl 02 is required.

If POl 05 is present, then POl 04 is required.

If either POl 06 or POl 07 is present, then the other is required.

If either POl 08 or POl 09 is present, then the other is required.

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

If either POl 12 or POl 13 is present, then the other is required.

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

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

If either POl 18 or POl 19 is present, then the other is required.

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

If either POl 22 or POl 23 is present, then the other is required.

If either POl 24 or POl 25 is present, then the other is required.

See the Data Dictionary for a complete list of ID's. POl 01 is the line item identification. POl 06 through POl 25 provide for ten (10) different product/service ID's per each

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

SKU.

Use this segment when BAK02 is code AC or AD.

2. When BAK02 is code AD, transmit the same information as contained in the

applicable 850 transaction set.

3. Wlien BAK02 is code AC, use to identify the correct line item information when it differs from that contained in the 850 transaction set or to identify a rejected line item.

4. Ifone or more line items are rejected, identify the line items in this segment and cite code IR in ACKOl.

Data

Element

350

330

355

212

Data Element Summary

Name Attributes

Assigned Identification O AN 1/11

Alphanumeric characters assigned for differentiation within a transaction set Cite the same line item number(s) as contained in the 850 transaction set. Quantity Ordered X R 1/9

Quantity ordered

Use to identify the quantity cited in the 850 transaction set or the quantity

accepted by the selling party. .,„„_., Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Use to identify the unit ofmeasure applicable to the quantity cited in PO102.

Refer to 003050 Data Element Dictionary for acceptable code values. Unit Price X R 1/17

Price per unit of product, service, commodity, etc. Use to identify the price cited in the 850 transaction set or the price accepted

by the selling party.

003050F855 1 23 08 April 1997
855 - Purchase Order Acknowledgment

Not Used PO105 639 Basis of Unit Price Code O ID 2/2

Code identifying the type of unit price for an item

PO106 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

1. When BAK02 is code AD, cite the same codes as contained in the 850

transaction set.

2. When BAK02 is code AC, cite the appropriate code to identify the line item ifdifferent than the code(s) contained in the 850 transaction set,

3. Any code may be used but the listed codes are preferred to cite differences

in line item identification.

CR Contract Number

IfBAK03 is a delivery order against a basic contract or GSA Schedule, use to indicate the contract number.

FS National Stock Number

LT Lot Number

MF Manufacturer

ND National Drug Code (NDC)

SN Serial Number

VP Vendor's (Seller's) Part Number

Refer to 003050 Data Element Dictionary for acceptable code values. PO107 234 Product/Service ID X AN 1/40

Identifying number for a product or service PO108 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values. PO109 234 Product/Service ID X AN 1/40

Identifying number for a product or service POllO 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values. POlll 234 Product/Service ID X AN 1/40

Identifying number for a product or service P0112 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values. P0113 234 Product/Service ID X AN 1/40

Identifymg number for a product or service P0114 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values.

003050F855 I 24 08 April 1997
855 - Purchase Order Acknowledgment

P0115 234 Product/Service ID X AN 1/40

Identifying number for a product or service P0116 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values. P0117 234 Product/Service ID X AN 1/40

Identifying number for a product or service P0118 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values. P0119 234 Product/Service ID X AN 1/40

Identifying number for a product or service PO120 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values. P0121 234 Product/Service ID X AN 1/40

Identifying number for a product or service P0122 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values. P0123 234 Product/Service ID X AN 1/40

Identifying number for a product or service P0124 235 Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Refer to 003050 Data Element Dictionary for acceptable code values. P0125 234 Product/Service ID X AN 1/40

Identifying number for a product or service

003050F855 1 25 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

PID Product/Item Description

050

PID

Detail Optional

1To describe a product or process in coded or free-form format

Semantic Notes:

1 If PID04 is present, then PID03 is required. 2 At least one of PID04 or PID05 is required.

3 If PID07 is present, then PID03 is required.

4 If PID08 is present, then PID03 is required.

1 Use PID03 to indicate the organization that publishes the code list being referred to. 2 PID04 should be used for industry-specific product description codes. 3 PID08 describes the physical characteristics of the product identified in PID04. A

"~Y" indicates that the specified attribute applies to this item. A ""N" indicates it does

not apply. Any other value is indeterminate. Comments: 1 If PIDOl = "F", then PID05 is used. If PIDOl = "S", then PID04 is used. If PIDOl =

^X", then both PID04 and PID05 are used.

2 Use PID06 when necessary to refer to the product surface or layer being described in the segment.

3 PID07 specifies the individual code list of the agency specified in PID03.

/. Use this segment when BAK02 is code AC or AD.

2, When BAK02 is code AD, transmit the same information as contained in the

applicable 850 transaction set.

3. When BAK02 is code AC, transmit tite item description if different than the

description contained in the 850 transaction set.

Notes:

Ref. Des. Must Use PIDOl

Not Used PID02

Not Used PID03

Not Used PID04

proos

Not Used PID06

Not Used PID07

Not Used PID08

Data Element Summary

Data

Element

349

750

559

751

352

752

822

1073

Attributes

M ID 1/1 NameItem Description Type

Code indicating the format of a description

F Free-form

Product/Process Characteristic Code O ID 2/3

Code identifying the general class of a product or process characteristic Agency Qualifier Code X ID 2/2

Code identifying the agency assigning the code values Product Description Code X AN 1/12

A code from an industry code list which provides specific data about a product

characteristic Description X AN 1/80

A free-form description to clarify the related data elements and their content Surface/Layer/Position Code O ID 2/2

Code indicating the product surface, layer or position that is being described

Source Subqualifler O AN 1/15

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

Yes/No Condition or Response Code O ID 1/1 Code indicating a Yes or No condition or response

003050F855 1 26 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

ACK

Semantic Notes:

Comments:

Notes:

Line Item Acknowledgment

270

ACK

Detail Optional

1To acknowledge the ordered quantities and specify the ready date for a specific line item

123

4

5

6

7

8

9

10

111213

14

1

If either ACK02 or ACK03 is present, then the other is required.

If ACK04 is present, then ACK05 is required. or ACK08 is present. then the other is required. or ACK10 is present. then the other is required. or ACK12 is present. then the other is required. or ACK14 is present, then the other is required. or ACK16 is present, then the other is required. or ACK18 is present. then the other is required. or ACK20 is present. then the other is required. or ACK22 is present. then the other is required. or ACK24 is present. then the other is required. or ACK26 is present, then the other is required. or ACK28 is present, then the other is required.

If ACK28 is present, then both ACK27 and ACK29 are required.

ACK29 Industry Reason Code may be used to identify the item status. In addition, it may be used in conjunction with ACKOl to further clarify the status.

1. Use this segment when BAK02 is code AC or AD to provide information related to the line item ordered in the applicable 850 transaction set. If a line item is rejected,

cite code IR in ACKOL

Ref. Pes. Must Use ACKOl

ACK02

ACK03

ACK04

ACK05

Not Used ACK06

2. Wlien providing delivery information, use as many repetitions ofthis segment as

necessary to specify the delivery schedule.

Data

Element

668

380

355

374

373

326

Data Element Summary

Name Attributes

Line Item Status Code M ID 2/2

Code specifying the action taken by the seller on a line item requested by the buyer

Use any code. Refer to 003050 Data Element Dictionary for acceptable code values. Quantity X R 1/15

Numeric value of quantity

Unit or Basis for Measurement Code X ID 2/2

Code specifying the units in which a value is being expressed, or maimer in which a measurement has been taken Refer to 003050 Data Element Dictionary for acceptable code values. Date/Time Qualifier O ID 3/3

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

073 Scheduled for Delivery (Prior to and Including)

Use to indicate the scheduled delivery datefor the

quantity cited in ACK02.

Date _

' ' X

Date (YYMMDD)

Request Reference Number O AN 1/45

Reference number or RFQ number to use to identify a particular transaction set and query (additional reference number or description which can be used with

003050F855 I 27 08 April 1997
855 - Purchase Order Acknowledgment

Not Used ACK07 235

Not Used ACK08 234

Not Used ACK09 235

Not Used ACKIO 234

Not Used ACKll 235

Not Used ACK12 234

Not Used ACK13 235

Not Used ACK14 234

Not Used ACK15 235

Not Used ACK16 234

Not Used ACK17 235

Not Used ACK18 234

Not Used ACK19 235

Not Used ACK20 234

Not Used ACK21 235

Not Used ACK22 234

Not Used ACK23 235

Not Used ACK24 234

Not Used ACK25 235

Not Used ACK26 234

Not Used ACK27 559

Not Used ACK28 822

Not Used ACK29 1271

contract number)

Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service Product/Service ID Qualifier X ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

Product/Service ID X AN 1/40

Identifying number for a product or service Agency Qualifier Code X ID 2/2

Code identifying the agency assigning the code values Source Subqualifier X AN 1/15

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

Industry Code X AN 1/20

003050F855 28 08 April 1997
855 - Purchase Order Acknowledgment

Code indicating a code from a specific industry code list

003050F855 1 29 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes: Comments:

SCH Line Item Schedule

310

SCH

Detail Optional

1To specify the data for scheduling a specific line-item

1 If SCH03 is present, then SCH04 is required. 2 If SCH08 is present, then at least one of SCH09 or SCH 1 0 is required.

3 If SCH09 is present, then SCH08 is required. 4 If SCH 1 0 is present, then SCH08 is required.

1 SCH 12 is the schedule identification.

1 SCH05 specifies the interpretation to be used for SCH06 and SCH07.

Ref. Pes. Must Use SCHOl

Must Use SCH02

Not Used SCH03

Not Used SCH04

Must Use SCH05

Must Use SCH06

SCH07

SCH08

SCH09

SCHIO

SCHll

Data Element Summary

Data

Element Name Attributes

380 Quantity M R 1/15

Numeric value of quantity

355 Unit or Basis for Measurement Code M ID 2/2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken Refer to 003050 Data Element Dictionary for acceptable code values. 98 Entity Identifier Code O ID 2/2

Code identifying an organizational entity, a physical location, or an individual 93 Name X AN 1/35

Free-form name

374 Date/Time Qualifier M ID 3/3

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

Refer to 003050 Data Element Dictionary for acceptable code values. 373 Date M DT 6/6 Date (YYMMDD)

337 Time O TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Use, if applicable, to identify the timefor a delivery. Specify time only in the

HHMMformat

374 Date/Time Qualifier X ID 3/3

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

Refer to 003050 Data Element Dictionary for acceptable code values. 373 Date X DT 6/6 Date (YYMMDD)

337 Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Use, if applicable, to identify' the timefor a delivery. Specify time only in the

HHMMformat

326 Request Reference Number O AN 1/45

Reference number or RFQ number to use to identify a particular transaction set

003050F855 1 30 08 April 1997
855 - Purchase Order Acknowledgment

and query (additional reference number or description which can be used with

contract number)

Use to identify a reference number appiitaile to the delivery, e.g., a

requisition number.

Not Used SCH12 350 Assigned Identification O AN 1/11

Alphanumeric characters assigned for differentiation within a transaction set

003050F855 1 31 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes: Comments:

Notes:

N9 Reference Number

350

N9

Detail Optional

1To transmit identifying numbers and descriptive information as specified by the reference number qualifier

1 At least one of N902 or N903 is required. 2 If N906 is present, then N905 is required.

1 N906 reflects the time zone which the time reflects.

When ACKOl is code IR, use to provide the reasonsfor rejection ofa line itenu

Must Use

Ref. Pes. N901

Not Used N902

N903

Not Used N904

Not Used N905

Not Used N906

Data

Element

128

127

369

373

337

623

Data Element Summary

Name Attributes

Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

55 Sequence Number

Use to indicate reasonsfor the rejection are being

provided. Cite tlie word "Reason " in N903 and state the reasons in thefollowing MSG segment

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.

Free-form Description X AN 1/45

Free-form descriptive text This data element may only contain the word "Reason". Date O DT6/6

Date (YYMMDD)

Time X TM 4/8

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-

59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds

are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

Time Code O ID 2/2

Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication

in hours in relation to Universal Time Coordinate (UTC) time; since + is a

restricted character, + and - are substituted by P and M in the codes that follow

003050F855 32 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes: Semantic Notes: Comments:

Notes:

Ref. Pes. Must Use MSGOl

Not Used MSG02

MSG Message Text

360

N9

Detail Optional

1000

To provide a free form format that would allow the transmission of text information.

1 MSG02 is not related to the specific characteristics of a printer, but identifies top of

page, advance a line, etc. Use this segment to provide the reasonsfor the rejection ofa line item.

Data Element Summary

Data

Element Name Attributes

933 Free-Form Message Text M AN 1/264

Free-form message text 934 Printer Carriage Control Code O ID 2/2

A field to be used for the control of the line feed of the receiving printer

003050F855 1 33 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes:

Semantic Notes: Comments:

CTT Transaction Totals

010

Summary

Mandatory

1To transmit a hash total for a specific element in the transaction set

1 If either CTT03 or CTT04 is present, then the other is required. 2 If either CTT05 or CTT06 is present, then the other is required.

1 This segment is intended to provide hash totals to validate transaction completeness

and correctness.

Ref. Pes. Must Use CTTOl

Not Used CTT02

Data

Element

354

347

Data Element Summary

Name Attributes

Number of Line Items M NO 1/6 Total number of line items in the transaction set When BAK02 is code AT, or when rejecting the entire 850 transaction set, cite the number "0"

Hash Total O R 1/10

Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs.

Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

Not Used CTT03

Not Used CTT04

Not Used CTT05

Not Used CTT06

Not Used CTT07

Example:

-.0018 First occurrence of value being hashed. .18 Second occurrence of value

being hashed. 1.8 Third occurrence of value being hashed. 18.01 Fourth

occurrence of value being hashed. 1855 Hash total prior to truncation. 855 Hash total after truncation to three-digit field. 81 Weight X R 1/10

Numeric value of weight

355 Unit or Basis for Measurement Code X ID 2/2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

183 Volume X R 1/8

Value of volumetric measure 355 Unit or Basis for Measurement Code X ID 2/2

Code specifying the units in which a value is being expressed, or maimer in which a measurement has been taken

352 Description O AN 1/80

A free-form description to clarify the related data elements and their content

003050F855 1 34 08 April 1997
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use: Purpose:

Syntax Notes: Semantic Notes: Comments:

SE Transaction Set Trailer

030

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.

Ref. Pes. Must Use SEOl

Must Use SE02

Data

Element

96

329

Data Element Summary

Name Attributes

Number of Included Segments M NO 1/10

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

segments

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 is the same number as ST02.

003050F855 1 35 08 April 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 incliided 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) devel- oped 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, 1 155 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. 11 27), 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 (NISTTR)—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.
oU

oo

o1 ON

ON

ooo

fc- '-g ^ W) g c o ^

. o