How To Fix DPR_UI_BSP135 - &1 not found in DPR_UI_GANTT_XSLT.xslt. Please contact your Administrator

SAP Error Message - Details

• Message type: E = Error

• Message class: DPR_UI_BSP - PLM Development Projects - BSP UI Messages

• Message number: 135

• Message text: &1 not found in DPR_UI_GANTT_XSLT.xslt. Please contact your Administrator

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 DPR_UI_BSP135 - &1 not found in DPR_UI_GANTT_XSLT.xslt. Please contact your Administrator ?

  The SAP error message "DPR_UI_BSP135 &1 not found in DPR_UI_GANTT_XSLT.xslt. Please contact your Administrator" typically occurs in the context of SAP Project Management or SAP Portfolio and Project Management (PPM) when there is an issue with the Gantt chart display or related functionalities.
  Cause:
  
  Missing or Corrupted XSLT File: The error indicates that a specific entry (or key) is not found in the XSLT file used for rendering the Gantt chart. This could be due to the file being missing, corrupted, or not properly configured.
  Configuration Issues: There may be issues with the configuration settings in the SAP system that are preventing the proper loading of the XSLT file.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access certain components or files, leading to this error.
  System Upgrade or Patch: If the system has recently been upgraded or patched, it may have introduced changes that affect the availability or functionality of the XSLT file.
  
  Solution:
  
  Check XSLT File: Verify that the DPR_UI_GANTT_XSLT.xslt file exists in the appropriate directory and is not corrupted. If it is missing, you may need to restore it from a backup or reinstall the relevant component.
  Review Configuration: Check the configuration settings related to the Gantt chart in the SAP system. Ensure that all necessary parameters are correctly set.
  User Authorizations: Ensure that the user encountering the error has the necessary authorizations to access the Gantt chart and related components.
  System Logs: Review the system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  Contact SAP Support: If the issue persists after checking the above points, it may be necessary to contact SAP support for further assistance. Provide them with the error message and any relevant details about the system configuration and recent changes.
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide patches or updates.
  Documentation: Review the official SAP documentation for Project Management and Gantt chart functionalities to ensure that all configurations are correctly implemented.
  Community Forums: Consider searching or posting in SAP community forums or discussion groups, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to diagnose and potentially resolve the error message you are encountering.