ECIA
/
Planning Schedule with Release Capability
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from ECIA. Contact ECIA for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
ECIA

X12 830 Planning Schedule with Release Capability

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with Release Capability Transaction Set (830) 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 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
EDI sample
    View the latest version of this implementation guide as an interactive webpage
    Powered by
    Build EDI implementation guides at stedi.com
    Overview
    ISA
    -
    Interchange Control Header
    Max use 1
    Required
    GS
    -
    Functional Group Header
    Max use 1
    Required
    heading
    ST
    010
    Transaction Set Header
    Max use 1
    Required
    BFR
    020
    Beginning Segment for Planning Schedule
    Max use 1
    Required
    N1 Loop
    GE
    -
    Functional Group Trailer
    Max use 1
    Required
    IEA
    -
    Interchange Control Trailer
    Max use 1
    Required
    ISA

    Interchange Control Header

    RequiredMax use 1

    To start and identify an interchange of zero or more functional groups and interchange-related control segments

    Example
    ISA-01
    I01
    Authorization Information Qualifier
    Required

    Code to identify the type of information in the Authorization Information

    00
    No Authorization Information Present (No Meaningful Information in I02)
    ISA-02
    I02
    Authorization Information
    Required
    Min 10Max 10

    Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

    ISA-03
    I03
    Security Information Qualifier
    Required

    Code to identify the type of information in the Security Information

    00
    No Security Information Present (No Meaningful Information in I04)
    ISA-04
    I04
    Security Information
    Required
    Min 10Max 10

    This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

    ISA-05
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-06
    I06
    Interchange Sender ID
    Required
    Min 15Max 15

    Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

    ISA-07
    I05
    Interchange ID Qualifier
    Required
    Min 2Max 2

    Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

    Codes
    ISA-08
    I07
    Interchange Receiver ID
    Required
    Min 15Max 15

    Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

    ISA-09
    I08
    Interchange Date
    Required
    YYMMDD format

    Date of the interchange

    ISA-10
    I09
    Interchange Time
    Required
    HHMM format

    Time of the interchange

    ISA-11
    I10
    Interchange Control Standards Identifier
    Required

    Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

    U
    U.S. EDI Community of ASC X12, TDCC, and UCS
    ISA-12
    I11
    Interchange Control Version Number
    Required

    This version number covers the interchange control segments

    00401
    Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
    ISA-13
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    ISA-14
    I13
    Acknowledgment Requested
    Required
    Min 1Max 1

    Code sent by the sender to request an interchange acknowledgment (TA1)

    0
    No Acknowledgment Requested
    1
    Interchange Acknowledgment Requested
    ISA-15
    I14
    Usage Indicator
    Required
    Min 1Max 1

    Code to indicate whether data enclosed by this interchange envelope is test, production or information

    I
    Information
    P
    Production Data
    T
    Test Data
    ISA-16
    I15
    Component Element Separator
    Required
    Min 1Max 1

    Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

    >
    Component Element Separator

    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 Code
    Required

    Code identifying a group of application related transaction sets

    PS
    Planning Schedule with Release Capability (830)
    GS-02
    142
    Application Sender's Code
    Required
    Min 2Max 15

    Code identifying party sending transmission; codes agreed to by trading partners

    GS-03
    124
    Application Receiver's Code
    Required
    Min 2Max 15

    Code identifying party receiving transmission. Codes agreed to by trading partners

    GS-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    GS-05
    337
    Time
    Required
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    GS-06
    28
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    GS-07
    455
    Responsible Agency Code
    Required
    Min 1Max 2

    Code used in conjunction with Data Element 480 to identify the issuer of the standard

    T
    Transportation Data Coordinating Committee (TDCC)
    X
    Accredited Standards Committee X12
    GS-08
    480
    Version / Release / Industry Identifier Code
    Required

    Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

    004010
    Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

    Heading

    ST
    010

    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 Code
    Required

    Code uniquely identifying a Transaction Set

    • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
    830
    Planning Schedule with Release Capability
    ST-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    BFR
    020

    Beginning Segment for Planning Schedule

    RequiredMax use 1

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

    Example
    At least one of Reference Identification (BFR-02) or Release Number (BFR-03) is required
    BFR-01
    353
    Transaction Set Purpose Code
    Required

    Code identifying purpose of transaction set

    • If BFR01 contains the value "04" (Net Change), BFR09 is required.
    05
    Replace
    BFR-02
    127
    Reference Identification
    Optional
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    • BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.
    BFR-03
    328
    Release Number
    Optional
    Min 1Max 30

    Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

    BFR-04
    675
    Schedule Type Qualifier
    Required

    Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast

    DL
    Delivery Based
    SH
    Shipment Based
    BFR-05
    676
    Schedule Quantity Qualifier
    Required

    Code identifying the type of quantities used when defining a schedule or forecast

    A
    Actual Discrete Quantities
    BFR-06
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BFR06 is the forecast horizon start date: The date when the forecast horizon (envelope) begins.
    BFR-07
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends.
    BFR-08
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • BFR08 is the date forecast generated: The date the forecast data was generated.
    N1 Loop
    RequiredMax >1
    N1
    230

    Name

    RequiredMax use 1

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

    Usage notes

    The N1 at the header level applies to all items (LIN) contained at the detail level.

    Example
    At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
    If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
    N1-01
    98
    Entity Identifier Code
    Required

    Code identifying an organizational entity, a physical location, property or an individual

    ST
    Ship To
    N1-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    N1-03
    66
    Identification Code Qualifier
    Optional

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

    1
    D-U-N-S Number, Dun & Bradstreet
    9
    D-U-N-S+4, D-U-N-S Number with Four Character Suffix
    91
    Assigned by Seller or Seller's Agent
    92
    Assigned by Buyer or Buyer's Agent
    N1-04
    67
    Identification Code
    Optional
    Min 2Max 80

    Code identifying a party or other code

    • 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.
    PER
    280

    Administrative Communications Contact

    OptionalMax use 3

    To identify a person or office to whom administrative communications should be directed

    Example
    If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
    PER-01
    366
    Contact Function Code
    Required

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

    BD
    Buyer Name or Department
    PER-02
    93
    Name
    Optional
    Min 1Max 60

    Free-form name

    PER-03
    365
    Communication Number Qualifier
    Optional

    Code identifying the type of communication number

    TE
    Telephone
    PER-04
    364
    Communication Number
    Optional
    Min 1Max 80

    Complete communications number including country or area code when applicable

    Detail

    LIN Loop
    RequiredMax >1
    LIN
    010

    Item Identification

    RequiredMax use 1

    To specify basic item identification data

    Usage notes

    If only the vendor part number (VP) is available, then send it in the first occurrence and float up all other remaining information.

    Example
    If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
    If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
    If either Product/Service ID Qualifier (LIN-08) or Product/Service ID (LIN-09) is present, then the other is required
    LIN-01
    350
    Assigned Identification
    Optional
    Min 1Max 20

    Alphanumeric characters assigned for differentiation within a transaction set

    • LIN01 is the line item identification
    LIN-02
    235
    Product/Service ID Qualifier
    Required

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

    • LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
    BP
    Buyer's Part Number
    LIN-03
    234
    Product/Service ID
    Required
    Min 1Max 48

    Identifying number for a product or service

    LIN-04
    235
    Product/Service ID Qualifier
    Optional

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

    EC
    Engineering Change Level
    LIN-05
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    LIN-06
    235
    Product/Service ID Qualifier
    Optional

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

    VP
    Vendor's (Seller's) Part Number
    LIN-07
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    LIN-08
    235
    Product/Service ID Qualifier
    Optional

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

    PO
    Purchase Order Number
    LIN-09
    234
    Product/Service ID
    Optional
    Min 1Max 48

    Identifying number for a product or service

    UIT
    020

    Unit Detail

    RequiredMax use 1

    To specify item unit data

    Example
    UIT-01
    C001
    Composite Unit of Measure
    To identify a composite unit of measure (See Figures Appendix for examples of use)
    C001-01
    355
    Unit or Basis for Measurement Code
    Required

    Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

    EA
    Each
    PC
    Piece
    FST Loop
    RequiredMax >1
    FST
    410

    Forecast Schedule

    RequiredMax use 1

    To specify the forecasted dates and quantities

    • At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. These two loops are mutually exclusive.
    Example
    If either Date/Time Qualifier (FST-06) or Time (FST-07) is present, then the other is required
    If either Reference Identification Qualifier (FST-08) or Reference Identification (FST-09) is present, then the other is required
    FST-01
    380
    Quantity
    Required
    Min 1Max 15

    Numeric value of quantity

    FST-02
    680
    Forecast Qualifier
    Required

    Code specifying the sender's confidence level of the forecast data or an action associated with a forecast

    • 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
    D
    Planning
    FST-03
    681
    Forecast Timing Qualifier
    Required

    Code specifying interval grouping of the forecast

    • If FST03 equals "F" (indicating flexible interval), then 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
    Discrete
    F
    Flexible Interval (from Date X through Date Y)
    M
    Monthly Bucket (Calendar Months)
    W
    Weekly Bucket (Monday through Sunday)
    FST-04
    373
    Date
    Required
    CCYYMMDD format

    Date expressed as CCYYMMDD

    FST-05
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    Usage notes

    Not required except for flexible interval – so not recommended.

    FST-06
    374
    Date/Time Qualifier
    Optional
    Min 3Max 3

    Code specifying type of date or time, or both date and time

    • FST06 qualifies the time in FST07. The purpose of the FST07 element is to express the specific time of day in a 24-hour clock to satisfy "just-in-time" requirements. As an alternative, the ship/delivery pattern segment (SDP) may be used to define an approximate time, such as a.m. or p.m.
    Usage notes

    If specific time is needed, can be used. Not recommended.

    FST-07
    337
    Time
    Optional
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    Usage notes

    Not recommended.

    FST-08
    128
    Reference Identification Qualifier
    Optional

    Code qualifying the Reference Identification

    PO
    Purchase Order Number

    If embedded releases with new purchase order is used in this process. Should only be provided here if firm schedule with its own purchase order identifier.

    FST-09
    127
    Reference Identification
    Optional
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    Usage notes

    Purchase Order identifier indicate for firm schedule with new purchase order.

    SHP Loop
    RequiredMax >1
    SHP
    470

    Shipped/Received Information

    RequiredMax use 1

    To specify shipment and/or receipt information

    Example
    If Quantity Qualifier (SHP-01) is present, then Quantity (SHP-02) is required
    If Date (SHP-04) is present, then Date/Time Qualifier (SHP-03) is required
    If Date/Time Qualifier (SHP-03) is present, then Date (SHP-04) is required
    If Date/Time Qualifier (SHP-03) is present, then at least one of Date (SHP-04) or Time (SHP-05) is required
    If Time (SHP-05) is present, then Date/Time Qualifier (SHP-03) is required
    SHP-01
    673
    Quantity Qualifier
    Optional

    Code specifying the type of quantity

    • If SHP01 equals "02", "07", "08", "09", or "10" (indicating cumulative quantities), then SHP04 and SHP06 are required to identify the start and end dates of the quantity count.
    01
    Discrete Quantity
    02
    Cumulative Quantity
    SHP-02
    380
    Quantity
    Optional
    Min 1Max 15

    Numeric value of quantity

    SHP-03
    374
    Date/Time Qualifier
    Optional

    Code specifying type of date or time, or both date and time

    050
    Received
    051
    Cumulative Quantity Start
    SHP-04
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • SHP04 is the date shipped, delivered, received, or the cumulative quantity start date (as qualified by SHP03).
    SHP-05
    337
    Time
    Optional
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    SHP-06
    373
    Date
    Optional
    CCYYMMDD format

    Date expressed as CCYYMMDD

    • SHP06 is the cumulative quantity end date.
    SHP-07
    337
    Time
    Optional
    HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

    Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

    REF
    480

    Reference Identification

    OptionalMax use 5

    To specify identifying information

    Example
    REF-01
    128
    Reference Identification Qualifier
    Required

    Code qualifying the Reference Identification

    SI
    Shipper's Identifying Number for Shipment (SID)
    REF-02
    127
    Reference Identification
    Optional
    Min 1Max 30

    Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

    Summary

    CTT
    010

    Transaction Totals

    RequiredMax 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.
      If used, hash total (CTT02) is the sum of the values of the quantities (FST01) for each FST segment.
    Example
    CTT-01
    354
    Number of Line Items
    Required
    Min 1Max 6

    Total number of line items in the transaction set

    CTT-02
    347
    Hash Total
    Optional
    Min 1Max 10

    Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.

    ## Example:
    -.0018 First occurrence of value being hashed.
    .18 Second occurrence of value being hashed.
    1.8 Third occurrence of value being hashed.
    18.01 Fourth occurrence of value being hashed.

    1855 Hash total prior to truncation.
    855 Hash total after truncation to three-digit field.

    SE
    020

    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 (ST) and ending (SE) segments)

    Example
    SE-01
    96
    Number of Included Segments
    Required
    Min 1Max 10

    Total number of segments included in a transaction set including ST and SE segments

    SE-02
    329
    Transaction Set Control Number
    Required
    Min 4Max 9

    Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

    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
    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
    Group Control Number
    Required
    Min 1Max 9

    Assigned number originated and maintained by the sender

    Interchange Control Trailer

    RequiredMax use 1

    To define the end of an interchange of zero or more functional groups and interchange-related control segments

    Example
    IEA-01
    I16
    Number of Included Functional Groups
    Required
    Min 1Max 5

    A count of the number of functional groups included in an interchange

    IEA-02
    I12
    Interchange Control Number
    Required
    Min 9Max 9

    A control number assigned by the interchange sender

    EDI Samples

    Sample

    BFR*05**366*DL*A*20101019*20110831*20101205
    N1*ST*company name*91*1234
    LIN*001*BP*PN12345*EC*001*VP*12345-6*PO*123456789
    UIT*PC
    FST*258*C*D*20101019
    FST*52*C*D*20101101
    FST*324*C*D*20101108
    FST*463*C*D*20101129
    FST*59*D*W*20110117
    FST*54*D*W*20110124
    FST*183*D*W*20110221
    FST*63*D*W*20110228
    FST*30*D*W*20110321
    FST*82*D*W*20110328
    FST*176*D*M*20110430
    FST*557*D*M*20110531
    FST*122*D*M*20110630
    FST*454*D*M*20110731
    FST*266*D*M*20110831
    FST*0*D*M*20110930
    SHP*01*912*050*20100810
    REF*SI*7891234
    SHP*01*912*050*20100622
    REF*SI*7891521
    SHP*02*6234*051*20100101**20101018
    CTT*1

    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.