TIME_OUT
highWork Process CPU Time Limit Exceeded
Module: BASIS / Performance
What this means
TIME_OUT (also TIMEOUT) fires when an ABAP program exceeds the maximum CPU time allowed for a single work process execution — controlled by the rdisp/max_wprun_time profile parameter (default typically 300–600 seconds). This is a hard termination by the dispatcher. Common causes: full table scans on large tables without WHERE clause; N+1 SELECT loops inside DO/WHILE (selecting inside a loop over thousands of records); a SELECT statement without an index hit on a growing table; or a custom program that worked fine on small test data but has not been optimised for production data volumes.
Check ST22 for the program and the point of termination — the call stack shows where the program was when the timeout hit. Use ST05 (SQL Trace) to identify missing indexes or full table scans. Review the SELECT statement and add appropriate WHERE conditions or hints. For reports with large selections, add parallel processing or break the selection into time-bounded chunks. Consider increasing rdisp/max_wprun_time for background jobs if the job is legitimately long-running.
Quick Info