How To Fix 6P513 - Requirement existed in deleted state, and was chenged

SAP Error Message - Details

• Message type: E = Error

• Message class: 6P - Messages for planned independent requirements (Appl.area 60)

• Message number: 513

• Message text: Requirement existed in deleted state, and was chenged

What causes this issue?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

The system saves all planned independent requirements that are entered
under a requirements number that is maintained internally within the
system. This requirements number is not deleted if you delete the
planned independent requirement. That is, if a planned independent
requirement item of a particular material is deleted, this requirements
number still remains in the system. New planned independent requirements
or changed independent requirements that are entered for this material
are continued to be saved under this number.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 6P513 - Requirement existed in deleted state, and was chenged ?

  The SAP error message 6P513 ("Requirement existed in deleted state, and was changed") typically occurs in the context of SAP's Project System (PS) or Production Planning (PP) modules. This error indicates that a requirement (such as a planned order, production order, or project requirement) was previously marked as deleted, but an attempt was made to change it or process it in a way that is not allowed because of its deleted status.
  Cause:
  
  Deleted Requirement: The requirement you are trying to modify or process has been marked as deleted in the system.
  Data Inconsistency: There may be inconsistencies in the data where the system is trying to access or modify a requirement that is no longer valid.
  User Actions: A user may have inadvertently deleted a requirement or made changes that led to this state.
  
  Solution:
  
  
  Check Requirement Status: Verify the status of the requirement in question. You can do this by navigating to the relevant transaction (e.g., CO03 for production orders, CJ20N for project management) and checking if the requirement is indeed marked as deleted.
  
  
  Restore Requirement: If the requirement was deleted by mistake, you may need to restore it. This can often be done by reversing the deletion if the system allows it. Consult your SAP documentation or your system administrator for specific steps.
  
  
  Recreate Requirement: If restoring is not possible, you may need to recreate the requirement. This involves entering the necessary data again to generate a new requirement.
  
  
  Check for Custom Logic: If there are custom developments or enhancements in your SAP system, check if any of these are affecting the behavior of requirements. Sometimes, custom logic can lead to unexpected states.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message. There may be patches or updates that resolve known issues.
  
  
  Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance. Provide them with detailed information about the error, including the steps that led to it.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CO03 (Display Production Order), CJ20N (Project Builder), or others depending on your specific context.
  User Authorizations: Ensure that you have the necessary authorizations to modify or view the requirements in question.
  System Logs: Check system logs (transaction SLG1) for any additional error messages or warnings that might provide more context about the issue.
  
  By following these steps, you should be able to diagnose and resolve the error message 6P513 in your SAP system.