How To Fix SPROJECT064 - Project is deleted by batch job (Name: &1/User: &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: SPROJECT - General Project Management Messages

• Message number: 064

• Message text: Project is deleted by batch job (Name: &1/User: &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 SPROJECT064 - Project is deleted by batch job (Name: &1/User: &2) ?

  The SAP error message SPROJECT064 indicates that a project has been deleted by a batch job. This message typically arises in the context of project management within SAP, particularly when dealing with the Project System (PS) module.
  Cause:
  The error occurs when a project that you are trying to access or work with has been deleted by a batch job. This could happen for several reasons, including:
  
  Scheduled Deletion Jobs: There may be a scheduled batch job that is set to delete projects based on certain criteria (e.g., projects that are completed, archived, or older than a specific date).
  Manual Deletion: A user with the necessary permissions may have manually deleted the project.
  Data Cleanup Processes: Regular data maintenance or cleanup processes may have been configured to remove inactive or obsolete projects.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check Batch Job Logs: Review the logs of the batch job that deleted the project. This can provide insights into why the project was deleted and whether it was intended.
  
  You can use transaction code SM37 to view the job logs and find the specific job that deleted the project.
  
  
  
  Verify Project Status: Confirm whether the project is indeed deleted or if it is still in the system but marked as inactive. You can check this using transaction code CJ20N (Project Builder) or CJ03 (Display Project).
  
  
  Restore the Project: If the project was deleted unintentionally and you have a backup or a way to restore it, you may need to recreate the project or restore it from an archive if applicable.
  
  
  Review Deletion Criteria: If the deletion was part of a scheduled job, review the criteria set for project deletion. You may want to adjust the parameters to prevent unintended deletions in the future.
  
  
  Consult with Basis or Security Team: If you suspect that the deletion was not intended, consult with your SAP Basis or security team to investigate further. They may have additional insights or logs that can help clarify the situation.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  CJ20N: Project Builder
  CJ03: Display Project
  SM37: Job Monitoring
  SARA: Archive Administration (if archiving is involved)
  
  
  
  User Permissions: Ensure that only authorized users have the ability to delete projects, and review user roles and permissions if necessary.
  
  
  Documentation: Check SAP documentation or notes related to project deletion and batch jobs for any specific configurations or best practices.
  
  
  By following these steps, you should be able to address the SPROJECT064 error and prevent similar issues in the future.