How To Fix /UI2/FDM013 - Target mapping &1&2: Refers to LPD_CUST entry

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/FDM -

• Message number: 013

• Message text: Target mapping &1&2: Refers to LPD_CUST entry

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/FDM013 - Target mapping &1&2: Refers to LPD_CUST entry ?

  The SAP error message /UI2/FDM013 Target mapping &1&2: Refers to LPD_CUST entry typically occurs in the context of SAP Fiori applications and the configuration of target mappings in the SAP Fiori Launchpad. This error indicates that the target mapping you are trying to use is referencing an entry in the LPD_CUST (Launchpad Customizing) table that is not properly configured or does not exist.
  Cause:
  
  Missing LPD_CUST Entry: The target mapping is pointing to a Launchpad configuration that does not exist in the LPD_CUST table.
  Incorrect Configuration: The entry in the LPD_CUST table may be incorrectly configured, leading to the error.
  Transport Issues: If the configuration was transported from one system to another, the LPD_CUST entries may not have been included or may not have been properly activated.
  
  Solution:
  
  
  Check LPD_CUST Entries:
  
  Go to transaction code LPD_CUST in the SAP GUI.
  Verify that the entry referenced in the error message exists and is correctly configured.
  If it does not exist, you may need to create it or correct the existing entry.
  
  
  
  Review Target Mapping:
  
  Check the target mapping configuration in the Fiori Launchpad Designer or using transaction UI2/FLP.
  Ensure that the target mapping is correctly pointing to the appropriate LPD_CUST entry.
  
  
  
  Transport Management:
  
  If the issue arose after a transport, ensure that all necessary objects, including LPD_CUST entries, were included in the transport request.
  Re-import the transport if necessary or manually create the missing entries.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the LPD_CUST entries and the associated Fiori applications.
  
  
  
  Clear Cache:
  
  Sometimes, clearing the cache can resolve issues related to outdated configurations. You can do this by using transaction /UI2/FLP_CLEANUP or by clearing the browser cache if you are using the Fiori Launchpad in a web browser.
  
  
  
  Related Information:
  
  LPD_CUST Table: This table is used for customizing the SAP Fiori Launchpad and contains entries for the launchpad configuration.
  Fiori Launchpad Designer: This is the tool used to manage and configure the Fiori Launchpad, including target mappings and catalogs.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message or provide additional troubleshooting steps.
  
  If the problem persists after following these steps, consider reaching out to your SAP Basis or Fiori support team for further assistance.