SAP Knowledge Base Article
l All kind of errors for which an SAP Note with ABAP correction instructions that solves the issue exist.
l All kind of errors caused by customer code
l All kind of errors caused by incorrect customizing
This application searches SAP correction notes for a specific problem based on the issue replication in your system. Additionally, it will provide a
list with the customer code involved together with other features useful to solve the problem.
How does it work ?
When a problem occurs and you suspect it's an error for which a SAP Note correction could exist, go to transaction ANST_SEARCH_TOOL and
reproduce the problem by specifying the transaction or program involved:
E.g. for transaction OASV:
Then start the tool: or F8:
Then replicate the issue:
After pressing "Enter" you get the following error at the bottom of the screen:
Now go back (F3)
The control is transferred again to the Note Search Tool. A list of the application components involved in the execution will be displayed:
1818192 - FAQ: Automated Note Search Tool
Version 6 Validity: 15.03.2013 - active Language English
Select the component or components you think the problem belongs to and click on icon: The tool will start searching for correction
After some time you get a list of notes that are not implemented in your system and that could be related to your issue:
You can click on the note link to read the note:
In our example, SAP note 1279254 solves the issue and after implementing it, the error will disappear and the note will not be displayed anymore.
Integration with the "Note Assistant" (SNOTE)
Once the error has been reproduced and the result of the search shows a relevant note that most likely will solve the program, you can decide the
implementation directly from the notes list by double clicking on the "Download Note" icon .
If you confirm the download, the tool will automatically call the note assistant (transaction SNOTE) and download the note leaving it ready for the
After reproducing the issue, if the first note search displays too many notes, you can be more specific selecting the components, e.g. just FI-FI-AA
but not FI:
You can also display the objects that were found in the trace for each subcomponent and search notes for a single object:
Also, you can navigate / edit the object by double clicking on it:e.g. doble click on MA03BO00:
And for example set a break-point if you wish or just analyze the code.
Customer Code identification
It may happen that the issue is not related to the standard code but to customer code such as Badi implementations, user-exits, field-exits or
repaired standard code. Click on icon to identify it:
Example for transaction PA30:
Issue: There is a mistake in the Spanish Income TAX percentage calculation for an employee. You were unsuccessful in searching Notes, but there
is still a chance that the issue is caused by a mistake on customer's side.
After running transaction PA30 for an employee and displaying infotype 0062 (TAX Spain), you get the list of objects involved in the trace,
classified by component (Yellow folders).
By the way, you will notice that sometimes you get a folder called "TMP": Objects that for any reason have no application component will be placed
there (Badis, Customer code..).
Click on the icon "Customer Code"
Double click on the row corresponding to the object you want to display / edit:
E.g. click on the 1st row that corresponds to a user exit:
Double click now on ZXPADU01:
The tool is also capable to reproduce web application issues, for this, the process is very similar to the Transaction and program options:
Imagine we want to reproduce a CRM WebUI issue:
We will get a new popup:
Just press Start Recording and the browser will open immediately to reproduce the web issue:
When the issue is reproduced, we should STOP the recording using the "Stop Recording" button of the popup:
The TBOM will be recording....
And you will get the objects like in a transaction or program:
Customizing tables list
When there aren't any notes available to solve an issue it can be that the customizing is involved. What seems to be a bug turns out to be a
customizing issue that is solved by changing customer settings.
For this purpose, another option is available by clicking on the icon "Customizing tables" :
You will get a list of the customizing tables involved in the process grouped by application component in a tree list.
By clicking on the table name, you will be directed to transaction SM30 with the name of the table view filled or a list of views in case there are
more than one.
Open trace option (reuse test cases)
Once an issue is reproduced with the tool, you can reuse the trace to search notes again. This means that for example, the application user can
reproduce the issue and an expert technical consultant can use the trace to search notes. Or perhaps try to search notes a week later when some
more notes may be available.
During the execution you can indicate a description for the trace that will be created.
Later on, you can use this description to identify and retrieve this trace by clicking the "Open trace" icon.
With the F4 option you can search and select your trace.
Delete trace option:
You may also want to remove some traces from the system. For this, you can use the button "Delete Trace":
You will see the existing traces and you can select the ones you want to remove and delete them from the system.
There exists also the possibility to customize some of the search parameters in order to optimize the performance and the results.
At this respect, you can activate/deactivate the objects that the internal search engine should take into account by clicking on the icon "Objects
customizing" . A list of dictionary objects will be presented that can be selected (classes, methods, function modules, etc…).
Also you can indicate the initial date from which the tool will search available notes. Notes released with a date older than the one specified in this
field will not be considered.
The ALV display option in case you wish to have the output lists in ALV format which is the default option.
This tool is based on the trace of the process replicated. After reproducing the issue, a list of application components is shown and later on, a note
search looking for notes that have these objects in their correction instructions is done.
Therefore, try to replicate the issue using the minimum steps possible. Otherwise, the performance might be endangered as the trace could get
unnecessary objects and as a result you could get notes that are irrelevant for the issue.
If there is any "Released for customer" SAP correction note that solves your issue, the note will be displayed (Otherwise, please report the case to
SAP). There is an exception with "Pilot release" notes that of course will not be shown.
Notice that the objects collected during the trace are classified by the component they belong to (yellow folders). Therefore, it might happen that
searches for notes in component X may get notes belonging to component Y, because objects that belong to component X where modified in a
note that belongs to component Y.
Refer to SAP note 1778716
No notes found?.
This function requires the correct setting up of the connection SAPSNOTE , which is also used for the Correction Workbench. If none of the
connections are available, no notes are found.
To set up the connection, see SAP Notes 33135 and 22235.
Too many notes found?.
It's necessary that the notes have the support package section filled, otherwise the tool will show notes that are already implemented. If any issues
happen with a particular note, it should be notified to be note owner by opening a message to the note component.
Can not start the tool: You get the following message:
Fatal Error. Customizing table is not filled!
Message no. ANST001
Table ANST_SETTINGS is empty, because it was not imported to the working client. You can find the standard settings at client 000. You can also
modify the settings to fit your requirements:
These are the settings for table ANST_SETTINGS:
ID (+): 1
Date: Notes with date older than this date will not be displayed.
ALV on res: Default is Yes.
Max size: 800
RFC destination: SAPSNOTE
Badi, Rep. object, Field exit, user exit, Transaction variant, BTE: Select the kind of customer code you want to be detected.
Due to a mistake, the content of table ANST_SETTINGS was not delivered in the support packages.
Also table ANST_CUST_OBJ content was not delivered in the supoprt packages. In this case the content is:
However, due to issue in the view, table ANST_CUST_OBJ cannot be update using transaction SM30. To update the content of table
ANST_CUST_OBJ create a local program ZANST_CUST_OBJ with the code in the attached file ZANST_CUST_OBJ.txt. Run the program just
once and then use transaction SM30 to include the entries in a transport request.
This document is not restricted to a product or product version
This document refers to:
CSS SAP Notes
Released On 15.03.2013 14:04:20
Release Status Released to Customer
Component BC-UPG-NA SAP Notes Assistant
33135 Guidelines for OSS1
22235 OSS1: What to do, if R/3 does not run?
File Name File Size (KB) Mime Type
ZANST_CUST_OBJ.txt 4862 text/plain