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

X12 861 Receiving Advice

X12 Release 2001
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/mazda/receiving-advice/01HPSY8RCC2EZZZ3M6ZJYT2EPM
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
Max use 12
Required
DTM
08
Date/Time Reference
Max use 10
Required
N1 Loop
N1
14
Name
Max use 1
Required
detail
RCD Loop
RCD
22
Receiving Conditions
Max use 1
Required
SN1
23
Item Detail (Shipment)
Max use 1
Required
LIN
25
Item Identification Detail
Max use 1
Required
summary
CTT
49
Transaction Totals
Max use 1
Required
SE
50
Transaction Set Trailer
Max use 1
Required
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

Indicates identifying numbers, date and time related to the transaction set.

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 MNAO to uniquely identify the transaction set.

BRA-02
373
Date
Required
Date (DT)
YYMMDD format

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

Usage notes

Date the transaction is created

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

Code identifying purpose of transmitted set.

00
Original
REF
06
Heading > REF

Reference

RequiredMax use 12

To transmit identifying numbers associated with the named party

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

Code qualifying the Reference Number.

SI
Shipper's Identifying Number for Shipment (SID)
REF-02
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

Supplier Generated ASN Number

DTM
08
Heading > DTM

Date/Time Reference

RequiredMax use 10

Indicates specific date and time information

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

Code specifying type of date or time.

Usage notes

Will contain “050” – Material received on this date or “011” – Material shipped on this date. Shipped date is used when a return is indicated.

011
Shipped on this Date/Time
050
Received on This Date
DTM-02
373
Date
Required
Date (DT)
YYMMDD format

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

Usage notes

Date shipment is received or shipped

N1 Loop
RequiredMax 200
N1
14
Heading > N1 Loop > N1

Name

RequiredMax use 1

Used to identify parties associated with the shipment.

Example
N1-01
98
Identifier
Required
Identifier (ID)

Code identifying the type of party being defined.

SF
Ship From
ST
Ship To
N1-03
66
ID Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67).

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

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

Usage notes

Code of shipper, or receiver.
Example:
"SF" = P1786 – Supplier
"ST" = 00321 – Receiver

Example values
  • P1786
  • 00321
N1 Loop end
Heading end

Detail

RCD Loop
RequiredMax >1
RCD
22
Detail > RCD Loop > RCD

Receiving Conditions

RequiredMax use 1

Used to report receiving conditions and discrepancies.

Example
RCD-02
663
Quantity Received
Optional
Decimal number (R)
Min 1Max 9

Number of units received.

Usage notes

Actual received quantity.

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

Code identifying the basic unit measurement.

Usage notes

Will contain same UOM as in the release (830) or purchase order (850)

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

Number of units returned.

Usage notes

When used will contain the return quantity

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

Code identifying the basic unit measurement.

Usage notes

Will contain same UOM as in the release (830) or purchase order (850)

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
Optional
Identifier (ID)
Min 2Max 2

Code identifying the basic unit measurement.

Usage notes

Will contain same UOM as in the release (830) or purchase order (850)

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

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

Usage notes

Valid codes from ANSI-X12

SN1
23
Detail > RCD Loop > SN1

Item Detail (Shipment)

RequiredMax use 1

Used to denote ASN quantity.

Example
SN1-02
382
ASN Quantity
Required
Decimal number (R)
Min 1Max 9

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set. Also see: Unit of Measurement Code (355).

SN1-03
355
Unit Measurement
Optional
Identifier (ID)
Min 2Max 2

Code identifying the basic unit measurement.

Usage notes

Will contain same UOM as in the release (830) or purchase order (850)

LIN
25
Detail > RCD Loop > LIN

Item Identification Detail

RequiredMax use 1

To specify basic item identification data.

Example
LIN-02
235
Product/Service Identifier
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

Actual 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

Usage notes

Used to specify transaction totals.

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

Total number of line items in the transaction set.

Usage notes

Total Number of RCD Segments

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

Sum of values of the specific data element.

Usage notes

Accumulation of the Quantity Received(RCD02) of all RCD segments

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
GE

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

ST*861*000000001
BRA*050213*940514*00
REF*SI*050213
DTM*050*940514
N1*SF**92*P1786
N1*ST**92*00321
RCD**126*PC***4*PC*02
SN1**130*PC
LIN**BP*GA2A50260
CTT*1*126
SE*000011*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.