How To Fix WS390 - Termination because time exceeded: &1 documents processed

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 390

• Message text: Termination because time exceeded: &1 documents processed

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 WS390 - Termination because time exceeded: &1 documents processed ?

  Certainly! Here's a detailed explanation for the SAP error message WS390 Termination because time exceeded: &1 documents processed:
  
  Error Message Overview
  
  Message ID: WS390
  Message Text: Termination because time exceeded: &1 documents processed
  Context: This message typically appears during batch processing or background jobs in SAP, especially when processing a large number of documents or records.
  
  
  Cause
  The error WS390 occurs because the processing time for a particular job or program has exceeded the allowed time limit set in the system. SAP has built-in time limits for certain processes to prevent long-running jobs from consuming excessive system resources or causing system performance issues.
  
  The parameter controlling this is often related to time limits for batch jobs or update tasks.
  The system terminates the process once the time limit is reached, even if not all documents have been processed.
  The message shows how many documents were processed before termination (&1 is replaced by the actual number).
  
  
  Common Scenarios
  
  Processing large volumes of documents in batch jobs (e.g., invoice posting, IDoc processing).
  Long-running update tasks or background jobs.
  Time limits set too low for the volume of data being processed.
  
  
  Solution
  
  
  Increase the Time Limit:
  
  Identify the time limit parameter causing the termination.
  For background jobs, check the job's time limit in transaction SM37 or the job definition.
  For update tasks or specific programs, check if there are program-specific parameters or profile parameters controlling the runtime.
  Common parameters to check:
  
  rdisp/max_wprun_time (maximum work process runtime in seconds)
  rdisp/max_wprun_time can be increased in transaction RZ10 or RZ11.
  
  
  For batch input or update programs, check if there is a program-specific timeout parameter.
  
  
  
  Optimize the Process:
  
  Reduce the number of documents processed in one run by splitting the job into smaller batches.
  Optimize the program or process to run more efficiently.
  Check for database performance issues or locks that might be slowing down processing.
  
  
  
  Check Job Scheduling:
  
  Schedule the job during off-peak hours to get more system resources.
  Ensure that the job has enough time allocated to complete.
  
  
  
  Monitor and Analyze:
  
  Use transaction SM37 to monitor job runtime and logs.
  Use transaction ST22 to check for any related short dumps.
  Use transaction SM50/SM66 to monitor work process runtime.
  
  
  
  
  Related Information
  
  SAP Notes: Search for SAP Notes related to WS390 or time exceeded errors for your specific SAP module or process.
  Transaction Codes:
  
  SM37 - Job Monitoring
  SM50/SM66 - Work Process Monitoring
  ST22 - Dump Analysis
  RZ10/RZ11 - Profile Parameter Maintenance
  
  
  Parameters:
  
  rdisp/max_wprun_time - Maximum runtime of a work process (default is often 600 seconds)
  rdisp/wp_no_btc - Number of work processes for background jobs
  
  
  Documentation: Check SAP Help Portal or module-specific guides for batch processing best practices.
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Processing time exceeded the allowed limit during batch or background job execution.
  
  
  Effect
  Job/process terminated prematurely after processing &1 documents.
  
  
  Solution
  Increase time limit, optimize processing, split jobs into smaller batches, reschedule job.
  
  
  Tools
  SM37, SM50, SM66, ST22, RZ10, RZ11
  
  
  
  
  If you provide more details about the specific process or transaction where this error occurs, I can help tailor the solution further.