Medline Industries
/
Purchase Order Acknowledgment
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Medline Industries . Contact Medline Industries for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Medline Industries  logo

X12 855 Purchase Order Acknowledgment

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/medline-industries/purchase-order-acknowledgment/01HP70VGR7HKP59ZSEB5T8PG58
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
010
Transaction Set Header
Max use 1
Required
BAK
020
Beginning Segment for Purchase Order Acknowledgment
Max use 1
Required
DTM
150
Date/Time Reference
Max use 10
Optional
N1 Loop
detail
PO1 Loop
PO1
010
Baseline Item Data
Max use 1
Required
PID Loop
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 to identify 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 to identify 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

Qualifier to designate 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

Qualifier to designate 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
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
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 sent by the sender to request an interchange acknowledgment (TA1)

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

Code to indicate 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

PR
Purchase Order Acknowledgement (855)
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

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

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 used in conjunction with Data Element 480 to identify the issuer of the standard

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

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
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) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
855
Purchase Order Acknowledgment
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

BAK
020
Heading > BAK

Beginning Segment for Purchase Order Acknowledgment

RequiredMax use 1

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

Usage notes
  1. BAK04 is the date assigned by the purchaser to purchase order.
    2 BAK08 is the seller's order number.
    3 BAK09 is the date assigned by the sender to the acknowledgment.
Example
BAK-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

06
Confirmation
BAK-02
587
Acknowledgment Type
Required
Identifier (ID)

Code specifying the type of acknowledgment

AD
Acknowledge - With Detail, No Change
BAK-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Medline's purchase order number

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

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

Medline's purchase order date

BAK-05
328
Release Number
Optional
String (AN)
Min 1Max 30

Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

BAK-06
326
Request Reference Number
Optional
String (AN)
Min 1Max 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)

BAK-07
367
Contract Number
Optional
String (AN)
Min 1Max 30

Contract number

BAK-08
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

  • BAK08 is the seller's order number.
Usage notes

Vendor's order number

Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BAK09 is the date assigned by the sender to the acknowledgment.
Usage notes

Vendor order date

BAK-10
640
Transaction Type Code
Optional
Identifier (ID)
Min 2Max 2

Code specifying the type of transaction

DTM
150
Heading > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Example
If either Date Time Period Format Qualifier (DTM-05) or Date Time Period (DTM-06) is present, then the other is required
At least one of Date (DTM-02), Time (DTM-03) or Date Time Period Format Qualifier (DTM-05) is required
If Time Code (DTM-04) is present, then Time (DTM-03) is required
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

Usage notes

At least one of DTM02 DTM03 or DTM05 is required.
2 If DTM04 is present, then DTM03 is required.
3 If either DTM05 or DTM06 is present, then the other is required.

002
Delivery Requested
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

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

DTM-04
623
Time Code
Optional
Identifier (ID)
Min 2Max 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

DTM-05
1250
Date Time Period Format Qualifier
Optional
Identifier (ID)
Min 2Max 3

Code indicating the date format, time format, or date and time format

DTM-06
1251
Date Time Period
Optional
String (AN)
Min 1Max 35

Expression of a date, a time, or range of dates, times or dates and times

N1 Loop
RequiredMax >1
N1
300
Heading > N1 Loop > N1

Name

RequiredMax use 1

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

Usage notes
  1. At least one of N102 or N103 is required.
    2 If either N103 or N104 is present, then the other is required.

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

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

ST
Ship To
VN
Vendor
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

Vendor name and Medline's ship-to name

N1-03
66
Identification Code Qualifier
Required
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
Required
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

Code identifying Medline's ship-to locations or Vendor number.
(Echo back from the N104 segment of the 850)

N1-05
706
Entity Relationship Code
Optional
Identifier (ID)
Min 2Max 2

Code describing entity relationship

  • N105 and N106 further define the type of entity in N101.
N1-06
98
Entity Identifier Code
Optional
Identifier (ID)
Min 2Max 3

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

N1 Loop end
Heading end

Detail

PO1 Loop
RequiredMax >1
PO1
010
Detail > PO1 Loop > PO1

Baseline Item Data

RequiredMax use 1

To specify basic and most frequently used line item data

  • PO102 is required.
Usage notes

If PO103 is present, then PO102 is required.
2 If PO105 is present, then PO104 is required.
3 If either PO106 or PO107 is present, then the other is required.
4 If either PO108 or PO109 is present, then the other is required.
5 If either PO110 or PO111 is present, then the other is required.
6 If either PO112 or PO113 is present, then the other is required.
7 If either PO114 or PO115 is present, then the other is required.
8 If either PO116 or PO117 is present, then the other is required.
9 If either PO118 or PO119 is present, then the other is required.
10 If either PO120 or PO121 is present, then the other is required.
11 If either PO122 or PO123 is present, then the other is required.
12 If either PO124 or PO125 is present, then the other is required.

Comments:
1 See the Data Element Dictionary for a complete list of IDs.
2 PO101 is the line item identification.
3 PO106 through PO125 provide for ten different product/service IDs per each item.
For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

Example
If either Product/Service ID Qualifier (PO1-10) or Product/Service ID (PO1-11) is present, then the other is required
If either Product/Service ID Qualifier (PO1-12) or Product/Service ID (PO1-13) is present, then the other is required
If either Product/Service ID Qualifier (PO1-14) or Product/Service ID (PO1-15) is present, then the other is required
If either Product/Service ID Qualifier (PO1-16) or Product/Service ID (PO1-17) is present, then the other is required
If either Product/Service ID Qualifier (PO1-18) or Product/Service ID (PO1-19) is present, then the other is required
If either Product/Service ID Qualifier (PO1-20) or Product/Service ID (PO1-21) is present, then the other is required
If either Product/Service ID Qualifier (PO1-22) or Product/Service ID (PO1-23) is present, then the other is required
If either Product/Service ID Qualifier (PO1-24) or Product/Service ID (PO1-25) is present, then the other is required
PO1-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • PO101 is the line item identification.
Usage notes

Medline's purchase order line number
(Must echo back from the 850)

PO1-02
330
Quantity Ordered
Required
Decimal number (R)
Min 1Max 15

Quantity ordered

PO1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)
Min 2Max 2

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

PO1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

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

PO1-05
639
Basis of Unit Price Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type of unit price for an item

PO1-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

  • PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
VN
Vendor's (Seller's) Item Number
PO1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Vendor material number

PO1-08
235
Product/Service ID Qualifier
Required
Identifier (ID)

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

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

Identifying number for a product or service

Usage notes

Medline's material number

PO1-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

PO1-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-12
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

PO1-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-14
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

PO1-15
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-16
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

PO1-17
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-18
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

PO1-19
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-20
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

PO1-21
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-22
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

PO1-23
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PO1-24
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

PO1-25
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

PID Loop
OptionalMax >1
PID
050
Detail > PO1 Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

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

Usage notes

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 PID04 is required.
5 If PID09 is present, then PID05 is required.

Semantic Notes:

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; an "N" indicates it does
not apply. Any other value is indeterminate.
4 PID09 is used to identify the language being used in PID05.

Comments:

1 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.
2 Use PID06 when necessary to refer to the product surface or layer being described in
the segment.
3 PID07 specifies the individual code list of the agency specified in PID03.

Example
If Product Description Code (PID-04) is present, then Agency Qualifier Code (PID-03) is required
If Source Subqualifier (PID-07) is present, then Agency Qualifier Code (PID-03) is required
If Yes/No Condition or Response Code (PID-08) is present, then Product Description Code (PID-04) is required
At least one of Product Description Code (PID-04) or Description (PID-05) is required
If Language Code (PID-09) is present, then Description (PID-05) is required
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)
Min 2Max 3

Code identifying the general class of a product or process characteristic

PID-03
559
Agency Qualifier Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying the agency assigning the code values

  • Use PID03 to indicate the organization that publishes the code list being referred to.
PID-04
751
Product Description Code
Optional
String (AN)
Min 1Max 12

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

  • PID04 should be used for industry-specific product description codes.
PID-05
352
Description
Optional
String (AN)
Min 1Max 80

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

PID-06
752
Surface/Layer/Position Code
Optional
Identifier (ID)
Min 2Max 2

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

  • Use PID06 when necessary to refer to the product surface or layer being described in the segment.
PID-07
822
Source Subqualifier
Optional
String (AN)
Min 1Max 15

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

  • PID07 specifies the individual code list of the agency specified in PID03.
PID-08
1073
Yes/No Condition or Response Code
Optional
Identifier (ID)
Min 1Max 1

Code indicating a Yes or No condition or response

  • 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.
PID-09
819
Language Code
Optional
Identifier (ID)
Min 2Max 3

Code designating the language used in text, from a standard code list maintained by the International Standards Organization (ISO 639)

  • PID09 is used to identify the language being used in PID05.
PID Loop end
ACK Loop
RequiredMax >1
ACK
270
Detail > PO1 Loop > ACK Loop > ACK

Line Item Acknowledgment

RequiredMax use 1

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

Usage notes

If either ACK02 or ACK03 is present, then the other is required.
2 If ACK04 is present, then ACK05 is required.
3 If either ACK07 or ACK08 is present, then the other is required.
4 If either ACK09 or ACK10 is present, then the other is required.
5 If either ACK11 or ACK12 is present, then the other is required.
6 If either ACK13 or ACK14 is present, then the other is required.
7 If either ACK15 or ACK16 is present, then the other is required.
8 If either ACK17 or ACK18 is present, then the other is required.
9 If either ACK19 or ACK20 is present, then the other is required.
10 If either ACK21 or ACK22 is present, then the other is required.
11 If either ACK23 or ACK24 is present, then the other is required.
12 If either ACK25 or ACK26 is present, then the other 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.

Semantic Notes:

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.

Example
If either Product/Service ID Qualifier (ACK-09) or Product/Service ID (ACK-10) is present, then the other is required
If either Product/Service ID Qualifier (ACK-11) or Product/Service ID (ACK-12) is present, then the other is required
If either Product/Service ID Qualifier (ACK-13) or Product/Service ID (ACK-14) is present, then the other is required
If either Product/Service ID Qualifier (ACK-15) or Product/Service ID (ACK-16) is present, then the other is required
If either Product/Service ID Qualifier (ACK-17) or Product/Service ID (ACK-18) is present, then the other is required
If either Product/Service ID Qualifier (ACK-19) or Product/Service ID (ACK-20) is present, then the other is required
If either Product/Service ID Qualifier (ACK-21) or Product/Service ID (ACK-22) is present, then the other is required
If either Product/Service ID Qualifier (ACK-23) or Product/Service ID (ACK-24) is present, then the other is required
If either Product/Service ID Qualifier (ACK-25) or Product/Service ID (ACK-26) is present, then the other is required
If either Agency Qualifier Code (ACK-27) or Source Subqualifier (ACK-28) is present, then the other is required
If Source Subqualifier (ACK-28) is present, then Agency Qualifier Code (ACK-27) and Industry Code (ACK-29) are required
If either Product/Service ID Qualifier (ACK-07) or Product/Service ID (ACK-08) is present, then the other is required
If either Quantity (ACK-02) or Unit or Basis for Measurement Code (ACK-03) is present, then the other is required
ACK-01
668
Line Item Status Code
Required
Identifier (ID)

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
IP
Item Accepted - Price Changed
IR
Item Rejected
ACK-02
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

Usage notes

Expected Ship Quantity

ACK-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 2Max 2

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

ACK-04
374
Date/Time Qualifier
Required
Identifier (ID)

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

068
Current Schedule Ship
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Scheduled Shipping Date

ACK-06
326
Request Reference Number
Optional
String (AN)
Min 1Max 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)

ACK-07
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

ACK-08
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK-09
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

ACK-10
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK-11
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

ACK-12
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK-13
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

ACK-14
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK-15
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

ACK-16
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK-17
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

ACK-18
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK-19
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

ACK-20
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK-21
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

ACK-22
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK-23
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

ACK-24
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK-25
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

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

ACK-26
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ACK-27
559
Agency Qualifier Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying the agency assigning the code values

ACK-28
822
Source Subqualifier
Optional
String (AN)
Min 1Max 15

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

ACK-29
1271
Industry Code
Optional
String (AN)
Min 1Max 30

Code indicating a code from a specific industry code list

  • 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.
ACK Loop end
PO1 Loop end
Detail end

Summary

CTT Loop
RequiredMax >1
CTT
010
Summary > CTT Loop > CTT

Transaction Totals

RequiredMax use 1

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

  • The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
Usage notes

If either CTT03 or CTT04 is present, then the other is required.
2 If either CTT05 or CTT06 is present, then the other is required.
Semantic Notes:
1 This segment is intended to provide hash totals to validate transaction completeness
and correctness.

Example
If either Weight (CTT-03) or Unit or Basis for Measurement Code (CTT-04) is present, then the other is required
If either Volume (CTT-05) or Unit or Basis for Measurement Code (CTT-06) is present, then the other is required
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

CTT-02
347
Hash Total
Optional
Decimal number (R)
Min 1Max 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.

CTT-03
81
Weight
Optional
Decimal number (R)
Min 1Max 10

Numeric value of weight

CTT-04
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 2Max 2

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

CTT-05
183
Volume
Optional
Decimal number (R)
Min 1Max 8

Value of volumetric measure

CTT-06
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 2Max 2

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

CTT-07
352
Description
Optional
String (AN)
Min 1Max 80

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

CTT Loop end
SE
030
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.