Daimler Trucks North America LLC

EDI Implementation Guide

861 Receiving Advice

ANSI ASC X12 3050

Document Revision History
Date Version Contributor Changes
2/25/1999 1.00 Original External
Document
12/13/2000 1.00 Last modified
7/1/2007 1.00 FTL EDI Support Format change
1/14/2008 2.00 DTNA EDI Support Name Change
1/2010 3.0 DTNA MFG Example

01/19/2010 2 861v3050DTNAMFGv3_00.rtf
861 Receiving Advice/Acceptance Certificate

Functional Group ID= RC

Introduction:
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.

Heading:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
M 010 ST Transaction Set Header M 1
M 020 BRA Beginning Segment for Receiving Advice or M 1 n1
Acceptance Certificate
050 REF Reference Numbers O 1
M 070 DTM Date/Time Reference M 10
LOOP ID - N1 200
130 N1 Name O 2

Detail:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
LOOP ID - RCD 200000
010 RCD Receiving Conditions O 1
020 SN1 Item Detail (Shipment) O 1
040 LIN Item Identification O 100

Summary:
Pos. Seg. Req. Loop Notes and
No. ID Name Des. Max.Use Repeat Comments
010 CTT Transaction Totals O 1 n2
M 020 SE Transaction Set Trailer M 1

Transaction Set Notes

1. This transaction set is used by Daimler Trucks North America to convey receiving discrepancies, i.e. 856
shipment quantity does not match quantity physically received to a supplier.

Contents / Organization

01/19/2010 3 861v3050DTNAMFGv3_00.rtf
An EDI 861 transmission (ISA though IEA segments) can consist of multiple transaction set, one transaction set (ST
though SE segments) per shipment. Transaction sets are presented in SID (Shipment Identification Number
sequence within a transmission.
Within each transaction set, discrepancies will be sequenced by Part Number, I.E. a RCD loop is specified for each
part within a shipment for which a discrepancy occurred.

Example:

ISA`00`FTL DATA `00`FTL DATA `ZZ`FTL MFG `ZZ`AB12 MFG

`100218`0310`U`00200`000001725`0`P`>_
GS`RC`FTL MFG`AB12 MFG`100218`0310`18`X`003050_
ST`861`000000018_
BRA`01`100218`00`1_
REF`SI_
DTM`050`100217`0210`ET_
N1`SF`AB12_
N1`ST`CLE`92`004_
RCD``1`PC````PC`03_
SN1``2`PC_
LIN``BP`000 446 15 54_
CTT`1`0_
SE`11`000000018_
GE`1`18_
IEA`1`000001725_

01/19/2010 4 861v3050DTNAMFGv3_00.rtf
 Segment: ST Transaction Set Header
Position: 010
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the start of a transaction set and to assign a control number
Syntax Notes:
Semantic Notes:
Comments:

Data Element Summary

Ref. Data
Des. Element Name Attributes
M ST01 143 Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set
861 Receiving Advice
M ST02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set

01/19/2010 5 861v3050DTNAMFGv3_00.rtf
 Segment: BRA Beginning Segment for Receiving Advice or Acceptance Certificate
Position: 020
Loop:
Level: Heading
Usage: Mandatory
Max Use: 1
Purpose: To indicate the beginning of a Receiving Advice or Acceptance Certificate Transaction
Set and transmit an identifying number, date, and time
Syntax Notes:
Semantic Notes:
Comments:

Data Element Summary

Ref. Data
Des. Element Name Attributes
M BRA01 127 Reference Number M AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
Note: Number assigned by the sender to uniquely identify the transaction set.
M BRA02 373 Date M DT 6/6
Date (YYMMDD)
Note: Date the transaction set was created
M BRA03 353 Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set
00 Original
M BRA04 962 Receiving Advice or Acceptance Certificate Type Code M ID 1/1
Code specifying type of receiving advice
Refer to 003050 Data Element Dictionary for acceptable code values.

01/19/2010 6 861v3050DTNAMFGv3_00.rtf
 Segment: REF Reference Numbers
Position: 050
Loop:
Level: Heading
Usage: Optional
Max Use: >1
Purpose: To specify identifying numbers.
Syntax Notes:
Semantic Notes:
Comments: 1 This segment is used to convey the SID (Shipment Identification Number of the
shipment for which a receiving discrepancy occurred. The SID comes from the
corresponding 856 (Ship Notice/Manifest) transaction sent by the supplier.

Data Element Summary

Ref. Data
Des. Element Name Attributes
M REF01 128 Reference Number Qualifier M ID 2/2
Code qualifying the Reference Number.
SI Shipper's Identifying Number for Shipment (SID)
REF02 127 Reference Number X AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
Note: SID (Shipment Identification Number)

01/19/2010 7 861v3050DTNAMFGv3_00.rtf
 Segment: DTM Date/Time Reference
Position: 070
Loop:
Level: Heading
Usage: Mandatory
Max Use: 10
Purpose: To specify pertinent dates and times
Syntax Notes:.
Semantic Notes:
Comments: 1 This segment is used to provide the date of shipment for a receiving
discrepancy.

Data Element Summary

Ref. Data
Des. Element Name Attributes
M DTM01 374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time
050 Received
DTM02 373 Date X DT 6/6
Date (YYMMDD)
Note: Date the shipment was received.
DTM03 337 Time X TM 4/8
Note: Always 0000
DTM04 623 Time Code O ID 2/2
Code identifying the time.
CT Central Time
ET Eastern Time
MT Mountain Time
PT Pacific Time

01/19/2010 8 861v3050DTNAMFGv3_00.rtf
 Segment: N1 Name
Position: 130
Loop: N1 Optional
Level: Heading
Usage: Optional
Max Use: 1
Purpose: To identify a party by type of organization, name, and code
Syntax Notes: 1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
Semantic Notes:
Comments: 1 This segment is used to identify the “Ship-from” and “Ship-to” locations relative to
the shipment for which a receiving discrepancy occurred.

Data Element Summary

Ref. Data
Des. Element Name Attributes
M N101 98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
Note: Always = “SF” or “ST” indicating “Ship-from” or “Ship-to”
SF Ship From
ST Ship To
N102 93 Name X AN 1/35
Free-form name
Note: Will equal supplier’s 4 position assigned vendor code if N101 = “SF” or
3-position ship to location abbreviation if N101 = “ST”.
N103 66 Identification Code Qualifier X ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
92 Assigned by Buyer or Buyer's Agent
N104 67 Identification Code X AN 2/20
Code identifying a party or other code
Note: will equal assigned ship-to location code for receiving location when
N101 = “ST”.

01/19/2010 9 861v3050DTNAMFGv3_00.rtf
 Segment: RCD Receiving Conditions
Position: 010
Loop: RCD Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To report receiving conditions and specify contested quantities
Syntax Notes:
Semantic Notes:
Comments: 1 This segment is used to convey the quantity actually received and disputed quantity
(shortage/overage quantity).

Data Element Summary

Ref. Data
Des. Element Name Attributes
RCD02 663 Quantity Units Received or Accepted X R 1/9
Number of Units Received or Accepted
Note: Number of units actually received of part number in next LIN segment.
RCD03 355 Unit or Basis for Measurement Code X ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
PC Piece
RCD06 667 Quantity in Question X R 1/9
Number of units contested because of physical condition or status of units
Note: Number of units believed either short or over of part number specified in
next LIN segment.
RCD07 355 Unit or Basis for Measurement Code X ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
PC Piece
RCD08 412 Receiving Condition Code X ID 2/2
Code designating physical condition or status of units received in a specific
shipment
02 Quantity Short
03 Quantity Over

01/19/2010 10 861v3050DTNAMFGv3_00.rtf
 Segment: SN1 Item Detail (Shipment)
Position: 020
Loop: RCD Optional
Level: Detail
Usage: Optional
Max Use: 1
Purpose: To specify line-item detail relative to shipment
Syntax Notes: .
Semantic Notes:
Comments: 1 This segment is used to indicate the shipment quantity from the corresponding 856
transaction sent by the supplier for shipment/part number for which a receiving
discrepancy occurred.

Data Element Summary

Ref. Data
Des. Element Name Attributes
M SN102 382 Number of Units Shipped M R 1/10
Numeric value of units shipped in manufacturer's shipping units for a line item
or transaction set
Note: Ship quantity of part number in next LIN segment (from supplier’s 856).
M SN103 355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003050 Data Element Dictionary for acceptable code values.

01/19/2010 11 861v3050DTNAMFGv3_00.rtf
 Segment: LIN Item Identification
Position: 040
Loop: RCD Optional
Level: Detail
Usage: Optional
Max Use: 100
Purpose: To specify basic item identification data
Syntax Notes:
Semantic Notes:
Comments: 1 This segment is used to indicate the Daimler Trucks North America’s part number
for which a receiving discrepancy occurred.

Data Element Summary

Ref. Data
Des. Element Name Attributes
M LIN02 235 Product/Service ID Qualifier M ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
BP Buyer's Part Number
M LIN03 234 Product/Service ID M AN 1/40
Identifying number for a product or service

01/19/2010 12 861v3050DTNAMFGv3_00.rtf
 Segment: CTT Transaction Totals
Position: 010
Loop:
Level: Summary
Usage: Optional
Max Use: 1
Purpose: To transmit a hash total for a specific element in the transaction set
Syntax Notes:
Semantic Notes:
Comments: 1 This segment is intended to provide hash totals to validate transaction
completeness and correctness.

Data Element Summary

Ref. Data
Des. Element Name Attributes
M CTT01 354 Number of Line Items M N0 1/6
Total number of line items in the transaction set
Note: Total number of RCD loops included in this transaction set.
CTT02 347 Hash Total O R 1/10
Sum of values of the specified data element.
Note: Sum total of quantity actually received for all part(s) included in this
transaction set (sum of element RCD02).

01/19/2010 13 861v3050DTNAMFGv3_00.rtf
 Segment: SE Transaction Set Trailer
Position: 020
Loop:
Level: Summary
Usage: Mandatory
Max Use: 1
Purpose: To indicate the end of the transaction set and provide the count of the transmitted
segments (including the beginning (ST) and ending (SE) segments).
Syntax Notes:
Semantic Notes:
Comments:

Data Element Summary

Ref. Data
Des. Element Name Attributes
M SE01 96 Number of Included Segments M N0 1/10
Total number of segments included in a transaction set including ST and SE
segments
M SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set

01/19/2010 14 861v3050DTNAMFGv3_00.rtf