SAP Knowledge Base Article

Symptom

Asyoualreadyknownthat,itisnecessarytoperformSPAUadjustmentduringoraftersystemupdate(upgrade/EHPinstallation/supportpackageimplementation).

As to the part of "Note corrections" in SPAU, there are following status:

1.Greytrafficlight

ItmeansthattheSAPnoteisobsolete,youcanjustselectthenotenumberandchoose"ResettoOriginal".

2. Green traffic light

ItmeansthatsomecorrectioninstructionsincludedintheSAPnoteareobsolete,butothersarestillvalid.Youcanjustclickthegreentrafficlight,theobsoletepartwillberesettooriginal.

3. Yellow traffic light

ItmeansthattheSAPnoteisstillvalid,youmustimplementitagain.Youcanclicktheyellowtrafficlighttoimplementit.

ButsometimeitmayhappenthatobsoleteSAPnotesaredisplayedwithyellowtrafficlightinSPAUlist.IfyoucheckthesenotesusingSNOTE,youwillfindthattheimplementationstatusforthemis"obsoleteversionimplemented".WhenyouclicktheyellowtrafficlightforthesenotesinSPAU,youwillgetmessageSCWN029"SAPNoteobsolete,willbedeimplemented",thenthecorrectionsincludedinthesenoteswillbedeimplementedcompletelyorpartly.

IfyoucheckthesenotesinSNOTEafterdeimplementation,theimplementationstatusforthesenoteschangestobe"Obsolete".AndifyoutrytoimplementthesenotesagainusingSNOTE,youwillbetoldthat"SAPNotealreadyimplementedbySupportPackage"or"SAPNotedoesnotcontainvalidcorrectioninstructions",whichmeansthatitisnotpossibleforyoutoimplementthesenotesanymore.

Attention:ItDOESNOTmeanthatalldeimplementationshappeninginSPAUadjustmentareincorrect.IftheSAPnoteisvalidtothesystemafterupdated,buttheversionalreadyoldversion,yellowtrafficlightwilldisplayforthisnoteaswell.Ifyouclicktheyellowtrafficlightforthisnote,thenotewillbedeimplementedfirstly,thenimplementedagain.AfterSPAUadjustment,theimplementationstatusforthisnotechangestobe"completelyimplemented"inSNOTE.Insuchcases,itisnotaproblem.

Reproducing the Issue

For example:

SAP note 884267 displayed with yellow traffic light in SPAU

This note is valid for FINBASIS 300-600. But the system is on FINBASIS 604.. So this note should be obsolete. The status for it is NOT correct. It should be displayed with grey traffic light, but not

1928534 - Obsolete SAP notes deimplemented during SPAU adjustment

Version 2 Validity: 29.10.2013 - active Language English

yellow traffic light.

IftocheckthisnoteinSNOTE,theimplementationstatusis"obsoleteversionimplemented".

Iftoclickyellowtrafficlightforthisnote,yougetmessagethatthenoteisobsoleteandwillbedeimplemented:

If you continue, the corrections within this note will be deimplemented wrongly:

Cause

program Bug, see SAP Note 1720495

Resolution

IfmessageSCWN029"SAPNoteobsolete,willbedeimplemented"occurredwhenclicktheyellowtrafficlightforoneSAPNote,pleasecheckwhetherthisnoteisstillvalidornot.Ifthisnoteisreallystillvalid,youcancontinuedeimplementit.Butifyoufinditisalreadyobsolete,youcanchoose"nodeimplementation"withdeselectingalltheobjectsasbelow:

Afterthattheimplementationstatuschangedto"Obsolete"automaticallywithoutdeimplementation.ThenotewilldisappearfromSPAUlistautomatically.

Inordertopreventtheproblem"obsoletenotesdeimplementedduringSPAUadjustment"fromoccuringduringsystemupdate,pleaseimplementSAPnote1720495beforeperformingSPAUadjustement.ThisnoteisalsoincludedinthecollectionSAPnote875986.(IfyoufindthatanyobsoleteSAPnoteweredeimplementedevenafterimplementingSAPnote1720495,pleasecontactSAPASAPbycreatingmessages.

Inmostcases,itisdifficultforyoutorecognizethattheproblemalreadyhappenedduringSPAUadjustment.Butyouwillfindthatlotsofdumpsareoccurringaftersystemupdate.Andifyoucheckfurther,youwillfindthatsomecorrectionsdeliveredbysystemupdatearelostormissingaftersystemupdate.

Iftheproblem"obsoletenotesdeimplementedduringSPAUadjustment"hasalreadyhappened,youcanfindoutalltherelevantSAPnoteswhichwerewronglydeimplementedusingreportSCWB_NOTE_MONITOR.

In SE38 execute report SCWB_NOTE_MONITOR, in the next screen specify the start date/time and end date/time when SPAU adjustment was performed, or specify the request with which SPAU adjustment was performed:

Inthenextscreen,searchthenoteswithstatus"obsolete",checktherelevantimplementationlogswhichlike

Correctioninstructionsxxxxxxxxxxxxxxxx0000xxxxxxx00xxcompletelydeimplemented

or

Correctioninstructionsxxxxxxxxxxxxxxxx0000xxxxxxx00xxincompletelydeimplemented

existsornot.Ifexist,thenotewouldbetheonewhichwasdeimplementedwrongly.

If the problem already happened, there are two possibilities to resolve the problem:

1).Findanothersystemwhichhasthesamesupportpackagelevelastheproblemsysteminyoursystemlandscape,createarequestinthissystemtoincludeallaffectedobjects(forwhichcorrectionswere deimplemented wrongly during SPAU adjustment), transport this request into the problem system.

2).Ifitisdifficultforyourtofindsuchasystemmentionedin1),andthereareonlyafewobjectswereaffected,youcanretrievethestandardversionwhichwasdeliveredbysystemupdatebeforeSPAUadjustmentviaversionmanagementfortheseobjectsonebyonemanually.

Ifthereisnosuchasystemhavingthesamesupportpackagelevelandtherearetoomanyobjectsaffected,itwillbeverydifficultandtime-consumingtoretrievethecorrectversionforalleffectedobjects.Asystemrestoremightbeamoreefficientway.

Keywords

SPAU, SCWN029, SNOTE

Header Data

Product

This document is not restricted to a product or product version

References

This document refers to:

CSS SAP Notes

Released On 01.11.2013 06:49:31

Release Status Released to Customer

Component BC-UPG-NA SAP Notes Assistant

BC-DWB-CEX Customer Extensions

BC-UPG-TLS-TLA Upgrade tools for ABAP

Priority Normal

Category Problem

1720495 Invalid deimplementation of obsolete notes by Snote tool 875986 Note Assistant: Important notes for SAP_BASIS up to 702

Other Components