Skip to Content
Product Information

OSS – Finding notes

I recently read a very nice blog about finding Finding what tables and fields lie behind an SAP transaction.  It made me think about some of the things that I do.  One of them – searching for OSS notes is something that I do on a regular basis.  It sometimes makes for a long day.

Does needle in a haystack sound familiar?  This documentation is meant to give you a starting place.  Remember there are many different ways to find OSS notes.   Explore your own.  If you find one that works well, please add your comment.

15 Comments
You must be Logged on to comment or reply to a post.
  • SAP note 192194 is also very usefull and even the official way to find notes via the attributes behind it, but I must admit it is rather difficult to find itself using it’s own advise… 🙂

    Cheers,
    Julius

    • I’m so glad I wrote this blog!  Thank you for the note information.  I’ve just read it.  There are a lot more ideas on searching.  And believe me – some days I need it.

      Thank you for the information!

      Michelle

  • Please also see the last sentence in the note and make use of the switch framework instead of the debugger.. 🙂
    • OK – I read and re-read the note.  I’m not sure what you are trying to tell me.  Can you explain?  For me and maybe some others who are having problems with this.

      Switch framework for switching off all our enhancements to SAP code?  At this point we have used classical BADIs, user exits…  It’s not so easy to turn these off.  And I’m not sure how that would help with debug.

      Thank you,

      Michelle

      • Did you find this OSS note (;-)) for a way to best implement custom code, by mixing old technologies with enhancement and switch framework: Note 1257033 – Cookbook: Modification/enhancement for standard SAP system
      • It was just a little joke about the last sentence in the note if you seek SAP support and a note does not solve thze problem.

        It is an old not (prior to the switch framework) and suggests changing the program name in the debugger to determine whether it is SAP code (-> support) or customer code (-> consulting) causing the problem in thze first place.

        Also see SAP Note No. 7 (seven). Obviously it did not take the first folks long to find that one… 🙂

        Cheers,
        Julius

  • A good way to shift through the notes results is to restrict the search by system (this only works if you have an OSS account that is connected to the company’s system).

    This restriction filters out all notes that are not applicable to your system’s version.

  • Hi, nice blog. I would make a correction to slide 19: you don’t create an OSS *note*, you create an OSS *message*.. 😉
    • Very true. 

      Thank you for the catch.  I’ll fix it.

      • Please take note that a program does not have to dump for there to be a bug, and might have created bug-dependent data already as well.

        I can also recommend proactively keeping an eye on application component which interests you for notes.

        In my area (security) this is not only limited to BC-SEC so SAP came up with a great solution.

        See SAP Note 888889.

        Cheers,
        Julius

        • Well you know what they say about Cockroaches.  If you’ve seen one, there are always more hidding. 🙂

          My next reading material is note 88889.

  • it is very icely presented and informative.

    muthu