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

X12 861 Receiving Advice

X12 Release 2001

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 1
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/ford/receiving-advice/01HRWS2VMXSGDMC76BR8YG3HYE
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
02
Transaction Set Header
Max use 1
Required
BRA
03
Beginning Segment (Receiving Advice)
Max use 1
Required
REF
06
Reference Numbers
Max use 2
Required
DTM
08
Date/Time Reference
Max use 1
Required
N1 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Max use 1
Required
GS

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
Required
Identifier (ID)

Code identifying a group of application related Transaction Sets.

RC
Receiving Advice
GS-02
142
Application Sender's Code
Required
Identifier (ID)
Min 2Max 12

Code identifying party sending transmission.

GS-03
124
Application Receiver's Code
Required
Identifier (ID)
Min 2Max 12

Code identifying party receiving transmission.

GS-04
29
Data Interchange Date
Required
Date (DT)
YYMMDD format

Date sender generated a functional group of transaction sets.

GS-05
30
Data Interchange Time
Required
Time (TM)
HHMM format

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

GS-06
28
Data Interchange 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 the version data element to identify the issuer of the standard.

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version/Release/ Industry ID
Required
Identifier (ID)

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

ST
02
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
Required
Identifier (ID)

Code uniquely identifying a Transaction Set.

861
X12.12 Receiving Advice
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)

BRA
03
Heading > BRA

Beginning Segment (Receiving Advice)

RequiredMax use 1

To indicate the beginning of a receiving advice transaction set and to transmit identifying number and date.

Example
BRA-01
127
Reference Number
Required
String (AN)
Min 1Max 30

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

Usage notes

A number assigned by Ford to uniquely identify the transaction set.

Required
Date (DT)
YYMMDD format

Date (YYMMDD). Also see: Date Qualifier (432).

Usage notes

Transaction creation date.

BRA-03
353
Transaction Set Purpose
Required
Identifier (ID)

Code identifying purpose of transmitted set.

00
Original
REF
06
Heading > REF

Reference Numbers

RequiredMax use 2

To transmit identifying numbers associated with the named party

Usage notes

Used to transmit shipment identification ASN and/or packing slip number.

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

Code qualifying the Reference Number.

PK
Packing List Number
SI
Shipper's Identifying Number for Shipment (SID)
REF-02
127
Reference Number
Optional
String (AN)
Min 1Max 30

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

Usage notes

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.

DTM
08
Heading > DTM

Date/Time Reference

RequiredMax use 1

To specify pertinent dates and times

Usage notes

Normally used to specify the receiving date. This segment will be used to specify the shipped date if return is indicated.

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time.

011
Shipped on this Date/Time
050
Received on This Date
Optional
Date (DT)
YYMMDD format

Date (YYMMDD). Also see: Date Qualifier (432).

N1 Loop
OptionalMax 200
N1
14
Heading > N1 Loop > N1

Name

RequiredMax use 1

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

Usage notes

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.

Example
N1-01
98
Organization Identifier
Required
Identifier (ID)

Code identifying the type of party being defined.

SF
Ship From
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).

92
Assigned by Buyer
N1-04
67
Identification Code
Optional
Identifier (ID)
Min 2Max 17

Code identifying one of the parties in the transaction. See Identification Code Qualifier (66).

Usage notes

Will contain Ford assigned code.

N1 Loop end
Heading end

Detail

RCD Loop
OptionalMax 200000
RCD
22
Detail > RCD Loop > RCD

Receiving Conditions

RequiredMax use 1

To report receiving conditions and specify contested quantities

Usage notes

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.
Example
RCD-02
663
Quantity Units Received
Optional
Decimal number (R)
Min 1Max 9

Number of units received.

RCD-03
355
Unit of Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying the basic unit measurement.

Usage notes

Will contain the same unit of measure as Ford Material Release (830).

RCD-04
664
Quantity Units Returned
Optional
Decimal number (R)
Min 1Max 9

Number of units returned.

Usage notes

Used by Assembly Division to indicate return quantity.

RCD-05
355
Unit of Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying the basic unit measurement.

Usage notes

Will contain the same unit of measure as Ford Material Release (830).

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.

Usage notes

Will contain difference between SN102 and RCD02.

RCD-07
355
Unit of Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying the basic unit measurement.

Usage notes

Will contain same unit of measure as Ford Material Release (830).

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

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

08
Rejected
12
13
RCD-09
667
Quantity in Question
Optional
Decimal number (R)
Min 1Max 9

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

Usage notes

When used will contain cum adjustment quantity.

RCD-10
355
Unit of Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code identifying the basic unit measurement.

Usage notes

Will contain same unit of measure as Ford Material Release (830).

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

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

11
Cum Adjustment Quantity
SN1
23
Detail > RCD Loop > SN1

Item Detail (Shipment)

RequiredMax use 1

To specify line item detail relative to shipment

Usage notes

Used to show ASN quantity for the part referenced in the LIN segment.

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. Also see: Unit of Measurement Code (355).

Usage notes

For Assembly Division, received quantity, otherwise ASN quantity.

SN1-03
355
Unit of Measurement Code
Required
Identifier (ID)
Min 2Max 2

Code identifying the basic unit measurement.

Usage notes

Will contain same unit of measure as Ford Material Release (830).

LIN
25
Detail > RCD Loop > LIN

Item Identification Detail

RequiredMax use 1

To specify basic item identification data.

Usage notes

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.

Example
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).

BP
Buyer's Part Number
LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 30

Identifying number for a product or service.

Usage notes

This field will contain the Ford part number.

RCD Loop end
Detail end

Summary

CTT
49
Summary > CTT

Transaction Totals

RequiredMax use 1

To transmit a hash total for a specific element in the transaction set

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set.

CTT-02
347
Hash Total
Required
Decimal number (R)
Min 1Max 10

Sum of values of the specific data element.

SE
50
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 and ending (SE) segment)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 6

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 assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)

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
Data Interchange Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender.

EDI Samples

sample 1

ISA~00~ ~00~ ~ZZ~F159B ~ZZ~BTCXA ~231222~1711~U~00200~000011819~0~P~<
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.