How To Fix HRPAYDEE2025 - Abmeldung zum Stichtag &1 aufgrund aktuellerer Meldung nicht möglich

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAYDEE2 - Message Class ELStAM Procedure

• Message number: 025

• Message text: Abmeldung zum Stichtag &1 aufgrund aktuellerer Meldung nicht möglich

Was verursacht dieses Problem?

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.

Systemantwort

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)</>.

Wie behebe ich diesen Fehler?

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

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

<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.

Vorgehensweise für Systemadministratoren

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE