X12 830 Material Release

X12 Release 2003

This standard provides the standardized format and establishes the data contents of a planning schedule with release capability transaction set. The planning schedule with release capability transaction set provides for customary and established business practice relative to the transfer of forecasting/material release information between organizations.

The planning schedule transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities,and specific ship/delivery patterns for requirements that have been represented in "buckets," such as weekly, monthly, or quarterly. The order release forecast may also contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders.

Delimiters

• ~ Segment
• * Element
• > Component

GS Functional Group Header

Required · Max use 1

To indicate the beginning of a functional group and to provide control information

GS-01 · 479 · Functional Identifier Code · Required · Identifier (ID)

Code identifying a group of application related Transaction Sets.

• PS: Planning Schedule with Release Capability (830)

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

Code identifying party sending transmission.

GS-03 · 124 · Application Receiver's Code · Required · Identifier (ID) · Min 2 Max 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 1 Max 9

Assigned number originated and maintained by the sender.

GS-07 · 455 · Responsible Agency Code · Required · Identifier (ID) · Min 1 Max 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 Code · Required · Identifier (ID)

Code indicating the version, release, and industry ID of the EDI standard being used. Positions 1 - 3, Major Version Number; Positions 4 - 6, Release Level of Version; Positions 7 - 12, Industry or Trade Association ID (optionally assigned by user)

• 002003: Draft Standard Approved by ASC X12 through August 1988.

Heading

2 Heading > ST

ST Transaction Set Header

Required · Max use 1

To indicate the start of a transaction set and to assign a control number

ST-01 · 143 · Transaction Set Identifier Code · Required · Identifier (ID)

Code uniquely identifying a Transaction Set.

• The transaction set identifier (ST01) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set).

• 830: X12.14 Planning Schedule

ST-02 · 329 · Transaction Set Control Number · Required · Numeric (N) · Min 4 Max 9

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

3 Heading > BFR

BFR Beginning Segment for Planning Schedule

Required · Max use 1

To indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast; and related forecast envelope dates

BFR-01 · 353 · Transaction Set Purpose Code · Required · Identifier (ID)

Code identifying purpose of transaction set.

• At least one of BFR02 or BFR03 must be present.
• If BFR01 equals "04" (Net Change) - BFR09 is required.

• 05: Replace

BFR-02 · 127 · Reference Number · Required · String (AN) · Min 1 Max 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).

• BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.

Usage notes

TMS assigned vendor code.

BFR-04 · 675 · Forecast Type Qualifier · Required · Identifier (ID)

Code which qualifies the type of dates used in the forecast.

• SH: Shipment Based

BFR-05 · 676 · Forecast Quantity Qualifier · Required · Identifier (ID)

Code which qualifies the types of quantities.

• A: Actual Quantities

BFR-06 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

• BFR06 - Forecast Horizon Start Date: The date when the forecast horizon (envelope) begins.

BFR-07 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

• BFR07 - Forecast Horizon End Date: The date when the forecast horizon (envelope) ends.

BFR-08 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

• BFR08 - Date Forecast Generated: The date the forecast data was generated.

Usage notes

Run date. This field will contain current date.

N1 Loop Required Max >1

10 Heading > N1 Loop > N1

N1 Name

Required · Max use 1

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

• Loop N1 is optional but, if used, segment N1 is mandatory.

Usage notes

Identifies material release issuer.

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity or a physical location.

• At least one of N102 or N103 must be present.

• MI: Planning Schedule/Material Release Issuer

N1-02 · 93 · Name · Required · String (AN) · Min 1 Max 35

Free form name.

• If either N103 or N104 is present, then the other is required.

N1-03 · 66 · Identification Code Qualifier · Required · Identifier (ID)

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

• 01: DUNS Number

N1-04 · 67 · Identification Code · Required · Identifier (ID) · Min 2 Max 17

Code identifying a party.

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

15 Heading > N1 Loop > PER

PER Administrative Communications Contact

Required · Max use 3

To identify a person or office to whom administrative communications should be directed (TMS Analyst).

PER-01 · 366 · Contact Function Code · Required · Identifier (ID)

Code identifying the major duty or responsibility of the person or group named.

• If PER03 is present, then PER04 is required.

• SC: Schedule Contact/Analyst

PER-02 · 93 · Name · Required · String (AN) · Min 1 Max 35

Free form name.

PER-03 · 365 · Communication Number Qualifier · Required · Identifier (ID)

Code identifying the type of communication number.

• TE: Telephone Number

PER-04 · 364 · Communication Number · Required · String (AN) · Min 7 Max 21

Complete communications number including country or area code when applicable. Also see: Communications Number Qualifier (365).

Detail

LIN Loop Required Max >1

32 Detail > LIN Loop > LIN

LIN Item Identification Detail

Required · Max use 1

To specify basic item identification data: part number, part description, supplier part number, purchase order number.

• At least one occurrence of loop LIN is required.

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

• If LIN06 is present, then LIN07 is required.
• LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.

• BP: Buyer's Part

LIN-03 · 234 · Product/Service ID · Required · String (AN) · Min 1 Max 30

Identifying number for a product or service.

• If LIN08 is present, then LIN09 is required.

Usage notes

TMS part number.

LIN-04 · 235 · Product/Service ID Qualifier · Required · Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

• If LIN10 is present, then LIN11 is required.

• VP: Vendor's (Seller's) Part Number

LIN-05 · 234 · Product/Service ID · Required · String (AN) · Min 1 Max 30

Identifying number for a product or service.

• If LIN12 is present, then LIN13 is required.

Usage notes

Vendor’s part number. If a vendor’s part number does not exist, this field will contain “N/A”.

LIN-06 · 235 · Product/Service ID Qualifier · Required · Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

• If LIN14 is present, then LIN15 is required.

• PD: Part Description

LIN-07 · 234 · Product/Service ID · Required · String (AN) · Min 1 Max 30

Identifying number for a product or service.

• If LIN16 is present, then LIN17 is required.

Usage notes

TMS part description.

LIN-08 · 235 · Product/Service ID Qualifier · Required · Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

• If LIN18 is present, then LIN19 is required.

• PO: Purchase Order Number

LIN-09 · 234 · Product/Service ID · Required · String (AN) · Min 1 Max 30

Identifying number for a product or service.

• If LIN20 is present, then LIN21 is required.

Usage notes

Purchase order number. If this is a forecast, P.O. Number will be “N/A”

LIN-10 · 235 · Product/Service ID Qualifier · Required · Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

• If LIN22 is present, then LIN23 is required.

• ON: Customer Order Number

LIN-11 · 234 · Product/Service ID · Required · String (AN) · Min 1 Max 30

Identifying number for a product or service.

• If LIN24 is present, then LIN25 is required.

Usage notes

Distributor/dealer order number. If none exists, this field will default to spaces.
This is only for direct ship. Otherwise it will contain a default value of spaces.

33 Detail > LIN Loop > UIT

UIT Unit Detail

Required · Max use 1

To specify item unit data

UIT-01 · 355 · Unit of Measurement Code · Required · Identifier (ID)

Code identifying the basic unit measurement.

• If UIT03 is present, then UIT02 is required.

• PC: Piece

N1 Loop Optional Max >1

This segment is optional. It will occur only in case of a firm order or a combination of a firm and forecast orders. It will not occur for forecast only orders.

53 Detail > LIN Loop > N1 Loop > N1

N1 Name

Required · Max use 1

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

• Loop N1 is optional but, if used, segment N1 is mandatory.

Usage notes

Indicates whether to ship direct or use routing slip.

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID)

Code identifying an organizational entity or a physical location.

• At least one of N102 or N103 must be present.

• MA: Customer Name
• ST: Ship-To Location

N1-02 · 93 · Name · Required · String (AN) · Min 1 Max 35

Free form name.

• If either N103 or N104 is present, then the other is required.

Usage notes

Ship-to name. This field will contain “SEE ROUTING SLIP” for normal orders and “SHIP DIRECT” for ship direct orders.

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID)

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

• 92: Mutually defined ID code

N1-04 · 67 · Identification Code · Optional · Identifier (ID) · Min 2 Max 17

Code identifying a party.

• This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.

Usage notes

In case of the direct ship order, this field will contain the dealer code. Otherwise it will default to “99999”.

54 Detail > LIN Loop > N1 Loop > N2

N2 Additional Name Information

Required · Max use 2

To specify additional names or those longer than 35 characters in length

Usage notes

Identifies the name and street address of the final destination.

N2-01 · 93 · Name · Required · String (AN)

Free form name.

Usage notes

Final destination. In case of a firm order, this field will contain a TMS depot code. Otherwise it will contain the dealer name. Valid depot codes are "51" and "KY".

• 51: Ontario
• KY: Kentucky

N2-02 · 93 · Name · Required · String (AN) · Min 1 Max 35

Free form name.

Usage notes

In case of a firm order, this field will contain the TMS depot name. Otherwise it will contain the dealer street address.

55 Detail > LIN Loop > N1 Loop > N3

N3 Address Information

Optional · Max use 2

To specify the location of the named party

Usage notes

Identifies the city, state, and zip code of the final destination.
This segment is optional. It will occur only for ship direct orders. It must be preceded by an N1 and an N2 segments.

N3-01 · 166 · Address Information · Required · String (AN) · Min 1 Max 35

Free-form field for address information.

N3-02 · 166 · Address Information · Required · String (AN) · Min 1 Max 35

Free-form field for address information.

SDP Loop Required Max >1

60 Detail > LIN Loop > SDP Loop > SDP

SDP Ship/Delivery Pattern

Required · Max use 1

To identify specific ship/delivery requirements

• At least one occurrence of loop SDP is required.

SDP-01 · 678 · Ship/Delivery Pattern Code · Required · Identifier (ID)

Code which specifies the days for routine shipments or deliveries.

• N: As Directed
• Z: Mutually Defined

SDP-02 · 679 · Ship/Delivery Pattern Time Code · Required · Identifier (ID)

Code which specifies the time for routine shipments or deliveries.

• F: Time of Day
• Z: Mutually Defined

61 Detail > LIN Loop > SDP Loop > FST

FST Forecast Schedule

Required · Max use 104

To specify the forecasted dates and quantities

Usage notes

In case of a firm order, this segment will be used to specify order date, and order quantity.
In case of a forecast, it will be used to specify forecasts’ dates and quantities.

FST-01 · 380 · Quantity · Required · Decimal number (R) · Min 1 Max 10

Numeric value of Quantity. Also see: Unit of Measurement Code (355).

• If FST06 is present, then FST07 is required.

FST-02 · 680 · Forecast Qualifier · Required · Identifier (ID)

Code specifying the sender's confidence level of the forecast data.

• If either FST08 or FST09 is used, the other is required.
• As qualified by FST02 and FST03, FST04 represents either a discrete forecast date, the first date of a forecasted bucket (weekly, monthly, quarterly, etc.) or the start date of a flexible interval.

• C: Firm Order
• D: Forecast Order

FST-03 · 681 · Forecast Timing Qualifier · Required · Identifier (ID)

Code specifying interval grouping of the forecast.

• If FST03 - "F" (indicating flexible interval) and FST04 and FST05 are required. FST04 would be used for the start date of the flexible interval and FST05 would be used for the end date of the flexible interval.

• D: Daily
• M: Monthly
• W: Weekly
• Z: Contract Period

FST-04 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

Summary

72 Summary > CTT

CTT Transaction Totals

Required · Max use 1

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

• Number of line items (CTT01) is the accumulation of the number of LIN segments. Hash total (CTT02) is the sum of the values of the quantities (FST01) for each FST segment.

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

Total number of line items in the transaction set.

• If CTT03 is present, then CTT04 is required.

73 Summary > SE

SE Transaction Set Trailer

Required · Max use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).

SE-01 · 96 · Number of Included Segments · Required · Numeric (N0) · Min 1 Max 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 4 Max 9

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

GE Functional Group Trailer

Required · Max use 1

To indicate the end of a functional group and to provide control information

GE-01 · 97 · Number of Transaction Sets Included · Required · Numeric (N0) · Min 1 Max 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 1 Max 9

Assigned number originated and maintained by the sender.