logn as authorization value

[Former Member]

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

[Former Member]

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

[former_member194669]

I have a doubt.

Whether you are going to check

1. Authorisation object with ekko-ernam

or

2. Authorisation object with sy-uname

or

3. sy-uname = ekko-ernam

a®

[Former Member]

Hi,

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

[former_member194669]

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®