X12 861 Receiving Advice
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
- None included
Interchange Control Header
To start and identify an interchange of one 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 sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier.
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 sender or the data in the interchange. The type of information is set by the Security Information Qualifier.
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 number 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.
- 00304
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1993
This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.
Code sent by the sender to request an interchange acknowledgment.
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test or production.
- P
- Production Data
- T
- Test Data
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.
- 003040
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1993
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
- X12.12 Receiving Advice
Beginning Segment for Receiving Advice or Acceptance Certificate
To indicate the beginning of a receiving advice or acceptance certificate transaction set and to 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.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
Shipment identification
Date (YYMMDD).
- BRA02 is the date that the receiving advice transaction set is created.
Code identifying purpose of transaction set.
- 00
- Original
Date/Time Reference
To specify pertinent dates and times
Name
To identify a party by type of organization, name and code
Code identifying an organizational entity, a physical location, or an individual
- VN
- Vendor Code
Code designating the system/method of code structure used for Identification Code (67).
- 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.
TMS assigned vendor code.
Detail
Receiving Conditions
To report receiving conditions and specify contested quantities
Number of Units Received or Accepted
Quantity received by the warehouse.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PC
- Piece
Number of units contested because of physical condition or status of units.
- RCD06 through RCD20 provide for five (5) different quantities whose condition upon receipt is under question.
Damaged quantity.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PC
- Piece
Code designating physical condition or status of units received in a specific shipment.
TMS uses “01” to indicate damaged quantity.
Number of units contested because of physical condition or status of units.
Shortage quantity.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PC
- Piece
Code designating physical condition or status of units received in a specific shipment.
TMS uses “02” to indicate shortage quantity.
Number of units contested because of physical condition or status of units.
Overage quantity.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PC
- Piece
Code designating physical condition or status of units received in a specific shipment.
TMS uses “03” to indicate overage quantity.
Number of units contested because of physical condition or status of units.
Rejected quantity.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PC
- Piece
Item Detail (Shipment)
To specify line item detail relative to shipment
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.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- BP
- Part Number
Purchase Order Reference
To provide reference to a specific purchase order
Identifying number for Purchase Order assigned by the orderer/purchaser.
Customer purchase order number.
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- The number of line items (CTT01) is the accumulation of the number of RCD segments. If used, hash total (CTT02) is the sum of the value of quantities received (RCD02) for each RCD segment.
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 one or more functional groups and interchange-related control segments
A count of the number of functional groups included in a transmission.
This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.
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.