How To Fix HRPAY00DME025 - Payment run still not executed from preliminary period

HRPAY00DME025 - Overview

• Message type: E = Error

• Message class: HRPAY00DME - Messages for the data medium exchange preliminary program

• Message number: 025

• Message text: 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:
Period &v2& (period modifier &v1&).

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

The personnel number is rejected.

How to fix this error?

Presumably, the cause of the error is: The <ZH>collective bank transfer
DME preliminary program</> was not started at all or not started for all
personnel numbers in period &v2& (period modifier &v1&).
The collective bank transfers must be processed from the previous
periods before the payment run can be executed for the current period.
Start the <ZH>collective bank transfer DME preliminary program</> if
necessary for the period(s) that have still not been processed before
you repeat the current run.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPAY00DME025 - Payment run still not executed from preliminary period ?

  The SAP error message HRPAY00DME025 indicates that a payment run has not been executed for a preliminary period in the payroll process. This error typically arises in the context of payroll processing in SAP HR (Human Resources) and can be related to various issues in the payroll configuration or execution.
  
  Cause:
  
  
  Preliminary Payroll Not Executed: The most common cause is that the preliminary payroll run has not been executed for the specified period. The system requires that a preliminary payroll run is completed before executing the actual payment run.
  
  
  Incorrect Configuration: There may be issues with the payroll configuration settings, such as incorrect period settings or missing payroll schemas.
  
  
  Missing Authorization: The user executing the payment run may not have the necessary authorizations to access the payroll data.
  
  
  Data Issues: There may be inconsistencies or errors in the employee master data or payroll results that prevent the payment run from being executed.
  
  
  
  Solution:
  
  
  Execute Preliminary Payroll: Ensure