How To Fix /UI2/CDMCNV_RES104 - Tile &1&2: FE\BE Missmatch

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/CDMCNV_RES -

• Message number: 104

• Message text: Tile &1&2: FE\BE Missmatch

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/CDMCNV_RES104 - Tile &1&2: FE\BE Missmatch ?

  The SAP error message /UI2/CDMCNV_RES104 Tile &1&2: FE\BE Mismatch typically occurs in the context of SAP Fiori applications and is related to a mismatch between the front-end (FE) and back-end (BE) components of the application. This error indicates that there is a discrepancy in the configuration or versioning of the Fiori tiles or the underlying OData services.
  Cause:
  
  Version Mismatch: The front-end components (like the Fiori Launchpad) and the back-end services (like OData services) may not be compatible due to version differences.
  Configuration Issues: There may be incorrect or incomplete configurations in the Fiori Launchpad or the OData service.
  Transport Issues: If the Fiori application was recently transported from one system to another, there may be inconsistencies in the transport process.
  Missing or Incorrect Roles: The user may not have the necessary roles assigned to access the specific tile or service.
  
  Solution:
  
  Check Version Compatibility: Ensure that the front-end and back-end components are compatible. This may involve checking the SAP Notes or documentation for the specific versions of the Fiori apps and OData services.
  Review Configuration: Verify the configuration settings in the Fiori Launchpad and ensure that the OData services are correctly defined and activated.
  Transport Validation: If the issue arose after a transport, check the transport logs and ensure that all necessary components were transported correctly.
  Role Assignment: Ensure that the user has the appropriate roles assigned to access the Fiori tile and the underlying OData service. This can be done through the PFCG transaction.
  Clear Cache: Sometimes, clearing the browser cache or the SAP Gateway cache can resolve issues related to outdated or incorrect data being displayed.
  Check OData Service: Use the transaction /IWFND/MAINT_SERVICE to check if the OData service is active and properly configured.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Fiori Launchpad Configuration: Familiarize yourself with the Fiori Launchpad configuration and how tiles are defined and linked to OData services.
  SAP Community: Engage with the SAP Community forums for insights 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 development team for further investigation.