Device types:

In SAP R/3 a generic type of device I2SWIN or ZSAPWIN4 is defined besides the types of devices for particular printers, that says something like this: „I do not know anything about on which specific printer will the output be, so I leave all the formatting completely on MS Windows driver". It is obvious that the device type is useful only for output via SAPlpd, thus the access methods F: or S:

For the device type can be in addition to character set (it is possible to create own character set) changed also page formats and control characters i.e. interpretation of commands by specific printer.

Note: ZSAPWIN4 was supplied by SAP ČR for SAP R/3 release 3.1x, but it is fully usable also in higher versions, device type I2SWIN is a part of SAP standard from release 4.0x.

Access methods:

F: Print on the front-end computer

Probably the most widely used and most universal method of printing available form SAP R/3 release 3.1G.

In SAP an output devices LOCL, LOKA or LOCWIN is usually defined with this access method, instead of the queue a keyword __DEFAULT or %DEFAULT% is used.

When selecting output on this device, printing is sent to the user's PC who entered the request, there is SAPlpd program automatically started which take over print job and forward it to default Windows print queue, regardless of whether the printer is local (LPT, COM or USB) or if it's a network printer (Novell Netware, MS Windows, UNIX, JetDirect etc.)

In certain transactions it is possible to choose a non-default print queue, SAPlpd receive the print job not with the keyword __DEFAULT, but with the name of the specific queue. Beware, length of the name is limited to 40 characters I guess, the rest will be cut by SAPlpd and it will report unknown name queue, which can be, mainly for network printers, sometimes a problem.

This access method can not be used when printing is not initiated by user, but it is the result of a process (management reports) e.g. maintenance message, store documents, purchase orders etc. It is also not suitable for large prints in amount of hundreds or even thousands pages especially for economic reasons.

On the other hand an advantage of this method is its universality, it is available practically anytime, there is no need to configure anything, with functional printer available from Windows adjustment of most of the print outputs is not necessary.

S: Printing using SAP protocol

method of printing through a print server running Windows and permanently running SAPlpd (using MS resource kit it is according to note 42268 possible to run SAPlpd on WinNT-2000 as a service), combines the advantages of methods F: a L:, in principle it is possible to make print server from every end PC or contrary to these purposes dedicate one machine, hardware requirements are not particularly high, it is only need to allow access from SAP R/3 server on TCP port 515 or communicate via saprouter.

In SAP for definition of output device with this acces method a hotspool name has to be set (machine, where SAPlpd is runninng) and a name of print queue.

a field for hostspool name is is named as router, previously it was necessary to give the name of either host table or DNS alias, because the field was too short for the IP address, it is now possible to specify both the name and IP address or state string THOST table (transaction SM55).

It is not absolutely necessary to use generic driver I2SWIN or ZSAPWIN4, it is possible to use SAP drive for pro particular printer type, then printing is essentially identical to the method L:, with one small but significant difference: printserver is in LAN and is much more accessible for maintenance and administration, it is not too good define print queue on SAP R/3 application server.

L: Local printing via LP / LPR

Print to a classic UNIX print queue, which must be defined in SAP R/3 application server respectively where the spool process is running, must be allowed to communicate on TCP port 515, saprouter can not be used.

U: Print using Berkeley protocol

Method is essentially identical to L method, the only difference is, that print queue (lpd demon) is running elsewhere than spool proces, direct printing on an intelligent network printer, which have their own service queue.

C: Direct call the operating system

Method available only for installation SAP R/3 on Windows NT respectively spool process can run on a separate application server based on Windows NT or Windows 2000 platform.

There are other methods of access for external output management systems, archiving programs, etc.

Printing with MS Windows driver is a graphical, in case of use dot matrix printers can be very slow, however, the output probably best fits the wysiwyg concept. It is not suitable for printing voluminous reports, among others for the size of the spool file.

Conversely printer-specific drivers should be substantially modify, in fact it is necessary for each group to create or edit page format. This method is particularly suitable for large or frequently repeated print jobs of a few kinds of reports.

Spool is one of the most patched matters, drivers and page formats can vary considerably depending on the level of support packages and output behavior may also be affected by kernel patch level or by SAPlpd versions on front-ends.

Note: everywhere, where the Windows operating system is mentioned, any Win 32-bit OS is meant.

SAP Note Number 894444: Tool for server-based printing on Windows (SAPSprint)