SAP TABLE_COLLECTOR_SDB Function Module for









TABLE_COLLECTOR_SDB is a standard table collector sdb 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 table collector sdb FM, simply by entering the name TABLE_COLLECTOR_SDB into the relevant SAP transaction such as SE37 or SE38.

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



Function TABLE_COLLECTOR_SDB 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 'TABLE_COLLECTOR_SDB'"
  EXPORTING
*  IV_CON_NAME =  "
*  IV_LIST_OUTPUT =  "
*  IV_TNAME =  "
*  IV_CALC =  "
*  IV_ECALC =  "
*  IV_EST =  "
*  IV_SEL_TAB =  "
*  IV_SEL_IND =  "
*  IV_SEL_CLASSCONT =  "
*  IV_SEL_SAVE_SDBCCMS =  "

 IMPORTING
   EV_NUM_COLL_TABLES =  "
   EV_NUM_COLL_CLASSCONTS =  "
   EV_NUM_COLL_INDEXES =  "
   EV_SCHEMANAME =  "
   EV_FROM_FILES =  "

EXCEPTIONS
   NO_CONNECTION = 1    NO_DBCON_ENTRY = 2    WRONG_DB_SYSTEM = 3
.



IMPORTING Parameters details for TABLE_COLLECTOR_SDB

IV_CON_NAME -

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

IV_LIST_OUTPUT -

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

IV_TNAME -

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

IV_CALC -

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

IV_ECALC -

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

IV_EST -

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

IV_SEL_TAB -

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

IV_SEL_IND -

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

IV_SEL_CLASSCONT -

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

IV_SEL_SAVE_SDBCCMS -

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

EXPORTING Parameters details for TABLE_COLLECTOR_SDB

EV_NUM_COLL_TABLES -

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

EV_NUM_COLL_CLASSCONTS -

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

EV_NUM_COLL_INDEXES -

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

EV_SCHEMANAME -

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

EV_FROM_FILES -

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

EXCEPTIONS details

NO_CONNECTION -

Data type:
Optional: No
Call by Reference: Yes

NO_DBCON_ENTRY -

Data type:
Optional: No
Call by Reference: Yes

WRONG_DB_SYSTEM -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TABLE_COLLECTOR_SDB 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:
lv_iv_con_name  TYPE DBCON_NAME, "   
lv_no_connection  TYPE DBCON_NAME, "   
lv_ev_num_coll_tables  TYPE I, "   
lv_iv_list_output  TYPE FLAG, "   
lv_iv_tname  TYPE OBJECTNAME, "   
lv_no_dbcon_entry  TYPE OBJECTNAME, "   
lv_ev_num_coll_classconts  TYPE I, "   
lv_iv_calc  TYPE FLAG, "   
lv_wrong_db_system  TYPE FLAG, "   
lv_ev_num_coll_indexes  TYPE I, "   
lv_iv_ecalc  TYPE FLAG, "   
lv_ev_schemaname  TYPE CHAR32, "   
lv_iv_est  TYPE FLAG, "   
lv_ev_from_files  TYPE FLAG, "   
lv_iv_sel_tab  TYPE FLAG, "   
lv_iv_sel_ind  TYPE FLAG, "   
lv_iv_sel_classcont  TYPE FLAG, "   
lv_iv_sel_save_sdbccms  TYPE FLAG. "   

  CALL FUNCTION 'TABLE_COLLECTOR_SDB'  "
    EXPORTING
         IV_CON_NAME = lv_iv_con_name
         IV_LIST_OUTPUT = lv_iv_list_output
         IV_TNAME = lv_iv_tname
         IV_CALC = lv_iv_calc
         IV_ECALC = lv_iv_ecalc
         IV_EST = lv_iv_est
         IV_SEL_TAB = lv_iv_sel_tab
         IV_SEL_IND = lv_iv_sel_ind
         IV_SEL_CLASSCONT = lv_iv_sel_classcont
         IV_SEL_SAVE_SDBCCMS = lv_iv_sel_save_sdbccms
    IMPORTING
         EV_NUM_COLL_TABLES = lv_ev_num_coll_tables
         EV_NUM_COLL_CLASSCONTS = lv_ev_num_coll_classconts
         EV_NUM_COLL_INDEXES = lv_ev_num_coll_indexes
         EV_SCHEMANAME = lv_ev_schemaname
         EV_FROM_FILES = lv_ev_from_files
    EXCEPTIONS
        NO_CONNECTION = 1
        NO_DBCON_ENTRY = 2
        WRONG_DB_SYSTEM = 3
. " TABLE_COLLECTOR_SDB




ABAP code using 7.40 inline data declarations to call FM TABLE_COLLECTOR_SDB

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!