Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Version compare during SPDD

ricky_shaw
Contributor
0 Likes
3,342

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

1 ACCEPTED SOLUTION
Read only

ThangaPrakash
Active Contributor
0 Likes
2,011

Hello Ricky,

In SPDD output, place your cursor on the index and click on versions in the toolbar.

Like below you can select the original version and click on retrieve, the system will ask for a transport request. Save and then activate it.

Regards,

TP

8 REPLIES 8
Read only

Private_Member_7726
Active Contributor
0 Likes
2,011

Hi,

If the versions are identical i'd still revert to the original for the object, so it does not show up in SPDD for subsequent upgrades.

cheers,

Janis

Read only

0 Likes
2,011

Hi Janis,

How do I revert it to the original? Will it prompt for a TR in this case?

Read only

0 Likes
2,011

Hi

Yes.Whenever you revert the changes,it will prompt for the TR.

Thanks,

Sreeram

Read only

0 Likes
2,011

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

Read only

ThangaPrakash
Active Contributor
0 Likes
2,012

Hello Ricky,

In SPDD output, place your cursor on the index and click on versions in the toolbar.

Like below you can select the original version and click on retrieve, the system will ask for a transport request. Save and then activate it.

Regards,

TP

Read only

0 Likes
2,011

Hello again,

Please tell me if I doing in a right way.

What i am doing in SPDD is as below:

For data elements: I am manually comparing the entries and if difference exists add those entries if needed and then put that into a TR(even if no change is done). After this, i am clicking on button 'Processor/Status' and checking on 'completed' box for all user entries to see a green check mark.

Same way I am doing for tables & also in SPAU.

Am I missing something here?

Pls suggest.

Read only

0 Likes
2,011

Sounds right, and yes, you should "turn the worklist green"... the only somewhat confusing part is that SPDD should have preceded SPAU and happen in so called shadow system - otherwise modifications are lost.

Read only

Former Member
0 Likes
2,011

This message was moderated.