Step 2(C) : Roles to be checked : This step helps to determine which roles are affected by changes to authorization data.You can double click on the authorization object for which SAP proposed check indicators and SAP proposed values need to be assigned to SU24. As per the below screenshot, the values are compared for those present in SU24 and those present in SU25 (i.e. The authorization objects for those tcodes can be compared for their check indicators and field values. The tcodes which have undergone any authorization object level change in new release, will be shown with red traffic light. Step 2(B) : Compare transactions : If any change has been made to check indicators or field values in SU24, you can compare these changes with the new SAP default values.Step 2(A) : Preparation: Compare with SAP values : This step is used to prepare the comparison and must be executed first.Step 2 : Post-processing the settings after upgrading to a higher Release: Steps 2A to 2D of SU25 are executed if you have used profile generator in an earlier release and you want to compare data with the new SAP default values after an upgrade. This is generally done when you use Profile Generator for the first time or when you want to overwrite SU24’s check indicator and field values with SAP default values. Step 1: Initially fill the customer tables – This step is used if the SU24 customer tables (USOBT_C and USOBX_C) need to be filled with SAP default values from the tables USOBT and USOBX. The below screenshot shows the steps of SU25: These steps are used to populate the customer tables of the Profile Generator the first time the Profile Generator is used, or update the customer tables after an upgrade (to update check indicators and field values of SU24). We will be discussing about these steps and also about when a certain step need to be executed. There are 6 different steps in this transaction code, not all of which need to be executed each time SU25 is used.
SU25 is a tcode which is executed during the initial implementation of SAP and also during each time an upgrade takes place. Let us discuss SU25 steps for SAP Security upgrade: Care should be taken while upgrading the system, because if the upgrade fails, it can affect business operations. This information can be found in the release note for the specific release. It should know if the new release brings “desired functionalities”. Business should be well aware of the reason as to why it needs to upgrade its system. The reason to upgrade SAP system should be driven by “Business Needs”. Why do we need to upgrade our SAP System?
This post is about SAP Security Upgrade (SU25 steps in SAP).
0 kommentar(er)
