How To Fix PMEVC_UI170 - Discard has been called for a new object: It has been deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: PMEVC_UI -

• Message number: 170

• Message text: Discard has been called for a new object: It has been deleted

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 PMEVC_UI170 - Discard has been called for a new object: It has been deleted ?

  The SAP error message PMEVC_UI170 "Discard has been called for a new object: It has been deleted" typically occurs in the context of SAP's Project Management or Project System modules. This error indicates that an attempt was made to discard changes to a new object that has already been deleted from the database or the session context.
  Cause:
  
  Object Deletion: The object you are trying to work with (e.g., a project, task, or other entity) has been deleted from the database or the session context before the discard operation was attempted.
  Session State: The session may have become inconsistent, possibly due to a previous operation that deleted the object or due to a network issue.
  User Actions: The user may have inadvertently deleted the object or navigated away from it before the discard operation was executed.
  
  Solution:
  
  Refresh the Session: Try refreshing the session or reloading the transaction to ensure that you are working with the most current data.
  Check Object Existence: Verify whether the object still exists in the database. You can do this by navigating to the relevant transaction or using a report to check for the object's status.
  Recreate the Object: If the object has been deleted and you need it, you may need to recreate it from scratch.
  Avoid Discarding: If you are working with a new object that has not been saved yet, avoid calling the discard operation if you are unsure about the object's state.
  Consult Logs: Check the application logs (transaction SLG1) for any additional error messages or warnings that might provide more context about the deletion.
  Contact Support: If the issue persists and you cannot determine the cause, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error.
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that might address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes related to project management (e.g., CJ20N for project planning) to navigate and verify object statuses.
  User Documentation: Review user documentation or training materials related to the specific module you are working with to understand the proper workflows and object management practices.
  
  By following these steps, you should be able to address the PMEVC_UI170 error and understand its implications in your SAP environment.