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 handling the logic correctly, leading to this conflict.
  
  Solution:
  
  Review the Data: Check the data being passed to the infotype update. Ensure that you are not trying to set both a new end date and a delete flag at the same time. You should choose one action based on your business requirement.
  Adjust the Logic: If you are using custom code, review the logic to ensure that it correctly handles the scenarios for updating or deleting records without causing conflicts.
  Check for Concurrent Updates: Ensure that there are no other processes or transactions that are trying to update the same infotype for the same employee at the same time.
  Use Transaction Codes: If you are using transaction codes to update the infotype, ensure that you are using the correct transaction for the intended operation (e.g., PA30 for maintaining infotypes).
  Testing: After making changes, test the updates in a development or quality environment to ensure that the issue is resolved before moving to production.
  
  Related Information:
  
  Infotype 0071: This infotype is used for managing flexible benefits in SAP HR. Understanding its structure and how it interacts with other infotypes can help in troubleshooting.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide guidance on handling Infotype 0071 updates.
  Transaction Codes: Familiarize yourself with transaction codes like PA30 (Maintain HR Master Data) and PA40 (Personnel Actions) for managing employee data.
  Debugging: If the issue persists, consider debugging the program or transaction that is causing the error to identify where the conflicting data is being set.
  
  By addressing the conflicting data and ensuring that only one action (either update or delete) is being performed at a time, you should be able to resolve the HRGB_PAE029 error.