SAP VERSION_VARIANTS_GET Function Module for NOTRANSL: Varianten von Versionen von Layoutbausteinen lesen
VERSION_VARIANTS_GET is a standard version variants get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Varianten von Versionen von Layoutbausteinen lesen 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 version variants get FM, simply by entering the name VERSION_VARIANTS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: VEVA
Program Name: SAPLVEVA
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VERSION_VARIANTS_GET 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 'VERSION_VARIANTS_GET'"NOTRANSL: Varianten von Versionen von Layoutbausteinen lesen.
EXPORTING
ASSORTMENT = "Assortment
TABLES
T_LAYOUT_MODULES = "Validity and Status of Layout Module Versions
T_WLVA = "Assignment Table for Layout Module Variants for Stores
IMPORTING Parameters details for VERSION_VARIANTS_GET
ASSORTMENT - Assortment
Data type: ASORTOptional: No
Call by Reference: Yes
TABLES Parameters details for VERSION_VARIANTS_GET
T_LAYOUT_MODULES - Validity and Status of Layout Module Versions
Data type: WLMVOptional: No
Call by Reference: Yes
T_WLVA - Assignment Table for Layout Module Variants for Stores
Data type: WLVAOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for VERSION_VARIANTS_GET 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_assortment | TYPE ASORT, " | |||
| lt_t_layout_modules | TYPE STANDARD TABLE OF WLMV, " | |||
| lt_t_wlva | TYPE STANDARD TABLE OF WLVA. " |
|   CALL FUNCTION 'VERSION_VARIANTS_GET' "NOTRANSL: Varianten von Versionen von Layoutbausteinen lesen |
| EXPORTING | ||
| ASSORTMENT | = lv_assortment | |
| TABLES | ||
| T_LAYOUT_MODULES | = lt_t_layout_modules | |
| T_WLVA | = lt_t_wlta | |
| . " VERSION_VARIANTS_GET | ||
ABAP code using 7.40 inline data declarations to call FM VERSION_VARIANTS_GET
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