Start of fixed lead-time horizon

To define a plan item's fixed lead-time horizon, use the Operations Time Fence field in the Items - Planning (cprpd1100m000) session. The Operations Time Fence field is used only for planned production orders.

The fixed lead-time horizon is the time period for which Enterprise Planning uses a fixed lead time to plan orders.

Before the fixed lead-time horizon, Enterprise Planning plans on the basis of routing data. Beyond the fixed lead-time horizon, Enterprise Planning plans orders by using a fixed lead time.

The fixed lead-time horizon applies especially to manufactured items. Beyond the fixed lead-time horizon, the planning run does not calculate or store operations during the planning run. Instead, the planning run uses the plan item's fixed lead time to calculate the start and finish date of planned orders. The orders without operations cannot be transferred to Job Shop Control module; which means the planned production orders can be transferred, if the order is within the fixed lead time horizon.

The fixed lead time is taken from the order lead time specified in the Items - Production (tiipd0101m000) session, which is calculated based on the routing and economic order quantity.

Planning with a fixed lead time is faster than planning on the basis of routing data, but the results are less precise.

For the planned purchase orders, you must define the plan item's fixed lead-time horizon, in the Items - Purchase Business Partner (tdipu0110m000) session. The lead time is defined in the Lead Time Horizon (Days) field.

To make a rough and faster calculations for the planned purchase orders, you can define the calculated lead time in the Calculated Lead Time (Days) field.

With in the lead time horizon, you can also define the following for a planned purchase orders.

  • Internal Processing Time
  • Safety Time
  • Supply Time
  • Transportation Time (Days)

Recommendation:

  • Do not make the number of days in the Operations Time Fence field too large.
Performance aspects
  • Effect on CPU: Yes
  • Effect on database growth: Yes