How To Fix FDT_CORE363 - Message log action &1 has deviating log settings

FDT_CORE363 - Overview

• Message type: E = Error

• Message class: FDT_CORE - Formula & Derivation Tool: Core

• Message number: 363

• Message text: Message log action &1 has deviating log settings

What causes this issue?

The application's default log setting deviates from the respective
setting of message log action &v1& . In addition, you have chosen that
the new application default setting shall be mandatory for all message
log actions of the application. Therefore, all existing message log
actions of the application must be adapted to the new default setting.

System Response

The application cannot be activated.

How to fix this error?

INCLUDE FDT_LOG_MISMATCH OBJECT DOKU ID TX

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

FDT_CORE363 - Details

• The SAP error message FDT_CORE363 indicates that there is a discrepancy in the logging settings for a specific action in the context of the SAP Fiori Design Time (FDT) framework. This error typically arises when the logging configuration for an action does not match the expected settings, which can lead to issues in tracking or auditing actions performed within the system.
  
  Cause:
  The error can be caused by several factors, including:
  
  Inconsistent Logging Settings: The action specified in the error message has logging settings that differ from the expected configuration. This could be due to manual changes or misconfigurations.
  System Updates or Changes: Recent updates or changes to the system might have altered the logging settings, leading to this inconsistency.
  Custom Development: If there are custom developments or enhancements in the system, they might not adhere to the standard logging practices, causing this error.
  
  
  Solution:
  To resolve the FDT_CORE363 error, you can follow these steps:
  
  
  Check Logging Configuration:
  
  Navigate