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

X12 861 Receiving Advice/Acceptance Certificate

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Receiving Advice/Acceptance Certificate Transaction Set (861) for use within the context of an Electronic Data Interchange (EDI) environment.
The transaction set can be used to provide for customary and established business and industry practice relative to the notification of receipt or formal acceptance of goods and services.

Delimiters
  • Segment
  • * Element
  • > Component
EDI sample
  • Sample from Deere
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/john-deere/receiving-adviceacceptance-certificate/01H9K55QYFFT1VQV3E5EEH0RPE
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
010
Transaction Set Header
Max use 1
Required
BRA
020
Beginning Segment for Receiving Advice or Acceptance Certificate
Max use 1
Required
REF
050
Reference Identification
Max use 1
Optional
DTM
070
Process
Max use 1
Required
DTM
070
Received
Max use 1
Required
Ship From
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

RC
Receiving Advice/Acceptance Certificate (861)
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).
861
Receiving Advice/Acceptance Certificate
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

BRA
020
Heading > BRA

Beginning Segment for Receiving Advice or Acceptance Certificate

RequiredMax use 1

To indicate the beginning of a Receiving Advice or Acceptance Certificate Transaction Set and transmit an identifying number, date, and time

  • This transaction set is a Receiving Advice unless BRA04 contains a value of "8". When BRA04 contains a value of "8", the transaction set is an Acceptance Certificate and the units received is the units accepted.
Usage notes

The beginning segment contains the reference the system date (Julian date and system time stamp) associated ASN for which the transaction is created. The Receiving Advice or Acceptance Certificate Type Code (BRA04) is a code to inform suppliers if the action to create this discrepancy information was created at original receipt time, or if it is 'post receipt' action, that is noticed later in the manufacturing and consumption process.

Example
BRA-01
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

BRA-02
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BRA02 is the date that the receiving advice transaction set is created.
BRA-03
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
BRA-04
962
Receiving Advice or Acceptance Certificate Type Code
Required
Identifier (ID)

Code specifying type of receiving advice

1
Receiving Dock Advice
2
Post Receipt Advice
REF
050
Heading > REF

Reference Identification

OptionalMax use >1

To specify identifying information

Usage notes

This segment will contain the ship id from the 856 ASN

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

SI
Shipper's Identifying Number for Shipment (SID)
REF-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

DTM
070
Heading > DTM

Process

RequiredMax use 1

To specify pertinent dates and times

Usage notes

To help the supplier identify the timing of the transaction which is in error, the date and time of receipt is provided, and the date and time of this EDI transaction may be provided as well.

Example
Variants (all may be used)
DTMReceived
If Time Code (DTM-04) is present, then Time (DTM-03) is required
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

009
Process
DTM-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

DTM-03
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)

DTM-04
623
Time Code
Optional
Identifier (ID)
Min 2Max 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

DTM
070
Heading > DTM

Received

RequiredMax use 1

To specify pertinent dates and times

Usage notes

To help the supplier identify the timing of the transaction which is in error, the date and time of receipt is provided, and the date and time of this EDI transaction may be provided as well.

Example
Variants (all may be used)
DTMProcess
If Time Code (DTM-04) is present, then Time (DTM-03) is required
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

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

050
Received
DTM-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

DTM-03
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)

DTM-04
623
Time Code
Optional
Identifier (ID)
Min 2Max 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

N1 Ship From
OptionalMax 1
Variants (all may be used)
Ship ToSupplier/Manufacturer
N1
130
Heading > Ship From > N1

Name

RequiredMax use 1

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

Usage notes

If an N1 segment with an indicator "ST", "SU" or "SF" is contained in the ASN, the same data is returned in this transaction. There will be an associated DUNS number or another Deere unique number to cross reference all the address information

Example
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

SF
Ship From
N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

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

1
D-U-N-S Number, Dun & Bradstreet
92
Assigned by Buyer or Buyer's Agent
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.
N1 Ship From end
N1 Ship To
OptionalMax 1
Variants (all may be used)
Ship FromSupplier/Manufacturer
N1
130
Heading > Ship To > N1

Name

RequiredMax use 1

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

Usage notes

If an N1 segment with an indicator "ST", "SU" or "SF" is contained in the ASN, the same data is returned in this transaction. There will be an associated DUNS number or another Deere unique number to cross reference all the address information

Example
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

ST
Ship To
N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

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

1
D-U-N-S Number, Dun & Bradstreet
92
Assigned by Buyer or Buyer's Agent
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.
N1 Ship To end
N1 Supplier/Manufacturer
OptionalMax 1
Variants (all may be used)
Ship FromShip To
N1
130
Heading > Supplier/Manufacturer > N1

Name

RequiredMax use 1

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

Usage notes

If an N1 segment with an indicator "ST", "SU" or "SF" is contained in the ASN, the same data is returned in this transaction. There will be an associated DUNS number or another Deere unique number to cross reference all the address information

Example
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

SU
Supplier/Manufacturer
N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

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

1
D-U-N-S Number, Dun & Bradstreet
92
Assigned by Buyer or Buyer's Agent
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.
N1 Supplier/Manufacturer end
Heading end

Detail

RCD Loop
OptionalMax 200000
RCD
010
Detail > RCD Loop > RCD

Receiving Conditions

RequiredMax use 1

To report receiving conditions and specify contested quantities

Usage notes

This segment specifies information regarding receipt quantity and unit of measure, along with a field for the quantity in question and a code to inform the nature of the problem condition (short, over, ok , or no ship notice available).

Example
If either Quantity in Question (RCD-06), Composite Unit of Measure (RCD-07) or Receiving Condition Code (RCD-08) are present, then the others are required
RCD-02
663
Quantity Units Received or Accepted
Optional
Decimal number (R)
Min 1Max 9

Number of Units Received or Accepted

RCD-03
C001
Composite Unit of Measure
OptionalMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-01
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

Usage notes

(Example: PC=pieces)

RCD-06
667
Quantity in Question
Optional
Decimal number (R)
Min 1Max 9

Number of units contested because of physical condition or status of units

  • RCD06 through RCD20 provide for five different quantities whose condition upon receipt is under question.
RCD-07
C001
Composite Unit of Measure
OptionalMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-01
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

Usage notes

(Example: PC=pieces)

RCD-08
412
Receiving Condition Code
Optional
Identifier (ID)

Code designating physical condition or status of units received in a specific shipment

02
Quantity Short
03
Quantity Over
07
Good Condition
14
Quantity Received and Processed with No Matching Ship Notice/Manifest
SN1
020
Detail > RCD Loop > SN1

Item Detail (Shipment)

OptionalMax use 1

To specify line-item detail relative to shipment

Usage notes

The quantity shipped as sent on the ASN (if available) is provided for information. The ship quantity is able to be calculated from the RCD segment as well, depending on the condition. If the quantity in the SN1 of the ASN(856) is less than the sum of the CLD quantities, Deere assumes the SN1 quantity is the correct ship quantity.

Example
SN1-02
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

SN1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)
Min 2Max 2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

  • SN103 defines the unit of measurement for both SN102 and SN104.
Usage notes

(Example: PC=pieces)

LIN
040
Detail > RCD Loop > LIN

Item Identification

OptionalMax use 100

To specify basic item identification data

Usage notes

This segment contains the Deere material number being receipted and as sent in the ship notice data. Some other information related to the part (see the code definitions in the guideline) may be included as appropriate. The Deere PO number will also be included on this segment

Example
If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
BP
Buyer's Part Number
PO
Purchase Order Number
RC
Returnable Container Number
VP
Vendor's (Seller's) Part Number
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-04
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

BP
Buyer's Part Number
PO
Purchase Order Number
RC
Returnable Container Number
VP
Vendor's (Seller's) Part Number
LIN-05
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-06
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

BP
Buyer's Part Number
PO
Purchase Order Number
RC
Returnable Container Number
VP
Vendor's (Seller's) Part Number
LIN-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

REF
070
Detail > RCD Loop > REF

Reference Identification

OptionalMax use 12

To specify identifying information

Usage notes

This optional segment might contain the pack list number from the line items on the shipment as sent in the ASN data.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

PK
Packing List Number
REF-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

RCD Loop end
Detail end

Summary

SE
020
Summary > 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

Summary 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

Sample from Deere

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231106*1252*U*00401*000000001*0*T*>
GS*RC*SENDERGS*RECEIVERGS*20231106*125239*000000001*X*004010
ST*861*0012
BRA*980629180557*19980629*00*1
REF*SI*159833
DTM*009*19980629*1708*CS
DTM*050*19980629*1509*CS
N1*SF**1*004465100
N1*ST**1*025423045
RCD**3765*PC***21*PC*03
SN1**3744*PC
LIN**BP*JD7445*PO*638607BO
REF*PK*6199
RCD******21*PC*02
SN1**21*PC
LIN**BP*JD7444*PO*638607BO*VP*RC0415
REF*PK*6212
SE*16*0012
GE*1*000000001
IEA*1*000000001

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.