DB2_KPI_GET_TS_LIMIT SAP Function module - Data for Space - KPIs - Tablespace Limits

DB2_KPI_GET_TS_LIMIT 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 DB2_KPI_GET_TS_LIMIT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM DB2_KPI_GET_TS_LIMIT - DB2 KPI GET TS LIMIT

CALL FUNCTION 'DB2_KPI_GET_TS_LIMIT' "Data for Space - KPIs - Tablespace Limits
  EXPORTING
    remote_dbcon =              " dbcon-con_name  Logical name for a database connection
*   topn = 15                   " db2numc03     Character counter
*   schema =                    " db2creator    DB2 creator name
  IMPORTING
    objects =                   " db2kpi_t_tslimits  table type for KPIs (ts near DB2 limits)
  CHANGING
    sqlerr_ref =                " cx_sql_exception  Exception Class for SQL Error
  EXCEPTIONS
    ADBC_SQL_ERROR = 1          "
    INTERNAL_ERROR = 2          "
    .  "  DB2_KPI_GET_TS_LIMIT

ABAP code example for Function Module DB2_KPI_GET_TS_LIMIT

The ABAP code below is a full code listing to execute function module DB2_KPI_GET_TS_LIMIT 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_objects  
 
 TYPE DB2KPI_T_TSLIMITS
.


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

SELECT single CON_NAME 
  FROM DBCON 
  INTO @DATA(ld_remote_dbcon).


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

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

CALL FUNCTION 'DB2_KPI_GET_TS_LIMIT'
  EXPORTING
    remote_dbcon =               ld_remote_dbcon
*   topn =                       ld_topn
*   schema =                     ld_schema
  IMPORTING
    objects =                    ld_objects
  CHANGING
    sqlerr_ref =                 ld_sqlerr_ref
  EXCEPTIONS
    ADBC_SQL_ERROR =             1
    INTERNAL_ERROR =             2
    .  "  DB2_KPI_GET_TS_LIMIT

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_sqlerr_ref
 
 TYPE CX_SQL_EXCEPTION ,
ld_objects
 
 TYPE DB2KPI_T_TSLIMITS ,
ld_remote_dbcon
 
 TYPE DBCON-CON_NAME ,
ld_topn
 
 TYPE DB2NUMC03 ,
ld_schema
 
 TYPE DB2CREATOR .


ld_sqlerr_ref = 'Check type of data required'.

SELECT single CON_NAME 
  FROM DBCON 
  INTO ld_remote_dbcon.

ld_topn = 'Check type of data required'.
ld_schema = 'Check type of data required'.