EDI 830 Planning Schedule with Release Capability

Functional Group PS

X12M Supply Chain Subcommittee

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.

Share via email

Heading

Position
Segment
Name
Max use

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

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

  3. To transmit information in a free-form format, if necessary, for comment or special instruction

  4. To specify the currency (dollars, pounds, francs, etc.) used in a transaction

  5. To specify identifying numbers.

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

  7. To provide data required for proper notification/determination of applicable taxes applying to the transaction or business described in the transaction

  8. To specify transportation instructions relating to shipment

  9. N1 Loop Optional
    Repeat 200

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

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

    3. To specify the location of the named party

    4. To specify the geographic place of the named party

    5. To specify identifying numbers.

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

    7. To specify transportation instructions relating to shipment

  10. To specify pricing information

  11. To specify special conditions or services associated with the purchased product

  12. To specify general conditions or requirements of the sale

  13. To specify terms of sale.

  14. To specify pertinent dates and times

  15. To describe a product or process in coded or free-form format

  16. To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001.)

  17. To identify the type and transmission of paperwork or supporting information

  18. To describe marking, packaging, loading and unloading requirements.

  19. To specify the transportation details relative to commodity, weight and quantity.

  20. To specify the carrier, sequence of routing and to provide transit time information

  21. To specify transportation details relating to the equipment used by the carrier.

  22. To specify transportation special handling requirements or hazardous materials information or both

  23. To indicate identifying marks and numbers for shipping containers

Detail

Position
Segment
Name
Max use
  1. LIN Loop Mandatory
    Repeat 10000

    1. To specify basic item identification data.

    2. To specify item unit data

    3. To specify pertinent dates and times

    4. To specify the currency (dollars, pounds, francs, etc.) used in a transaction

    5. To specify additional item related data involving variations in normal price/quantity structure.

    6. To specify pricing information

    7. To describe a product or process in coded or free-form format

    8. To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001.)

    9. To identify the type and transmission of paperwork or supporting information

    10. To describe marking, packaging, loading and unloading requirements.

    11. To specify the physical qualities, packaging, weights and dimensions relating to the item.

    12. To indicate the status of the part being ordered or forecast with respect to this material release or planning document.

    13. To specify identifying numbers.

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

    15. To specify special conditions or services associated with the purchased product

    16. To specify allowances, charges or services

    17. To specify terms of sale.

    18. To provide data required for proper notification/determination of applicable taxes applying to the transaction or business described in the transaction

    19. To specify transportation instructions relating to shipment

    20. To specify lead time for availability of products and services.

    21. To specify quantity information.

      QTY is used to specify supplemental quantities relevant to the forecast function. However, QTY is not related to the actual forecast quantity in the FST segments.
    22. SLN Loop Optional
      Repeat 100

      1. To specify product subline detail item data

      2. To describe a product or process in coded or free-form format

    23. N1 Loop Optional
      Repeat 200

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

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

      3. To specify the location of the named party

      4. To specify the geographic place of the named party

      5. To specify identifying numbers.

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

      7. To specify transportation instructions relating to shipment

    24. FST Loop Optional
      Repeat 260

      1. To specify the forecasted dates and quantities

        At least one occurence of segment FST is required, either in the FST loop or within the SDP loop. These two loops are mutually exclusive.

      2. To specify destination and quantity detail.

    25. SDP Loop Optional
      Repeat 260

      1. To identify specific ship/delivery requirements

      2. To specify the forecasted dates and quantities

    26. To specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule.

    27. SHP Loop Optional
      Repeat 25

      1. To specify shipment and/or receipt information

      2. To specify identifying numbers.

    28. To specify the transportation details relative to commodity, weight and quantity.

    29. To specify the carrier, sequence of routing and to provide transit time information

    30. To specify transportation details relating to the equipment used by the carrier.

    31. To specify transportation special handling requirements or hazardous materials information or both

    32. To indicate identifying marks and numbers for shipping containers

Summary

Position
Segment
Name
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. If used, hash total (CTT02) is the sum of the values of the quantities (FST01) for each FST segment.

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

Stedi.comDocumentationContact us

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site 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. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.