How To Fix FDT_CHANGE_INFO586 - Log Persistence was set

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 586

• Message text: Log Persistence was set

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_INFO586 - Log Persistence was set ?

  The SAP error message FDT_CHANGE_INFO586 indicates that "Log Persistence was set." This message typically arises in the context of the SAP Fiori Design Time (FDT) or when working with the Fiori elements and UI5 applications. It suggests that the logging mechanism for changes made to the data is enabled, which can affect performance and data handling.
  Cause:
  
  Log Persistence Setting: The error is triggered when the log persistence feature is enabled in the system. This feature is used to keep a record of changes made to the data, which can be useful for auditing and tracking purposes.
  Configuration Issues: There may be a misconfiguration in the settings related to logging or persistence in the application or system.
  Performance Impact: Enabling log persistence can lead to performance issues, especially if the volume of changes is high.
  
  Solution:
  
  
  Disable Log Persistence: If log persistence is not required for your application, you can disable it. This can typically be done in the application configuration settings or through the relevant transaction codes in SAP.
  
  Navigate to the relevant configuration area (e.g., transaction code SPRO) and look for settings related to logging or persistence.
  Change the setting to disable log persistence.
  
  
  
  Review Application Requirements: Assess whether you need log persistence for your application. If it is necessary for auditing or tracking, consider optimizing the logging mechanism instead of disabling it.
  
  
  Check for Updates: Ensure that your SAP system is up to date with the latest patches and updates, as newer versions may have improvements or fixes related to logging and performance.
  
  
  Consult Documentation: Refer to the official SAP documentation or help portal for specific instructions related to your version of SAP and the Fiori applications you are using.
  
  
  Contact SAP Support: If the issue persists or if you are unsure about making changes, consider reaching out to SAP support for assistance.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide guidance on log persistence settings.
  Performance Monitoring: If log persistence is enabled, monitor the performance of your application to ensure that it is not adversely affected.
  Audit Requirements: If your organization has specific audit requirements, ensure that any changes to logging settings comply with those requirements.
  
  By following these steps, you should be able to address the FDT_CHANGE_INFO586 error and manage log persistence effectively in your SAP environment.