X12 861 Receiving Advice/Acceptance Certificate
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.
- Segment
- * Element
- > Component
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
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
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
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
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- RC
- Receiving Advice/Acceptance Certificate (861)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
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
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
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
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
Beginning Segment for Receiving Advice or Acceptance Certificate
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.
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.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date expressed as CCYYMMDD
- BRA02 is the date that the receiving advice transaction set is created.
Code identifying purpose of transaction set
- 00
- Original
Reference Identification
To specify identifying information
This segment will contain the ship id from the 856 ASN
Code qualifying the Reference Identification
- SI
- Shipper's Identifying Number for Shipment (SID)
Process
To specify pertinent dates and times
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.
Code specifying type of date or time, or both date and time
- 009
- Process
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)
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
Received
To specify pertinent dates and times
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.
Code specifying type of date or time, or both date and time
- 050
- Received
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)
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
Name
To identify a party by type of organization, name, and code
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
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
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
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.
Name
To identify a party by type of organization, name, and code
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
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
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
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.
Name
To identify a party by type of organization, name, and code
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
Code identifying an organizational entity, a physical location, property or an individual
- SU
- Supplier/Manufacturer
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
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.
Detail
Receiving Conditions
To report receiving conditions and specify contested quantities
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).
Number of Units Received or Accepted
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.
Item Detail (Shipment)
To specify line-item detail relative to shipment
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.
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Item Identification
To specify basic item identification data
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
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
Identifying number for a product or service
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
Identifying number for a product or service
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
Reference Identification
To specify identifying information
This optional segment might contain the pack list number from the line items on the shipment as sent in the ASN data.
Code qualifying the Reference Identification
- PK
- Packing List Number
Summary
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample from Deere
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.