How To Fix RE659 - & entries were marked for deletion

SAP Error Message - Details

• Message type: E = Error

• Message class: RE - Earmarked funds

• Message number: 659

• Message text: & entries were marked for deletion

What causes this issue?

You have defined customer-specific or partner-specific fields using the
enhancement wizard and then later deleted these fields in the
corresponding append structures or customer includes again.
The append structures or customer includes may also possibly have been
completely deleted.

System Response

The system recognizes that the fields were deleted and issues the
number of fields deleted.

How to fix this error?

To avoid inconsistencies, you should <ZH>definitely</> regenerate the
corresponding charts or set them to "not active".

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RE659 - & entries were marked for deletion ?

  The SAP error message RE659 typically indicates that there are entries in the system that have been marked for deletion, which can affect various processes, such as reporting or data integrity. This message is often encountered in the context of Real Estate Management (RE) or other modules where data integrity is crucial.
  Cause of RE659 Error
  
  
  Marked for Deletion: The primary cause of this error is that certain entries (like contracts, objects, or master data) have been marked for deletion in the system. This means that these entries are no longer active and cannot be processed in certain transactions.
  
  
  Data Integrity Issues: The presence of marked-for-deletion entries can lead to inconsistencies in reporting or processing, as the system may attempt to access or manipulate data that is no longer valid.
  
  
  Configuration Issues: Sometimes, the configuration settings in the SAP system may lead to entries being marked for deletion inadvertently.
  
  
  Solution to RE659 Error
  
  
  Review Marked Entries: Check the entries that are marked for deletion. You can do this by using transaction codes like SE16 or SE16N to view the relevant tables (e.g., RE objects, contracts).
  
  
  Unmark Entries: If the entries should not be marked for deletion, you can unmark them. This typically involves changing the status of the entries in the relevant transaction or using a specific program designed to reverse the deletion flag.
  
  
  Data Cleanup: If the entries are indeed obsolete, consider cleaning up the data by permanently deleting them if they are no longer needed. Ensure that you have backups and that this action complies with your organization's data retention policies.
  
  
  Check Configuration: Review the configuration settings related to the data management processes in your SAP system. Ensure that there are no settings that are causing entries to be marked for deletion incorrectly.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific module you are working with for any additional guidance or known issues.
  
  
  Contact Support: If the issue persists or if you are unsure about the implications of unmarking entries, consider reaching out to SAP support or your internal SAP team for assistance.
  
  
  Related Information
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE16 (Data Browser), SE11 (Data Dictionary), and others that may help you analyze the data.
  SAP Notes: Check SAP Notes for any specific fixes or recommendations related to the RE659 error.
  Data Management Best Practices: Implement best practices for data management to prevent similar issues in the future, such as regular audits of marked-for-deletion entries.
  
  By following these steps, you should be able to address the RE659 error and manage entries marked for deletion effectively.