SSERP85 - Report Tree Migration
This report transforms report trees that were created using the old version of transaction SERP (Release 4.5 and older) to the area menu structures used in Release 4.6. It should be executed in the client that contains the productive versions of your report trees.
The original report trees are not deleted and can still be displayed using transaction SARP. In order to avoid naming conflicts or redundancy, you must, however, delete the tree created in the target structure (using transaction SE43, area menu maintenance) before migrating the tree again within the same client.
Description of Select-Options and Parameters:
- Report Trees:
Selection according to the old technical names of report trees. This entry is merely a preliminary selection. You can restrict your selection values further on the subsequent list screen.
- Languages:
Enter those languages in which language-dependent text entries from your tree should be migrated to the new structure.
- Master language:
Language to be used as the tree's master language in future translations. Must already be contained in the list of possible entries (Choose F4).
- Development class:
Enter the development class that you want all trees to be migrated to.
Since the private nodes concept no longer exists in new trees, their contents are not migrated. Lists stored in your tree are not migrated either.
After you have made your selections, a table control appears where you have the opportunity to check the original language, development classes, and the name of the converted structure for each individual report tree selected.
Note: If the name of the target structure appears as the name of your report tree with the extension "_1, _2 ...", a report tree with the same name has already been migrated. Report trees that have already been migrated can be hidden by selecting the checkbox "Do not display report trees already migrated".
If you want to display any of the report trees listed, double-click on them in the list.
To start report tree migration, choose "Start migration".
The trees selected are checked for inconsistencies and removed from the final selection if any inconsistencies are found.
A log is displayed in compressed form after successful migrations. Detailed information about nodes that were not passed can be displayed upon demand: An overview of the reports and variants that were hanging under private nodes is available, as well as a list of all list screens contained the old tree.
(Please be aware that reports that belong to a list are not necessarily stored in the node cited.)