Version compare during SPDD

Question

Hello, We are in the process of carrying upgrade. I am using SPDD. I see some yellow lights for table indexes. For most of the table indexes, when i do the version compare i see that almost 99% of the old version are identical to the current version and need no changes to the new version. Am i doing the version comparison correctly? Do i need to create a Transport (TR) even if the versions are identical? Thanks

Answer 1

Hi Ricky,
It's this function and the literature says it's a valid choice during SPDD phase:
Yes, the object should get added to SPDD TR and should disappear from SPDD after refresh.
However, after reading the follwing helptext to Message no. 0M400 (I do think it applies only to using SE95 to reset, not the SPDD):
"In the Modification Browser (Transaction se95), you can reset modified objects to the original.
Caution: In the SPDD phase, you should never use SE95 to reset objects because activation is required for this. Instead, modify the object - for example, using SE11 - so that it is identical with the original object. For this purpose, use the compare option in Version Management."
you also could choose to play safe, accept the "nonexistant" Modification, and reset to original in SE95 only after you are through with SPDD and DDIC Activation and have released the SPDD TR. You'll record the resets to original in another TR then.
Reset to original is also possible only if you do have the original in the system; use menu Modifications->Display Original to verify that.
cheers
Janis