SAP OSS Notes Series – Part 2 – Discovering and reading notes
This is the second part of a series called “SAP OSS Notes”. If you missed part one, I suggest you to read before continuing this post. On the first post, we talked about how SAP give versions to its software and how is the strategy to update it. Moreover, we answer 5 simple W’s questions about SAP OSS Notes.
In part 2, we are going to see how a SAP Note is documented and the different ways to find and read it.
How to find a SAP Note
There is a few ways to search and find for a SAP Note. However, I organized this post according to the situations you might have. Depending on the circumstances, you are going to search for a note in a different way.
Scenario I: You already know the SAP Note
As you might know now, a SAP Note is represented by a number. It contains bug fixes and sometimes documentation about a specific subject. You might be given a SAP note number when using search engines as Google or reading a thread here at SDN.
So, if you have a problem and someone suggests you to check out a SAP Note, you might do it in two ways.
Again, SAP Marketplace is where you check for SAP notes. On the home page, click on “SAP Support Portal”. Enter your credentials (they are not the same as SDN – SAP Marketplace is not available to anyone). On the menu of the following screen, go to:
Help & Support >> Search for SAP Notes & KBAs.
Supposing you want to check SAP Note 1444611, enter its number in the right side of the screen.
A new tab will be opened with SAP note documentation as below.
In the upper part, we can see the note title, its current version (we are going to discuss SAP Notes versions on a next post) and the validity. The sections in blue and orange in the body are common in most SAP Notes. Let’s discuss a little about them in the last section of this post.
Even thought you might not have a SAP Marketplace account you might be able to see a note. Log into your SAP system and enter in transaction SNOTE. There, you can download the note you wan to see and open it. Be aware that when using this transaction you will always have to know the OSS Number. It’s not possible to search for notes using different criteria as it’s possible in SAP Marketplace. Also, you will usually do from a development environment because if you apply the note a transport will be generated.
To download a SAP Note, go to the green icon marked below and enter the note number in the proper field.
If you get an error tell the admin responsible. If you get a success message, then you can open the sap Note.
A simple report will be shown. Enter the note(s) which are already downloaded by the transaction. Afterwards, the OSS note will be shown in a PDF format as below.
Basically, the same information displayed in the transaction is the one available in SAP Marketplace.
Scenario II: You want to check the existence of a SAP Note
Usually, searching for a SAP note is not the first option when coming across an error in the system. You might check first some master data, system configuration, user privileges and other data which might cause a specific problem. However when you are sure everything is set right and the problem still persists, it’s worth searching for some SAP notes which might fix the issue.
Search Engines and SDN
You might use SAP Marketplace to search for a specific term and this is totally feasible. Note that you can sort SAP Marketplace results by release date and this is important when the error you have is related to something new in the system. The advantage of SAP Marketplace is that you can search for a note for a specific product/software component. However it’s also possible to search for the DUMP/error message you might be getting in Google/SDN and someone suggests you to read a specific note. Then you would fall in the first scenario already described.
How to read a SAP Note
No matter you open a SAP Note in SAP Marketplace or SNOTE transaction. The documentation is organized in the following sections. Understanding how to read a SAP note is crucial to understand if it applies to you. Check the sections below:
Symptom – This section will describe the error being fixed by the note. Basically, what error occurs and when it occurs.
Other Terms – some keywords that might be used to search for this note. Usually related to the error name, transactions or tables involved.
Reason and Prerequisites – This section will describe why the error occurs and also if you need to check/apply previous SAP Notes before the current one. (prerequisites will be discussed in a future post)
Solution – Usually, it will contain the the application of the note itself. However there might be manual steps in this process. (Manual steps will be discussed in a future post)
Header Data – Information about the product component being fixed.
Validity – This section is one of the most important ones. It tells you if the SAP release you are on contains the error described by the note. If you don’t find your release in the table, you shouldn’t worry about the SAP because the error just doesn’t happen in your release
Correction Instructions – This sections contains all changes of the SAP repository objects being fixed for each release.
Support Packages & Patches – This section is also very important. It tells you which Support Package contains this note. As a consequence, if you are on SAP ECC 6 EHP 04 SP 11 and the Note is contained in SP 7 of ECC 6 EHP 04 then you don’t have to worry about the note as well – it is already fixed. On the other hand, if the note is contained in SP 11 of ECC 6 EHP 04 and you are in SAP ECC 6 EHP 04 SP 10, then you will have to apply the SAP note independently or wait for the next upgrade project of the company you work for the see the error fixed.
Tags – Other search terms that you might use to find this note.
Attachments – Some SAP Notes contains a sections for attachments as well (just show in SAP Marketplace). They are available when you have to upload a file in your system or when the documentation is so big that SAP creates some PDF files for it instead of writing everything inside the note body.
Coming Up Next
We will see in part 3 how to apply a SAP note considering possible pre-requisites and manual steps usually performed by different people (BASIS, ABAPers an Functional professionals).
Searching for a SAP Note and knowing how to read it is crucial to check if you have a system or customization issue. Also, it enables you to validate if you release has a specific bug and decide if it’s the right time to fix it or not. Search for some notes in Marketplace and SNOTE and get used to this process. Also, read each section and understand what is the purpose of this note. And also, if you found this post useful or have a specific question, don’t forget to comment below.
Excellant explanation..thank you very much. Please add link for Part 3.
Thank you Abhishek.
To be honest, part 3 is not written yet. As soon as I write I will definitely update both posts with links. Please follow the post to get the notification.
Enjoying the series. Will you be explainig the differences between SNOTE and Marketplace versions as well as language comparison tools of the different versions of the same note?
I keep my fingers crossed when we reach the milestone of 2000000.
Well, the last episode will be more focused on pre-requisites and things that might go wrong.
In terms of language comparison tools, what are you referring to? Usually SAP recommends to be logged in English when applying a SAP Note and then manually translate what is needed.
I have noticed that SAP Notes come in two languages: English and German. If a Note has multiple versions as many of them do, sometimes you can compare the text of the note between versions and you have to choose the language in which the comparison should be performed. I have seen some notes that don't have the 100% equivalency in one language versus the other, but maybe this was by design.
Got it. Thanks for the suggestion.
Usually I just read the last version of notes on marketplace. However, there are some old and famous one which might require you from comparing versions. Thanks for the suggestion. I will definitely include on the last episode.
Article is well documented. Thanks for sharing.
How to find notes which can be applied to a specific system?
The applications System Recommendations and Maintenance Optimizer within the SAP Solution Manager show relevant notes which can be applied to a system.
All technical system types which you register in the LMDB are covered: ABAP, Kernel, Java, HANA, ...
Examples for usage:
SAP Active Global Support - Security Services
Explained well.. Thanks for the post.
Awaiting for the Part 3 ....
Thanks for the comment. It was already published some months ago. It had to be moved to a different space so that's why it might be hard to find.
SAP OSS Notes Series - Applying SAP Notes
Very well explained.
However the access to the 3rd part shows unauthorized. Can someone suggest how to access part 3?
For some unknow reason my post was rejected yesterday with no justification by the moderation.
It had 30 likes, 25 bookmarks, 20 comments, 10 5-starts... a 18 months old blog post... I just can't understand.
That sounds strange. But I enjoyed reading first 2, and I am sure most people did.
Thankyou for posting.
Nice article Fabio!
We can mention also the ANST Tool (Advanced Note Search Tool).
I'm looking for performance improvement on an SAP object (program) and I get 10 notes relevant to my system. What is the order of implementation? The note # or its released on date?