How To Fix LTR2_BASIS_SL060 - Stop-command by user

SAP Error Message - Details

• Message type: E = Error

• Message class: LTR2_BASIS_SL - Step List Messages

• Message number: 060

• Message text: Stop-command by user

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 LTR2_BASIS_SL060 - Stop-command by user ?

  The SAP error message LTR2_BASIS_SL060 with the description "Stop-command by user" typically indicates that a user has manually stopped a process or job in the SAP system. This can occur in various contexts, such as during data processing, batch jobs, or other long-running operations.
  Cause:
  
  Manual Intervention: The most common cause is that a user or administrator has issued a stop command for a job or process that was running in the background.
  System Configuration: Sometimes, system settings or configurations may lead to processes being stopped if they exceed certain thresholds or time limits.
  User Permissions: Users with the appropriate permissions can stop jobs, which may lead to this error if they do so intentionally or accidentally.
  
  Solution:
  
  Check Job Status: Review the job or process that was stopped. You can do this by navigating to the relevant transaction (e.g., SM37 for job monitoring) to see the status and logs of the job.
  Restart the Job: If the job needs to be completed, you can restart it. Ensure that you have the necessary permissions to do so.
  Investigate User Actions: If the stop command was issued unintentionally, check with the users who have access to the job to understand why it was stopped.
  Review System Logs: Check the system logs (transaction SM21) for any additional information that might indicate why the job was stopped or if there were any related issues.
  Adjust Job Parameters: If jobs are frequently being stopped due to timeouts or resource limits, consider adjusting the job parameters or system settings to accommodate longer processing times.
  
  Related Information:
  
  User Permissions: Ensure that only authorized users have the ability to stop jobs. Review user roles and permissions if necessary.
  Monitoring Tools: Utilize SAP monitoring tools to keep track of job statuses and system performance to prevent unexpected stops.
  Documentation: Refer to SAP documentation or support notes related to job management and error handling for more detailed guidance.
  
  If the issue persists or if you need further assistance, consider reaching out to your SAP Basis team or SAP support for more in-depth troubleshooting.