C_GET_DB_ORA_SQL_ADVISOR SAP Function module - Database Metrics: System Metrics

C_GET_DB_ORA_SQL_ADVISOR is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name C_GET_DB_ORA_SQL_ADVISOR into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: S_ORA_COCKPIT_1
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM C_GET_DB_ORA_SQL_ADVISOR - C GET DB ORA SQL ADVISOR

CALL FUNCTION 'C_GET_DB_ORA_SQL_ADVISOR' "Database Metrics: System Metrics
  EXPORTING
    i_remote_system =           " dbcon_name    Logical name for a database connection
    i_inst_id =                 " ora_inst_id   Oracle monitor: Instance ID
    i_sqlid =                   " ora_sql_id    Oracle monitoring: SQL_ID
  IMPORTING
    es_report =                 " string
  EXCEPTIONS
    SQL_EXCEPTION = 1           "               SQL Exception
    WRONG_SQL_ID_FORMAT = 2     "               Wrong format of SQL ID
    .  "  C_GET_DB_ORA_SQL_ADVISOR

ABAP code example for Function Module C_GET_DB_ORA_SQL_ADVISOR

The ABAP code below is a full code listing to execute function module C_GET_DB_ORA_SQL_ADVISOR including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).

DATA:
ld_es_report  
 
 TYPE STRING
.


DATA(ld_i_remote_system) = 'Check type of data required'.

DATA(ld_i_inst_id) = 'Check type of data required'.

DATA(ld_i_sqlid) = 'Check type of data required'.
.

CALL FUNCTION 'C_GET_DB_ORA_SQL_ADVISOR'
  EXPORTING
    i_remote_system =            ld_i_remote_system
    i_inst_id =                  ld_i_inst_id
    i_sqlid =                    ld_i_sqlid
  IMPORTING
    es_report =                  ld_es_report
  EXCEPTIONS
    SQL_EXCEPTION =              1
    WRONG_SQL_ID_FORMAT =        2
    .  "  C_GET_DB_ORA_SQL_ADVISOR

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_es_report
 
 TYPE STRING ,
ld_i_remote_system
 
 TYPE DBCON_NAME ,
ld_i_inst_id
 
 TYPE ORA_INST_ID ,
ld_i_sqlid
 
 TYPE ORA_SQL_ID .


ld_i_remote_system = 'Check type of data required'.
ld_i_inst_id = 'Check type of data required'.
ld_i_sqlid = 'Check type of data required'.