SPAU issues with: Without Modification Assistant: No versions found

[Former Member]

Hi,

We have upgraded from SAP 4.7 to SAP ECC 6 with Unicode.

After the upgradation we have started working with SPAU objects.

Currently I am working on SPAU: Without Modification Assistant.

I have gone though some docs in those they have asked to compare the versions using Version Management options.

But when I am tiring to check the Version Management for many of the objects I am getting the message: No versions found

Some of the objects are for which I am getting the message No versions found are as follows :

Selection Views : SAPBRFSTANDARD 100789 23.12.2010 ABCK900506

Programs :RM06BF00 Collective Release of Purchase Requisitions

Transactions FEBA A_1234 13.07.2006 XYZK906487 Postprocess Electronic Bank Statmt

Transaction Variants O4_TIGER1 D_ABCD 18.06.2005 AB5K901250

Screen Variants O4_TIGER1_0999 D_ABC 18.06.2005 AB5K901250

Message Classes 38 General Basis: ABAP Runtime Environment

Maintenance and Transport Objects J_1IEWT_ACKNS D_ABCDE 27.06.2008 ABC3910542

Request you to check and let us know how to proceed.

Thanks and Regards,

Prem.

<personal information removed by moderator>

Edited by: Thomas Zloch on Jan 18, 2011 12:43 PM

[Former Member]

Hi,

We have upgraded from SAP 4.7 to SAP ECC 6 with Unicode.

After the upgradation we have started working with SPAU objects.

Currently I am working on SPAU: Without Modification Assistant.

I have gone though some docs in those they have asked to compare the versions using Version Management options.

But when I am tiring to check the Version Management for many of the objects I am getting the message: No versions found

Some of the objects are for which I am getting the message No versions found are as follows :

Selection Views : SAPBRFSTANDARD 100789 23.12.2010 ABCK900506

Programs :RM06BF00 Collective Release of Purchase Requisitions

Transactions FEBA A_1234 13.07.2006 XYZK906487 Postprocess Electronic Bank Statmt

Transaction Variants O4_TIGER1 D_ABCD 18.06.2005 AB5K901250

Screen Variants O4_TIGER1_0999 D_ABC 18.06.2005 AB5K901250

Message Classes 38 General Basis: ABAP Runtime Environment

Maintenance and Transport Objects J_1IEWT_ACKNS D_ABCDE 27.06.2008 ABC3910542

Request you to check and let us know how to proceed.

Thanks and Regards,

Prem.

<personal information removed by moderator>

Edited by: Thomas Zloch on Jan 18, 2011 12:43 PM

[Former Member]

Login to your 4.7 version of the program and check the version history for any customer changes. If you find no versions even in the 4.7 version, then set it as 'Reset to original'.

PS: Please read the rules of engagement. Personal information should not be disclosed in public forums.

Vikranth

[Former Member]

Hi,

Thanks for the reply.

This is first time I am working on SPAU, so I want to confirm one question, I have checked the objects in 4.7, and many of the objects have the customer changes. So I should go to the change mode and make all the necessary changes and I have to save the changes and should compare manually with the 4.7 system.

Thanks and Regards,

Sham

[former_member404244]

Hi,

in SPAU you will be getting three things..

1>Green light 2>yellow light and 3>Red light

when the upgrade takes place if you see any object under Green that means the changes are automatically carried to the new version from older version

for yellow it has done partially and for red you need to do manually copying the code to the new version.

You have an option is "RESET to original" if you do this , the code will be reset to what SAP provided in the new version. Your old code won't be there.

Please go through the below link to understand about SPAU and SPDD.

http://help.sap.com/saphelp_nw04s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm

Regards,

Nagaraj

[Rushikesh_Yeole]

Check the version in old system.

CHeck the traffic light Grren or lred or yellow.

I case of red or yellow, version conflicts will happen.

If it is green, Reset to original.

[eduardo_hinojosa]

Hi

You must have the versions managament for dev.objects in your development enviroment. Perhaps, in the past, if anybody do a copy of mandant from production, he or she could delete versions. The versions are saved in table VRSD and help you to decide in SPAU if a modification is mantained or deleted by standard (ie, it's possible that entries were deleted). Check Note 130906 - How can versions be transported? for more information.

Regards

Eduardo

[Former Member]

Got the soluiton form SAP Market place.

Note number : 634146

Short Text SPAU: Objects from the customer namespace in SPAU

We need to execute RSUMOD_CHECK_NON_TADIR report so that we can delete the incorrect entries.

[Former Member]

hey prem,

I did the same but we got the list of objects and nothing moved out of SPAU.

Could you please elaborate on the solution.

Thankssss