Dispatching Operations 

Dispatching operations is the main function of capacity leveling. Operations are dispatched to the time when there is sufficient capacity for them to be executed. You can also dispatch sub-operations and work elements.

Depending on whether finite scheduling is to be carried out, operations can be dispatched based on unlimited available capacity or existing available capacity. Existing available capacity is calculated as the difference between the available capacity maintained in the capacity and the requirements already dispatched. You can specify another work center when dispatching operations, if necessary.

If you set the indicator Finite scheduling in the strategy profile, the system searches for remaining available capacity according to the planning direction starting from the dispatching date that either you or the system determines. The operations that were dispatched are given the status "dispatched". If an operation has the status "dispatched", then the capacity requirements for this operation are shown as having been dispatched as well. The operation cannot easily be moved during scheduling once an order has been changed.

The basic procedure for dispatching operations in capacity leveling is as follows:

  1. Either the user specifies the dispatch date of the operation or it is determined by scheduling.
  2. If there are several operations to be dispatched then a dispatching sequence is specified.
  3. The system carries out checks for:

– the dates to which operations are to be dispatched

– the work center to which operations are to be dispatched

  1. Finite scheduling is carried out.
  2. The operation check is carried out:
  3. The status "dispatched" is set for the operation.
  4. The system carries out midpoint scheduling.

Planning log

A planning log is written for all planning activities. Error messages and relevant points in time in finite scheduling are logged and can be called up after the planning run. Errors in finite scheduling lead to termination of the planning run, if you have set the relevant parameters in the strategy profile in Customizing. You can call up the planning log directly from either of the planning tables.