No Spool Request Generated: Analyzing a Spool Dump

Procedure

If the spool system is unable to generate a spool request when a user selects Print, then the spool program logic terminates the program. All the details about the abnormal termination are recorded in an ABAP short dump. Use transaction ST22 to call the runtime error analysis to analyze the program termination or to obtain information before you call the SAP Hotline. The short dump includes the name of the affected user, the time and date, and a description of the error.

Monitor of the Spool System or you can find error information in the system log (transaction SLG1) and in (transaction RZ20).

Example

You want to create more than 32000 print requests in the system. In the SAP default, the number of print requests is restricted to 32000. If you reach this limit, no free number can be found and the short dump SPOOL_INTERNAL_ERROR appears where the message 'Spool Full' or 'Spool Overflow' appears in the dump itself or in the system log. In this case, the monitor of the spool system shows that 100% of the spool numbers are occupied. You have two options for reacting to this problem:

You have your print requests deleted regularly in the background.
You extend the numbers that can be granted.

SAP Printing Guide Start Page