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

X12 824 Application Advice

X12 Release 3010

This standard provides the format and establishes the data contents of the Application Advice Transaction Set (824) within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides 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 accomodate 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 acknowledgement sent in response to a purchase order).

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • sample 1
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/ford/application-advice/01HRWR6PJG4ECX5JMNZMBA3V9V
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
detail
OTI Loop
OTI
010
Original Transaction Identification
Max use 1
Required
REF
020
Reference Numbers
Max use 12
Optional
TED Loop
SE
090
Transaction Set Trailer
Max use 1
Required
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Max use 1
Required
GS

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
Acceptance/Rejection Advice (999) and Application Advice (824)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 12

Code identifying party sending transmission. Codes agreed to by trading partners.

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 12

Code identifying party receiving transmission. Codes agreed to by trading partners.

GS-04
29
Group Date
Required
Date (DT)
YYMMDD format

Date sender generated a functional group of transaction sets.

GS-05
30
Group Time
Required
Time (TM)
HHMM format

Time (HHMM) when the sender generated a functional group of transaction sets (local time at sender's location).

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 used in conjunction with Data Element 480 to identify the issuer of the standard.

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
Identifier (ID)

Code indicating the version, release, subrelease and industry identifier of the EDI standard being used. Positions 1-3, version number; positions 4-6, release and subrelease level of version; positions 7-12, industry or trade association identifier (optionally assigned by user).

003010
Draft Standards Approved By ASC X12 Through June 1990.

Heading

ST
010
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 intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set).
824
X12.44 Application Advice
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number assigned by the originator for a transaction set.

BGN
020
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.

  • If BGN05 is used, BGN04 is required.
00
Original
12
Test
BGN-02
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

  • BGN02 is the Transaction Set Reference Number.
Required
Date (DT)
YYMMDD format

Date (YYMMDD).

  • BGN03 is the Transaction Set Date.
Optional
Time (TM)
HHMM format

Time expressed in 24-hour clock time (HHMM, time range: 0000 though 2359).

  • BGN04 is the Transaction Set Time.
Heading end

Detail

OTI Loop
RequiredMax 10000
OTI
010
Detail > OTI Loop > OTI

Original Transaction Identification

RequiredMax use 1

To identify the edited transaction set, the level at which the results of the edit are reported, and to indicate the accepted, rejected or accepted with change edit result.

  • A segment appearing in Table 1 applies to the entire transaction set, and this may be overridden for the duration of a specific occurrence of a loop in Table 2 when the same segment with a changed value is present in that occurrence of the loop.
Example
OTI-01
110
Application Acknowledgment Code
Required
Identifier (ID)
Min 1Max 2

Code indicating the application system edit results of the business data.

OTI-02
128
Reference Number Qualifier
Required
Identifier (ID)
Min 2Max 2

Code qualifying the Reference Number.

  • OTI02 contains the qualifier identifying the business transaction from the original business application, and OTI03 will contain the original business application identification.
OTI-03
127
Reference Number
Required
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

  • If OTI09 is present, the OTI08 is required.
OTI-10
143
Transaction Set Identifier Code
Optional
Identifier (ID)
Min 3Max 3

Code uniquely identifying a Transaction Set.

REF
020
Detail > OTI Loop > REF

Reference Numbers

OptionalMax use 12

To specify identifying numbers.

  • REF segments can be used as needed to further identify the original transaction set.
Example
REF-01
128
Reference Number Qualifier
Required
Identifier (ID)
Min 2Max 2

Code qualifying the Reference Number.

REF-02
127
Reference Number
Optional
String (AN)
Min 1Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

  • Either REF02 or REF03 is required.
REF-03
352
Description
Optional
String (AN)
Min 1Max 80

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

TED Loop
OptionalMax 10000
TED
070
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)
Min 1Max 3

Code indicating application error condition.

  • If used, TED02 will contain a generic description of the data in error (e.g., Part Number, Date, Reference Number, etc.).
TED-02
3
Free Form Message
Optional
String (AN)
Min 1Max 60

Free-form text.

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 Loop end
OTI Loop end
SE
090
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 6

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

EDI Samples

sample 1

ISA~00~ ~00~ ~ZZ~F159B ~ZZ~BTCXA ~240229~1541~U~00200~000016138~0~P~<
GS~AG~AF1CC~BTCXA~240229~1536~000016138~X~003010
ST~824~0001
BGN~00~000000000000000000000000000001~240229~1535
OTI~IR~PK~SHP3024020~~~~~~~856
REF~IT~33021~FCSD CUSTOMER
REF~RE~YFZBJ8~FCSD 'Y' ORDER NUMBER
TED~006~DUPLICATE~~~~~YFZBJ8/BTCXA/33021/VNZ6Z99501A42G /SHP302/000000003
SE~7~0001
GE~1~000016138
IEA~00001~000016138

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.