SAP EXISTS_COLUMN_SDB Function Module for









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

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



Function EXISTS_COLUMN_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 'EXISTS_COLUMN_SDB'"
  EXPORTING
*  IV_CON_NAME =  "
*  IV_OWNER =  "
   IV_TABLENAME =  "
   IV_COLUMNNAME =  "
*  IV_SYSDBA =  "
*  IV_USER =  "

CHANGING
*  CV_KERNELVERSION =  "

EXCEPTIONS
   COLUMN_DOESNT_EXIST = 1    NO_CONNECTION = 2
.



IMPORTING Parameters details for EXISTS_COLUMN_SDB

IV_CON_NAME -

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

IV_OWNER -

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

IV_TABLENAME -

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

IV_COLUMNNAME -

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

IV_SYSDBA -

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

IV_USER -

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

CHANGING Parameters details for EXISTS_COLUMN_SDB

CV_KERNELVERSION -

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

EXCEPTIONS details

COLUMN_DOESNT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

NO_CONNECTION -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for EXISTS_COLUMN_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_cv_kernelversion  TYPE CHAR15, "   
lv_column_doesnt_exist  TYPE CHAR15, "   
lv_iv_owner  TYPE CHAR32, "   
lv_no_connection  TYPE CHAR32, "   
lv_iv_tablename  TYPE SADATAB, "   
lv_iv_columnname  TYPE SADATAB, "   
lv_iv_sysdba  TYPE FLAG, "   
lv_iv_user  TYPE FLAG. "   

  CALL FUNCTION 'EXISTS_COLUMN_SDB'  "
    EXPORTING
         IV_CON_NAME = lv_iv_con_name
         IV_OWNER = lv_iv_owner
         IV_TABLENAME = lv_iv_tablename
         IV_COLUMNNAME = lv_iv_columnname
         IV_SYSDBA = lv_iv_sysdba
         IV_USER = lv_iv_user
    CHANGING
         CV_KERNELVERSION = lv_cv_kernelversion
    EXCEPTIONS
        COLUMN_DOESNT_EXIST = 1
        NO_CONNECTION = 2
. " EXISTS_COLUMN_SDB




ABAP code using 7.40 inline data declarations to call FM EXISTS_COLUMN_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!