Do you have any question about this error?
Message type: E = Error
Message class: HRPAY00DME - Messages for the data medium exchange preliminary program
Message number: 026
Message text: Payment run & & is already reserved
A payment run with date &v1& and run ID &v2& has been entered in table
REGUV.
The processing is aborted since no payment run can be performed.
Several data medium exchange preliminary programs (single or collective
bank transfer) can be started in parallel.
Repeat the current run.
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.
HRPAY00DME026
- Payment run & & is already reserved ?The SAP error message HRPAY00DME026, which states "Payment run & & is already reserved," typically occurs in the context of payroll processing when there is an attempt to execute a payment run that has already been reserved or processed. This can happen for various reasons, such as duplicate attempts to process the same payroll run or issues with the configuration of the payroll system.
Causes:
- Duplicate Payment Run: The payment run you are trying to execute has already been processed or reserved in the system.
- Incorrect Configuration: There may be issues with the configuration settings in the payroll module that prevent the payment run from being executed.
- User Error: A user may have inadvertently attempted to run the payment process multiple times.
- System Lock: The payment run may be locked due to ongoing processes or transactions that are still being completed.
Solutions:
- Check Payment Run Status: Verify the status of the payment run in the system. You can do this by navigating to the relevant transaction (e.g., PC00_MXX_PY) and checking if the payment run is already completed or reserved.
- Release or Delete Reservation: If the payment run is reserved but not yet completed, you may need to release or delete the reservation. This can typically be done through the payroll transaction codes or by using the appropriate administrative functions.
- Consult Logs: Review the payroll logs for any errors or warnings that may provide additional context on why the payment run is reserved.
- Check for Locks: Ensure that there are no locks on the payment run that could be preventing it from being processed. This may involve checking for other users or processes that are currently accessing the same data.
- Contact Support: If the issue persists and you cannot resolve it, consider reaching out to your SAP support team or consulting the SAP Help Portal for further assistance.
Related Information:
By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
HRPAY00DME025
Payment run still not executed from preliminary period
What causes this issue? A predecessor event was found in a retroactive accounting period with unstamped BT entries for a collective bank transfer: Pe...
HRPAY00DME024
Incorrect country grouping: & instead of &
What causes this issue? The report can only process personnel numbers with one country grouping within a run. The first processed personnel number ha...
HRPAY00DME027
No authorization for reading the payroll results
What causes this issue? There is no authorization available for reading the payroll results with sequence number &v1&.System Response The pe...
HRPAY00DME028
Error when reading the payroll results
What causes this issue? The payroll result with the sequence number &v1& could not be read. The function module PYXX_READ_PAYROLL_RESULT deli...
Click on this link to search all SAP messages.