PeopleSoft Supply Planning Preface

This preface discusses:

Note. PeopleSoft Supply Planning is a web-based planning system that enables simultaneous optimization of plant-level transfers, procurement, and production. Using a material planning solver, the application creates a material plan to give an accurate picture of the lead time and materials necessary to satisfy all of the demands. The solver is based on the concepts found in traditional material requirements planning (MRP)–low-level codes, single sourcing, and lead times.

PeopleSoft Supply Planning also includes a material and capacity feasible solver, and an enterprise material and capacity feasible solver. The solvers look at alternate sources of supply, consider capacity, and focus on customer service based on demand priorities throughout the entire supply chain.

PeopleBooks document only page elements that require additional explanation. If a page element is not documented with the process or task in which it is used, then either it requires no additional explanation or it is documented with common elements for the section, chapter, PeopleBook, or product line. Elements that are common to all PeopleSoft applications are defined in this preface.

Click to jump to parent topicPeopleSoft Products

This PeopleBook refers to these Oracle products:

Click to jump to parent topicPeopleSoft Application Fundamentals

Oracle's PeopleSoft Supply Planning PeopleBook provides you with implementation and processing information for Oracle's PeopleSoft Supply Chain Management system. However, additional, essential information describing the setup and design of the system resides in companion documentation, Oracle's PeopleSoft Application Fundamentals PeopleBook. The companion documentation consists of important topics that apply to many or all of Oracle's PeopleSoft applications across the PeopleSoft Financials, Enterprise Service Automation, and Supply Chain Management product lines. You should be familiar with the contents of this PeopleBook.

Click to jump to parent topicPages With Deferred Processing

Several pages in Oracle's PeopleSoft Supply Planning operate in deferred processing mode. Most fields on these pages are not updated or validated until you save the page or refresh it by clicking a button or link or selecting a tab. This delayed processing has various implications for the field values on the page. For example, if a field contains a default value, any value that you enter before the system updates the page overrides the default. Another implication is that the system updates quantity balances or totals only when you save or otherwise refresh the page.

See Also

PeopleTools: PeopleSoft Application Designer Developer's Guide PeopleBook

Click to jump to parent topicCommon Elements Used in This PeopleBook

These elements are common to multiple pages in PeopleSoft Supply Planning.

As of Date

The last date for which a report or process includes data.

Business Unit

An identification code that represents a high-level organization of business information. Use a business unit to define regional or departmental units within a larger organization.

When populating this field on a search criteria page, select a value to include items associated with a specific business unit. Leave this field blank to include all of the business units associated with the problem instance.

Buying Agreement

A schedule between you and the customer defining terms and conditions. Buying agreements enable you to define beginning dates, ending dates, and maximum amounts; specify the minimum dollar value per order placed, as well as the maximum and minimum line item ordering quantities for each line item; define shipping defaults for all sales orders, as well as all products and product groups to be included; define special pricing terms for a customer or customer group; generate sales orders automatically when customers know in advance when products are needed; create sales orders in situations where shipment scheduling is unknown and create rebates and penalties.

Capacity Fence

Represents the date and time that solvers begin ignoring capacity violations. Solvers do not use plan for capacity or report-on capacity-type exceptions after the capacity fence.

The capacity fence should occur between the current time and the end of time. If you define the capacity fence as current time, solvers attempt no capacity smoothing. The default value for capacity fence is end of time.


Category information helps to reduce redundant data entry during both item setup, requisition, and purchase order processing. The system assigns the purchasing attributes of an item category as defaults to any item in that category. Item categories can provide transaction information for requisitions, requests for quotes, contracts, and purchase orders. Item categories also serve as the organizational unit for item catalogs; item catalogs are a collection of item categories. The system adds each item added to a category to each catalog that contains that category.

If the installation includes PeopleSoft Purchasing, you must create categories for the items. You are required to assign new items to a category on the Define Item - General: Common page.

When populating this field on a search criteria page, select a value to include only those items associated with a specific item category.

Configuration Code

Configuration codes are 50-character, alphanumeric identifiers for configured items. The system automatically generates configuration codes as you configure items, using information about the customer's selections that you define as elements of the code. Configuration codes enable you to identify the options for a configured item easily.

You can also use configuration codes to track and cost configured inventory. After you define the elements of the configuration code for an item, the system automatically assigns a configuration code to each product that it configures during distribution configuration. When configured items pass to PeopleSoft Inventory, they are put away and shipped in lots that carry that same configuration code. In addition, because lots are linked through the configuration code to the cost information, you have access to standard costing data for the configuration.

When populating this field on a search criteria page, select a value to include only those items associated with a specific configuration code.

See Working With Configuration Codes.

Customer Order

A general demand category to cover all of the customer demand transaction types, including sales orders, quotes, and buying agreements.

Current Date/Time

Each planning instance contains a base date and time known as current date and time. All of the other fences and horizons are specified as offsets to this base date. It is not related to the actual (or system date and time) except when the system date and time is used as a default for specifying the current date and time

Demand Date

Displays the requested or scheduled ship date and represents the date on which customer order demand is recognized. Solvers attempt to satisfy the demand on the selected date.

Demand Time Fence (Item Level)

Identifies the point in time that forecasts for an item are to be considered and consumed. Before this fence, only actual orders (and quotes) are considered as demand.

The demand time fence should be at or greater than current time


Enter up to 30 characters of text.

Early Fence

This time fence represents the beginning time at which solvers can actively change the supply plan to make it material- and capacity-feasible. Usually, you set the early fence to the first date that you can accommodate changes in the supply plan.

Before the early fence, solvers cannot:

  • Create any new supply with a start time before the early fence.

  • Reschedule current tasks that have a start time before the early fence.

  • Reschedule existing tasks starting after the early fence to start before the early fence.

  • Cancel current tasks that have a start time before the early fence.

The early fence must occur between the start of time and the end of time.

Effective Date

Date on which a table row becomes effective; the date that an action begins. For example, to close out a ledger on June 30, the effective date for the ledger closing would be July 1. This date also determines when you can view and change the information. Pages and batch processes that use the information, use the current row.

End of Time (End Fence)

This fence represents the concluding time boundary. PeopleSoft Supply Planning solvers do not recognize orders or changes after this date.

The end date and time fence must occur at or after the current date and time.


In PeopleSoft Inventory, you can categorize items by groups and families. No formal relationship exists between item groups and item families, but you can use an item family to further classify an item group. For example, you can further define the hardware group as consisting of families of fresh-water equipment and salt-water equipment.

When populating this field on a search criteria page, select a value to include only those items associated with a specific item family.

Forecast Fulfillment Fence

If a solver cannot fulfill a forecast demand before this fence, it ignores the forecast demand. The forecast fulfillment fence must exist after the start of time and at or before the end of time. The default value is the current date

Forecast Source

Specify the data source for item forecasts. If the data source is the inventory system, you must also specify a forecast set. If the forecast data originated in Demantra Demand Management, you must also specify the name and date of a published forecast contained in PeopleSoft Publish Forecast tables. These tables are available in the Advanced Planning component.

See Integrating with Oracle's Demantra Demand Management.

Include Quantity

Select to include the order in all of the planning functions. The system populates this field by default. This option enables you to load an order in PeopleSoft Supply Planning and ignore the order during simulations.

If you do not select this option, the order appears on the corresponding maintenance page only; the order does not appear on workbenches or reports and is ignored by solvers.

Item Group

A grouping of items that enable you to design the accounting structure for a group of similar items, such as sporting equipment or dress shoes. The item group is attached to an item using the Item Definition - General page.

When populating this field on a search criteria page, select a value to include only those items associated with a specific item group.

Item ID

Represents the unique identifier that the system uses to track and retrieve an item.

When populating this field on a search criteria page, select a value to include only the item specified. If you do not enter a value in this field on a search criteria page, the system includes all of the items in the business unit that meet the specified search criteria.

Late Fence

Used as a reporting fence. PeopleSoft Supply Planning does not consider exceptions that occur after the late fence in any metrics used to analyze plan quality. The late fence must occur after the early fence and at or before the end of time. The default value for late fence is end of time.

Note. All of the solvers net supply and demand and create new supplies through the end of time fence.

Once, Always, and Don't Run

Select Once to run the request the next time the batch process runs. After the batch process runs, the process frequency is automatically set to Don't Run.

Select Always to run the request every time the batch process runs.

Select Don't Run to ignore the request when the batch process runs.

Planned By

Indicate whether you want the system to include items or exceptions that have been defined in either the material plan, master plan, distribution plan, or any combination. When processing requests, the system includes only those items or exceptions associated with the specified planned-by types.

Planner Code

Represents the name of a specific planner. Use planner codes to provide access to information more efficiently and filter information in most pages and processes.

When populating this field on a search criteria page, select a value to include only those items associated with a specific planner.

Planning Instance ID

Represents a complete set of data within the PeopleSoft Optimization framework. You define planning instance IDs on the Planning Instance Definition page.

The system uses planning instance default values on any page where the field is available for entry. The system uses the value that you defined for the planning instance on the User Preferences - Planning page. Otherwise, it uses the value that you defined on the Installation Options - Planning page.

See Creating Planning Instance Definitions.

Plan Unit Group

Select the plan unit group that you want to associate with the planning instance. You define business unit groups on the Business Unit Group Definition page. A business unit group represents all of the business units that you want to include in a planning instance. This field is required.

See Setting Up Business Unit Groups.

Process Monitor

Click to access the Process List page, where you can view the status of submitted process requests.

Quantity On Hand Date/Time

Represents the date and time for which the item and business unit quantity on-hand values are calculated. This value is often equal to the system date and time when you ran the Load Planning Instance process (PL_LOAD_OPT).

While the system calculates the quantity on hand date for each item in a sequential order, it applies the same quantity on hand date to all of the items. The system considers all of the orders before this date and time are past due.

Report Manager

Click to access the Report List page, where you can view report content, check the status of a report, and see content detail messages (which show you a description of the report and the distribution list).

Request ID

An ID that represents a set of selection criteria for a report or process.

Round Component Demand

Select to round a component demand. This option overrides the component rounding option on the item master. Use this option to prevent the accumulation of rounding errors.

Maintain this option at the business unit level.


Click to access the Process Scheduler request page, where you can specify the location where a process or job runs and the process output format.

Run Lateness/Stock Phase

The Feasible solver performs an exhaustive search to determine all of the possible methods to source the end item and meet the end demand on time. The Feasible solver lateness repair considers late demands in priority order, working on intolerably late orders first. The solver attempts to meet the demand on time. If it cannot, it attempts to meet the demand as close as possible to the due date; failing that, the solver attempts to reduce the lateness of the order as much as possible.

The Feasible solver stock adjustment phase attempts to reduce temporary excess by scheduling supplies just in time for their demands while maintaining capacity. In addition, it attempts to restore any missed safety stock periods by scheduling late any demands that are a lower priority than safety stock.


An ID that represents a set of control table information, or TableSets. TableSets enable you to share control table information and processing options among business units. The goal is to minimize redundant data and system maintenance tasks. When you assign a setID to a record group in a business unit, you indicate that all of the tables in the record group are shared between that business unit and any other business unit that also assigns that setID to that record group. For example, you can define a group of common job codes that are shared between several business units. Each business unit that shares the job codes is assigned the same setID for that record group.

Short Description

Enter up to 15 characters of text.

Start of Time (Start Fence)

This time fence represents the beginning time boundary, before which time does not exist. Used with the end of time, the region defines the time period within which the system recognizes orders and changes. PeopleSoft Supply Planning solvers do not recognize orders and changes before start of time.

Define the start of time fence far enough in the past to ensure that the start date for all in-process production orders are included.

User ID

An ID that represents the person who generates a transaction.

Utilization Type

Classifies inventory items based on their demand and usage. When populating this field on a search criteria page, select a value to include only those items associated with a specific item utilization type.

Vendor Location

Select a vendor location. When purchasing items from a vendor who has multiple locations, you can, for example, select a location with the shortest lead time.

Request ID

Enter a request identification to represent the set of selection criteria for this process.

Click to jump to parent topicPeopleBooks and the PeopleSoft Online Library

A companion PeopleBook called PeopleBooks and the PeopleSoft Online Library contains general information, including:

You can find PeopleBooks and the PeopleSoft Online Library in the online PeopleBooks Library for your PeopleTools release.