Solution : https://service.sap.com/sap/support/notes/48284 (SAP Service marketplace login required)
Summary :
In SAP environments, creation of excessive spool requests can lead to performance bottlenecks and errors such as SPOOL_INTERNAL_ERROR, signaled by system messages like "Spool full" or "Spool overflow". This issue typically arises when the system's predefined limit of 32,000 spool requests is reached. To address this, SAP allows for the adjustment of the spool request upper limit post-Release 4.0, with a recommended maximum of 999,999 to facilitate user management. Administrators should modify this setting through transaction SNRO, specifically adjusting the number range for object SPO_NUM. Regular cleanup of outdated spool requests is recommended using jobs RSPO0041 or RSPO1041 to maintain optimal system performance. Monitoring and managing spool usage through RZ20 is also advised to prevent future overflows.
Key words :
human user finds higher numbers difficult, symptom creating spool requests takes, short dump spool_internal_error occurs, spool requests simultaneously held, call transaction snro, delete spool requests, standard sap system, terms spool full, spool number monitor, interval higher
Related Notes :
| 422136 | Incorrect spool assignment for the background step |
| 64333 | Change default value for spool retention period |
| 48400 | Reorganization of TemSe and Spool |
| 41547 | How does report RSPO0041 work? |