I see many questions posted in SCN could be resolved by a single note or KBA. Considering the amount of notes/KBAs, I know that it could be quite difficult to find out the right note/KBA to resolve a specific problem. So I’d like to share some tricks and experiences to search for the suitable notes/KBAs.
Where is the Note/KBA search tool?
- Go to the link :Home | SAP Support Portal
- Click the link “Note and KBA search tool” on the right
- Click the button “Launch the SAP Note and KBA search”
- The search tool will be opened.
What search options can be used?
- There are 3 checkboxes for option “Language”: German, English and Japanese
If the deveopers are located in Germany, they tend to write original notes in German and then translate the notes to English or Japanese. Since translation may need time, if you search with the option English or Japanese, you may not get a full list of the newest notes/KBAs.
So my suggestion is :
If you can read German and you know the developers for the application area is located in Germany, use the language “German” to search.
If you cannot read German, but you suspect this is a new bug/error which should have been covered by a note, you can still search with the language “German”, but search with key words like program name, field name, error message number etc.
- Choose your search terms carefully.
Use error message number instead of short text.
If an error occurs, you can find the error message number in the long text by double clicking the error. For example, search by “CP466” or “CP 466”.
Use field technical name instead of field description
For example, use ELIKZ instead of “delivery completed”.
Use full name instead of abbreviation.
eg. purchase requisition instead of PR, planned independent requisition instead of PIR
Use function modules/programs if you know which is called and is behaving strangely
eg. error occurs when converting planned orders to production orders, the function module CO_SD_PLANNED_ORDER_CONVERT is called.
Use different t-codes
eg. although error occurs in CO02, you can also try to use t-code CO01 during search.
For short dumps, use the key words suggested in the dump.
You can usually see the following statement in the dump:
If the error occures in a non-modified SAP program, you may be able to find an interim solution in an SAP Note. If you have access to SAP Notes, carry out a search with the followingkeywords:
- Choose a right application area to restrict the selected note/KBA numbers, or do not enter the application area to expand the selection to all components (this could be useful if you don’t know the right component or the issue crosses many applications).
You can simply use a wildcard * after a main application (eg. PP* or PP-SFC*) if you are not sure about the sub-components.
- Choose the validity of your system release in the field “Restriction” by selecting “Restrict by Software Components”.
If the problem only appears after a system upgrade, it’s better to specify your system release to filter out old notes.
For example, you can find your own system release by t-code SPAM. Click the button “Package level”. Usually for application areas like PP, QM, you should look for the component SAP_APPL.
During search, input the software component, release from, release to. ( “From support package” is optional.)
Here is the result from above search criterias:
- Choose a note/KBA category.
If you are just looking for some explanation of system logic, you can choose category consulting and FAQ. They usually don’t include any coding.
If you suspect a system error(for example issue only appears after system upgrade), you can choose category “program error ” “modification”. They usually contain correction codes.
Common questions regarding notes/KBAs:
The note contains code corrections. How can I see the codes?
Take the note 1327813 for example.
In the section ” Correction Instructions”, you can find a correction number corresponding to the valid system release. Click the number. A new window will be opened. You can then click the object name to see the codes.
How do I know if the note is valid for my system?
Take the note 1327813 for example.
See the section “Validity”. It shows the main SAP_APPL release for which the note is valid.
See the section “Support Packages & Patches”. It lists the exact SP and patch that imports the note. If your system release is lower than the listed SP and patch level, the note should be able to be implemented by SNOTE.
The note includes Z reports. How to implement it?
Many notes contain Z reports to correct inconsistencies. For example the notes listed in blog Often used PP reports in SAP Notes
These Z reports usually cannot be imported by SNOTE. You have to create them manually in t-code SE38 and copy the source code in the notes.
Where are the related notes?
In the section “References”. You can see which notes are referenced to and referenced by. Sometimes they can be quite useful to see other related notes.
Also refer to the following KBAs about searching notes/KBAs:
2081285 – How to enter good search terms to an SAP search?
1540080 – How to search for KBs, KBAs, SAP Notes, product documentation, and SCN
Amazing tool for automatic note search:
I have to mention the amazing tool which enables automatic note search. It enables the user to find out which note correction is missing on your system automatically. See the following note:
1818192 – FAQ: Automated Note Search Tool
Be aware that this tool can only find notes with correction codes. So if you are looking for consulting and explanatory notes/KBAs, you still have to use the tips above to search by yourself.