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
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
Code identifying party sending transmission.
Code identifying party receiving transmission.
Date sender generated a functional group of transaction sets.
Time (HHMM) expressed in 24-hour clock time when the sender generated a functional group of transaction sets (local time at sender's location).
(Time range: 0000 through 2359.)
Assigned number originated and maintained by the sender.
Code used in conjunction with the version data element to identify the issuer of the standard.
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
The Version Code is used in conjunction with the Functional Identifier to specify an exact version of an EBDI standard. Format of the version is: Positions Content
1 - 3 Major Version Number
4 - 6 Release Level of Version
7 - 12 Industry or Trade Assoc. ID (Optionally assigned by user)
- 002001
- Draft Standard Approved by ASC X12 Through February 1987.
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set.
- 861
- X12.12 Receiving Advice
Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)
Beginning Segment (Receiving Advice)
To indicate the beginning of a receiving advice transaction set and to transmit identifying number and date.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
A number assigned by Ford to uniquely identify the transaction set.
Date (YYMMDD). Also see: Date Qualifier (432).
Transaction creation date.
Code identifying purpose of transmitted set.
- 00
- Original
Reference Numbers
To transmit identifying numbers associated with the named party
Used to transmit shipment identification ASN and/or packing slip number.
Code qualifying the Reference Number.
- PK
- Packing List Number
- SI
- Shipper's Identifying Number for Shipment (SID)
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Ford will send the supplier generated ASN number and/or packing slip number for the referenced shipment (BSN02). Ford will only provide up to the first 11 characters.
Date/Time Reference
To specify pertinent dates and times
Normally used to specify the receiving date. This segment will be used to specify the shipped date if return is indicated.
Name
To identify a party by type of organization, name and code
Two occurrences of the N1 are required. One for the "ship from" location (N101 - "SF") and one for the "ship to" (N101 - "ST"). If a return is indicated, the "SF" will be Ford and "ST" will be the supplier.
Code identifying the type of party being defined.
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer
Code identifying one of the parties in the transaction. See Identification Code Qualifier (66).
Will contain Ford assigned code.
Detail
Receiving Conditions
To report receiving conditions and specify contested quantities
In each RCD loop Ford will send detail level information for all receipts, discrepancies and Assembly Division returns.
RCD02 will contain the quantity received. RCD04 will contain the quantity returned. (Return quantity is used by Assembly Division only.)
RCD08 will contain one of the following codes:
- "08" - Return, reject, do not adjust cum.
- "12" - Return, overshipment, adjust cum. (The cum adjustment quantity will be specified in the RCD09 - RCD11 discrepancy area with a RCD11 code of "11" and the adjust cum quantity in RCD09.)
- "13" - Quantity discrepancy, do not adjust cum.
Code identifying the basic unit measurement.
Will contain the same unit of measure as Ford Material Release (830).
Number of units returned.
Used by Assembly Division to indicate return quantity.
Code identifying the basic unit measurement.
Will contain the same unit of measure as Ford Material Release (830).
Number of units contested because of physical condition or status of units.
Will contain difference between SN102 and RCD02.
Code identifying the basic unit measurement.
Will contain same unit of measure as Ford Material Release (830).
Code designating physical condition or status of units received in a specific shipment.
- 08
- Rejected
- 12
- 13
Number of units contested because of physical condition or status of units.
When used will contain cum adjustment quantity.
Code identifying the basic unit measurement.
Will contain same unit of measure as Ford Material Release (830).
Code designating physical condition or status of units received in a specific shipment.
- 11
- Cum Adjustment Quantity
Item Detail (Shipment)
To specify line item detail relative to shipment
Used to show ASN quantity for the part referenced in the LIN segment.
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set. Also see: Unit of Measurement Code (355).
For Assembly Division, received quantity, otherwise ASN quantity.
Code identifying the basic unit measurement.
Will contain same unit of measure as Ford Material Release (830).
Item Identification Detail
To specify basic item identification data.
Use for Ford part number. Ford part number may consist of a prefix, base, suffix and control code. Any of these, except the base, may or may not be present. The portions of the part number are delimited by spaces.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- BP
- Buyer's Part Number
Identifying number for a product or service.
This field will contain the Ford part number.
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning and ending (SE) segment)
Total number of segments included in a transaction set including ST and SE segments.
Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)
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.
Assigned number originated and maintained by the sender.
sample 1
GS~RC~AP10A~BTCXA~231222~1706~000011819~X~002001
ST~861~0001
BRA~2023-12-22-17.06.33.022717~231222~00
REF~PK~342779700
REF~SI~0007412116
DTM~050~231222
N1~ST~~92~AP10A
N1~SF~~92~BTCXA
RCD~~24~EA
SN1~~24~EA
LIN~~BP~AMPC3J 17B820 AC
CTT~1~24
SE~12~0001
GE~1~000011819
IEA~00001~000011819
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.