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

X12 824 Application Advice

X12 Release 4010

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
EDI samples
  • Load is already completed but received update after closed.
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/whirlpool/application-advice/01HAD5R7GFK166YFXK7N8YJ0RK
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
detail
OTI Loop
SE
090
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 to identify 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 to identify 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

Qualifier to designate 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

Qualifier to designate 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
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
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 sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate 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

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
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
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

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

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) 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
020
Heading > BGN

Beginning Segment

RequiredMax use 1

To indicate the beginning of a transaction set

Example
If Time Code (BGN-05) is present, then Time (BGN-04) is required
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 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

  • BGN02 is the transaction set reference number.
BGN-03
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BGN03 is the transaction set date.
BGN-04
337
Time
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)

  • BGN04 is the transaction set time.
BGN-05
623
Time Code
Optional
Identifier (ID)

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

  • BGN05 is the transaction set time qualifier.
ES
Eastern Standard Time
ET
Eastern Time
BGN-06
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

  • BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction.
BGN-07
640
Transaction Type Code
Optional
Identifier (ID)
Min 2Max 2

Code specifying the type of transaction

Heading end

Detail

OTI Loop
RequiredMax 999
OTI
010
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

TE
Transaction Set Accept with Error
TR
Transaction Set Reject
OTI-02
128
Reference Identification Qualifier
Optional
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.
CN
Carrier's Reference Number (PRO/Invoice)
OTI-03
127
Reference Identification
Optional
String (AN)
Min 1Max 30

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

This will be the value from the 214 field B10-01

OTI-06
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • OTI06 is the group date.
OTI-07
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

  • OTI07 is the group time.
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

REF
020
Detail > OTI Loop > REF

Reference Identification

OptionalMax use 12

To specify identifying information

  • 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.
Example
At least one of Reference Identification (REF-02) or Description (REF-03) is required
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

11
Account Number
SI
Shipper's Identifying Number for Shipment (SID)
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

If REF-01=“SI” , REF-02 will contain Penske Load Number, what was sent in the B102-02 from the 214. If the REF-01=“11”, REF-02 will contain the Penske customer ID

If available and sent on 214 then they will be returned.

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
RequiredMax >1
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)

Code indicating application error condition

007
Missing Data
011
Not Matching
848
Incorrect Data
999
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 Messages
Error # Error Message (TED-02)

10010 Load Id is empty.
10012 Load Id ... is not numeric.
10014 Carrier Code is empty.
10016 Customer Code is empty.
10018 Stop sequence number ... is not numeric.
10020 Load ID ... is not found in the system.
10022 Stop Number ;... does not exist for load ....
10024 Carrier code ... does not match carrier code for load ....
10026 There are no shipments being pickup up or delivered on load ..., stop ... for customer ....
10028 Status code ... is invalid or empty.
10030 Invalid Date format ....
10032 Load ... is not in Tendered, Tender Accepted or In Transit status.
10034 Load ... is in Completed status. Cannot update Delivery Arrival.
10036 Cannot update delivery before pickup (320 or 325).
10038 Load ... is in Tendered status, cannot do status updates.
10040 Cannot update delivery before pickup (310).
10042 Reason code is required for Delivery Departure when it is late for more than ... minutes.
10044 Reason code is required for Delivery Arrival when it is late for more than ... minutes.
10046 Reason code is required for Pickup Arrival when it is late for more than ... minutes.
10048 Reason code is required for Pickup Departure when it is late for more than ... minutes.
10050 Pickup Arrival submitted is later than Pickup Departure.
10052 Pickup Departure submitted for the first stop is earlier than Pickup Arrival or Pickup Arrival is missing.
10054 Pickup Departure submitted is earlier than Pickup Arrival.
10056 Cannot process status updates other than Pickup Arrival (X3) or Pickup Departure (AF) for the first stop.
10058 Arrival is before the previous stop departure/arrival or the previous stop departure/arrival is missing.
10060 Pickup Departure submitted is earlier than Pickup Arrival or Pickup Arrival is missing.
10062 Pickup departure must be after Arrival or, if arrival is missing, after previous stop departure/arrival.
10064 Delivery arrival is before the previous stop departure/arrival or the previous stop departure/arrival is missing.
10066 Either delivery arrival is missing or delivery departure is before delivery arrival.
10068 Invalid event to validate (not X3, AF, X1 or D1)

TED-03
721
Segment ID Code
Optional
Identifier (ID)
Min 2Max 3

Code defining the segment ID of the data segment in error (See Appendix A - Number 77)

TED-04
719
Segment Position in Transaction Set
Optional
Numeric (N0)
Min 1Max 6

The numerical count position of this data segment from the start of the transaction set: the transaction set header is count position 1

TED-05
722
Element Position in Segment
Optional
Numeric (N0)
Min 1Max 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

TED-06
725
Data Element Reference Number
Optional
Numeric (N0)
Min 1Max 4

Reference number used to locate the data element in the Data Element Dictionary

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

Load is already completed but received update after closed.

ISA^00^ ^00^ ^ZZ^SENDER ^ZZ^RECEIVER ^231101^0203^U^00401^000000001^0^T^>
GS^AG^SENDERGS^RECEIVERGS^20231101^020335^000000001^X^004010
ST^824^24980001
BGN^00^00000000001^20100414^1604^ET
OTI^TR^CN^123123123^^^20100414^1502^35337^353370001^214
REF^11^WHRLLP-CT
REF^SI^LOADNBR
TED^848^Load LOADNBR is in Completed status. Cannot update Delivery
TED^999^Arrival.
SE^8^24980001
GE^1^000000001
IEA^1^000000001

Statuses received out of sequence.

ISA^00^ ^00^ ^ZZ^PenskeWPCT ^02^SCAC ^100414^1257^U^00400^000002562^0^T^;
GS^AG^PSKLWP^SCAC^20100414^1257^2481^X^004010
ST^824^24810001
BGN^00^00000000001^20100414^1257^ET
OTI^TR^CN^123123123^^^20100413^1413^35330^353300001^214
REF^11^WHRLLP-CT
REF^SI^LOADNBR
TED^848^Either delivery arrival is missing or delivery departure is
TED^999^before delivery arrival
SE^8^24810001
GE^1^2481
IEA^1^000002562

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.