Professional Documents
Culture Documents
Version Comparison
Version Comparison
In the next screen, select the tab "Maint. Objects". This helps to identify the maintenance view
for the relevant node. As you see in below screen, it is V_T052.
Now let us identify the underlying tables for the view V_T052.
Now, we can find underlying tables that are updated when we do any change through the
respective node in customization.
Other alternative is to find the list of tables from view definition in t-code SE11/SE12.
Step 2: Find out the version differences.
Go to t-code SCU0, select "Manual selection" option and click on create.
In the next popup, enter the list of table names identified earlier.
In next screen, Enter some description and RFC destination of the system to be compared with.
You can find the destination name from t-code SM59 or your BASIS consultant can help to
identify this. Once the details are entered, click on "Total comparison".
System prompts for user ID and password of destination system. Enter the details and proceed.
After this, A report summary is displayed with the list of differences between the two systems.
This is self explanatory.
Going into details of the differences between the systems, select one table at a time (This is a
restriction) and click on comparison button in tool bar.
Select the appropriate option in next popup. If we select restrict number of entries, addition
popup would appear to ask for selection criteria for filtering.
In this case, I am selecting total table comparison. After this, enter the log in credentials of
destination system again.
Below is the sample output (Part of the output is masked due to confidentiality).
If you are trying to change some existing entry, that should be shown same as the production
entry (White/light gray background). If it is different, further analysis can be done through
change logs t-code SCU3 and proceed accordingly. There shouldn't be any issue if our change
is related to creation of new entries as these entries doesn't exist in target system.
Same procedure has to be repeated for all the tables of the maintenance view to confirm the
dependency. This T-code can be used for any customization change irrespective of module.
There are many other options/t-codes that are being explored further to find out more Gems
hidden by SAP in their treasure...