Buchungsdatum_Vorgang_und_Leistung

VORGANGSKOPF

Field

Description

Date used

Time used

DATUM

DATUM is the bookingdate for the booking (systemdate of the creation of the booking). Under normal conditions it will be the same for all sequences. Only in case that a booking with state "Vormerkung" is set to "option" it will be actualized.  Furthermore it is possible to set the value for DATUM by using the /D within the multifunctionline or by defining a value in genesis for the systemdate.
If setting "If AN/RQ/OQ/OP fix, then change booking date" is activated the systemdate of the time when the booking is fixed, is used to actualize the value.
Following prio is used:

  1. Date from multifunctionline
  2. FakeDateTime from request (for fitnesse)
  3. SystemDate from request (will be sent from GenVAS to Genesis and back and, if not changed manually, will assure that the date will stay the same for the rebooking)
  4. Current system date from GenVAS machine

X

X

DATUM_VON

Departure date of the earliest departure date of all services within the booking

X

 

DATUM_BIS

Arrival date of the latest arrival date of all services within the booking

X

 

OPTION_BIS

In case of option bookings the date is stored at which the booking will be fixed or expire. The option date can be set within the booking request.
If the public holidays are setup within davinci and the agency has the setting activated that no option dates should be on public holidays, the optione date is automatically set to the next working day.
And last but not least the earliest allotment release date of all services is checked and used as option date in case that it is earlier as the other two dates.

X

X

LASTDATE

LASTDATE is always updated with the current system date when the booking is stored in the database. Even if the booking is manipulated with actions which do not create a new sequence (e.g. CR)

X

X

MODIFICATION_DATE

MODIFICATION_DATE is always updated with the current system date when the booking rebooked and a new sequence is created.

X

X

CRUISE_BEGIN_DATE

Departure date of the earliest departure date of all ship services within the booking

X

 

CRUISE_END_DATE

Arrival date of the latest arrival date of all ship services within the booking

X

 

 
 
 
LEISTUNGSKOPF

Field

Description

Date used

Time used

DATUM

DATUM is the creation date of a service when a new booking sequence is created

X

X

DATUM_VON

Departure date of the service

X

 

DATUM_BIS

Arrival date of the service

X

 

ERFASSUNGSDATUM

Not filled anymore!!!

 

 

LASTDATE

LASTDATE is always updated with the current system date when the service is stored in the database. Even if the booking is manipulated with actions which do not create a new sequence (e.g. CR)

X

X

BOOKINGDATE

BOOKINDATE contains the same value as the field DATUM from vorgangskopf and will be kept the same over all sequences.
But ...

  1. It can be manually overruled with the service properties.
  2. It will not be actualized, even not when setting "If AN/RQ/OQ/OP fix, then change booking date" is activated.
  3. The field will only be actualized, if the booking is booked from state "offer to fix" or "offer to option".

X

X

DATE_CHANGED

DATE_CHANGED is actualized during a rebooking when the booking process recognizes any kind of change to a service, else it will be copied from the sequence before or it will be the current system date in case of the first booking sequence

X

X