Title
RSSERP80 - Report Tree Migration

Purpose
This report transforms report trees that were created using the oldversion of transaction SERP (Release 4.5 and older) to the newstructure that is compatible with the new version (Release 4.6). Itshould be executed in the client that contains the productive versionsof your report trees.
The original report trees are not deleted and can still be displayedusing transaction OLD_SERP. In order to avoid naming conflicts orredundancy, you must, however, delete the tree created in the targetstructure (using SERP) before migrating the tree again within the sameclient.

Features
Description of Select-Options and Parameters:
- Report Trees:
Selection according to the old technical names of report trees. Thisentry is merely a preliminary selection. You can restrict yourselection values further on the subsequent list screen.
- Languages:
Gives users the possibilty of restricting the language-dependent textentries of a selected tree to the language you choose.
- Master language:
Language that you want to be used as the tree's master language forfuture translations. Must already be contained in the list of possibleentries.
- Package:
If you enter a package here, all report trees that are to be migratedwill be assigned to it. If you do not enter anything in this field, thesystem queries you for a package for each tree.
Since the private nodes concept no longer exists in new trees, privatenode contents are not migrated. Lists that were stored in your tree arenot migrated either.

Activities
The trees selected using select options are checked for inconsistenciesand removed from the final selection if any inconsistencies are found.Users may also restrict the number of trees selected.
A log is displayed in compressed form after successful migrations.Detailed information about nodes that were not migrated can bedisplayed upon demand: An overview of the reports and variants thatwere hanging under private nodes is available, as well as a list of alllist screens contained the old tree.
(Please be aware that reports that belong to a list are not necessarilystored in the node cited.)