How To Fix HRGB_PAE029 - Infotype 0071 update conflict. Both NEW_ENDDA and DELETE were filled

SAP Error Message - Details

• Message type: E = Error

• Message class: HRGB_PAE - HR: Messages for pension auto enrolment

• Message number: 029

• Message text: Infotype 0071 update conflict. Both NEW_ENDDA and DELETE were filled

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRGB_PAE029 - Infotype 0071 update conflict. Both NEW_ENDDA and DELETE were filled ?

  The SAP error message HRGB_PAE029 indicates an update conflict in Infotype 0071 (which is related to the "Flexible Benefits" infotype) due to both the NEW_ENDDA (new end date) and the DELETE flag being filled at the same time. This situation typically arises when there is an attempt to update an employee's benefits record in a way that conflicts with the existing data.
  
  Cause:
  
  Conflicting Data: The error occurs because the system is trying to process a record that has both a new end date and a delete operation specified. This is logically inconsistent because if you are deleting a record, you should not also be trying to set a new end date for it.
  Concurrent Updates: There may be concurrent updates happening on the same infotype for the same employee, leading to conflicts.
  Incorrect Logic in Custom Code: If there is any custom code or enhancement that manipulates Infotype 0071, it may not be