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

X12 824 Application Advice

X12 Release 4030

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

Delimiters
  • ~ Segment
  • * Element
  • > Component
  • ^ Repetition
EDI samples
  • FOR REJECTED 855
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/albertsons/application-advice/01GWA2GF05H7K86YBQCXDHQH7E
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

00403
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999
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 Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
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

004030
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999

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

Usage notes

BGN340202221*20130323~

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

Code identifying purpose of transaction set

00
Original

ORIGINAL (from TS810 or TS855)

12
Not Processed
34
Payment Declined

Payment Declined from TS 880

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

Vendor's invoice number or foreign PO number.

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.
Usage notes

BGN03 is the date the transaction set was generated in the sender's application system.

VENDOR REFERENCE DATE.

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

Name

RequiredMax use 1

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

Usage notes

N1FRSAFEWAY INC90091372091700~

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
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

FR
Message From
Optional
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)

9
D-U-N-S+4, D-U-N-S Number with Four Character Suffix
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.
Usage notes

009127209XXXX = SAFEWAY DUNS #
DUNS Listing: http://suppliers.safeway.com/pdf/pdf_us/DunsListing-USA.pdf

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

Usage notes

PERAAECR/EDI DEPARTMENTTE925-467-3197EMECREDI@SAFEWAY.COM~

Example
If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
PER-01
366
Contact Function Code
Required
Identifier (ID)

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

AA
Authorized Representative
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

(SAFEWAY) ECR/EDI DEPARTMENT

PER-03
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

TE
Telephone
PER-04
364
Communication Number
Optional
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

Usage notes

925-467-3197

PER-05
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

EM
Electronic Mail
PER-06
364
Communication Number
Optional
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

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

Name

RequiredMax use 1

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

Usage notes

N1TOXYZ SUPPLIER CORP91234567890000~

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
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

TO
Message To
Optional
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)

9
D-U-N-S+4, D-U-N-S Number with Four Character Suffix
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.
Usage notes

009127209XXXX = SAFEWAY DUNS #
DUNS Listing: http://suppliers.safeway.com/pdf/pdf_us/DunsListing-USA.pdf

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

Usage notes

PERAAECR/EDI DEPARTMENTTE925-467-3197EMECREDI@SAFEWAY.COM~

Example
If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
PER-01
366
Contact Function Code
Required
Identifier (ID)

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

AA
Authorized Representative
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

(SAFEWAY) ECR/EDI DEPARTMENT

PER-03
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

TE
Telephone
PER-04
364
Communication Number
Optional
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

Usage notes

925-467-3197

PER-05
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

EM
Electronic Mail
PER-06
364
Communication Number
Optional
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

Usage notes
N1 Message To end
N1 Payee
OptionalMax >1
Variants (all may be used)
Message FromMessage To
N1
0300
Heading > Payee > N1

Name

RequiredMax use 1

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

Usage notes

N1PEXYZ SUPPLIER CORP91234567890000~ (for invoice only)

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
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

PE
Payee
Optional
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)

9
D-U-N-S+4, D-U-N-S Number with Four Character Suffix
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.
Usage notes

009127209XXXX = SAFEWAY DUNS #
DUNS Listing: http://suppliers.safeway.com/pdf/pdf_us/DunsListing-USA.pdf

PER
0800
Heading > Payee > PER

Administrative Communications Contact

OptionalMax use 3

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

Usage notes

PERAAECR/EDI DEPARTMENTTE925-467-3197EMECREDI@SAFEWAY.COM~

Example
If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
PER-01
366
Contact Function Code
Required
Identifier (ID)

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

AA
Authorized Representative
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

(SAFEWAY) ECR/EDI DEPARTMENT

PER-03
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

TE
Telephone
PER-04
364
Communication Number
Optional
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

Usage notes

925-467-3197

PER-05
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

EM
Electronic Mail
PER-06
364
Communication Number
Optional
String (AN)
Min 1Max 256

Complete communications number including country or area code when applicable

Usage notes
N1 Payee 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.
Usage notes

OTITRTN0202221777888999980197211932013032109305520055200010810~

Example
If Transaction Set Control Number (OTI-09) is present, then Group Control Number (OTI-08) is required
OTI-01
110
Application Acknowledgment Code
Required
Identifier (ID)

Code indicating the application system edit results of the business data

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.
Usage notes

OTI02 identifies error transaction set's key field. For example, TransactionSet 810's key field is invoice number and Transaction Set 850's key field is purchase order number.

TN
Transaction Reference Number

The actual business application identification number for the transaction will be inOTI03, e.g. purchase order number, invoice number, ship notice number, etc.

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

VENDOR’S INVOICE or FPO NUMBER.

OTI-04
142
Application Sender's Code
Optional
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

  • If used, OTI04 through OTI08 will contain values from the original electronic functional group generated by the sender.
Usage notes

OTI04 contains GS02 data contents from the original functional group generated by the sender.

OTI-05
124
Application Receiver's Code
Optional
String (AN)
Min 2Max 15

Code identifying party receiving transmission; codes agreed to by trading partners

Usage notes

OTI05 contains GS03 data contents from the original functional group generated by the sender.

Optional
Date (DT)
CCYYMMDD format

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

  • OTI06 is the group date.
Usage notes

OTI06 contains GS04 data contents from the original functional group generated by the sender.

Optional
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)

  • OTI07 is the group time.
Usage notes

OTI07 contains GS05 data contents from the original functional group generated by the sender.

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

Assigned number originated and maintained by the sender

Usage notes

OTI08 contains GS06 data contents from the original functional group generated by the sender.

OTI-09
329
Transaction Set Control Number
Optional
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.
Usage notes

OTI09 contains ST02 data contents from the original transaction set header generated by the sender.

OTI-10
143
Transaction Set Identifier Code
Optional
Identifier (ID)

Code uniquely identifying a Transaction Set

Usage notes

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

810
Invoice
855
Purchase Order Acknowledgment
880
Grocery Products Invoice
DTM
0300
Detail > OTI Loop > DTM

Invoice Date

OptionalMax use 2

To specify pertinent dates and times

  • The DTM segment allows for the provision of date, time, or date and time information required to uniquely identify the original transaction set.
Usage notes

DTM00320130319~

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

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

Usage notes

003 = INVOICE DATE (from TS810 or TS880)

003
Invoice
Optional
Date (DT)
CCYYMMDD format

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

Usage notes

INVOICE DATE

DTM
0300
Detail > OTI Loop > DTM

Process Date

OptionalMax use 2

To specify pertinent dates and times

  • The DTM segment allows for the provision of date, time, or date and time information required to uniquely identify the original transaction set.
Usage notes

DTM00920130319~

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

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

Usage notes

009 = PO DATE (from TS855)

009
Process
Optional
Date (DT)
CCYYMMDD format

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

Usage notes

PURCHASE ORDER DATE

DTM
0300
Detail > OTI Loop > DTM

Settlement Date as Specified by the Originator

OptionalMax use 2

To specify pertinent dates and times

  • The DTM segment allows for the provision of date, time, or date and time information required to uniquely identify the original transaction set.
Usage notes

DTM04420130319~

Example
Variants (all may be used)
DTMInvoice DateDTMProcess Date
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

Usage notes

044 = SETTLEMENT DATE (from TS810)

044
Settlement Date as Specified by the Originator
Optional
Date (DT)
CCYYMMDD format

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

Usage notes

PRICE CHANGE EFFECTIVE DATE

AMT
0500
Detail > OTI Loop > AMT

Monetary Amount

OptionalMax use >1

To indicate the total monetary amount

  • The AMT segment should be utilized if monetary amount information is important to the unique identification of the original transaction set.
Usage notes

AMTTP22234.8~

Example
AMT-01
522
Amount Qualifier Code
Optional
Identifier (ID)

Code to qualify amount

TP
Total payment amount
AMT-02
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount

Usage notes

INVOICE AMT SENT ON ORIG TS810 or TS880
0.0 IF ORIGINAL WAS TS855.

QTY
0600
Detail > OTI Loop > QTY

Quantity

OptionalMax use >1

To specify quantity information

  • The QTY segment should be utilized if quantity information is important to the unique identification of the original transaction set.
Usage notes

QTY5360~

Example
QTY-01
673
Quantity Qualifier
Required
Identifier (ID)

Code specifying the type of quantity

53
Original payment item count.
QTY-02
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

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

Usage notes

TED012INVALID SHIP-TO OR INVALID PO NUMBER*****SHIP-TO DUNS SUFFIX/PO# (1922/912938)~

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

Code indicating application error condition

008
Out of Range

OUT OF RANGE (PO number TS855)

009
Invalid Date

INVALID DATE (from TS880)

010
Total Out of Balance

TOTAL OUT OF BALANCE (from TS880)

012
Invalid Combination

INVALID COMBINATION (from TS880)

024
Other Unlisted Reason

OTHER UNLISTED REASON (from TS880 or TS855)

813
Missing or Invalid Payee Name and Address

MISSING or INVALID NAME/ADDRESS (from TS880)

MF
Missing or Invalid Internal Vendor Number

MISSING / INVALID VENDOR NUMBER

MG
Missing or Invalid U.P.C. Code

MISSING OR INVALID UPC

MH
Missing or Invalid DUNS Number

MISSING OR INVALID DUNS NUMBER

P
Missing or Invalid Item Quantity

MISSING OR INVALIDITEM QUANTITY

Q
Missing or Invalid Item Identification

MISSING OR INVALID ITEM IDENTITY

TED-02
3
Free Form Message
Optional
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

SAFEWAY GENERATED ERROR MESSAGE

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

This is a copy of the data element in error

Usage notes

ADD’L SAFEWAY GENERATED ERROR MESSAGE

NTE
0800
Detail > OTI Loop > TED Loop > NTE

Note/Special Instruction

OptionalMax use 100

To transmit information in a free-form format, if necessary, for comment or special instruction

Usage notes

NTEGENCONTACT BROKER OR ORDER ENTRY DEPARTMENT~

NTEGENPLEASE CORRECT INVOICE(S) & RETRANSMIT EDI. PAPER INVOICES WILL NOT BE ACCEPTED.~

Example
NTE-01
363
Note Reference Code
Optional
Identifier (ID)

Code identifying the functional area or purpose for which the note applies

GEN
Entire Transaction Set
NTE-02
352
Description
Required
String (AN)
Min 1Max 80

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

Usage notes

SAFEWAY MESSAGE

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

FOR REJECTED 855

ST*824*00011001~
BGN*12*326654*20140211~
N1*FR*SAFEWAY INC*9*0091372091700~
N1*TO*XXX Foods*9*0019990350000~
PER*AA*ECR/EDI DEPARTMENT*TE*925-467-3197*EM*ECREDI@SAFEWAY.COM~
OTI*TR*TN*326654*7162256XXX*8019721193*20140210*1900*16489*164890001*855~
DTM*009*20140210~
AMT**0~
TED*024*075928367321 ORDER UNIT OF MEASURE NOT 'CA', 'EA' OR 'PL'*****XX~
NTE*GEN*ORDER UNIT OF MEASURE NOT 'CA', 'EA' OR 'PL'~
SE*11*00011001~
ST*824*00011002~
BGN*12*326658*20040211~
N1*FR*SAFEWAY INC*9*0091372091700~
N1*TO*XXX Foods*9*0099990350000~
PER*AA*ECR/EDI DEPARTMENT*TE*925-467-3197*EM*ECREDI@SAFEWAY.COM~
OTI*TR*TN*326658*7162256XXX*8019721193*20140210*1900*16489*164890005*855~
DTM*009*20140210~
AMT**0~
TED*008*326658 PO NUMBER NOT IN ASSIGNED RANGE~
NTE*GEN*PO NUMBER NOT IN ASSIGNED RANGE – ORDER IS REJECTED~
TED*024*000099999999 ITEM QUANTITY NOT NUMERIC*****9999R~
NTE*GEN*ITEM QUANTITY NOT NUMERIC -- ITEM IS REJECTED~
TED*024*004470009219 UPC QUALIFIER NOT 'UA'*****AA~
NTE*GEN*UPC QUALIFIER NOT 'UA' – ITEM IS REJECTED~
SE*15*00011002~

FOR REJECTED INVOICE

ST*824*00917001~
BGN*34*0202221*20030323~
N1*FR*SAFEWAY INC*9*0091372091700~
N1*TO*XYZ SUPPLIER*9*1234567890000~
N1*PE*XYZ SUPPLIER*9*1234567890000~
PER*AA*ECR/EDI DEPARTMENT*TE*925-467-3197*EM*ECREDI@SAFEWAY.COM~
OTI*TR*TN*0202221*7778889999*8019721193*20030321*0930*5520*055200010*810~
DTM*003*20130319~
AMT*TP*22234.8~
QTY*53*60~
TED*012*INVALID SHIP-TO OR INVALID PO NUMBER*****SHIP-TO DUNS SUFFIX/PO # (1922/912938)~
NTE*GEN*CONTACT BROKER OR ORDER ENTRY DEPARTMENT~
NTE*GEN*PLEASE CORRECT INVOICE(S) & RETRANSMIT EDI. PAPER INVOICES WILL NOT BE ACCEPTED.~
SE*14*00917001~

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.