SAPlpd is a transfer program for print output using a Microsoft Windows operating system and is required in the following cases:
· Remote Printing with Microsoft Windows
As the host spool system (Microsoft Windows spooler) and the spool system (application server with a spool work process) are on different hosts with remote printing using Microsoft Windows, the SAP spool system requires an external process that transfers the output requests from the SAP spool server to the Microsoft Windows spooler. This process is provided by the SAPlpd transfer program.
· Local Printing with Microsoft Windows with the device type SWIN
In the case of local Microsoft Windows printing, the SAP spool server (application server with a spool work process) and host spool system (operating system spooler) are on the same host.
The SAPlpd transfer process is only required if you have defined the output devices with device type SWIN. For more information, see Generic Device Type SWIN for Microsoft Windows Printing.
· SAPLPD.EXE and associated files may be updated between SAP releases. You can download the newest version from the SAP Service Marketplace (alias /patches) as described in SAP Note 328252. You can find out about the newest features of SAPlpd by choosing Help ® Display README-file in SAPlpd.
· You can also use the TCP/IP print server under Microsoft Windows NT/2000 instead of SAPlpd, but only for access method U and not for device type SWIN.
· You can use SAPlpd in all Microsoft Windows systems.
· Like the line printer daemon lpd, SAPlpd accepts print data and forwards them to the host spooler.
· SAPlpd also interprets the special SWIN/SAPWIN data stream and converts it to GDI calls for Microsoft Windows. The system then uses the printer drivers that are available for Microsoft Windows and/or the printers.
To be able to use SAPlpd, you must perform the following:
Checking the SAPlpd Working Directory for Work Files