Transaction Format Interpretation
Transaction Header
ST*824*000000001$ TRANSACTION SET 824 Remittance Advice TRANSACTION SET CONTROL NO=000000001
BGN*00*9707011039*950207*1345$ TRANSACTION SET PURPOSE CODE 00 - ORIGINAL
9707011039 - REFERENCE NO 950207 - TRANS DATE 1345 - TRANS TIME Detail Data
OTI*TR*SI*02JC07*******856$ ORIGINAL TRANSACTION IDENTIFICATION APPLICATION ACKNOWLEDGMENT CODE
TE – ACCEPT WITH ERROR
TR - REJECT
REFERENCE NUMBER QUALIFIER SI - SHIPPER ID
REFERENCE NUMBER
02JC07 - ASN NUMBER
TRANSACTION SET IDENTIFIER CODE
856 - ASN
REF*BP* GA2A51710$ IDENTIFYING NUMBERS
REF*PO*111839 BP – PART NUMBER
GA2A51710 - PART NUMBER PO- PURCHASE ORDER 111839 – PO NUMBER
TED*ZZZ*PURCHASE ORDER INVALID$ TECHNICAL ERROR DESCRIPTION ZZZ - MUTUALLY DEFINED
PURCHASE ORDER INVALID – ERR DESC Transaction Trailer
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 41 of 139
Application Advice Transaction - 824 Required Data Segment Sequence Table
Seg ID Title Usage Max Use Loop/
Repeat
ST Transaction Set Header M 1
BGN Beginning Segment – Application Advice
M 1
OTI Original Transaction ID M 1 OTI-Begin/
10,000
Transaction Set : Application Advice - 824 Segment : ST - Transaction Set Header
Level : Header
Information : Indicates the start of the transaction set and assigns a control number. The ST control number must match the control number in the transaction set trailer SE segment.
Example : ST*824*000000001$
Element Name Features Use
01 Transaction Set ID M ID 03/03 Use "824"
02 Transaction Set Control Number
M AN 04/09 A unique number assigned to each transaction set within a functional group. This number must match the SE segment control number.
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 43 of 139
Transaction Set : Application Advice - 824
Segment : BGN - Beginning Segment Application Advice
Level : Header
Information : Indicates identifying numbers, date and time related to the transaction set.
Example : BGN*00*9707011039*950207*1345$
Element Name Features Use
01 Transaction Code M ID 02/02 '00' = Response
02 Reference Number M AN 01/30 Unique Reference Number 03 Date M DT 06/06 "950207" = 824 Creation Date 04 Time M TM 04/04 "1345" = 824 Creation Time
Transaction Set : Application Advice - 824
Segment : OTI - Original Transaction Identification
Level : Detail
Information : Used to identify transaction information.
Example : OTI*TR*SI*02JC07*******856$
Element Name Features Use
01 Application Ack.
Code
M ID 01/01 "TE" = Accept with Error
“TR” = Reject with Error
02 Reference Qualifier M ID 02/02 ANSI-X12 list of values allowed 03 Reference Number M AN 01/30 “02JC07” = ASN Number or any
other reference number
10 Transaction Set ID M ID 03/03 “856” = Advance Shipping Notice
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 45 of 139
Transaction Set : Application Advice - 824 Segment : REF – Reference Numbers
Level : Detail
Information : Used to transmit identifying numbers.
Example : REF*BP* GA2A51710$
REF*PO*111839
Element Name Features Use
01 Reference Qualifier M ID 02/02 ANSI-X12 list of values allowed 02 Reference Number M AN 01/30 Part Number/ PO Number/DO
Number or any other reference number
Transaction Set : Application Advice - 824
Segment : TED - Technical Error Description
Level : Detail
Information : Identifies erroneous element.
Example : TED*ZZZ*PURCHASE ORDER INVALID$
Element Name Features Use
01 Application Error Code
M ID 02/02 ANSI-X12 list of values allowed 02 Error Message M AN 01/60 Error Description
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 47 of 139
Transaction Set : Application Advice - 824 Segment : SE - Transaction Set Trailer
Level : Trailer
Information : Used to indicate the end of the transaction set and provide the count of the transmitted segments.
Example : SE*12*1019$
Element Name Features Use
01 Number of segments
M N0 01/06 Actual number of segments.
02 Transaction Set Control
M AN 04/09 Same number in the ST segment.
BFR*05**0523**DL*A*940523*941002*940513$ TRANSACTION PURPOSE=05 (REPLACE)
RELEASE NO=0523
FORCAST TYPE = DL
FORCAST QUANTITY=A (Actual Discrete Quantities)
HORIZON START =940523
LIN**BP*GA2E68520D78$ ┐ PART NO=GA2E68520D78
│ NOTE: NO PURCHASE ORDER NO
│
UNT*EA$ │ UNIT OF MEASURE=EA (EACH)
│
PER*EX*EMILY P~TE~734-782-8778$ │
SDP*Y*Y$ │ NO SHIPMENT/DELIVERY PATTERN FOR PLANNING QTY
│
FST*1350*A*D*940523****DO*111786019$ │ 05/23 EMERGENCY QTY =1350 (NET) FST*1368*C*D*940524****DO*111786022$ │ 05/24 FIRM QTY =1368 FST*1404*D*D*940603$ │ LOOP 06/03 PLANNED QTY =1404
FST*1567*D*F*940711*940731$ │ PLANNED NET QTY FROM 940711 THRU 940731 = 1567 FST*1729*D*F*940801*940904$ │ PLANNED NET QTY FROM 940801 THRU 940904 = 1729 FST*1819*D*F*940905*941002$ │ PLANNED NET QTY FROM 940905 THRU 941002 = 1819
│
SHP*01*10*050*940511$ │ LAST SHIPMENT RECEIVED FOR 10 UNITS SHIPPED ON
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 49 of 139
Material Release - 830
Required Data Segment Sequence Table
Seg ID Title Usage Max
Use
Loop/ Repeat
ST Transaction Set Header M 1
BFR Beginning Segment - Planning Schedule
M 1
N1 Name M 1 N1/
200
LIN Item Identification Detail M 1 LIN-Begin/
10,000
UNT Unit of Measure M 1
PER Administrative Contact Person O 3
SDP Ship/Delivery Pattern M 1 SDP-Begin/
104
NTE Note/Special Instructions F 100
FST Forecast Schedule M 104 SDP-End/
104
ATH Resource Authorization O 20
SHP Shipped/Received Info. O 1 SHP-Begin/
Transaction Set : Material Release - 830 Segment : ST - Transaction Set Header
Level : Header
Information : Indicates the start of the transaction set and assigns a control number. The ST control number must match the control number in the transaction set trailer SE segment.
Example : ST*830*000000001$
Element Name Features Use
01 Transaction Set ID M ID 03/03 Use "830"
02 Transaction Set Control Number
M AN 04/09 A unique number assigned to each transaction set within a functional group. This number must match the SE segment control number.
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 51 of 139
Transaction Set : Material Release - 830
Segment : BFR - Beginning Segment Planning Schedule
Level : Header
Information : Indicates the time frame of the shipping schedule.
Example : BFR*05**89*DL*A*940509*941002*940429$
Element Name Features Use
01 Purpose Code M ID 02/02 05 = Original (Normal)
00 = First Release after CUM Reset 02 Forecast order
number
Not Used.
03 Release Number M AN 01/30 Release Number 04 Forecast Type M ID 02/02 “SH” - Shipment based
"DL" - Delivery based 05 Forecast Quantity
Qualifier
Transaction Set : Material Release - 830 Segment : N1 - Name
Level : Header
Information : Used to identify parties associated with the shipment. The ship-from and ship-to segments are mandatory.
Example : N1*ST**92*CH$
N1*SF**92*11795$
Element Name Features Use
01 Identifier M ID 02/02 "ST" = Ship-To Location
"SF" = Ship-From Location
“BT” = Bill-To Location
“IC” = Intermediate Consignee
02 Not Used
03 ID Code Qualifier M AN 01/02 Use "92".
04 ID Code M ID 02/05 Will contain MNAO assigned code
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 53 of 139
Transaction Set : Material Release - 830
Segment : LIN - Item Identification Detail
Level : Detail
Information : Used to specify basic item identification data.
Example : LIN**BP*GA2E68520D78*PO*111786$
Element Name Features Use
01 Not used.
07 Product/Service ID O AN 01/30 May contain a Mazda part number if Element 03 contains a Ford part number. Only applicable to Ford orders.
Transaction Set : Material Release - 830 Segment : UNT- Unit of Measure
Level : Detail
Information : Used to specify item unit data.
Example : UNT*EA$
Element Name Features Use
01 Unit of Measurement
M ID 02/02 A code from ANSI Unit of Measure Table
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 55 of 139
Transaction Set : Material Release - 830
Segment : PER - Administrative Communications Contact
Level : Detail
Information : To identify a person to whom administrative communications should be directed.
Example : PER*EX*EMILY P~TE~734-782-8778$
Element Name Features Use
01 Contact Function Code
Transaction Set : Material Release - 830 Segment : SDP - Ship/Delivery Pattern
Level : Detail
Information : Used to specify ship/delivery requirements. MNAO does not specify these requirements in the 830.
Example : SDP*Y*Y$
Element Name Features Use
01 Ship/Delivery Pattern
M ID 01/02 "Y" used.
02 Ship/Delivery Pattern Time
M ID 01/01 "Y" used.
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 57 of 139
Transaction Set : Material Release - 830
Segment : NTE - Note/Special Instructions
Level : Detail
Information : Used to specify engineering changes and other pertinent information.
Example : NTE*LIN*111786019
Element Name Features Use
01 Constant O ID 03/03 Will contain “GEN” when used at a heading level or “LIN” when used at a detail level. May be used transmit DO number.
02 Freeform Message M AN 01/60
Information : Used to specify the forecast dates and quantities (both firm and planned).
Example : FST*1350*A*D*940523****DO*111786019$
FST*1368*C*D*940524****DO*111786022$
FST*1404*D*D*940603$
FST*1567*D*F*940711*940731$
Element Name Features Use
01 Quantity M R 01/10 Net or Cumulative Quantity 02 Forecast Qualifier M ID 01/01 “A” – Immediate
“C” – Firm
“D” – Planned 03 Forecast Timing
Qualifier
M ID 01/01 "D" – Discrete
“W” – Weekly
“F” – Flexible
04 Starting Date M DT 06/06 If weekly – week starting date If discrete – specific date
If Flexible – period beginning date 05 Ending Date O DT 06/06 Only used for Flexible Intervals –
period ending date 08 Reference Number O ID 02/02 May contain “DO”
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 59 of 139
Transaction Set : Material Release - 830
Segment : SHP - Shipped/Received Information
Level : Detail
Information : Used to specify resource authorization in the planning schedule.
Example : SHP*01*10~050~940511$
SHP*02*1224*050*931001**940511$
Element Name Features Use
01 Quantity Qualifier O ID 02/02 "01" - Discrete quantity
"02" - Cumulative quantity 02 Quantity O R 01/10 Net/Cum quantity received 03 Date Qualifier O ID 03/03 “011” or "050" or “051” used 04 Date O DT 06/06 Receive Date/ Cum Start Date
-Format: YYMMDD
06 Date O DT 06/06 If present will contain date of last shipment received
Transaction Set : Material Release - 830
Segment : ATH – Resource Authorization
Level : Detail
Information : To specify resource authorization in the planning schedule.
Example : ATH*FI*890401*56000**880801$
ATH*MT*890501*60000**880801$
Element Name Features Use
01 Resource Auth Qualifier
M ID 02/02 “FI” = Fabrication
“MT” = Raw Material
02 Date M DT 06/06 Cumulative Quantity Ending Date 03 Quantity M R 01/10 Cumulative Quantity Authorized
through date in ATH02
05 Date M DT 06/06 Cumulative Quantity Start Date
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 61 of 139
Transaction Set : Material Release - 830 Segment : REF – Reference Number
Level : Detail
Information : To transmit identifying numbers associated with the named party Example : REF*SI*72396$
Element Name Features Use
01 Reference Number Qualifier
M ID 02/02 “SI” – Shipment Iidentification number
02 Reference Number M AN 01/30 Contains shipment identification Number
Transaction Set : Material Release - 830 Segment : CTT - Transaction Totals
Level : Trailer
Information : Used to specify transaction totals.
Example : CTT*1*13665$
Element Name Features Use
01 Number of line items
M N0 01/06 Total number of LIN segments 02 Quantity Hash
Totals
M R 01/10 Hash total of quantities released
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 63 of 139
Transaction Set : Material Release - 830 Segment : SE - Transaction Set Trailer
Level : Trailer
Information : Used to indicate the end of the transaction set and provide the count of the transmitted segments.
Example : SE*000387*000000001$
Element Name Features Use
01 Number of segments
M N0 01/06 Actual number of segments.
02 Transaction Set Control
M AN 04/09 Same number in the ST segment.
Transaction Header
ST*850*000000001$ TRANSACTION SET 850
TRANSACTION SET CONTROL, NO=000000001
BEG*00*SA*110786***940513$ TRANSACTION PURPOSE=00 (ORIGINAL) STAND ALONE PURCHASE ORDER (“SA”) PURCHASE ORDER NUMBER = 110786 PURCHASE ORDER DATE = 940513
NTE*INV*NONE NO INVOICE INSTRUCTIONS
NTE*PMT*NONE NO PAYMENT INSTRUCTIONS
PER*EX*DEANNE MOSCROP*949-727-XXXX EXPEDITOR NAME AND TEL NUMBER
N1*BY*MAZDA NORTH AMERICAN OPERATIONS*92*MNAO$ BUYING PARTY NAME AND CODE N3*7755 IRVINE CENTER DRIVE* PO BOX 19734$ BUYING PARTY ADDRESS N4*IRVINE,CALIFORNIA$
N1*SU*TRW AUTOMOTIVE*92*11731$ SUPPLIER NAME AND CODE N3*12000 TECH CENTER DR$ SUPPLIER ADDRESS N4*LIVONIA, MI 48150$
Detail Data
┐ PO LINE NUMBER = 001 PO1*001*20*EA*140.84**BP*GA2A82939$ │ QTY = 20, UNIT PRICE = 140.84
│ BUYER PART NUMBER = GA2A82939
│
CUR*BY*USD$ │ CURRENCY OF BUYER = USD
│
PID*F****NONE$ │ NO FREE FORMAT PART DESCRIPTION
│
N1*ST**00321$ │ SHIP-TO CODE = 00321
│
REF~DO~112700001 │ DELIVERY ORDER NUMBER = 11270001
│LOOP
SCH*20*EA****002*000104$ │ DELIVERY REQUESTED FOR LINE ITEM ON 000104
││
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 65 of 139
Material Release - 850
Required Data Segment Sequence Table
Seg ID Title Usage Max
Use
Loop/ Repeat
ST Transaction Set Header M 1
BEG Beginning Segment – Purchase Order
M 1
NTE Header Notes O 100
REF Reference Numbers O 12
PER Administrative Communications O 3
TAX Sales Tax Reference O 1
PER Administrative Communications O 3 N1-End/200 ITA Allowance, Charge or Service O 10
ITD Terms of Sale O 2
DTM Date/Time Reference O 10
SHH General Schedule O 5
TD5 Carrier Details (Routing Sequence/Transit Time)
PID Product/Item Description O 200
REF Reference Numbers O 12
N1 Name O 1 N1-Begin/200
N2 Additional Name Information O 2
N3 Address Information O 2
N4 Geographic Information O 1
PER Administrative Communications O 3 N1-End/200
DTM Date/Time Reference O 10
SCH Line Item Schedule O 104 PO1-End/
100000
CTT Transaction Totals M 1
SE Transaction Set Trailer M 1 Usage: M - Mandatory
O - Optional (as needed) F – Floating (as needed)
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 67 of 139
Transaction Set : Purchase Order - 850
Segment : ST - Transaction Set Header
Level : Header
Information : Indicates purchase order number and date.
Example : ST*850*000000001$
Element Name Features Use
01 Transaction Set ID M ID 03/03 Use "850"
02 Transaction Set Control Number
M AN 04/09 A unique number assigned to each transaction set within a functional group. This number must match the SE segment control number.
Transaction Set : Purchase Order - 850
Segment : BEG – Beginning Segment for Purchase Order
Level : Header
Information : Indicates the start of the transaction set and assigns a control number. The ST control number must match the control number in the transaction set trailer SE segment.
Example : BEG*00*SA*110786***940513$
Element Name Features Use
01 Transaction Set Purpose Code
M ID 02/02 Use “00” – Original 02 Purchase Order
Type Code
M ID 02/02 Purchase Order Type Code
“SA” – Stand Alone 03 Purchase Order
Number
M AN 01/18 Purchase Order Number 06 Purchase Order
Date
M DT 06/06 Purchase Order Date
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 69 of 139
Transaction Set : Purchase Order - 850 Segment : NTE – Header Notes
Level : Header
Information : Notes at the purchase order header level.
Example : NTE*INV*NONE$
NTE*PMT*NONE$
Element Name Features Use
01 Note Reference Code
M ID 03/03 “INV” – Invoice Instruction
“GEN” – Entire Transaction Set
“PMT” – Payment 02 Free Form Message M AN 01/60 Message Description
Transaction Set : Purchase Order - 850 Segment : REF – Reference Numbers
Level : Header
Information : Used to indicate purchase order header information like ship from, etc at a header level.
Example : REF*SF*DEAR*DEARBORN, MI$
Element Name Features Use
01 Reference Number Qualifier
M ID 02/02 Valid codes from ANSI-X12 02 Reference Number M AN 01/17 Reference Number
03 Description M AN 01/80 Description
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 71 of 139
Transaction Set : Purchase Order - 850
Segment : PER – Administrative Communications Contact
Level : Header
Information : Administrative Communications Contact
Example : PER*EX*DEANNE MOSCROP*949-727-XXXX
Element Name Features Use
01 Contact Function Code
M ID 02/02 “IC” – Information Contact
“EX” – Expeditor
“BD” – Buyer Name or Department
“SU” – Supplier Code
Transaction Set : Purchase Order - 850 Segment : TAX – Sales Tax Reference
Level : Header
Information : Tax identification number of buying organization.
Example : TAX*983240-34-4$
Element Name Features Use
01 Tax Identification Number
O AN 01/20 Tax Identification Number (Tax Exemption Number or Direct Pay Number)
02 Location Qualifier O ID 01/02 “SP” = State
“CC” = Country. If code is “SP”, TAX03 will contain appropriate 2 digit state or province code 03 Location Identifier O AN 01/25 State/United States Code
(Governing entity location where the exemption is occuring)
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 73 of 139
Transaction Set : Purchase Order - 850
Segment : FOB – FOB Related Instructions
Level : Header
Information : Indicates shipment method of payment and location.
Example : FOB*DE*ZZ*DEARBORN*02*FOB$
Element Name Features Use
01 Shipment method of payment
M ID 02/02 “CC” – Collect
“CF” – Collect Freight credited to Payment Customer
“PP” – Prepaid by Seller
“PC” – Prepaid but charged to customer
02 Transportation Responsibility Location Qualifier
O ID 02/02 “OR” – Origin (Shipping Point)
“DE” – Destination (Shipping) 03 Description O AN 01/25 Location Description
Transaction Set : Purchase Order - 850 Segment : N1 – Name
Level : Header
Information : To identify a party by type of organization, name and code.
Example : N1*BY*MAZDA NORTH AMERICAN OPERATIONS*92*MNAO$
Element Name Features Use
01 Organization Identifier
M ID 02/02 “SP” – Party filling shipper’s order
“BT” – Party to be billed for other than freight (Bill-To)
“ST” – Ship to
“SU” – Supplier/Manufacturer
“BY” – Buying Party (Purchaser)
02 Name M AN 01/30
03 Identification Code Qualifier
M ID 01/02 “92” – Assigned by buyer 04 Identification Code M ID 02/05 MNAO assigned supplier code
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 75 of 139
Transaction Set : Purchase Order - 850
Segment : N2 – Additional Name Information
Level : Header
Information : To specify additional names or those longer than 30 characters in length.
Example : N2*ANY ADDITIONAL NAME INFORMATION$
Element Name Features Use
01 Name M AN 01/30
Transaction Set : Purchase Order - 850
Segment : N3 – Additional Name Information
Level : Header
Information : To specify the location of the named party.
Example : N3*7755 IRVINE CENTER DRIVE* PO BOX 19734$
Element Name Features Use
01 Address M AN 01/35 02 Address O AN 01/35
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 77 of 139
Transaction Set : Purchase Order - 850 Segment : N4 – Geographic Location
Level : Header
Information : To specify the geographic place of the named party.
Example : N4*IRVINE,CALIFORNIA$
Element Name Features Use
01 City Name M AN 02/15 02 State M ID 02/02 03 Postal Code M ID 05/09 04 Country Code O ID 02/02
Transaction Set : Purchase Order - 850
Segment : ITA – Allowance, Charge or Service
Level : Header
Information : To specify allowance or charges
Example : ITA*C***06**.1$
Element Name Features Use
01 Allowance or charge indicator
M ID 01/01 “C” = Charge 03 Special Services
Code
O ID 02/10 Transport Cost Service Code 04 Method of Handling M ID 02/02 “06” – Charge to be paid by
customer 06 Allowance or
Charge Rate
M R 01/09 Use only monetary value
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 79 of 139
Transaction Set : Purchase Order - 850
Segment : ITD – Terms of Sale/Deferred Terms of Sale
Level : Header
Information : To specify terms of sale
Example : ITD*09*3*2**15**30$
Element Name Features Use
01 Terms Type Code M ID 02/02 “08” – Basic Discount Offered
“09” – Proximo 02 Terms Basis Date
Code
M ID 01/02 “3” – Invoice Date 03 Terms Discount
Percent (If paid on or before Terms Discount Due Date)
M R 01/06
05 Terms Discount Days Due
M N0 01/02 07 Number of days
until total invoice amount is due (discount not applicable)
M N0 01/02
Transaction Set : Purchase Order - 850
Segment : DTM – Date/Time Reference
Level : Header
Information : To specify pertinent dates and times.
Example : DTM*007*991230$
DTM*036*000627$
Element Name Features Use
01 Date/Time Code M ID 03/03 “007” – Effective Date/Time
“036” – Expiration Date/Time 02 Date M DT 06/06 Date (YYMMDD)
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 81 of 139
Transaction Set : Purchase Order - 850 Segment : SHH – General Schedule
Level : Header
Information : To specify general scheduling conditions
Example : SHH*DD*069*000106$
Element Name Features Use
01 Schedule Code M ID 02/02 “DD” – Deliver on Date
02 Date/Time Qualifier M ID 03/03 “069” – Promised for Delivery
03 Date M DT 06/06
Transaction Set : Purchase Order - 850
Segment : TD5 – Carrier Details (Routing Sequence/Transit Time)
Level : Header
Information : To specify carrier, sequence of routing and to provide transit time information
Example : TD5*Z****SELLER’S DELIVERY$
Element Name Features Use
01 Routing Sequence Code
M ID 01/02 “Z” – Mutually Defined 05 Routing(Origin
Carrier)
M AN 01/25 Free-form Description
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 83 of 139
Transaction Set : Purchase Order - 850
Segment : PO1 – Purchase Order Baseline Item Data
Level : Detail
Information : To specify basic and most frequently used purchase order line item data.
Example : PO1*001*20*EA*140.84**BP*GA2A82939$
Element Name Features Use
01 PO Line Number M AN 01/06 Alphanumeric number which increments by one for each PO1 within a transaction set
02 Quantity Ordered M R 01/09 Quantity
06 Product/Service ID Qualifier
O ID 02/02 “BP” – Buyer’s Part Number
“MF” – Manufacturers Name
“MG” – Manufacturers Part Number
“PN” – Company Part Number
“PI” - Purchaser’s Item Code
“PT” – Print or Drawing
“OH” – Opposite Hand Part Number
“RP” – Replaced Part Number 07 Product/Service ID O AN 01/30
08-25 Used in same manner as 06-07
Transaction Set : Purchase Order - 850 Segment : NTE – Detail Notes
Level : Detail
Information : Notes at the purchase order line level.
Example : NTE*LIN*SPEC 114567$
Element Name Features Use
01 Note Reference Code
M ID 03/03 “LIN” – Line Notes 02 Free Form Message M AN 01/60 Message Description
Mazda North American Operations EDI Implementation Guidelines
EDI_MANUAL_2015_10_21.DOC Revision: Oct 21, 2015 Page 85 of 139
Transaction Set : Purchase Order - 850 Segment : CUR – Currency
Level : Detail
Information : To specify currency used in the transaction
Example : CUR*BY*USD$
Element Name Features Use
01 Organization M ID 02/02 “BY” = Purchaser 02 Currency Code M ID 03/03 Any valid ISO Code
Transaction Set : Purchase Order - 850
Segment : PO3 – Additional Item Detail
Level : Detail
Information : To specify additional item related data involving variations in normal price/quantity structure.
Example : PO3*QP*870102*MIN*1.98**12*EA$
PO3*QT*910701*ICL*1.00**5*EA$
PO3*QT*910701*ICL*.75**10*EA$
Element Name Features Use
01 Change Reason Code
M ID 02/02 “QP” – Quantity Based on Price Qualifer
“QT”- Quantity Price Break 02 Date O DT 06/06 Date (YYMMDD – Quantity Price
Effective Date)
03 Price Qualifier Code O ID 03/03 “MIN” – Minimum Order Quantity Price
“ICL” – Unit Price through Quantity 04 Unit Price O R 01/14
06 Quantity M R 01/10 07 Unit of Measure M ID 02/02 08 Description O AN 01/80
Mazda North American Operations
Mazda North American Operations