SPOOL
AND PRINTING
The spool request
contains device-independent print data and includes administrative information
(such as author,date, number of copies) and the actual print data. Only when
the spool request is to be output on a particular device is an output request created.
The device-independent print data from the spool request is converted to the
printer language that the selected output device understands.There can also be
several output requests for one spool request.The actual document content of a
spool request is stored in TemSe (for temporary sequential objects), for which
you define the storage location with the profile
Parameterrspo/store_location.
Valuedb (the default value): Spool requests are stored in database table TST03 (Advantage:
backup as part of the database).
ValueG: Stored at operating system level in the global directory (advantage: performance).
Note: If a printer
cannot be controlled at operating system level, it cannot be used from the SAP
system, either.
Local Printing
SAP users can output documents on their local printers using front-end
printing. These local printers do not need to be individually defined in the
SAP system.
Remote Printing
With remote printing, the spool work process and operating system spooler
are running on different hosts.Network printers provide their own operating
system spoolers and are directly connected to a computer network.
We'll all be familiar with that moment before an important meeting; you're at the printer to collect a print job but instead find yourself sifting through piles of paper trying to locate your document in amongst those of your colleagues and goodness knows what else. 3dm8
ReplyDelete