How To Fix /UI2/FDM_2_CDM3038 - TM &1: Not Found

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FDM_2_CDM3 -

• Message number: 038

• Message text: TM &1: Not Found

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 /UI2/FDM_2_CDM3038 - TM &1: Not Found ?

  The SAP error message /UI2/FDM_2_CDM3038 TM &1: Not Found typically indicates that a specific object or resource that the system is trying to access cannot be found. This error is often related to the Fiori Launchpad or the Fiori Design Studio, and it may occur when trying to access a tile or application that is not properly configured or does not exist in the system.
  Possible Causes:
  
  Missing or Incorrect Configuration: The application or tile may not be properly configured in the Fiori Launchpad.
  Authorization Issues: The user may not have the necessary authorizations to access the application or tile.
  Transport Issues: The application may not have been transported correctly from the development environment to the production environment.
  Object Deletion: The object (like a catalog, group, or tile) may have been deleted or is not active.
  Backend Service Issues: The backend service that the Fiori application relies on may not be active or properly configured.
  
  Solutions:
  
  
  Check Configuration:
  
  Verify that the application or tile is correctly configured in the Fiori Launchpad.
  Ensure that the corresponding catalog and group are assigned to the user role.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the application. You can check this in transaction PFCG (Role Maintenance).
  
  
  
  Transport Verification:
  
  If the issue occurred after a transport, verify that all necessary objects were included in the transport request and that they were successfully imported.
  
  
  
  Object Status:
  
  Check if the object (tile, catalog, or group) exists and is active. You can do this in the Fiori Launchpad Designer.
  
  
  
  Backend Service Check:
  
  Ensure that the backend OData service is active and properly configured. You can check this in transaction /IWFND/MAINT_SERVICE to see if the service is registered and active.
  
  
  
  Clear Cache:
  
  Sometimes, clearing the browser cache or the SAP Gateway cache can resolve issues related to outdated information.
  
  
  
  Related Information:
  
  Fiori Launchpad Designer: Use this tool to manage tiles, catalogs, and groups.
  Transaction Codes:
  
  PFCG: Role Maintenance
  /IWFND/MAINT_SERVICE: OData Service Maintenance
  /UI2/FLP: Fiori Launchpad
  
  
  SAP Notes: Check for any relevant SAP Notes that might address known issues related to this error message.
  
  If the issue persists after trying the above solutions, it may be helpful to consult with your SAP Basis or Fiori team for further investigation.