Do you have any question about this error?
Message type: E = Error
Message class: HRPAYDEPF - Error messages for German infotype module pools: garnishment
Message number: 321
Message text: Set earliest personal retroactive accounting date (infotype 0003) to &1
A cleanup of the personnel number is necessary. As payroll cannot be run
for the employee due to the employee leaving the company, the cleanup is
generally not possible.
The system sets the status to <LS>S01 Check</>.
Enter the date of the current in-period (&v1&) as the earliest personal
retroactive accounting date for the personnel number in the <LS>Payroll
Status</> infotype (0003). If the employee joins the company again, you
can cancel the retroactive accounting lock and then perform a new check
and cleanup of the shadow cluster at that time.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
HRPAYDEPF321
- Set earliest personal retroactive accounting date (infotype 0003) to &1 ?The SAP error message HRPAYDEPF321 indicates that there is an issue with the retroactive accounting date in the employee's infotype 0003 (Payroll Status). This error typically arises when the system detects that the earliest personal retroactive accounting date is not set correctly, which can prevent payroll processing for the employee.
Cause:
- Missing or Incorrect Retroactive Accounting Date: The earliest personal retroactive accounting date (PRAD) is not set or is set to a date that is not valid for the payroll period being processed.
- Infotype 0003 Configuration: The configuration of infotype 0003 may not align with the payroll processing requirements.
- Employee Status: The employee's status may not allow for retroactive changes, or there may be inconsistencies in the employee's data.
Solution:
Set the Earliest Personal Retroactive Accounting Date:
- Go to the employee's infotype 0003 (Payroll Status) in the SAP system.
- Check the field for the earliest personal retroactive accounting date (PRAD).
- Set this date to a valid date that allows for the necessary payroll adjustments. This date should be before or equal to the current payroll period.
Review Infotype Configuration:
- Ensure that the configuration for infotype 0003 is correct and aligns with the payroll processing requirements.
- Check if there are any specific rules or settings that might affect the retroactive accounting date.
Check Employee Data:
- Verify the employee's status and ensure that there are no inconsistencies in their data that could affect payroll processing.
- Make sure that all relevant infotypes are correctly maintained and up to date.
Consult Documentation:
- Refer to SAP documentation or help resources for additional guidance on handling retroactive accounting dates and infotype configurations.
Testing:
- After making the necessary changes, run a test payroll to ensure that the error is resolved and that payroll processing can proceed without issues.
Related Information:
If the issue persists after following these steps, it may be necessary to consult with an SAP HR expert or your organization's SAP support team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
HRPAYDEPF320
Garnishment &1/&2: Difference seizable amount (&3) exists in period &4
What causes this issue? The repaid amount of the garnishment (&v1&/&v2&) changes in the period &v4& during the cleanup. At th...
HRPAYDEPF319
Update is not permitted during payroll for payroll area &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYDEPF322
Periods with the status "To Check" saved
What causes this issue? The periods in which a relevant difference is marked with a "P" have been saved to database table P01PF_PFBB_DIR. T...
HRPAYDEPF323
Cannot update "To Check" periods if status &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.