Scribd
Upload
342 views2 pages

SU25

The SU25 transaction is used during initial SAP installation and upgrades to copy check indicator defaults from SAP tables to customer tables. This ensures customer changes are not overwritten during upgrades. The SU25 process involves initially filling the customer tables, comparing customer and SAP values, accepting proposed SAP values or keeping customer values, and options to transport, modify roles, or branch to SU24. Changes made require thorough analysis and testing due to impacts on transaction security.

Uploaded by

debsankhaghosh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
342 views2 pages

SU25

The SU25 transaction is used during initial SAP installation and upgrades to copy check indicator defaults from SAP tables to customer tables. This ensures customer changes are not overwritten during upgrades. The SU25 process involves initially filling the customer tables, comparing customer and SAP values, accepting proposed SAP values or keeping customer values, and options to transport, modify roles, or branch to SU24. Changes made require thorough analysis and testing due to impacts on transaction security.

Uploaded by

debsankhaghosh
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

The SU25 transaction is needed during the initial installation of SAP and during each subsequent upgrade.

Its main utility is to copy the SAP provided check indicator defaults from the USOBT and USOBX tables to the corresponding customer tables, USOBT_C and USOBX_C. These two sets of tables are needed so that the customer changes are not overwritten by SAP delivered values during a future upgrade. The initial screen of the tcode is shown below.

SU25 - Initial Screen

As can be noted, the SU25 transaction is organized as a sequence of actions which need to be executed in order during installation/upgrade depending on requirement. For example, the first step (1) is to initially fill the customer tables (USOBT_C and USOBX_C) is ONLY executed during initial installation of SAP. Executing this step during a future upgrade will over-write all customer changes to check indicators. The next set of steps compare the customer value with SAP delivered values. We have the option of accepting one or more of SAP proposed values while keeping the customer values for the rest of the objects. Since any change to check indicators for a transaction will impact all roles with it, a change during SU25 should be thorough analyzed and backed up by rigorous testing of the affected transaction. The SU25 initial screen also has options to transport the new values for the customer tables, modify and generate roles which are affected by changes made for check indicators or even branch to SU24. Its also a good practice to document all changes performed during SU25 to help in future decision making around security.

You might also like