How To Fix MPD079 - Maintenance plan start in process

SAP Error Message - Details

• Message type: E = Error

• Message class: MPD - Message Class for A&D MPD

• Message number: 079

• Message text: Maintenance plan start in process

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 MPD079 - Maintenance plan start in process ?

  The SAP error message MPD079, which states "Maintenance plan start in process," typically occurs when a maintenance plan is already being processed or is in the middle of execution. This can happen in various scenarios, such as when a maintenance plan is scheduled to run, or if there is a background job that is currently executing the maintenance plan.
  Causes:
  
  Concurrent Execution: The maintenance plan is already being processed by another job or user.
  System Lock: There may be a lock on the maintenance plan due to a previous execution that has not yet completed.
  Background Job: A background job related to the maintenance plan is still running.
  Database Lock: A database lock might be preventing the maintenance plan from being executed again.
  
  Solutions:
  
  
  Check Background Jobs: Use transaction code SM37 to check if there are any background jobs related to the maintenance plan that are still running. If you find any, you may need to wait for them to complete or terminate them if they are stuck.
  
  
  Review Lock Entries: Use transaction code SM12 to check for any lock entries related to the maintenance plan. If you find locks that are no longer needed, you can delete them (ensure you have the necessary authorizations and that it is safe to do so).
  
  
  Wait for Completion: If the maintenance plan is genuinely in process, you may need to wait for it to complete before attempting to start it again.
  
  
  Check for Errors: Review the logs for any errors that may have occurred during the execution of the maintenance plan. This can provide insights into why it is still in process.
  
  
  Restart the Process: If you have confirmed that no other jobs are running and there are no locks, you can try to restart the maintenance plan.
  
  
  Consult Documentation: Refer to SAP documentation or support notes for any specific guidance related to your version of SAP and the maintenance plan configuration.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM37: Monitor background jobs.
  SM12: Display and delete lock entries.
  IW38: Change maintenance orders (to check related orders).
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the MPD079 error message.
  
  
  System Performance: Sometimes, system performance issues can cause delays in job processing. Ensure that the system is running optimally.
  
  
  If the issue persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.