Migration program for release 2016

Table of contents

• 1 Short Description
• 2 Transformations
• 2.1 Setting of Version Number
• 2.2 Migration for Update 1 for Release 2014.0
• 2.3 Migration for Release 2016

The migration programm for release 2016 has to be invoked once per installation (database) after migration to the release 2016 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.

As far as Update 1 for Release 2014.0 has not been installed before the migration program performs the following transformations in the database:

• The maintenance of check sums is activated for all facts.
• All existing positions are provided with a position type with respect to the usage of the position in position account allocations and reports if unique.
• The posting key usage tag 'B07' is replaced by 'B04' . In this context the development areas of the participation development 'B' are provided with the depreciation flag 'AHK' or 'AFA', respectively, if doubtless determinable.
• Postings of all vouchers allocated to a business unit are provided with this business unit as business unit of the posting.
• The authorisations for rule templates are corrected if the licence for IDL.FORECAST had been acquired after installation of release 2014.0.

The migration program performs the following transformations for release 2016:

• Posting keys with the disposed usage tag 'DIV' are transformed into the new usage tag 'EOI'.
• Entries for the control of transaction developments per period or fact (ABRSPI or FACSPI, respectively) are transformed into the corresponding entries per transaction development area (ABRSBE or FACSBE, respectively).
• As far as the column head text (from now on required entry) is not specified for a transaction development area, it is supplemented. It consists of the development transaction short text, a word wrap and the transaction development area short text.
• Voucher classifications / consolidation functions (KVA) 'AE' as well as 'A0' up to 'A9' are supplied with 'AV' as voucher classification for carry forward.
• Entries for the former "Account for deferred taxes - cost" in the consolidation parameter 'LT' are copied to both of the new accounts for cost and earnings.