ASC X12 Version/Release 004010

850 – Purchase Order

Implementation Guide
850 Implementation Guide Victor Reinz Division

Document Change Log

VERSION DATE DESCRIPTION
1.0 10/15/02 Initial document issued.

This document is the intellectual property of the Victor Reinz Division of Dana Corporation. This
document must not be reproduced in whole or part without written consent from Victor Reinz Division.

For comments and suggestions concerning this document; contact Bob Mulvey at 630/271-4862 or email at
[email protected]

850-004010 Page 2 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Table of Contents
1. Table of Contents…………………………………………………… 3

2. Introduction………………………………………………………… 5

3. Transaction Set Definition………………………………………….. 5

4. Functional Definition……………………………………………….. 5

5. Principles…………………………………………………………… 5

6. References………………………………………………………….. 6

7. Application…………………………………………………………. 7

8. Transaction Set Description………………………………………… 7

9. Interchange Terms of Reference…………………………………… 8

10. Delimiter Terms of Reference……………………………………… 8

11. Header Segment Addressing………..……………………………… 9

11.1. Interchange Header………………………………………….. 9
11.2. Functional Group Header……………………………………. 9

12. Functional Group Terms of Reference……………………………… 9

13. Acknowledgements…………………………………………………. 10

14. How To Read This Documentation…………………………………. 10

14.1. Transaction Set Table…………………………………………10
14.2. Segment Usage………………………………………………. 10
14.3. Data Element Usage…………………………………………. 10

15. Transaction Set Table………………………………………………. 12

16. Business Data Matrix……………………………………………….. 13

850-004010 Page 3 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

17. Segment Descriptions

17.1. ST – Transaction Set Header………………………………… 14
17.2. BEG – Beginning Segment for Purchase Order…..…………. 15
17.3. FOB – F.O.B. Related Instructions………………………….. 16
17.4. ITD – Terms of Sale/Deferred Terms of Sale……………….. 17
17.5. DTM – Date/Time Reference…………………………………18
17.6. N1 - Name…………………………………………………… 19
17.7. N3 – Address Information…………………………………… 21
17.8. N4 – Geographic Location…………………………………... 22
17.9. PER – Administrative Communications Contact……………. 23
17.10. PO1 – Baseline Item Data…………………………………… 24
17.11. CTP – Pricing Information…………………………………... 27
17.12. CUR – Currency………………………………………………29
17.13. PID – Product/Item Description….………………………… 30
17.14. SCH – Line Item Schedule……………………………………32
17.15. SE - Transaction Set Trailer………………………………… 34

18. EXAMPLES
18.1. Order for a single part………………………..……………… 35
18.2. Orders for Multiple parts……………………………………. 36

850-004010 Page 4 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

2. Introduction

This document provides the specific description of a subset of the ANSI ASC X12
Purchase Order Transaction Set to be used between a Victor Reinz Division facility and a
supplier. Hereafter the Transaction Set will be called either “850” or “Purchase Order”.

3. Transaction Set Definition

This document provides the definition of a Purchase Order based on the ANSI ASC X12
850 to be used in Electronic Data Interchange (EDI) between a Victor Reinz Division
facility and a supplier.

This Implementation Guide is fully comprehensive and allows for the installation of the
ANSI ASC X12 850 Transaction Set without the necessity of any additional ASC X12
Standards documentation.

4. Functional Definition

The Purchase Order is a Transaction Set from a Victor Reinz Division facility to a Victor
Reinz Division supplier. It provides information concerning the part number, unit price,
quantity and due date requirements for a part being ordered.

5. Principles

The Purchase Order intends to:

• advise the supplier of a part (or parts) being ordered with a specific requested
delivery date and quantity,

• advise the supplier of the unit price Victor Reinz expects to pay for the part
(or parts),

• advise the supplier which Victor Reinz Division facility or joint venture to
ship the part (or parts) to, and

• advise the supplier of the Victor Reinz buyer’s name and telephone number
that can be used for follow-up actions regarding the order.

A Purchase Order can relate to:

• a single part with a single requirement,

850-004010 Page 5 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

• a single part with multiple requirements,

• multiple parts with single requirements, or

• multiple parts with multiple requirements.

The Purchase Order will always include the Purchase Order Number, Part Number being
ordered (Victor Reinz Part Number or supplier part number), unit price, quantity required
and expected delivery date.

As the information transmitted in the Purchase Order is vital to insure efficient and timely
delivery of the materials to the Victor Reinz facility, it is expected that the information
contained within it is read into the supplier’s MRP or Order Entry system in an
automated fashion whenever possible.

6. References

The contents of this Transaction Set are based upon:

• the Transaction Set structure as defined by ASC X12 as a Draft Standard For
Trial Use (DSTU) by the Procedures Review Board in October, 1997 and as
published in Version/Release 004010.

• the agreement between the Trading Partners on the data elements to be used,
their unique definitions, their representation and their values (coded or clear-
form) as defined in this document.

Victor Reinz Division has opted for ASC X12 Version/Release 004010 and will be
consistently using this Version/Release for all of its X12-enabled suppliers.

The language to be used for all Victor Reinz Division ASC X12 Transaction Sets and
UN/EDIFACT Messages is (American) English.

Dun and Bradstreet numbers (DUNS) will be used to identify the interchange
Sender/Receiver, Functional Group Application Sender/Receiver and Victor Reinz
Division facility Ship To. Victor Reinz Division facility-assigned vendor ID numbers
will be used to identify the supplier within the Transaction Set. These vendor ID
numbers will vary from facility to facility

A companion EDIFACT Message, the Purchase Order (ORDERS) based upon the
UN/EDIFACT D97.A directory is also used by the Victor Reinz Division for EDIFACT-
enabled Suppliers.

The Automotive Industry Action Group (AIAG) has issued Implementation Guidelines
for Version/Release 004010 of the 850 (Publication EG8, issued 2/98, available from
AIAG Customer Service at 248/358-3003 or visit http://www.aiag.org). This subset of

850-004010 Page 6 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

the 850 defined by Victor Reinz Division and described in this document follows as close
as possible the structure of the AIAG subset. Variances from the AIAG are as follows:

• Shipping address information is contained within the N2 and N3 segments rather

than the N2 through N4 segments.

• The N103 Identification Code Qualifier Data Element for a supplier uses code
value 92 (Assigned by Buyer or Buyer’s Agent).

• The PID Product/Item Description segment uses a free form text description
rather than a structured industry code list.

• The optional CTT Transaction Totals segment is not used

7. Application

The following definition of a Purchase Order in X12 format is applicable for the
interchange of order requirements and shipping instructions issued by Victor Reinz
Division for material shipments to one or more Victor Reinz Division facilities.

8. Transaction Set Description

The following pages contain a full description of the ASC X12 850 as implemented by
Victor Reinz Division. Optional Segments or Data Elements not used in the Transaction
Set by Victor Reinz Division have not been included. The official ASC X12 segment
description has been complimented with remarks pertaining to the specific requirements
for an interchange with Victor Reinz Division. Those remarks contain specific code
values used, additional information on the values shown in a specific field, etc and are
shaded in gray.

850-004010 Page 7 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

9. Interchange Terms of Reference

The following chart defines usage of the data elements contained within the Interchange
Header segment to be used for the Purchase Order:

DATA ELEMENT USE

ISA01 – Authorization Information Qualifier 00 – No Authorization Information Present
ISA02 – Authorization Information Not Used – blank
ISA03 – Security Information Qualifier 00 – No Security Information Present
ISA04 – Security Information Not Used – blank
ISA05 – Interchange ID Qualifier 01 – DUNS (Dun & Bradstreet Number)
ISA06 – Interchange Sender ID 096799101 (Victor Reinz Division)
ISA07 – Interchange ID Qualifier 01 – DUNS (Dun & Bradstreet Number)
ISA08 – Interchange Receiver ID Supplier's DUNS Number
ISA09 – Interchange Date Date of Interchange in format YYMMDD
ISA09 – Interchange Time Time of Interchange in format HHMM
ISA10 – Interchange Control Standards U - U.S. EDI Community of X12, TDCC and UCS
ISA11 – Interchange Control Version Number 00200 - DSTU approved for use through 10/97
ISA12 – Interchange Control Number Unique identifier assigned by Victor Reinz
ISA13 – Acknowledgement Requested 1 – Interchange Acknowledgement Requested
ISA14 – Usage Indicator P – Production Data T - Test Data
ISA15 – Component Element Separator Refer to Delimiter Terms of Reference Table

10. Delimiter Terms of Reference

The actual values of the delimiters are set by the Interchange Control Header in the
following positions:

DELIMITER POSITION IN ISA HEADER

Data Element 4
Component Element 105
Segment 106

Because of the potential conflicts with either the data elements or with special data used
in the transmission or device control, Victor Reinz Division has selected the following
delimiter characters for use:

DELIMITER CHARACTER ASCII HEX EBCDIC HEX

Element * 2A 5C
Component Element ^ 5E 5F
Segment ~ 7E A1

850-004010 Page 8 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

While the ‘New Line’ character (EBCDIC 15) has been widely used as the Segment
Delimiter, there is not a clear mapping for this character between the EBCIDC and ASCII
character sets. For that reason, Victor Reinz Division discourages its use.

11. Header Segment Addressing

11.1. Interchange Header

COMMUNICATIONS VICTOR REINZ DIVISION
METHOD SENDER ID FOR ISA06
Victor Reinz Supplier Web Site 096799101
Internet FTP 096799101
Internet Email 096799101

11.2. Functional Group Header

VICTOR REINZ FACILITY
VICTOR REINZ APPLICATION SENDER FOR
DIVISION FACILITY GS02
Avilla, Indiana 878833979
Chatham, Ontario 249186818
Danville, Kentucky 188962112
Lisle, Illinois 096799101
Milwaukee, Wisconsin 848532529
Robinson, Illinois 047074661

12. Functional Group Terms of Reference

The following chart defines usage of the data elements contained within the Interchange
Header segment to be used for the Purchase Order:

DATA ELEMENT USE

GS01 - Functional ID Code PO – Purchase Order
GS02 - Application Sender's Code Refer to Header Segment Addressing Table above
GS03 - Application Receiver's Code Suppliers DUNS Number
GS04 - Group Date Date of Functional Group in format YYMMDD
GS05 - Group Time Time of Functional Group in format HHMM
GS06 - Group Control Number Unique identifier assigned by Victor Reinz
GS07 - Responsible Agency Code X – Accredited Standards Committee X12
GS08 - Version/Release Industry ID Code 004010

850-004010 Page 9 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

13. Acknowledgements

A 997 Functional Acknowledgement must be returned to Victor Reinz Division for each
850 issued with an AK1/AK9 pair used to indicate the Functional Group being
acknowledged, an AK2/AK5 pair used to indicate the Transaction Set begin
acknowledged and, optionally, AK3 and AK4 segments used to report syntax errors. The
Sender/Receiver ID's in the ISA header of the Purchase Order should be reversed and
used for receiver addressing when sending the acknowledgement.

14. How to Read the Documentation

14.1. Transaction Set Table

Only segments used by Victor Reinz Division are listed in the table. Mandatory and
some optional segments are required. The Functional Group Identifier is provided.

14.2. Segment Usage

Only those segments used by Victor Reinz Division are included in this section of
the document.

Segment Name, Level, Table, Loop, Usage, Max Use, Purpose, Syntax, and
Comments are taken directly from the ASC X12 004010 Standards.

Victor Reinz Division notes for the entire segment appears after the Comments
section and are shaded in gray.

Examples are provided to aid in understanding the usage.

14.3. Data Element Usage

Data elements used by Victor Reinz Division are shown. Mandatory and some
optional Data Element are required. Trailing data elements not used in a segment by
Victor Reinz Division are not shown. ASC X12 codes used by Victor Reinz
Division appear after the data element and are shaded in gray. Data elements can
also have their usage specified notes shaded in gray.

Numeric (Nn) and decimal (R) fields are assumed to be positive unless a leading
minus sign indicating a negative value is transmitted. A plus sign is never
transmitted.

850-004010 Page 10 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

If a data element is not transmitted, its default value should not be assumed.

Numeric and decimal data will be transmitted with only significant zeros.

Alphanumeric data elements will be transmitted with no leading or trailing blanks.

The following Data Element Attributes are used throughout the document:

Requirement Designators:
M - Mandatory. Required information.
X - Conditional. The data element is required based on a defined condition stated
in the X12 standard.
O - Optional. Information is not required by the X12 standard but may be used
by Victor Reinz Division

Data Element Types:

Nn - Numeric with n specified decimal places (implied decimal point)
R - Explicit decimal point
AN - Alphanumeric
DT - Date
TM - Time
ID - Identification code

The following are standardized notes that are used throughout this document.

Required
Indicates that Victor Reinz requires data in this data element if the segment is
being used.

Any Code
When the term Any Code is used, it refers to any code defined by ASC X12 at
Version/Release 004010.

Not Used
Indicates that Victor Reinz Division does not use this data element.

850-004010 Page 11 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

15. Transaction Set Table

850 Purchase Order

Functional Group = PO

Heading
POS.#. Seg. ID Segment Name Req. Des. Max Use Loop Repeat
010 ST Transaction Set Header M 1
020 BEG Beginning Segment for Purchase Order M 1
080 FOB F.O.B. Related Instructions O >1
130 ITD Terms of Sale/Deferred Terms of Sale O >1
150 DTM Date/Time Reference O 10
Loop ID – N1 200
310 NI Name O 1
330 N3 Address Information O 2
340 N4 Geographic Location O >1
360 PER Administrative Communications Contact O >1

Detail
POS.#. Seg. ID Segment Name Req. Des. Max Use Loop Repeat

Loop ID – PO1 100000

010 PO1 Baseline Item Data M 1

Loop ID - CTP >1

040 CTP Pricing Information O 1
043 CUR Currency O 1

Loop ID - PID 1000

050 PID Product/Item Description O 1

Loop ID – SCH 200

295 SCH Line Item Schedule O 1

Summary
POS.#. Seg. ID Segment Name Req. Des. Max Use Loop Repeat

020 SE Transaction Set Trailer M 1

850-004010 Page 12 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

16. Business Data Matrix

Element Element
Name Qualifier Data Element Type Min/Max
Buyer Name PER01 = BD PER02 AN 1/60
Buyer Telephone PER03 = TE PER04 AN 1/80
Delivery Date Requested SCH05 = 002 SCH06 DT 8/8
Engineering Change Level PO108 = EC PO109 AN 1/48
Item Description PID01 = F PID05 AN 1/80
Part Number PO106 – PN PO107 AN 1/48
Purchase Order Create Date BEG05 DT 8/8
Purchase Order Line Number PO101 AN 1/20
Purchase Order Number BEG02 = KN BEG03 AN 1/22
Purchase Order Revision Date DTM01 = 167 DTM02 DT 8/8
Quantity Ordered PO102 R 1/15
Quantity Ordered SCH01 R 1/15
Quantity Ordered CTP04 R 1/15
Payment Terms ITD01 = 01 ITD12 AN 1/80
Price; Currency CUR01 = BY CUR02 ID 2/2
Price; Extended CTP08 R 1/18
Price; Unit PO105 = QT PO104 R 1/17
Price, Unit CTP02 = QT CTP03 R 1/17
Ship To City N101 = ST N401 AN 2/30
Ship To Country Code N101 = ST N404 ID 2/3
Ship To Name N101 = ST N102 AN 1/60
Ship To Plant ID (DUNS) N101 = ST N104 AN 2/80
Ship To Postal Code N101 = ST N403 ID 3/15
Ship To State/Province N101 = ST N402 ID 2/2
Ship To Street Address N101 = ST N301 AN 1/55
Shipping Method of Payment FOB03 AN 1/80
Supplier ID N101 = SU N104 AN 2/80
Supplier Name N101 = SU N102 AN 1/60
Unit of Measure Code SCH02 ID 2/2
Unit of Measure Code PO103 ID 2/2
Unit of Measure Code CTP05 ID 2/2

850-004010 Page 13 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: ST Transaction Set Header

Level: Header
Loop:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number.
Syntax:
Semantic:
Comments:
Notes: The Transaction Set Control Number (ST02) in this header, must
match the Transaction Set Control Number (SE02) in the Transaction Set
Trailer segment (SE).

Data Element Summary

Ref. Data
Des. Element Name Attributes
ST01 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set.

850 – Purchase Order

ST02 329 Transaction Set Control Number M AN 4/9

Identifying control number that must be unique within a
transaction set Functional Group assigned by the
originator for a Transaction Set.

Example: ST*850*993300001~

850-004010 Page 14 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: BEG Beginning Segment for Purchase Order

Level: Header
Loop:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of the purchase Order transaction set and
transmit identifying numbers and dates.
Syntax:
Semantic: 1. BEG05 is the date assigned by the purchaser to the purchase order.
Comments:
Notes: Defines forecast as delivery-based, discrete quantities. Defines
Blanket PO start and end dates, PO number, and date forecast was
generated. BEG06 through BEG12 are not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
BEG01 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of Tr ansaction Set.

05 - Replace

BEG02 92 Purchase Order Type Code M ID 2/2

Code specifying the type of purchase order.

KN – Purchase Order

BEG03 324 Purchase Order Number M AN 1/22

Identifying number for purchase order assigned by
orderer/purchaser.

Victor Reinz Purchase Order Number

BEG04 328 Release Number O AN 1/30

Number identifying a release against a purchase order
previously placed by the parties involved in the
transaction.

Not used by Victor Reinz Division

BEG05 373 Date M DT 8/8

Date expressed as CCYYMMDD.

Date purchase order was originally issued or

re-issued.

BEG06 through BEG12 are not used.

Example: BEG*05*KN*TR5692**20021010~

850-004010 Page 15 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: FOB F.O.B Related Instructions

Level: Header
Loop:
Usage: Optional
Max Use: >1
Purpose: To specify transportation instructions relating to the shipment.
Syntax: 1. C0302 – If FOB03 is present, then FOB02 is required.
2. C0405 – If FOB04 is present, then FOB05 is required.
3. C0706 – If FOB05 is present, then FOB06 is required.
4. C0809 – If FOB08 is present, then FOB09 is required.
Semantic: 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:
Notes: Defines transportation cost responsibility. BEG06 through BEG12
are not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
FOB01 146 Shipment Method of Payment M ID 2/2
Code identifying payment terms for transportation
charges.

DE – Per Contract

FOB02 309 Location Qualifier C ID 1/2

Code identifying type of location.

DE – Destination (Shipping)

FOB03 352 Description O AN 1/80

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

Description of freight terms

FOB04 through FOB09 not used by Victor

Reinz

Example: FOB*DE*DE*DEST NO CHARGE~

850-004010 Page 16 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: ITD Terms of sale/Deferred Terms of Sale

Level: Header
Loop:
Usage: Optional
Max Use: >1
Purpose: To specify terms of sale.
Syntax: 1. L03040513 – If ITD03 is present, then at least one ITD04, ITD05 or
ITD13 is required.
2. L08040513 – If ITD08 is present, then at least one ITD04, ITD05 or
ITD13 is required.
3. L091011 – If ITD09 is present, then at least one ITD10 or ITD11 is
required.
Semantic: ITD15 is the percentage applied to a base amount used to determine a late
payment charge,
Comments: If the code in ITD04 is “04”, then ITD04 or ITD09 is required and either
ITD10 or ITD11 is required; if the code in ITD01 is “05” then ITD06 or
ITD07 is required.
Notes: Defines Purchase Order payment terms. ITD02 through ITD11 are not
used. ITD13 through ITD15 are not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
ITD01 336 Terms Type Code O ID 2/2
Code identifying type of payment terms.

01 – Basic

ITD02 through ITD11 not used.

ITD12 373 Description O AN 1/80

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

Free-form payment terms.

ITD13 through ITD15 not used by Victor

Reinz

Example: ITD*01***********NET 30~

850-004010 Page 17 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: DTM Date/Time Reference

Level: Header
Loop:
Usage: Optional
Max Use: 10
Purpose: To specify pertinent dates and times.
Syntax: 1. R020305 – At least one DTM02, DTM03 or DTM05 is required.
2. C0404 – If DTM04 is present, then DTM03 is required.
3. PO506 – If either DTM05 or DTM05 are present, then the other
is required.
Semantic:
Comments:
Notes: Defines Purchase Order revision date. DTM03 through DTM06
are not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date
and time

167 – Most Recent Revision (or Initial Version)

DTM02 373 Date C DT 8/8

Date expressed as CCYYMMDD.

DTM03 through DTM06 not used by Victor

Reinz

Example: DTM*167*20021011~

850-004010 Page 18 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: N1 Name
Level: Header
Loop: N1
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code.
Syntax: 1. R0203 -- At least one of N102 or N103 is required.
2. P0304 -- If either N103 or N104 are present, then the others
are required.
Semantic:
Comments: 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.

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

Notes: Defines Supplier/Shipper and Dana Corporation receiving facility or

joint venture. N105 and N106 are not used. One N1*SU loop and
one N1*ST loop will be used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
N101 98 Entity Identifier Code M ID 2/3
Code identifying an organizational entity, a physical
location, property or an individual.

ST = Ship To

SU = Supplier

N102 93 Name X AN 1/60

Free-form name.

Name of Supplier or name or Victor Reinz plant.

N103 66 Identification Code Qualifier X ID 1/2

When N101 = ST use code 1 for Dun & Bradstreet

Number.

When N101 = SU use code 92 for Assigned by

Buyer or Buyer's Agent.

850-004010 Page 19 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Ref. Data
Des. Element Name Attributes
N104 67 Identification Code X AN 2/80
Code identifying a party or other code.

When N101 = ST use the following DUNS #'s:

Avilla, IN 878833979
Chatham, ON 249186818
Danville, KY 188962112
Lisle, IL 096799101
Milwaukee, WI 848532529
Robinson, IL 047074661

Note: joint venture Ship To’s will not have a DUNS

number.

When N101 = SU use Victor Reinz facility-

assigned Supplier ID.

N105 and N106 are not used.

Example: N1*SU*GENERIC METALS*92*633~

N1*ST*VICTOR REINZ, AVILLA PLANT*1*878833979~

850-004010 Page 20 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: N3 Address Information

Level: Header
Loop: N1
Usage: Optional
Max Use: 2
Purpose: To specify the location of the named party.
Syntax:
Semantic:
Comments:

Notes: Defines address, city, state/province and postal code of receiving

facility or joint venture. One N3 within the N1 Ship To loop will
be used. N302 is not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
N301 93 Address Information M AN 1/55
Address information.

Street Address

N302 is not used.

Example: N3*301 PROGRESS WAY~

850-004010 Page 21 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: N4 – Geographic Location

Level: Header
Loop: N1
Usage: Optional
Max Use: >1
Purpose: To specify the geographic place of the named party.
Syntax: 1. C0605 – If N406 is present, then N405 is required.
Semantic:
Comments: A combination of either N401 through N404 or N405 and N406 may be
adequate to specify a location.

N402 is required only if city name (N401) is in the U.S. or Canada.

Notes: Defines city, state/province, postal code and country of receiving

facility or joint venture. One N4 within the N1 Ship To loop will
be used. N405 and N406 are not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
N401 19 City Name O AN 2/30
Free form text for city name.

City Name

N402 156 State or Province Code O ID 2/2

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

IL = Illinois IN = Indiana
KY = Kentucky ON = Ontario
WI = Wisconsin

N403 116 Postal Code O ID 3/15

Code defining international postal zone code excluding
punctuation and blanks (zip code for United States).

United States Zip Code or Canadian Postal Code

N404 26 Country Code O ID 2/3

Code identifying the country.

CA = Canada
US = United States of America

N405 and N406 are not used.

Example: N4*AVILLA*IN*46710*US~

850-004010 Page 22 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: PER Administrative Communications Contact

Level: Header
Loop: N1
Usage: Optional
Max Use: >1
Purpose: To identify a person or office to whom administrative communications
should be directed.
Syntax: 1. P0304 – If either PER03 or PER04 are present, then the others
are required.
2. P0506 -- If either PER05 or PER06 are present, then the others
are required.
2. P0708 -- If either PER07 or PER08 are present, then the others
are required
Semantic:
Comments:

Notes: Defines buyer name and telephone number at Victor Reinz ordering
facility. PER05 through PER09 are not used. One PER within the
NI Ship To loop will be used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
PER01 366 Contact Function Code M ID 2/2
Code identifying the major duty or responsibility of
the person or group named.

BD = Buyer Name or Department

PER02 93 Name O AN 1/60

Free-form name.

Buyer’s name

PER03 365 Communication Number Qualifier C ID 2/2

Code identifying the type of communication
number

TE = Telephone Number

PER04 93 Communication Number C AN 1/80

Complete communications number including country or
area code when applicable.

Buyer’s telephone number

Example: PER*BD*TOM MILLS*TE*630/271-4990~

850-004010 Page 23 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: PO1 Baseline Item Data

Level: Detail
Loop: PO1
Usage: Mandatory
Max Use: 1
Purpose: To specify basic and most frequently used line item data.
Syntax: 1. C0302 – If PO103 is present, then PO102 is required.
2. C0504 – If PO105 is present, then PO104 is required.
3. P0607 – If either PO106 or PO107 are present, then the other is required.
4. P0809 – If either PO108 or PO109 are present, then the other is required.
5. P1011 – If either PO110 or PO111 are present, then the other is required.
6. P1213 – If either PO112 or PO113 are present, then the other is required.
7. P1415 – If either PO114 or PO115 are present, then the other is required.
8. P1617 – If either PO116 or PO117 are present, then the other is required.
9. P1819 – If either PO118 or PO119 are present, then the other is required.
10. P2021 – If either PO120 or PO121 are present, then the other is required.
11. P2223 – If either PO122 or PO123 are present, then the other is required.
12. P2425 – If either PO124 or PO125 are present, then the other is required.
Semantic:
Comments: See the Data Element Dictionary for a complete list of ID’s

PO101 is the line item identification

PO106 through PO125 provide for ten different product/service ID’s

per each item

Notes: Defines PO Line number, part, quantity, unit price, unit of measure
and, optionally, engineering change level for part being ordered.
PO110 through PO125 are not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
PO101 350 Assigned Identification O AN 1/20
Alphanumeric characters assigned for differentiation
within a transaction set..

Line number with the purchase order. Starts at 1

and increments by 1 for each line item within the
purchase order

850-004010 Page 24 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Ref. Data
Des. Element Name Attributes
PO102 330 Quantity Ordered C R 1/15
Quantity Ordered.

Total quantity ordered. If multiple SCH segments

Are used to define multiple shipments, the sum of
Individual shipment quantities in SCH01 will
equal the total quantity in PO102

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

Codes used by Victor Reinz Division::

AF = Centigram LB = Pound
BR = Barrel LT = Liter
BI = Bar LO = Lot
BO = Bottle ME = Milligram
BX = Box ML = Milliliter
C3 = Centiliter MM = Millimeter
CA = Case MR = Meter
CC = Cubic Centimeter OZ = Ounce
CF = Cubic Feet PR = Pair
CI = Cubic Inch PT = Pint
CM = Centimeter QT = Quart
CN = Can RL = Roll
DR = Drum RM = Ream
DZ = Dozen SF = Square Foot
EA = Each SH = Sheet
FT = Foot SI = Square Inch
GA = Gallon SO = Spool
GR = Gram ST = Set
GS = Gross TN = Net Ton (2,000 lb.)
HR = Hour TH - Thousand
HU = Hundred U3 = 10
IN = Inch UM = Million of Units
JR = Jar UN = Unit
K6 = Kiloliter UQ = Wafer
KG = Kilogram Y4 = Tub

PO104 212 Unit Price C R 1/17

Price per unit of product, service, commodity, etc.

Unit price quoted to Victor Reinz Division.

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

Code identifying the type of unit price for an item

QT = Quoted

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

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

PN = Part Number

850-004010 Page 25 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Ref. Data
Des. Element Name Attributes
PO107 234 Product/Service ID M AN 1/48
Identifying number for a product or service.

Victor Reinz or supplier’s part number.

PO108 235 Product/Service ID X ID 2/2

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

EC = Engineering Change Level.

Optionally used by Victor Reinz Division if

PO109 is used

PO109 234 Product/Service ID X AN 1/48

Identifying number for a product or service.

Victor Reinz Engineering Change Level provided

in releasing documents (e.g., 830, 850 or 862).

Optionally used by Victor Reinz Division

PO110 through PO125 are not used.

Example: PO1*1*1200*EA*1.50*QT*PN*R4571M*EC*00A~

850-004010 Page 26 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: CTP Pricing Information

Level: Detail
Loop: CTP
Usage: Optional
Max Use: 1
Purpose: To specify pricing information.
Syntax: 1. P0405 – If either CTP04 or CTP05 are present, then the other
is required.
2. C0607 – If CTP06 is present, then CTP07 is required.
3. C0902 – If CTP09 is present, then CTP02 is required.
is required.
4. C1002 – If CTP10 is present, then CTP02 is required.
5. C1103 – If CTP10 is present, then CTP03 is required.
Semantic: 1. CTP07 is a multiplier factor to arrive at a final discounted price.
A multiplier of .90would be the factor if a 10% discount is given.
2. CTP08 is the rebate amount.
Comments:
Notes: Defines unit and extended price. CTP01, CTP06, CTP07, CTP09
through CTP11 not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
CTP01 687 Class of Trade Code O ID 2/2
Code indicating class of trade.

Not used by Victor Reinz Division.

CTP02 236 Price Identifier Code C ID 2/3

Code identifying pricing specification

QTE = Quote price

CTP03 212 Unit Price C R 1/17

Price per unit of product, service, commodity, etc.

Unit price

CTP04 380 Quantity C R 1/15

Numeric value of quantity

Quantity ordered

850-004010 Page 27 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Ref. Data
Des. Element Name Attributes
CTP05 C001:355 Unit or Basis of Measurement Code M ID 2/2
Code specifying the units in which a value is
being expressed, or manner in which a
measurement has been taken.

Codes used by Victor Reinz Division::

AF = Centigram LB = Pound
BR = Barrel LT = Liter
BI = Bar LO = Lot
BO = Bottle ME = Milligram
BX = Box ML = Milliliter
C3 = Centiliter MM = Millimeter
CA = Case MR = Meter
CC = Cubic Centimeter OZ = Ounce
CF = Cubic Feet PR = Pair
CI = Cubic Inch PT = Pint
CM = Centimeter QT = Quart
CN = Can RL = Roll
DR = Drum RM = Ream
DZ = Dozen SF = Square Foot
EA = Each SH = Sheet
FT = Foot SI = Square Inch
GA = Gallon SO = Spool
GR = Gram ST = Set
GS = Gross TN = Net Ton (2,000 lb.)
HR = Hour TH - Thousand
HU = Hundred U3 = 10
IN = Inch UM = Million of Units
JR = Jar UN = Unit
K6 = Kiloliter UQ = Wafer
KG = Kilogram Y4 = Tub

CTP06 and CTP07 not used by Victor Reinz

Division

CTP08 782 Monetary Price 0 R 1/18

Monetary amount.

Extended price

CTP09 through CTP11 not used by Victor Reinz

Division

Example: CTP**QTE*1.50*1200*EA***1800~

850-004010 Page 28 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: CUR Currency

Level: Detail
Loop: CTP
Usage: Optional
Max Use: 1
Purpose: To specify the currency used in a transaction.
Syntax: 1. C0807 -- If CUR08 is present, then CUR07 is required.
2. C0907 – If CUR09 is present, then CUR07 is required.
3. L101112 – If CUR10 is present, the at least one of CUR11 or CUR12 is required.
4. C1110 – If CUR11 is present, then CUR10 is required.
5. C1210 – If CUR12 is present, then CUR10 is required.
6. L131415 – If CUR13 is present, then at least one CUR14 or CUR15 is required.
7. C1413 – If CUR14 is present, then CUR13 is required.
8. C1513 – If CUR15 is present, then CUR13 is required.
9. L161718 – If CUR16 is present, then at least one CUR17 or CUR18 is required.
10. C1716 – If CUR17 is present, then CUR16 is required.
11 C1816 -- If CUR18 is present, then CUR16 is required.
12 L192021 – If CUR19 is present, then at least one CUR20 or CUR21 is required.
13 C2019 – If CUR20 is present, then CUR19 is required.
14 C2119 – If CUR21 is present, then CUR19 is required.
Semantic:
Comments:

Notes: Used to define the buyer’s currency used in the unit price data
element; PO104 in the preceding PO1 segment. CUR03 through
CUR21 not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
CUR01 98 Entity Identifier Code M ID 2/3
Code identifying an organizational entity, a physical
location, property or an individual.

BY = Buying Party (Purchaser)

CUR02 100 Currency Code M ID 3/3

Code (Standard ISO) for country in whose currency the
charges are being specified.

CND = Canadian Dollars

USD = United States Dollars

Example: CUR*BY*USD~

850-004010 Page 29 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: PID Product/Item Description

Level: Detail
Loop: PID Repeat: 1000
Usage: Optional
Max Use: 1
Purpose: To describe a product or process in coded or free-form format.
Syntax: 1. C0304 -- If PID04 is present, then PID03 is required.
2. R0405 – At least one of PID04 or PID05 is required.
3. C0703 – If PID07 is present, then PID03 is required.
4. C0804 – If PID08 is present, then PID04 is required.
5. C0905 – If PID09 is present, then PID05 is required.
Semantic: Use PID03 to indicate the organization that publishes the code list being
referred to.

PID04 should be used for industry-specific product description codes.

PID08 describes the physical characteristics of the product identified in

PID04. A ‘Y’ indicates that the specified attribute applies to this item ; an
‘N’ indicates it does not apply. Any other value is indeterminate.

PID09 is used to identify the language being used in PID05

Comments: If PID01 equals ‘F’, then PID05 is used. If PID01 equals ‘S’ then PID04 is
used. If PID01 equals ‘X’, then both PID04 and PID05 are used.

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

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

Notes: Used optionally to further describe the part being ordered in the
preceding PO1 segment. PID02, PID03, PID04 and PID06 through
PID09 not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
PID01 349 Item Description Type M ID 1/1
Code indicating the format of a description.

F = Free Form

PID02 750 Product/Process Characteristic Code O ID 2/3

Code identifying the general class of a product or process
characteristic.

Not used by Victor Reinz Division

850-004010 Page 30 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Ref. Data
Des. Element Name Attributes
PID03 559 Agency Qualifier Code C ID 2/2
Code Identifying the agency assigning the code values.

Not used by Victor Reinz Division

PID04 751 Product Description Code C AN 1/12

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

Not used by Victor Reinz Division

PID05 352 Description C AN 1/80

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

Optionally used by Victor Reinz Division

PID06 through PID09 are not used.

Example: PID*F****SILICONE COATED RUBBER WASHER~

850-004010 Page 31 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: SCH Line Item Schedule

Level: Detail
Loop: SCH
Usage: Optional
Max Use: 1
Purpose: To specify the data for scheduling a specific line item.
Syntax: 1. C0304 – If SCH03 is present, then SCH04 is required.
2. L080910 – If SCH08 is present, then at least one of SCH09 or
SCH10 is required.
3. C0908 – If SCH09 is present, then SCH08 is required.
4. C1008 – If SCH10 is present, then SCH10 is required
Semantic: SCH12 is the schedule identification.
Comments: SCH05 specifies the interpretation to be used for SCH06 and SCH07.

Notes: Used to describe quantity ordered with a requested delivery date.

SCH03, SCH04 and SCH07 through SCH12 not used.

Data Element Summary

Ref. Data
Des. Element Name Attributes
SCH01 380 Quantity M R 1/15
Numeric value of quantity.

Quantity of part being ordered for this due date

SCH02 355 Unit or Basis of Measurement Code M ID 2/2

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

Codes used by Victor Reinz Division::

AF = Centigram LB = Pound
BR = Barrel LT = Liter
BI = Bar LO = Lot
BO = Bottle ME = Milligram
BX = Box ML = Milliliter
C3 = Centiliter MM = Millimeter
CA = Case MR = Meter
CC = Cubic Centimeter OZ = Ounce
CF = Cubic Feet PR = Pair
CI = Cubic Inch PT = Pint
CM = Centimeter QT = Quart
CN = Can RL = Roll
DR = Drum RM = Ream
DZ = Dozen SF = Square Foot
EA = Each SH = Sheet
FT = Foot SI = Square Inch
GA = Gallon SO = Spool
GR = Gram ST = Set
GS = Gross TN = Net Ton (2,000 lb.)
HR = Hour TH - Thousand
HU = Hundred U3 = 10
IN = Inch UM = Million of Units
JR = Jar UN = Unit
K6 = Kiloliter UQ = Wafer
KG = Kilogram Y4 = Tub

850-004010 Page 32 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Ref. Data
Des. Element Name Attributes
SCH03 98 Entity Identifier Code O ID 2/3

Not used by Victor Reinz Division

SCH04 93 Name C AN 1/60

Code specifying interval grouping of the forecast.

Not used by Victor Reinz Division

SCH05 374 Date/Time Qualifier M ID 3/3

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

002 = Delivery Requested

SCH06 373 Date M DT 8/8

Date expressed as CCYYMMDD

Requested delivery date.

SCH07 through SCH12 not used by Victor Reinz

Division.

Example: SCH*1200*EA***002*20021031~

850-004010 Page 33 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

Segment: SE Transaction Set Trailer

Level: Summary
Loop:
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the
transmitted segments (including the beginning (ST) and ending (SE)
segments).
Syntax:
Semantic:
Comments: SE is the last segment of each transaction set.

Notes: The Transaction Set Control Number value in this trailer must match
the same element value in the Transaction Set Header (ST02).

Data Element Summary

Ref. Data
Des. Element Name Attributes
SE01 96 Number of Included Segments M N0 1/10
Total number of segments included in a
transaction set including ST and SE segments.

SE02 329 Transaction Set Control Number M AN 4/9

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

Example: SE*19*993300001~

850-004010 Page 34 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

EXAMPLE 1
Order for a single part

ST*850*993300001~ Start Transaction Set 850 with control number 993300001.

BEG*05*KN*TR5692**20021010~ This is purchase order TR5692 generated on 10/10/02 and
replaces all prior purchase orders with the same PO ID.
FOB*DE*DE*DEST NO CHARGE~ There are to be no shipping charges paid by the Destination per
the terms of this contract.
ITD*01***********NET 30~ Payment terms are Net 30 days.
DTM*167*20021011~ Purchase Order was last revised on 10/11/02.
N1*SU*GENERIC METALS*92*633~ Supplier is Generic Metals and their Victor Reinz Avilla
Plant supplier ID is 633.
N1*ST*VICTOR REINZ. AVILLA PLANT*1*878833979~ Ship To is the Avilla plant of Victor Reinz and that facility’s
DUNS number is 878833979.
N3*301 PROGRESS WAY~ Ship to street address is 301 Progress Way
N4*AVILLA*IN*46710*US~ Ship to city is Avilla, Indiana. The zip code is 46710 and
it is located in the United States
PER*BD*TOM MILLS*TE*630/271-4990~ Buyer’s name is Tom Mills and his phone number
is 630/271-4990
PO1*1*1200*EA*1.50*QT*PN*R4571M*EC*00A~ Being ordered are 1,200 pieces of part R4571M which has
an engineering change level of 00A. The quoted unit price
is $1.50
CTP**QTE*1.50*1200*EA***1800~ Quoted price is $1.50 each and the extended price for 1,200
ordered, is $1,800
CUR*BY*US~ Buyer’s currency for the pricing is United States dollars
PID*F****SILICONE COATED RUBBER WASHER~ Item description is a ‘Silicone Coated Rubber Washer’
SCH*1200*EA***002*20021031~ The requested delivery for (all) 1,200 pieces is 11/31/02.
SE*16*993300001~ End Transaction Set control number 993300001 which
contained 16 segments

850-004010 Page 35 of 36 Effective: 10/15/02

850 Implementation Guide Victor Reinz Division

EXAMPLE 2
Orders for multiple parts

ST*850*993300001~ Start Transaction Set 850 with control number 993300001.

BEG*05*KN*TR5692**20021010~ This is purchase order TR5692 generated on 10/10/02 and
replaces all prior purchase orders with the same PO ID.
FOB*DE*DE*DEST NO CHARGE~ There are to be no shipping charges paid by the Destination per
the terms of this contract.
ITD*01***********NET 30~ Payment terms are Net 30 days.
DTM*167*20021011~ Purchase Order was last revised on 10/11/02.
N1*SU*GENERIC METALS*92*633~ Supplier is Generic Metals and their Victor Reinz Avilla
Plant supplier ID is 633.
N1*ST*VICTOR REINZ. AVILLA PLANT*1*878833979~ Ship To is the Avilla plant of Victor Reinz and that facility’s
DUNS number is 878833979.
N3*301 PROGRESS WAY~ Ship to street address is 301 Progress Way
N4*AVILLA*IN*46710*US~ Ship to city is Avilla, Indiana. The zip code is 46710 and
it is located in the United States
PER*BD*TOM MILLS*TE*630/271-4990 Buyer’s name is Tom Mills and his phone number
is 630/271-4990
PO1*1*1200*EA*1.50*QT*PN*R4571M*EC*00A~ Being ordered are 1,200 pieces of part R4571M which has
an engineering change level of 00A. The quoted unit price
is $1.50
CTP**QTE*1.50*1200*EA***1800~ Quoted price is $1.50 each and the extended price for 1,200
ordered, is $1,800
CUR*BY*US~ Buyer’s currency for the pricing is United States dollars
PID*F****SILICONE COATED RUBBER WASHER~ Item description is a ‘Silicone Coated Rubber Washer’
SCH*1200*EA***002*20021031~ The requested delivery for (all) 1,200 pieces is 1-/31/02.
PO1*2*500*EA*.60*QT*PN*LA66T*~ Being ordered are 500 pieces of part LA66T which has
no engineering change level.. The quoted unit price
is $.60
CTP**QTE*.60*500*EA***300~ Quoted price is $.60 each and the extended price for 500
ordered, is $300.
CUR*BY*US~ Buyer’s currency for the pricing is United States dollars
PID*F****FLAT BRASS WASHER~ Item description is a ‘Brass Flat Washer’
SCH*500*EA***002*20021111~ The requested delivery for (all) 500 pieces is 11/11/02.
SE*21*993300001~ End Transaction Set control number 993300001 which
contained 21 segments

850-004010 Page 36 of 36 Effective: 10/15/02