Skip to Content
avatar image
Former Member

Unable to reset obsolete notes during SPAU "Format of correction instructions XXXX"

I have upgraded from R/3 4.6C to ECC6 EHP7 (SAP_BAIS 741 SP0016)
In SPAU it is not possible to reset any obsolete notes, message "Format of correction instructions xxx, unable to read corr. instruct'
I seems that SAP wants to read a correction in the note although it is obsolete regarding to component SAP_APPL version
Thanks for your help

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Oct 05, 2017 at 06:32 PM

    If the obsolete notes are the only ones you are having problem with then I'd suggest to reach to the SAP Support.

    This is not an ABAP question though, make sure with your Basis admin first. Or add one of those Netweaver tags and hopefully someone will see this on SCN.

    As a side note, always include the message class and number when posting such questions on SCN. And search SAP notes by that number.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 17, 2017 at 12:00 PM

    Thanks for this reply, I had already open a message to SAP, the answser is below:

    "The only way to solve this problem consistently would be to provide the missing note information by a transport from the source system of the inconsistent transports. Due to the history of your systems this is not possible anymore.

    Accordingly there is no other way to overcome the problems than deceiving the system the completeness of the information and to reset the notes/objects affected manually and individually to SAP original, neglecting the standard SNOTE/SPAU procedures.

    The consequences of this manual intervention are:

    1) The objects/information is not automatically included in transport requests => this has to be done manually.

    2) These are system tables, so in generally these entries are created by the system. To change these entries means, that later no-one can decide, which entry is correct and which one is manipulated. This can have consequences for later support decisions. That's why we need your approval to do this, because we cannot overtake the responsibility for these entries anymore."

    -> No "classic" solution, instead a manual procedure that does not certificate the system anymore and no insurance that the problem won't occur in the subsequent systems to be upgraded

    Add comment
    10|10000 characters needed characters exceeded

    • Have you discussed this with a local Basis admin?

      I'm not sure what obsolete notes you have exactly but I'd probably just let it be if they don't cause any harm. Otherwise you'll have to review each note to make sure the actual ABAP code is not affected and then SAP would need to do the update they suggested. It's up to you and depends on the note volume and impact.

      Unfortunately, it's much easier in SAP to install a note than to get rid of it. :(