How To Fix /UI2/FCM123 - Target mapping '&1' was deleted in another session

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FCM -

• Message number: 123

• Message text: Target mapping '&1' was deleted in another session

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/FCM123 - Target mapping '&1' was deleted in another session ?

  The SAP error message /UI2/FCM123 Target mapping '&1' was deleted in another session typically occurs in the context of SAP Fiori applications and the Fiori Launchpad. This error indicates that a target mapping, which is a configuration that defines how a specific application is launched from the Fiori Launchpad, has been deleted or modified in another session or by another user.
  Cause:
  
  Concurrent Modifications: The target mapping was deleted or modified by another user or session while you were trying to access or modify it.
  Transport Issues: If the target mapping was part of a transport request that was moved to a different system, it may no longer exist in the current environment.
  System Synchronization: In a multi-system landscape, changes made in one system may not yet be reflected in another, leading to inconsistencies.
  
  Solution:
  
  Refresh the Session: Log out and log back into the Fiori Launchpad or refresh the browser session to ensure you are working with the latest data.
  Check Target Mapping: Verify if the target mapping still exists in the system. You can do this by navigating to the relevant configuration area in the SAP Fiori Launchpad Designer or using transaction code /UI2/FLP.
  Recreate the Target Mapping: If the target mapping has indeed been deleted, you may need to recreate it. Ensure that you have the necessary details (like the application ID, semantic object, etc.) to set it up correctly.
  Check Transport Requests: If you suspect that the target mapping was part of a transport, check the transport logs and ensure that the transport was successfully imported into the target system.
  Consult with Colleagues: If you are working in a team, check with your colleagues to see if anyone else has made changes to the target mapping that could have led to its deletion.
  
  Related Information:
  
  Fiori Launchpad Designer: This is the tool used to manage target mappings and other configurations for Fiori applications. You can access it via the URL or transaction code /UI2/FLP.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  System Logs: Review system logs (transaction SLG1) for any additional error messages or warnings that might provide more context about the issue.
  
  If the problem persists after trying the above solutions, consider reaching out to your SAP Basis or Fiori support team for further assistance.