How To Fix SO785 - No entries were changed, added or deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: SO - SAPoffice: message texts

• Message number: 785

• Message text: No entries were changed, added or deleted

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 SO785 - No entries were changed, added or deleted ?

  The SAP error message SO785 ("No entries were changed, added or deleted") typically occurs when you attempt to perform an operation that requires changes to be made to the database, but no actual changes are detected. This can happen in various contexts, such as when trying to save changes in a transaction or when executing a report that is expected to modify data.
  Causes:
  
  No Changes Made: The most common cause is that the user did not make any changes to the data before attempting to save or execute the operation.
  Data Already Exists: If you are trying to add a new entry that already exists, the system may not recognize it as a new entry.
  Validation Errors: There may be validation rules that prevent the changes from being accepted, leading to no changes being recorded.
  Authorization Issues: Lack of proper authorization to make changes can also lead to this error.
  Incorrect Selection Criteria: If the selection criteria for a report or transaction do not match any records, the system may not find any entries to change.
  
  Solutions:
  
  Check for Changes: Ensure that you have made actual changes to the data before saving. If you are trying to add a new entry, verify that the data is indeed new and does not already exist.
  Review Data: Double-check the data you are trying to modify or add. Make sure it meets all necessary criteria and does not violate any constraints.
  Authorization Check: Ensure that you have the necessary permissions to perform the operation. If not, contact your system administrator to obtain the required authorizations.
  Validation Rules: Review any validation rules that may be in place. If your changes are being rejected due to validation, you may need to adjust your input accordingly.
  Debugging: If you are a developer or have access to debugging tools, you can trace the execution of the transaction to identify where the process is failing.
  
  Related Information:
  
  Transaction Codes: Depending on the context of the error, you may be working with specific transaction codes (e.g., SE11 for data dictionary, SE80 for development objects).
  SAP Notes: Check SAP Notes for any known issues related to the specific transaction or module you are working with. SAP frequently updates its knowledge base with solutions to common problems.
  User Forums: Consider searching or posting on SAP community forums or user groups for additional insights from other users who may have encountered the same issue.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP support team or a technical consultant for further assistance.