The SQL Trace is especially useful for Development and Performance analysis.

Steps to follow for applying SQL Trace:

  - Launch the SQL Trace application.
  - Activate the SQL Trace.
 - Run the application that you want to trace.
 - Deactivate the SQL Trace.
 - Set filters optionally.
 - Evaluate the trace.

Lets follow the steps and trace the SQL:

(i) Launch the SQL Trace application – with T-Code ST05.

SQL Trace - Initial Screen

Following function can be performed on the Initial Screen:

Select trace Mode:

 · Select the trace mode SQL Trace, Enqueue Trace, RFC Trace, or Table Buffer Trace. You can select multiple trace modes simultaneously.

 Select trace function:

 · Start the trace recording.

 · Stop the trace recording.

 · Branch to trace list, detailed list, or time-sorted list.

 · Branch to Explain SQL to analyze an SQL statement without an explicit trace file.

(ii) Activate the SQL Trace:

If you want to switch on the trace under your user name, choose Trace on.

If you want to pass on values for one or several filter criteria, choose Trace with Filter.( Typical filter criteria are: the name of the user, transaction name, process name, and program name).

  (iii) Run the application that you want to trace. Execute all the screens/steps for which you want to trace.

(iv) Deactivate the SQL Trace – Get back to ST05 and click deactivate button to deactivate the SQL trace. It will stop further / unnecessary SQL recording.

(v) Evaluate the trace by clicking Display Trace. The basic list is displayed at the start.

Basic Trace List

The displayed result can be drilled down to get more detailed result for better analysis.

Apart from this, summary report can also be generated shown as below.

Summary Trace List

(vi) Evolving Individual SQL statements:

Click Enter SQL statement to enter the SQL statement you want to evaluate. Enter the SQL and click Explain.

Enter SQL

The details of SQL is then displayed.

SQL statement Evaluation

Summarized Table Information can also be display by clicking the Table Name.

Display Table Details

You might also be interested in these posts:

1. Analyzing the SAP Dumps
2. Debugging Smartforms and SAPScript in ABAP
3. Finding Obsolete BAPIs in SAP

If a runtime error occurs, the ABAP runtime environment terminates the execution of the program, generates a short dump and branches to a special screen for analyzing the short dump. You can also find short dumps in transaction ST22 or by choosing the menu path Tools → ABAP Workbench → Test → Dump Analysis.

 A short dump is divided into different sections that document the error. The overview shows what other information is output in the short dump, such as contents of data objects, active calls, control structures, and so on. You can branch to the ABAP Debugger at the termination point from the short dump view.

The following different error situations exist:

. Internal Error -The kernel identifies an error state. In this case, notify SAP.

. Installation and Environment/Resource Error - In this case, an error occurred that was caused by incorrect system installation or missing resources (such as the database being shutdown).

. Error in Application Program

Typical causes of errors are:

. Content of a numerical field not in the correct format

. Arithmetic overrun

. An external procedure is not available

. Type conflict when transferring parameters to an external procedure

By default, short dumps are stored in the system for 14 days. The transaction for managing short dumps is ST22. You can delete short dumps in accordance with a time specification using the Reorganize function, which you can call by choosing Goto → Reorganize. You can save a short dump without a time limit using the Keep function, which you can choose under Short Dump → Keep/Release.

If problems that you cannot solve yourself occur with ABAP programs, you can send an extract of the short dump to SAP. A short dump is the basis on which the SAP Hotline and remote consulting solve problems.

. If a runtime error occurs, a short dump is generated. You can use transaction ST22 to analyze this short dump.

. Dump data is stored in the database.

. Dump data can be reorganized.

. Individual short dumps can be flagged for retention.

SAP System Trace

You can use the system trace to record internal system activities. The system trace is primarily used if an authorization trace is to be created. SAP recommends that you use the system log or the developer trace for system monitoring and problem analysis.

You can call the SAP System Trace using transaction ST01 or by choosing the menu path Tools → Administration → Monitor → Traces → System Trace. You can also use transaction ST01 to display the inactive trace file.

You can use the SAP system trace to monitor the following components:

. Authorization checks

. Kernel functions

. Kernel modules

. DB accesses (SQL Trace)

. Table buffers

. Lock operations (client-side)

You select the components to be logged on the initial screen. If the trace is activated for the authorization check, all authorization checks performed by the system are recorded. During the evaluation, you can identify which authorizations the system checked at which times. The following detail information is also provided: Date, time, work process number, user, authorization object, program, line, number of authorization values, authorization values.

You can use the SQL Trace to follow how the Open SQL commands in reports and transactions are converted to standard SQL commands and the parameters with which the SQL commands are transferred to the database system in use. The results of the SQL command are also logged, such as the return code and the number of records found, inserted, or deleted by the database. Logging the execution time and the callpoint in the application program allows you to perform more advanced evaluations.

With the enqueue trace, you can follow which lock instructions the SAP system performs on which lock objects, and which parameters the system uses for these locks.

The program that triggered the lock, the owner of the lock, and the time that the enqueue server required to release the lock again are all also logged in the trace file.

You can use the RFC trace to follow which remote calls the SAP system executes, and the instance on which these calls are executed. You can see from the trace which function modules were called remotely by the program that is to be analyzed, and whether the RFC was successfully executed. The total time required for the execution of the remote call and the number of bytes sent and received during the RFC are also logged in the trace file.

You might also be interested in these posts:

1. Catch the Dump in ABAP – I
2. Tracing your SQL in SAP
3. Assign/Create Authorization Group for a Table in SAP

 SAP also have Object Oriented Class based exceptions which are easy to handle and less cumbersome.

Class-based exceptions are handled in the following control structure:

TRY.

… ” TRY block (application coding)

CATCH cx_… cx_… …

… ” CATCH block (exception handler)

CATCH cx_… cx_… …

… ” CATCH block (exception handler)

…

CLEANUP.

… ” CLEANUP block (cleanup context)

ENDTRY.

The TRY statement opens a control structure to be ended with ENDTRY, in which three statement blocks can be listed in a specified order (this is not obligatory).

 1. A TRY block, in which exceptions can occur.

This exception block consists of all the statements between the TRY and the CATCH statement.

 2. One or more CATCH blocks for catching exceptions.

These exception blocks are initiated with CATCH and ended with a further CATCH, CLEANUP, or ENDTRY.

 3. A CLEANUP block for cleanup work after the exceptions have been caught.

This statement block is initiated by CLEANUP and ended with ENDTRY. A TRY-ENDTRY structure must not contain more than one CLEANUP block in precisely this position.

 We can also raise explicit exception by using statement RAISE EXCEPTION <CUSTOM_EXCEPTION>.

Sample Report

 Report DEMO_HANDLE_EXCEPTIONS.

parameters NUMBER type I.

data RESULT type P decimals 2.
data OREF type ref to CX_ROOT.
data TEXT type STRING.

start-of-selection.
write: / ‘Testing division and Sqare root with’, NUMBER.

uline.

try.

if ABS( NUMBER ) > 100.
raise exception type CX_DEMO_ABS_TOO_LARGE.

endif.

try.

RESULT = 1 / NUMBER.
write: / ‘Result of division:’, RESULT.
RESULT = SQRT( NUMBER ).
write: / ‘Result of square root:’, RESULT.

catch CX_SY_ZERODIVIDE into OREF.
TEXT = OREF->GET_TEXT( ).
cleanup.
clear RESULT.

endtry.

catch CX_SY_ARITHMETIC_ERROR into OREF.
TEXT = OREF->GET_TEXT( ).

catch CX_ROOT into OREF.
TEXT = OREF->GET_TEXT( ).

endtry.

if not TEXT is initial.
write / TEXT.
endif.

write: / ‘Final result:’, RESULT.

The output of the above program when zero (0) is entered:

Catching Zero (0) Exception

You might also be interested in these posts:

1. Catch the Dump in ABAP – I
2. ABAP Program for Table Maintenance in SAP
3. ABAP Program to display SAP Data in 3-Dimension

Explicit Error Handling

We will convert the dump into an error message (like in above snap) or some text statement. For this we need to call this statement
     RECEIVE RESULTS FROM FUNCTION ‘function module’ 

Sample Program

 
REPORT zcustom_errmsg.
PARAMETERS: p_file LIKE rlgrap-filename .
DATA: v_file TYPE string.
DATA: BEGIN OF itab OCCURS 0,
      name(23) TYPE  c,
      END OF itab.

DATA: errormessage TYPE char50.
v_file = p_file.
CALL FUNCTION ‘GUI_UPLOAD’
  EXPORTING
    filename            = v_file
    filetype            = ‘ASC’
    has_field_separator = ‘ ‘
  TABLES
    data_tab            = itab.

RECEIVE RESULTS FROM FUNCTION ‘GUI_UPLOAD’
 EXCEPTIONS
   file_open_error               = 1
   file_read_error               = 2
   no_batch                      = 3
   gui_refuse_filetransfer       = 4
   invalid_type                  = 5
   no_authority                  = 6
   unknown_error                 = 7
   bad_data_format               = 8
   header_not_allowed            = 9
   separator_not_allowed         = 10
   header_too_long               = 11
   unknown_dp_error              = 12
   access_denied                 = 13
   dp_out_of_memory              = 14
   disk_full                     = 15
   dp_timeout                    = 16
   OTHERS                        = 17 .

CASE sy-subrc.
  WHEN 0.
    errormessage     = ‘Data Loaded’.
  WHEN 1.
    errormessage     = ‘FILE_OPEN_ERROR’.
  WHEN 2.
    errormessage     = ‘FILE_READ_ERROR’.
  WHEN 3.
    errormessage     = ‘NO_BATCH’.
  WHEN 4.
    errormessage     = ‘GUI_REFUSE_FILETRANSFER’.
  WHEN 5.
    errormessage     = ‘INVALID_TYPE’.
  WHEN 6.
    errormessage     = ‘NO_AUTHORITY’.
  WHEN 7.
    errormessage     = ‘UNKNOWN_ERROR’.
  WHEN 8.
    errormessage     = ‘BAD_DATA_FORMAT’.
  WHEN 9.
    errormessage     = ‘HEADER_NOT_ALLOWED’.
  WHEN 10.
    errormessage     = ‘SEPARATOR_NOT_ALLOWED’.
  WHEN 11.
    errormessage     = ‘HEADER_TOO_LONG’.
  WHEN 12.
    errormessage     = ‘UNKNOWN_DP_ERROR’.
  WHEN 13.
    errormessage     = ‘ACCESS_DENIED’.
  WHEN 14.
    errormessage     = ‘DP_OUT_OF_MEMORY’.
  WHEN 15.
    errormessage     = ‘DISK_FULL’.
  WHEN 16.
    errormessage     = ‘DP_TIMEOUT’.
  WHEN 17.
    errormessage     = ‘OTHERS’.
ENDCASE.

MESSAGE e001(00) WITH errormessage .

The above program will give an error message instead of a dump, dump in terms of minor errors is quite worthless to search for.

You might also be interested in these posts:

1. Catch the Dump in ABAP – II
2. Analyzing the SAP Dumps
3. ABAP Program to Search For SMARTFORMS in your Language