The Table Journal

These table and detail table are a system log showing changes in the database. It is configured by topsystem upon installation.

The Journal and Journal Details show exactly where data changes have been made, what has been changed as well as who performed the change including the corresponding time stamp. The log is used for information purposes only, i.e. to track editing operations. Data in the journal cannot be changed.

  • User:

Name of the user account via which the change has been performed

  • Who:

ID of the user who performed the change

  • When:

Date and time when the change has been performed

  • Category:

Category in which the change has been performed

  • Action:

Description of the change which has been performed

Example: In case someone needs to know all changes done to a certain flight, the flight number and the ST-date needs to be entered in the field Fieldname in the Search panel, for example: LH 6384*03.05.2011".

The Table Journal -> Journal Detail

The table Journal -> Journal Detail displays further information to the journal row selected in the main table.

Following fields are available in the table Journal -> Journal Detail:

  • Table:

Shows the table in which the change(s) has been made

  • Fieldname:

Field in which the change has been performed

  • ID:

ID of the data row that has been modified as defined in the module User Administration

  • Old Value:

Old value of the changed data field. If the DB entry was created (no old value) a "+" is shown here

  • New Value:

New value which has replaced the Old Value.

  • Autoid:

Automatically generated, unique sequential number which is used as an identifier for the data record.

  • Table (DB):

Internal Name of the DB table

  • Fieldname (DB):

Internal fieldname of the database

Following tables are monitored in the Journal:

(Please note that this configuration is only an example. The tables to be journalized may be customized according to the customer's requirements, i.e. further tables may be included or excluded from monitoring. Nevertheless, this example setting represents a useful configuration.)

  • Master Data G:

Table Settings

  • Master Data C:

Table Customer -> Financial Profile
Table Customer -> Services
Table Customer -> Services -> Price Configurations
Table Customer -> Services -> Price Configurations -> Rules

  • Module Rights:

Table Users
Table Users > Roles

  • Module Contract:

Table Contract
Table Contract -> Contract Items
Table Contract -> Contract Items -> Price Configurations
Table Contract -> Contract Items -> Price Configurations -> Rules
Table Contract -> Contract Items -> Rollout Configurations
Table Contract -> Contract Items -> Rollout Configurations -> Rules

  • Module Flights:

Table Rotations (Ready flag fields)
Table Rotations -> Route -> Loads