Report Tree Migration

Scope of Functions

In Release 4.6, the report trees are integrated in the area menus. Report trees are processed using the area menu maintenance tools.

This provides the following advantages:

• Uniform navigation through all functions in the R/3 System

• Improved authorization checks through granting of transaction codes for all report types

• Support for the componentization of R/3 application components

• Reuse of subtrees using reference technology

• Uniform concept for user-specific and system-specific adaptation of menus and report trees

All of these goals are supported by activity groups. When a user assigned to one or more activity groups logs on to the system, the system displays the relevant user menu in a tree. SAP delivers a number of typical activity groups. These are client-dependent.

The activity groups are integrated in the Profile Generator, thus simplifying authorization administration.

The SAP menu, which provides an overview of all functions delivered by SAP, is also available. This overview can be used if no user menus have been defined.

The activity groups include a selection of typical functions, while the SAP menu includes all delivered functions.

All standard report trees delivered by SAP are integrated in the SAP menu. They can be used as templates for your own activity groups.

The integration of the report trees in the area menus and the introduction of activity group replace the following:

• Authorization groups in report trees

• Client-dependent and user-dependent report trees

To use your own report trees, these must be migrated to area menus.

If you still want to use the old report tree tools, you can use the activity group delivered by SAP that includes all the old start transactions for report trees. We recommend you only do this if urgently required.

Migrating your own report trees

To migrate your own report trees to area menus, first log on to the client where the report trees you want to convert are located. Call Transaction RTTREE_MIGRATION . You use this transaction to generate area menus from your report trees.

To use the generated area menus, use Transaction PFCG to add these menus to your own activity groups. Then assign users to one or more activity groups using Transaction PFCG or user administration. If you want to be able to access the area menu created from the report tree in the SAP menu, you can add the menu to the SAP menu using Transaction SE43.

Continuing to use the old report tree tools

If you want to continue to use the old report trees and the corresponding tools, you can do this using a work center menu delivered with activity group SAP_CA_OLD_REPORTINGTREES_AG . In user administration or Transaction PFCG, assign this activity group (or edit it and then assign it) to users who require access to the old report trees.

We recommend you only use the old report trees if urgently required, as they are very difficult to integrate in the new navigation concept and will no longer be developed. This allows you to display the report trees, but not to change them.

Effects on Existing Data

As the report trees are used as templates during the migration and not deleted, there is no danger of data loss.

See also

For more information about the migration tool RTTREE_MIGRATION, see the online documentation.

During the migration, transaction codes are automatically assigned for all reports in a tree. If you want to create these using a company- specific prefix, you can set this in the Implementation Guide (IMG) by choosing "Basis" -> "System administration" -> "Set namespace for report tree migration".