The SAP List Viewer (ALV) simplifies lists and reports by providing users with standardized interfaces and list formats. The ALV grid control, a piece of functionality within the ALV, arranges reports in a grid format. When you start some reports in SAP SCM, the ALV grid control automatically activates. For example, you can run transaction code IW38 (change Plant Maintenance [PM] orders: list of orders), which brings you to a report in which the ALV grid control is automatically activated (Figure 1). Figure 1 displays a PM orders table with the ALV grid control that contains options for the ALV in the function toolbar. In the output table, the ALV presents you with several actions, such as resizing columns, moving columns using the drag and drop functionality, and sorting the list by several columns simultaneously.

Figure 1

A table displayed with the ALV grid control via transaction code IW38

In this article, I’ll explain how to use authorization object S_ALV_LAYO (ALV standard layout) to restrict users’ access to changing report layouts. This process applies to R/3 4.6C and higher.

End users frequently want to change report layouts of the ALV because they don’t like its appearance. The user changes it and saves it under a variant that many users utilize. Then other users using the same report variant complain about these changes and make further layout changes themselves. These can cause variations in the report layouts, such as altered columns and removed subtotals, which in turn create inconveniences for other users accustomed to using the same report variants layouts.

To prevent users from globally changing these report layouts, you should restrict users’ access by using authorization object S_ALV_LAYO. Only authorization administrators can control authorizations for S_ALV_LAYO, which controls the save process for ALV report layouts.

Restrict Users’ Authorization Access Using S_ALV_LAYO

The authorization administrator can access authorization object S_ALV_LAYO by using the Profile Generator tool and can define it by running transaction code PFCG (role maintenance). On the screen that appears, he or she should click on the pencil icon , which displays a pop-up window (see Figure 2).

Figure 2

Maintain the authorization value in the authorization object S_ALV_LAYO via transaction code PFCG

Authorization object S_ALV_LAYO always contains only one authorization field with one authorization value – activity 23 Maintain. If the authorization administrator checks the 23 Maintain check box under authorization object S_ALV_LAYO’s activity field, he or she allows the end user to change the default variant for all users who use the same report layout. When saved, the variant becomes global and everyone can see it.

Authorization object S_ALV_LAYO without an authorization value (23 Maintain) for the activity field (ACTVT), however, forces the layout to be user-specific and prevents users from changing report layouts globally. For example, when users create a report using transaction code IW38 or change the layout, they need to save the layout variant by following menu path Settings>Display variants>Save as variant (Figure 3). End users with this authorization do not have the ability to uncheck the User-specific check box, so they won’t be able to globally change or overwrite a variant. Moreover, they cannot create global variants seen by everyone.

Figure 3

Save a layout variant when creating or changing a report

Which activity field, if any, is checked determines whether or not the user has authorization to create, change, or set default layouts. (In this example, the activity field is ACTVT = 23.) Note that no user can change the table data. Authorization object S_ALV_LAYO and the activity field with value 23 Maintain only refer to the layout.

Maria Nikolova

Maria Nikolova has worked as a senior SAP expert for the National Electricity Company (NEK) in Bulgaria since January 1999. Maria has a master’s degree in telecommunications as an engineer from the Technical University in Sofia, Bulgaria. She has experience with an MIS project implementation of SAP R/3 (headquarters and rollout), the authorization concept and user administration, SAP Customer Competence Center (SAP CCC) , SRM, and the SD, HR, CO, Asset Management (AM), MM, and PM modules. Prior to joining NEK, she worked as a manager of Equipment Engineering Ltd. for four years.

You may contact the author at searchsapmnikolova@yahoo.com.

If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.