How To Fix FDT_CORE026 - Name changed for a transported application.

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 026

• Message text: Name changed for a transported application.

What causes this issue?

You are changing the name of a BRFplus application, that has already
been transported into other systems. A renamed BRFplus application may
have unintended side effects in the target systems, that should be taken
care of.

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?

Before you save and eventually transport the application with a new
name, you should ensure that the application is not referred to by its
name elsewhere outside BRFplus, including different software layers.
Only references by the application UUID (which does not change) are
stable.
It is strongly recommended to adjust references by name and transport
the required adaptations together with the renamed BRFplus application.
Also authorization objects like FDT_OBJECT and FDT_TRACE take the
application name into account and might need to be adjusted.

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_CORE026 - Name changed for a transported application. ?

  The SAP error message FDT_CORE026 indicates that there has been a change in the name of a transported application. This typically occurs in the context of SAP Fiori or SAP UI5 applications when there are discrepancies between the application names in the transport request and the target system.
  Cause:
  
  Name Change: The application name was changed in the source system after the transport request was created, but the transport request still references the old name.
  Transport Issues: The transport request may not have been properly updated or synchronized with the latest changes in the application.
  Version Mismatch: The version of the application in the target system does not match the version in the source system.
  
  Solution:
  
  Check Transport Request: Review the transport request to ensure that it includes the latest version of the application with the correct name.
  Recreate Transport Request: If the application name has changed, you may need to recreate the transport request to include the updated application name.
  Adjust Application Name: If the application name was changed intentionally, ensure that all references to the old name are updated in the source system before transporting.
  Manual Adjustment: In some cases, you may need to manually adjust the application name in the target system to match the source system.
  Clear Cache: Clear the cache in the target system to ensure that any old references are removed.
  
  Related Information:
  
  Transport Management System (TMS): Familiarize yourself with how transports work in SAP, including how to manage and track changes.
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or fixes related to this error.
  Documentation: Review the SAP Fiori or SAP UI5 documentation for best practices on managing application names and transports.
  Version Control: Implement version control practices to keep track of changes made to applications, which can help prevent such issues in the future.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.