Payroll Frequently Asked Questions || Common errors during live run in SAP

Payroll – FAQ 

Common errors during live run: 

1. RA accounting date set by system, 01.10.18, is before persearli: 

Reason: This means that RA date is changed by the user. If corrections are done for the period before RA date, the RA date has to be changed. 

Solution: Before changing the RA date, please note down the date available in the system. After changes in the PA30, restore the RA date. 

2. Wage type incorrectly reduced: 

This means that the deductions are more than the earnings. It happens when there is LWA or absences or Unauthorized leave, when earnings are less or NIL. In such cases, the mandatory deductions are taken off by the system. However the out of account recoveries need to be delimited, to enable the system to run the payroll. Even if it is zero salary, the payroll run should happen and zero payslips should be generated.

3. Current payroll payment date ** less than last payroll payment date

Reason: Off cycle payment has been done after the current payroll payment date. Ie the off cycle payment for the previous date could not be executed, if any offcycle has been executed, after the entered date. 

Solution: Modify the off cycle date, as any date after the previous payment date.

Common errors during posting run:

4. Incorrect status:

Reason: This is because of the use of wrong Wage Type while maintaining data e.g. Postal Pensioners using Telecom Pensioners Wagetype.

Solution: Click on Document Overview, and then double click on the document, you will find the details of the issue and the incorrect Emp IDs. Correct the wrong wage type and save the data

5. PPMOD:

Reason: This error occurs, if the cost centre is missing or org. key (head of account) is missing/incorrect or more than one official is mapped to the same position ID. 

Solution: Delete the live run. Then map the missing data or correct the incorrect head of account, then do live run and then final posting run. The post id of the official has to be checked whether 2 officials are placed in the same position id. This should be avoided. 

6. Posting balance run: 

Reason: This error is due to any changes in the previous payroll data or deletions of data in info type 57. All out of account records act for the current month and not for retrospective months, for which pay roll is already executed. 

Solution: Double click on the arrow symbol available before Employee ID or symbol at Messages and it will show the period and year e.g. 02/2018 means April 2018 data. Identify the difference of the data and pay slip of the period given in the error and restore the original data. 

7. Posting skipped:

Reason: This error occurs if posting is already completed. This may also be due to non-completion of live pay roll run. 

Solution: If live run is not completed, please execute the live run. Posted employees are displayed in the bank transfer report.