NIST Special Publication 881-6

NIST

PUBLICATIONS

4 Hllllilllilillll

lllilillilliliiiiflii Iliiikililiiilklil

lllllllllll 1 1

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 855

Purchase Order Acknowledgment

Implementation Convention

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology

U57

NO. 881 -6

1996

QC
7he 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 Public Inquiries Desk, 301-975-3058.

Office of the Director

• Advanced Technology Program

• Quality Programs

• International and Academic Affairs

Technology Services

• Manufacturing Extension Partnership

• Standards Services

• Technology Commercialization

• Measurement Services

• Technology Evaluation and Assessment

• Information Services

Materials Science and Engineering

Laboratory

• Intelligent Processing of Materials

• Ceramics

• Materials Reliability'

• Polymers

• Metallurgy

• Reactor Radiation

Chemical Science and Technology

Laboratory

• Biotechnology

• Chemical Kinetics and Thermodynamics

• Analytical Chemical Research

• Process Measurements

• Surface and Microanalysis Science

• Thermophysics^

Physics Laboratory

• Electron and Optical Physics

• Atomic Physics

• Molecular Physics

• Radiometric Physics

• Quantum Metrology

• Ionizing Radiation

• Time and Frequency'

• Quantum Physics'

Manufacturing Engineering Laboratory

• Precision Engineering

• Automated Production Technology

• Intelligent Systems

• Manufacturing Systems Integration

• Fabrication Technology

Electronics and Electrical Engineering

Laboratory

• Microelectronics

• Law Enforcement Standards

• Electricity

• Semiconductor Electronics

• Electromagnetic Fields'

• Electromagnetic Technology'

• Optoelectronics'

Building and Fire Research Laboratory

• Structures

• Building Materials

• Building Environment

• Fire Safety

• Fire Science

Computer Systems Laboratory

• Office of Enterprise Integration

• Information Systems Engineering

• Systems and Software Technology

• Computer Security

• Systems and Network Architecture

• Advanced Systems

Computing and Applied Mathematics

Laboratory

• Applied and Computational Mathematics^

• Statistical Engineering^

• Scientific Computing Environments^

• Computer Services

• Computer Systems and Communications^

• Information Systems

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

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003050 Transaction Set 855

Purchase Order Acknowledgment

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

February 1996

U.S. DEPARTMENT OF COMMERCE

Ronald H. Brown, Secretary

Technology Administration

Mary L. Good, Under Secretary for Tecluiology

National Institute of Standards and Technology

Arati Prabhakar, Director
Reports on Computer Systems Technology

The National Institute of Standards and Technology (NIST)'s Computer Systems Laboratory (CSL)

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

related telecommunications systems to advance the effective utilization of information technology

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

commerce, CSL 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-6

Natl. Inst. Stand. Technol. Spec. Publ. 881-6, 37 pages (Feb. 1996)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1996

For sale by the Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402
FOREWORD

In a memorandum of October 26, 1993, the President sought to stimulate the Federal Government's deployment of

Electronic Commerce in order to simplify and streamline the acquisition process. In this regard, the President set forth the following objectives:

0 Exchange acquisition information electronically between the private sector and the Federal Government to the

maximum extent practicable.

0 Provide businesses, including small, small disadvantaged, and woman-owned businesses, with greater access to Federal acquisition opportunities.

0 Ensure that potential suppliers are provided simplified access to the Federal Government's EC system.

0 Employ nationally and internationally recognized data formats that serve to broaden and ease the interchange of

data.

0 Use agency and industry systems and networks to enable the government and potential suppUers to exchange

information and access Federal acquisition data.

As part of the Federal Government wide effort to implement EC, NIST has been given the responsibiUty of coordinating

tlie development and promulgation of Implementation Conventions for the fimctional areas ofEC which will be deployed

across the Agencies.

Various Agencies have been actively pursuing Electronic Data Interchange (EDI) for several years - the DoD, GSA,

Customs and HHS, for instance, have been particularly active in adopting ANSI X12 standards, and looking ahead to EDIFACT. There became a danger that with fiagmentation of usage across the Federal Government a significant burden

would be placed on many small businesses to support an uimecessary profusion of formats and conventions.

In Uie Presidential Memorandum, President Clinton required Federal agencies to implement tlie use of electronic commerce in Federal purchases as quickly as possible. As the initial step, the President's Management Council (PMC)

Electronic Commerce Task Force (ECTF), chaired by the Administrator, OflBce of Federal Procurement Policy (OFPP),

chartered the Federal Electronic Commerce Acquisition Team (ECAT) to complete the first milestone of the President's

memorandum. The PMC assigned the Electronic Commerce Acquisition Team, composed of representatives from

various Federal departments and agencies, the task of defining the architecture for the government electronic commerce

acquisition system and identifying the executive departments or agencies responsible for developing, implementing,

operating, and maintaining the Federal electronic system.

Another key step in the implementation of EDI in the Federal Government relies on the definition of

Implementation Conventions (ICs). EDI syntax standards, both ASC X12 and UN/EDEFACT, accommodate a full range of business activities for all industries. A standard is the result of a consensus among a large number of

users, each with its own set of needs. It is a superset intended to meet the diverse requirements of all users. Standards commonly contain more data elements and structure options than any one user or industry needs. Far

too many opportunities exist for inefficient, or ambiguous transactions. Therefore, actual EDI business processes

require implementation conventions (ICs) to fiilly define transactions. ICs do that by tailoring the use of the

standards' segments, data elements, and code values and providing a subset menu of those distinct parts. This

Special Publication defines a Federal IC based on ASC X12 Version 3050 and is the result of coordinated

development and adoption within the Federal Government.

Federal 855 - Purchase Order Acknowledgment RELEASE- FED 1

855 Purchase Order Acknowledgment

Functional Group ID=PR

Introduction:

This Draft Standard for Trial Use contains the format and establishes 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 used for purchase 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 tlie 850 transaction set is not transmitted, an 855 transaction set should not be used for

acknowledgment.

When BEG07 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.

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.

4. When BAK02 is either code AT or RJ, transmit the mandatory and required segments and data elements. Also

transmit the Nl loop with codes BY and 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 BY and SE.

Heading:

Pos. Seg. Req.

No. ID Name Des. Max.Use

010 ST Transaction Set Header M 1

020 BAK Beginning Segment for Purchase Order M 1 Acknowledgment

Not Used 030 NTE Note/Special Instruction F 100

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 >1

Not Used 090 CTP Pricing Information O >1

Loop

Repeat

Notes and

Comments

35FED855 (003050) 1 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED1

Not Used 095 PAM

Not Used 110 CSH

Not Used 120 SAC

Not Used 125 CUR

130 ITD

Not Used 140 DIS

Not Used 145 INC

Not Used 150 DTM

Not Used 160 LDT

Not Used 180 LIN

Not Used 185 SI

Not Used 190 PID

Not Used 200 MEA

Not Used 210 PWK

Not Used 220 PKG

Not Used 230 TDl

Not Used 240 TD5

Not Used 250 TD3

Not Used 260 TD4

Not Used 270 MAN

Not Used 275 TXl

280 N9

290 MSG

300 Nl

310 N2

320 N3

330 N4

Not Used 335 NX2

340 REF

350 PER

Not Used 360 FOB

Not Used 370 TDl

Not Used 380 TD5

Not Used 390 TD3

Not Used 400 TD4

Not Used 410 PKG

Not Used 420 MSG

Detail:

Pos. Seg.

flO,

010 POl

Period Amount

Header Sale Condition

Service, Promotion, Allowance, or Charge

Information Currency

O

O

o

o

10

1 I

1

1

Terms of Sale/Deferred Terms of Sale O

Discount Detail O

Installment Information O

Date/Time Reference O

Lead Time O

Item Identification O

Service Characteristic Identification O

Product/Item Description O

Measurements O

Paperwork O

Maricing, Packaging, Loading O

Carrier Details (Quantity and Weight) O

Carrier Details (Routing SequenceA'ransit Time) O

Carrier Details (Equipment) O

Carrier Details (Special Handling or Hazardous O

Materials or Both)

Marks and Numbers O

Tax Information O

Reference Number O

Message Text O

5

20

1

10

12

5

2

200

40

25

25

2

12

12

5

10

>1

1

1000

nl

Name O

Additional Name Information O

Address Information O

Geographic Location O

Real Estate Property ID Component O

Reference Numbers O

Administrative Communications Contact O

F.O.B. Related Instructions O

Carrier Details (Quantity and Weight) O

Carrier Details (Routing Sequence/Transit Time) O

Carrier Details (Equipment) O

Carrier Details (Special Handling or Hazardous O

Materials or Both)

Marking, Packaging, Loading O

Message Text O

1

2

2

1

3

12

>1

1

2

12

12

5

25

>1

Name

Req.

Des. Mas.Use

Loop

eat

Baselme Item Data

Repi

Notes and

Comments

o n2

35FED855 (003050) October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED 1

Not Used 018 SI

Not Used 020 CUR

Not Used 030 P03

Not Used 040 CTP

Not Used 045 PAM

Not Used 049 MEA

050 PID

Not Used 060 MEA

Not Used 070 PWK

Not Used 090 P04

Not Used 100 REF

Not Used 110 PER

Not Used 130 SAC

Not Used 135 CUR

Not Used 140 ITS

Not Used 150 ITD

Not Used 160 DIS

Not Used 165 INC

Not Used 170 TAX

Not Used 180 FOB

Not Used 190 SDQ

Not Used 200 DTM

Not Used 210 LDT

Not Used 230 TDl

Not Used 240 TD5

Not Used 250 TD3

Not Used 260 TD4

270 ACK

Not Used 280 DTM

Not Used 290 MAN

Not Used 300 AMT

Not Used 302 TXI

Not Used 303 PKG

Not Used 305 MEA

310 SCH

Not Used 315 TDl

Not Used 320 TD5

Not Used 330 TD3

Not Used 340 TD4

Service Characteristic Identification o 5

Currency o 1

Additional Item Detail O 25

Pricing Information O >1

Period Amount O 10

Measurements O 40

Product/Item Description o 1

Measurements o 10

Paperwork. o 25

Item Physical Details o >1

Reference Numbers o >1

Administrative Communications Contact o 3

Service, Promotion, Allowance, or Charge

Information Currency

Conditions of Sale

Terms of Sale/Deferred Terms of Sale

Discount Detail

Installment Information

Tax Reference

F.O.B. Related Instructions

Destination Quantity

Date/Time Reference

Lead Time

Carrier Details (Quantity and Weight)

Carrier Details (Routing Sequence/Transit Time)

Carrier Details (Equipment)

Carrier Details (Special Handling or Hazardous

Materials or Both)

o 1

o 1

o 1 o 2

o 20

o 1 o >1

o >1

o 500

o 10 o 12 0 1 o 12 o 12 o 5

Date/Time Reference

O

O

Marks and Numbers

Monetary Amount

Tax Information

Marking, Packaging, Loading

Measurements

O

O

o

o

O

10

1

>1

1

>1

n3

Line Item Schedule

Carrier Details (Quantity and Weight)

Carrier Details (Routing Sequence/Transit Time)

Carrier Details (Equipment)

Carrier Details (Special Handling or Hazardous

Materials or Both)

0 1 o 2 0 12 0 12 o 5n4

35FED855 (003050) 3 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE -FEDl

Not Used 350 N9 Reference Number O 1

Not Used 360 MSG Message Text O 1000

Not Used 370 Nl Name o 1

Not Used 380 N2 Additional Name Information o 2

Not Used 390 N3 Address Information o 2

Not Used 400 N4 Geographic Location o 1

Not Used 405 NX2 Real Estate Property ID Component o 3

Not Used 410 REF Reference Numbers o 12

Not Used 420 PER Administrative Communications Contact o 3

Not Used 430 FOB F.O.B. Related Instructions o 1

Not Used 435 SCH Line Item Schedule 0 200

Not Used 440 TDl Carrier Details (Quantity and Weight) 0 2

Not Used 450 TD5 Carrier Details (Routing Sequence/Transit Time) o 12

Not Used 460 TD3 Carrier Details (Equipment) o 12

Not Used 470 TD4 Carrier Details (Special Handling or Hazardous

Materials or Both)

o 5

Not Used 480 PKG Marking, Packaging, Loading o 25

Not Used 490 SLN

Not Used 500 SI

Not Used 510 PID

Not Used 520 P03

Not Used 522 CTP

Not Used 523 PAM

Not Used 530 ACK

Not Used 540 SAC

Not Used 545 CUR

Not Used 550 DTM

Not Used 554 P04

Not Used 557 TAX

Not Used 560 Nl

Not Used 570 N2

Not Used 580 N3

Not Used 590 N4

Not Used 600 NX2

Not Used 610 REF

Not Used 620 PER

Summary:

Pos. Seg. No. ID

010 CTT

Not Used 020 AMT

030 SE

Subline Item Detail

Service Characteristic Identification

Product/Item Description

Additional Item Detail

Pricing Information

Period Amount

Line Item Acknowledgment

Service, Promotion, Allowance, or Charge

Information Currency

O

O

o

o

o

o

o

o

o

1

5

1000

25

25

10

104

1

1

1

Date/Time Reference

Item Physical Details

Tax Reference

O

O

o

10

1

3

iO()Plt>.i\I

Name O

Hi

Additional Name Information 0 2

Address Information O 2

Geographic Location O 1

Real Estate Property ID Component O 3

Reference Numbers O 12

Administrative Communications Contact O 3

Req. Loop Notes and

Name Des. Max.Use Repeat Comments

Transaction Totals M 1 n5

Monetary Amount O 1 n6

Transaction Set Trailer M 1

35FED855 (003050) 4 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FEDl

Transaction Set Notes

1. If segment LIN 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 (POl02) 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

amount as calculated by the sender.

35FED855 (003050) 5 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

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

Data Element Summary

Ref.

Pes.

» STOl

» ST02

Data

Element

143

329

Name Attributes

Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set. 855 X12.9 Purchase Order Acknowledgment

Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set. This unique control number is assigned by the originator ofthe transaction set or by the originator's application program. This same number is carried in

SE02.

35FED855 (003050) 6 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FED1

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

BAK Beginning Segment for Purchase Order Acknowledgment

020

Heading

Mandatory

1To indicate the begiiming 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.

BAKOl

Data

Element

353

Data Element Summary

Name

Transaction Set Purpose Code

Code identifying purpose of transaction set. 00 Original

Attributes

M ID 2/2

» BAK02 587

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

RJ

Acknowledge - With Detail and Change

Use to indicate an order is being acknowledged with

detail and changes. 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

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

Rejected - No Detail

Use to indicate the rejection (without reasons) ofa

purchase order.

35FED855 (003050) 7 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE -FED!

» BAK03

» BAK04

BAK05

X BAK06

BAK07

BAK08

324 Purchase Order Number M AN 1/22

Identifying number for Purchase Order assigned by the orderer/piu-chaser.

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

Use 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 previousfy 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 numberfrom

BEG04 ofthe applicable 850 transaction set. 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 numberfor 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.

1. Use to indicate the Seller's order number

2. When BAK02 is code AC, AD, or AT, 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).

Use to identify the date this 855 transaction set was transmitted.

35FED855 (003050) 8 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

PER Administrative Communications Contact

060

Heading

Optional

3

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

directed.

Use this segment when BAK02 is code AC, AD, or RJ.

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.

»

Ref.

Pes.

PEROl

PER02

PER03

PER04

X

X

X

X

PER05

PER06

PER07

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.

1. Use to identify the name ofthe contact.

2. Cite the last namefirst, followed by the first name. Ifthe whole name is longer than 35 characters, use the initialfor the first name. Ifnecessary, use PER09 to provide the party's title. Communication Number Qualifier X ED 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.

Cite the area code and commercial telephone orfacsimile number ofthe party

identified in PER02.

Communication Number Qualifler 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.

35FED855 (003050) 9 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE -FED]

Segment: FOB F.O.B. Related Instructions

Position: 080

Loop:

Level: Heading

Usage: Optional

Max Use: >1

Purpose: To specify transportation instructions relating to shipment.

Notes: 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 same

information contained in the applicable 850 transaction set.

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.

Syntax Notes:

Semantic Notes:

Comments:

»

Ref.

Pes.

FOBOl

Data

Element

146

Attributes

M ID 2/2

FOB02

FOB03

309

352

Data Element Summary

Name

Shipment Method of Payment

Code identifying payment terms for transportation 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 are prepaid 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

35FED855 (003050) 10 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED 1

A free-form description to clarily the related data elements and their content. X FOB04 334 Transportation Terms Qualifier Code O ID 2/2

Code identifying the source of the transportation terms.

X FOB05 335 Transportation Terms Code X ID 3/3

Code identifying the trade terms which apply to the shipment transportation

responsibility.

X FOB06 309 Location Qualifier X ID 1/2

Code identifying type of location.

X FOB07 352 Description O AN 1/80

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

Code specifying where responsibility for risk of loss passes.

X FOB09 352 Description X AN 1/80

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

35FED855 (003050) 11 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED1

X

X

Segment: ITD Terms of Sale/Deferred Terms of Sale

Position: 130

Loop:

Level: Heading

Usage: Optional

Max Use: 5

Purpose: To specify terms of sale. Notes: 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

in the applicable 850 transaction set.

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 1TD04 ITD05 or ITD 1 3 is required.

3 If ITD09 is present, then at least one of ITD 10 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 ITD 10 or ITDl 1 is required; if the code in ITDOl is 05, then ITD06 or ITD07 is required.

Syntax Notes:

Semantic Notes:

Comments:

Ref.

Pes.

ITDOl

ITD02

ITD03

Data

Element

336

333

338

Attributes

O ID 2/2

O ID 1/2

1/6

X ITD04

ITD05

X ITD06

ITD07

X ITD08

X ITD09

X ITDIO

X ITDll

X ITD12

370

351

446

386

362

388

389

342

352

Data Element Summary

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

Terms discoimt 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

O DT 6/6

N2 1/10

R 1/5

O AN 1/80

35FED855 (003050) 12 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED 1

X ITD13

X ITD14

X ITD15

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

The nmneric value of the day of the month between 1 and the maximmn day of

the month being referenced.

107 Payment Method Code O ID 1/1

Code identifying type of payment procedm^es.

954 Percent O R 1/10

Percentage expressed as a decimal.

35FED855 (003050) 13 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE -FED]

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

N9 Reference Number

280

N9

Heading

Optional

1To transmit identifying nmnbers and descriptive information as specified by the

reference number qualifier.

When BAK02 is code RF, use to provide reasons for rejection of a purchase order.

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.

Data Element Summary

Ref.

Pes.

» N901

X

X

X

N902

N903

N904

N905

N906

Data

Element

128

127

369

373

337

623

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 the following 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

Free-form descriptive text.

This data element may only contain the word "Reason. '

Date

Date (YYMMDD).

Time

X AN 1/45

O DT 6/6

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.

35FED855 (003050) 14 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED1

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

MSG Message Text

290

N9

Heading

Optional

1000

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

Use this segment to provide the reasons for a rejection of a purchase order.

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

page, advance a line, etc.

»

Ref.

Pes.

MSGOl

MSG02

Data

Element

933

934

Data Element Summary

Attributes

M AN 1/264

Name

Free-Form Message Text

Free-form message text.

Printer Carriage Control Code O ID

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

2/2

35FED855 (003050) 15 October I, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE -FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Nl Name

Syntax Notes:

Semantic Notes:

Comments:

300

Nl

Heading

Optional

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

1. Whenever possible, address information should be transmitted using code values

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

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

full 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 of this segment are required with NlOl citing code

BY and SE.

1 At least one of N102 or N103 is required.

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

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

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

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

2 N105 and N106 further define the type of entity in NlOl.

Data Element Summary

Ref.

Pes.

» NlOl

Data

Element

98

Name Attributes

N102

N103

93

66

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 Sliip 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).

While the federal EDIprogram uses the DUNS number, other government users ofthis implementation convention may require the use ofother and additional

numbersfor a transition period in order to cross reference existing data bases

to new procurement actions.

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

Use ofthe DUNs number is preferred over any other

coded number to identify a namedparty.

10 Department of Defense Activity Address Code

(DODAAC)

35FED855 (003050) 16 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FEDl

Use to indicate either a Department ofDefense Activity

Address Code or a Civilian Agency Activity Address

Code.

21 Health Industry I.D. Number (HIN)

Use only when BAK02 is code AC or AD.

33 Commercial and Goverrunent Entity (CAGE)

Use to indicate vendors with CAGE codes.

N104 67 Identification Code X AN 2/20

Code identifying a party or other code.

X NIOS 706 Entity Relationship Code O ID 2/2

Code describing entity relationship.

X N106 98 Entity Identifier Code O ID 2/2

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

35FED855 (003050) 17 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED 1

Segment: N2 Additional Name Information

Position: 310

Loop: Nl

Level: Heading

Usage: Optional

Max Use: 2

Purpose: To specify additional names or those longer than 35 characters in length.

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

inNlOl/03/04.

2. Use only if BAK02 is code AC or AD.

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

applicable 850 transaction set. Syntax Notes:

Semantic Notes:

Comments:

»

Ref.

Pes.

N201

N202

Data

Element

93

93

Data Element Summary

Name

Name

Free-form name. Name

Free-form name.

Attributes

M AN 1/35

O AN 1/35

35FED855 (003050) 18 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FEDl

Segment: N3 Address Information

Position: 320

Loop: Nl

Level: Heading

Usage: Optional

Max Use: 2

Purpose: To specify the location of the named party.

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

in NIO 1/03/04.

2. Use only if BAK02 is code AC or AD.

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

applicable 850 transaction set. Syntax Notes:

Semantic Notes:

Comments:

Data Element Summary

»

Ref.

Pes.

N301

N302

Data

Element

166

166

Name

Address Information

Address information

Address Information

Address information

Attributes

M AN 1/35

O AN 1/35

35FED855 (003050) 19 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FEDl

Segment: N4 Geographic Location

Position: 330

Loop: Nl

Level: Heading

Usage: Optional

Max Use: 1 Purpose: To specify the geographic place of the named party.

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

in NIO 1/03/04.

Syntax Notes:

Semantic Notes:

Comments:

Ref.

Pes.

N401

N402

N403

N404

X N405

X N406

2. UseonlyifBAK02iscodeACor AD.

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

applicable 850 transaction set.

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.

Data Element Summary

Data

Element Name Attributes

19 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 government agency.

116 Postal Code O D) 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 coimtry.

309 Location Qualifier X E) 1/2

Code identifying type of location.

310 Location Identifier O AN 1/30

Code which identifies a specific location.

35FED855 (003050) 20 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED 1

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

REF Reference Numbers

340

Nl

Heading

Optional

12

To specify identifying numbers.

Use of this segment is required in all acknowledgments when NlOl is code SE to

identify the personal identification number of the selling party.

1 At least one of REF02 or REF03 is required.

»

Ref.

Pes.

REFOl

REF02

REF03

Data

Element

128

127

352

Data Element Summary

Name Attributes

Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

EL Electronic device pin number

Use to indicate the identification number assigned to the contractor at the time ofregistration. Use ofthis

code is REQUIRED.

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.

Description X AN 1/80

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

35FED855 (003050) 21 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE -FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

PER Administrative Communications Contact

350

Nl

Heading

Optional

>1

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

directed.

Use this segment when BAK02 is code AT, RF, or RJ.

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.

Data Element Summary

Ref.

Pes.

» PEROl

Data

Element

366

PER02 93

PER03 365

PER04 364

PER05 365

PER06 364

Name Attributes

Contact Function Code M ID 2/2

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

AA Authorized Representative

Use to indicate the person authorized to transmit their

transaction set. Use this code only when BAK02 is AT,

RForRJ.

IC Information Contact

Name O AN 1/35

Free-form name.

Cite the last namefirst, fi)llowed by the first name. Do not truncate the last

name ifthe whole name is longer than 35 characters. Instead, truncate or use

the initial ofthe first name. Ifnecessary, use PER09 to provide 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.

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

Communication Number Qualifier X ID 2/2

Code identifying the type of conmiunication 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 Electronic Mail

EX Telephone Extension

Use only ifPER03 is used citing code TE.

FX Facsimile

TE Telephone

Communication Number X AN 1/80

Complete communications niunber including country or area code when

35FED855 (003050) 22 October 1, 1995
i Federal 855 - Purchase Order Acknowledgment RELEASE - FEDl

applicable.

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

PER07 365 Communication Number Qualifier X YD 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.

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

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.

35FED855 (003050) 23 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED1

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

POl Baseline Item Data

010

POl

Detail

Optional

1To specify basic and most frequently used line item data.

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 the correct line item information when it differs from that contained in the 850 transaction set.

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 1 1 is present, then the other is required.

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

7 If either POl 14 or POl 15 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 PO1 1 8 or PO1 1 9 is 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 P0124 or P0125 is present, then the other is required.

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

3 PO106 through P0125 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.

Ref.

Pes.

POlOl

PO102

PO103

PO104

Data

Element

350

330

355

212

Data Element Summary

Name Attributes

PO105 639

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

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.

Basis of Unit Price Code O ID 2/2

35FED855 (003050) 24 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FEDl

Code identifying the type of unit price for an item.

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

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

Product/Service ID (234).

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

ifdijferent 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

IfBAKOS 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

1/40

2/2

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

Identifying number for a product or service.

POllO 235 Product/Service ID Qualifier X ID

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

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

35FED855 (003050) 25 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED1

P0115 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

P0116 235 Product/Service ID Qualifier X D) 2/2

Code identifying the type/soiu-ce 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.

35FED855 (003050) 26 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FED 1

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

PID Product/Item Description

050

PID

Detail

Optional

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

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, transmit the item description if different than the

description contained in the 850 transaction set.

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.

1 If PIDO 1 = ' T", then PID05 is used. If PIDO 1 =

' ' S", then PID04 is used. If PIDO

1

= "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.

Ref.

Pes.

» PIDOl

X

X

X

X

X

X

proo2

PID03

PID04

proos

PID06

proo7

proos

Data

Element

349

750

559

751

352

752

822

1073

Data Element Summary

Name

Item Description Type

Code indicating the format of a description

F Free-form

Product/Process Characteristic Code

Attributes

M ro 1/1

o ro 2/3

Code identifying the general class of a product or process characteristic

Agency Qualifier Code X ro 2/2

Code identifying the agency assigning the code values.

Product Description Code X AN 1/12

A code fi"om 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 ro 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 ro 1/1

Code indicating a Yes or No condition or response.

35FED855 (003050) 27 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED1

Segment: ACK Line Item Acknowledgment

Position: 270

Loop: ACK

Level: Detail

Usage: Optional

Max Use: 1 Purpose: To acknowledge the ordered quantities and specify the ready date for a specific line

item.

Notes: 1. Use this segment when BAK02 is code AC, AD, or RJ to provide information related

to the line item ordered in the applicable 850 transaction set. When BAK02 is code RJ, use this segment only to identify the rejected line item.

Syntax Notes:

Semantic Notes:

Comments:

2. When providing delivery information, use as many repetitions of this segment as necessary to specify the delivery schedule.

12

3

4

5

6

7

8

9

10

11

12

13

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 ACKIO 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 ACKI8 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.

»

Ref.

Pes.

ACKOl

ACK02

ACK03

ACK04

ACK05

Data

Element

668

380

355

374

373

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

Niuneric value of quantity.

Unit or Basis for Measurement Code X D) 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.

Date/Time Qualifier O ID 3/3

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

073

Date

Date (YYMMDD).

Scheduled for Delivery (Prior to and Including)

Use to indicate the scheduled delivery datefor the

quantity cited inACQ02.

X DT 6/6

35FED855 (003050) 28 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FEDl

X ACK06 326 Request Reference Number O AN 1/45

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

contract number).

X ACK07 235 Product/Service m Qualifier X D) 2/2

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

Product/Service ID (234).

X ACK08 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACKIO 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACK12 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACK14 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACK16 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACK18 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACK20 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACK22 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACK24 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACK26 234 Product/Service ID X AN 1/40

Identifying number for a product or service.

35FED855 (003050) 29 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED1

X ACK27 559 Agency Qualifier Code X ID 2/2

Code identifying the agency assigning the code values.

X ACK28 822 Source Subqualifier X AN 1/15

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

X ACK29 1271 Industry Code X AN 1/20

Code indicating a code from a specific industry code list.

35FED855 (003050) 30 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED 1

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

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 SCHIO is required.

3 If SCH09 is present, then SCH08 is required.

4 If SCHIO is present, then SCH08 is required.

1 SCH12 is the schedule identification.

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

Ref.

Pes.

» SCHOl

» SCH02

X SCH03

X SCH04

» SCH05

» SCH06

SCH07

SCH08

SCH09

SCHIO

Data

Element

380

355

98

93

374

373

337

374

373

337

Data Element Summary

Name Attributes Quantity M R 1/15

Numeric value of quantity.

Unit or Basis for Measurement Code M 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.

Entity Identifier Code O ID 2/2

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

Name X AN 1/35

Free-form name. 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.

Date M DT 6/6

Date (YYMMDD).

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, ifapplicable, to identify the time for a delivery. Specify time only in the

HHMMformat.

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.

Date X 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)

Use, ifapplicable, to identify the time for a delivery. Specify time only in the

HHMMformat.

35FED855 (003050) 31 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED 1

SCHll 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).

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

number.

Alphanumeric characters assigned for differentiation within a transaction set. X SCH12 350 Assigned Identification O AN 1/11

35FED855 (003050) 32 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE - FEDl

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

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.

Data Element Summary

»

Ref.

Pes.

CTTOl

CTT02

Data

Element

354

347

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.

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. X CTT03 81 Weight X R 1/10

Numeric value of weight.

X CTT04 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

X CTT05 183 Volume X R 1/8

Value of volumetric measure. X CTT06 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

X CTT07 352 Description O AN 1/80

A fi-ee-form description to clarify the related data elements and their content.

35FED855 (003050) 33 October 1, 1995
Federal 855 - Purchase Order Acknowledgment RELEASE- FED1

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

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 begiiming (ST) and ending (SE) segments).

SE is the last segment of each transaction set.

»

»

Ref.

Pes.

SEOl

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.

35FED855 (003050) 34 October 1, 1995


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 Instimte'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 NISTlRs—from the National Technical Information

Service, Springfield, VA 22161.

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

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

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

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

Title 15 CFR (Code of Federal Regulations).

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

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

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

in paper copy or microfiche form.
BoO 00

is ^

a>—. o P z

OS

ON

00oQ

o

c3

pa

c

o