SAP SVRS_GET_VERSION_SQLD_40 Function Module for









SVRS_GET_VERSION_SQLD_40 is a standard svrs get version sqld 40 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 svrs get version sqld 40 FM, simply by entering the name SVRS_GET_VERSION_SQLD_40 into the relevant SAP transaction such as SE37 or SE38.

Function Group: SVRW
Program Name: SAPLSVRW
Main Program: SAPLSVRW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SVRS_GET_VERSION_SQLD_40 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 'SVRS_GET_VERSION_SQLD_40'"
  EXPORTING
*  DESTINATION =  "
   OBJECT_NAME =  "
   VERSNO =  "
*  IV_NO_RELEASE_TRANSFORMATION =  "

 IMPORTING
   INFO_LINE =  "

TABLES
*  VSMODISRC =  "
*  DD06TV_TAB =  "
*  DD06V_TAB =  "
*  DD16V_TAB =  "
*  VSMODILOG =  "

EXCEPTIONS
   NO_VERSION = 1    SYSTEM_FAILURE = 2    COMMUNICATION_FAILURE = 3
.



IMPORTING Parameters details for SVRS_GET_VERSION_SQLD_40

DESTINATION -

Data type: RFCDES-RFCDEST
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT_NAME -

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

VERSNO -

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

IV_NO_RELEASE_TRANSFORMATION -

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

EXPORTING Parameters details for SVRS_GET_VERSION_SQLD_40

INFO_LINE -

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

TABLES Parameters details for SVRS_GET_VERSION_SQLD_40

VSMODISRC -

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

DD06TV_TAB -

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

DD06V_TAB -

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

DD16V_TAB -

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

VSMODILOG -

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

EXCEPTIONS details

NO_VERSION -

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

SYSTEM_FAILURE -

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

COMMUNICATION_FAILURE -

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

Copy and paste ABAP code example for SVRS_GET_VERSION_SQLD_40 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_info_line  TYPE ABAPTEXT-LINE, "   
lt_vsmodisrc  TYPE STANDARD TABLE OF SMODISRC, "   
lv_no_version  TYPE SMODISRC, "   
lv_destination  TYPE RFCDES-RFCDEST, "   
lt_dd06tv_tab  TYPE STANDARD TABLE OF DD06TV, "   
lv_object_name  TYPE VRSD-OBJNAME, "   
lv_system_failure  TYPE VRSD, "   
lv_versno  TYPE VRSD-VERSNO, "   
lt_dd06v_tab  TYPE STANDARD TABLE OF DD06V, "   
lv_communication_failure  TYPE DD06V, "   
lt_dd16v_tab  TYPE STANDARD TABLE OF DD16V, "   
lv_iv_no_release_transformation  TYPE SVRS_BOOL, "   
lt_vsmodilog  TYPE STANDARD TABLE OF SMODILOG. "   

  CALL FUNCTION 'SVRS_GET_VERSION_SQLD_40'  "
    EXPORTING
         DESTINATION = lv_destination
         OBJECT_NAME = lv_object_name
         VERSNO = lv_versno
         IV_NO_RELEASE_TRANSFORMATION = lv_iv_no_release_transformation
    IMPORTING
         INFO_LINE = lv_info_line
    TABLES
         VSMODISRC = lt_vsmodisrc
         DD06TV_TAB = lt_dd06tv_tab
         DD06V_TAB = lt_dd06v_tab
         DD16V_TAB = lt_dd16v_tab
         VSMODILOG = lt_vsmodilog
    EXCEPTIONS
        NO_VERSION = 1
        SYSTEM_FAILURE = 2
        COMMUNICATION_FAILURE = 3
. " SVRS_GET_VERSION_SQLD_40




ABAP code using 7.40 inline data declarations to call FM SVRS_GET_VERSION_SQLD_40

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.

"SELECT single LINE FROM ABAPTEXT INTO @DATA(ld_info_line).
 
 
 
"SELECT single RFCDEST FROM RFCDES INTO @DATA(ld_destination).
 
 
"SELECT single OBJNAME FROM VRSD INTO @DATA(ld_object_name).
 
 
"SELECT single VERSNO FROM VRSD INTO @DATA(ld_versno).
 
 
 
 
 
 


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!