Creating Planning Instance Definitions
To create planning instance definitions, use the Problem Instance Definition component.
This topic provides an overview of planning instance IDs and discusses how to create new planning instance IDs.
|
Page Name |
Definition Name |
Usage |
|---|---|---|
|
PL_PROBINST_DEF |
Create new planning instances. |
Planning instance IDs define a complete set of data analyzed to create a feasible supply plan. When you create a planning instance ID, define which inventory business unit group and which items you want to include in the planning model. When you run the Load Planning Instance process (PL_LOAD_OPT), you incorporate into the planning instance business unit data such as calendars and business unit planning options; item-specific data such as item planning options, inventory positions, sourcing options, supplies, and demands; and capacity-specific data such as work-center capacity definitions. All PeopleSoft Supply Planning occurs within a planning instance.
The Planning Instance table (PL_PROBINST) contains information pertaining to the state of the planning instance and the data that it comprises, including the types of data loaded, the range of dates used to select data, and global attributes used by the planning solvers.
Planning Instance Locks
The system locks the planning instance data tables at the beginning of the Load Planning Instance process to prevent two processes from updating the same subset of the planning instance concurrently. It releases the locks only if the process terminates normally. If the process terminates, release these locks manually on the Planning Instance Lock page, where you can also verify that a Load Planning Instance process is not currently running for a planning instance.
Planning Instance Inquiry
PeopleSoft Supply Planning provides a planning instance inquiry component to enable you to view the data that is used to create the corresponding planning instance dataset and view the current planning instance attributes.
Safety Stock Option
In SCM Inventory, you can define stock period for an item. A stocking period consists of start time and end time, safety level, excess level, safety limit, and excess limit. Safety limit is the lower bound of the safety stock, and excess limit is the upper bound of the safety stock. Safety and excess levels are the preferred safety stock level and excess stock level. For planning, stocking period’s start and end time and safety limit are the only concerns when solving for the safety stock demand.
Since a planning instance has a start and end time, and early fence and late fence where the demands are planned, the stock periods will be processed, so only those falling inside the planning horizon will be processed.
Planning always takes the start time of the stock periods, and the increased safety stocking level as demand when planning its supplies. In addition, when considering early fence, late fence and item phase out date, the safety stock demand date is further adjusted when its period lands on those dates.
PeopleSoft Supply Planning provides a safety stock flag, which is global for planning instance, and is applied to all the Show Demand places. This flag is passed to plugin for Show Demand’s transaction to process. To read in the changed flag, shutting down the engine is not required. The default for this flag is “Fulfill”.
In either MRP or Feasible solver, the safety stock is fulfilled using the start time of stocking period and increased safety limit quantity from the previous highest safety limit, except the first period. First period’s safety stock demand is the safety limit quantity. There are some special handlings with regard to the safety stock demand date as discussed below. This special handling also depends on safety stock setting in MRP Solver run control and Feasible Solver run control. There are three selections that a user can pick when considering the safety stock:
Fulfill
This setting ensures the solver to fulfill the safety stock from the planning period start, or the early fence when the demand is considered. All stocking periods outside of the planning period are discarded. For periods that lands in the early fence, its start time will be adjusted to the early fence. For the period that lands on the late fence, its end date will be adjusted to the late fence. An existing item phased out date overrides the late fence and changes the end time for considering the stock period to the phased out date, if it is earlier then the late fence.
The system uses the same logic in Show Demand for Fulfill setting.
Ignore until First Demand
This setting ensures the solver to delay considering the safety stock until it sees the first demand. That is, not to solve plan just for safety stock. With this setting, the demand date for the first safety stock period is adjusted to the first demand date.
The system uses the same logic in Show Demand for Ignore until First Demand setting.
Ignore
This setting ensures the solver to completely ignore the safety stock demand.
The system uses the same logic in Show Demand for Ignore.
Use the Planning Instance page
Navigation:
This example illustrates the fields and controls on the Planning Instance Page. You can find definitions for the fields and controls later on this page.
Field or Control |
Description |
|---|---|
Status |
Displays the status of the Planning Instance Load process for the corresponding planning instance ID or the last major data exchange that occurred for the planning instance. |
Safety Stock Option |
Select the desired safety stock option from:
|
Planned By Type |
Select only those items that are associated with the specified planned by types. |
Note: A change to the item selection criteria has no effect on the next regenerative select or net change Load Planning Instance process run. Field values in the Item Selection group box apply to full regenerations only.