How To Fix /UI2/CDMFCC347 - Reference of &1 &2 is set to &3

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/CDMFCC -

• Message number: 347

• Message text: Reference of &1 &2 is set to &3

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/CDMFCC347 - Reference of &1 &2 is set to &3 ?

  The SAP error message /UI2/CDMFCC347 Reference of &1 &2 is set to &3 typically indicates an issue related to the configuration of a Fiori app or a related component in the SAP system. This message is often associated with the Fiori Launchpad and its configuration settings.
  Cause:
  The error message generally arises due to one of the following reasons:
  
  Incorrect Configuration: The reference to a specific object (like a catalog, group, or tile) is not correctly set up in the system.
  Missing Authorization: The user may not have the necessary authorizations to access the referenced object.
  Inconsistent Data: There may be inconsistencies in the data related to the Fiori app configuration, such as missing entries in the backend or frontend systems.
  Transport Issues: If the configuration was transported from one system to another, there might be issues with the transport that led to missing or incorrect references.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Configuration:
  
  Verify the configuration of the Fiori app in the SAP Fiori Launchpad Designer.
  Ensure that the references to catalogs, groups, and tiles are correctly set up.
  
  
  
  Review Authorizations:
  
  Check the user roles and authorizations to ensure that the user has access to the referenced objects.
  Use transaction PFCG to review and adjust roles as necessary.
  
  
  
  Consistency Check:
  
  Perform a consistency check on the Fiori configuration. You can use transaction /UI2/FLP to check for any inconsistencies.
  Ensure that all necessary entries exist in the backend and frontend systems.
  
  
  
  Transport Management:
  
  If the issue arose after a transport, check the transport logs for any errors or warnings.
  Ensure that all necessary objects were included in the transport request.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the application to identify the exact point of failure.
  Use transaction SE80 or SE37 to analyze the relevant code or function modules.
  
  
  
  SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  
  
  Related Information:
  
  SAP Fiori Launchpad: Understanding the architecture and configuration of the Fiori Launchpad can help in troubleshooting issues related to app references.
  Authorization Management: Familiarity with role-based access control in SAP can assist in resolving authorization-related issues.
  SAP Community: Engaging with the SAP Community forums can provide insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance.