The report tree data structure has changed. Existing report trees must be adjusted to the changed data structures if they are to continue to be used. The migration is performed by the transaction RTTREE_MIGRATION. You only need to run the transaction in the clients which contain the production versions of the report trees. Transaction codes are assigned to all reports in a tree during the migration. This allows you to put reports in the user menu in the role maintenance. You can define a company-specific transaction code prefix in the SAP Reference IMG under Basis ® System administration ® Report tree migration namespace.

If you have made changes to check indicators or field values in Transaction SU24, you can compare these with the new SAP default values. The previous and new settings are displayed in a list. You can decide whether you want to use each new setting or retain the previous one.

In the next step, the system displays a list of roles affected by changes to the authorization data. Edit and regenerate their authorization profiles.

To save time if you utilize a large number of roles, you can skip editing and assign the profile SAP_NEW to the users manually. The profile SAP_NEW is delivered with every new Release and contains the authorizations for all new checks in existing transactions.

Use step 2e to display a list of any transactions that have been replaced by one or more other transactions. A list of all roles containing such transactions is output.

In the last section, you can adjust authorization checks. This includes changing check indicators (Transaction SU24) and globally switching off authorization objects.