Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Control User Specific button in ALV report

Former Member
0 Likes
626

Hi,

Can anybody please suggest me how to control "USER SPECIFIC" button in ALV report layout using authorization object. I mean if you can tell me which authorization object is responsible to control the "USER SPECIFIC" button.

Hi,

Can anybody please suggest me how to control "USER SPECIFIC" button in ALV report layout using authorization object. I mean if you can tell me which authorization object is responsible to control the "USER SPECIFIC" button.

2 REPLIES 2
Read only

Former Member
0 Likes
500

Dear Gordon,

Could you please provide more details about the report that you are checking?

Normally the below object are used for the administration of ALV reports.

F_IT_ALV

S_ALV_LAYO

Regards,

Read only

Former Member
0 Likes
500

additional info to what Lakshmi already said:-

normally the restrictions for saving layouts/display variants are done at 2 levels:

1) The developer of an ALV list first predetermines the authorization in the 'i_save' parameter within the code.

I_SAVE = ' ' -


layouts cannot be saved

I_SAVE = 'A' -


user-specific and cross-user layouts can be saved

I_SAVE = 'X' --- cross-user layouts can be saved

I_SAVE = 'U' --- user-specific layouts can be saved

2) The second level comes to us restriciting the S_ALV_LAYO which gives access to users to save global layouts if I_SAVE for that particular transaction is A or X.

for example, a report has I_SAVE= 'A', which means

it will allow to save User-specific layouts without any restrictions.

and if user has S_ALV_LAYO then he can save both User-Specific and Global Layouts(variants).

it would be better to keep this object separate.