How To Fix HRPAYAT_3670026 - At least one ELDA notification already exists for &1 &2

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAYAT_3670 - Insured Person Notif. Infotype 3670 (SI Notif. Suppl. A)

• Message number: 026

• Message text: At least one ELDA notification already exists for &1 &2

What causes this issue?

You want to create a new infotype record.

System Response

However, the SAP system returns the message that a data record already
exists for the required subtype and date and a message has been
transferred to ELDA for this data record.
This note only occurs if you have transferred an ELDA record to the
wrong SI agency by mistake in the past, such as submitting a reg
istration to the BVA, although the GKK would have been the correct SI
agency.

How to fix this error?

Create a reversal data record (such as <ZK>Cancel Registration</>) which
is sent to the SI agency entered by mistake.
Then create a data record (such as registration) that displays the
correct SI agency and the same start date as in the reverse record.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPAYAT_3670026 - At least one ELDA notification already exists for &1 &2 ?

  The SAP error message HRPAYAT_3670026 indicates that there is an issue related to the ELDA (Electronic Notification of Employment Data) notifications in the context of payroll processing. Specifically, the message states that at least one ELDA notification already exists for the specified employee (indicated by &1 and &2, which typically represent the employee's ID and the relevant period).
  Cause:
  The error usually occurs when:
  
  An attempt is made to create a new ELDA notification for an employee for a period where a notification has already been submitted.
  There may be a duplicate submission or an attempt to process an ELDA notification that overlaps with an existing one.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Existing Notifications:
  
  Use transaction codes like PA20 or PA30 to check the employee's records and see if there are existing ELDA notifications for the specified period.
  Look for any notifications that may have been submitted previously.
  
  
  
  Review ELDA Submission:
  
  If a notification already exists, determine if it is correct and if it needs to be modified or canceled.
  If the existing notification is valid, you may need to wait until the next period to submit a new notification.
  
  
  
  Modify or Cancel Existing Notification:
  
  If the existing notification is incorrect or needs to be updated, you may need to cancel it and then create a new one.
  Use the appropriate transaction codes to modify or delete the existing notification.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to ELDA notifications for any specific guidelines or updates that may apply to your version of SAP.
  
  
  
  Contact Support:
  
  If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting SAP Notes for further assistance.
  
  
  
  Related Information:
  
  ELDA Notifications: These are used in the context of payroll to report employment data electronically to the relevant authorities.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as PA20 (Display HR Master Data), PA30 (Maintain HR Master Data), and others that may be used for managing employee records and notifications.
  SAP Notes: Check for any SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.