Edit

Parameters not used by Planning Optimization

  • Article
  • 5 minutes to read

This article lists the parameters that Planning Optimization doesn't currently consider during its operation. The planning service might skip a parameter because, for example, related functionality isn't yet supported. Alternatively, the parameter might have become obsolete because of functional changes.

The following sections list the parameters that Planning Optimization doesn't use on specific pages. They also explain why each parameter isn't used.

Master planning parameters page

Planning Optimization doesn't use the following parameters or options on the Master planning parameters page:

  • General tab:

    • Current forecast plan – Planning Optimization doesn't consider this parameter. Instead, create a master plan that specifies a forecast model.
    • Copy the complete and updated static master plan to the dynamic master plan – Not supported in Planning Optimization. You can run each plan independently, but results won't be copied between them.
    • Start time for calculated delays – Not supported in Planning Optimization.
    • Use dynamic negative days – Planning Optimization always uses the Dynamic negative days approach.
    • Today's date calendar – Not supported in Planning Optimization. Planning Optimization always uses current time rounded to the next whole hour.
    • Use of cache – This parameter isn't considered because Planning Optimization manages performance and scaling.
    • Number of tasks in helper task bundle – This parameter isn't considered because Planning Optimization manages performance and scaling.
    • Pre-processing: Automatically filter by items with direct demand – Not supported in Planning Optimization.
    • Post-processing: Automatically filter by items with direct demand – Not supported in Planning Optimization.
    • Number of threads – This parameter isn't considered because Planning Optimization manages performance and scaling.
    • Planning process timeout in minutes – In Planning Optimization, there's a fixed timeout of 1 hour.
    • Scheduling start time – This parameter isn't considered in Planning Optimization. With Planning Optimization, an explosion run is a run of the plan for the selected item(s).

  • Planned orders tab:

    • Receipt time – Not supported in Planning Optimization. The receipt time exactly matches the demand time in Planning Optimization.

  • Number sequences tab:

    • Master scheduling planned order number - Planning Optimization uses its own number sequence, which can't be selected, so this parameter isn't considered.

Coverage groups page

Planning Optimization doesn't use the following parameters or options on the Coverage groups page:

  • General FastTab:

    • Positive days – The Positive days value isn't used. With Planning Optimization, positive days are considered infinite.

  • Other FastTab:

    • Freeze time fence (days) – Pending Freeze time fence support.
    • BOM explosion time fence (days) – Not supported in Planning Optimization.
    • Capacity scheduling time fence (days) – Not supported in Planning Optimization.
    • Forecast plan time fence – Forecast plans aren't supported in Planning Optimization. Instead, create a master plan that specifies a forecast model.

  • Delays FastTab:

    • Calculated delays – This parameter isn't considered because delays are always calculated for the coverage group.
    • Calculate delays time fence (days) – This parameter isn't considered because delays are calculated for the Coverage time fence (days).

Item coverage page

Planning Optimization doesn't use the following parameters or options on the Item coverage page:

  • General tab:

    • Planned order type – Planning Optimization doesn't support the Kanban option.
    • Freeze time fence (days) – Pending Freeze time fence support.
    • BOM explosion time fence (days) – Not supported in Planning Optimization.
    • Fulfill minimum – Planning Optimization doesn't support the Today's date, First issue, and Coverage time fence options. It always uses the Today's date + procurement time option.
    • Minimum periods – Not supported in Planning Optimization.
    • Planning formula – Pending. Planning items support for Planning Optimization must be enabled in feature management.
    • Default priority – Supported in version 10.0.33 and later. The feature Process Manufacturing support for Planning Optimization must be enabled in feature management.
    • Current priority – Supported in version 10.0.33 and later. The feature Process Manufacturing support for Planning Optimization must be enabled in feature management.
    • Date changed – Supported in version 10.0.33 and later. The feature Process Manufacturing support for Planning Optimization must be enabled in feature management.

Master plans page

Planning Optimization doesn't use the following parameters or options on the Master plans page:

  • General FastTab:

    • Include continuity plan – Not supported in Planning Optimization.
    • Backward scheduling capacity time fence – Not supported in Planning Optimization.
    • Capacity time fence for bottleneck resources – This field will no longer be supported in Planning Optimization because we detected that customers weren't using it.
    • Planned orders – Planning Optimization uses fixed number sequences.
    • Session – Planning Optimization uses fixed number sequences.
    • Continuity plan – Not supported in Planning Optimization.

  • Time fences in days FastTab:

    • Freeze – Freeze time fence isn't yet supported in Planning Optimization.
    • Explosion – Not supported in Planning Optimization.
    • Forecast plan – Not supported in Planning Optimization.
    • Continuity plan – Not supported in Planning Optimization.
    • Calculated delays – This parameter isn't considered. Calculated delays are created for the coverage time fence (days).
    • Capacity - Not supported in Planning Optimization.

  • Calculated delays FastTab:

    • Ensure that the planned orders are not created prior to the master planning run date – Not supported in Planning Optimization. Planning Optimization never creates planned orders in the past.
    • Add the calculated delay to the requirement date (in the Planned purchase orders section) – Starting January 18, 2023, Planning Optimization supports this field.
    • Add the calculated delay to the requirement date (in the Planned production orders section) – Starting January 18, 2023, Planning Optimization supports this field.
    • Add the calculated delay to the requirement date (in the Planned transfer section) – Starting January 18, 2023, Planning Optimization supports this field.
    • Add the calculated delay to the requirement date (in the Planned kanban section) – Kanban isn't supported in Planning Optimization.

  • Action message FastTab:

    • Update postponed date as requirement date - This parameter is discontinued with Planning Optimization.

  • Sequencing FastTab:

    • Sequence planned orders after master planning – Supported in version 10.0.33 and later. The feature Process Manufacturing support for Planning Optimization must be enabled in feature management.
    • Bucket type – Supported in version 10.0.33 and later. The feature Process Manufacturing support for Planning Optimization must be enabled in feature management.
    • Period type – Supported in version 10.0.33 and later. The feature Process Manufacturing support for Planning Optimization must be enabled in feature management.
    • Number of buckets in the campaign cycle – Supported in version 10.0.33 and later. The feature Process Manufacturing support for Planning Optimization must be enabled in feature management.

Released product details page

Planning Optimization doesn't use the following parameter option on the Released product details page:

  • Engineer FastTab:

    • Production type – Supported in version 10.0.33 and later. The feature Process Manufacturing support for Planning Optimization must be enabled in feature management.