Kontakt

Ansicht
Dokumentation

ANST_SEARCH_TOOL - Automated Note Search & Customer Code Detection Tool

ANST_SEARCH_TOOL - Automated Note Search & Customer Code Detection Tool

General Data in Customer Master   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

&PURPOSE&

This tool looks for SAP Correction notes in order to solve a specific issue. When a problem with a transaction arises, and there is already a SAP correction note available to solve it, the relevant note will be found by the Note Search Tool by starting the tool and reproducing the issue step by step. Once the issue is reproduced, go back (F3 key) and a list of workbench objects classified by application component will be displayed (e.g. Payroll, Finance, Logistics, Basis). Then, select the appropriate component(s) or application area(s) and press the button "Search notes". A list of available notes for the process will be displayed. These notes will be selected among those that are relevant for the current release and support package level of each software component installed. This means that all the notes in the result list will solve "a" problem but only one of them will solve "the" problem. As to which is the relevant component, it depends on the kind of issue, e.g. report TAX report "X"· shows an incorrect income TAX percentage for an employee (Select payroll component) / The same report does not show correctly Japanese characters (Select Basis). Sometimes it's not clear enough which component is behind a bug. In that case you may select several components. Actually, it could happen that you search notes for a specific component and you get notes for a different component. This happens because the SAP Note component is not always the same as the component of the objects that are corrected in the Note. E.g. an object "X" belongs to component PY-ES but there is a note belonging to component PA-PA-ES that contains correction instructions for this note. However, the rule should be that the SAP Note component is the same as the component of the objects modified by the Note. It may happen too that a Note that is not relevant anymore because it was already implemented is shown in the Note list because the Support Package section of the Note is not correctly maintained or empty. This infrequent case should be reported to SAP (However the support package section of a SAP Note could be empty because is a new Note that is not yet included in any Support Package).

Only Notes that are in status "Release for Customer" will be searched, therefore "Pilot release" Notes which could solve the issue will not be displayed.

When reproducing the issue, it's very important to minimize the number of steps, avoiding unnecessary actions which would yield irrelevant Notes.

It might happen that the issue is not caused by a SAP error but by customer's own code. As an additional feature, the customer code involved in the process is shown. Customer code includes standard modification, Badi implementations, User-exits and field exits.

ANST can be used too as a debugging tool as after reproducing a specific issue you get the objects (Methods, Includes, Function Modules and so on), that were executed, classified by application areas. The navigation capabilities enable you to double click on an object and displaying / editing it and making it possible to set a break-point without having to open a new session or analyze the ABAP code.

Following are the enhancements delivered with Note 2605555:

  • Breakpoints:You can set external breakpoints to debug your application.
  • Scan Source:You can scan for a particular term in the source code of all the objects in the trace displayed in the ALV tree.
  • All tables:View all the tables involved during the issue replication.
  • Save Trace and Download Trace with Call Stack: During issue replication, the generated trace can be saved or downloaded for easy reference with call stack.
  • Filters:You can filter the trace generated based on the Application Component(s), software components, or packages. For example, check the "Customer code only" check-box to filter the trace based on customer code.





TXBHW - Original Tax Base Amount in Local Currency   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4272 Date: 20240531 Time: 020233     sap01-206 ( 109 ms )