Helzberg Diamonds
/
Purchase Order Change Request - Buyer Initiated
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Helzberg Diamonds. Contact Helzberg Diamonds for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Helzberg Diamonds logo

X12 860 Purchase Order Change Request - Buyer Initiated

X12 Release 4030

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Change Request - Buyer Initiated Transaction Set (860) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide the information required for the customary and established business and industry practice relative to a purchase order change. This transaction can be used: (1) by a buyer to request a change to a previously submitted purchase order or (2) by a buyer to confirm acceptance of a purchase order change initiated by the seller or by mutual agreement of the two parties.

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/helzberg-diamonds/purchase-order-change-request-buyer-initiated/01HC2F92AEHHG0PVPT1PPM17HZ
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
0100
Transaction Set Header
Max use 1
Required
BCH
0200
Beginning Segment for Purchase Order Change
Max use 1
Required
REF
0500
Customer Order Number
Max use 1
Optional
REF
0500
Internal Customer Number
Max use 1
Optional
REF
0500
Internal Vendor Number
Max use 1
Optional
PER
0600
Administrative Communications Contact
Max use 3
Optional
CSH
1100
Sales Requirements
Max use 5
Optional
SAC Loop
ITD
1300
Terms of Sale/Deferred Terms of Sale
Max use 5
Optional
DTM
1500
Cancel After
Max use 1
Optional
DTM
1500
Delivery Requested
Max use 1
Optional
CTB
2670
Restrictions/Conditions
Max use 1
Optional
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code identifying the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Code indicating the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

^
Repetition Separator
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

Code specifying the version number of the interchange control segments

00403
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code indicating sender's request for an interchange acknowledgment

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code indicating whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

PC
Purchase Order Change Request - Buyer Initiated (860)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission; codes agreed to by trading partners

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004030
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999

Heading

ST
0100
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
860
Purchase Order Change Request - Buyer Initiated
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

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

BCH
0200
Heading > BCH

Beginning Segment for Purchase Order Change

RequiredMax use 1

To indicate the beginning of the Purchase Order Change Transaction Set and transmit identifying numbers and dates

Usage notes

Every Purchase Order Change Request - Buyer Initiated (EDI 860) must be acknowledged with a Purchase Order Change Acknowledgment/Request - Seller Initiated (EDI 865) to complete the legal commitment of fulfillment. No changes are allowed on the Purchase Order Change Acknowledgment/Request - Seller Initiated (EDI 865).

"Consigned Orders" are for initial or replenishment of memo inventory orders (BEG02 - CO). A memo contract number will be supplied if available (BEG06).

"Rush Orders" are used to indicate that the order should be expedited (BEG02 -RO).

"Stand Alone Orders" are used for normal asset inventory replenishment (BEG02 - SA).

"Special Orders" are used for orders that have specific requirements or specifications (BEG02 - SO). The requirements or specifications will be provided in the MTX Segment in the N9 detail loop.

Example
BCH-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

01
Cancellation
04
Change
BCH-02
92
Purchase Order Type Code
Required
Identifier (ID)

Code specifying the type of Purchase Order

CO
Catalog Order

Consigned Order

OS
Special Order
RO
Rush Order
SA
Stand-alone Order
BCH-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Retailer's original purchase order number.

BCH-05
327
Change Order Sequence Number
Optional
String (AN)
Min 1Max 8

Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set

Usage notes

Retailer's sequence number for the purchase order changes. The highest
number is the latest version.

BCH-06
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

  • BCH06 is the date assigned by the purchaser to purchase order.
Usage notes

Retailer's original purchase order date.

BCH-08
367
Contract Number
Optional
String (AN)
Min 1Max 30

Contract number

Usage notes

This is used with consigned orders (BEG02 - CO).

REF
0500
Heading > REF

Customer Order Number

OptionalMax use 1

To specify identifying information

Usage notes

The Retailer-assigned customer number (REF01 - IT) and Retailer assigned customer order number (REF01 - CO) are only present on Special Orders (BEG02 - SO).

Example
Variants (all may be used)
REFInternal Customer NumberREFInternal Vendor Number
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

CO
Customer Order Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

This is the Retailer-assigned supplier number (REF01 - IA); or the customer number (REF01 - IT); or customer order number (REF01 - CO).

REF
0500
Heading > REF

Internal Customer Number

OptionalMax use 1

To specify identifying information

Usage notes

The Retailer-assigned customer number (REF01 - IT) and Retailer assigned customer order number (REF01 - CO) are only present on Special Orders (BEG02 - SO).

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

IT
Internal Customer Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

This is the Retailer-assigned supplier number (REF01 - IA); or the customer number (REF01 - IT); or customer order number (REF01 - CO).

REF
0500
Heading > REF

Internal Vendor Number

OptionalMax use 1

To specify identifying information

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

IA
Internal Vendor Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 50

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

This is the Retailer-assigned supplier number (REF01 - IA); or the customer number (REF01 - IT); or customer order number (REF01 - CO).

PER
0600
Heading > PER

Administrative Communications Contact

OptionalMax use 3

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

Example
If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
PER-01
366
Contact Function Code
Required
Identifier (ID)

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

BD
Buyer Name or Department
PER-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

This is the name of the retailer contact for the purchase order.

PER-03
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

WP
Work Phone Number
PER-04
364
Communication Number
Optional
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

Usage notes

This is the office telephone number for the retailer contact.

PER-05
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

EM
Electronic Mail
PER-06
364
Communication Number
Optional
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

Usage notes

This is the Email address for the retailer contact.

CSH
1100
Heading > CSH

Sales Requirements

OptionalMax use 5

To specify general conditions or requirements of the sale

Example
CSH-01
563
Sales Requirement Code
Optional
Identifier (ID)

Code to identify a specific requirement or agreement of sale

N
No Back Order
P4
Do Not Preship
SC
Ship Complete
SAC Loop
OptionalMax >1
SAC
1200
Heading > SAC Loop > SAC

Service, Promotion, Allowance, or Charge Information

RequiredMax use 1

To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

Usage notes

This segment will only be used if an allowance is to be applied to this purchase order. This is for supplier information only, as the retailer will deduct this amount from the invoice associated to the purchase order.

Example
If either Allowance/Charge Percent Qualifier (SAC-06) or Percent (SAC-07) is present, then the other is required
SAC-01
248
Allowance or Charge Indicator
Required
Identifier (ID)

Code which indicates an allowance or charge for the service specified

  • If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.
A
Allowance
SAC-02
1300
Service, Promotion, Allowance, or Charge Code
Required
Identifier (ID)

Code identifying the service, promotion, allowance, or charge

A260
Advertising Allowance
SAC-06
378
Allowance/Charge Percent Qualifier
Optional
Identifier (ID)

Code indicating on what basis allowance or charge percent is calculated

2
Item Net Cost
SAC-07
332
Percent
Optional
Decimal number (R)
Min 1Max 6

Percent expressed as a percent

Usage notes

The percent is sent with a decimal point, e.g., 9.25% is sent as "9.25", and
5% is sent as "5.0".

SAC Loop end
ITD
1300
Heading > ITD

Terms of Sale/Deferred Terms of Sale

OptionalMax use 5

To specify terms of sale

Usage notes

This segment is used to specify the terms associated with the purchase order and will only be used in the header area.

Example
ITD-01
336
Terms Type Code
Optional
Identifier (ID)

Code identifying type of payment terms

  • If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
14
Previously agreed upon
ITD-03
338
Terms Discount Percent
Optional
Decimal number (R)
Min 1Max 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

Usage notes

The percent is sent with a decimal point only when needed, e.g., 9.25% is
sent as "9.25", and 5% is sent as "5".

ITD-05
351
Terms Discount Days Due
Optional
Numeric (N0)
Min 1Max 3

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

ITD-07
386
Terms Net Days
Optional
Numeric (N0)
Min 1Max 3

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

ITD-12
352
Description
Optional
String (AN)
Min 1Max 80

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

DTM
1500
Heading > DTM

Cancel After

OptionalMax use 1

To specify pertinent dates and times

Usage notes

This segment is used to specify order processing dates.

Example
Variants (all may be used)
DTMDelivery Requested
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

001
Cancel After
DTM-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

DTM
1500
Heading > DTM

Delivery Requested

OptionalMax use 1

To specify pertinent dates and times

Usage notes

This segment is used to specify order processing dates.

Example
Variants (all may be used)
DTMCancel After
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

002
Delivery Requested
DTM-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

CTB
2670
Heading > CTB

Restrictions/Conditions

OptionalMax use >1

To specify restrictions/conditions (such as shipping, ordering)

Usage notes

This segment is used to specify shipping instructions such as "Next Day", "2 Day", etc.

Example
CTB-01
688
Restrictions/Conditions Qualifier
Required
Identifier (ID)

Code identifying the type of restriction/condition

SR
Shipping
CTB-02
352
Description
Optional
String (AN)
Min 1Max 80

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

N1 Bill-to-Party
OptionalMax 1
Variants (all may be used)
Ship To
N1
3000
Heading > Bill-to-Party > N1

Name

RequiredMax use 1

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

Usage notes

Two loops will be generated for each Purchase Order; one for the bill to party and one for the ship to party.

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

BT
Bill-to-Party
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

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

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • 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.
Usage notes

This is the location code as defined by N103. The location refers to a store, warehouse, or customer. Location codes are used to alleviate the need to send complete names and addresses.

Location number (N101 = BT, ST) or Retail Customer number (N101 = ST).

N3
3200
Heading > Bill-to-Party > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
3300
Heading > Bill-to-Party > N4

Geographic Location

OptionalMax use >1

To specify the geographic place of the named party

Usage notes

This segment is used to identify the Ship To (N101 = ST) geographic location.

Example
N4-01
19
City Name
Optional
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

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

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Optional
Identifier (ID)
Min 3Max 15

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

N4-04
26
Country Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the country

Usage notes

ISO Numeric country code is required if not USA.

N1 Bill-to-Party end
N1 Ship To
OptionalMax 1
Variants (all may be used)
Bill-to-Party
N1
3000
Heading > Ship To > N1

Name

RequiredMax use 1

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

Usage notes

Two loops will be generated for each Purchase Order; one for the bill to party and one for the ship to party.

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

ST
Ship To
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

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

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • 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.
Usage notes

This is the location code as defined by N103. The location refers to a store, warehouse, or customer. Location codes are used to alleviate the need to send complete names and addresses.

Location number (N101 = BT, ST) or Retail Customer number (N101 = ST).

N3
3200
Heading > Ship To > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
3300
Heading > Ship To > N4

Geographic Location

OptionalMax use >1

To specify the geographic place of the named party

Usage notes

This segment is used to identify the Ship To (N101 = ST) geographic location.

Example
N4-01
19
City Name
Optional
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

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

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Optional
Identifier (ID)
Min 3Max 15

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

N4-04
26
Country Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the country

Usage notes

ISO Numeric country code is required if not USA.

N1 Ship To end
Heading end

Detail

POC Loop
OptionalMax >1
POC
0100
Detail > POC Loop > POC

Line Item Change

RequiredMax use 1

To specify changes to a line item

Example
If Basis of Unit Price Code (POC-07) is present, then Unit Price (POC-06) is required
If either Product/Service ID Qualifier (POC-08) or Product/Service ID (POC-09) is present, then the other is required
If either Product/Service ID Qualifier (POC-10) or Product/Service ID (POC-11) is present, then the other is required
If either Product/Service ID Qualifier (POC-12) or Product/Service ID (POC-13) is present, then the other is required
POC-02
670
Change or Response Type Code
Required
Identifier (ID)

Code specifying the type of change to the line item

AI
Add Additional Item(s)
DI
Delete Item(s)
PC
Price Change
QD
Quantity Decrease
QI
Quantity Increase
RE
Replacement Item
RZ
Replace All Values
POC-03
330
Quantity Ordered
Optional
Decimal number (R)
Min 1Max 15

Quantity ordered

Usage notes

This is the revised quantity for an item that is changed or the order quantity for an item that is added.

POC-04
671
Quantity Left to Receive
Optional
Decimal number (R)
Min 1Max 9

Quantity left to receive as qualified by the unit of measure

Usage notes

This is the revised quantity less the quantity that has been received
previously.

POC-05
C001
Composite Unit of Measure
RequiredMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-01
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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

CA
Case
EA
Each
PR
Pair
ST
Set
POC-06
212
Unit Price
Optional
Decimal number (R)
Min 1Max 15

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

Usage notes

The price is sent with a decimal point only when needed, e.g., $219.99
would be sent as "219.99", and $289.00 would be sent as "289".

To indicate a no charge item or free goods, PO104 will contain a single zero (0) and POC06 will contain code NC.

SKU cost price. Cost price is per unit of measure. Price contains a maximum of five integer and two decimal positions for all retail merchandise.

POC-07
639
Basis of Unit Price Code
Optional
Identifier (ID)

Code identifying the type of unit price for an item

Usage notes

This data element is used to clarify the basis of unit price. The unit price
expressed in POC07 is always in the same terms as the unit of measure in PO103.

NC
No Charge
WH
Wholesale
POC-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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

IN
Buyer's Item Number
POC-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

This is the Retailer's identification number for the item.

POC-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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

VN
Vendor's (Seller's) Item Number
POC-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

This is the Manufacturing Style Number for the item.

POC-12
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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

IZ
Buyer's Size Code
POC-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

This is the size of the item requested.

PID Loop
OptionalMax >1
PID
0500
Detail > POC Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

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

Usage notes

The PID segment is used to provide product/item descriptions in text and or coded formats.

Example
PID-01
349
Item Description Type
Required
Identifier (ID)

Code indicating the format of a description

  • 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.
F
Free-form
PID-02
750
Product/Process Characteristic Code
Optional
Identifier (ID)

Code identifying the general class of a product or process characteristic

08
Product
PID-03
559
Agency Qualifier Code
Optional
Identifier (ID)

Code identifying the agency assigning the code values

  • Use PID03 to indicate the organization that publishes the code list being referred to.
VI
Voluntary Inter-Industry Commerce Standard (VICS) EDI
PID-05
352
Description
Optional
String (AN)
Min 1Max 80

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

Usage notes

This contains the retailer's item description for the product.

PID Loop end
MTX
2920
Detail > POC Loop > MTX

Text

OptionalMax use >1

To specify textual data

Usage notes

This is used to describe detail requirements for special orders.

Example
If Note Reference Code (MTX-01) is present, then Message Text (MTX-02) is required
MTX-01
363
Note Reference Code
Optional
Identifier (ID)

Code identifying the functional area or purpose for which the note applies

PDS
Product Specification
MTX-02
1551
Message Text
Optional
String (AN)
Min 1Max 4096

To transmit large volumes of message text

POC Loop end
Detail end

Summary

CTT Loop
OptionalMax >1
CTT
0100
Summary > CTT Loop > CTT

Transaction Totals

RequiredMax use 1

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

  • Number of line items (CTT01) is the accumulation of the number of POC segments.
    If used, hash total (CTT02) is the sum of the value of quantities ordered (POC03) for each POC segment.
Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

Usage notes

The number of POC segments present in the transaction set.

CTT Loop end
SE
0300
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

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

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

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

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.