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: 318
Message text: Update not permitted during check of current cleanup
The garnishment results were cleaned up in the current payroll period
and were fixed by the productive payroll that already took place for
this period. However, since according to the control record the payroll
run is not yet completed it is only possible to check the garnishment
results again by taking into consideration the cleanup and payroll run
that was just performed. No update is possible because the current
payroll run is not yet completed and therefore no cleanup can be saved
yet for the next period.
The system does not save the data.
If you want to repeat the cleanup in the current payroll period that is
not yet completed, select the parameter <LS>Repetition of Cleanup</> on
the selection screen for report RPCPCAD0_EP_CHECK_UPDATE.
If you want to perform a cleanup for the current payroll period that is
not yet completed, end the payroll run by setting the control record
(transaction PA03) and start the cleanup report again.
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.
HRPAYDEPF318
- Update not permitted during check of current cleanup ?The SAP error message HRPAYDEPF318 typically occurs in the context of payroll processing in the SAP HR module. This error indicates that an update is not permitted during the check of the current cleanup process. Here’s a breakdown of the cause, potential solutions, and related information:
Cause:
Payroll Locking Mechanism: The error usually arises when there is an attempt to update payroll data while the system is in a state where it is performing cleanup operations. This can happen if the payroll run is still in progress or if there are pending processes that need to be completed before any updates can be made.
Data Consistency: SAP enforces data consistency during payroll processing. If the system detects that an update could compromise the integrity of the payroll data, it will prevent the update from occurring.
Concurrent Processes: If multiple users or processes are trying to access or modify payroll data simultaneously, it can lead to this error.
Solution:
Check Payroll Status: Ensure that the payroll run is complete and that there are no ongoing processes. You can check the status of the payroll run in the relevant transaction (e.g., PC00_MXX_CALC) to see if it is still processing.
Wait for Cleanup to Complete: If the system is currently performing cleanup operations, wait for these processes to finish before attempting to make any updates.
Review Lock Entries: Use transaction SM12 to check for any lock entries that might be preventing updates. If you find any locks that are no longer needed, you can delete them (with caution).
Check for Background Jobs: Use transaction SM37 to check for any background jobs related to payroll processing that might be running. If there are jobs that are stuck or taking too long, you may need to investigate further.
Consult with Basis Team: If the issue persists, it may be necessary to involve your SAP Basis team to check for any system-level issues or to perform a system restart if required.
Review Custom Code: If there are any custom enhancements or modifications in your payroll processing, review them to ensure they are not causing conflicts during the cleanup process.
Related Information:
SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error. There may be patches or updates that can resolve known issues.
Documentation: Review the SAP HR documentation for payroll processing to understand the workflow and any prerequisites for making updates during payroll runs.
Community Forums: Consider searching or posting in SAP community forums or SAP Community Network (SCN) for insights from other users who may have encountered similar issues.
By following these steps, you should be able to identify the cause of the HRPAYDEPF318 error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
HRPAYDEPF317
Update only possible with 'Rebuild for All In-Periods' option
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYDEPF316
The report is not currently released for general use
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
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...
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...
Click on this link to search all SAP messages.