How To Fix FDT_CHANGE_INFO044 - The message log was made non-persistent

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_CHANGE_INFO - FDT: Changes info in object for different versions

• Message number: 044

• Message text: The message log was made non-persistent

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 FDT_CHANGE_INFO044 - The message log was made non-persistent ?

  The SAP error message FDT_CHANGE_INFO044 indicates that the message log has been made non-persistent. This typically occurs in the context of the SAP Fiori Design Time (FDT) or when working with the Fiori elements and UI5 applications. The message log is used to capture messages, warnings, and errors during the execution of certain processes, and making it non-persistent means that the messages will not be saved for future reference.
  Cause:
  The primary cause of this error message is usually related to the configuration or state of the message log within the application. It can occur due to:
  
  Configuration Settings: The system may be configured to not retain logs for certain operations, leading to non-persistent message logs.
  Application Logic: The application logic may explicitly set the message log to be non-persistent based on certain conditions or user actions.
  Performance Considerations: In some cases, non-persistent logs are used to improve performance by reducing the amount of data stored in the system.
  
  Solution:
  To resolve the issue, consider the following steps:
  
  
  Check Configuration: Review the configuration settings related to message logging in your SAP system. Ensure that the settings allow for persistent logging if that is required for your use case.
  
  
  Review Application Code: If you have access to the application code, check if there are any explicit settings or conditions that lead to the message log being set as non-persistent. Adjust the logic if necessary.
  
  
  Consult Documentation: Refer to the SAP documentation for the specific application or module you are working with. There may be specific guidelines or settings that need to be adjusted.
  
  
  System Settings: If you are an administrator, check the system settings related to logging and message handling. Ensure that the system is configured to retain logs as needed.
  
  
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP support for assistance. They may provide insights specific to your system version or configuration.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide updates related to message logging.
  Fiori Elements Documentation: Review the official SAP Fiori Elements documentation for best practices regarding message handling and logging.
  Community Forums: Engage with the SAP Community or forums where other users may have encountered similar issues and can share their solutions.
  
  By following these steps, you should be able to address the FDT_CHANGE_INFO044 error and ensure that your message logs are handled as required.