Showing posts with label SAP Upgrade. Show all posts
Showing posts with label SAP Upgrade. Show all posts

SAP Security related activities in Upgrade

The SAP system profile parameter auth/no_check_in_some_cases has the value
“Y”. If the profile parameter is set to .N, the value must be changed. (This ensures better security).

If roles were already used in the source release, they must be updated. Transactions that were selected in the menu of existing roles can be protected using additional authorization objects in the target release. This means that tables USOBT_C and USOBX_C have to be updated as well as the existing roles.

The SU25 tcode is used for to fill the customer tables of the profile generator the first time the profile generator is used, or update the customer tables after an upgrade.

1. SU25
Step 2A

Compares the new USOBT and USOBX tables with USOBT_C and USOBX_C.
This compares the Profile Generator data from the previous release with the data for
the current release. New default values are written in the customer tables for the
Profile Generator

Step 2B
Add any new transactions/updates to tables USOBX_C and USOBT_C.

If you have made changes to the check indicators or field values in transaction
SU24, you can compare these with the new SAP defaults. You can see the values
delivered by SAP and the values that you changed next to each other, and can make
an adjustment, if desired.

Hint:
Steps 2A and 2B make changes to the customer tables of the Profile Generator.
If you want to transport these changes, choose step 3 in transaction .SU25. Before implementing any changes in system, take corresponding business approval for all role changes. The step 2C and 2D step will clearly identify the roles affected and new tcodes introduced in new systems.


Step 2C

This step guides you through all the roles that are affected by newly added authorization checks and that have to be changed to correspond. The corresponding authorization profiles need to be edited and regenerated. You can jump directly to role maintenance.

SU25, 2C step also contains the new SAP roles introduced.

If you go to one by one role, there are some authorization objects that are got affected during upgrade. We can categorize these authorization objects as below:-

1. Standard New – These are new authorization objects that are introduced in new system for corresponding tcode.

2. Manually new - It shows the authorization objects which were manually added in old system. Some of the values got updated for this also.
3. Standard Updated - Updated means, in old system if you have kept the standard values as it is, SAP has updated these standard values (u can check this one in SU24 check indicators).
4. Maintained New- Some of the organizational values introduced as field in authorization object.

After maintaining all new authorization objects, you can save it and generate the profile. If you get back to SU25 2C step shows all the roles with green signal. Means all roles saved and generated.

SU25, 2C step also contains the new SAP roles introduced.
After generating all profiles in SU25 2C step, you can jump to 2D step.

Step 2D
If you execute this step, it will show the list of roles and old tcode and corresponding new tcode.
If business wants to use new tcode, then u can replace old tcodes by new one by clicking on automatically adjust menu. Otherwise go to manually adjust menu and generate the profile.
The new tcodes are introduced in 2D step, this doesn't means the old tcodes are no longer exists in new system. We have to check manually for each and every tcode.Some tcode does not exists in new systems. FOr e.g. RZ02 is replaced by RZ20 in ECC6. RZ02 no longer exists in ECC6.

STEP 3
This step transports the changes made in steps 1, 2a, and 2b. Tailoring the Authorization Checks .This area is used to make changes to the authorization checks.

STEP 4
Changes to the check indicators are made in step 4. You can also go to step 4 by calling transaction-SU24.

You can then change an authorization check within a transaction.

1. When a profile to grant the user authorization to execute transaction is generated, the authorizations are only added the Profile Generator when the check indicator is set to Check/Maintain.
2. If the check indicator is set to do not check, the system does not check the authorization object of the relevant transaction.

Review Items:-
Security Related Parameters
You can compare and check security related parameters from old release to current release.
Review users (via SU01) to check for any new or changed fields on the user masters (Check especially background user-ID for authorizations, to avoid cancellation of batch jobs).

Migrate Report Trees

Use

The report tree data structure was changed in SAP R/3 Release 4.6B. Existing report trees must be adjusted to the changed data structures if they are to continue to be used. This also allows you to put reports in the user menu in the role maintenance.

Procedure

  1. Call the transaction RTTREE_MIGRATION. The migration is automatically executed.
  2. Transaction codes are assigned to all reports in a tree during the migration.

  3. In the SAP Reference IMG, call Set Namespace for Report Tree Migration under the node Basis ® System Administration. You can, if you wish, enter a company-specific prefix for the transaction codes here.

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).

SAP Upgrade Procedure

After an upgrade, you must make adjustments to the user and role administration. What these are depends on whether you were already using the profile generator in the source release.

In the following, it is assumed that you have not yet used the profile generator, and that you are not upgrading from SAP R/3 3.0F.


If you were already using the profile generator in the last release, read Source Release with the Profile Generator (> SAP R/3 3.0F).

First of all, choose one of the following options:

  1. Convert the profiles that you manually created to roles. To do this, choose step 6 in transaction SU25.
  2. This has the advantage that the administrator can assign all of the existing, thoroughly checked profiles to the corresponding roles. You can, however, only create a user menu for the role if the corresponding authorizations for the authorization object S_TCODE are contained in the profile. Additionally, you cannot use the configuration tables (USOBX_C, USOBT_C) in which the predefined authorization values are contained.

  3. Carry out a new implementation of the authorization administration using the profile generator.

This has the following advantages:

      • Customers’ experiences have made it clear that the time invested in the new implementation of the authorization administration pays off with a large time saving during other maintenance of the user and authorization data.
      • Your employees can take advantage of user-friendly user menus.

We recommend the second option. In addition to the advantages already mentioned, you can use the three level model for the implementation of roles, as shown in the section First Installation Procedure. A redesign of the authorization administration using the three-level model makes sense in the long term, in that the work time that an authorization administrator must expend for the maintenance of the roles can be significantly reduced.

If you have decided to use the second option (Redesigning the Authorization Administration), read the First Installation Procedure, and the following advice:

  • Plan the conversion of profiles to roles. Produce a list of transactions and associated profiles for which you want to set up roles. Use the Infosystem (transaction SUIM). You can download the Infosystem lists to a Microsoft Excel sheet and use it as the basis for the migration to be performed. Contact the departments and discuss which roles should be provided for which departments.
  • During the conversion to roles, you can decide if the naming conventions that you used have proved to be useful. If necessary, you can define a different naming convention.
  • Create the new roles in the development system.

The following procedure may be useful when copying the authorization values from the old profiles:

Open three sessions in the SAP system.

      • In the first session, start transaction SU02 and choose a profile that you want to convert to a role
      • In the second session, call transaction PFCG and create the new role there.
      • In the third session, start the transaction SUIM as a utility for maintaining the authorizations. Choose Authorization Objects ® Authorization Objects by Complex Selection Criteria. Enter the name of an authorization object. You want to know, for example, in which profile the object S_TABU_DIS is used. Choose Where-Used List. Choose the profile for which you want to create a role. Select the profile and choose Expand Subtree.
        You can now search for the desired authorization object (in this case S_TABU_DIS) and enter the authorization values in the role.
  • When you have finished the conversion of profiles to roles, call step 2C of transaction SU25.

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.

Transaction SU25 would have produced no output for profiles. It makes sense to create the roles beforehand, in order to find out which roles authorization checks have been added for.

  • Call step 2D to find out if transaction codes have been changed in the new release. You can also download this list to a Microsoft Excel sheet and then remove the old transaction codes during the test phase once the testers are satisfied with the new transactions.

Step 2D uses a traffic light system to display which roles have already been revised after the upgrade. For revised roles, the traffic light is green. For roles that have not yet been revised, the traffic light is red. You can switch the traffic light from red to green by double clicking it. You can call the report repeatedly without overwriting adjustments that you have already made.

In Step 2D, you can use the following pushbuttons to add new transactions to roles or to replace old transactions with new ones:

      • Manually adjust menu

You can manually replace or add transactions.

      • Automatically adjust menu

Old transactions are automatically replaced by new ones.

      • Automatically add menu

You can use this function to add the new transactions to each role. The system checks whether the role already contains each individual transaction. It is only added to the role if this is not the case. In this way, the users can continue using the old transactions until they have had time to learn how to use the new ones.