How To Fix LTR_DELIM_WORKBENCH035 - Run has not been started yet

SAP Error Message - Details

• Message type: E = Error

• Message class: LTR_DELIM_WORKBENCH - Application Messages

• Message number: 035

• Message text: Run has not been started yet

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 LTR_DELIM_WORKBENCH035 - Run has not been started yet ?

  The SAP error message LTR_DELIM_WORKBENCH035: Run has not been started yet typically occurs in the context of the SAP Landscape Transformation (SLT) Replication Server or when working with data replication and transformation tasks. This error indicates that a specific replication run or task has not been initiated or started properly.
  Causes:
  
  Replication Task Not Started: The most common cause is that the replication task or job has not been initiated. This could be due to a manual oversight or a configuration issue.
  Job Scheduling Issues: If the job is scheduled but not executed, it may lead to this error.
  Technical Issues: There may be underlying technical issues, such as connectivity problems between the source and target systems, or issues with the SLT configuration.
  Authorization Issues: The user executing the task may not have the necessary authorizations to start the replication run.
  
  Solutions:
  
  
  Start the Replication Task: 
  
  Go to the SLT configuration in the SAP GUI.
  Navigate to the relevant replication configuration and ensure that the task is started. You can do this by selecting the task and choosing the option to start it.
  
  
  
  Check Job Scheduling:
  
  Verify if the job is scheduled correctly in the background job management (transaction SM37).
  If it is scheduled but not running, you may need to manually start it or check for any errors in the job logs.
  
  
  
  Review Configuration:
  
  Ensure that the SLT configuration is set up correctly. Check the source and target system connections, and ensure that all necessary settings are in place.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to execute the replication task. You may need to consult with your SAP security team to verify this.
  
  
  
  Monitor Logs:
  
  Check the SLT logs for any additional error messages or warnings that could provide more context about why the run has not started. You can use transaction SLG1 to view application logs.
  
  
  
  Restart SLT Replication:
  
  If the issue persists, consider stopping and restarting the SLT replication configuration. This can sometimes resolve transient issues.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SLT Configuration: Transaction LTRC
  Monitoring: Transaction LTRM
  Job Monitoring: Transaction SM37
  
  
  Documentation: Refer to SAP Help documentation for SLT for detailed guidance on configuration and troubleshooting.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message.
  
  If the problem continues after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.