Hi,
Can read the below note that tell about where are spool request saved.
20176 - Where is the spool request saved?
For more info can also check the below note.
| 16513 | File system full - what can you do? | |
| 504952 | Composite note regarding spooling and printing | |
| 11070 | Space requirements of TemSe and spooler |
In general, spool request data is written and read much quicker if it is stored in files rather than in database table TST03. The advantages and disadvantages are described in Notes 11070, 10551 and 20176. Profile parameter: "rspo/store_location".
Make sure that the spooler database does not become too full. Program RSPO0041 is described in Notes 16083 and 41547.
Quite a few printers can be slow in various emulation modes. It may be worthwhile abandoning continuous lines (note 15594). (See Note 15594).
As of Release 3.0A, all users should use the
Option: 'Delete after printing' if possible, to keep the number of simultaneous spool requests in the system to a minimum.
Regardless of the configuration of the R/3 spool system, you can improve spool performance to a certain extent by the way in which you generate spool requests in applications. Performance is better if you create a few large spool requests instead of several smaller ones. The amount of data transferred and the overheads involved with establishing links to the external spool system are reduced. If you can configure your applications in this way (for example, via message control), this should improve the performance of your spooler system.
Thanks
Rishi Abrol