How To Fix /PF1/FIORI_UI059 - Template not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/FIORI_UI -

• Message number: 059

• Message text: Template 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 /PF1/FIORI_UI059 - Template not found ?

  The SAP error message /PF1/FIORI_UI059 Template not found typically indicates that the Fiori application is unable to locate a specific template that it requires to render the user interface. This can occur for several reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Missing Template: The specified template may not be available in the system. This could be due to an incomplete installation or configuration of the Fiori application.
  Incorrect Configuration: The Fiori launchpad or the application configuration might be incorrect, leading to the system looking for a template that does not exist.
  Transport Issues: If the application was recently transported from another system, the transport might not have included all necessary components.
  Authorization Issues: The user may not have the necessary authorizations to access the template.
  Version Mismatch: There may be a version mismatch between the Fiori front-end server and the back-end system.
  
  Solutions:
  
  
  Check Template Availability:
  
  Verify that the template exists in the system. You can do this by checking the relevant Fiori application configuration in the SAP Fiori launchpad designer or the backend system.
  
  
  
  Review Configuration:
  
  Ensure that the Fiori launchpad is correctly configured. Check the launchpad settings and the application configuration to ensure that the correct template is referenced.
  
  
  
  Transport Check:
  
  If the application was recently transported, ensure that all necessary components were included in the transport request. You may need to re-transport the missing components.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary roles and authorizations to access the Fiori application and its templates. You can check this in the user management area of SAP.
  
  
  
  Update and Patch:
  
  Ensure that both the Fiori front-end server and the back-end system are up to date with the latest patches and updates. Sometimes, bugs in earlier versions can lead to such issues.
  
  
  
  Check Logs:
  
  Review the application logs and the Fiori launchpad logs for any additional error messages that might provide more context about the issue.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues related to the specific Fiori application you are using. SAP frequently releases notes that address bugs and provide guidance on configuration.
  Fiori Launchpad Designer: Familiarize yourself with the Fiori Launchpad Designer, as it is a key tool for managing Fiori applications and templates.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance.