Source Release with the Profile Generator (> SAP R/3 3.0F)

You must perform the following steps after an upgrade, if you were already using the profile generator before the upgrade.

• Choose steps 2A to 2C if you made a large number of modifications in transaction SU24 in the last release. Step 1 (Initial Filling of Customer Tables) should only be executed in transaction SU25 if you made no changes in transaction SU24 in the previous release. The system overwrites tables USOBT_C and USOBX_C when it executes step 1, and the values that you maintained in the last release are lost. In steps 2A and 2B, a synchronization procedure is performed.

• Step 2A

The tables USOBT and USOBX, delivered by SAP, are compared with tables USOBT_C and USOBX_C. You can find a description of the meaning of these tables in Upgrade Procedure.

• Step 2B

If you have made changes to check indicators or field values in Transaction SU24 in the source release, you can compare these with the new SAP default values. If you did not make any changes in transaction SU24 in the source release, the system displays a message informing you that a comparison is not necessary.

The status of the transactions is displayed at the right edge of the list of the transactions to be checked. The status is to be checked at first.

By selecting the appropriate menu entry in the list of transactions, you can set the status to checked, or reset it to to be checked without changing check indicators or field values.

If you want to copy the SAP default values for all transaction that you have not yet checked manually, you can choose the menu entry to copy the remaining SAP default values.

To go to the assignment of check indicators and field values, double click the line of the desired transaction. You can perform the maintenance as described in the documentation for transaction SU24.

The system displays the values delivered by SAP and those that you have maintained next to each other, and you can, if necessary, adjust them.

• Step 2C

All roles that are affected by newly added authorization checks and must be correspondingly supplemented. Edit and regenerate their authorization profiles. The system assigns the status Profile comparison required to the affected roles. Step 2C uses a traffic light system to display which roles must be checked after an upgrade. For revised roles, the traffic light is green. For roles that have not yet been revised, the traffic light is red. You can call the report repeatedly without overwriting adjustments that you have already made.

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. You should only leave the subprofiles that match your release upgrade in the SAP_NEW profile. The system assigns the status Profile Comparison Required to the roles and you can adjust them when you make the next required change: for example, when you are changing the menu for the role.

You can go to the authorization data for a role by double clicking on the corresponding line in the output list.

If you have roles in more than one client, you must perform this step separately in each client to determine the affected roles.

If you are upgrading from SAP R/3 Release 4.0B to SAP R/3 Release 4.6B and you used responsibilities in SAP R/3 Release 4.0B, these are automatically converted to derived roles, which replaced responsibilities in SAP R/3 4.5A (See SAP Note 156250).