后台作业,Spool立即打印问题

今天在客户身边的同事，测试JOB作业打印report时发现report都还在spool中待机中，没有即时打印。 立即打印参数(http://help.sap.com/saphelp_nw04/helpdata/en/9f/dba56d35c111d1829f0000e829fbfe/content.htm)已设，前台跑是没问题的。最后查出来，output device是非网络打印机。(SPAD)
有两条NOTE可以参考

Note 352739 - Dunning: Print immediately
Summary

Symptom
Even though the 'Print immediately' indicator is set for the dunning notice printout, immediate printing does not occur.
The following applies, irrespective of this correction: If the selected printer is a local printer, immediate printing is not possible from a background job.
For information about front-end printing, see Note 128105 also.
Note the difference between:
1. The 'Start immediately' indicator: this refers to the print program rather than the print output. The print program is either scheduled for a future point in time or started immediately.
2. The 'Print immediately' indicator in the spool control: If the indicator is set, the letters are printed immediately and a separate spool request is created for every letter. If the flag is not set, you have to start the print request, and only one spool request is created.

Note 128105 - Frontend printing (collective note)
Summary

Symptom
This note describes how frontend printing works.


Other terms
LOCL, frontend printing, PC print, control, control technology

Reason and Prerequisites
1. What does "Frontend printing" mean?
Frontend printing involves data, which needs to be printed, being sent using the GUI connection of the user to a printer that is installed on the frontend of the user. Usually, a default printer is involved.


Only a general printer definition is required in the backend system, since you are not required to define the names or IP addresses of the individual computers. You can use dynamic IP addresses (Dynamic Host Configuration Protocol) in frontend printing, unlike in network printing from the SAP System.


2. Availability
As of Basis Release 4. 6C, access method 'G' is available and replaces the previous method using access method 'F'. If you use access method 'G', frontend printing is also possible on non-Windows frontends. If you use a terminal server, no other settings are necessary. For more information, see Note 821519.


Access method 'F' is used in earlier releases (lower than 4.6C). As of Release 4.6C, access method 'F' is no longer developed, and no more corrections will be delivered.
Solution

1. Setting up frontend printing
To use access method 'G', see the prerequisites in Note 821519.

a) Definition of an output device
Define a general output device for frontend printing using transaction SPAD. You can use SAPWIN (or language-dependent SAPWIN versions) as a device type for Windows frontend computers. You can use any other device type, provided that all printers that you use can process the relevant format.
You cannot use SAPWIN on Non-Windows platforms, but you can use device type POST2 (for example), depending on the print administration setting.
On Windows platforms, enter __DEFAULT as the host printer, while on non-Windows platforms, enter a printer name that is standard on all frontend computers.


b) Authorizations
The following authorizations are required for frontend printing:
- Device authorization for the object S_SPO_DEV
(The following authorizations are only necessary for access method 'F':)
- Device authorization for device '%LOC' for the object S_SPO_DEV
- Authorization for the object S_RFC:
RFC_TYPE 'FUGR'
RFC_NAME 'LPRF'
ACTVT 16


c) Restrictions
Since frontend printing uses the local GUI connection, it is generally unsuitable for the output of large or particularly time-critical documents.

Frontend printing always requires an existing GUI connection. Therefore, you cannot use frontend printing to output the spool output of a background job.

Frontend printing is also impossible if you use RFC to go from your current mode into a process in which you first create the output request.


To print using the Windows Terminal Server (WTS), see Note 150533 also.

For further information about frontend printing using the SAPGUI for HTML, see Notes 351230 and 7721683.