How To Fix HRPAYDEE2025 - Deregistr. for key date &1 not possible due to more recent notification

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAYDEE2 - Message Class ELStAM Procedure

• Message number: 025

• Message text: Deregistr. for key date &1 not possible due to more recent notification

What causes this issue?

While analyzing the master data it was determined that the employee
needs to be deregistered for the key date &V1&. However, since there has
already been a registration or deregistration for a more recent date,
the deregistration for &V1& cannot be performed automatically.

System Response

The deregistration for &V1& is created with the status 'With Errors' and
is not transferred to the clearing house using the subsequent report
<DS:RE.RPCE2SD0_OUT>Collect Registrations and Deregistrations (Report
RPCE2SD0_OUT)</>.

How to fix this error?

Check if the notification must be manually forced using the relevant
special processing in infotype Tax Data D (IT0012) at a later key date.

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

<ZH>Example 1 - No To-Do:</>
You register an employee for the ELStAM procedure as the main employer
as of January 1, yyyy. The clearing house responds to your request with
procedural note 552020200 - No authorization to register -. Tax class 6
is then entered in IT0012 in the system. You can use <ZK>Special
Processing Registration </>in IT0012 with specification <ZK>Force</> to
create another registration as the main employer as of February 1, yyyy.
The clearing house responds to this. This means that tax class 6 is
entered in IT0012 from January 1, yyyy to January 31, yyyy, and tax
class 1-5 is entered as of February 1, yyyy. During the next run of
notification creator <DS:RE.RPCE2VD0_OUT>ELSTAM: Create Registrations
and Deregistrations</>(RPCE2VD0_OUT), this determines that there was a
change from secondary employer to main employer as of February 1, yyyy.
This would make a deregistration and registration necessary. The system
tries to create a deregistration as of January 31, yyyy but recognizes
that the employment relationship of the employee has already been
successfully registered as a main employment relationship as of February
1, yyyy. The deregistration is, therefore, created with the status With
Errors and no further manual creation of notifications is necessary.
<ZH>Example 2 - Manual Creation of Notifications is Necessary:</>
An employee is active in your company from January 1, yyyy to January
15, yyyy. You register the employee for the ELStAM procedure as of
January 1, yyyy an, however the clearing house responds to the
registration with procedural note 552020214 - Registration after period
of grace, new ref. date ER for current employment. [Ref. date ER =
January 31, yyyy] -. The deregistration as of January 15, yyyy is
created again during the next run of the notification creator by the
changes of SAP Note 2579717 using the ref. date ER returned by the
clearing house. The report recognizes from this registration that there
is a more up-to-date notification. The deregistration would be rejected
by the clearing house as there is no longer any employment relationship
registered for the employee as of January 15, yyyy. This means that the
deregistration is created with the status With Errors. To deregister the
employment relationship again, IT0012 must be delimited accordingly with
special processing Deregistration and specification Force (delimitation
as of January 31, yyyy).
You can use <DS:RE.RPUE2ED0>ELStAM: Check Tool to Check Notification
Data</> to check if the notification data is correct.

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 HRPAYDEE2025 - Deregistr. for key date &1 not possible due to more recent notification ?

  The SAP error message HRPAYDEE2025 indicates that a deregistration for a specific key date cannot be processed because there is a more recent notification that conflicts with the deregistration request. This typically occurs in the context of payroll or personnel administration when trying to deregister an employee or a specific event related to their employment.
  Cause:
  
  Recent Notification: The primary cause of this error is that there is a more recent notification (such as a change in employment status, a new payroll run, or an update to personal data) that has been recorded in the system after the key date you are trying to deregister.
  Data Consistency: SAP enforces data consistency, and if there are changes that affect the employee's status or payroll after the key date, it prevents deregistration to avoid inconsistencies.
  
  Solution:
  
  Check Notifications: Review the notifications or changes made to the employee's record after the key date. You can do this by checking the infotypes related to the employee (e.g., infotype 0000 for actions, infotype 0001 for organizational assignment, etc.).
  Adjust Key Date: If possible, adjust the key date for the deregistration to a date that is before the most recent notification.
  Remove Conflicting Notifications: If the recent notification is not valid or needs to be changed, you may need to reverse or adjust that notification before attempting the deregistration again.
  Consult with HR or Payroll Team: If you are unsure about the changes or how to proceed, consult with your HR or payroll team to ensure that you are following the correct procedures and that the data is accurate.
  
  Related Information:
  
  Infotypes: Familiarize yourself with the relevant infotypes that may be involved in the deregistration process, such as:
  
  Infotype 0000 (Actions)
  Infotype 0001 (Organizational Assignment)
  Infotype 0002 (Personal Data)
  
  
  Transaction Codes: Use transaction codes like PA20 (Display HR Master Data) or PA30 (Maintain HR Master Data) to view and manage employee records.
  SAP Notes: Check for any relevant SAP Notes or documentation that may provide additional insights or updates regarding this error message.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.