We chose u0093Adopt Modificationu0094 instead of u0093Reset to SAP Originalu0094

[Former Member]

We applied Note 932711 back in July 2006. Then in Dec 2006, we applied support pack SAPKGPPD05 which contains the corrections of note 932711. Via transaction SPAU, during the application of SAPKGPPD05, we chose “Adopt Modifications” of the object modified by note 932711. We could have chosen “Reset to SAP Original” but we did not.

Now this choice is causing problems. We just applied support packs SAPKGPPD06 through 9. During the application, SPAU flagged the same object again and we chose “Reset to SAP Original” this time around. Now our applications related to note 932711 do not work as the corrections aren’t there anymore because of the “Resetting to original”. We also tried to re-implement note 932711 but it’s not implementable anymore.

Has anyone else made the bad decision of choosing “Adopt Modification” instead of choosing “Reset to SAP Original” the modifications which are already incorporated in the support stack being applied? Had we chosen “Reset to SAP Original” back in Dec 2006, we would not have this problem now. Yes, hindsight is 20/20.

We appreciate anyone sharing their experiences and knowledge on fixing this problem.

Thanks so much in advance.

Mario

[Matt_Fraser · Accepted solution]

Mario,

Did you apply the Note originally via SNOTE or manually? You might try re-applying it via SNOTE, but perhaps what you need to do is 'update' it if it won't re-apply, if there's a newer version of the Note available.

Assuming you no longer see the Note in SNOTE, you should be able to use Goto... SAP Note Browser, and then call up the implemented Note. Select it and click the button for "Download Latest Version of SAP Notes." Afterwards, if there were any updates to the Note, you should be able to re-implement with the newest version.

Also, if you implement with SNOTE, then later when you implement support packs that contain the Note, you shouldn't have to either "adopt" or "reset"... it should become automatically "obsolete," unless your Note was newer than the version in the support pack.

I'm not sure if this will help you to solve your problem, but perhaps it will help to point you in a direction to solve it.

Best regards,

Matt

[Former Member]

Mario,

Each of these adjusted objects should have versioning tunred on. Like for a report you can dig into the report in SE38, Utilities -> Versions -> Version Management. You should be able to 'roll back' to the working version.

This will not solve your SPAU issue though - you'll see it again. SNOTE may work, but it also may kick back that it's not applicable since you are on a support pack level higher than the note.

Note also that Resetting to orginal did not undo the original note corrections - be careful with your assumptions here - it may very well be that the new support packs introduced the issue - a very common occurance. Search the notes based upon your errors to see if there are advanced corrections for issues 'delivered' in the support packs. You should also open a SAP ticket with this same information.

Hope this helps.

Tim