It is the only process that is used to output documents to printer/email/fax/sms. There should be at least one spool work process required by per system.
It is configured by parameter-:
It is also possible to configure as many spool processes as required depending upon the available resources.
Spool can see in SP01 (Global user’s request)
To see TEMSE go to SP12 (Size of the TEMSE objects)
****SPOOL SERVER MEANS THE INSTANCE WITH AT LEAST ONE SPOOL PROCESS****
Dialog process or background process generates the spool requests. These spool requests are converted by spool process into output (printer specific) requests.
The spool processes are defined by parameter rdisp/wp_no_spo there should be at least one spool process for entire system.
It is possible to configure as many spool processes as possible depending upon the available resources.
Users generates the spool requests either by using dialog or background process which are stored in TEMSE (temporary sequential objects)
TEMSE is defined by parameter-:
rspo/store_location=’G’ or ‘db’
G — means global directory in
db — means TST01 and TST03 tables
Spool process reads TEMSE and converts the spool requests into printer specific requests based on access methods.
Specifies how the spool work process transfer data to the host spool system for two printers.
Local Access Method-:
If the printer formatting is performed locally then it is referred as local access method.
Access Method “C”-:
If the spool service is running on a Microsoft Windows NT server and requests for this printer are to be transferred to the local windows NT printer manager.
Access Method “L”-:
If the spool server is running on a UNIX system and output requests for this printer are to be transferred to the local host spooler.
Access Method “F”-:
If the output requests for this printer should be output locally on the user’s pc or workstation.
Remote Access Method-:
If the formatting process is to transfer the output data to the remote host system then it is referred as RAM.
Access Method “U”-:
If the formatting process is to transfer the output data to the remote host system using Beckley Protocol (BSD).
Access Method “S”-:
If the formatting process is to transfer the output data to the remote system (a Microsoft windows pc) using the SAP protocol.
The formatting process transfer the output data to the SAP output processer SAPLPD (line print DAEMON) running on the remote pc.
Spool server means the Instance with at least one spool process. The TEMSE can be stored either in OS/DB.
db(lower case)-: save in the database table TST03.
The spool and TEMSE data are backend up during the normal database backup. The database keeps the various spool and TEMSE tables consistent during a restore.
No additional file system memory is required for TEMSE. No special monitoring required and the db requests are not virus prone.
Writing to the DB is slower than writing to the file system. The ‘temporary’ spool data is always backend along with regular backup, thus increasing backup time.
G (Upper case)-; save in global directory
Data is backed up outside database backup. This means the administration tables TSP01 and TST01 may be inconsistent with files in the file system. This must be corrected using a consistency check, if a backup is restored after a disk crash the global directory has to be mounted to all the instances.
SP01-: is used to monitor the spool requests by administration.
SP02-: is used to monitor the user own spool requests.
The STATUSES of spool work processes-:
- Not yet sent to the host system (no output request exists)
- Spool requested being generated (stored in spool system)
Writing spool system has not yet processed output requests not yet sent to host systems.
In PROC — the spool work process is formatting the output requests for printing.
Printing the host spool is printing the output requests.
The output request printed successfully. In the system where the spool system does not receive any information about the host spool the status changes to “COMPL” as soon as the output request is sent to the host spool.
Problem indicates a minor error such as an incomplete character set. The output requests printed, but the output probably contains errors.
Error indicates a server error such as a network error. The request has not printed and remains in the spool system until they are deleted or until they reach their expiration date and are deleted.
TEMSE by default stores 32000 and increased to any number (up to 2 billion). Use the transaction SNRO to increase the number range of SPOOL requests. Select the object SPO_NUM and increase the interval from 32000 to 2000000. But ensure that spool requests are reorganized from time to time else it impacts on spool performance of the system.
Transaction SPAD (SPOOL ADMINISTRATION) is used to define printers.
- Each printer has to be defined in the SAP system. So that they can be initiated through programs either in the dialog/BTC mode.
- Execute SPAD àSelect output deviceàclick on changeàclick on createàspecify output device name:
LP_12_HR_RW/PS_02_HR_CW (identify the printer as the naming convention to identify the printer uniquely in the organization)
Specify the Shortname: LP01/BC01/PS01/IN01/PO01/LB01
Device type: Select the device type based on vendor/model/type.
Spool Server: It can be real or logical.
Device Class — Standard printing/Mass printing.
Specify authorization group to assign the printer to the users.
Model/Location and Message [HP2000, hightechcity_quad 3-5, please print only shipping order]
Specify the access method-: LOCAL/REMOTE/FRONT END
For remote specify the name of the host where formatting is performed.
Query Status through Polling-:
The Spool process waits for the status of the printing and updates it as finished/problem/error. If this option is not checked then the spool process queries the printer for every 60 seconds for the print status which is a performance bottleneck (It only works on querying until the print is completed and does not handle any other tasks)
- Select the cover page/Language etc.
- Process request sequentially-: If the sequence is mandatory then select this option else leave it, so that the performance improves by serving the some request with multiple spool processes.
Front End Printing-:
- The Spool process formats the Spool requests into output request and its process is dedicated to the user desktop until the print is completed.
- Spool process congestion occurs when more processes go into Front End Mode.
- Configure parameter rdisp/wp_no_spo_Fro_max to either 1 or 2
- If front end printing is done by the spool service, the number of Spool work processes used for processing front end jobs can be limited to keep the regular spool service available even if there is a heavily load produced by front end jobs.
- Spool requests are maintained in SP01 and users can monitor their own requests using SP02 [Statusàown spool requests]
The major advantage and disadvantage of the spool requests is the output can be displayed in SP01 before it is printed to the printer [Security wise sensitive information should not be displayed]
The Spool requests remains in the system [TEMSE] unless they are deleted by a standard background jobs
- Use transaction SU01 — delete the output requests immediately after printing.
- But this option causes performance bottleneck because Spool process need to delete the request after output without handling the queue.
- SAP recommends deleting the requests by using the standard background jobs.
- This is used when the Spool requests are more sensitive (like pay slip, payments etc.)
- The Spool requests remain in TEMSE and used to print as many times as possible by the owner or basis consultant.
SP01 MONITORING AND ADMINISTRATION-:
- The spool requests can be printed to any other alternate printer, change the priority of printing, forward to any other users, number of copies etc.
- Spool requests are displayed based on user, date and time, client etc.
THE FOLLOWING ARE THE SPOOL REQUSTS STATUSES
- ‘-‘ : not yet sent to the host system [no output request exists]
- ‘+’ : Spool requests being generated [Stored in spool system i.e., TEMSE]
- Wating-: Spool system has yet processed output request; not yet sent to the host system.
- In proc-: The spool work process is formatting the output request for printer.
- Printing-: The host spool is printing the output requests. If the SAP Spool system does not receive any status information from the host spool, this status is displayed for approximately 1mm. The system then sets the status to “COMPL” [completed] or Error.
- Compl-: The output request printed successfully. In systems where the Spool system does not receive any information about the host spool, the status changes to “COMPL” as soon as the output request is sent to the host spool[RAM]
- Problem-: Indicates a minor error such as a incomplete character set. The output request printed, but the output probably contains errors.
Check whether correct characters set is selected.
Check whether printer supports the character set.
Check whether proper device type is available.
8. Error-: Indicates a server error such as a network error. The requests have not printed and remains in the Spool system until they are deleted or until they reach their expiration date and are deleted during reorganization.
Check the printer status.
Check the printer server status.
Check the logistics such as printer, page, paper jam, toner, power off [out of SAP]
Thanks Samar ,
Really Nice Document .
doc is very nice.
it is step to stop back-end process for spool printing .
Thanks a lot for sharing this detailed information... great help and easily understandable...