How To Fix FDT_CHANGE_INFO664 - External identification was set to hidden for the application

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 664

• Message text: External identification was set to hidden for the application

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_INFO664 - External identification was set to hidden for the application ?

  The SAP error message FDT_CHANGE_INFO664 indicates that the external identification for a specific application has been set to hidden. This typically occurs in the context of SAP Fiori or SAP UI5 applications where the external identification is used for various purposes, such as integration with external systems or for tracking purposes.
  Cause:
  
  Configuration Settings: The external identification might have been intentionally set to hidden in the application configuration settings. This could be due to security reasons or to prevent unnecessary exposure of certain identifiers.
  Development Changes: Changes made during the development or customization of the application could lead to this setting being altered.
  Transport Issues: If the application was transported from one system to another (e.g., from development to production), the transport might not have included the necessary settings or configurations.
  
  Solution:
  
  Check Application Configuration: Review the configuration settings of the application in the SAP Fiori Launchpad or the relevant development environment. Ensure that the external identification is set to visible if it is required for your use case.
  Modify the Application: If you have access to the application code, you can modify the relevant parts to change the visibility of the external identification. This may involve adjusting the XML or JavaScript files associated with the application.
  Consult Documentation: Refer to the SAP documentation or help resources for guidance on how to manage external identification settings in your specific application context.
  Transport Management: If the issue arose after a transport, check the transport logs and ensure that all necessary objects and configurations were included in the transport request.
  Contact SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP support for assistance. They can provide insights based on the specific version and configuration of your SAP system.
  
  Related Information:
  
  SAP Fiori and UI5 Documentation: Review the official SAP documentation for Fiori and UI5 applications, which often includes best practices for configuration and troubleshooting.
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can share their solutions.
  System Logs: Check the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.