SAP REUSE_ALV_VARIANT_MAINTAIN Function Module for Definition of a display variant outside the list context
REUSE_ALV_VARIANT_MAINTAIN is a standard reuse alv variant maintain SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Definition of a display variant outside the list context 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 reuse alv variant maintain FM, simply by entering the name REUSE_ALV_VARIANT_MAINTAIN into the relevant SAP transaction such as SE37 or SE38.
Function Group: SALV
Program Name: SAPLSALV
Main Program: SAPLSALV
Appliation area:
Release date: 16-Jul-1997
Mode(Normal, Remote etc): Normal Function Module
Update:

Function REUSE_ALV_VARIANT_MAINTAIN 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 'REUSE_ALV_VARIANT_MAINTAIN'"Definition of a display variant outside the list context.
EXPORTING
* I_TABNAME_HEADER = "Header Table Name
* I_TABNAME_ITEM = "Item Table Name
* I_SAVE = ' ' "Variants can be saved
* I_POPUP = 'X' "Output in popup
* IS_LAYOUT = "List layout specifications
* IT_SPECIAL_GROUPS = "Grouping fields for column selection
* IT_SORT = "Sort table
IMPORTING
E_SAVE = "Changes were saved.
CHANGING
CT_FIELDCAT = "Field catalog with field descriptions
EXCEPTIONS
NO_CHANGE = 1 PROGRAM_ERROR = 2
IMPORTING Parameters details for REUSE_ALV_VARIANT_MAINTAIN
I_TABNAME_HEADER - Header Table Name
Data type: SLIS_TABNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TABNAME_ITEM - Item Table Name
Data type: SLIS_TABNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SAVE - Variants can be saved
Data type:Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_POPUP - Output in popup
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_LAYOUT - List layout specifications
Data type: SLIS_LAYOUT_ALVOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SPECIAL_GROUPS - Grouping fields for column selection
Data type: SLIS_T_SP_GROUP_ALVOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SORT - Sort table
Data type: SLIS_T_SORTINFO_ALVOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for REUSE_ALV_VARIANT_MAINTAIN
E_SAVE - Changes were saved.
Data type: SLIS_CHAR_1Optional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for REUSE_ALV_VARIANT_MAINTAIN
CT_FIELDCAT - Field catalog with field descriptions
Data type: SLIS_T_FIELDCAT_ALVOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_CHANGE - No change made
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PROGRAM_ERROR - Program errors
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for REUSE_ALV_VARIANT_MAINTAIN 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_e_save | TYPE SLIS_CHAR_1, " | |||
| lv_no_change | TYPE SLIS_CHAR_1, " | |||
| lv_ct_fieldcat | TYPE SLIS_T_FIELDCAT_ALV, " | |||
| lv_i_tabname_header | TYPE SLIS_TABNAME, " | |||
| lv_program_error | TYPE SLIS_TABNAME, " | |||
| lv_i_tabname_item | TYPE SLIS_TABNAME, " | |||
| lv_i_save | TYPE SLIS_TABNAME, " ' ' | |||
| lv_i_popup | TYPE SLIS_TABNAME, " 'X' | |||
| lv_is_layout | TYPE SLIS_LAYOUT_ALV, " | |||
| lv_it_special_groups | TYPE SLIS_T_SP_GROUP_ALV, " | |||
| lv_it_sort | TYPE SLIS_T_SORTINFO_ALV. " |
|   CALL FUNCTION 'REUSE_ALV_VARIANT_MAINTAIN' "Definition of a display variant outside the list context |
| EXPORTING | ||
| I_TABNAME_HEADER | = lv_i_tabname_header | |
| I_TABNAME_ITEM | = lv_i_tabname_item | |
| I_SAVE | = lv_i_save | |
| I_POPUP | = lv_i_popup | |
| IS_LAYOUT | = lv_is_layout | |
| IT_SPECIAL_GROUPS | = lv_it_special_groups | |
| IT_SORT | = lv_it_sort | |
| IMPORTING | ||
| E_SAVE | = lv_e_save | |
| CHANGING | ||
| CT_FIELDCAT | = lv_ct_fieldcat | |
| EXCEPTIONS | ||
| NO_CHANGE = 1 | ||
| PROGRAM_ERROR = 2 | ||
| . " REUSE_ALV_VARIANT_MAINTAIN | ||
ABAP code using 7.40 inline data declarations to call FM REUSE_ALV_VARIANT_MAINTAIN
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.| DATA(ld_i_save) | = ' '. | |||
| DATA(ld_i_popup) | = 'X'. | |||
Search for further information about these or an SAP related objects