How To Fix MDG_HDB_SEARCH070 - Data has been changed; save the data first and then generate

SAP Error Message - Details

• Message type: E = Error

• Message class: MDG_HDB_SEARCH -

• Message number: 070

• Message text: Data has been changed; save the data first and then generate

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 MDG_HDB_SEARCH070 - Data has been changed; save the data first and then generate ?

  The SAP error message MDG_HDB_SEARCH070 typically occurs in the context of SAP Master Data Governance (MDG) when there is an attempt to generate or save data that has been modified but not yet saved. This error indicates that the system has detected changes in the data that need to be saved before proceeding with the generation process.
  Cause:
  
  Unsaved Changes: The most common cause of this error is that the user has made changes to the data in the MDG application but has not saved those changes. The system requires that all changes be saved before any further actions can be taken.
  Concurrent Modifications: Another possible cause could be that another user or process has modified the same data, leading to a conflict that needs to be resolved.
  Session Timeout: If the session has timed out, the system may not recognize the current state of the data, leading to this error.
  
  Solution:
  
  Save Changes: The immediate solution is to save any changes made to the data. Look for a "Save" button or option in the application and ensure that all modifications are saved before attempting to generate or perform any other actions.
  Refresh the Data: If you suspect that the data has been changed by another user, refresh the data in the application to ensure you are working with the most current version. After refreshing, you can reapply your changes if necessary and then save.
  Check for Locks: If the error persists, check if there are any locks on the data that might be preventing you from saving. You can use transaction codes like SM12 to check for locks.
  Review Change Logs: If applicable, review the change logs to see if there are any recent modifications made by other users that could be causing the conflict.
  Session Management: If you suspect a session timeout, log out and log back in to the system to reset your session.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MDG_MAT (for material master data) or MDG_BP (for business partner data) depending on the context of your work.
  SAP Notes: Check for any SAP Notes related to the MDG_HDB_SEARCH070 error for specific patches or updates that may address known issues.
  Documentation: Refer to the official SAP documentation for Master Data Governance for best practices on data management and error handling.
  Support: If the issue persists after trying the above solutions, consider reaching out to your SAP support team or consulting the SAP Community for further assistance.
  
  By following these steps, you should be able to resolve the MDG_HDB_SEARCH070 error and continue with your work in SAP MDG.