How To Fix MDC_GW_CUST013 - Save not possible: configuration has been modified in the meantime

SAP Error Message - Details

• Message type: E = Error

• Message class: MDC_GW_CUST - Customizing messages

• Message number: 013

• Message text: Save not possible: configuration has been modified in the meantime

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 MDC_GW_CUST013 - Save not possible: configuration has been modified in the meantime ?

  The SAP error message MDC_GW_CUST013, which states "Save not possible: configuration has been modified in the meantime," typically occurs in the context of the SAP Multi-Domain Configuration (MDC) or when working with the SAP Gateway. This error indicates that the configuration you are trying to save has been altered by another user or process since you last loaded it, leading to a conflict.
  Cause:
  
  Concurrent Modifications: Another user or process has made changes to the configuration after you loaded it but before you attempted to save it.
  Session Timeout: Your session may have timed out, and the system has refreshed the configuration, leading to discrepancies.
  Data Locking: The configuration might be locked by another transaction or user, preventing you from saving your changes.
  
  Solution:
  
  Refresh the Configuration: Reload the configuration to ensure you have the latest version. After refreshing, reapply your changes and try saving again.
  Check for Locks: Use transaction codes like SM12 to check for any locks on the configuration. If you find locks that are no longer needed, you can release them.
  Communicate with Other Users: If you are working in a collaborative environment, communicate with your team to ensure that no one else is making conflicting changes.
  Review Change Logs: If available, check the change logs to see what modifications were made and adjust your changes accordingly.
  Session Management: Ensure that your session is active and not timed out. If it has timed out, log back in and refresh the configuration.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MDC, SM12, and SM21 (for system logs) to help diagnose and resolve issues.
  User Authorizations: Ensure that you have the necessary authorizations to make changes to the configuration.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Documentation: Review the official SAP documentation for the specific module you are working with to understand the configuration process better.
  
  If the problem persists after trying the above solutions, consider reaching out to your SAP Basis or technical support team for further assistance.