Application Development 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: 

SPAU - Reset objects

ricky_shaw
Contributor
0 Kudos

Hello, While doing SPAU during upgrade, some of the programs like Func Groups/FM's,BOR objects, Screens..etc are asking for access key/object key. In that case, i am comparing the current & previous versions of the object and if there are NO changes to be made to the current version, then i am choosing 'Reset to original'. Is this way of resetting the objects, a right way to do? if not, can anyone please suggest the alternatives? thanks

1 ACCEPTED SOLUTION

ceedee666
Active Contributor
0 Kudos

Hi Ricky,

resetting objects to standard is always the best option. This way you will reduce the amount of objects that need to be compared in the next upgrade. The situation you are describing occurs, for example, if a objects was changed due to the implementation of a SAP Note, and this changes is now incorporated into the version to which the upgrade is performed.

However, when comparing versions be sure that you really compare the previous active version with the new SAP version. Usually you'll see 2 SAP versions after the upgrade. You need to compare the most recent SAP version with the one that was modified (most likely a non-SAP) version.

Furthermore, it is advisable to also carefully check non-identical versions. There are a lot of reasons why the versions might not be identical but a reset to standard is the best option (e.g. the new version of an table was further extended by SAP and contains now all the fields of the previous one plus additional field).

Best,

Christian

2 REPLIES 2

ceedee666
Active Contributor
0 Kudos

Hi Ricky,

resetting objects to standard is always the best option. This way you will reduce the amount of objects that need to be compared in the next upgrade. The situation you are describing occurs, for example, if a objects was changed due to the implementation of a SAP Note, and this changes is now incorporated into the version to which the upgrade is performed.

However, when comparing versions be sure that you really compare the previous active version with the new SAP version. Usually you'll see 2 SAP versions after the upgrade. You need to compare the most recent SAP version with the one that was modified (most likely a non-SAP) version.

Furthermore, it is advisable to also carefully check non-identical versions. There are a lot of reasons why the versions might not be identical but a reset to standard is the best option (e.g. the new version of an table was further extended by SAP and contains now all the fields of the previous one plus additional field).

Best,

Christian

Former Member
0 Kudos

Hi Ricky,

Yes it is a good approach.

Please go through the following document which will be very helpful in your SPDD and SPAU.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/709abcf3-7d77-2c10-8d86-b9d2cb01c...

Regards,

Kannan