SAP GET_VERSION_LIST_40 Function Module for Extracts the Versions of an Object from the Version Directory
GET_VERSION_LIST_40 is a standard get version list 40 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Extracts the Versions of an Object from the Version Directory processing and below is the pattern details for this FM, 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 version list 40 FM, simply by entering the name GET_VERSION_LIST_40 into the relevant SAP transaction such as SE37 or SE38.
Function Group: SVRZ
Program Name: SAPLSVRZ
Main Program: SAPLSVRZ
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function GET_VERSION_LIST_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 'GET_VERSION_LIST_40'"Extracts the Versions of an Object from the Version Directory.
EXPORTING
* OBJNAME = ' ' "
* OBJTYPE = ' ' "
TABLES
VERSION_LIST = "
IMPORTING Parameters details for GET_VERSION_LIST_40
OBJNAME -
Data type: VRSD_40A-OBJNAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJTYPE -
Data type: VRSD_40A-OBJTYPEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GET_VERSION_LIST_40
VERSION_LIST -
Data type: VRSD_40AOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GET_VERSION_LIST_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_objname | TYPE VRSD_40A-OBJNAME, " SPACE | |||
| lt_version_list | TYPE STANDARD TABLE OF VRSD_40A, " | |||
| lv_objtype | TYPE VRSD_40A-OBJTYPE. " SPACE |
|   CALL FUNCTION 'GET_VERSION_LIST_40' "Extracts the Versions of an Object from the Version Directory |
| EXPORTING | ||
| OBJNAME | = lv_objname | |
| OBJTYPE | = lv_objtype | |
| TABLES | ||
| VERSION_LIST | = lt_version_list | |
| . " GET_VERSION_LIST_40 | ||
ABAP code using 7.40 inline data declarations to call FM GET_VERSION_LIST_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 OBJNAME FROM VRSD_40A INTO @DATA(ld_objname). | ||||
| DATA(ld_objname) | = ' '. | |||
| "SELECT single OBJTYPE FROM VRSD_40A INTO @DATA(ld_objtype). | ||||
| DATA(ld_objtype) | = ' '. | |||
Search for further information about these or an SAP related objects