X12 830 Material Release
- ~ 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.
- PS
- Planning Schedule with Release Capacity
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)
- 002001MNAO
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
The ST control number must match the control number in
the transaction set trailer SE segment.
Example: ST830000000001$
Code uniquely identifying a Transaction Set.
Use "830"
- 830
- X12.14 Planning Schedule
A unique number assigned to each transaction set within a functional group.
This number must match the SE segment control number.
Beginning Segment Planning Schedule
Indicates the time frame of the shipping schedule.
Example: BFR05**89DLA940509941002940429$
Code identifying purpose of transmitted set.
- 00
- First Release after CUM Reset
- 05
- Original (Normal)
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.
Code which qualifies the type of dates used in the forecast.
- DL
- Delivery Based
- SH
- Shipment Based
Code which qualifies the types of quantities.
- A
- Net
- C
- Cumulative
Date (YYMMDD). Also see: Date Qualifier (432).
Date (YYMMDD). Also see: Date Qualifier (432).
Note/Special Instruction
Used to specify engineering changes and other pertinent information.
Example: NTEGENTerms and conditions apply. Visit: suppliers.mazdausa.com.
Note: Mazda's implementation guide references NTE in the detail, but this isn’t allowed by the X12 spec.
Code identifying the functional area or purpose for which the note applies.
Also see: Free Form Message (3).
Will contain “GEN” when used at a heading level
- GEN
- Entire Transaction Set
Free-form text.
Terms and conditions apply. Visit: suppliers.mazdausa.com
Name
Used to identify parties associated with the shipment.
The ship-from and ship-to segments are mandatory.
Example:
N1ST**92CH$
N1SF**92P1795$
Code identifying the type of party being defined.
- BT
- Bill To Location
- IC
- Intermediate Consignee
- SF
- Ship From Location
- ST
- Ship To Location
Code designating the system/method of code structure used for Identification Code (67).
Use "92".
Code identifying one of the parties in the transaction. See Identification Code Qualifier (66).
Will contain MNAO assigned code
Detail
Item Identification Detail
To specify basic item identification data.
Example: LIN*BPGA2E68520D78PO111786$
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- BP
- Part Number
Identifying number for a product or service.
Actual part number.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
May contain “EP”
Identifying number for a product or service.
May contain a Mazda part number if Element 03 contains a Ford part
number. Only applicable to Ford orders.
Unit of Measure
To specify item unit data.
Example: UNT*EA$
Code identifying the basic unit measurement.
A code from ANSI Unit of Measure Table
Administrative Communications Contact
To identify a person to whom administrative communications should
be directed.
Example: PEREXEMILY PTE734-782-8778$
Code identifying the major duty or responsibility of the person or group named.
- EX
- General Office Expeditor
Code identifying the type of communications used in Communication Number (364). Also see: Communication Number (364).
May contain “TE”. MNAO contact number follows.
Complete communications number including country or area code when applicable. Also see: Communications Number Qualifier (365).
May contain MNAO’s contact number.
Ship/Delivery Pattern
To identify specific ship/delivery requirements
MNAO does not specify these requirements in the 830.
Example: SDPYY$
Forecast Schedule
Used to specify the forecast dates and quantities (both firm and planned).
Example:
FST1350AD940523*DO111786019$
FST*1368CD940524*DO111786022$
FST*1404DD940603$
FST1567DF940711*940731$
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
Net or Cumulative Quantity
Code specifying the sender's confidence level of the forecast data.
- A
- Immediate
- C
- Firm
- D
- Planned
Code specifying interval grouping of the forecast.
- D
- Discrete
- F
- Flexible
- W
- Weekly
Date (YYMMDD). Also see: Date Qualifier (432).
If weekly – week starting date
If discrete – specific date
If Flexible – period beginning date
Date (YYMMDD). Also see: Date Qualifier (432).
Only used for Flexible Intervals – period ending date
Code qualifying the Reference Number.
May contain “DO”
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).
May contain Delivery Order Number for Immediate or Firm Orders
Resource Authorization
To specify resource authorization in the planning schedule.
Example:
ATHFI89040156000**880801$
ATHMT89050160000**880801$
Code identifying the resource which the buyer is authorizing the seller to commit to.
- FI
- Fabrication
- MT
- Raw Material
Date (YYMMDD). Also see: Date Qualifier (432).
Cumulative Quantity Ending Date
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
Cumulative Quantity Authorized through date in ATH02
Date (YYMMDD). Also see: Date Qualifier (432).
Cumulative Quantity Start Date
Shipped/Received Information
Used to specify resource authorization in the planning schedule.
Example:
SHP0110050940511$
SHP021224050931001**940511$
Code specifying the type of quantity.
- 01
- Discrete Quantity
- 02
- Cumulative Quantity
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
Net/Cum quantity received
Code specifying type of date or time.
- 011
- Shipped on this Date/Time
- 050
- Received on This Date
- 051
- Cumulative Quantity Start Date
Date (YYMMDD). Also see: Date Qualifier (432).
If present will contain date of last shipment received
Reference Number
To transmit identifying numbers associated with the named party
Example:
REFSI72396$
Code qualifying the Reference Number.
- SI
- Shipment Identification Number
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).
Contains shipment identification Number
Summary
Transaction Totals
Used to specify transaction totals.
Example:
CTT113665$
Total number of line items in the transaction set.
Total number of LIN segments
Sum of values of the specific data element.
Hash total of quantities released
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)
Example:
SE000387000000001$
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.)
Same number in the ST segment.
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
BFR*05**0523*DL*A*940523*941002*940513
NTE*GEN*Terms and conditions apply. Visit: suppliers.mazdausa.com
N1*ST**92*CH
N1*SF**92*P1795
LIN**BP*GA2E68520D78
UNT*EA
PER*EX*EMILY P~TE~734-782-8778
SDP*Y*Y
FST*1350*A*D*940523****DO*111786019
FST*1368*C*D*940524****DO*111786022
FST*1404*D*D*940603
FST*1440*D*D*940612
FST*1476*D*D*940620
FST*1512*D*D*940623
FST*1567*D*F*940711*940731
FST*1729*D*F*940801*940904
FST*1819*D*F*940905*941002
SHP*01*10*050*940511
REF*SI*12KP01
SHP*02*1224*050*931001**940511
CTT*01*13665
SE*000023*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.