SAP DB2_KPI_GET_LARGEST_TABLES Function Module for Data for Space - KPIs - Largest Tables

Search SAP Function Modules

DB2_KPI_GET_LARGEST_TABLES is a standard db2 kpi get largest tables SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Data for Space - KPIs - Largest Tables processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for db2 kpi get largest tables FM, simply by entering the name DB2_KPI_GET_LARGEST_TABLES into the relevant SAP transaction such as SE37 or SE38.

Function Group: DB2_KPI
Program Name: SAPLDB2_KPI
Main Program: SAPLDB2_KPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DB2_KPI_GET_LARGEST_TABLES pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'DB2_KPI_GET_LARGEST_TABLES'"Data for Space - KPIs - Largest Tables
  EXPORTING
   REMOTE_DBCON =  "Logical name for a database connection
*  TOPN = 15 "Character counter
*  SCHEMA =  "DB2 creator name

 IMPORTING
   LARGE_TABS =  "table type fpr KPIs concerning tables

CHANGING
   SQLERR_REF =  "Exception Class for SQL Error

EXCEPTIONS
   ADBC_SQL_ERROR = 1    INTERNAL_ERROR = 2 

.

IMPORTING Parameters details for DB2_KPI_GET_LARGEST_TABLES

REMOTE_DBCON - Logical name for a database connection

Data type: DBCON-CON_NAME
Optional: No
Call by Reference: Yes

TOPN - Character counter

Data type: DB2NUMC03
Default: 15
Optional: Yes
Call by Reference: Yes

SCHEMA - DB2 creator name

Data type: DB2CREATOR
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for DB2_KPI_GET_LARGEST_TABLES

LARGE_TABS - table type fpr KPIs concerning tables

Data type: DB2KPI_T_TABLES
Optional: No
Call by Reference: Yes

CHANGING Parameters details for DB2_KPI_GET_LARGEST_TABLES

SQLERR_REF - Exception Class for SQL Error

Data type: CX_SQL_EXCEPTION
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ADBC_SQL_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for DB2_KPI_GET_LARGEST_TABLES Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM DB2_KPI_GET_LARGEST_TABLES

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects