SAP G_VARIANT_UNLOAD Function Module for
G_VARIANT_UNLOAD is a standard g variant unload 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 g variant unload FM, simply by entering the name G_VARIANT_UNLOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: GUTV
Program Name: SAPLGUTV
Main Program:
Appliation area: G
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function G_VARIANT_UNLOAD 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 'G_VARIANT_UNLOAD'".
EXPORTING
* I_CLIENT = SY-MANDT "
I_PROGRAM = "
I_VARIANT = "
* I_LANGUAGE_VECTOR = "
IMPORTING
E_T_VARID_EXP = "
E_T_VARIT_EXP = "
E_T_VARIS_EXP = "
E_T_VARI_EXP = "
EXCEPTIONS
VARIANT_NOT_FOUND = 1
IMPORTING Parameters details for G_VARIANT_UNLOAD
I_CLIENT -
Data type: SY-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PROGRAM -
Data type: GUTV_PROGRAMOptional: No
Call by Reference: No ( called with pass by value option)
I_VARIANT -
Data type: GUTV_VARIANTOptional: No
Call by Reference: No ( called with pass by value option)
I_LANGUAGE_VECTOR -
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for G_VARIANT_UNLOAD
E_T_VARID_EXP -
Data type: GUTV_T_VARID_EXPOptional: No
Call by Reference: Yes
E_T_VARIT_EXP -
Data type: GUTV_T_VARIT_EXPOptional: No
Call by Reference: Yes
E_T_VARIS_EXP -
Data type: GUTV_T_VARIS_EXPOptional: No
Call by Reference: Yes
E_T_VARI_EXP -
Data type: GUTV_T_VARI_EXPOptional: No
Call by Reference: Yes
EXCEPTIONS details
VARIANT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for G_VARIANT_UNLOAD 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_i_client | TYPE SY-MANDT, " SY-MANDT | |||
| lv_e_t_varid_exp | TYPE GUTV_T_VARID_EXP, " | |||
| lv_variant_not_found | TYPE GUTV_T_VARID_EXP, " | |||
| lv_i_program | TYPE GUTV_PROGRAM, " | |||
| lv_e_t_varit_exp | TYPE GUTV_T_VARIT_EXP, " | |||
| lv_i_variant | TYPE GUTV_VARIANT, " | |||
| lv_e_t_varis_exp | TYPE GUTV_T_VARIS_EXP, " | |||
| lv_e_t_vari_exp | TYPE GUTV_T_VARI_EXP, " | |||
| lv_i_language_vector | TYPE C. " |
|   CALL FUNCTION 'G_VARIANT_UNLOAD' " |
| EXPORTING | ||
| I_CLIENT | = lv_i_client | |
| I_PROGRAM | = lv_i_program | |
| I_VARIANT | = lv_i_variant | |
| I_LANGUAGE_VECTOR | = lv_i_language_vector | |
| IMPORTING | ||
| E_T_VARID_EXP | = lv_e_t_varid_exp | |
| E_T_VARIT_EXP | = lv_e_t_varit_exp | |
| E_T_VARIS_EXP | = lv_e_t_varis_exp | |
| E_T_VARI_EXP | = lv_e_t_vari_exp | |
| EXCEPTIONS | ||
| VARIANT_NOT_FOUND = 1 | ||
| . " G_VARIANT_UNLOAD | ||
ABAP code using 7.40 inline data declarations to call FM G_VARIANT_UNLOAD
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 MANDT FROM SY INTO @DATA(ld_i_client). | ||||
| DATA(ld_i_client) | = SY-MANDT. | |||
Search for further information about these or an SAP related objects