How To Fix /PF1/MSG_EH085 - Response not found for PO authorization with key &1/&2

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_EH -

• Message number: 085

• Message text: Response not found for PO authorization with key &1/&2

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_EH085 - Response not found for PO authorization with key &1/&2 ?

  The SAP error message /PF1/MSG_EH085 Response not found for PO authorization with key &1/&2 typically indicates that there is an issue with the authorization checks related to Purchase Orders (PO) in the SAP system. This error can occur when the system is unable to find the necessary authorization response for a specific Purchase Order based on the provided keys.
  Cause:
  
  Missing Authorization: The user may not have the necessary authorizations to perform actions on the specified Purchase Order.
  Configuration Issues: There may be a misconfiguration in the authorization objects or the related settings in the SAP system.
  Data Issues: The Purchase Order may not exist, or the keys provided in the error message may be incorrect or not properly linked to the authorization checks.
  Custom Development: If there are custom developments or enhancements in the system, they may not be correctly handling the authorization checks.
  
  Solution:
  
  
  Check User Authorizations:
  
  Verify that the user has the necessary authorizations to access and modify the Purchase Order. This can be done by checking the user's roles and profiles in transaction SU01 or PFCG.
  Ensure that the relevant authorization objects (e.g., E_BKPF_BES, E_BKPF_BES) are included in the user's roles.
  
  
  
  Review Configuration:
  
  Check the configuration settings for Purchase Order authorization in the relevant customizing transactions (e.g., SPRO).
  Ensure that the authorization checks are correctly set up for the Purchase Order process.
  
  
  
  Validate Purchase Order:
  
  Confirm that the Purchase Order exists and is correctly entered in the system. Use transaction ME23N to display the Purchase Order and verify its status.
  
  
  
  Debugging:
  
  If the issue persists, consider debugging the authorization check process to identify where the failure occurs. This may require assistance from a technical consultant or developer.
  
  
  
  Consult Documentation:
  
  Review SAP Notes and documentation related to the error message for any known issues or patches that may address the problem.
  
  
  
  Contact SAP Support:
  
  If the issue cannot be resolved internally, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SU01 (User Maintenance)
  PFCG (Role Maintenance)
  ME23N (Display Purchase Order)
  SPRO (SAP Reference IMG)
  
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that govern Purchase Order processing.
  
  
  SAP Notes: Search for SAP Notes related to the error message for any specific fixes or recommendations.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.