Planning Engine Parameters (plaps0120m000)

Field Information

Introduction Date

The date on which the Planning Engine (PE) parameters is created.

Scenario

The name or code of the PE parameters.

Description

The description of the PE parameters.

Simulation Control

Weights

Consistent Dispatching

The time period allocated for consistent dispatching.

Note: By default, this value is set to 7200 seconds.

This field determines the relative importance that the planning engine prioritizes reducing gaps by assigning jobs to resources as soon as possible.

Reducing the time value increases the weight of this factor compared to other factors.

Default Time Loss

The Planning Engine uses this parameter to determine the relative importance of avoiding time gaps in resource utilization.

Note: If this parameter is 0, the Planning Engine ignores this field and consider these fields:

• Consistence Dispatching
• Due Date Respect
• Set up Optimization

Cycle Time Reduction

If this check box is selected, the cycle time for individual orders is reduced after the post-validation phase at the end of the engine run. This phase improves results when the last steps of orders use resources that are not constrained.

The post-validation phase compresses all supply networks toward the end of demands to which they are allocated. However, this compression can increase the cycle time of individual orders when the last operations can be compressed, but their predecessors cannot.

Due Date Respect

The due date to complete supply order steps. Reducing the time value of this factor increases its weight compared to the other factors.

The Planning Engine considers these fields as relative factors:

• CONSISTENT DISPATCHING
• DUE DATE RESPECT
• SETUP OPTIMIZATION
• TIME LOSS

Note: This field determines the priority of the Planning Engine for completing supply order steps on time.

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.

Offset Priority

The time difference between the due dates of the prioritized manufacturing orders. This parameter is used to prioritize manufacturing orders during a planning run.

Setup Optimization

The time period during which the Planning Engine performs setup optimization on resources.

The Planning Engine considers the following parameters as relative factors:

• CONSISTENT DISPATCHING
• DUE DATE RESPECT
• SETUP OPTIMIZATION
• TIME LOSS

Note: When you decrease the time value of this factor, the Planning Engine assigns this factor a higher weight than other factors.

Gradation Weight

The value used to emphasize the gradation level associated with each resource setup state. It is expressed in seconds.

Note: This field value multiplied by the difference in gradation levels between two setup states is added to the setup duration (only for the evaluation of the best solution). For example, a gradation factor of 3600 seconds means that a difference in the gradation level between two consecutive setup states is equivalent to adding two hours to the setup time for the evaluation.

Default Setup Lookup Period

The time period for which the Planning Engine is allowed to look forward in time during synchronization to group supply order steps for setup optimization.

Backward

The number of supply order steps that the Planning Engine evaluates and compares simultaneously when leveling backward in time.

Forward

The time for validating forward scope when leveling.

Note: The value specified in this field determines the number of supply order steps that the Planning Engine evaluates and compares when leveling forward in time.

The Planning Engine uses this field value to define the scope of the phase.

Allocate Validate

The number of supply order steps that the Planning Engine simultaneously evaluates and compares during the allocation validation phase.

Synchronize

The time period for the synchronization phase.

Note: This field determines the number of supply order steps that the Planning Engine simultaneously evaluates and compares during the synchronization phase.

Restrained

Material

The type of material availability.

Allowed values

Finite

Infinite

Note: 

• By default, the value is set to Finite. If this value is set to Finite, the PE builds the production plan in finite material for all items.
• If this value is set to Infinite, the PE considers infinite material availability.

Capacity

The type of capacity availability.

Allowed values

Finite

Infinite

Note: By default, the value is set to Finite.

Infinite Purchase

If this check box is selected, the Planning Engine builds the production plan in infinite material for all items.

Note: 

• By default, this check box is not selected, which means, the PE builds the production plan in finite material for all items.
• The purchased items are planned based on this setting:
  • If this check box is not selected and the Material field is set to Finite, the PE considers all items in finite material.
  • If this check box is selected, and the Material field is set to Finite, the PE considers purchased items in infinite material and all other items in finite material.
  • If this check box is not selected and the Material field is set to Infinite, the PE considers all items in infinite material.
• You can select this check box if you require to plan infinite purchased materials, while planning finite manufactured materials such as, subassemblies. If this check box is selected, and run the Planning Engine in finite material mode. The Planning Engine considers the Constraint Type for all purchased items as Never, regardless of the actual value. As a result, the user cannot view allocations for purchase orders in the Supply Network.

Move Confirmed MO

Determines whether to transfer confirmed manufacturing order steps 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

Note: Moving confirmed order steps is not intended for rescheduling order steps. However, to determine the remaining capacity available for additional planned or firm planned order steps.

Move Released MO

Determines whether to transfer released manufacturing order steps 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

Indicates if Planner transfers confirmed demand order steps 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

Note: Moving confirmed order steps is not intended for rescheduling order steps. However, to determine the remaining capacity available for additional planned or firm planned order steps.

Move Released DO

Indicates if Planner transfers release demand order steps 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

Note: Moving released order steps is not intended for rescheduling order steps. However, to determine the remaining capacity available for additional planned or firm planned order steps.

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.

Note: If this check box is not selected, the planning engine does not move confirmed substitution orders. This situation corresponds with the Frozen planning method for confirmed manufacturing orders and confirmed distribution orders.

Move Released SO

If this check box is selected, the planning engine moves released substitution orders in the same way as firm-planned and planned substitution orders.

Note: If this check box is not selected, the planning engine does not move released substitution orders. This situation corresponds with the Frozen planning method for confirmed manufacturing orders and confirmed distribution orders.

Compress Firm Planned Supply

If this check box is selected, the Planning Engine compresses non-constrained firm-planned supply orders.

Note: 

• If this field value is set to 1, the Planning Engine compresses non-constrained firm-planned supply orders (manufacturing, distribution, or substitution type) on their constrained successors. This setting minimizes inventory build-up of sub-assemblies.
• If this field value is set to 0, the Planning Engine plans non-constrained firm-planned supply orders (manufacturing, distribution, or substitution type) on their due dates. This setting can result in inventory build-up of sub-assemblies if the successors of the supply order are planned late because of constraints.

Compress Planned Supply

Indicates if the Planning Engine compresses non-constrained planned supply orders.

Note: 

• If this field value is set to 1, the Planning Engine compresses non-constrained planned supply orders (manufacturing, distribution, or substitution type) on their constrained successors. This setting minimizes inventory build-up of sub-assemblies.
• If this field value is set to 0, the Planning Engine plans non-constrained planned supply orders (manufacturing, distribution, or substitution type) on their due dates. This setting can result in inventory build-up of sub-assemblies if the successors of the supply order are planned late because of constraints.

Synchronize Purchase Orders

If this check box is selected, and a production order is delayed due to planning constraints, the Planner reschedules the planned or firm-planned purchase order allocated to that production order. Planner sets the planned completion date of a purchase order to the planned start date of the production order.

Expedite Distribution

If this check box is selected, the steps in the distribution order are expedited. Expedition is performed at the end of the planning. Each distribution step moves backward to the predecessor. When no predecessor exists, the step moves to the plan start date.

Push Unconfirmed Released PO

The Purchase orders in the Order Management package are transferred to Planner as released purchase orders. A purchase order usually includes a confirmed delivery date that represents the date communicated by the supplier. However, if the planned delivery date of a purchase order is within the item lead time and the supplier has not provided a confirmed delivery date, do not assume that the supplier can deliver on time.

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.

Released Material Time Fence

The time period/duration in which the Released and Confirmed demand orders have priority to use on hand inventory.

Note: By default, the value is set to 2592000 seconds.

Released Material Time Fence

Allocate CO Lines by Due Date

If this check box is selected, the Customer Order Lines are allocated by due dates.

Note: By default, this value is set to 0.

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.

Material Constraint Generation

The type of material constraint used to set the logic on how material constraints are generated 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 type of capacity constraint used to set the logic on how capacity constraints are generated 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.

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 the planned date < due date + PE_CONSTRAINT_THRESHOLD.

Constraint Threshold

Timeout

A predefined time limit that interrupts a running process or task when execution exceeds the specified duration. This setting monitors the total execution time of the Planning Engine. If the overall Planning Engine execution exceeds the configured time limit, the process is terminated and a timeout is logged.

Phase Statistics

If this check box is selected, the memory-usage details for each phase after phase is displayed. This displays the amount of heap memory used after the completion. This helps users to monitor and analyze memory use across phases.

Log Assertions

If this check box is selected, the Planning Engine logs detailed assertion data during code execution. If an assertion fails, the application records internal validation errors along with the exact execution flow.

For example: java.lang.AssertionError: Assertion Failed. fndItr must be valid.

Indicates that the required eligibility criterion or internal condition was not satisfied during code execution. The log captures:

• The assertion failure message
• The class and method where the failure occurred
• The execution path (stack trace)

Execute Trace Enable

If this check box is selected,, the stack tracing mechanism is enabled.

Debug Level

The level for the debug file.

Allowed values

No Debug

The debugging is disabled.

Quick Debug

The option is used to test or verify a small change without a full debugging process.

Full Debug

This option is used for comprehensive debugging of the entire application, especially for complex issues or production-level troubleshooting.

Current Debug Item

The debug information of the requested business object SO steps.

Number of Debug Steps

Indicates the number of SO steps that the current debug steps count setting logs.

Current Debug Steps

Indicates the debug log info for the requested Business Object SO steps.

Number of Debug Resources

Indicates number of resources can be logged.

Current Debug Resources

The debug log info of the requested resources.

Log Phase-wise Results

If this check box is selected, the Planning Engine creates .csv files at end of each phase execution.

(De)Select All

Propagation Phase

If this check box is selected, the planning engine propagates inherited priority, customer order line percentage, and warehouse order percentage through all levels of the supply network.

Note: This information is used by planning engine evaluation functions.

Load Phase

If this check box is selected, the pre-planning for Purchase orders that are not synchronized during the run is performed.

PreCalculation Phase

If this check box is selected, the planning engine detects and removes cyclic relations that cause problems for the rest of the calculation.

Frozen Released Phase

If this check box is selected, planned dates are calculated for frozen steps.

The planned dates are equal to the due dates, even when constraints are not respected. The capacity that frozen steps require is not available to successive phases. The resources are reserved. If two steps overlap on the same resource, the planning engine does not move either step to solve the capacity problem.

Released Step Backward Phase

If this check box is selected, backward capacity levelling is performed by using the scoped simulation method.

This phase is a backward phase. The plan is constructed from the end to the beginning, and steps are planned as late as possible. The planned end date for a step is the minimum of the due end date and the earliest successor start date.

Temporary material allocations are ignored during this phase. The resulting plan has no lateness. Some steps are planned before the plan start date and are repaired in later phases.

Released Step Forward Phase

If this check box is selected, forward capacity levelling is performed by using the scoped simulation method.

This phase is a forward phase. The plan is constructed from the beginning to end, and steps are planned as early as possible. The earliest possible start date for a step is the latest of the plan start date, the planned end date of the latest predecessor, and the start date calculated in the previous phase.

Temporary material allocations are ignored during this phase. The plan is valid for Capacity Only steps. No planned steps are present yet.

The plan is used only the Capacity Only steps.

The capacity assignments required for Capacity Only steps do not change after this phase.

Backward Phase

If this check box is selected, the backward phase is enabled.

This phase processes all steps first and performs backward leveling. Steps are planned as late as possible and in reverse order by using the scoped simulation heuristic. The planned end date for a step is the minimum of the due date or the earliest successor start date. Temporary material is considered during this phase.

An inventory curve is constructed, and a step is not inserted after the earliest start date of demands that consume the supply.

The resulting plan has no lateness, but some steps are planned before the plan start date. The evaluation function is based on the planned end date only.

Forward Phase

If this check box is selected, the backward phase is enabled.

This phase produces a fully constrained and valid plan with minimal lateness. This phase is a forward phase and plans steps in the order of the previous phase start date by using the scoped simulation heuristic.

The earliest start date for a step is the latest of the plan start date, the previous phase start date, and the planned end date of the latest predecessor.

The plan is fully constrained, and temporary material is considered.

The resulting plan is complete and valid but not optimal because work in process is not reduced and cross-allocations exist. The evaluation function is based on consistent dispatching, due date compliance, setup optimization, and time loss.

Allocate Compress Phase

If this check box is selected, the WIP steps are reduced by compressing the predecessors or successors.

If successors are not planned, the planning engine compresses on the due date.

This phase performs postponements only. No step is expedited.

This phase runs in infinite capacity mode, and calendars are used to calculate planned dates. Steps are grouped by low-level code and processed one group at a time, from low-level code 1 to the maximum low-level code.

Each group is sorted by the latest successor start date, and steps are processed backward from the end to the beginning of the plan.

The planned end date for a step is the earliest successor start date or the later of the due end date and the previous phase end date. The resulting plan is invalid because of infinite capacity, and work in process and cross-allocation are eliminated.

Synchronize Phase

If this check box is selected, the planning engine performs backward leveling. This is similar to backward Planned phase.

Setup optimization rules are applied at the step choice level, unlike the Backward Planned phase, which applies them at the resource choice level. Steps are planned as late as possible, and the planned end date is the previous phase end date or the earliest successor start date. Temporary material is considered, an inventory curve is constructed, and a step is not planned after the earliest start date of demands that consume the supply. The resulting plan is invalid and contains steps before the current date, and demand transactions precede supplies when supplies are not movable. The evaluation function is based on consistent dispatching, due date compliance, and setup optimization.

Allocate Validate Phase

If this check box is selected, the planning engine performs forward leveling. This is similar to backward Planned phase.

This phase plans steps in the order of the previous phase start date by using the scoped simulation heuristic. The earliest start date for a step is the latest of the plan start date, the previous phase start date, and the planned end date of the latest predecessor. The plan is fully constrained, and temporary material is considered. Setup optimization rules are applied and the resulting plan is complete and valid, but allocations are not optimal, and capacity is wasted at the beginning of the plan after work in process reduction. The evaluation function is based on consistent dispatching, due date compliance, setup optimization, and time loss.

Final Allocate Inventory Phase

If this check box is selected, the planning engine recalculates allocations based on the inventory supplies.

This phase consumes on-hand and released inventory supplies as early as possible in the plan.

Steps are sorted and processed by previous planned start dates.

Forward-forward allocations are performed by scanning demands and supply transactions forward, and on-hand and released supplies are considered.

A demand remains unallocated when sufficient on-hand and released supplies do not exist before the planned date.

The plan is invalid after this phase because allocations on planned supplies remain missing.

Final Allocate Material Phase

If this check box is selected, the planning engine recalculates the allocations based on the planned supplies.

This phase consumes planned supplies as late as possible in the plan. Steps are sorted and processed in reverse order of the previous planned start dates. Backward-backward allocations are performed by scanning demands backward and allocating each demand by scanning supply transactions backward from the demand date.

Validate Phase

If this check box is selected, the planning engine plans the steps as early as possible.

Steps are sorted and processed by the planned start date from the previous phase. The earliest start date for a step is the latest of the plan start date, the material availability date, and the planned end date of the latest predecessor. Constraints are generated during this phase.

Free Unconstrained Demand Phase

If this check box is selected, the steps are sorted and processed by the previous phase start date, and the sequence is not relevant in this phase.

Demand transactions allocated to the internal constraint time fence are set to free.

UnConstrained Demand Allocation Phase

If this check box is selected, the allocations between unconstrained demands and remaining free supplies is created.

Steps are sorted and processed in reverse order of the previous phase start date. Backward-backward allocations are performed by scanning unconstrained demands backward and allocating each demand by scanning unallocated supply transactions from the demand date.

Post Validate Phase

If this check box is selected, steps are sorted and processed in reverse order of the previous phase planned end date.

The planned end date for a step is the earliest successor start date or the later of the due end date and the previous phase end date. The planning buffer is applied during this phase.

Cycle Time Reduction Phase

If this check box is selected, the planning engine reduces the cycle time of the individual orders after the post validation phase.

The results are improve when the final steps of orders use resources that are not constrained.

The Post Validation phase compresses supply networks toward the end demands to which they are allocated. This compression increases individual order cycle time when final operations are compressed but predecessor operations are not compressed.

This phase reverses these effects and reduces cycle times. Steps are compressed backward only within the same order. The first steps of an order are not compressed toward supplying subassemblies. The total cycle time of the supply network remains unchanged.

Expedite Distribution Phase

If this check box is selected, the planning engine expedites steps that belong to distribution orders.

This phase is performed at the end of the planning process, after all calculations are completed.

All distribution steps are compressed backward to predecessors or to the plan start date when a predecessor does not exist.

Post Calculation Phase

If this check box is selected, the planning engine calculation results are saved to object server, planned step dates are updated, and allocations are created. The resource assignments and used capacity are created.

DOA Phase

If this check box is selected, allocations are created for demand orders due inside the item constraint time fence but planned outside.

Allocations are created for dependent demand inside the constraint time fence in infinite material mode.

Constraint Generator

If this check box is selected, the constraint generator creates constraints.

The constraints are created when Material Constraint Generation is set to Infinite Plan. The constraints are also created when Capacity Constraint Generation is set to Infinite plan sequenced on due dates or Infinite Plan Planned sequenced on planned dates.