Downtimes 

Definition

In the master data, you can define downtimes, in which the resource is not available for finite scheduling, for all resources (except vehicle resources). A distinction should be made between the following types of downtimes:

·        Planned downtime

Time in which the resource cannot be used due to maintenance, for example. A planned downtime can be changed, added or deleted in interactive planning, for instance in the detailed scheduling planning board. If you copy the simulation version into the planning version, the system also adopts the changed downtimes.

·        Resource is inactive

Unexpected resource standstill. This downtime cannot be changed in a simulation version.

You define a downtime by specifying a start date/time and end date/time as well as the type. In addition, you can enter a language-dependent short text that describes the downtime in more detail.

It does not make sense to define downtimes that are outside the validity period of the resource, since a capacity has not been defined for the resource for these times. Downtimes outside the validity period are not taken into consideration during scheduling.

Integration

Activities cannot be interrupted by downtimes. This means the activities always come completely before or after a downtime. If you move an activity in the planning board over a downtime, then the activity “jumps” behind the downtime.

If you implement the BAdI /SAPAPO/CRESDOWNTIME, you can define that the activities can be interrupted by downtimes. If an activity is moved onto a downtime, the activity duration is increased by the duration of the downtime. The activity is then continued after the downtime. See also: SAP Note 448601