How To Fix /PF1/MSG_PO955 - EV-set could not be determined

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_PO -

• Message number: 955

• Message text: EV-set could not be determined

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_PO955 - EV-set could not be determined ?

  The SAP error message /PF1/MSG_PO955 indicating that "EV-set could not be determined" typically occurs in the context of purchasing or procurement processes, particularly when dealing with purchase orders or related documents. This error suggests that the system is unable to determine the expected value set (EV-set) for a particular operation or transaction.
  Causes:
  
  Missing Configuration: The EV-set may not be properly configured in the system. This could be due to missing entries in the customizing settings for purchasing or procurement.
  Incorrect Master Data: The master data for materials, vendors, or purchasing info records may be incomplete or incorrect, leading to the inability to determine the EV-set.
  System Bugs or Issues: There may be bugs or issues in the specific version of SAP you are using that affect the determination of the EV-set.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access certain data or configurations, leading to this error.
  
  Solutions:
  
  Check Configuration: Review the configuration settings related to purchasing and ensure that the EV-set is properly defined. This can typically be found in the SPRO transaction under the relevant purchasing settings.
  Review Master Data: Ensure that all relevant master data (materials, vendors, purchasing info records) is complete and correctly maintained. Check for any missing or incorrect entries.
  Debugging: If you have access to debugging tools, you can analyze the program logic to see where the determination of the EV-set is failing. This may require assistance from a technical consultant.
  Check Authorizations: Verify that the user encountering the error has the necessary authorizations to perform the action. This can be checked in the user roles and profiles.
  Consult SAP Notes: Look for any relevant SAP Notes or patches that may address this specific error. SAP frequently releases updates that fix known issues.
  Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and ME23N (Display Purchase Order) to see where the error occurs.
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can provide insights or solutions.
  Documentation: Review SAP documentation related to purchasing and procurement processes for additional context on EV-sets and their configurations.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution.