Fred Meyer
/
Application Advice
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Fred Meyer. Contact Fred Meyer for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Fred Meyer logo

X12 824 Application Advice

X12 Release 5010

This X12 Transaction Set 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).

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
  • Duplicate Carton ID – EDI856
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/fred-meyer/application-advice/01H6V2CK8GPG2T8NT633GNKQVB
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
BGN
0200
Beginning Segment
Max use 1
Required
Message From
detail
OTI Loop
SE
0900
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

AG
Application Advice (824)
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).
824
Application Advice
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

BGN
0200
Heading > BGN

Beginning Segment

RequiredMax use 1

To indicate the beginning of a transaction set

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

Code identifying purpose of transaction set

00
Original
BGN-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

  • BGN02 is the transaction set reference number.
Usage notes

Kroger Assigned unique document ID.

Required
Date (DT)
CCYYMMDD format

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

  • BGN03 is the transaction set date.
N1 Message From
OptionalMax >1
Variants (all may be used)
Message To
N1
0300
Heading > Message From > N1

Party Identification

RequiredMax use 1

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

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

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

Usage notes

If the original document fails the Kroger Application system/If the Original document fails the Inbound Editor then the following elements will contain:

N102 = “The Kroger Co. – EDI Department”
N103 = “93” qualifier
N104 = “9254110060” Kroger’s ISA ID

FR
Message From
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

Division

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

1
D-U-N-S Number, Dun & Bradstreet
9
D-U-N-S+4, D-U-N-S Number with Four Character Suffix
93
Code assigned by the organization originating the transaction set
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
PER
0800
Heading > Message From > PER

Administrative Communications Contact

OptionalMax use 3

To identify a person or office to whom administrative communications should be directed

Example
PER-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

IC
Information Contact
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

EDI Web Site – http://edi.kroger.com

N1 Message From end
N1 Message To
OptionalMax >1
Variants (all may be used)
Message From
N1
0300
Heading > Message To > N1

Party Identification

RequiredMax use 1

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

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

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

Usage notes

If the original document fails the Kroger Application system/If the original
document fails the Inbound Editor then the following element will contain:

N102 = “The Kroger Co. – EDI Department”

TO
Message To
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

Division

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

1
D-U-N-S Number, Dun & Bradstreet
9
D-U-N-S+4, D-U-N-S Number with Four Character Suffix
93
Code assigned by the organization originating the transaction set
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
PER
0800
Heading > Message To > PER

Administrative Communications Contact

OptionalMax use 3

To identify a person or office to whom administrative communications should be directed

Example
PER-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

IC
Information Contact
Required
String (AN)
Min 1Max 60

Free-form name

Usage notes

EDI Web Site – http://edi.kroger.com

N1 Message To end
Heading end

Detail

OTI Loop
RequiredMax >1
OTI
0100
Detail > OTI Loop > OTI

Original Transaction Identification

RequiredMax use 1

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

  • The OTI loop is intended to provide a unique identification of the transaction set that is the subject of this application acknowledgment.
Example
OTI-01
110
Application Acknowledgment Code
Required
Identifier (ID)

Code indicating the application system edit results of the business data

TA
Transaction Set Accept
TE
Transaction Set Accept with Error
TR
Transaction Set Reject
OTI-02
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

  • OTI02 contains the qualifier identifying the business transaction from the original business application, and OTI03 will contain the original business application identification.
TN
Transaction Reference Number
OTI-03
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

  • OTI03 is the primary reference identification or number used to uniquely identify the original transaction set.
Usage notes

Division Number, PO Number, Invoice Number, Original document reference #. We will send the control# of the transmission if the document received does not have a reference number.

OTI-08
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

OTI-09
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

  • If used, OTI09 through OTI10 will contain values from the original electronic transaction set generated by the sender.
OTI-10
143
Transaction Set Identifier Code
Required
Identifier (ID)
Min 3Max 3

Code uniquely identifying a Transaction Set

TED Loop
OptionalMax >1
TED
0700
Detail > OTI Loop > TED Loop > TED

Technical Error Description

RequiredMax use 1

To identify the error and, if feasible, the erroneous segment, or data element, or both

Example
TED-01
647
Application Error Condition Code
Required
Identifier (ID)

Code indicating application error condition

006
Duplicate
007
Missing Data
010
Total Out of Balance
011
Not Matching
012
Invalid Combination
024
Other Unlisted Reason
TED-02
3
Free-form Message
Required
String (AN)
Min 1Max 60

Free-form text

  • If used, TED02 will contain a generic description of the data in error (e.g., part number, date, reference number, etc.).
Usage notes

Error Code with brief description.

Error Code: See 824 Application Advice documentation under Programs & Requirements for explanation of error. http://edi.kroger.com

W = Warning
F = Fatal (document will not be processed must be resent)

TED-07
724
Copy of Bad Data Element
Optional
String (AN)
Min 1Max 99

This is a copy of the data element in error

TED-08
961
Data Element New Content
Optional
String (AN)
Min 1Max 99

New data which has replaced erroneous data

Usage notes

This is a free form note when used for the 889.

TED Loop end
OTI Loop end
SE
0900
Detail > 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

Detail 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

Duplicate Carton ID – EDI856

BGN*00*2013-08-16-17.07.50.40*20130816~
N1*FR*FRED MEYER*9*0079088090000~
PER*IC*EDI WEB SITE-HTTP://EDI.KROGER.COM/EDI~
N1*TO*STYLE ACCESSORIES*9*0868642680000~
OTI*TR*TN*0044333892*****1278*1278*856~
TED*006*3414F - DUPLICATE CARTON ID*****MAN02 = '008' IN HL/1376 (FIRST USE IN HL/1270)~

Invoice Total Amount does not balance to Detail – EDI810

BGN*00*729664*20130826~
N1*FR*CHEHALIS NON FOOD*9*0079088090000~
PER*IC*EDI WEB SITE-HTTP://EDI.KROGER.COM/EDI~
N1*TO**1*008286254~
OTI*TR*TN*260751*****729*7290001*810~
TED*011*0381F - Invoice Total Amount Does not Balance to Detail*****000002163.08*000002151.88~

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.