Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Former Member

SAP Spool Overflow

As a Sap Administrator you first notice that for reasons unknown it is taking a long time to create spool requests.
Next, users begin calling and adage that nothing is printing out of SAP.

SAP Error Messages: Spool Full or Spool Overflow

To diagnose the problem, you make a quick check in SP01 which shows that SAP isn’t creating any more spool requests. Soon you discover that SAP is slowing down and transaction SM50 reveals that all of your dialog processes are full.

Checking the system log (Transaction: SM21) and immediately notice that there are errormessages such as short dumps “SPOOL_INTERNAL_ERROR” and “Spool full” or “Spool Overflow”.

SAP Spool request limits
There are limits to the number of spool requests that can be created in SAP. The standard SAP system has a limit of 32000. When this breaking point is arrived at, the above failure messages occur because there are no more free numbers available.

Resolving the “SAP Spool full” issue
Basically two solutions need to implement to resolve this issue.

First you need to run the SAP programs RSP00041 or RSP01041 to delete and free up spool request numbers for new spool requests. Select the appropriate number of days to keep

for each spool type and execute. This step should quickly delete any spool requests that are no longer needed. Rather quickly this will allow new spool requests to be created

and printing will be restored to normal.

i.  Run tcode -> SE38 -> RSP00041 -> Click the Execute button
ii.  Select client (*)n -> for all client
iii.  All the pending spool deleted

Second, you should look at increasing the spool request limit. Use transaction SNRO while logged in to client 000 and adjust the upper limit of interval SPO_NUM. The value can be increased up to 999,999 but is really dependent upon the capacity of the database and the host computer.

To make sure that this error doesn’t appear again, make sure to schedule the program RSP00041 in a batch process. If it is already scheduled, then make sure that you adjust the variant so that it has the proper values. This way you can ensure that there will be enough spool requests available so that you don’t run out before the next time the batch process runs.

The program RSPO0041 required a variant to run. In the variant, we can specify how long you need to retain the spool requests. By default, the standard job SAP_REORG_SPOOL runs this program using the variant SAP&001 which the minimum age of spool requests is 10 days.

You can create new variants and run this job accordingly. If you need to verify this, you can go to SE38 and execute the job RSPO0041. In the next screen, when you click on variants, you will be able to see the default variant SAP&001. You can save new variants from that screen itself. ( Goto >> Variants >> save as variants)

You can use transaction RZ20 to monitor the spool number. If the system ever reaches the specified threshold values an alert will be created to notify you of the problem before your users begin calling.
  RZ20 > SAP CCMS Monitor Template > Spool System > Spool wide > Spool > Spool number

SAP Notes
SAPNote: 48284 – System can no longer create spool requests



1 Comment
Labels in this area