Audit compliance S_DEVELOP DEBUG

[Former Member]

Hi,

We are having a situation where a user is unable to view one particular WebDynpro Application in Production. However, the same user can view the remaining webdynpro Application. All other production users can also view this WebDynpro Applciation in Production. We have checked all the Authorization of this user and did a comparison with another user who does the same job. We couldnt find any difference.

Also, we used this user in our Test System and are unable to reproduce this issue. We compared this user from the Test System and Production System and found no difference.

My last option is to debug with the user account by using an external breakpoint on the user's account in production.

I understand that as per Audit compliances, end users shouldnt have S_DEVELOP DEBUG access. But for such situations, where we find it necessary, how do we go about doing this. We need to get past this issue and at the same time make sure that the auditors dont fire us.

Is it all right to give S_DEVELOP with ACTVT=03 (display) and OBJTYPE=DEBUG ?

Please suggest.

THanks.

Edited by: Muralidaran Shanmugham on Mar 29, 2011 12:43 AM

[Former Member]

> Is it all right to give S_DEVELOP with ACTVT=03 (display) and OBJTYPE=DEBUG ?

Even a display access with object type DEBUG will provide debug access to the users. Why not check with your developers if they have enabled a check for table with user entries( who should be authorized to to view the webdynpro application.)

Thanks .

Anjan pandey