SUM requires snote download, but system settings do not permit

[former_member197700]

Hi gurus,

During the preparation for enhancement pack update, SUM stops and needs confirmation that a list of OSS notes have been applied.

One note is obsolete, but SUM won't continue unless I download the note with snote.  For QA and Production, I must open the system with scc4/se06 to perform the download.  Is there a method to avoid the system open, for example, a transport?

Warm Regards,

CM

[Former Member · Accepted solution]

I'd also be interested in any good solutions to this, as it's a bit of a pain.

Basically, SUM has a list of notes, and it cannot check whether they are valid in your system or not, unless they are loaded into SNOTE.

For valid notes, this is easy, you apply them in Dev, you transport them through your landscape before running SUM, and when SUM checks SNOTE it finds they have been applied.

For obsolete notes, it's not so easy.  In your Dev system, you download them in SNOTE, and SUM is able to check, see that they're not valid, and move on.  But you have no way to populate SNOTE in your other systems via a transport for these obsolete notes, which means that you now need to run SNOTE in every system and download these obsolete notes, just so that SUM will be able to see them and be happy that they're not needed.

It's not the end of the world, but it's a bit of a pain.  Most people never run SNOTE in any system other than Dev, so you can sometimes have problems running it in say a Prod system simply because your ID doesn't have access to run such things.

Yes, one solution for these is to edit the EHPINOTES.XML file and remove them, so SUM never checks, but that doesn't seem like a particularly clean or proactive solution.  What would be ideal would be a way to create a transport from Dev which just contained the SNOTE information for these notes, so that moving the transport had the same effect as downloading the note.  Much easier to send a transport to 10 systems than it is to run SNOTE 10 times, or modify an XML file 10 times...

[martin_mikala · Accepted solution]

SAP recommended me remove obsolete notes from EHPINOTES.LST/XML files. And this helped me.

[former_member197700 · Accepted solution]

Thank you for more clearly explaining what I was trying to say. As you stated, editing an xml is not idea, but it does beat opening the production system, downloading an obsolete note, and closing it again so thank you for the workaround.