Up to this point, the output of the ALV does not allow the user to save changes made to layout. In this recipe, we will add coding that will allow saving user-specific layouts, load layouts, as well as specify a default layout.
For enabling layout saving, follow these steps:
- We declare two variables and also, an object reference to the class
cl_salv_layout. In addition, a key is defined based on the typesalv_s_layout_key. - The
get_layoutmethod is then used to get the layout object for the ALV. - The
set_keymethod is called for the layout objectmylayout. Themykeystructure having the report namesy-repidis passed to this method. - Next, the
set_save_restrictionmethod is called. It is passed the static attributeRESTRICT_USER_DEPENDANTof the interfaceif_salv_c_layout. - Finally, the
set_defaultlayout method is called with the value'X', as shown in the next screenshot.
- The code is added before the
ALVdisplay method call shown in the first screenshot of this chapter.
In this recipe, we declared a layout variable based on the cl_salv_layout class. An essential step is to set the key of the layout object and passing the name of the program. This is done using the set_key method.
Next, for enabling the Save layout button, the
set_save_restriction method is used. Based on the value passed on to the method, the system determines whether the user is allowed to save layout as user-specific, user-unspecific, or without any restrictions. Three possible constant values may be passed.
Since our requirement was to enable user to store layout as User-Specific, we used RESTRICT_USER_DEPENDANT constant attribute of the interface if_salv_c_layout.
Finally, we wanted the Default setting checkbox to be enabled so that the user may save a particular layout as his or her default. For this reason, the set_default method was called with the value 'X'.
The next time the user executes the report, his or her default layout is loaded and data displayed in that layout format.