How To Fix WS347 - Run with name & does not exist (see long text)

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 347

• Message text: Run with name & does not exist (see long text)

What causes this issue?

Processed documents have been saved under the name of the program run.
If the program is terminated, because time is exceeded, or any other
reason, you can continue with the next document due for processing.
Enter the name of the run, and deselect the <LS>New run</> indicator.
As further selection parameters such as supplier and purchasing
organization are not stored, you should save these as a variant.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check the name you entered and the <LS>New run</> indicator.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WS347 - Run with name & does not exist (see long text) ?

  SAP Error Message:
  
  WS347 - Run with name & does not exist (see long text)
  
  Cause:
  This error occurs when you try to execute or reference a background job (job run) by a name that does not exist in the system. The system cannot find a job run with the specified name in the job scheduling or job monitoring tools.
  Common scenarios include:  
  
  Typing an incorrect job name or run name.  
  The job run was deleted or never created.  
  Attempting to rerun or monitor a job run that has not been scheduled or started.  
  Using a program or transaction that expects a valid job run name, but the input is missing or incorrect.
  
  
  Solution:
  
  
  Verify the Job Run Name:  
  
  Check the exact job run name you are trying to use.  
  Use transaction SM37 (Job Monitoring) to list existing jobs and their runs.  
  Confirm the job run name exists and is active or completed.
  
  
  
  Correct the Input:  
  
  If you are entering the job run name manually, ensure there are no typos or extra spaces.  
  If the job run name is passed from a program or script, verify the source of the name.
  
  
  
  Create or Schedule the Job Run:  
  
  If the job run does not exist, schedule the job first using SM36 or the relevant scheduling tool.  
  After scheduling, the job run will be available for execution or monitoring.
  
  
  
  Check Authorizations:  
  
  Ensure you have the necessary authorizations to view or execute the job run.
  
  
  
  Review Long Text for Details:  
  
  The message suggests checking the long text for more information.  
  In SAP GUI, press F1 on the message and then click on "Long Text" to get detailed explanation and hints.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:  
  
  SM36 - Define Background Job  
  SM37 - Job Monitoring  
  SM50/SM66 - Process Monitoring (to check running jobs)  
  SM21 - System Log (for related errors)
  
  
  
  SAP Notes:  
  
  Check SAP Notes related to job scheduling and job run errors if the problem persists.
  
  
  
  Background Jobs:  
  
  Background jobs in SAP are scheduled tasks that run asynchronously. Each job can have multiple runs (executions). The system tracks these runs by name and run number.
  
  
  
  
  Summary:
  The error WS347 indicates that the system cannot find a background job run with the specified name. Verify the job run name, ensure the job is scheduled and exists, and correct any input errors. Use SM37 to check job runs and refer to the long text for detailed guidance.