liiilli

A1110S 131000

NIST

PUBLICATIONS

SfflBMfflHH ; S9BHI . S B

NIST Special Publication 881-12

4

lllllilllllllllilllllll ,

I l inn ill Hi i in i i i i-i in mi

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 Transaction Set 855

Purchase Order Acknowledgment

Implementation Convention

NIST

U.S. DEPARTMENT OF COMMERCE

Technology Administration

National Institute of

Standards and Technology

QC

100

.157

N0.881-12

1997

NIST Special Publication 881-12

Federal Implementation Guideline

for Electronic Data Interchange

ASC X12 003040 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

March 1997

U.S. DEPARTMENT OF COMMERCE

William M. Daley, Secretary

Technology Administration

Mary L. Good, Under Secretary for Technology

National Institute of Standards and Technology

Arati Prabhakar, 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-12

Natl. Inst. Stand. Technol. Spec. Publ. 881-12, 33 pages (March 1997)

CODEN: NSPUE2

U.S. GOVERNMENT PRINTING OFFICE

WASHINGTON: 1997

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

Functional Group ID=

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 bilateral 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 BIG07 in the 850 transaction set is not transmitted, an 855 transaction set should not be used for

acknowledgment.

When BIG07 in the 850 transaction set is code AC, BIG02 can contain code AC, AD, or RJ.

When BIG07 in the 850 transaction set is code AK, BIG02 can contain code AT, RF or RJ. When BIG07 in the 850 transaction set is code AD, BIG02 can contain code AD or RJ.

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

850 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 12

060 PER Administrative Communications Contact O 3

Not Used 070 TAX Tax Reference O >1

Loop Notes and

Repeat Comments

RELEASE - 003040FED01A August 31, 1994
855 - Purchase Order Acknowledgment

080 FOB

Not Used 090 CTP

Not Used no CSH

Not Used 120 SAC

130 ITD

Not T Wed 140 DIS

14S INC

Not T Wed 150 DTM

Not I ked 160 LDT

Not Used 180 LIN

Not Used 185 SI

Not T Wed 190 PID

Not T Wed 900 UFA

Nnt I Wed 710

Not Used 220 PKG

Not Used 230 TD1

Not Used 240 TD5

Not Used 250 TD3

Not Used 260 TD4

Not Used 270 MAN

Not Used 275 TXI

280 N9

290 MSG

300 Nl

310 N2

320 N3

330 N4

Not I Ised 335 NX2

Not T Wed 340 REF

350 PER

Not Used 360 FOB

Not Used 370 TD1

Not Used 380 TD5

Not Used 390 TD3

Not Used 400 TD4

Not Used 410 PKG

Detail:

Pos. No.Seg.

ID

010 POl

F.O.B. Related Instructions O >1

Pricing Information O 25

Header Sale Condition O 1

Service, Promotion, Allowance, or Charge

Information

1 CI 1 1 io *Jl JdlC L/C1CI I CU 1 CI IIlo Ul OdlC

o 25

cj

Dicfoimt Fietail 90

Installment Tnfr^rmritirtn 11

Date/Time/Period o 10

T e^d Time o 12

Item Identification o 5 nl

Service Characteristic Identification o 2

Product/Item Description o 200

Measurements o 40

Paperwork o 25

Marking, Packaging, Loading o 25

Carrier Details (Quantity and Weight) o 2

Carrier Details (Routing Sequence/Transit Time) o 12

Carrier Details (Equipment) o 12

Carrier Details (Special Handling or Hazardous

Materials or Both)

Marks and Numbers

o

o

5

10

i ax uiioi manon r\1

Reference Number

*¥:¥?:¥:¥:¥:¥: Ml

o 1

i ,

Message Text o 1000

LOQ.PffiUi

Name O 1

Additional Name Information o 2

Address Information o 2

frpopranhir I oration o 1

Real Estate Property ID Component o 3

Reference Numbers o 12

Administrative Communications Contact o 3

F.O.B. Related Instructions o 1

Carrier Details (Quantity and Weight) o 2

Carrier Details (Routing Sequence/Transit Time) o 12

Carrier Details (Equipment) o 12

Carrier Details (Special Handling or Hazardous

Materials or Both)

Marking, Packaging, Loading

o

o

5

25

Name

Baseline Item Data

RELEASE - 003040FED01A 2 August 31, 1994
855 - Purchase Order Acknowledgment

Not Used 018 SI

Not Used 020 CUR

Not usea VjV rKJj

Not Used 040 CTP

Not Used 049 MEA

050 PID

Not Used 060 MEA

XJnt INul TUacU TcpH 07(1 r w IX

Not Used 090 P04

Not Used 100 REF

Not Used 110 PER

Not Used 130 SAC

XT,** T Not Used 14U 115

Not Used i cn1 Jl) 11D

Not used

XT-** T T- - -1 Not Used 165 INC

XT-** I T- . -1 Not Used 170 1 AX

Not Used 180 FOB

Not Used 190 SDQ

Not Used 200 DTM

Not Used 210 LDT

Not Used 220 SCH

Not Used 230 TD1

Not Used 240 TD5

Not Used 250 TD3

Not Used 260 TD4

270 ACK

Not Used 280 DTM

XTrt* I !i- ,-wl [Not used MAIN

Not Used 300 AMT

Not Used 302 TXI

Not Used 303 PKG

Not Used 305 MEA

Not Used 350 N9

Not liUl IU5CU kef. MSG

Not Used 370 Nl

Not Used 380 N2

Not Used 390 N3

Service Characteristic Identification

Currency

Additional Item Detail

Pricing Information

Measurements

Product/Item Description

Measurements

O

O

o

o

o

1

6

o

5

1

25

25

40

mm

1

10

Paperwork O

Item Physical Details O

Reference Numbers O

Administrative Communications Contact O

Service, Promotion, Allowance, or Charge O

Information Conditions of Sale O

Terms of Sale/Deferred Terms of Sale O

Discount Detail O

Installment Information O

Tax Reference O

F.O.B. Related Instructions O

Destination Quantity O

Date/Time/Period O

Lead Time O

Line Item Schedule 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)

25

1

12

3

25

1

2

20

1

>1

1

500

10

12

200

1

12

12

5

n3

Line Item Acknowledgment

Date/Time/Period

o

o

Marks and Numbers

Monetary Amount

Tax Information

||§|||§§

Marking, Packaging, Loading

Measurements

O

o

o

lis

o

o

10

1

>1

I

1

>1

n4

Reference Number

Message Text

O

O

1

1000

Name

Additional Name Information

Address Information

O

O

o

RELEASE - 003040FED01A 3 August 31, 1994
855 - Purchase Order Acknowledgment

in ot usee Ann XT/1 IN4

IN 01 useu er\Jj XJV7 IN Ax

INOl UScQ ivcr

1NUL U&CU r CIV

Kr»t INUl TUbCU FOB

Not Used 435 SCH

Not Used 440 TD1

Not Used 1 Uj

Not Used 460 TD3

Not Used 470 TD4

Not Used 480 PKG

INUl U3CU 490 SI N

Nnt I keH 500 SI

Not Used 510 PID

Not Used 520 P03

Not Used 522 CTP

Not Used 530 ACK

Not Used 540 SAC

Not Used 550 DTM

Not I ked 554 P04

1NUL UoCU N1

Mnt T IcpH

Not Used 580 N3

Not Used 590 N4

Not Used 600 NX2

Not Used 610 REF

Not Used 620 PER

Summary:

Pos. No. 010

Seg. IDCTT

Not Used 020 AMT

030 SE

Geographic Location

Real Estate Property ID Component

Reference Numbers

Administrative Communications Contact

F.O.B. Related Instructions

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)

Marking, Packaging, Loading

o 1 U J

Li 1

1

1j

11 o 200

o 2 o 12 o 12 o 5

o 25

^^^^;•^^^^^^^:<'^^:"X'^^Kv:'I Subline Item Detail

Service Characteristic Identification

Product/Item Description

Additional Item Detail

Pricing Information

Line Item Acknowledgment

Service, Promotion, Allowance, or Charge

Information Date/Time/Period

Item Physical Details

Name

Additional Name Information

Address Information

Geographic Location

Real Estate Property ID Component

Reference Numbers

Administrative Communications Contact

o 1 o 5 0 1000

o 25 o 25 o 104 o 10

o 10 o 1

O 1 O 2 O 2 O 1 O 3 O 12 O 3

Name

Transaction Totals

Monetary Amount

Transaction Set Trailer

Req.

Pes. M

O

M

Max.Use

1

1

1

Loop

Repeat

Notes and

Comments

n5

n6

Transaction Set Notes

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

2. PO102 is required.

3. 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 (SCH01)

should always equal the quantity ordered (POl02) in the POl segment.

RELEASE - 003040FED01A 4 August 31, 1994
855 - Purchase Order Acknowledgment

4. If AMT is used in the detail area, then AMT01 will = 1 and AMT02 will indicate total line amount as

calculated by the sender.

5. The number of line items (CTT01) 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 AMT01 will = TT and AMT02 will indicate total transaction

amount as calculated by the sender.

RELEASE - 003040FED01A 5 August 31, 1994
855 - Purchase Order Acknowledgment

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

» ST01

» ST02

Data

Element

143

329

Attributes

M ID 3/3

Data Element Summary

Name

Transaction Set Identifier Code

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.

RELEASE - 003040FED01A 6 August 31, 1994
855 - Purchase Order Acknowledgment

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 beginning of the purchase order acknowledgment transaction set and

transmit identifying numbers and dates.

1 BAK08 is the seller's order number.

»

Ref.

Pes.

BAK01

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

Used 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

Acknowledge - With Detail and Change

Use to indicate an order is being acknowledged with

detail and changes. Use this code only ifBlG07 in the

application 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 BIG07

in the applicable 850 transaction set was code AC of

AD.

AT

RF

RJ

Accepted

Use to indicate acceptance ofa bilateral purchase

order. Use this code only ifBIG07 in the applicable

850 transaction set was code AK.

Reject with Exception Detail Only

Use to indicate a rejection (with reasons) ofa bilateral

purchase order. Use this code only ifBIG07 in the

applicable 850 transaction set was code AK.

Rejected - No Detail

Use to indicate the rejection (without reasons) ofa

bilateral purchase order. Use this code only ifBIGO?

in the applicable 850 transaction set was AC, AD, or AK.

RELEASE - 003040FED01A 7 August 31, 1994
855 - Purchase Order Acknowledgment

» BAK03 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. » BAK04 323 Purchase Order Date M DT 6/6

Date assigned by the purchaser to Purchase Order.

Use to identify the date ofthe purchase order to which this transaction set

applies. Cite the date from BEG05 ofthe applicable 850 transaction set. X BAK05 328 Release Number O AN 1/30

Number identifying a release against a Purchase Order previously placed by the

parties involved in the transaction.

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

X BAK07 367 Contract Number O AN

Contract number.

BAK08 127 Reference Number O AN

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.

1/30

1/30

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. The number is used to

facilitate references in future communications.

BAK09 588 Acknowledgment Date O DT 6/6

Date assigned by the sender to the acknowledgment.

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

RELEASE - 003040FED01A 8 August 31, 1994
I

i

855 - Purchase Order Acknowledgment

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.

Data Element Summary

»

X

X

Ref.

Pes.

PER01

PER02

PER03

PER04

PER05

PER06

Data

Element Name Attributes

366 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

93 Name O AN 1/35

Free-form name.

1. Use to indicate the name and title ofthe contact.

2. Cite the last namefirst, followed by the first name, followed by the title. If

the name and title are longer than 35 characters, use the initialfor the first name. 365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number.

FX Facsimile

TE Telephone

364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable.

Cite the area code and commercial telephone number ofthe party identified in

PER02.

365 Communication Number Qualifier X ID 2/2

Code identifying the type of communication number.

364 Communication Number X AN 1/80

Complete communications number including country or area code when

applicable.

RELEASE - 003040FED01A 9 August 31, 1994
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

FOB F.O.B. Related Instructions

080

Heading

Optional

>1

To specify transportation instructions relating to shipment

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

2. When BAK02 is code AC or 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 FOB01 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.

Comments:

»

Ref.

Pes.

FOB01

Data

Element

146

Data Element Summary

Name

Shipment Method of Payment

Code identifying payment terms for transportation charges.

Attributes

M ID 2/2

BP

PE

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 that the FOB point is origin.

Prepaid and Summary Bill

Use to indicate transportation charges are authorized

to be prepaid by the seller and added to the invoice.

Do not use this code when transmitting an 855

transaction set to the Department of Veteran Affairs.

PP Prepaid (by Seller)

Use to indicate that the FOB point is destination.

X FOB02 309 Location Qualifier X ID 1/2

Code identifying type of location.

X FOB03 352 Description O AN 1/80

A free-form description to clarify 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

RELEASE - 003040FED01A 10 August 31, 1994
855 - Purchase Order Acknowledgment

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.

RELEASE - 003040FED01A 11 August 31, 1994
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

ITD Terms of Sale/Deferred Terms of Sale

130

Heading

Optional

5

To specify terms of sale.

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

2. When BAK02 is code AC or 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 13 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 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 ITD0 1 is 04, then ITD07 or ITD09 is required and either ITD 10 or ITD 11 is required; if the code in ITD01 is 05, then ITD06 or ITD07 is required.

X

X

X

X

X

X

Ref.

Pes.

ITD01

ITD02

ITD03

ITD04

ITD05

ITD06

ITD07

ITD08

ITD09

ITD10

ITD11

Data

Element

336

333

338

370

351

446

386

362

388

389

342

Attributes

O ID 2/2

O ID 1/2

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

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.

O DT 6/6

X N2 1/10

R 1/5

RELEASE - 003040FED01A 12 August 31, 1994
855 - Purchase Order Acknowledgment

X

X

X

X

ITD12

ITD13

ITD14

ITD15

352 Description O AN 1/80

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

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

the month being referenced.

107 Payment Method Code O ID 1/1

Code identifying type of payment procedures.

954 Percent O R 1/10

Percentage expressed as a decimal

RELEASE - 003040FED01A 13 August 31, 1994
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

N9 Reference Number

280

N9

Heading

Optional

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

reference number qualifier

When BAK02 is code RF, use to provide reasons for rejection of a bilateral 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.

Ref.

Pes.

» N901

Data

Element

128

Attributes

M ID 2/2

Data Element Summary

Name

Reference Number Qualifier

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.

X

X

N902

N903

N904

N905

N906

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

369 Free-form Description X AN 1/45

Free-form descriptive text.

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

373 Date

Date (YYMMDD).

337 Time

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)

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

O DT 6/6

TM 4/8

RELEASE - 003040FED01A 14 August 31, 1994
855 - Purchase Order Acknowledgment

Segment: Message Text

Position: 290

Loop: N9

Level: Heading

Usage: Optional

Max Use: 1000

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

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

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

Syntax Notes:

Semantic Notes:

page, advance a line, etc.

Data Element Summary

»

Ref.

Pes.

MSG01

Data

Element

933 Free-Form Message Text M AN

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.

Name Attributes

1/264

X MSG02 934 2/2

RELEASE - 003040FED01A 15 August 31, 1994
855 - Purchase Order Acknowledgment

Segment: Nl Name

Position: 300

Loop: Nl

Level: Heading

Usage: Optional

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

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

contained in a combination of the N101, 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.

Syntax Notes:

Semantic Notes:

Comments:

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

applicable 850 transaction set.

3. At least 2 iterations of this segment are required with N101 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 N101.

Data Element Summary

Ref.

Pes.

» N101

Data

Element

98

N102

N103

93

66

Name Attributes

Entity Identifier Code M ID 2/2

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

BY

SE

ST

Buying Party (Purchaser)

Selling Party

Ship To

Use only when BAK02 is code AC or AD.

Name X AN 1/35

Free-form name. Use only ifBIG07 in the applicable 850 transaction set was code AC or AD.

Identification Code Qualifier X ID 1/2

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

Code (67).

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

Use ofthe DUNs number is preferred over any other

coded number to identify a namedparty.

Department of Defense Activity Address Code

(DODAAC)

Use to indicate either a Department ofDefense Activity

Code or a Civilian Agency Activity Address Code.

10

RELEASE - 003040FED01A 16 August 31, 1994
855 - Purchase Order Acknowledgment

2 1 Health Industry I.D. Number (fflN)

Use only when BAK02 is code AC or AD.

33 Commercial and Government Entity (CAGE)

Use to indicate vendors with CAGE codes.

N104 67 Identification Code X AN 2/17

Code identifying a party or other code.

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

RELEASE - 003040FED01A 17 August 31, 1994
855 - Purchase Order Acknowledgment

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

in N10 1/03/04.

2. Use only if BIG07 in the applicable 850 transaction set was code AC or AD.

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

applicable 850 transaction set.

Syntax Notes:

Semantic Notes:

Comments:

»

Ref.

Pes.

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

RELEASE - 003040FED01A 18 August 31, 1994
855 - Purchase Order Acknowledgment

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 N101/03/04.

2. Use only if BIG07 in the applicable 850 transaction set was code AC or AD.

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

applicable 850 transaction set. Syntax Notes:

Semantic Notes:

Comments:

»

Ref.

Pes.

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

RELEASE - 003040FED01A 19 August 31, 1994
855 - Purchase Order Acknowledgment

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 N10 1/03/04.

Syntax Notes:

Semantic Notes:

Comments:

2. Use only if BIG07 in the applicable 850 transaction set was code AC or AD.

3. When BAK02 is code AC or 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

X

X

Ref.

Pes.

N401

N402

N403

N404

N405

N406

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 ID 3/9

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.

RELEASE - 003040FED01A 20 August 31, 1994
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

PER Administrative Communications Contact

350

Nl

Heading

Optional

3

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.

Data Element Summary

Ref.

Pes.

» PER01

Data

Element

366

PER02

PER03

PER04

PER05

Name Attributes

ID 2/2

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 this

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

IC Information Contact

93 Name O AN 1/35

Free-form name.

Cite the last namefirst, followed by the first name. Do not truncate the last

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

the initial ofthe first name. 365 Communication Number Qualifier

Code identifying the type of communication number.

EM Electronic Mail

FX Facsimile

TE Telephone

364 Communication Number

Complete communications number including country or area code when

applicable.

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

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.

X AN 1/80

EM

EX

FX

TE

Electronic Mail

Telephone Extension

Use only ofPER03 is used citing code TE.

Facsimile

Telephone

PER06 364 Communication Number AN 1/80

RELEASE - 003040FED01A 21 August 31, 1994
855 - Purchase Order Acknowledgment

Complete communications number including country or area code when

applicable.

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

RELEASE - 003040FED01A 22 August 31, 1994
855 - Purchase Order Acknowledgment

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 AC or 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 IfPO103 is present, then POl02 is required.

2 IfPO105 is present, then PO104 is required.

3 IfPO106 is present, then POl07 is required.

4 IfPO108 is present, then PO109 is required.

5 If POl 10 is present, then POl 11 is required.

6 IfP0112 is present, then POl 13 is required.

7 IfP0114 is present, then POl 15 is required.

8 IfP0116 is present, then POl 17 is required.

9 IfPOH8 is present, then POl 19 is required.

10 IfPO120 is present, then P0121 is required.

11 IfP0122 is present, then P0123 is required.

12 IfP0124 is present, then POl 25 is required.

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

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

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

SKU.

Data Element Summary

Ref.

Pes.

PO101

PO102

PO103

Data

Element

350

330

355

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

PO104 212

Refer to 003040 Data Element Dictionary for acceptable code values.

Unit Price X R 1/14

RELEASE - 003040FED01A 23 August 31, 1994
855 - Purchase Order Acknowledgment

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,

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

National Stock Number

Lot Number

Manufacturer

National Drug Code (NDC)

Serial Number

Vendor's (Seller's) Part Number

AN 1/30

O ID 2/2

FS

LT

MF

ND

SN

VP

PO107 234 Product/Service ID

Identifying number for a product or service

PO108 235 Product/Service ID Qualifier

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

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

PO109 234 Product/Service ID X AN

Identifying number for a product or service.

PO110 235 Product/Service ED Qualifier O ID

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

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

POlll 234 Product/Service ED X AN

Identifying number for a product or service.

P0112 235 Product/Service ED Qualifier O ED

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

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

P0113 234 Product/Service ED X AN

Identifying number for a product or service.

P0114 235 Product/Service ED Qualifier O ED

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

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

1/30

2/2

1/30

2/2

1/30

2/2

RELEASE - 003040FED01A 24 August 31, 1994
855 - Purchase Order Acknowledgment

P0115 234 Product/Service ID X AN 1/30

Identifying number for a product or service.

POH6 235 Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

P0117 234 Product/Service ID X AN 1/30

Identifying number for a product or service.

P0118 235 Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

POH9 234 Product/Service ID X AN 1/30

Identifying number for a product or service.

PO120 235 Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

P0121 234 Product/Service ID X AN 1/30

Identifying number for a product or service.

P0122 235 Product/Service ID Qualifier O ID 2/2

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

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

P0123 234 Product/Service ID X AN 1/30

Identifying number for a product or service.

P0124 235 Product/Service ID Qualifier O ED 2/2

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

Product/Service ID (234).

Refer to 003040 Data Element Dictionary for acceptable code values.

P0125 234 Product/Service ED X AN 1/30

Identifying number for a product or service.

RELEASE - 003040FED01A 25 August 31, 1994
855 - Purchase Order Acknowledgment

Segment: PID Product/Item Description

Position: 050

Loop: PID

Level: Detail

Usage: Optional

Max Use: 1 Purpose: To describe a product or process in coded or free-form format

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

2. When BAK02 is code AC or 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 840 transaction set.

Syntax Notes:

Semantic Notes:

Comments:

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 = "F", then PID05 is used. If PfDO 1 = " S", then PID04 is used. If PIDO

1

= "X", then both P1D04 and P1D05 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 PED03.

Ref.

Pes.

» PID01

X

X

X

X

X

X

PID02

PID03

PID04

PID05

PID06

PID07

PID08

Data

Element

349

750

559

751

352

752

822

1073

Attributes

M ID 1/1

Data Element Summary

Name

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

RELEASE - 003040FED01A 26 August 31, 1994
855 - Purchase Order Acknowledgment

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.

1 If ACK02 is present, then ACK03 is required.

2 If ACK04 is present, then ACK05 is required.

3 If ACK07 is present, then ACK08 is required.

4 If ACK09 is present, then ACK10 is required.

5 If ACK11 is present, then ACK12 is required.

6 If ACK13 is present, then ACK14 is required.

7 If ACK15 is present, then ACK16 is required.

8 If ACK17 is present, then ACK18 is required.

9 If ACK1 9 is present, then ACK20 is required.

10 If ACK2 1 is present, then ACK22 is required.

11 If ACK23 is present, then ACK24 is required.

12 If ACK25 is present, then ACK26 is required.

13 If either ACK27 or ACK28 is present, then the other is required.

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

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

Data Element Summary

»

Ref.

Pes.

ACK01

Data

Element

668

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.

AC Item Accepted and Shipped

AR Item Accepted and Released for Shipment

BP Item Accepted - Partial Shipment, Balance

Backordered

DR Item Accepted - Date Rescheduled

IA Item Accepted

IB Item Backordered

IC Item Accepted - Changes Made

ID Item Deleted

BE Item Accepted, Price Pending

IF Item on Hold, Incomplete Description

ffl Item on Hold

RELEASE - 003040FED01A 27 August 31, 1994
855 - Purchase Order Acknowledgment

ACK05

X ACK06

IP Item Accepted - Price Changed

IQ Item Accepted - Quantity Changed

IR Item Rejected

IS Item Accepted - Substitution Made

IW Item on Hold-Waiver Required

SP Item Accepted - Schedule Date Pending

ACK02 380 Quantity O R 1/15

Numeric value of quantity.

ACK03 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

Refer to 003040 Data Element Dictionary for acceptable code values.

ACK04 374 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 date for the

quantity cited inACK02.

373 Date X DT 6/6

Date (YYMMDD).

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

X ACK07 235 Product/Service ID Qualifier O ID 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/30

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACK10 234 Product/Service D3 X AN 1/30

Identifying number for a product or service.

X ACK11 235 Product/Service ID Qualifier O 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/30

Identifying number for a product or service.

X ACK13 235 Product/Service ID Qualifier O 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/30

Identifying number for a product or service.

X ACK15 235 Product/Service ID Qualifier O 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/30

Identifying number for a product or service.

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

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

RELEASE - 003040FED01A 28 August 31, 1994
855 - Purchase Order Acknowledgment

X AN 1/30

Product/Service ID (234).

X ACK18 234 Product/Service ID

Identifying number for a product or service.

X ACK19 235 Product/Service ID Qualifier O 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/30

Identifying number for a product or service.

X ACK21 235 Product/Service ID Qualifier O 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/30

Identifying number for a product or service.

X ACK23 235 Product/Service ID Qualifier O 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/30

Identifying number for a product or service.

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

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

Product/Service ID (234).

X ACK26 234 Product/Service ID

Identifying number for a product or service.

X ACK27 559 Agency Qualifier Code

Code identifying the agency assigning the code values.

X ACK28 822 Source Subqualifier

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

AN 1/30

ID 2/2

AN 1/15

RELEASE - 003040FED01A 29 August 31, 1994
855 - Purchase Order Acknowledgment

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 CTT03 is present, then CTT04 is required.

2 If CTT05 is present, then CTT06 is required.

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

and correctness.

»

X

X

X

X

X

Ref.

Pes.

CTT01

CTT02

Data

Element

354

347

CTT03

CTT04

CTT05

CTT06

CTT07

81

355

183

355

352

Attributes

M NO 1/6

Data Element Summary

Name

Number of Line Items

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. Weight O R 1/10

Numeric value of weight.

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

Volume O R 1/8

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

Description O AN 1/80

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

RELEASE - 003040FED01A 30 August 31, 1994
855 - Purchase Order Acknowledgment

Segment:

Position:

Loop:

Level:

Usage:

Max Use:

Purpose:

Notes:

Syntax Notes:

Semantic Notes:

Comments:

SE

030

Transaction Set Trailer

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.

» SE01

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

RELEASE - 003040FED01A 31 August 31, 1994



Technical Publications

Periodical

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

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

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

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

Nonperiodicals

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

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

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

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

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

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

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

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

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

20056.

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

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

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

characteristics of building elements and systems.

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

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

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

other government agencies.

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

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

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

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

standardizing organizations.

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

Service, Springfield, VA 22161.

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

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

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

1 127), and as implemented by Executive Order 1 1717 (38 FR 12315, dated May 1 1, 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.
O c/5 = o E 3 **-*

ooI a\

On

00o

O 60

om

H

a

C >