The usual procedure when you face an error in your SAP ERP system, which seems to be a bug, is to raise an OSS message to SAP Product Support via the SAP Service Marketplace. Then you will have to wait for a SAP support engineer to investigate, what is the root cause. Required for this is the remote access and an example to replicate the same issue directly on your system. If the error is really a known program error, then you get a reply with the information which note will have to be implemented to resolve the case.
Now imagine how much faster and more convenient it would be, if you are able to carry out the note search yourself and find exactly the relevant note, suited for your particular system, which can be downloaded immediately?
This is possible thanks to the newly developed tool, called ANST - which is the abbreviation for Automated Note Search Tool.
The tool is available after you have upgraded your system to one of the following SAP basis support packages (see Knowledge Base Article 1818192😞
Software Component Release Package name
________________________________________________________________________
SAP Basis component
SAP_BASIS 700 SAPKB70028
SAP_BASIS 701 SAPKB70113
SAP_BASIS 702 SAPKB70213
SAP_BASIS 731 SAPKB73106
The transaction to start the tool is named ANST_SEARCH_TOOL.
After the following newer support package with note 1915529 the shorter transaction ANST will become available:
Software Component Release Package name
________________________________________________________________________
SAP Basis component
SAP_BASIS 700 SAPKB70030
SAP_BASIS 701 SAPKB70115
SAP_BASIS 702 SAPKB70215
SAP_BASIS 731 SAPKB73111
SAP_BASIS 740 SAPKB74005
The functionality is the same, the shorter transaction name is more convenient.
Now how does it work in the billing area?
First of all the tool will have to be started by entering the transaction (either ANST_SEARCH_TOOL or ANST, depending on your Support package):
Thereafter you will see the main screen of the tool.The investigation is based on a trace of the action performed. In the example, supposedly a problem in transaction VF01 occurs.
In field transaction VF01 is entered and a name is given in the description field:
A description is necessary, here you can choose any meaningful text yourself.
Then pressing button 
"Execute" or F8 the transaction VF01 starts with the tool tracing in the background:
Here in VF01 you perform the steps until the error occurs and thereafter return with the back button 
to the ANST tool, where you get the following overview screen:
Listed are all components that had been involved. Depending on in which area the error occurred, you can navigate to there:
Suppose it has something to do with pricing, then you mark SD-BF-PR and press the button "Note search" 
and you will get a list with all relevant notes, that are not yet implemented:
From this list you can even download the relevant note directly and start with the implementation.
Two other functions are useful. Apart from searching notes, you can get as well an overview of which user-exits and customer modifications had been executed, by pressing the button "Customer Code":
Here in the example, two user-exits and one BAdI had been involved.
The third important help is a list of the relevant customizing tables, which you can access by pressing the button "Customizing tables":
For pricing the tables that contain condition exclusion logic are listed:
With these three functions
you will get a detailed overview of the possible error causes, and it will be possible that you find and correct the root cause yourself.
May the power of ANST help you!
Related reading:
http://scn.sap.com/community/abap/blog/2010/12/16/automated-note-search-and-customer-code-detection
SAP ANST: experience the magic... - NB Conseil.com
- SAP Managed Tags:
28 Comments
