SEL_EXTENDED_VERSION_SDB SAP Function module

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

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

Pattern for FM SEL_EXTENDED_VERSION_SDB - SEL EXTENDED VERSION SDB

CALL FUNCTION 'SEL_EXTENDED_VERSION_SDB' "
* EXPORTING
*   con_name =                  " dbcon_name    Logical Name for a Database Connection
*   use_dbmrfc = 'C'            " sdbusrset-use_dbmrfc  SAP DB: DBMRFC Call Mode
  IMPORTING
    long_version =              " char15        Char 15
    disp_version =              " char10
* CHANGING
*   kernelversion =             " sdb_answ-line  SAP DB: Response line from DBM command
  EXCEPTIONS
    NO_ENTRY_FOUND = 1          "
    TABLE_NOT_FOUND = 2         "
    KERNELVERSION_NOT_FOUND = 3  "
    .  "  SEL_EXTENDED_VERSION_SDB

ABAP code example for Function Module SEL_EXTENDED_VERSION_SDB

The ABAP code below is a full code listing to execute function module SEL_EXTENDED_VERSION_SDB 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_long_version  
 
 TYPE CHAR15
,
ld_disp_version  
 
 TYPE CHAR10
.



DATA(ld_kernelversion) = some text here

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

SELECT single USE_DBMRFC 
  FROM SDBUSRSET 
  INTO @DATA(ld_use_dbmrfc).

.

CALL FUNCTION 'SEL_EXTENDED_VERSION_SDB'
* EXPORTING
*   con_name =                   ld_con_name
*   use_dbmrfc =                 ld_use_dbmrfc
  IMPORTING
    long_version =               ld_long_version
    disp_version =               ld_disp_version
* CHANGING
*   kernelversion =              ld_kernelversion
  EXCEPTIONS
    NO_ENTRY_FOUND =             1
    TABLE_NOT_FOUND =            2
    KERNELVERSION_NOT_FOUND =    3
    .  "  SEL_EXTENDED_VERSION_SDB

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
ELSEIF SY-SUBRC EQ 3. "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_kernelversion
 
 TYPE SDB_ANSW-LINE ,
ld_long_version
 
 TYPE CHAR15 ,
ld_con_name
 
 TYPE DBCON_NAME ,
ld_disp_version
 
 TYPE CHAR10 ,
ld_use_dbmrfc
 
 TYPE SDBUSRSET-USE_DBMRFC .



ld_kernelversion = some text here
ld_con_name = 'Check type of data required'.

SELECT single USE_DBMRFC 
  FROM SDBUSRSET 
  INTO ld_use_dbmrfc.