How To Fix /FTI/WEBGUI_MSG116 - Entry for this SSCUI was not found in the Web GUI item table

SAP Error Message - Details

• Message type: E = Error

• Message class: /FTI/WEBGUI_MSG -

• Message number: 116

• Message text: Entry for this SSCUI was not found in the Web GUI item table

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 /FTI/WEBGUI_MSG116 - Entry for this SSCUI was not found in the Web GUI item table ?

  The SAP error message /FTI/WEBGUI_MSG116 Entry for this SSCUI was not found in the Web GUI item table typically indicates that there is a missing entry in the Web GUI item table for a specific Self-Service Configuration UI (SSCUI). This can occur in the context of SAP Fiori or SAP S/4HANA environments where the Web GUI is used to access certain functionalities.
  Cause:
  
  Missing Configuration: The SSCUI you are trying to access may not be properly configured or may not exist in the system.
  Transport Issues: If the configuration was transported from another system (e.g., from development to production), it may not have been transported correctly.
  Authorization Issues: The user may not have the necessary authorizations to access the SSCUI.
  System Version: The version of the system may not support the specific SSCUI you are trying to access.
  
  Solution:
  
  
  Check SSCUI Configuration:
  
  Go to the SSCUI configuration in the SAP system and verify that the entry exists and is correctly configured.
  You can check the relevant SSCUI in the Fiori Launchpad or through the SAP GUI.
  
  
  
  Transport Check:
  
  If the SSCUI was recently transported, ensure that the transport request was completed successfully and that all necessary objects were included.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary roles and authorizations to access the SSCUI. You can check this in the user profile or by using transaction SU53 to analyze authorization issues.
  
  
  
  System Version Compatibility:
  
  Ensure that your system version supports the SSCUI you are trying to access. Check the SAP notes or documentation for any version-specific requirements.
  
  
  
  Check Web GUI Item Table:
  
  If you have access, you can check the Web GUI item table directly (usually a database table) to see if the entry for the SSCUI exists. The table name may vary, but it is often related to the Web GUI configuration.
  
  
  
  SAP Notes and Support:
  
  Search for relevant SAP Notes that might address this specific error. SAP frequently updates their knowledge base with solutions for common issues.
  
  
  
  Related Information:
  
  SAP Fiori and SSCUI: Understanding how Self-Service Configuration UIs work in the context of SAP Fiori can help in troubleshooting.
  SAP Community: Engaging with the SAP Community forums can provide insights from other users who may have encountered similar issues.
  SAP Help Portal: The official SAP Help Portal contains documentation and guides that can assist in understanding the configuration and usage of SSCUIs.
  
  If the issue persists after trying the above solutions, consider reaching out to your SAP support team or consulting with SAP directly for further assistance.