How To Fix /LTB/MC085 - Job &1/&2 could not be deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: /LTB/MC -

• Message number: 085

• Message text: Job &1/&2 could not be 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 /LTB/MC085 - Job &1/&2 could not be deleted ?

  The SAP error message /LTB/MC085 Job &1/&2 could not be deleted typically occurs when there is an issue with deleting a background job in the SAP system. This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  Job Status: The job may be in a status that does not allow deletion (e.g., it might be currently running or finished).
  Authorization Issues: The user attempting to delete the job may not have the necessary authorizations to perform this action.
  Job Locking: The job might be locked by another process or user, preventing its deletion.
  System Errors: There could be underlying system issues or inconsistencies in the job management tables.
  Job Dependencies: The job may have dependencies on other jobs that need to be resolved before it can be deleted.
  
  Solutions:
  
  Check Job Status: Use transaction code SM37 to check the status of the job. If it is still running or in a finished state, you may need to wait until it is completed or canceled before attempting to delete it.
  Cancel the Job: If the job is running, you can try to cancel it first. In SM37, select the job and choose the option to cancel it.
  Check Authorizations: Ensure that the user has the necessary authorizations to delete background jobs. You may need to consult with your SAP security team.
  Release Locks: If the job is locked, you may need to identify the locking process and release it. You can use transaction SM12 to check for locks.
  Use Transaction SM36: If you are unable to delete the job through SM37, you can try using transaction SM36 to manage jobs and see if you can delete it from there.
  Check for Dependencies: Review any dependencies that the job may have and resolve them before attempting to delete the job again.
  System Check: If the issue persists, consider checking for system errors or inconsistencies. You may need to consult with your SAP Basis team for further investigation.
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Monitor Background Jobs
  SM12: Display and Delete Locks
  SM36: Define Background Job
  
  
  SAP Notes: Check SAP Notes for any known issues related to job deletion errors. You can search for relevant notes in the SAP Support Portal.
  Documentation: Refer to SAP Help documentation for more details on managing background jobs and troubleshooting job-related issues.
  
  If the problem continues after trying the above solutions, it may be necessary to escalate the issue to your SAP Basis or technical support team for further assistance.