Salary account transfer: error in the first productive payroll run after going live during the year
Initial Situation
During the first payroll run after going live during the year and an associated payroll account transfer during the year after 05/2020, the error occurs: The retroactive accounting date set by the system is before the personal LOWEST retroactive accounting.
The error should not occur if you are on the latest patch level, which is mentioned in Note 2940786.
The error correction on the part of SAP became necessary due to an incorrect calculation of social security contributions for the wage tax statement. You can read about it in SAP Note 2875932.
If the aforementioned note is in your system, if certain wage types (e.g. /2L3-/2L6) exist, the retroactive accounting date 01.01.2020/0/XNUMX is written to the cluster that is created when the wage account is transferred (accounting with the schema DLKXNUMX).
Unfortunately, there is no reference to the payroll account transfer in any of the instructions mentioned, which is why we mention this.
There are several notes and fixes of fixes on this topic:
The origin notice is the following:
2875932 - LStB: Proportionate calculation SV - corrections 01/2020
https://launchpad.support.sap.com/#/notes/2875932
2925500 - LStB: Proportional calculation SV - Proportional calculation is not carried out
https://launchpad.support.sap.com/#/notes/2925500
2930340 - LStB: Pro rata calculation SV - SV contributions to be certified are too high
https://launchpad.support.sap.com/#/notes/2930340
2940786 - LStB: Pro rata calculation SV - Automatic recall before personally lowest retrospective date
https://launchpad.support.sap.com/#/notes/2940786
Solution or workaround
Either you import all the mentioned notes including their dependencies.
If this is not possible because you For example, if you have migrated to an existing productive environment on which other productive personnel areas are located and short-term patching is undesirable, you can use the following workaround:
In table T596C, change the entry for subapplication LBSV to the date of your productive start month. A change in the customer table T596D has no effect
After a patch, a forced recalculation must then be carried out to the personnel areas that were already billed before the go-live.
Do you need further help on the topic: Errors in the first productive accounting after going live during the year? Use the contact form and send us a message.
