SAP GET_INDEX_SIZE_DB2 Function Module for









GET_INDEX_SIZE_DB2 is a standard get index size db2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 get index size db2 FM, simply by entering the name GET_INDEX_SIZE_DB2 into the relevant SAP transaction such as SE37 or SE38.

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



Function GET_INDEX_SIZE_DB2 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 'GET_INDEX_SIZE_DB2'"
IMPORTING
INDEXES_NOT_FOUND = "

TABLES
INDEX_SIZE_LIST = "

EXCEPTIONS
NO_LISTCAT_DATA = 1
.



EXPORTING Parameters details for GET_INDEX_SIZE_DB2

INDEXES_NOT_FOUND -

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

TABLES Parameters details for GET_INDEX_SIZE_DB2

INDEX_SIZE_LIST -

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

EXCEPTIONS details

NO_LISTCAT_DATA -

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

Copy and paste ABAP code example for GET_INDEX_SIZE_DB2 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.

DATA:
lt_index_size_list  TYPE STANDARD TABLE OF TABIX_INDEX_SIZE_LIST, "   
lv_no_listcat_data  TYPE TABIX_INDEX_SIZE_LIST, "   
lv_indexes_not_found  TYPE I. "   

  CALL FUNCTION 'GET_INDEX_SIZE_DB2'  "
    IMPORTING
         INDEXES_NOT_FOUND = lv_indexes_not_found
    TABLES
         INDEX_SIZE_LIST = lt_index_size_list
    EXCEPTIONS
        NO_LISTCAT_DATA = 1
. " GET_INDEX_SIZE_DB2




ABAP code using 7.40 inline data declarations to call FM GET_INDEX_SIZE_DB2

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!