How To Fix /UI2/CDMFCC_CHECK158 - Given AppConfig &1&2 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/CDMFCC_CHECK -

• Message number: 158

• Message text: Given AppConfig &1&2 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/CDMFCC_CHECK158 - Given AppConfig &1&2 not found ?

  The SAP error message /UI2/CDMFCC_CHECK158 with the description "Given AppConfig &1&2 not found" typically indicates that the system is unable to find the specified application configuration (AppConfig) for a particular Fiori application. This can occur for various reasons, such as missing configuration entries, incorrect application IDs, or issues with the Fiori launchpad setup.
  Causes:
  
  Missing AppConfig: The specified AppConfig does not exist in the system.
  Incorrect Application ID: The application ID provided in the configuration might be incorrect or misspelled.
  Transport Issues: If the application configuration was transported from another system, it might not have been transported correctly.
  Authorization Issues: The user might not have the necessary authorizations to access the AppConfig.
  Caching Issues: Sometimes, caching issues can prevent the system from recognizing newly created or modified AppConfigs.
  
  Solutions:
  
  
  Check AppConfig Existence:
  
  Go to the Fiori Launchpad Designer or the relevant transaction (like /UI2/FLP) and verify if the AppConfig exists for the specified application ID.
  If it does not exist, you may need to create it.
  
  
  
  Verify Application ID:
  
  Double-check the application ID used in the configuration to ensure it is correct.
  
  
  
  Transport Check:
  
  If the AppConfig was supposed to be transported, check the transport logs to ensure it was successfully imported into the target system.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary roles and authorizations to access the Fiori application and its configuration.
  
  
  
  Clear Cache:
  
  Clear the cache of the Fiori Launchpad. This can often resolve issues related to outdated configurations.
  You can do this by using the transaction /UI2/FLP and selecting the option to clear the cache.
  
  
  
  Check Backend Services:
  
  Ensure that the backend services required by the Fiori application are active and properly configured.
  
  
  
  Related Information:
  
  Fiori Launchpad Configuration: Familiarize yourself with the Fiori Launchpad configuration and how AppConfigs are set up.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Documentation: Refer to the official SAP documentation for Fiori and Launchpad configuration for more detailed guidance.
  
  If the issue persists after trying the above solutions, consider reaching out to your SAP Basis or Fiori support team for further assistance.