2010 Mar 15 4:57 PM
Currently we are using P_ORIGIN Authorisation. In this we are using personnel area and Org. Key as restrictions. Org. Key is currently set to be Personnel Subarea.
Example-
Authorization level: M, R, W
Infotype: *
Personnel Area: US10
Employee Group: *
Employee Subgroup: *
Subtype: *
Organizational Key: US01
The authorization restriction works correctly for Personnel area and users are not able to view employee data from other personnel areas. However, they are able to view employees with Personnel areas other than US01. Though they do not have access to change this information, they are still able to display employee data.
Is there anyway to make authorisation on Organization Key behave the same way as Personnel Area. i.e. users should be restricted only the Org Key (Personnel subarea) US01.
Alternately: Can we have a custom authorisation object based on a field from PA0008 - example: TRFST?
Thanks,
Anil
Currently we are using P_ORIGIN Authorisation. In this we are using personnel area and Org. Key as restrictions. Org. Key is currently set to be Personnel Subarea.
Example-
Authorization level: M, R, W
Infotype: *
Personnel Area: US10
Employee Group: *
Employee Subgroup: *
Subtype: *
Organizational Key: US01
The authorization restriction works correctly for Personnel area and users are not able to view employee data from other personnel areas. However, they are able to view employees with Personnel areas other than US01. Though they do not have access to change this information, they are still able to display employee data.
Is there anyway to make authorisation on Organization Key behave the same way as Personnel Area. i.e. users should be restricted only the Org Key (Personnel subarea) US01.
Alternately: Can we have a custom authorisation object based on a field from PA0008 - example: TRFST?
Thanks,
Anil
2010 Mar 15 6:36 PM
Hi,
Goto SU21 to create your own Authorization object.
Regards,
Srini.