How To Fix RSPLW036 - Unsaved changes have been discarded

SAP Error Message - Details

• Message type: E = Error

• Message class: RSPLW - Messages from planning modeler

• Message number: 036

• Message text: Unsaved changes have been discarded

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 RSPLW036 - Unsaved changes have been discarded ?

  The SAP error message RSPLW036: Unsaved changes have been discarded typically occurs in the context of SAP BW (Business Warehouse) when a user attempts to navigate away from a screen or transaction without saving changes made to a query or report. This message serves as a warning that any unsaved modifications will be lost.
  Cause:
  
  Unsaved Changes: The most common cause is that the user has made changes to a query, report, or other configuration settings but has not saved those changes before attempting to exit or navigate away.
  Session Timeout: If the session times out, any unsaved changes may be discarded automatically.
  Navigation: Attempting to navigate to another transaction or screen without saving changes can trigger this message.
  
  Solution:
  
  Save Changes: Before navigating away from the screen, ensure that you save any changes you have made. Look for a "Save" button or use the keyboard shortcut (usually Ctrl + S) to save your work.
  Review Changes: If you receive this message, check if you can return to the previous screen to save your changes before proceeding.
  Session Management: Be mindful of session timeouts. If you are working on a long task, consider saving your work periodically to avoid losing changes.
  Check for Locks: Sometimes, if another user has locked the object you are trying to save, you may not be able to save your changes. Ensure that no locks are preventing you from saving.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific issues related to your version of SAP BW that might provide additional context or solutions.
  User Training: Ensure that users are trained on the importance of saving changes and the implications of navigating away from screens without saving.
  System Configuration: Review system settings related to session timeouts and user permissions to ensure they align with your organization's workflow.
  
  If the problem persists or if you encounter this message frequently, it may be beneficial to consult with your SAP Basis or BW administrator for further investigation and support.