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
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.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
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.
Error message extract from SAP system. Copyright SAP SE.
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
Get instant SAP help. Sign up for our Free Essentials Plan.
FDT_TRACE_INFO357
Value of context data object &1 has been updated
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_TRACE_INFO356
Precondition not fulfilled, skip the processing of current rule
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_TRACE_INFO366
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FDT_TRACE_INFO370
Static method &2 of class &1 was called
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.