The first thing we do when we encounter a bug or issue in an SAP application is to search for a SAP Note. It is sometimes time-consuming and a daunting task to find the exact SAP Note. You might also choose to debug yourself but may not be sure where to start, and where to put debug points.
Broadly classified, there are four key steps to identify an issue or bug in an SAP application:
- Search relevant and most accurate SAP Notes related to the bug.
- Identification of custom codes which are related to the bug.
- Identification of customizing tables, missing entries.
- Identify the possible objects from where debugging can be triggered.
As of Release 740 ANST is available for All support packages
KBA , anst , search tool , BC-UPG-NA , SAP Notes Assistant , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.