...

4. using action D In any case, new flag in system setting ( see 1) set or not, booking display with action 'D' is possible.
Booking will be displayed without booking lock.
4.1 new flag is not set No changes in current system behaviour action 'D' :

• All booking modifications are allowed according to user rights.
  4.2 new flag is set
  New system behaviour action 'D' :
• NO booking modification can be done because booking is not locked.
  Try to do any change will lead to an error message `Dieser Vorgang kann momentan
  nicht berarbeitet werden' with additional information in remark field `bitte sperren sie zuerst den Vorgang mit Aktion DE´
  
• Additional locking information should be displayed in Genesis mask.
  -> In case booking is not already locked by another user :
  Booking number is displayed in black and message `Darstellung OK´(`Display ok´).
  -> In case booking is already locked by another user :
  Booking number is displayed in red and message Darstellung OK´(`Display ok´) with
  additional information about user who locked booking in remark comes up.
  Sample action 'D' for already locked booking :
  Image Modified

5. using new transaction code DE

5.1 new flag is not set New action 'DE' must execute normal 'D' action according to actual system behaviour.

• All booking modifications are allowed according to user rights.
  5.2 new flag is set
  If new flag in system setting is activated any booking modifications according to user rights are only possible after booking lock with action code 'DE'. Using new action 'DE' displays last booking sequence (same as action 'D') and additionally lock actual booking for other users. Lock takes place on user level. Information is taken from Log-In entries ('Name').
  'Sales office' is also stored for information purpose. Image Modified
  Additional locking information should be displayed in Genesis mask.
  -> In case booking is not already locked by another user :
  Booking number is displayed in green and message `Darstellung OK´(`Display ok´) with
  additional information about user who locked booking (actual user) in remark comes up.
  -> In case booking is already locked by another user :
  Booking number is displayed in red and message 'Dieser Vorgang kann momentan
  nicht berarbeitet werden' with additional information about user who locked booking and text
  'Buchungssperre nicht möglich' in remark comes up.
  Sample action 'DE' for not already locked booking :
  Image Modified
  

  6. Unlock / check in of bookings

  
  Locked bookings are automatically checked in again if
  1. booking change is successfully done; independent of new sequence.
  2. using action D or DE on any booking (same or other booking) independent
  on successful execution.3. closing Genesis.
  

  7.Super user functionality

  
  Super users (user rights) are able to lock EVERY booking with action 'DE' independent if they are already locked by another user. By using 'DE' and following action 'D' it is possible to unlock every booking which is e.g. mistakenly locked.
  Furthermore new list for locked bookings is available (only) for super users.
  List can be executed via Genesis menu new entry 'show locked bookings' and contains all checked-out bookings from all users (sort by click on column header).
  Image Modified
  Double click on booking number opens booking in Genesis (action D).
  
  
  

  8.Reiseanmeldung

  In Genesis ‚Reiseanmeldung' is just available in case user has locked booking with action 'DE'. Action is normal booking modification.
  In DaVinci 'Reiseanmeldung' can just be executed if booking is NOT locked by any user;
  otherwise error message has to come up.
  -> DaVinci logic is part of second Bedev document 'one user per booking_part_2.doc'