|
Q1: How to retrieve "how many
infotype Auth are given to a user"?
Report : RHUSERRELATIONS - This report provides a means to evaluate all SAP HR authorizations for a specific user. The report is used for checking the consistency of relationships and then removes all inconsistent relationship records from the database, depending on whether you have selected the "direct delete" option in the initial select screen. The removal of inconsistencies from the database, like the entries (relationship records) in HRP1001 (DB table for infotype 1001) that do not have a source or target object are deleted. Also the system deletes the inverse relationships of the inconsistent records. Logically, 'P' objects (people) whose personnel numbers have been deleted, hence do not exist anymore but the relationship would still exist between the Person and the object (like position, holder etc) and such relationships are also deleted. this is to ensure that the vacant positions report and other reports get the correct data, for example the vacant positions report would not give the correct output if this still exists. The following are useful transaction you can find it out: SOBN01- Personal data of user HRUSER - TO get all the data PFCG
- to get Role Maintenance
Q2: How to restrict by EE Subgroup say for example 13, 14 , 17 - 20 and I did that by adding these numbers in the MASTER DATA --> EMPLOYEE SUBGROUP, but still when executing PA20 I am able to view the subgroup 15. Seems like your user has more access than that you said you gave. Run the report for displaying user assignment : RHUSERRELATIONS, when you run it, check the radio button which says "HR authorization", and leave the P_ORGIN check box like that. This will show you from which profiles user is getting P_ORGIN and what level of access he is getting from those. |
|
Read also
Do you have a SAP Basis Question? SAP Basis Admin Books
SAP Basis Tips
Administration In SAP - Sapgui, Unix, SAP ITS, Router, Client Copy and IDES Main Index
All the site contents are Copyright © www.erpgreat.com
and the content authors. All rights reserved.
|