The Table Rotations -> Delays
This table is used to record delays of a rotation. The delays are administered in the module master data Fis, Delay-Codes.
To enter a delay make sure to have the correct rotation selected in the table Rotations, then move to the table Delays and create a new entry. Then select the leg the delay applies to in the field A/D, enter the delay time, the delay reason code before you can save the entry.
|
Arrival/Departure indication; to be selected to record to which leg the delay applies |
|
Flight number of the leg to which the delay applies, automatically filled when A/D is selected |
|
Time of delay in the format hhmm |
|
Reason for delays administered in master data Fis, Delay-Codes |
|
Code as administered in master data Fis, Delay-Codes |
|
Additional detail code as administered in master data Fis, Delay-Codes -> Sub-Delay-Codes |
|
Indicates whether the delay is under the own responsibility (derived from master data Fis, Delay-Codes) |
|
Scheduled time of the flight |
|
Information source of the delay |
|
Flag to be set if the delay can be billed |
|
From this drop-down list the organisation unit (as defined in the module Rights), which is responsible for the delay, can be chosen. |
|
Freely definable text comment |
|
Name of the last user who changed the data record. Filled in automatically. |
|
Date and time when the data record was changed last. This entry is filled in automatically. |
Occurring delays might influence the handling costs for a flight. This can either result in a price reduction (e.g. if you as a handler have been responsible for a delay) or a price increase (e.g. if your customer has caused a delay resulting in increased efforts). Which consequences a delay might have, is defined in handling contracts with help of corresponding price configurations. A delay price configuration can be used, for example, to define a delay length after which a surcharge has to be paid etc.
Please also consider the following video: Caused By Default Values: |