A Few Words About the RPUAUD00 Program
Briefly About RPUAUD00
SAP’s standard functionality includes the ability to view change logs for any infotype that might be of interest to you as a functional consultant or business user. The configuration for this process is so straightforward that, in my opinion, it's not worth detailing here — you can simply refer to the relevant section in the SAP documentation:
See: Logged Changes in Infotype Data (Report RPUAUD00)
Prerequisites
So that changes to infotype fields (change, create, delete) are recorded as documents, you must make sure that these fields are maintained in the views HR Documents: Infotypes to be Logged (V_T585A), HR Documents: Field Group Definition (V_T585B) and HR Documents: Field Group Characteristics (V_T585C) .
An archive can only be displayed if it has been created with Archive Administration (transaction SARA).
Once the necessary configuration steps outlined in the documentation are completed, you can use the RPUAUD00
program to view change logs for employee infotype data.
And Then Came the Update...
In one of the updates to the SAP_HRRXX
component, the vendor introduced additional selection criteria for the RPUAUD00
program by moving them to a new report: RPUAUD00_PNPCE
.
See: SAP Note 2132315 – RPUAUD00: Additional selection criteria
Delivery:
Import the relevant Support Package. After you import the Support Package, a new switch is available in the table T77S0 (system table) - group ADMIN, semantic abbreviation RPAUD. After you activate this switch, the previous report RPUAUD00 is no longer available. When you call this report, the system performs an automatic redirection to the new report RPUAUD00_PNPCE. This contains the enhancements listed above.
After activating the ADMIN / RPAUD switch in T77S0
the selection screen of the familiar program is slightly modified.
It’s important to note that you cannot run RPUAUD00_PNPCE
directly, which is confirmed by the corresponding error message.
The RPUAUD00_PNPCE program is called from RPUAUD00, and this call includes a check via the read_t77s0_switch form routine.
P.S. (1)
Special attention should be paid to SAP Note 2321263 – Report RPUAUD00 and authorization check, which addresses the topic of authorization handling for the RPUAUD00
program.
Example from the Note:
- A user with "restricted" authorizations for a specific infotype runs RPUAUD00.
- In the example, Infotype 0008 for a given personnel number has two records:
from 01.02.2015 to 06.09.2015 and from 07.09.2015 to 31.12.9999 - The user has authorization for Infotype 0008 only for the first period (01.02.2015 to 06.09.2015).
- However, when the user runs RPUAUD00, both records of Infotype 0008 are displayed.
SAP’s explanation: The report serves as an “audit of master data changes.” In other words, it’s sufficient for a user to have general read access to the infotype, regardless of the specific authorized time period.
Additional Note:
Since the report is based on the PNPCE logical database, personnel master data authorizations are governed by the P_ORGIN authorization object.
Disabling authorization checks for this report is handled by the P_ABAP authorization object.
For this object, enter the report name(s) in the REPID field and the degree of simplification to be used for the authorization check in the COARS field.
The following degrees of simplification are possible:Authorization using COARS = <BLANK> or no authorization. The authorization checks are to be processed as in
Authorization using COARS = 1 . The authorization checks for the infotype/subtype combination and for organizational assignment are to be checked separately. This means that a user is authorized to read a personnel number when he or she has a read authorization for all the infotypes (subtypes) requested by the program and that the user has a read authorization for the organizational assignment of the personnel number.Authorization using COARS = 2. The authorization check is inactive
P.S. (2)
If this note seemed boring or pointless to you, you can entertain yourself by hunting for grammatical errors in SAP Note 2321263 – Report RPUAUD00 and authorization check. You might as well skim through that note too — whichever way you prefer. Take care!