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

X12 855 Purchase Order Acknowledgment

X12 Release 5010

This X12 Transaction Set 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
  • ^ Repetition
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/j-crew/purchase-order-acknowledgment/01H4G4MDQSZ0QR290KHFF1C2MN
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
BAK
0200
Beginning Segment for Purchase Order Acknowledgment
Max use 1
Required
REF
0500
Internal Vendor Number
Max use 1
Required
REF
0500
Approved Factory ID
Max use 1
Required
FOB
0800
F.O.B. Related Instructions
Max use 1
Optional
N1 Loop
summary
CTT Loop
SE
0300
Transaction Set Trailer
Max use 1
Required
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

00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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 Interchange Acknowledgment Requested
1
Interchange Acknowledgment Requested (TA1)
ISA-15
I14
Interchange 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

PR
Purchase Order Acknowledgment (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 where CC represents the first two digits of the calendar year

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

005010
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

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

Usage notes

Vendor Notes:
AC-Used when the PO is accepted, but there are changes to some or all items.
AD- Used when all items are accepted. All [ItemStatusCode] values must contain IA.
RD- Used when all items are rejected. All [ItemStatusCode] values must contain IR

AC
Acknowledge - With Detail and Change
AD
Acknowledge - With Detail, No Change
AK
Acknowledge - No Detail or Change

Only sent when Acknowledging a Full Cancel 860 Order No Line level detail to be sent with this code

RD
Reject with Detail
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 where CC represents the first two digits of the calendar year

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

Purchase Order Date

Required
Date (DT)
CCYYMMDD format

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

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

PO Acknowledgement Date

REF
0500
Heading > REF

Internal Vendor Number

RequiredMax use >1

To specify identifying information

Example
Variants (all may be used)
REFApproved Factory ID
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

IA
Internal Vendor Number

Mandatory - Retailer Assigned Vendor Number as sent on the PO

REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 50

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

Usage notes

Factory Number

REF
0500
Heading > REF

Approved Factory ID

RequiredMax use >1

To specify identifying information

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

Code qualifying the Reference Identification

JD
Approved Factory ID

The factory ID is assigned when J Crew's social compliance department adds an approved factory for a given vendor. It consists of the following components…

“SAP Vendor Number” (without country suffix) + “-“ + “2 character ISO country code for the FACTORY” + “2 digit incremental number assigned by JCI”.

If a vendor doesn’t have any factories, the code would be “SAP Vendor Number” + “-“ + “2 character ISO country code for the VENDOR” + “01”

The vendors should know this code because it is supposed to be printed on the tag sewn into the garment.

REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 50

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

Usage notes

Factory Number

FOB
0800
Heading > FOB

F.O.B. Related Instructions

OptionalMax use >1

To specify transportation instructions relating to shipment

Usage notes

Only return if different from the Purchase Order

Example
If Description (FOB-03) is present, then Location Qualifier (FOB-02) is required
FOB-01
146
Shipment Method of Payment
Required
Identifier (ID)

Code identifying payment terms for transportation charges

  • FOB01 indicates which party will pay the carrier.
DF
Defined by Buyer and Seller
FOB-02
309
Location Qualifier
Optional
Identifier (ID)

Code identifying type of location

  • FOB02 is the code specifying transportation responsibility location.
RG
Region Code
FOB-03
352
Description
Optional
String (AN)
Min 1Max 80

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

N1 Loop
RequiredMax >1
N1
3000
Heading > N1 Loop > N1

Party Identification

RequiredMax use 1

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

Example
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

SU
Supplier/Manufacturer
Required
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)

91
Assigned by Seller or Seller'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.
N2
3100
Heading > N1 Loop > N2

Additional Name Information

OptionalMax use 2

To specify additional names

Example
Required
String (AN)
Min 1Max 60

Free-form name

N3
3200
Heading > N1 Loop > N3

Party Location

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 > N1 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Required
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
Required
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
Required
Identifier (ID)
Min 2Max 3

Code identifying the country

N1 Loop end
Heading end

Detail

PO1 Loop
RequiredMax >1
Usage notes

Lines will not be sent back on the 855 when using the AK to acknowledge a full 860 order cancel

PO1
0100
Detail > PO1 Loop > PO1

Baseline Item Data

RequiredMax use 1

To specify basic and most frequently used line item data

  • PO102 is required.
Example
If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) 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
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

Acknowledge back the Prepack detail lines at this level Include the matchingLine Seqeunce Number

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

Numeric value of quantity

  • PO102 is quantity ordered.
Usage notes

Original PO order qty

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.

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.
BP
Buyer's Part Number
PO1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

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

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

UP
UCC - 12
PO1-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

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

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

CH
Country of Origin Code
PO1-11
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

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

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

BO
Buyers Color
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)

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

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

Identifying number for a product or service

PID Loop
RequiredMax >1
PID
0500
Detail > PO1 Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

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

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
Required
Identifier (ID)

Code identifying the general class of a product or process characteristic

08
Product

Mandatory -Item Description

PID-05
352
Description
Required
String (AN)
Min 1Max 80

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

PID Loop end
DTM
2000
Detail > PO1 Loop > DTM

Date/Time Reference

RequiredMax use 10

To specify pertinent dates and times

Usage notes

Send back the original Ship From Port date from the PO

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

Original Ship From Port Date

Required
Date (DT)
CCYYMMDD format

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

TD1
2300
Detail > PO1 Loop > TD1

Carrier Details (Quantity and Weight)

OptionalMax use 1

To specify the transportation details relative to commodity, weight, and quantity

Usage notes

Only send if updating the HTS number

Example
If Commodity Code Qualifier (TD1-03) is present, then Commodity Code (TD1-04) is required
TD1-03
23
Commodity Code Qualifier
Optional
Identifier (ID)

Code identifying the commodity coding system used for Commodity Code

J
Harmonized System-Based Schedule B
TD1-04
22
Commodity Code
Optional
String (AN)
Min 1Max 30

Code describing a commodity or group of commodities

TD5
2400
Detail > PO1 Loop > TD5

Carrier Details (Routing Sequence/Transit Time)

OptionalMax use 12

To specify the carrier and sequence of routing and provide transit time information

Usage notes

Only send if changing the Transportation Mode

Example
TD5-01
133
Routing Sequence Code
Optional
Identifier (ID)

Code describing the relationship of a carrier to a specific shipment movement

O
Origin Carrier (Air, Motor, or Ocean)
TD5-04
91
Transportation Method/Type Code
Required
Identifier (ID)

Code specifying the method or type of transportation for the shipment

A
Air
AF
Air Freight

Vendor Paid Air

M
Motor (Common Carrier)
S
Ocean
ACK Loop
RequiredMax >1
Usage notes

One ACK allowed per PO1 Line Item

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

DR
Item Accepted - Date Rescheduled
IA
Item Accepted
IC
Item Accepted - Changes Made

Use this code if changing something other than Price/Quantity/Date (i.e. FOBPoint. Country Of Origin, Transportation Method, HTS Number)
If changing more than one status per PO1 line, (i.e. Qty, Price and/or Date) use ICand return the updated values in the correct ACK fields and updated price in thePO104

IP
Item Accepted - Price Changed

If the price has changed new price sent in UnitPrice PO104

IQ
Item Accepted - Quantity Changed
IR
Item Rejected

If used, please include a note why in the MTX02 of the

ACK-02
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

Usage notes

Please send for any status even if not changing the qty from the original PO amount
This will reflect the new Qty if ACK01 = IQ.

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
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 where CC represents the first two digits of the calendar year

Usage notes

Required for any status even if not making a change to the original PO date
This will be the new date if ACK01 = DR

ACK Loop end
N9 Loop
RequiredMax >1
Usage notes

Please send a reason why when a line is rejected (ACK01 = IR)

N9
3500
Detail > PO1 Loop > N9 Loop > N9

Extended Reference Information

RequiredMax use 1

To transmit identifying information as specified by the Reference Identification Qualifier

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

Code qualifying the Reference Identification

L1
Letters or Notes
N9-02
127
Reference Identification
Required
String (AN)

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

GEN
General

Please include a note as to why if rejecting an order line

MTX
3600
Detail > PO1 Loop > N9 Loop > MTX

Text

RequiredMax use >1

To specify textual data

Example
MTX-02
1551
Textual Data
Required
String (AN)
Min 1Max 4096

To transmit large volumes of message text

Usage notes

If an item is being rejected, please provide a note indicating why

N9 Loop end
PO1 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

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