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: 320
Message text: Garnishment &1/&2: Difference seizable amount (&3) exists in period &4
The repaid amount of the garnishment (&v1&/&v2&) changes in the period
&v4& during the cleanup. At the same time, the seizable amount changes
by &v3& EUR. In constrast to message 309, the amount of the change is
smaller than or equal to the limit amount <LS>A_PFBB_MAX</>.
The limit amount <LS>A_PFBB_MAX</> is to be defined so that it
corresponds to the amount up to which a change of the seizable amount is
to be tolerated.
This is only an information message and has no effect on the status of
the personnel number.
You can specify the limit amounts. See the report documentation.
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.
HRPAYDEPF320
- Garnishment &1/&2: Difference seizable amount (&3) exists in period &4 ?The SAP error message HRPAYDEPF320 typically relates to garnishments in payroll processing. This error indicates that there is a discrepancy in the seizable amount for a garnishment during a specific payroll period. Here’s a breakdown of the components of the error message and potential solutions:
Cause:
Seizable Amount Discrepancy: The error suggests that the seizable amount for the garnishment (the amount that can be legally withheld from an employee's wages) does not match the expected amount for the specified period. This could be due to:
- Incorrect configuration of garnishment rules.
- Changes in the employee's salary or deductions that were not properly accounted for.
- Manual entries or adjustments that have created inconsistencies.
Payroll Processing Issues: If there were changes in the employee's payroll data (like salary changes, bonuses, or other deductions) that were not reflected in the garnishment calculations, this could lead to discrepancies.
Data Entry Errors: Mistakes in entering garnishment amounts or related payroll data can also trigger this error.
Solution:
Review Garnishment Configuration: Check the configuration settings for the garnishment in the SAP system. Ensure that the rules and limits are set correctly according to legal requirements and company policies.
Check Employee Payroll Data: Review the employee's payroll data for the period in question. Look for any changes in salary, deductions, or other relevant factors that could affect the seizable amount.
Adjust Payroll Results: If discrepancies are found, you may need to adjust the payroll results for the affected period. This could involve recalculating the payroll or making manual adjustments to the garnishment amounts.
Consult Legal Guidelines: Ensure that the garnishment calculations comply with local laws and regulations. If necessary, consult with legal or compliance teams to verify that the garnishment amounts are correct.
Run Payroll Simulation: Before finalizing payroll, run a simulation to check for any discrepancies in garnishment calculations. This can help identify issues before they affect actual payroll processing.
Contact SAP Support: If the issue persists and cannot be resolved through the above steps, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration or updates.
Related Information:
By following these steps, you should be able to identify the cause of the HRPAYDEPF320 error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
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...
HRPAYDEPF318
Update not permitted during check of current cleanup
What causes this issue? The garnishment results were cleaned up in the current payroll period and were fixed by the productive payroll that already t...
HRPAYDEPF321
Set earliest personal retroactive accounting date (infotype 0003) to &1
What causes this issue? A cleanup of the personnel number is necessary. As payroll cannot be run for the employee due to the employee leaving the com...
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...
Click on this link to search all SAP messages.