Hierarchy
SAP_HRCDE (Software Component) Sub component SAP_HRCDE of SAP_HR⤷
PA-PA-DE (Application Component) Germany⤷
PBAS_ERD (Package) Employee-Related Data
IMG Activity
| ID | PA_XX_ERD_095 | Create Role for Administrator |
| Transaction Code | S_L4H_49002527 | (empty) |
| Created on | 20111107 | |
| Customizing Attributes | PA_XX_ERD_01 | Information of Employee-Related Data (Optional/Not Critical) |
| Customizing Activity | PA_XX_ERD_095 | Create Role for Administrator |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | PA_XX_ERD_095 |
Use
In this Customizing activity, you create the role that you assign to the administrator for executing the transaction (S_L4H_60400001_SB) to call the report program Information of Employee-Related Data (RPLERDX0).
Requirements
Standard settings
Activities
Copy the SAP sample role SAP_HR_99_ERD_PERS_ADMIN to your customer-specific role.
Use the transaction Info. Employee Data by Administrator (S_L4H_60400001_SB) for the authorization object Transaction Code Check at Transaction Start.
Assign the authorizations based on your authorization objects, for example, HR: Master Data (P_ORGIN) und HR: Master Data - Extended Check (P_ORGXX). Assign the read authorization for all infotypes. If the read authorization is missing for an infotype, the report program Information of Employee-Related Data (RPLERDX0) does not output anything and terminates with an error message about insufficient authorization. The role for an administrator does not need to maintain the authorization of the authorization object HR: Master Data - Personnel Number Check (P_PERNR). If this administrator could collect the information for himself or herself using the organizational authorization check, but this is to be expressly forbidden, you define the authorization object HR: Master Data - Personnel Number Check (P_PERNR) such that the access is to be excluded for the administrator#s own personnel number (PERNR) by setting the field Interpretation of assigned personnel number (PSIGN) to E.
For details on processing the roles, see the documentation for transaction PFCG.
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | I | Valid for countries specified |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| PFCG | T - Individual transaction object | PFCG |
History
| Last changed by/on | SAP | 20111107 |
| SAP Release Created in |
