Wal-Mart Stores, Inc.

Electronic Data Interchange Implementation Guideline

ANSI X12 Version 5010

5
0
1
0
824 Application Advice

Business Usage:
Response from Wal-Mart Application System Edits

EDI Direction: From Wal-Mart

Implementation Guide Version 1.1

Published December 2004
Last Changed June 2005
 Table of Contents
824 Application Advice - Wal-Mart Stores, Inc. Introduction .................................................................................................3

824 Application Advice – Wal-Mart Stores, Inc. Implementation ..........................................................................................4

Wal-Mart Stores, Inc. Business Example of an 824 EDI Document.......................................................................................6

824 Application Advice - ANSI X12 Introduction...................................................................................................................19

824 Application Advice – ANSI X12 Standards.......................................................................................................................20

824 Application Advice - VICS Introduction............................................................................................................................22

Conventions used in these guidelines..........................................................................................................................................24

Example of Conventions...............................................................................................................................................................26

824 Application Advice – Changes from Previous (4030) Version.......................................................................................27

Change History................................................................................................................................................................................28

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 2

824 Application Advice - Wal-Mart Stores, Inc. Introduction
The purpose of this 824 implementation is to enable Wal-Mart to notify suppliers of invalid or
insufficient data sent to Wal-Mart applications for transaction sets 830, 832, 855, 856 etc..
Receipt of an 824 for a rejected document requires action. It is very important when dealing with
time sensitive documents to correct any errors and re-send these documents as soon as possible.
Note: Do not use this transaction set to communicate EDI compliance errors.

Business Changes

To support our growing company, Wal-Mart Stores, Inc. will be incorporating the following
business changes into this 5010 upgrade.

Wal-Mart will utilize the GTIN (Global Traded Item Number) in EDI X12 Version 5010. GTIN
information will be sent in addition to the UPC code. It will be the suppliers' responsibility to
handle the information as their systems become GTIN compliant. For more information
regarding GTIN, please visit the UCC website (<www.uc-council.org>) in the U.S. and ECCC
(<www.eccc.org>) in Canada, or the appropriate numbering orga nization for your country.

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 3

824 Application Advice – Wal-Mart Stores, Inc.
Implementation

Functional Group ID= AG

Heading:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
M 0100 ST Transaction Set Header M 1
M 0200 BGN Beginning Segment M 1
LOOP ID - N1 >1
0300 N1 Party Identification O 1
0700 REF Reference Identification O 12

Detail:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
LOOP ID - OTI >1
M 0100 OTI Original Transaction Identification M 1 n1
0200 REF Reference Information O 12 n2
0300 DTM Date/Time Reference O 2 n3
0400 PER Administrative Communications Contact O 3 n4
0500 AMT Monetary Amount Information O >1 n5
0600 QTY Quantity Information O >1 n6
0650 NM1 Individual or Organizational Name O 9 n7
LOOP ID - TED >1
0700 TED Technical Error Description O 1
0750 CTX Context O 10
0800 NTE Note/Special Instruction O 100
0820 RED Related Data O 100 n8

LOOP ID - LM >1
0850 LM Code Source Information O 1 n9
LOOP ID - LQ 100
M 0860 LQ Industry Code Identification M 1
0870 RED Related Data O 100 n10

M 0900 SE Transaction Set Trailer M 1

Transaction Set Notes

1. The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this
application acknowledgment.
2. The REF segment allows for the provision of secondary reference identification or numbers required to
uniquely identify the original transaction set. The primary reference identification or number should be
provided in elements OTI02-03.
3. The DTM segment allows for the provision of date, time, or date and time information required to uniquely
identify the original transaction set.
4. The PER segment should be utilized if administrative communications contact information is important to the
unique identification of the original transaction set.
824-5010 (005010) Wal-Mart Stores, Inc. Confidential 4
5. The AMT segment should be utilized if monetary amount information is important to the unique
identification of the original transaction set.
6. The QTY segment should be utilized if quantity information is important to the unique identification of the
original transaction set.
7. The NM1 segment allows for the provision of entity identification information required to uniquely identify
the original transaction set.
8. The RED segment may be used to provide data related to the error condition specified in the associated
TED01 element.
9. The LM loop is used to identify industry-based or proprietary application error conditions.
10. The RED segment may be used to provide data related to the error condition specified in the associated LQ02
element.

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 5

Wal-Mart Stores, Inc. Business Example of an 824 EDI
Document
EDI TRANSMISSION DESCRIPTION

ST*824*0001 824 is the Transaction Set Identifier Code. “824”

Indicates an “Application Advice”.
0001 is the Transaction Set Control Number.
BGN*00*2066400*20050202 00 is the Transaction Set Purpose Code. “00”
indicates an “Original”.
2066400 is the Reference Identification.
20050202 is the Date that the transaction was generated
by Wal-Mart.
N1*FR*WAL-MART STORES FR is the Entity Identifier Code. “FR” indicates
INC.*UL*0078742000008 “Message From”.
WAL-MART STORES INC. is the Name.
UL is the Identification Code Qualifier. “UL”
indicates “Global Location Number (GLN)”.
0078742000008 is the Identification Code.
N1*TO*SUPPLIER NAME TO is the Entity Identifier Code . “TO” indicates
“Message To”.
SUPPLIER NAME is the Name.
REF*IA*123456060 IA is the Reference Identification Qualifier. “IA”
indicates “Internal Vendor Number”.
123456060 is the Reference Identification.
OTI*TR*TN*2066400*967174AM* 925485US00*200 TR is the Application Acknowledgment Code. “TR”
50201*1530*4419*44190001*856 indicates “Transaction Set Reject”.
TN is the Transaction Reference Qualifier. “TN”
indicates “Transaction Reference Number”.
2066400 is the Reference Identification.
967174AM is the Application Sender’s Code.
925485US00 is the Application Receiver’s Code.
20050201 is the Date .
1530 is the Time
4419 is the Group Control Number.
44190001 is the Transaction Set Control Number.
856 is the Transaction Set Identifier Code. “856”
indicates “Ship Notice/Manifest”.(This indicates the
document Set that was in Error).
TED*024*Not a valid WM store*****9999 024 is the Application Error Condition Code. “024”
indicates “Other Unlisted Reason”.
Not a valid WM store is the Free Form Message.
9999 is the Copy of Bad Data Element.
NTE**Error is not a valid or approved Wal -Mart Error is not a valid or approved Wal-Mart store
store number for the vendor. Record Rejected. number for the vendor. Record Rejected. is the
Description. Note that this segment will only be used if
the error description in the TED contains more than 60
characters of data.
SE*9*0001 9 is the Number of Included Segments (including ST
& SE).
0001 is the Transaction Set Control Number.

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 6

 Segment: ST Transaction Set Header
Position: 0100
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes: 1 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).
2 The implementation convention reference (ST03) is used by the translation routines
of the interchange partners to select the appropriate implementation convention to
match the transaction set definition.
Comments:

Data Element Summary

Ref. Data
Des. Element Name Attributes
M ST01 143 Transaction Set Identifier Code M 1 ID 3/3
Code uniquely identifying a Transaction Set
824 Application Advice
M ST02 329 Transaction Set Control Number M 1 AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
The number is sequentially assigned by the sender starting with 0001
within each functional group. For each functional group, the first
transaction set control number will be 0001 and incremented by one for
each additional transaction set within the group.
ST03 1705 Implementation Convention Reference O 1 AN 1/35
Reference assigned to identify Implementation Convention

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 7

 Segment: BGN Beginning Segment
Position: 0200
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of a transaction set
Syntax Notes: 1 If BGN05 is present, then BGN04 is required.
Semantic Notes: 1 BGN02 is the transaction set reference number.
2 BGN03 is the transaction set date.
3 BGN04 is the transaction set time.
4 BGN05 is the transaction set time qualifier.
5 BGN06 is the transaction set reference number of a previously sent transaction
affected by the current transaction.
Comments:

Data Element Summary

Ref. Data
Des. Element Name Attributes
M BGN01 353 Transaction Set Purpose Code M 1 ID 2/2
Code identifying purpose of transaction set
00 Original
M BGN02 127 Reference Identification M 1 AN 1/50
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
The sender's internal number used to identify this transaction set within
the sender's application system.
M BGN03 373 Date M 1 DT 8/8
Date expressed as CCYYMMDD where CC represents the first two digits of
the calendar year
The date the transaction was generated in the sender's application system.
It is analogous to the date placed on the paper document; the date it was
written.
BGN04 337 Time X 1 TM 4/8
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)
BGN05 623 Time Code O 1 ID 2/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
BGN06 127 Reference Identification O 1 AN 1/50
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
BGN07 640 Transaction Type Code O 1 ID 2/2
Code specifying the type of transaction
BGN08 306 Action Code O 1 ID 1/2
Code indicating type of action
BGN09 786 Security Level Code O 1 ID 2/2
Code indicating the level of confidentiality assigned by the sender to the
information following

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 8

 Segment: N1 Name
Position: 0300
Loop: N1
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
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.

Notes: In some EDI Implementations, it may be necessary to identify the sender and/or
receiver of the transaction set within each transaction set. To identify the sender of
the transaction set, N101 will contain code FR, N103 will contain 93, and N104 will
contain the actual identification number. To identify the receiver of the transaction
set, N101 will contain code TO, N103 will contain code 94, and N104 will contain the
actual identification number. These four codes may be used only in the combination
listed above and may be used only to identify the sender and/or receiver of the
transaction set.

Data Element Summary

Ref. Data
Des. Element Name Attributes
M N101 98 Entity Identifier Code M 1 ID 2/3
Code identifying an organizational entity, a physical location, property or an
individual
FR Message From
N102 93 Name X 1 AN 1/60
Free-form name
N103 66 Identification Code Qualifier X 1 ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
UL Global Location Number (GLN)
A globally unique 13 digit code for the identification of a
legal, functional or physical location within the Uniform
Code Council (UCC) and International Article Number
Association (EAN) numbering system
N104 67 Identification Code X 1 AN 2/80
Code identifying a party or other code
N105 706 Entity Relationship Code O 1 ID 2/2
Code describing entity relationship
N106 98 Entity Identifier Code O 1 ID 2/3
Code identifying an organizational entity, a physical location, property or an
individual

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 9

 Segment: N1 Name
Position: 0300
Loop: N1
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
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.

Notes: In some EDI Implementations, it may be necessary to identify the sender and/or
receiver of the transaction set within each transaction set. To identify the sender of
the transaction set, N101 will contain code FR, N103 will contain 93, and N104 will
contain the actual identification number. To identify the receiver of the transaction
set, N101 will contain code TO, N103 will contain code 94, and N104 will contain the
actual identification number. These four codes may be used only in the combination
listed above and may be used only to identify the sender and/or receiver of the
transaction set.

Data Element Summary

Ref. Data
Des. Element Name Attributes
M N101 98 Entity Identifier Code M 1 ID 2/3
Code identifying an organizational entity, a physical location, property or an
individual
TO Message To
N102 93 Name X 1 AN 1/60
Free-form name
N103 66 Identification Code Qualifier X 1 ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
N104 67 Identification Code X 1 AN 2/80
Code identifying a party or other code
N105 706 Entity Relationship Code O 1 ID 2/2
Code describing entity relationship
N106 98 Entity Identifier Code O 1 ID 2/3
Code identifying an organizational entity, a physical location, property or an
individual

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 10

 Segment: REF Reference Identification
Position: 0700
Loop: N1
Level: Heading
Usage: Optional
Max Use: 12
Purpose: To specify identifying information
Syntax Notes: 1 At least one of REF02 or REF03 is required.
2 If either C04003 or C04004 is present, then the other is required.
3 If either C04005 or C04006 is present, then the other is required.
Semantic Notes: 1 REF04 contains data relating to the value cited in REF02.
Comme nts:

Data Element Summary

Ref. Data
Des. Element Name Attributes
M REF01 128 Reference Identification Qualifier M 1 ID 2/3
Code qualifying the Reference Identification
IA Internal Vendor Number
REF02 127 Reference Identification X 1 AN 1/50
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
This is the Wal-Mart vendor number.
REF03 352 Description X 1 AN 1/80
A free-form description to clarify the related data elements and their content
REF04 C040 Reference Identifier O 1
To identify one or more reference numbers or identification numbers as
specified by the Reference Qualifier
C04001 128 Reference Identification Qualifier M ID 2/3
Code qualifying the Reference Identification
C04002 127 Reference Identification M AN 1/50
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
C04003 128 Reference Identification Qualifier X ID 2/3
Code qualifying the Reference Identification
C04004 127 Reference Identification X AN 1/50
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
C04005 128 Reference Identification Qualifier X ID 2/3
Code qualifying the Reference Identification
C04006 127 Reference Identification X AN 1/50
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 11

 Segment: OTI Original Transaction Identification
Position: 0100
Loop: OTI
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To identify the edited transaction set and the level at which the results of the edit are
reported, and to indicate the accepted, rejected, or accepted-with-change edit result
Syntax Notes: 1 If OTI09 is present, then OTI08 is required.
Semantic Notes: 1 OTI03 is the primary reference identification or number used to uniquely identify the
original transaction set.
2 OTI06 is the group date.
3 OTI07 is the group time.
4 If OTI11 is present, it will contain the version/release under which the original
electronic transaction was translated by the receiver.
5 OTI12 is the purpose of the original transaction set, and is used to assist in its unique
identification.
6 OTI13 is the type of the original transaction set, and is used to assist in its unique
identification.
7 OTI14 is the application type of the original transaction set, and is used to assist in
its unique identification.
8 OTI15 is the type of action indicated or requested by the original transaction set, and
is used to assist in its unique identification.
9 OTI16 is the action requested by the original transaction set, and is used to assist in
its unique identification.
10 OTI17 is the status reason of the original transaction set, and is used to assist in its
unique identification.
Comments: 1 OTI02 contains the qualifier identifying the business transaction from the original
business application, and OTI03 will contain the original business application
identification.
2 If used, OTI04 through OTI08 will contain values from the original electronic
functional group generated by the sender.
3 If used, OTI09 through OTI10 will contain values from the original electronic
transaction set generated by the sender.
Data Element Summary
Ref. Data
Des. Element Name Attributes
M OTI01 110 Application Acknowledgment Code M 1 ID 1/2
Code indicating the application system edit results of the business data
TA Transaction Set Accept
TE Transaction Set Accept with Errors
TR Transaction Set Reject
M OTI02 128 Reference Identification Qualifier M 1 ID 2/3
Code qualifying the Reference Identification
TN Transaction Reference Number
The actual business application identification number for
the transaction will be in OTI03, e.g., purchase order
number, invoice number, ship notice number, etc.
M OTI03 127 Reference Identification M 1 AN 1/50
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
Identification of the transaction within the business application, or the
financial institution's trace number.
OTI04 142 Application Sender's Code O 1 AN 2/15
Code identifying party sending transmission; codes agreed to by trading
partners
Contains GS02 data contents from the original functional group generated
by the sender.
OTI05 124 Application Receiver's Code O 1 AN 2/15

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 12

 Code identifying party receiving transmission; codes agreed to by trading partners
Contains GS03 data contents from the original functional group generated by
the sender.
OTI06 373 Date O 1 DT 8/8
Date expressed as CCYYMMDD where CC represents the first two digits of
the calendar year
Contains GS04 data contents from the original functional group generated
by the sender.
OTI07 337 Time O 1 TM 4/8
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)
Contains GS05 data contents from the original functional group generated
by the sender.
OTI08 28 Group Control Number X 1 N0 1/9
Assigned number originated and maintained by the sender
Contains GS06 data contents from the original functional group generated
by the sender.
OTI09 329 Transaction Set Control Number O 1 AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
Contains ST02 data contents from the original transaction set header
generated by the sender.
OTI10 143 Transaction Set Identifier Code O 1 ID 3/3
Code uniquely identifying a Transaction Set
Contains ST01 data contents from the original transaction set header
generated by the sender. If the original document was not an EDI
transaction, use the appropriate code that would have been in ST01, e.g.,
paper invoice would be 810.
212 Motor Carrier Delivery Trailer Manifest
214 Transportation Carrier Shipment Status Message
830 Planning Schedule with Release Capability
832 Price/Sales Catalog
855 Purchase Order Acknowledgment
856 Ship Notice/Manifest
879 Price Information
888 Item Maintenance
889 Promotion Announcement
OTI11 480 Version / Release / Industry Identifier Code O 1 AN 1/12
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
OTI12 353 Transaction Set Purpose Code O 1 ID 2/2
Code identifying purpose of transaction set
OTI13 640 Transaction Type Code O 1 ID 2/2
Code specifying the type of transaction
OTI14 346 Application Type O 1 ID 2/2
Code identifying an application
OTI15 306 Action Code O 1 ID 1/2
Code indicating type of action
OTI16 305 Transaction Handling Code O 1 ID 1/2
Code designating the action to be taken by all parties
824-5010 (005010) Wal-Mart Stores, Inc. Confidential 13
 OTI17 641 Status Reason Code O 1 ID 3/3
Code indicating the status reason

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 14

 Segment: TED Technical Error Description
Position: 0700
Loop: OTI-TED
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To identify the error and, if feasible, the erroneous segment, or data element, or both
Syntax Notes:
Semantic Notes:
Comments: 1 If used, TED02 will contain a generic description of the data in error (e.g., part
number, date, reference number, etc.).

Data Element Summary

Ref. Data
Des. Element Name Attributes
M TED01 647 Application Error Condition Code M 1 ID 1/3
Code indicating application error condition
007 Missing Data
012 Invalid Combination
024 Other Unlisted Reason
The reason for the application error condition cannot be
described using any other code on the standard code list
134 Missing or Invalid Invoice (Pro) Number
140 Missing or Invalid Ship-To Location
803 Missing or Invalid Payment Method Code
IID Invalid Identification Code
INF Invalid Status Code
IQT Invalid Quantity
IWT Invalid Weight
MB Missing or Invalid Purchase Order Number
MID Missing Identification Code
MK Missing or Invalid Ship Date Location
OTH Other
Unspecified application error
POI Purchase Number Invalid
SCA Invalid SCAC
ZZZ Mutually Defined
TED02 3 Free Form Message O 1 AN 1/60
Free-form text
TED03 721 Segment ID Code O 1 ID 2/3
Code defining the segment ID of the data segment in error (See Appendix A -
Number 77)
TED04 719 Segment Position in Transaction Set O 1 N0 1/6
The numerical count position of this data segment from the start of the
transaction set: the transaction set header is count position 1
TED05 722 Element Position in Segment O 1 N0 1/2
This is used to indicate the relative position of a simple data element, or the
relative position of a composite data structure with the relative position of the
component within the composite data structure, in error; in the data segment
the count starts with 1 for the simple data element or composite data structure
immediately following the segment ID
TED06 725 Data Element Reference Number O 1 N0 1/4
Reference number used to locate the data element in the Data Element
Dictionary
824-5010 (005010) Wal-Mart Stores, Inc. Confidential 15
 TED07 724 Copy of Bad Data Element O 1 AN 1/99
This is a copy of the data element in error
TED08 961 Data Element New Content O 1 AN 1/99
New data which has replaced erroneous data

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 16

 Segment: NTE Note/Special Instruction
Position: 0800
Loop: OTI-TED
Level: Detail
Usage: Optional
Max Use: 100
Purpose: To transmit information in a free-form format, if necessary, for comment or special
instruction
Syntax Notes:
Semantic Notes:
Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12
standard implementations, is not machine processible. The use of the NTE segment
should therefore be avoided, if at all possible, in an automated environment.

Data Element Summary

Ref. Data
Des. Element Name Attributes
NTE01 363 Note Reference Code O 1 ID 3/3
Code identifying the functional area or purpose for which the note applies
M NTE02 352 Description M 1 AN 1/80
A free-form description to clarify the related data elements and their content

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 17

 Segment: SE Transaction Set Trailer
Position: 0900
Loop:
Level: Detail
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted
segments (including the beginning (ST) and ending (SE) segments)
Syntax Notes:
Semantic Notes:
Comments: 1 SE is the last segment of each transaction set.

Data Element Summary

Ref. Data
Des. Element Name Attributes
M SE01 96 Number of Included Segments M 1 N0 1/10
Total number of segments included in a transaction set including ST and SE
segments
M SE02 329 Transaction Set Control Number M 1 AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
This must be the same number as is in the ST segment (ST02) for the
transaction set.

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 18

824 Application Advice - ANSI X12 Introduction

This Draft Standard for Trial Use contains the format and establishes the data contents of the Application
Advice Transaction Set (824) for use within the context of an Electronic Data Interchange (EDI)
environment. The transaction set can be used to provide the ability to report the results of an application
system's data content edits of transaction sets. The results of editing transaction sets can be reported at the
functional group and transaction set level, in either coded or free-form format. It is designed to
accommodate the business need of reporting the acceptance, rejection or acceptance with change of any
transaction set. The Application Advice should not be used in place of a transaction set designed as a
specific response to another transaction set (e.g., purchase order acknowledgment sent in response to a
purchase order).

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 19

824 Application Advice – ANSI X12 Standards

Functional Group ID= AG

Heading:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
M 0100 ST Transaction Set Header M 1
M 0200 BGN Beginning Segment M 1
LOOP ID - N1 >1
0300 N1 Name O 1
0400 N2 Additional Name Information O 2
0500 N3 Address Information O 2
0600 N4 Geographic Location O 1
0700 REF Reference Identification O 12
0800 PER Administrative Communications Contact O 3

Detail:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
LOOP ID - OTI >1
M 0100 OTI Original Transaction Identification M 1 n1
0200 REF Reference Identification O 12 n2
0300 DTM Date/Time Reference O 2 n3
0400 PER Administrative Communications Contact O 3 n4
0500 AMT Monetary Amount O >1 n5
0600 QTY Quantity O >1 n6
0650 NM1 Individual or Organizational Name O 9 n7
LOOP ID - TED >1
0700 TED Technical Error Description O 1
0800 NTE Note/Special Instruction O 100
0820 RED Related Data O 100 n8

LOOP ID - LM >1
0850 LM Code Source Information O 1 n9
LOOP ID - LQ 100
M 0860 LQ Industry Code M 1
0870 RED Related Data O 100 n10

M 0900 SE Transaction Set Trailer M 1

Transaction Set Notes

1. The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this
application acknowledgment.
2. The REF segment allows for the provision of secondary reference identification or numbers required to
uniquely identify the original transaction set. The primary reference identification or number should be
provided in elements OTI02-03.
3. The DTM segment allows for the provision of date, time, or date and time information required to uniquely
identify the original transaction set.
4. The PER segment should be utilized if administrative communications contact information is important to the
unique identification of the original transaction set.

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 20

5. The AMT segment should be utilized if monetary amount information is important to the unique
identification of the original transaction set.
6. The QTY segment should be utilized if quantity information is important to the unique identification of the
original transaction set.
7. The NM1 segment allows for the provision of entity identification information required to uniquely identify
the original transaction set.
8. The RED segment may be used to provide data related to the error condition specified in the associated
TED01 element.
9. The LM loop is used to identify industry-based or proprietary application error conditions.
10. The RED segment may be used to provide data related to the error condition specified in the associated LQ02
element.

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 21

824 Application Advice - VICS Introduction

The purpose of this section is to present and explain the application of the ASC X12 standards as
they pertain to the retail industry implementation of the Application Advice Transaction Set.
The VICS EDI utilization of the transaction set is two fold: 1) to report any application errors
from any business application system, e.g., invoice edit errors, and 2) for a financial institution
(bank) to report acceptance or discrepancies to either the sender or receiver of a Payment Order/
Remittance Advice Transaction Set (820).

When sending an 824 application advice transaction set, the following generation guidelines
should be considered:

§ The 824 eliminates the need for reporting application system edit errors via phone, fax, or
mailed paper reports.
§ Do not use this transaction set to communicate EDI compliance errors. Transaction Set 997
Functional Acknowledgment is to be used for communicating EDI compliance errors.
§ There may be a need within certain business functions to acknowledge receipt of
transmissions with no errors. This will be confined to transaction sets that do not have
existing response transaction sets and only with trading partner agreement. For example, a
financial institution may use Transaction Set 824 to respond to an 820 transmission
confirming the payment order.
§ Do not use Transaction Set 824 for communicating 824 application system edit errors
detected on the 824 Transaction Set, e.g., Functional Acknowledgments are never
acknowledged with a Functional Acknowledgment, nor are Application Advices responded
to by an Application Advice.
§ Transaction Set 832, Price Sales Catalog, edit errors should not be reported to the third party
service provider. Report Transaction Set 832 edits errors to the data originator.
§ Transaction Set 824, where applicable, can be sent for non-EDI documents (e.g., paper
invoice).
§ All edit errors on a document should be reported (do not stop editing once an error is
detected on a document).
§ The 824 can be sent for application errors detected on different transaction sets received, e.g,
810, 856, etc. It is recommended that the 824 sender generate a unique interchange file (ISA
to IEA Segments) for application errors detected on a specific transaction set. For example, a
separate interchange would be generated for application errors detected on an 856 versus
errors detected on an 810. It is also recommended that the 824 sender assign a unique sender-
ID which will enable the 824 receiver to identify which transaction set errors are being
received. By generating a unique interchange and sender-ID for each transaction set’s
application errors, the 824receiver can quickly direct the 824 data to the appropriate internal
group for corrective action.
§ If the sender of this transaction set has access to the GS and ST segments associated with the
detected errors, it is recommended that the following data elements be included in the 824:
functional group number, functional group date, and transaction set control number. This
information can facilitate the error correction process.
§ 824 application errors are usually forwarded to individuals who are not familiar with data
processing terminology. As a result, if it is necessary to describe the error condition in text
form, use business terminology, rather than EDI terminology. For example, use ‘‘store’’
number instead of ‘‘buying location’’, use ‘‘U.P.C. code’’ instead of ‘‘Product/Service ID’’.

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 22

§ The 824 transaction set can be used to accept or reject multiple 820 transaction sets. For the
820, most financial institutions can provide the originator with detailed information about
which payment transactions have been accepted or rejected. Key data from the 820 is used to
uniquely identify each 820 payment; an example would be using the payees account number.
§ Do not use transaction set 824 in place of transaction 812 (Credit/Debit Adjustment) to
communicate adjustments related to allowances or pricing.

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 23

Conventions used in these guidelines

1. Every data element on each segment is listed in the Data Element Summary section of the
segment documentation, including unused Elements.
2. Every data element has the ANSI X12 data element ID noted.
3. Every data element has the ANSI X12 data element title noted.
4. Every data element has the ANSI X12 data element attributes noted:
4.1. Data element requirement designation
4.1.1. Mandatory (M) This element is required to appear in the segment.
4.1.2. Optional (O) The appearance of this data element is at the option of the
sending party or is based on the mutual agreement of the interchange
parties.
4.1.3. Relational (X) Relational conditions may exist between two or more data
elements within a segment based on the presence or absence of one of
those data elements. The relational condition is displayed under the
heading “Syntax Notes.”
4.2. Data element type
4.2.1. Numeric (Nn) — The numeric type of data element is symbolized by the
two-position representation Nn. N indicates a numeric, and n indicates the
decimal places to the right of a fixed, implied decimal point. the decimal
point is not transmitted in the character stream. For negative values, the
leading minus sign (-) is used. Absence of a sign indicates a positive
value. The plus sign (+) should not be transmitted. Leading zeros should
be suppressed unless necessary to satisfy a minimum length requirement.
The length of the data element is the number of digits used. The minus
sign (-) is not counted when determining the length of the data element
value.
4.2.2. Decimal Number (R) — The decimal type of data element is symbolized
by the representation R. The decimal point is optional for integer values,
but required for fractional values. For negative values, the leading minus
sign (-) is used. Absence of a sign indicates a positive value. The plus
sign (+) should not be transmitted. Leading zeros should be suppressed
unless necessary to satisfy a minimum length requirement. The minus
sign and the decimal point are not counted when determining the length of
the data element value.
4.2.3. Identifier (ID) — The identifier type of data element is symbolized by the
representation ID. An identifier data element must always contain a value
from a predefined list of values that is maintained by ASC X12 or other
bodies that are recognized by ASC X12. The value is left justified.
Trailing spaces should be suppressed.
4.2.4. String (AN) — The string type of data element is symbolized by the
representation AN. Contents of string type data elements are a sequence
of any letters, digits, spaces, and/or special characters and contain at least
one non-space character. The significant characters must be left justified.
Leading spaces, if used, are assumed to be significant characters. Trailing
spaces should be suppressed.
4.2.5. Date (DT) — The date type of data element is symbolized by the
representation DT. Format for the date type is CCYYMMDD. CC is the
two digit Century (00-99). YY is the last two digits of the year (00-99),
824-5010 (005010) Wal-Mart Stores, Inc. Confidential 24
 MM is the numeric value of the month (01-12), and DD is the numeric
value of the day (01-31).
4.2.6. Time (TM) — The time type is symbolized by the representation TM.
Format for this type is expressed in 24-hour clock format, HHMMSSd..d.
HH is the numeric expression of the hour (00-23), MM is the numeric
expression of the minute (00-59), SS is the numeric expression of the
second (00-59), and d..d is the numeric expression of decimal seconds.
4.3. Data element length (minimum/maximum)
5. Data elements utilized by Wal-Mart applications are noted in bold type.
6. Data elements ignored by Wal-Mart application are noted in italicized type.
7. Every data element utilized by Wal-Mart applications has the ANSI X12 data element
purpose noted.
8. ID-type data elements have the list of utilized values noted.
9. Industry comments relating to segments and data elements are noted in bold text with
a shaded background.
10. Wal-Mart comments relating to segments and data elements are noted in underlined
bold text with a shaded background.

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 25

 Example of Conventions

Segment: N1 Name
Position: 0300
Loop: N1
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
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.
Notes: In some EDI Implementations, it may be necessary to identify the sender and/or
receiver of the transaction set within each transaction set. To identify the sender of
the tr ansaction set, N101 will contain code FR, N103 will contain 93, and N104 will
contain the actual identification number. To identify the receiver of the transaction
set, N101 will contain code TO, N103 will contain code 94, and N104 will contain the 9
actual identification number. These four codes may be used only in the combination
listed above and may be used only to identify the sender and/or receiver of the
transaction set.
This segment will always identify Wal-Mart Stores, Inc. as the sender of the
document 10
Data Element Summary
4.3
1 Ref. Data 8 4.1
Des. Element Name Attributes
M N101 98 Entity Identifier Code M ID 2/3
2 Code identifying an organizational entity, a physical location, property or an
individual 4.2
3 FR Message From
N102 93 Name X AN 1/60
Free-form name
N103 66 Identification Code Qualifier X ID 1/2
Code designating the system/method of code structure used for Identification
Code (67) 7
UL UCC/EAN Location Code
A globally unique 13 digit code for the identification of a
legal, functional or physical location within the Uniform
Code Council (UCC) and International Article Number
Association (EAN) numbering system
5 N104 67 Identification Code X AN 2/80
Code identifying a party or other code
1 N105 706 Entity Relationship Code O ID 2/2
Code describing entity relationship
6 N106 98 Entity Identifier Code O ID 2/3
Code identifying an organizational entity, a physical location, property or an
individual

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 26

824 Application Advice – Changes from Previous (4030)
Version
NOTE: This change summary is included as a checklist only, to help ensure that all changes
have been accounted for. It is not to be used as a complete implementation reference, as it does
not include all of the necessary information.

Segment Position Data Element Change Qualifier

No Changes

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 27

Change History

Date Version Description of Changes

December , 2004 DRAFT 0.1 Publish Draft version 0.1 of the Document
January, 2005 Version 1.0 Production version of guide published
June, 2005 Version 1.1 New Application Error Condition Code added to the TED segment.

824-5010 (005010) Wal-Mart Stores, Inc. Confidential 28