Strategy Profile 
You specify data in the strategy profile that controls how operations are dispatched on the planning tables.
Settings for the planning tables
The following settings are important for dispatching operations on both types of planning table:
- Finite scheduling
: If you set this indicator then finite scheduling is carried out during dispatching. You can find more information on finite scheduling in
Finite scheduling.
- Plan. direction forwards
: If you set this indicator, during automatic dispatching, the system looks to the "future" for a possible date to dispatch operations within the planning period. If you do not set the indicator, the system looks to the "past".
- Dispatch at earliest point in time
: If you have set this indicator then the system tries to dispatch operations as early as possible in the planning period without taking preceding operations in the order into account. If this indicator is set, then the system switches to Planning direction forwards.
- Consider Float bef. prod
.: If this indicator is set, the system is to check whether, during dispatching, an operation was shifted within the float before production. The system only takes this indicator into account if you have activated the dispatching function Operation date check and set the indicator Take op. floats into accnt.
- Use float before prod.: This indicator specifies that the system is to check whether an operation was dispatched within the float before production. This indicator is only taken into account if you have activated the dispatching function Operation date check and set the indicator Use float before production.
- Use float aft. production
: This indicator specifies that the system is to check whether an operation was dispatched within the operation float. This indicator is only taken into account if you have activated the dispatching function Operation date check and set the indicator Use float before production.
- Cancel dispatching due to error: If this indicator is set, the system terminates the dispatching of an operation if it discovers errors during finite scheduling or the operation date check.

For example, if you have set the indicator Use operation float, Use float before production and Cancel dispatching due to error then the system checks whether the operation was shifted within the sum of the operation float and the float before production. If the time of dispatching lies outside this period, then the dispatching of the operation is terminated.
If you have not set the indicator, and the system finds errors during scheduling or the operation date check, it still dispatches the operation. The system always makes an entry in the planning log.
- Reschedule with production. version
: This indicator is only relevant for planned orders. You thus specify that when an operation is rescheduled, the production version in which the work center is entered as the production line is copied to the order. If no such production version exists, then the planned order is rescheduled. It is scheduled using the old standard values and the formulas from the new work center.
- Term. resch. with prod. version:
This indicator is only effective in conjunction with the indicator Reschedule with prod. version. It specifies that rescheduling a planned order taking the production version into account is terminated if no production version exists in which the new work center is entered as the production line.
- Date entry when dispatching
: If you set this indicator, the system does not dispatch operations automatically on the planning tables. Dispatching is only possible manually. If you have set the indicator, you reach a dialog box once you have selected the planning table function Dispatch. You have to enter a start time or finish time and/or a target work center in this dialog box depending on the planning time that has been set. This entry is then valid for all operations that you have selected.

You can manually dispatch an operation on the planning table (tabular form) with the function key Manual dispatching
even if the indicator
Date entry on dispatching is not set in the strategy profile.
- Dispatch. sequence
: Sequence and format key or sort key used to specify the sequence in which operations are to be dispatched.
- Treatment of queue time
: Key you use to define the queue time used for scheduling if you do not want the system to use the queue time calculated by lead time scheduling. It is important to note that with finite scheduling for an operation the system does not take other reduction measures, such as splitting, into account.
- Reduction level
: If you have used the key Treatment of queue time to specify that the queue time is to be reduced, then you should enter the desired reduction level.
- Change planning direction
: If you set this indicator, the system searches for remaining available capacity to dispatch operations in the whole planning period. The system first looks for remaining available capacity in the planning direction defined. If it doesn’t find any here it searches in the other direction.
The indicator Insert operation should not be set. If it is set, then the system only searches in the planning direction specified in the strategy profile.
Settings in the capacity planning table
Insert operation: If this indicator is set, you can dispatch operations at a particular time. If the time to which it is dispatched clashes with an already existing commitment, then the system dispatches the operation before or after the commitment depending on the planning direction. Other operations that have already been dispatched are shifted in the planning direction.
- Close gaps
: Key you use to specify how the system is to deal with gaps caused when an operation has been deallocated or rescheduled. The following options are available:
- The gap in the capacity commitment remains.
- All the operations up to the next gap in the commitment are shifted one way or the other depending on the planning direction so as to close the gap.
- All the operations are shifted to the end of the planning period according to the planning direction in order to close the gap that has arisen.
- Planning in non-work periods:
This indicator specifies that operations can be dispatched to non-work periods without you having to change the available capacities in the work centers. During dispatching, the calendar, operating times and available capacities in the work centers are ignored and instead the following data is used:
Operating time |
00:00 to 24:00 |
Efficiency rate |
100% |
- Dispatching at best time for setup
: If you set this indicator, the system dispatches operations into existing commitments in such a way that the setup times of the commitments increase as little as possible. You must also set the indicator Insert operation.

This function is not available for capacity leveling in the process industry (PP-PI), that is, for capacity leveling of process orders and planned orders that refer to master recipes.
- Initial setup state
: Initial setup states are states of work centers. They are used in:
- Adjustment of setup time
- Setup time optimization
- Dispatching of an operation at the best time for setup
A key for a setup group category that is a maximum of three characters long identifies an initial state.

These functions are not relevant for capacity leveling in the process industry (PP_PI) - See previous point
- Period split
: Defines the period split for dispatching operations on the capacity planning table (for example, shift split). You use the following indicators to define whether and how the period split is taken into account on dispatching:
- Start search in period split
: Specifies for dispatching with the period split at what point the system starts to look for remaining available capacity.
- Always adhere to period split
: Specifies that when dispatching to the period split either the start or finish dates of operations (depending on the planning direction) lie on points of the period split.
- Operation completely in period split
: Specifies that when dispatching to the period split the start- and finish date of an operation must lie within an interval of a period split, for example, a shift. If the indicator is set and an operation is longer than a split interval, then the operation is dispatched at the next possible time.
Settings for the planning table (tabular form)
The following indicator is relevant for dispatching operations on the capacity planning table (tabular form):
- Overall capacity load
: If you have set this indicator, the system takes account of overloads in individual periods when dispatching operations. Thus, a 200% load for one period means that no operation can be dispatched to the following period.
Setting for the capacity planning table (tabular form) with periodic-continuous display
When dispatching operations on the capacity planning table (tabular form) with the periodic-continuous display the following indicators are relevant as for the capacity planning table:
- Dispatch at best time for setup

The Initial setup state and Dispatch at best time for setup in the process industry; that is, for capacity leveling of process orders and planned orders that refer to a master recipe, are not relevant or are not available.
Dispatching functions
In the strategy profile you can define which functions are to be active when dispatching. The following functions are possible:
- Forming the dispatching sequence
: This function must be activated if you want to define the dispatching sequence (for example, with a user exit). For more information, see
Planning Taking Account of the Sequence
Taking account of the operation sequence in the order: If you have activated this function, you can dispatch an operation depending on the planning direction only after its immediate dispatched predecessor (planning direction forwards) or its immediate dispatched successor (planning direction backwards). This function is only relevant for planned orders, production orders and maintained orders without explicitly maintained relationships. For more information, see
Planning Taking Account of the Sequence
- Operation date check
: This function must be active if the system is to check operation dates.
- Midpoint scheduling
: This function must be activated if, when dispatching an operation, you want midpoint scheduling to take place when the status has been set. Otherwise midpoint scheduling takes place when you save the planning table.
- Change production version on error
: If you have activated this function and an error in automatic dispatching occurs (for example, capacity overload), the next production version is automatically copied to the planned order. The production versions are sorted alphanumerically according to production version key. The planned order is scheduled using the routing for this version, but not dispatched. The operations remain in the pool and can be dispatched to the new production line along with other operations. This function only works with planned orders.
- Setup time optimization
: If you have activated this function, then you can dispatch a group of selected operations in the pool to the target work centers in the sequence that minimizes setup time. For more information about this function, see
Optimization of setup time.

This function is not available for capacity leveling in the process industry (PP-PI), that is, for capacity leveling of process orders and planned orders that refer to master recipes.
Further settings for dispatching
In the strategy profile, you can use the key Dispatching internal production to specify at what time the system is to dispatch internally processed operations, for example from plant maintenance orders and networks. Here you can choose between dispatching at the earliest point in time, the latest point in time and dispatching depending on the valid distribution key of the scheduling capacity.
Dispatching using the distribution key leads to the operation being dispatched to the period when it is currently displayed. The distribution key contains a distribution strategy. The earliest and latest dates for the distribution are defined in the distribution strategy. This determines whether the system uses the earliest or latest start date.