How To Fix /UI2/FDM_2_CDM3093 - Page &1: Not Found

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FDM_2_CDM3 -

• Message number: 093

• Message text: Page &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_CDM3093 - Page &1: Not Found ?

  The SAP error message /UI2/FDM_2_CDM3093 Page &1: Not Found typically indicates that a specific Fiori application or page cannot be found in the system. This can occur for several reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Missing or Inactive Fiori App: The Fiori application might not be installed or activated in the SAP system.
  Authorization Issues: The user may not have the necessary authorizations to access the specific Fiori app or page.
  Incorrect Configuration: The configuration for the Fiori launchpad or the specific app might be incorrect.
  Transport Issues: If the app was recently transported from another system, there may have been issues during the transport process.
  Cache Issues: Sometimes, the cache may need to be cleared for the changes to take effect.
  
  Solutions:
  
  
  Check App Availability:
  
  Verify that the Fiori app is installed and activated in the system. You can do this by checking the Fiori apps library or using transaction code /UI2/FLP to access the Fiori launchpad.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary roles and authorizations to access the app. You can use transaction code SU53 to check for authorization issues after the error occurs.
  
  
  
  Review Configuration:
  
  Check the configuration settings for the Fiori launchpad and the specific app. Ensure that the app is correctly defined in the launchpad configuration.
  
  
  
  Transport Check:
  
  If the app was recently transported, check the transport logs for any errors. Ensure that all necessary objects were included in the transport.
  
  
  
  Clear Cache:
  
  Clear the browser cache and the SAP Fiori launchpad cache. You can do this by using transaction code /UI2/FLP and selecting the option to clear the cache.
  
  
  
  Check System Logs:
  
  Review the system logs (transaction code SLG1) for any related error messages that might provide more context about the issue.
  
  
  
  Related Information:
  
  Fiori Apps Library: Use the Fiori Apps Library to check the status and details of the specific app you are trying to access.
  SAP Notes: Search for relevant SAP Notes that might address known issues related to the specific error message.
  SAP Community: Engage with the SAP Community forums for additional insights and solutions from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or Fiori team for further investigation.