Walmart 855 - Purchase Order Acknowledgement

Modified on Tue, May 26 at 9:51 AM

**These specifications are a base model. All customers are responsible for ensuring their map or EDI is compliant with their trading partner's most current specifications.

X12 855 [5010] Purchase Order Acknowledgment

X12 Release 5010Revised March 12, 2024

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

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*00* *00* *XX*XXXXXXXXXXXXXXX*XX*XXXXXXXXXXXXXXX*241023*0539*^*00501*000000000*X*X*>~

ISA-01

I01

Authorization Information Qualifier

Required

Identifier (ID)

Code identifying the type of information in the Authorization Information

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

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

No Interchange Acknowledgment Requested

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

Information

Production Data

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*PR*XXXXXXX*XXX*20241023*1002*00000*X*005010~

GS-01

479

Functional Identifier Code

Required

Identifier (ID)

Code identifying a group of application related transaction sets

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

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

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

Transportation Data Coordinating Committee (TDCC)

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

0100

Transaction Set Header

RequiredMax use 1

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

Example

ST*855*0001~

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

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*19*RJ*0123456789*20221101*****20221104~

BAK-01

353

Transaction Set Purpose Code

Required

Identifier (ID)

Code identifying purpose of transaction set

Cancellation

Send when requesting retailer's purchase order cancellation. When sent, Acknowledgment Type Code (BAK02) should contain Rejected - No Detail (RJ) qualifier.

Seller initiated change

Send when acknowledging a retailer's purchase order with change. When sent the Acknowledge Type Code (BAK02) should contain either code Acknowledge - With Detail and Change (AC) or Acknowledge - With Exception Detail Only (AE) qualifier.

BAK-02

587

Acknowledgment Type

Required

Identifier (ID)

Code specifying the type of acknowledgment

Acknowledge - With Exception Detail Only

Sent when acknowledging PO with changes requested, when sent only the changes being requested should be sent. When sent, Transaction Set Purpose Code (BAK01) with Seller initiated change (19) is required by Walmart.

Rejected - No Detail

When sent, Transaction Set Purpose Code (BAK01) with Cancellation (01) is required by Walmart.

BAK-03

324

Purchase Order Number

Required

String (AN)

Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

This element is required by standard. When sent, this should contain the Walmart Assigned 10-digit PO number as send in the Purchase Order Number (BEG03) on the Purchase Order (X12 850).

BAK-04

373

Date

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

This element is required by standard. When sent, this should contain the original PO date as send in the Date (BEG05) on the Purchase Order (X12 850).

BAK-09

373

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

This element is required by Walmart. When sent, the element must contain the Supplier Acknowledgment Date.

REF

0500

Reference Information

OptionalMax use >1

To specify identifying information

Example

REF*TD*61~

REF-01

128

Reference Identification Qualifier

Required

Identifier (ID)

Code qualifying the Reference Identification

Internal Vendor Number

At least one instance of the Reference Identification (REF) segment with Internal Vendor Number (IA) qualifier is required by Walmart. When sent, the Reference Identification (REF02) element must contain the 9-digit Walmart assigned Supplier/Vendor number with department-sequence.

Reason for Change

One instance of the Reference Information (REF) segment with this qualifier is required by Walmart for all PO header/summary level changes. When sent, a PO Change Reason code from the provided code list must be sent in the Reference Identification (REF02).

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

Weather/Natural Disaster