Migration program for release 2011.1

Table of contents

• 1 Short Description
• 2 Transformations
• 2.1 Setting of Version Number
• 2.2 Migration for Interim Release 2011.1

The migration programm for release 2011.1 has to be invoked once per installation (database) after migration to the release 2011.1 to perform necessary adjustments of data contents.

The migration program outputs a protocol of the transformed data or data to be transformed manually in a message window. The content of the message window is simultaneously written into a log file. These log files can be read by all users independently from the executing user. You can display the log file via action "Display log file". Usually no more data are transformed at repeated call of the migration.

The following transformations are performed by this migration program:

The version number of the migration is updated in the database table A000 even if no transformation is required otherwise providing a check of the consistency of the version numbers of programs, database structures, meta data and migration.

The migration program performs the following transformations for release 2011.1:

• All accounts defined as an interim difference amount account in an existing consolidation parameter are provided with the new account flag 'T' if the account had no other account flag before. Conflicts of account flags are listed in the migration log file and have to be cleared manually.
• The new table CK1 for controlling flags 1 is charged with the controlling flags firmly defined up to now. However still unused controlling flags are not transferred.
• Column options for function of expense method reports ('#CALT', '#CBUC', '#CKON', '#CKTK', '#CNEU', and '#CSUM') are transformed into individual maintainable column options starting with a '$' instead of the '#'.
• The lines of the report line descriptions (REPZEI) receive an additional invisible number uniquely identifying the lines e.g. after renumbering in addition to the visible number defined up to now providing the order of the lines.
• All remark texts for reported data are transferred from a central text table into new attributes of the respective database table for reported data. This step may require extensive time but provides significant performance improvements of several applications in the following work with IDL Konsis.