The SAP System differentiates between two types of request when printing:
● Spool request: A spool request is a document for which a print function has been selected. However, it has not yet been output to a printer or another device. The output data for the print document is stored partly formatted in a data store until an output request is created, that is, until it is sent to a particular output device.
The spool system uses a spool request to store the print data temporarily and to access it. The data is stored in a temporary format. You can also display the print document.
The system automatically assigns a 10-digit ID number to a spool request.
● Output request: From the point of view of the SAP spool system, an output request outputs the print data of a spool request to a particular output device.
Multiple output requests may exist for a single spool request. Each represents an instance of the output of the same spool request. Each of these output requests may have different attributes, such as the target printer or number of copies.
By differentiating between spool request and output requests, the spool system provides a means of storing the data temporarily.
Showing posts with label Spool Management. Show all posts
Showing posts with label Spool Management. Show all posts
Monday, July 28, 2008
Exporting the Contents of Spool Requests
You want to export the contents of a spool request in one of the following ways:
● As a text file to the SAP GUI working directory
● Unconverted or as a table, RTF, or HTML to a directory of your choice
● As a PDF file to a directory of your choice
Exporting to the SAP GUI Working Directory
If you are exporting large quantities of data, downloading the spool request as a text file to the SAP GUI working directory is a good solution.
Choose Spool Request -> Forward -> Export as Text.
The entire text is stored in your SAP GUI working directory in ASCII format.
A file of this type is named using the following pattern:
.txt
Note : You require appropriate authorization from your administrator for this function.
Exporting Unconverted or as a Table, RTF, or HTML to a Directory of Your Choice
The contents of the spool request are first displayed. You then download the contents in the format of your choice to a directory of your choice.
1. Select the spool request to be exported and choose Display Contents.
2. For SAPscript/Smart Forms documents, activate the list display by choosing Goto.
3. Choose System -> List -> Save -> Local File.
4. Select a format and confirm your choice.
5. Select a directory and save the spool request.
By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto -> Display Requests -> Settings and making the desired entries in the Display Area group box.
Exporting as PDF File
You want to export the contents of a spool request as a PDF file to a directory of your choice, and print the file. The PDF file contains the print data in the format in which it will be output by the printer.
The following procedure is irrelevant when printing PDF-based forms, since a PDF file is already returned with this method.
Note :You also require authorization from your administrator to run this report.
The PDF file is generated as follows with report RSTXPDFT4:
1. Generate a spool request from the document to be printed.
2. In transaction SE38, start report rstxpdft4.
3. In the displayed window, enter the spool request number and the directory in which
the PDF file is to be stored.
Leave the Download PDF File option selected. Choose Execute.
4. In the next window, confirm or change the path where the file is be stored.
Save your entries.
5. The system displays a log from which you can see whether the report was successfully
performed.
You can then open the file from the directory and print it.
Restrictions for Exporting as a PDF File
● The PDF conversion only supports true bar codes for Smart Forms, which were generated with the new bar code technology with SAP NetWeaver 2004. In all other cases, the bar code is only simulated.
● PDF conversion, especially of ABAP lists, is slower and is therefore not suitable for mass printing. However, you can speed up the conversion to PDF using the FASTLISTCONV option in report RSTXPDF3.
● The font selection for ABAP lists is predefined in the PDF converter and cannot be changed.
For more information about constraints, see SAP Note 323736 on the SAP Service Marketplace.
● As a text file to the SAP GUI working directory
● Unconverted or as a table, RTF, or HTML to a directory of your choice
● As a PDF file to a directory of your choice
Exporting to the SAP GUI Working Directory
If you are exporting large quantities of data, downloading the spool request as a text file to the SAP GUI working directory is a good solution.
Choose Spool Request -> Forward -> Export as Text.
The entire text is stored in your SAP GUI working directory in ASCII format.
A file of this type is named using the following pattern:
Note : You require appropriate authorization from your administrator for this function.
Exporting Unconverted or as a Table, RTF, or HTML to a Directory of Your Choice
The contents of the spool request are first displayed. You then download the contents in the format of your choice to a directory of your choice.
1. Select the spool request to be exported and choose Display Contents.
2. For SAPscript/Smart Forms documents, activate the list display by choosing Goto.
3. Choose System -> List -> Save -> Local File.
4. Select a format and confirm your choice.
5. Select a directory and save the spool request.
By default, only the first 10 pages of a spool request are saved in a file. You can increase the number of pages to be saved by choosing Goto -> Display Requests -> Settings and making the desired entries in the Display Area group box.
Exporting as PDF File
You want to export the contents of a spool request as a PDF file to a directory of your choice, and print the file. The PDF file contains the print data in the format in which it will be output by the printer.
The following procedure is irrelevant when printing PDF-based forms, since a PDF file is already returned with this method.
Note :You also require authorization from your administrator to run this report.
The PDF file is generated as follows with report RSTXPDFT4:
1. Generate a spool request from the document to be printed.
2. In transaction SE38, start report rstxpdft4.
3. In the displayed window, enter the spool request number and the directory in which
the PDF file is to be stored.
Leave the Download PDF File option selected. Choose Execute.
4. In the next window, confirm or change the path where the file is be stored.
Save your entries.
5. The system displays a log from which you can see whether the report was successfully
performed.
You can then open the file from the directory and print it.
Restrictions for Exporting as a PDF File
● The PDF conversion only supports true bar codes for Smart Forms, which were generated with the new bar code technology with SAP NetWeaver 2004. In all other cases, the bar code is only simulated.
● PDF conversion, especially of ABAP lists, is slower and is therefore not suitable for mass printing. However, you can speed up the conversion to PDF using the FASTLISTCONV option in report RSTXPDF3.
● The font selection for ABAP lists is predefined in the PDF converter and cannot be changed.
For more information about constraints, see SAP Note 323736 on the SAP Service Marketplace.
Sunday, March 30, 2008
SAP Printing Methods
Local Printing (Access Methods C and L)
Use local printing if the host spool system (operating system spooler) and the spool work process of the SAP System are on the same host.
• It is irrelevant whether the printer is directly connected to the PC or whether it is a shared network printer.
• The printer must be defined at operating system level of the spool server.
Access method C: Microsoft Windows NT, Microsoft Windows 2000;
Access method L: UNIX
Define the output devices in the SAP spool system.
To do this, create device definitions for the output devices in transaction SPAD (choose the Output Devices pushbutton ® Output Device menu ® Create/Create Using Template).
1. Specify the host system on which the spool server (application server with a spool work process) is running, as the spool server of the output device.
1. In the Access method field, choose method L for a UNIX host.
2. For a Microsoft Windows NT/2000 host, choose access method C. other Microsoft Windows operating systems are not suitable for local printing, as you cannot set up a spool server on them.
Remote Printing (Access Methods S and U)
Use remote printing if you are printing over a network; that is, when the host spool system (operating system spooler) and the spool work process of the SAP System are on different hosts.
Access Method U: UNIX systems; Microsoft Windows system (using a TCP/IP Print Server and SAPlpd)
Access Method S: Microsoft Windows systems (using SAPlpd)
To set up the print architecture for remote Microsoft Windows PC printing, follow the procedure below:
1. To use SAPWIN/SWIN, install and start the SAPLPD transfer program on a Microsoft Windows PC.
SAPlpd is installed with the SAP GUI frontend software.
If you are using Microsoft Windows NT/2000, remote printing can also be implemented using the TCP/IP Print Server.
SAPlpd and TCP/IP Print Server accept the data stream and forward it to the host spool system (operating system spooler).
2. Define the printers you want to use in the Microsoft Windows spooler.
You can use both locally connected and shared network devices.
3. Define the output devices in the SAP System.
To do this, create a device definition for the PC output device in transaction SPAD (choose the Output Devices pushbutton ® Output Device menu ® Create/Create Using Template).
1. • Specify the host system on which the spool work process is running, as the spool server of the output device.
2. • For printing using SAPlpd, choose Access method U (Print on LPDHOST using Berkeley protocol) or S (Print on LPDHOST using SAP protocol). For printing using the TCP/IP Print Server, you can only use access method U.
It is irrelevant whether the printer is directly connected to the PC or whether it is a shared network printer.
Frontend Printing on Local Printers
Prerequisite
In addition to the general print authorizations, every user requires the following authorizations for frontend printing:
• Authorization object S_SPO_DEV, authorization field SPODEVICE, authorization %LOC
• Authorization object S_RFC:
Field Value
RFC_TYPE FUGR
RFC_NAME LPRF
ACTVT 16
Use local printing if the host spool system (operating system spooler) and the spool work process of the SAP System are on the same host.
• It is irrelevant whether the printer is directly connected to the PC or whether it is a shared network printer.
• The printer must be defined at operating system level of the spool server.
Access method C: Microsoft Windows NT, Microsoft Windows 2000;
Access method L: UNIX
Define the output devices in the SAP spool system.
To do this, create device definitions for the output devices in transaction SPAD (choose the Output Devices pushbutton ® Output Device menu ® Create/Create Using Template).
1. Specify the host system on which the spool server (application server with a spool work process) is running, as the spool server of the output device.
1. In the Access method field, choose method L for a UNIX host.
2. For a Microsoft Windows NT/2000 host, choose access method C. other Microsoft Windows operating systems are not suitable for local printing, as you cannot set up a spool server on them.
Remote Printing (Access Methods S and U)
Use remote printing if you are printing over a network; that is, when the host spool system (operating system spooler) and the spool work process of the SAP System are on different hosts.
Access Method U: UNIX systems; Microsoft Windows system (using a TCP/IP Print Server and SAPlpd)
Access Method S: Microsoft Windows systems (using SAPlpd)
To set up the print architecture for remote Microsoft Windows PC printing, follow the procedure below:
1. To use SAPWIN/SWIN, install and start the SAPLPD transfer program on a Microsoft Windows PC.
SAPlpd is installed with the SAP GUI frontend software.
If you are using Microsoft Windows NT/2000, remote printing can also be implemented using the TCP/IP Print Server.
SAPlpd and TCP/IP Print Server accept the data stream and forward it to the host spool system (operating system spooler).
2. Define the printers you want to use in the Microsoft Windows spooler.
You can use both locally connected and shared network devices.
3. Define the output devices in the SAP System.
To do this, create a device definition for the PC output device in transaction SPAD (choose the Output Devices pushbutton ® Output Device menu ® Create/Create Using Template).
1. • Specify the host system on which the spool work process is running, as the spool server of the output device.
2. • For printing using SAPlpd, choose Access method U (Print on LPDHOST using Berkeley protocol) or S (Print on LPDHOST using SAP protocol). For printing using the TCP/IP Print Server, you can only use access method U.
It is irrelevant whether the printer is directly connected to the PC or whether it is a shared network printer.
Frontend Printing on Local Printers
Prerequisite
In addition to the general print authorizations, every user requires the following authorizations for frontend printing:
• Authorization object S_SPO_DEV, authorization field SPODEVICE, authorization %LOC
• Authorization object S_RFC:
Field Value
RFC_TYPE FUGR
RFC_NAME LPRF
ACTVT 16
Subscribe to:
Posts (Atom)
