How To Fix /SAPAPO/MD357 - Changes not saved

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/MD -

• Message number: 357

• Message text: Changes not saved

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 /SAPAPO/MD357 - Changes not saved ?

  The SAP error message /SAPAPO/MD357 Changes not saved typically occurs in the context of SAP Advanced Planning and Optimization (APO) when there are issues related to saving changes made in the planning book or during the planning process. Here are some common causes, potential solutions, and related information for this error:
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to save changes in the planning book.
  Locking Issues: Another user might be editing the same data, leading to a lock that prevents saving.
  Data Consistency Errors: There may be inconsistencies in the data that prevent the system from saving changes.
  Technical Errors: System or network issues could interrupt the saving process.
  Incorrect Configuration: The planning book or data view may not be configured correctly, leading to issues when trying to save changes.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to make changes in the planning book. This can be done by checking the user roles and authorizations in the SAP system.
  Release Locks: If another user is editing the same data, wait for them to finish or coordinate with them to release the lock. You can also check for locks using transaction SM12.
  Validate Data: Review the data being changed for any inconsistencies or errors. Ensure that all required fields are filled out correctly.
  Technical Troubleshooting: If the issue seems to be technical, check for any system messages or logs that might indicate a problem. You can also try logging out and back in or restarting the session.
  Configuration Review: Review the configuration of the planning book and data views to ensure they are set up correctly. This may involve checking the settings in transaction /SAPAPO/MC62 for planning books.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide patches.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/MC62 (for planning book configuration) and /SAPAPO/MDP1 (for planning book maintenance).
  SAP Documentation: Refer to the official SAP documentation for APO for detailed information on planning books and data management.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical support team for further investigation.