How To Fix MM_PUR_PO_EXT_MSG035 - Previous job scheduled for automatic restart of initial load was aborted.

SAP Error Message - Details

• Message type: E = Error

• Message class: MM_PUR_PO_EXT_MSG - Message class for Backend PO Extraction

• Message number: 035

• Message text: Previous job scheduled for automatic restart of initial load was aborted.

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 MM_PUR_PO_EXT_MSG035 - Previous job scheduled for automatic restart of initial load was aborted. ?

  The SAP error message MM_PUR_PO_EXT_MSG035 indicates that a previous job scheduled for the automatic restart of an initial load was aborted. This typically occurs in the context of data extraction or loading processes, particularly when dealing with Purchase Orders (PO) in the Materials Management (MM) module.
  Cause:
  
  
  Job Abortion: The job that was supposed to perform the initial load may have encountered an error or issue that caused it to abort. This could be due to various reasons such as:
  
  Data inconsistencies or errors in the source system.
  Network issues or connectivity problems.
  Resource limitations (e.g., memory, CPU) on the server.
  Configuration issues in the job scheduling or in the data extraction process.
  
  
  
  System Configuration: Incorrect configuration settings for the job or the data extraction process can lead to failures.
  
  
  Data Volume: Large volumes of data being processed can sometimes lead to timeouts or resource exhaustion.
  
  
  Solution:
  
  
  Check Job Logs: Review the job logs for the specific job that was aborted. This will provide detailed information about why the job failed. You can do this by navigating to the job management transaction (e.g., SM37) and checking the status and logs of the relevant job.
  
  
  Analyze Error Messages: Look for any specific error messages or codes in the job logs that can give you more insight into the cause of the failure.
  
  
  Restart the Job: If the issue has been resolved (e.g., data issues fixed, resources allocated), you can manually restart the job. Ensure that the job is configured correctly before restarting.
  
  
  Adjust Job Scheduling: If the job is consistently failing due to resource limitations, consider adjusting the scheduling of the job to run during off-peak hours or increasing the resources available to the job.
  
  
  Data Validation: Ensure that the data being processed is valid and does not contain any inconsistencies that could cause the job to fail.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific error message for additional troubleshooting steps or patches that may be required.
  
  
  Contact SAP Support: If the issue persists and you cannot determine the cause, consider reaching out to SAP support for assistance.
  
  
  Related Information:
  
  Transaction Codes: Use transaction codes like SM37 (Job Monitoring) to check job status and logs, and ST22 (Dump Analysis) to check for any ABAP runtime errors that may have occurred.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address known issues related to this error message.
  Performance Monitoring: Monitor system performance and resource usage to identify any bottlenecks that may be affecting job execution.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the MM_PUR_PO_EXT_MSG035 error message.