SYSTEM_NO_ROLL
criticalWork Process Roll Area Exhausted
Module: BASIS / Memory
What this means
SYSTEM_NO_ROLL fires when an ABAP work process exhausts its roll area — the memory region used to store the local call stack, local variables, and field symbols. Unlike TSV_TNEW_PAGE_ALLOC_FAILED which relates to internal tables, SYSTEM_NO_ROLL is specifically about the program stack depth and local variable accumulation. Common causes: deeply recursive ABAP programs exceeding the stack; function modules that allocate large IMPORTING or EXPORTING parameters per call; programs that create thousands of local objects without clearing references; or the rdisp/ROLL_MAXFS and rdisp/ROLL_SHM memory parameters being sized for smaller workloads than the current usage pattern.
Check the call stack in ST22 — a recursive call pattern will be immediately visible. Review RZ11 for rdisp/ROLL_MAXFS (total roll area size) and rdisp/ROLL_SHM (in-memory portion). Check SM50 to see if other work processes are also hitting memory limits simultaneously. If the program is recursive, add a depth counter and break recursion into iterative processing. If parameters are large, consider EXPORTING BY REFERENCE instead of BY VALUE.
Quick Info