How To Fix FDT_TRACE_INFO365 - Saving trace data not possible due to versioning status; see long text

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_TRACE_INFO - Messages to enrich traces with additional info

• Message number: 365

• Message text: Saving trace data not possible due to versioning status; see long text

What causes this issue?

After execution of the current function, the application has tried to
save the trace data that the system has recorded. However, there is at
least one object involved that is currently not under version control.
Therefore, the trace data cannot be saved.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

If saving the trace data is crucial for you, make sure that versioning
is turned on for all objects that are involved in the function
execution. To accomplish this, choose one of the following alternatives:
Starting from the function to be executed, drill down the entire
hierarchy of dependent objects and make sure that each of these objects
has versioning set on. This approach is recommended only for simple and
straightforward scenarios with a relatively small number of objects
involved.
Temporarily enforce versioning for the current BRFplus application. When
you choose this setting, the system offers to set versioning on not only
for all objects that are newly created, but also for all objects that
already exist in the application.
This approach guarantees that all objects are under version control.
However, it also has the drawback of usually putting much more objects
under version control than you really need. We therefore recommend to
use this option carefully, and to reset the application's versioning
setting to its previous state once the trace has been written.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FDT_TRACE_INFO365 - Saving trace data not possible due to versioning status; see long text ?

  The SAP error message FDT_TRACE_INFO365 indicates that there is an issue with saving trace data due to the versioning status of the data. This error typically occurs in the context of the SAP Fiori or SAP S/4HANA environments, particularly when dealing with the FDT (Field Data Tool) or similar functionalities.
  Cause:
  The error is usually caused by one of the following reasons:
  
  Versioning Status: The object you are trying to save trace data for may be in a versioning state that does not allow for changes or updates. This can happen if the object is locked, in a transport request, or if it is in a state that does not permit modifications.
  Authorization Issues: The user may not have the necessary authorizations to save or modify the trace data.
  Technical Issues: There may be underlying technical issues with the system, such as database locks or inconsistencies in the data.
  
  Solution:
  To resolve the issue, you can try the following steps:
  
  
  Check Versioning Status:
  
  Verify the versioning status of the object you are working with. Ensure that it is not locked or in a transport request.
  If it is locked, you may need to wait until it is released or contact the administrator to unlock it.
  
  
  
  Review Authorizations:
  
  Ensure that your user account has the necessary authorizations to save trace data. You may need to consult with your SAP security team to verify your roles and permissions.
  
  
  
  Check for Technical Issues:
  
  Look for any database locks or inconsistencies that may be affecting the ability to save data. You can use transaction codes like SM12 (to check for locks) and SM21 (to check system logs) to investigate further.
  If you find any issues, you may need to resolve them or contact your SAP Basis team for assistance.
  
  
  
  Consult Long Text:
  
  The error message suggests checking the long text for more details. You can do this by navigating to the error message in the SAP GUI and viewing the long text for additional context or specific instructions.
  
  
  
  System Restart:
  
  In some cases, a simple restart of the application or the SAP system may resolve temporary issues.
  
  
  
  SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates available that can resolve the issue.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE80 (Object Navigator), SE37 (Function Module), and SE11 (Data Dictionary) for further investigation.
  SAP Community: Consider searching or posting in the SAP Community forums for additional insights from other users who may have encountered the same issue.
  Documentation: Review SAP documentation related to the FDT and versioning to understand how it works and any best practices for managing trace data.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.