Planning Engine (plaps0110m000)
Use this session to view the planning engine and configure applicable parameters.
Field Information
- GUID
- The GUID code.
- Name
- The name or code of the planning engine.
- Scenario
- The code of the scenario.
- Planning Start Date
- The date on which planning is started.
- Status
-
The status of the planning engine.
Allowed values
- Initial
- Running
- Completed
- Failed
- Weights ID
- Path
- The location path of the planning engine.
- Run Number
- Planning Updated On
- The date and time when the planning information is last updated.
- Planning Engine Progress
- The current progress of the planning engine.
- Consistent Dispatching
- The time period for consistence dispatching.
- Due Date Respect
- The time period for due date respect.
- Setup Optimization
- The time period for set up optimization.
- Material
-
The type of material availability the planning engine to consider when creating a plan.
Allowed values
- Finite
- Infinite
- Capacity
-
The type of capacity availability the planning engine to consider when creating a plan.
Allowed values
- Finite
- Infinite
- Site Selection
-
The site to be considered by the planning engine.
Allowed values
- All Sites
- Selected Sites
- Selected Site Groups
- Gradation Weight
- The factor used to convert the setup state gradation level into a comparable time unit.
- Setup Grouping Period
- Constraint Threshold
-
The time period after which a supply order step is considered as constrained.
Note:
- You can view which supply orders are constrained when reviewing supply orders in a supply network. However, you can only consider late orders as constrained.
- The Supply Order step is not constrained if planned date < due date + PE_CONSTRAINT_THRESHOLD.
- Priority Factor if Allocated to Customer Demand
-
The priority of the customer order.
Note:
- This field determines the factor corresponding to: "How many times more important is a supply order allocated to a customer order/warehouse demand order than a supply order allocated to a forecast".
- If the field value is set to 1, the supply order steps for CO lines, or warehouse demand orders to be equivalent to forecast orders.
- If the field value is set to 2, the CO lines, or warehouse demand orders have twice the priority.
- Synchronize Purchase Orders
-
If this field is set to Yes, and a production order is late due to planning constraints, Planner postpones a planned or firm-planned purchase order that is allocated to that production order.Note: If this field is set to No, and a production order is late due to planning constraints, Planner does not postpone planned or firm-planned purchase orders that are allocated to that production order.
- Use Requirement Engine
-
...
- Detailed Logging
-
If this field is set to Yes, detail logging is enabled.
- Integration Date at the Last Planning Engine Run
-
The date of the last planning engine run.
Note: The Planning engine updates each time when a Planning engine run is completed.
- Last Planning Engine Run Start Date
- The start date of the last planning engine run.
- Last Planning Engine Run End Date
- The completion date of the last planning engine run.
- Last Planning Engine Run Duration
- The time taken for the last Planning Engine run to complete.
- PO After CTF Count
- MO DO After CTF Count
- Due Date Respect Threshold
- The maximum lateness duration during which the PE due date respect evaluation function calculates the due date scores using a linear curve.
- Backward Scope
- The time period for backward scope.
- Forward Scope
- The time period for forward scope.
- Synchronize Scope
- The number of supply order steps that the Planning Engine simultaneously evaluates and compares during synchronization phase.
- Allocate Validate Scope
- The number of supply order steps that the Planning Engine simultaneously evaluates and compares during the allocation validation phase. This value is defaulted from the Planning Engine Parameters (plaps0120m000) session.
- Infinite Purchase
-
If this field is set to Yes, the purchased items are planned in infinite material.
- Move Released MO
-
The type of released manufacturing order steps to transfer when constraints are encountered.
Allowed values
- For capacity
- For Capacity inside FTF; always outside
- Always
- Frozen
- Frozen inside FTF; always outside
- Frozen inside FTF; for capacity outside
- MT_AlwaysNoExpediteCompress
- Move Released DO
-
The type of released demand order steps to transfer when constraints are encountered.
Allowed values
- For capacity
- For Capacity inside FTF; always outside
- Always
- Frozen
- Frozen inside FTF; always outside
- Frozen inside FTF; for capacity outside
- MT_AlwaysNoExpediteCompress
- Move Confirmed MO
-
The type of confirmed manufacturing order steps to transfer when constraints are encountered.
Allowed values
- For capacity
- For Capacity inside FTF; always outside
- Always
- Frozen
- Frozen inside FTF; always outside
- Frozen inside FTF; for capacity outside
- MT_AlwaysNoExpediteCompress
- Move Confirmed DO
-
The type of confirmed demand order steps to transfer when constraints are encountered.
Allowed values
- For capacity
- For Capacity inside FTF; always outside
- Always
- Frozen
- Frozen inside FTF; always outside
- Frozen inside FTF; for capacity outside
- MT_AlwaysNoExpediteCompress
- Move Released SO
-
If this check box is selected, the planning engine moves the released substitution orders in the same way as firm-planned and planned substitution orders.
- Move Confirmed SO
-
If this check box is selected, the planning engine moves confirmed substitution orders in the same way as firm-planned and planned substitution orders.
- Push Unconfirmed Released PO
-
The scenario in which Purchase Orders without a confirmed delivery date to transfer.
Allowed values
- Never
- The planning engine sets the planned delivery date to the due delivery date.
- No Confirmed Date
- A released purchase order moves only when the confirmed delivery date is not specified. The Due end date must be within NOW + Supply time + Safety time.
- No Confirmed or Changed Date
- A released purchase order moves only when the Confirmed Delivery Date or Changed Delivery Date is not specified. The Due end date must be within NOW + Supply time + Safety time.
- Material Constraint Generation
-
The method used to generate material constraints during a Planning Engine run.
Allowed values
- No Constraint
- The material constraints are not generated.
- Finite Plan
-
The material constraints are identified in the finite plan by evaluating material demand by due date.
A material constraint is generated when finite-plan supply does not meet material demand on the due date.
Material demands are evaluated sequentially by planned date by using forward scanning in the finite plan.
With this method, material constraints are generated only for purchased items.
Subassemblies are not identified as material constraints.
A material constraint is generated when the producing manufacturing order step is released or confirmed and cannot be moved.
- Infinite Plan
-
The material constraints are generated when demand is not satisfied on the requested due date. Generated constraints include a used date and an available date.
Constraints generated by the Infinite plan method are not related to the finite plan. Late orders exist in the finite plan without associated constraints when this method is used.
The Finite plan method is recommended for material constraint generation.
- Capacity Constraint Generation
-
The method used to generate capacity constraints during a Planning Engine run.
Allowed values
- No Constraint
- The capacity constraints are not generated.
- Finite Plan
-
The capacity constraints are generated for manufacturing order steps based on the finite plan.
The capacity demand for a manufacturing order step is evaluated at the due start date to identify capacity constraints. When sufficient capacity is not available, the resource is considered available at the planned completion date of the step.
Manufacturing order steps are evaluated in the finite plan sequence, based on planned start dates.
- Infinite Plan Due
-
The capacity constraints are generated for manufacturing order steps based on the infinite plan generated by the Requirements Engine.
The capacity demand is evaluated at the due start date, and manufacturing order steps are sequenced by due start date. The capacity constraint analysis and resolution use the same sequencing logic as constraint generation, based on due start date.
- Infinite Plan Planned
-
The capacity constraints are generated for manufacturing order steps based on the infinite plan generated by the Requirements Engine.
The Capacity demand is evaluated at the due start date, and manufacturing order steps are sequenced by planned start date. The capacity constraint analysis and resolution use the same sequencing logic as constraint generation, based on planned start date.