topic logn as authorization value in Application Development and Automation Discussions

logn as authorization value

Former Member — Wed, 22 Apr 2009 15:08:29 GMT

Hello,

For on of our clients, we recived the demand of limiting the view for purchase orders on the creator-field (ekko-ernam).

The only thing we found so far, is to built a user exit where we check a custom authorization object.

But maybe we're overlooking something , so I decided to put the question on sdn

Re: logn as authorization value

former_member194669 — Wed, 22 Apr 2009 15:19:16 GMT

I have a doubt.

Whether you are going to check

1. Authorisation object with ekko-ernam

2. Authorisation object with sy-uname

3. sy-uname = ekko-ernam

a®

Re: logn as authorization value

Former Member — Wed, 22 Apr 2009 15:21:18 GMT

Hi,

we want to check if the ekko-ernam field is equal to sy-uname...

Re: logn as authorization value

former_member194669 — Wed, 22 Apr 2009 15:32:37 GMT

But i think this is not a good idea.

Implications:users only view their own PO's.

My suggestion will be create a custom authorisation object . Give access this custom auth obhect to super users ( some specific users who are treated as business owners and wanted to see all PO's)

then


call authorisation-check      " Check for super users 
if sy-subrc ne 0.                 " If don't have auth then check for sy-uname eq ekko-ernam
   if sy-uname ne ekko-ernam
      Message Error
   endif
endif.

a®