A Few Words About Retroactive Accounting and Personnel Infotypes

Hi there! Once again, I had the good fortune of digging around in a sandbox filled with mothball dust. In this note, I want to elaborate on configuring retroactive accounting in personnel infotypes. If reading that sentence made you yawn confidently, you're better off looking at the "Marilyn Monroe Effect" on pigeons.

So, it's no secret that for each PA infotype in SAP, it's possible to activate a relevance property responsible for triggering retroactive payroll accounting. This is done using table T582A.

See: Retroactive Accounting

Depending on the system settings, if the payroll control record is in a certain status, users will not be able to make changes to an infotype for which the aforementioned property is active.

See: Payroll Control Record

Based on business process requirements, the settings for each infotype may vary—down to specifying which infotype fields will trigger retroactive accounting if changed.

I acknowledge that there might be cases where it’s necessary to bypass the settings in table T582A. The following sections will explain how this can be done.

The configuration of infotype 0021 – "Family Member/Dependents" in my system looks as follows:

Additional system reaction settings for changes to any field in IT 0021 – "Family Member/Dependents" are defined in table T588G.

Let’s not dwell on this.

Using transaction PA03, lock the payroll control record.

Create an implementation for BAdI HRPAD00_RETRO_RELE and fill it with the required rules and validations (in simpler terms: write some ABAP). Also, define a filter for the infotype for which the new implementation is being created, and activate the changes in the new implementation class.

Ensure the implementation is active and will be called upon activation.