How To Fix /UI2/FDM_2_CDM3070 - Group &1&2 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FDM_2_CDM3 -

• Message number: 070

• Message text: Group &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/FDM_2_CDM3070 - Group &1&2 not found ?

  The SAP error message /UI2/FDM_2_CDM3070 Group &1&2 not found typically indicates that the system is unable to locate a specific group that is referenced in the context of the Fiori Launchpad or the Fiori Design Studio. This error can occur due to various reasons, such as configuration issues, missing authorizations, or incorrect group definitions.
  Causes:
  
  Missing Group Definition: The group specified in the error message does not exist in the system.
  Authorization Issues: The user may not have the necessary authorizations to access the specified group.
  Transport Issues: If the group was recently transported from another system, it may not have been properly imported or activated.
  Configuration Errors: There may be misconfigurations in the Fiori Launchpad or the underlying OData services.
  
  Solutions:
  
  
  Check Group Definition:
  
  Go to the Fiori Launchpad Designer or the relevant transaction (e.g., /UI2/FLP or /UI2/FLP_ADMIN) and verify if the group exists.
  If it does not exist, you may need to create it or correct the reference in your application.
  
  
  
  Verify Authorizations:
  
  Ensure that the user has the necessary roles and authorizations to access the group. You can check this in transaction PFCG by reviewing the roles assigned to the user.
  
  
  
  Transport and Activation:
  
  If the group was recently transported, check the transport logs to ensure it was successfully imported.
  Activate the group if it is in a deactivated state.
  
  
  
  Check Configuration:
  
  Review the configuration settings for the Fiori Launchpad and ensure that all necessary components are correctly set up.
  Check the OData services associated with the group to ensure they are active and functioning.
  
  
  
  Debugging:
  
  If the issue persists, consider enabling debugging or checking the application logs (transaction SLG1) for more detailed error messages that could provide additional context.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Fiori Launchpad Documentation: Review the official SAP documentation for Fiori Launchpad configuration and troubleshooting.
  Community Forums: Engage with the SAP Community or forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement the appropriate solution.