Upgrade Procedure  

You should perform the following activities in an upgrade from a Release before 4.6A to Release 4.6A or later:

  1. Migrate report trees
  2. 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.

  3. Reconcile the default check indicator and field values in the previous and new releases in transaction SU25 (steps 2a - 2d).
  4. 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.

    Step 2d display a list all roles containing any transactions that have been replaced by one or more other transactions.

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

  5. Activate the Profile Generator

This step is not necessary in new installations or when upgrading from Release 4.5B or 4.6A to 4.6B, as the parameter is already set.

Make the following setting in the system profile maintenance:

auth/no_check_in_some_cases=Y

This parameter setting has the following effect:

Help ® Application help in transaction RZ10 contains system profile parameter maintenance information.

  1. Install the Central User Administration and perform the user administration with the Global User Manager if several systems must be managed. See Central user administration.