Common Elements Used to Understand the Plan Generation Process
Field or Control |
Description |
|---|---|
Allow Item Substitution |
Select to enable the Feasible solver to use substitute items to correct material inversions. When you select this option, the solver tries to reallocate the supply of a valid substitute item from the bill of materials. If you do not select this option, the solver makes no substitutions during solver processing. |
Allow Rescheduling |
Select to enable the Feasible solver to reschedule tasks when resolving late supply violations. Note: You must select Allow Rescheduling to ensure a feasible capacity plan during plan processing. In case of frozen demand, the supply is scheduled earlier if the demand cannot be made on time. In all other cases, the default behavior schedules the demand later. |
Calculate Low Level Codes |
Select to verify the accuracy of low-level codes. When you select this option, the system calculates the low-level code for each item prior to the solver run. Low level codes are numbers that identify the lowest level in a BOM at which a component appears. These codes are maintained on items and calculated by the planning engine. PeopleSoft Supply Planning explodes the demand for an item by level code, from top to bottom until all of the demand is exploded, then creates supply for all of the exploded demand. The system assigns level code to each item in the structure. Items that are assigned at the top level code are those that are highest on the supply chain, those normally shipped to the customer, and are denoted as level 0. Items with larger level code numbers exist at a lower level in the product structure. Note: Solvers plan items in low-level code order. Ensure that the low-level code that is associated with each item is accurate before you run a solver, especially if you have made BOM changes. |
Reconsume Forecast |
Select to reconsume the forecast. The system consumes forecast when you load the model into memory the first time. However, if you add more demands to the model on any of the Refine Plan components, you might need to reconsume these demands. |
Start Planning Engine and URL |
Select to start the planning engine for the corresponding planning instance prior to running the solver. If the planning engine is already running, the system ignores this option and uses the domain on which the planning engine is currently running to run the solver. If you select Start Planning Engine and the planning engine is not currently running, the system starts the planning engine for the corresponding planning instance using the domain that you specify in the URL field. If you specify no domain, or if the planning engine fails to start on the domain that you specify in the URL field, the system uses the default URL that you define on the Planning Engine Domains page. |
Violation Count Collection |
Select Pre-Solver Violations and Post-Solver Violations to save violation counts before and after a solver runs. You cannot specify filters. |