Visit our Google Group Way 2 SAP BASIS


Forum where general Basis related topics are discussed.

Moderators: BASIS24x7, Rashed


Postby moiz7070 »

When a request is made to print a document, a spool request is created. A spool request has two parts:
1. Administrative information (origin, date, author name, logical printer) is stored in the R/3 database
2. The data to be printed is stored in a repository called the temporary sequential database (TemSe).

TemSe data can be stored inside the R/3 database or at operating system level. Profile parameter rspo/store_location (see SAP Note 20176) determines where TemSe is located:
• db stores the data in the database (default)
• G stores the data in an operating system file in the global directory
• Output requests are usually sent to the spool server in the order they were created, but if more than one spool work process is configured, the requests may be printed in a different order.

Local printing
The operating system spooler runs on the same host as the R/3 spool work process.

In Windows NT systems : access method C.

In UNIX systems : access method L.
Local printing is the fastest and most reliable way of printing in R/3

Remote printing
When using remote printing, an R/3 spool work process passes the print-ready output stream to the operating system spooler on a different host. This data transfer requires moving the output stream across a network link.
In UNIX systems : access method U .

Printers having their operating system ( network printer with NIC) : access method U
In Windows systems and other systems without an lpd, SAP provides the program saplpd : access method S for a proprietary SAP protocol or U for the UNIX Berkeley protocol

Frontend printing
Frontend printing allows R/3 users to send output to printers that are defined on their local frontend PCs (access method F)

In Windows systems, the output is sent to program saplpd on the frontend PC.
In other systems (UNIX, Macintosh, ...), the output is passed to the operating system spooler.

You can set an upper limit to the number of spool work processes used for frontend printing using parameter rdisp/wp_no_spo_Fro_max. The default value of the parameter is 1.

Frontend printing only works as long as there is an active connection to the frontend PC. Therefore, frontend printing cannot be used in background processing.

Device type: The type of printer. For frontend printing in Windows systems, the device independent printer driver SWIN can be used to shift processing from R/3 to the frontend PC.

Device class: shows the dialog box with the available device classes.
For printers, which is the most common class, leave this field blank.
A for Archiving flag
F for Fax
T for Telex

Access method: Specifies the data transfer method to the host spooler.

A logical spool server can be mapped to a real spool server or to another logical spool server
• Logical spool servers open up a wide range of further possibilities, such as:
• Spool server switchover
• Workload balancing
• Transporting the printer architecture

Separate the spool printers and servers for the different kinds of print job:
• High volume print (for example, cost-center lists)
• Production print (for example, documents or cover letters)
• Desktop print (for example, SAPoffice documents)
• Test print

Spool server switchover

When creating a real or logical spool server, you can define an alternative spool server. If the normal spool server becomes unavailable, R/3 switches all the devices using this spool server to the alternative. For this strategy to function, you must ensure that all the printers can be driven in the same way by all the spool servers involved.

Workload balancing

When an alternative spool server is defined for a spool server, you can allow load balancing (load comparison). The load on a spool server is calculated from the number of spool work processes, of output requests, and of pages. Load balancing can be activated independently for each logical or real spool server.
Sequential request processing has priority over the load balancing option for spool servers.

Therefore, if a device is configured for sequential processing and it is assigned using load balancing to a spool server, load balancing is ignored for output requests generated for that device.

When deleting a spool request, the system removes:
The spool request itself and associated table entries
The print file
All output requests that were generated for that spool request

To display spool or output requests, call transaction SP01
The status of a spool request is one of the following:
- : no output request for this spool request
Proc. : a spool work process is processing the corresponding output request
Waiting : a spool work process is waiting for a return code from the operating system spool
Compl. : the corresponding output request(s) has (have) been printed successfully
Error : the corresponding output request(s) has (have) not been printed successfully
<F5> : the corresponding output requests have different statuses

A log is written for every unsuccessful output request. You can use the log for error analysis.

You must define a regular schedule for maintaining your R/3 spool database. Regular maintenance tasks include deletion of old spool requests and checking the consistency of the spool database.
To delete old spool requests, run ABAP program RSPO1041 with a suitable variant regularly as a background job.
To perform spool database consistency checks, run ABAP program RSPO1043 with a suitable variant every day

End users have full control over their spool requests in the output controller.

Spool administrators can manage all spool requests through authorization objects S_ADMI_FCD and S_SPO_ACT.

Authorization object S_ADMI_FCD allows the administrator to perform different management tasks, such as spool request administration and output device administration.

Authorization object S_SPO_ACT specifies what actions you can perform on which spool requests.
For example, SPOACTION = BASE, DISP and SPOAUTH = xyz allow you to list and display all spool requests with the authorization field xyz.
Shaik Moiz Ahmed
Terrenos Software Technologies Pvt.Ltd
Posts: 14
Location: Hyderabad

Re: Spool

Postby meetmuqeet »

hi dude
very nice info ,really appreciate you in this kind of posting....
thanks & regards
thanks & regards
Posts: 40

Return to General Basis Forum

Who is online

Users browsing this forum: No registered users and 1 guest

Visit our Google Group Way 2 SAP BASIS