Migration program for release 2014

Table of contents

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

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

• The new flags for classification of user groups for menu items and for data objects, respectively, are initialised with respect to the existing data.
• The new flags for authorisation for scenarios and rule templates in the "Startup data and authorisation" (VORADMIN) are initialised with '1' (authorised for all objects) for all users corresponding to the hitherto existing practice.
• As far as the startup data (VOR) of a user indicated a sort option for the group companies for display in list structure it is replaced by the corresponding sort option with tree structure.
• All transaction developments defined without development areas up to now are provided with a standard development area. This area receives the key '0' and the description "Standard".
• The transaction development properties "Carry-forward type", "Automatic calculation of changes" and "Development transaction with currency rate average per month" are transferred to the corresponding new attributes per development area with account balance check of this transaction development as far as this development area contains posting keys with the corresponding usage tags ('V' or 'L', respectively).
• The new flag for account balances in the fact master data (FAC) is preset due to the existence of account balances on the respective fact.
• Reference consolidation function codes in the consolidation function master data (KVA), consolidation parameters (KTKPAR) and group processing controls (KVERARB) are transformed due to the new nomenclature for deconsolidation.
• Disposed consolidation functions are provided with a "valid until" entry with respect to their last usage or even deleted if they were not used at all.
• Provided the account "Difference amount CapSequentCons" had been specified in the consolidation parameter 'KK' a new consolidation parameter 'KB' is generated with the same keys.
• The database tables K056 and K057 (representation of the group structure and group companies for usage by IDL Datamart and individual MIS interfaces) are provided with current data for all defined group companies independent from the active MIS parameter.