The document discusses spool requests in SAP systems. It defines what a spool request contains, where it is stored, and the different spool statuses and their meanings. It also describes which work processes create spool requests and output requests, and the difference between the two. The document then provides answers to common questions about spool overflow issues, how to troubleshoot them, check spool numbers, delete old requests, and define the storage location for spool requests.

1. What are the different Spool statuses and their significance?
This article answers the following queries:
1. What does spool request contain?
2. Where is the spool request stored?
3. What are different Spool statuses and their significance?
4. Which work processes will create spool requests?
5. What is the difference between spool request and output request?
6. Which work process will create output request or print request?
1. What does spool request contain?
ANS: Spool request contains detailed information regarding printer
model, formatting to be done on the data to be output.
2. Where is the spool request stored?
ANS: The spool request that is generated is stored in the
Temse(temporary sequential file)
3. What are different Spool statuses and their significance?
ANS: Spool requests will have different statuses like Completed (The
output request printed successfully) Waiting (Spool request is in waiting
status and spool system has not yet processed the output request and
not yet sent to the host system)
In process (The spool work process is in the process of formatting
output request for printing) Printing (The host spool is in the process of

2. printing the output request Problem (This indicates there are some
minor errors. It means output request printed but contains some errors
like incomplete character set etc)
Error (This status indicates some serious issues such as network error. It
means the requests have not printed and they remain in the spool
system until they are deleted or until they reach their expiration date.
After expiry date, they are deleted by the reorganisation jobs.
Archive (This status is set for spool requests that are sent to an
archiving device. This status means that the spool request was already
processed by the spool system and it is now waiting to be archived)
Time (This status means that the user who has created the spool has
mentioned some specific time for output)
- (This minus status means that the spool request is not yet sent to the
host system and no output request exists)
+ (This plus status means that the spool request is being generated and
it is stored in the spool system)
4. Which work processes will create spool requests?
ANS: Spool requests will be created by dialog or background work
processes. Please note that spool work processes do not create spool
requests
4: What is the difference between spool request and output request?
ANS: Spool request contains detailed information regarding printer
model, formatting to be done on the data to be output. Output request
contains all the data in the format that the printer understands.

3. A spool workprocess formats the data specified in the spool request
and generates the output request. Output request is also termed as
print request.
5: Which work process will create output request?
Ans:Output request will be created by spool work processes.
Spool overflow issues :
what is spool overflow ? How to troubleshoot spool overflow issue ?
1. What is spool overflow ?
2. How to troubleshoot spool overflow ?
3. How to delete old spool requests?
4. How to avoid spool overflow issue?
5. How to check spool numbers?
6. How to set the spool number in SAP?
7. How to define storage location (Temse) of spool requests ?
1. What is spool overflow ?
ANS: Spool request that got generated are stored in a temporary
sequential file called Temse. Please note that these are stored in Temse
because these are not stored permanently. The size of the Temse is
limited by the parameter definition.
The default size of Temse is 32,000 and it can be increased till 2 billion.
However, defining very high value can effect the databasePerformance.

4. Due to limited storage capacity of Temse, when this file got full, this
throws an SAP spool overflow error.
If this happens, customers could not print from SAP. If you check in
SM21 and ST22 transactions, you may encounter some error log or
dumps like
ERROR IN SPOOL call: SPOOL OVERFLOW
SPOOL_INTERNAL_ERROR
System internal error in the spool system
2. How to troubleshoot spool overflow?
ANS:To resolve this spool issue, some of the old spools can be deleted
from the sap system. Goto transaction SPAD. From the initial screen,
navigate to Administration -> Clean_up_spool. Once you click this,
Spool Administration: Delete old spool requests screen will be
displayed.
In that screen, you will be prompted to choose requests for deletion
like
Old spool requests older than the maximum set age, Requests already
printed .All spool requests and enter value for minimum age (in days)
text box. Select the check boxes as per the requirement (eg: delete all
requests already printed and minimum age in days equal to 30 days)
and execute to delete old spool requests, which will clear Temse and
will resolve spool over flow issue. Apart from this there are others ways
of resolving spool overflow issue. They are

5. 1) Run the report RSPO0041 from SE38 transaction to delete old spool
requests
2) Run the report RSPO0043 from SE38 transaction, which checks the
Temse/spool consistency and reorganizes the spool
3. How to avoid spool overflow issue?
ANS: These reports RSPO0041 and RSPO0043 should be scheduled as
background jobs with proper variants on a periodic basis which avoids
spool overflow issue.
You can try to increase the spool numbers from default 32000 to a bit
higher value but please note do not set this too high as it may impact
database performance
Proactive monitoring check can be made in RZ20 transaction to see
how much the fill level of spool numbers is.
4. How to check spool numbers?
ANS: To check spool numbers: Goto RZ20 transaction, navigate to SAP
CCMS Monitor Templates -> Spool System.
Here you can check the status of spool servers and the used numbers
percentage of spool numbers. If you find that used numbers is greater
than 80%, you can manually run above mentioned reports or delete old
spool requests from SPAD tcode as mentioned earlier.
5: How to set the spool number in SAP?
ANS: Using Transaction SNRO (Number range object maintenance) and
object SPO_NUM, you can set the spool number in an SAP system.Once
you provide object as SPO_NUM, click on change icon.

6. It displays another screen. In that screen, click on Number Ranges push
button. It displays another screen "Number range for spooler
numbers". Click on change icon here and set the value of spooler (from
number and to number). Please note that a change request may be
generated here based on the client settings (if automatic recording of
changes is set in SCC4 transaction of the client)
6.How to define storage location (Temse) of spool requests ?
Ans:Every Temse object contains a header in TST01 table and the actual
object. This can be either stored in table TST03 or in file system. You
can set a parameter rspo/store_location in RZ10 to define whether to
store Temse objects TST03 table or in filesystem.
If value G is set to this parameter, it will be stored in filesystem and if it
is db it is stored in TST03 table.