Boot Barn
/
Purchase Order Acknowledgment
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Boot Barn. Contact Boot Barn for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Boot Barn 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
  • Partially accepted, balance backordered
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/boot-barn/purchase-order-acknowledgment/01HZHS8RVC98C6W5QNJ5K5W6K1
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
detail
PO1 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

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

Code identifying purpose of transaction set

00
Original
BAK-02
587
Acknowledgment Type
Required
Identifier (ID)

Code specifying the type of acknowledgment

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

Identifying number for Purchase Order assigned by the orderer/purchaser

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BAK04 is the date assigned by the purchaser to purchase order.
BAK-08
127
Reference Identification
Required
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.
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BAK09 is the date assigned by the sender to the acknowledgment.
REF
050
Heading > REF

Reference Identification

OptionalMax use >1

To specify identifying information

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

Code qualifying the Reference Identification

19
Division Identifier
REF-02
127
Reference Identification
Required
String (AN)

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

Usage notes

Must refer to the N902 value sent in the 850 to determine which value to pass in the REF02.

B
B

If the N902 sent in the 850 = "4" then "B" must be passed in the REF02.

C
C

If the N902 sent in the 850 = "3" then "C" must be passed in the REF02.

S
S

If the N902 sent in the 850 = "1" or "2" then "S" must be passed in the REF02.

DTM
150
Heading > DTM

Date/Time Reference

RequiredMax use 10

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

010
Requested Ship
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

DTM02 must be your actual estimated arrival date and not simply a return of the value transmitted in the PO.

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.
Example
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.
PO1-02
330
Quantity Ordered
Required
Decimal number (R)
Min 1Max 15

Quantity ordered

Usage notes

The PO102 must be the actual quantity transmitted in the PO.

PO1-03
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

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

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

Usage notes

The PO104 must be the actual cost of each item transmitted in the PO.

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.
UP
U.P.C. Consumer Package Code (1-5-5-1)
PO1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

CTP
040
Detail > PO1 Loop > CTP

Pricing Information

OptionalMax use >1

To specify pricing information

Example
CTP-03
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

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

  • See Figures Appendix for an example detailing the use of CTP03 and CTP04.
  • See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.
Usage notes

The CTP03 is the actual unit cost. This may or may not match the PO104. Boot Barn will use CTP03 to determine cost discrepancies.

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

Example
If Date/Time Qualifier (ACK-04) is present, then Date (ACK-05) 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

IA
Item Accepted
IB
Item Backordered
IR
Item Rejected
ACK-02
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

Usage notes

If the ACK01 = "IB" or "IR", then the ACK02 is the quantity being backordered/cancelled.

If the ACK01 = "IA", then the ACK02 is quantity being fulfilled.

ACK-03
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

EA
Each
ACK-04
374
Date/Time Qualifier
Optional
Identifier (ID)

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

010
Requested Ship
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

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.
Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

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

EDI Samples

Partially accepted, balance backordered

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240604*2336*U*00401*000000001*0*T*>~
GS*PR*SENDERGS*RECEIVERGS*20240604*233646*000000001*X*004010~
BAK*00*AC*PONUM*20170524****ACKNUM*20170524~
DTM*010*20170615~
PO1*1*3*EA*12.75**UP*000000000000~
CTP***25~
ACK*IA*1*EA~
ACK*IB*2*EA~
CTT*1~
GE*1*000000001~
IEA*1*000000001~

Partially accepted, balance rejected

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240604*2337*U*00401*000000001*0*T*>~
GS*PR*SENDERGS*RECEIVERGS*20240604*233703*000000001*X*004010~
BAK*00*AC*PONUM*20170524****ACKNUM*20170524~
DTM*010*20170615~
PO1*1*3*EA*12.75**UP*000000000000~
CTP***25~
ACK*IA*1*EA~
ACK*IR*2*EA~
CTT*1~
GE*1*000000001~
IEA*1*000000001~

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.