How To Fix IDCN118 - Changes were not saved

SAP Error Message - Details

• Message type: E = Error

• Message class: IDCN -

• Message number: 118

• Message text: Changes were 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 IDCN118 - Changes were not saved ?

  The SAP error message IDCN118, which states "Changes were not saved," typically occurs when there is an issue with saving changes in the system. This can happen in various contexts, such as when trying to save data in a transaction, customizing settings, or updating master data. Here are some common causes, potential solutions, and related information:
  Causes:
  
  Authorization Issues: The user may not have the necessary permissions to make changes to the data or configuration.
  Data Validation Errors: The data being entered may not meet the required validation rules, leading to a failure in saving.
  Technical Errors: There may be a temporary technical issue with the SAP system, such as a database lock or connectivity problem.
  Incomplete Data: Required fields may be missing or incorrectly filled out, preventing the save operation.
  Custom Code Issues: If there are custom enhancements or user exits, they may be causing the error during the save process.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the action. This can be verified by checking the user roles and permissions in the SAP system.
  Review Input Data: Double-check the data being entered for completeness and correctness. Ensure that all mandatory fields are filled out and that the data adheres to the required formats.
  Check for System Issues: Look for any system messages or logs that might indicate a technical issue. You can check transaction codes like SM21 (System Log) or ST22 (Dump Analysis) for any relevant errors.
  Retry the Operation: Sometimes, simply retrying the operation after a short period can resolve temporary issues.
  Consult with Technical Support: If the issue persists, it may be necessary to involve your SAP Basis or technical support team to investigate further, especially if custom code is involved.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that can help diagnose issues, such as SE80 (Object Navigator) for checking custom code or SE37 (Function Module) for analyzing function modules.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide patches and updates.
  Documentation: Review SAP documentation or help files related to the specific module or transaction where the error occurred for additional context and troubleshooting steps.
  
  If you continue to experience issues, providing specific details about the context in which the error occurs can help in diagnosing the problem more effectively.