Small SAP Talk. Collecting Available Employee HR Information in SAP

In my opinion, it is becoming increasingly clear every day that there is a growing trend toward granting individuals access to their personal data. By “individuals,” I primarily mean myself—as a subject who leaves personal data in various online services or information systems (we could argue here about the terminology and definitions of what is what). More and more often, we hear the abbreviation GDPR.

See: General Data Protection Regulation

Regardless of various localization challenges, I would like to believe that sooner or later, the successful experience of applying practices and technologies that handle and protect personal data—both at the legislative and informational levels—will be adopted across most regions worldwide. But enough with the digression.

It is possible that, in some project, the question may arise of providing employees with all the HR information available about them in the HCM component—either in full or in part. Below are a few paragraphs about how the vendor has a rather old solution that can perform this relatively simple function.

On this topic, SAP has the report RPLERDX0, which can help collect all information stored in the HR-related infotypes in the system.

See: HR Infotypes

Each execution of the report is logged in the THRPAD_ERD_LOG table.

The reasons for collecting an employee’s data are configured in the corresponding SPRO section:

IMG: Personnel Management -> Personnel Administration -> Information of Employee-Related Data -> Enter Reasons for Executing Employee Information

A set of BAdIs for customizing the report, with detailed descriptions, can be found in the following SPRO branches:

• IMG: Personnel Management -> Personnel Administration -> Information of Employee-Related Data -> BAdI: Implementation of Module for Employee Information
• IMG: Personnel Management -> Personnel Administration -> Information of Employee-Related Data -> BAdI: Change of Order of Infotypes in Employee Information
• IMG: Personnel Management -> Personnel Administration -> Information of Employee-Related Data -> BAdI: Change of Created Tree Before Output
• IMG: Personnel Management -> Personnel Administration -> Information of Employee-Related Data -> BAdI: Transformation of Infotype Data to Own Format

The vendor suggests using transaction S_L4H_60400001 to allow employees to run it themselves. An example of how to fill a standard role can be found in SAP_HR_99_ERD (transaction PFCG).

The central authorization object in this role is P_PERNR.

See: Authorization Object P_PERNR

This authorization object controls a user’s access to their own personnel number and related HR data.

The personnel number is assigned to the user in the Communication infotype (0105), subtype 0001 (System User Name). Access to an employee’s own master data is primarily used in ESS scenarios, where the user should only have access to their own data for viewing or editing.

To control access to an employee’s own personnel number using P_PERNR, you must activate the main switch in table T77S0 (transaction OOAC, switch AUTSW/PERNR). For more information on this authorization object, see P_PERNR (HR: Master Data - Personnel number check).

Some reference material on this topic can be found in the following SPRO branch:

IMG: Personnel Management -> Personnel Administration -> Information of Employee-Related Data -> Create Role for Employee

For administrators of this process, the vendor proposes using transaction S_L4H_60400001_SB. The difference from S_L4H_60400001 is the ability to select a personnel number for generating the report, as well as a different set of administrative authorizations.

For more information on authorizations, refer to the standard role SAP_HR_99_ERD_PERS_ADMIN.

Additional reference material can be found in the following SPRO branch:

IMG: Personnel Management -> Personnel Administration -> Information of Employee-Related Data -> Create Role for Administrator

Everything you need to know about the Small SAP Talk section is available in the following post:

See: Small SAP Talk