Retroactive Accounting for Concurrent
Employment 
Use
In an SAP R/3 System, in which concurrent employment is active, retroactive accounting is different in some ways to a system without concurrent employment.
Features
SAP R/3 uses function XRETR (Retroacting Accounting) in concurrent employment to calculate rounding differences and take them into account in the original period. Function XRETR uses processing class 23 (Processing Wage Types in Retroactive Accounting) to determine all wage types from the previous payroll results that are required for retroactive accounting. Function XRETR stores the retroactive differences in internal table DT_PERSON (Difference Table for Person).
All wage types that affect retroactive
accounting depend on the 
grouping reason
XXNT (Net, Retroactive Accounting, Payment). Therefore they are
processed together for all personnel assignments of an employee that belong to
the same grouping according to this grouping reason. As a rule this
grouping is according to employer.For more information, see Grouping Personnel
Assignments for Net Calculation, Retroactive Accounting, and
Payment.
This has the following effects:
Retroactive accounting differences
SAP R/3 does not transfer retroactive accounting differences (wage type /551) from one grouping to another. This is also the case when all personnel assignments of an employee, which belong to the same grouping, end and yet these personnel assignments still have retroactive differences. In this case, SAP R/3 runs payroll again for the personnel assignments, although they are inactive, and creates a payment for them.
An employee has four personnel assignments. Personnel assignments 1 and 2 belong to employer A, personnel assignments 3 and 4 belong to employer B. A retroactive difference occurs in a payroll period for personnel assignments 1 and 2. Personnel assignments 1 and 2 belong to employer A, personnel assignments 3 and 4 belong to employer B. A retroactive difference occurs in a payroll period for personnel assignments 1 and 2. The retroactive difference is, however, not transferred to personnel assignments 3 and 4. Instead, SAP R/3 runs payroll for personnel assignments 1 and 2 again.
Balances for the subsequent period
SAP R/3 does not transfer balances for the subsequent period (wage type /565) from one grouping to another. This is also the case when all personnel assignments of an employee, which belong to the same grouping, end and yet these personnel assignments still have a balance for the subsequent period. In this case, SAP R/3 runs payroll again for the personnel assignments, although they are inactive. Payroll is run for the personnel assignments as long as there is still a balance for the subsequent period.
You receive a message in the payroll log if there is a balance for the subsequent period for an employee.
Claims
The same applies to claims (wage type /561) as for balances for the subsequent period.
Arrears wage types
SAP R/3 does not transfer arrears wage types from one grouping to another. This is also the case when all personnel assignments of an employee, which belong to the same grouping, end and yet arrears wage types still exist for these personnel assignments. In this case you can use function PREND (Modify Table DDNTK at Loop End) to ensure that SAP R/3 still runs payroll for these personnel assignments, even though they are inactive. For more information, see the documentation for function PREND.
For
more information on retroactive accounting before conversion to concurrent
employment, see convert payroll to
concurrent employment.
See also: