How To Fix /PF1/MSG_GUI058 - PO type not allowed; no items can be displayed

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_GUI -

• Message number: 058

• Message text: PO type not allowed; no items can be displayed

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/MSG_GUI058 - PO type not allowed; no items can be displayed ?

  The SAP error message /PF1/MSG_GUI058 PO type not allowed; no items can be displayed typically occurs when you are trying to display or process a Purchase Order (PO) in SAP, but the system has determined that the type of PO you are attempting to access is not permitted for the current operation. This can happen for several reasons, including configuration settings or authorization issues.
  Causes:
  
  
  PO Type Configuration: The Purchase Order type you are trying to access may not be configured correctly in the system. Certain PO types may be restricted based on the user's role or the transaction being performed.
  
  
  Authorization Issues: The user may not have the necessary authorizations to view or process the specific type of Purchase Order.
  
  
  Document Type Settings: The document type settings in the configuration may restrict certain types of POs from being displayed or processed in specific transactions.
  
  
  User Role Assignment: The user role assigned may not include permissions for the specific PO type.
  
  
  Solutions:
  
  
  Check PO Type Configuration:
  
  Go to the configuration settings for Purchase Orders in the SAP system (transaction code SPRO).
  Navigate to the relevant section for Purchase Order types and ensure that the type you are trying to access is allowed for the transaction you are using.
  
  
  
  Review User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check for authorization issues.
  If there are missing authorizations, work with your SAP security team to ensure that the user has the necessary permissions for the PO type.
  
  
  
  Consult with SAP Basis or Configuration Team:
  
  If you suspect that the issue is related to system configuration, consult with your SAP Basis or configuration team to review the settings for the Purchase Order types.
  
  
  
  Check User Role Assignment:
  
  Ensure that the user has the correct roles assigned that include access to the specific PO type. This can be checked in transaction code PFCG.
  
  
  
  Use Alternative Transactions:
  
  If the current transaction does not allow for the PO type, consider using an alternative transaction that supports the PO type you are trying to access.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME23N (Display Purchase Order), ME22N (Change Purchase Order), and ME21N (Create Purchase Order).
  SAP Notes: Check SAP Notes for any known issues or patches related to the error message.
  Documentation: Review SAP documentation for Purchase Order types and their configurations to understand the implications of different settings.
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.