ST05 Tracking SQL

SAP R/3 provides standard ABAP SQL tracing tools. Use t-code:st05 to enter the tracking Settings screen:

In the Trace Modes area, select the range of trace that needs to be on the SAP R/3 Server: SQL Trace:Trace the filtered SQL statements on the AP Server. Enqueue Trace:Track the queues on the Enqueue Server. RFC Trace:Track the RFC behavior on this AP Server. Buffer Trace:Tracks the behavior in buffer on this AP Server. To trace SQL here, just select SQL Trace. Then, in the trace requests area, select the trace on with filter for output filtering: Only the SBA account is tracked for all MB03 SQL operations. You can also fill in the program name or even the process code on the AP Server to track. You can also select included/excluded table names in the table name area.          Click on the hook and then start tracking. You need to stop tracking (trace off) when you need to view the results of the trace and then click the display Trace to show the following: You need to filter the results again (because SAP R/3 has only one or two log files, the system does not automatically decompose the log information of the corresponding program). Trace modes only selects SQL Trace. The SQL Trace Period system is automatically set up without changes. The User name can be set by itself, where a null value indicates any account (because only one account is filtered when the trace is started, so there is no need to filter further).         The Objectname retains the system settings (this eliminates the log information generated by the log itself). Duration: The time spent executing this operation, in microseconds.1 microseconds =1/1000000 seconds. Objectname: An object that indicates the action of the bar, which is generally the table name for SQL Trace. Op.: Indicates the type of action for this bar.         The entry corresponding to open has great reference value for SQL performance. Statement: Indicates that the SQL statement under this action (not exactly the same as SQL in the ABAP statement) clicks on the SQL statement and can display all the information for that statement, including the condition variable (replaced with the @pxxx character). Even press F5 can jump directly to the ABAP statement, convenient for everyone to modify debugging. Precautions :1. After entering the ST05 trace, you can close the interface to continue other operations without affecting the execution of ST05. 2. Because the ST05 does not end with the interface closing, you must manually stop the trace after you have finished using ST05, otherwise it will continue to be tracked until the SAP DB LOG is full. This can cause a system failure. 3. The SQL statement that you see Using tracing is an interpreted version of ABAP SQL, where ABAP SQL may be automatically decomposed or optimized. You can refer to ABAP code for comparison.