SPOOL WORK PROCESS

Spool Process:
It is the Only Process that is used to output the documents to a Printer, fax, email etc..
Spool Work Processes are created by using parameter risp/wp_no_spo=1
it is possible to configure more than one spool work process based on available resources.
Spool Process Work Flow:
User Submits the request to print a Document.
  1. The Dialog Process handles the request and print directly or schedules to print in the background.The Print requests are stored in the TemSe(Temporary Sequential Files)
  2. Temporary Sequential Files are stored either at File System or at database Level which is defined by parameter rspo/store_location. rspo/store_location=”G” or ‘DB’ G means global directory stores the TEMSE in /usr/sap/SID/SYS/global db mean the Tables TST01 and TST03.(TST01 Contains Print Attributes and TST03 Contains the Spool Data to be Printed) Due to Spool in DB the DB Size Increases, as a Result, the backup time increases and Tapes may not fit with the data for Smaller Organizations File System(300mb-500mb) is fine but Medium and Large Size Organizations “DB” is recommended. If the OS is crashed there may be an inconsistency between OS restore and DB Spool Files.
  3. The Print Requests which are stored in TemSe are called as Spool Requests.
  4. The Spool requests are converted into Printer Specific output requests using a Spool Work Process
  5. The output requests are printed in the Printer.
Why a dedicated Spool Process is required for Printing???
DIA and Background are designed for interactive and background Processing. when they are asked to print then they need to identify the Printer, Printer Model, Printer Driver, Printer Tray, Print Format, Print Character and Other Attributes.
These tasks are performed by a dedicated Spool Process.
The Spool Requests generated by Dia and BTC are displayed in SP01/SP02
The Output requests generated by Spool Process are displayed in SP01. Access Methods:
  1. It specifies How the Spool Work Process Formats/Converts/transforms/ transfers the Spool request into Printer Specific Output Request.
Local Access Method:
  1. If the Spool Work Process performs the formatting locally on the Application Server then it is called LAM
  2. If the Spool Work Process(server) is Configured in Unix System then the Local Access Method “L”(lp & lpr) is used.
  3. If the Spool Work Process(server) is Configured in Windows System the Local Access Method “C” is used(direct operating system call)
Remote Access Method:
  1. If the Spool Work Process performs the formatting Remotely on a Printer Server then the Application Server then it is called RAM
  2. If the Spool Work Process(server) is Configured in Unix System then the Remote Access Method “U” is used(Unix Berkely Protocol)
  3. If the Spool Work Process(server) is Configured in Windows System then the Remote Access Method “S” is used(SAP Specific Protocol)
Front Access Method:
  1. If the Print Request is given to a Desktop/Laptop Printer then it is referred as Front End Printing(method F)
  2. If more then one Printer is connected then Print by Control Technology “G” Access Method will be Used.
Printers are defined in SPAD.
These are referred as output devices.
Defining a Printer:
Execute SPAD
Click on Output Devices Display
Click on Change and Click on Create
Specify the Printer Name and Printer Short Name like(LB01, LP01, BC01, CP01)
Provide the Device Type Attributes:
Device Type:(Provides the Printer Model–>it specifies that printer is known as SAP System and Printer Driver is available in the System.
Select the Available Device Type from the displayed list
I am not able to display the printer device in the List???
Update the Device List from SAP Market Place using Note 1036961 which provides the Latest Device Types in the XML File.
Firstly check whether the printer is available and recognized in SAP System.Else Refer to the sap Note Number 1100779 for PVP(Printer Vendor Program).
Update Device Types:
Each Vendor has a Specific Note with Device Type Drivers which can be downloaded and Transported into SAP System.
Ex: Download Dell Drivers using 1135033 (devicetypes.zip) and Import into SAP System.
if the device type is not available then select ‘SWIN’ or “SAPWIN”
SWIN makes use of ‘saplpd'(line print daemon) an exe in windows desktops, it comes through SAP GUI.
Spool Server can be Real/Logical Spool Server:
The Application Server(Instance) with at least one Spool Work Process.it is also called as Real Spool Server.
Logical Spool Server:
It does not exist, but points to one or more Real Spool Servers. These are used for Load Balancing and Fail over.
Define Logical Spool Server in SPAD by assigning a mapping server and alternate server.
Execute SPAD–>Select Spool Servers–>Display–>Change–>Define Spool Server–>Select Logical–>Specify the Alternate and Mapping Server.Save.
The Real Spool Servers are displayed in Thick Green Colour
The Logical Spool Servers are displayed in light Green Colour
Authorization Group: to Provide Access to the Printer. it Prevents access to sensitive Printers. Specify the Model, Location, and Message Specific to the Printer.
Specify the Access Method(Local, Front end, Remote)
Each Print Request has to be formatted by the spool work process based on the Printer. So configure Logical Spool Servers when more than one real spool servers are available.
Select the option:
Do not Query the out spooler for the status.
The spool work process keeps track of print requests sent to the host spool system to be able to update the status of the requests in the SAP system.
it runs periodically(1min or 60 sec) to get the status without handling the Queue.
Specify the output Attributes and the Printer Tray Info.
Select process requests sequentially if the print order is mandatory. A dedicated process prints the request, else multiple spool work process prints the request irrespective of the Order(Sequence).
Spool Request Statuses:
when the Spool requests are created/generated by Dialog/Background Process the Status is ‘+’.(-) the output Request does not exist.
(Waiting): Waiting for the Spool Work Process to format into output request.
(Processing): The Spool Requests are processed and being formatted by Spool Process
(Printing): The Output Requests are in the process of Printing, the Printing status remains for 60 seconds and the status is updated as canceled/ finished.
(Finished/completed): The Request is printed successfully.
(Problem): The Request is printed and the output contains minor errors such as page format, character set etc..
Error: Print is not Delivered.Error Indicates a severe error such as a network error. The requests have not printed and remain in the spool system until they are deleted or until they reach their expiration date and are deleted during a reorganization.(RSPO0041/1041)
Spool Table Overflow: TemSe Overflow:
Generally, the Spool Numbers are between 0 to 32000.
This Spool range is defined in SNRO using the Spool Number Range Object SPO_NUM
Execute SNRO–>Specify the SPO_NUM–>Click on Number Ranges–>Change Intervals–>increase value to 999999. When this Number is reached the Spool Overflow Occurs. Spool Reorganization
Delete the Old Spool requests using the reports RSPO0041/RSPO1041.
Check the Consistency of the Spool by using the report RSPO0043/1043.
Check the Spool Memory Usage by using SP12. it displays the total spool volume based on Client , User, Logs etc…
Execute SPAD–>Extended Admin–>Delete OLD Spool request/TemSe Consistency Check .
A User Complains that he could not print the Document.
  1. Check whether spool requested generated in SP02(ask a user to check) or check in SP01 as Spool Admin.
  2. Check whether a printer is on,toner/cartridge/ available, the print tray is available with papers, the print is given to the right printer and tray.
  3. Check whether a printer is reachable over the network, check printer device is available/printer name is available in the device list etc..
  4. Check the User has necessary Authorizations to print to that device.
  5. Check whether saplpd(sap line print daemon) is working in the workstation.
  6. Advice the User to Print to alternate printer from SP02
  7. Advice the User to route print request output to some other user for print.
  8. Advice the User to route the request to other Users Inbox(User can print using SBWP)
  9. Change the priority of the Printing using SP01/SP02
  10. Check whether Desktop supports/Printer Supports language specific printing
Front End Printing:
The Spool Work Process will be dedicated to desktops if the Front Printing is not minimized by using the parameter rdisp/wp_no_spo_Fro_max=1 or 2.
if this Parameter is not set then regular spool service may be congested.
Configure as many spool processes as possible based on availability of resources.
Note: As an Admin, Do not Print from SP01 for any User unless there is a black and white(email)request from the End User.
SP01 is too sensitive as it provides the output format of the Spool Request.
Set the Option in SU01 for sensitive Users.
Delete the output from print.So, that the spool/out requests are deleted after the output immediately.

Comments

Post a Comment

Popular posts from this blog

ENQUEUE WORK PROCESS

It is used to lock and unlock the Objects during an update.These locks are displayed in SM12 and Held for longer hours until the transaction is committed or rollback.These locks are issued from a lock table which resides in the main memory of the instance where enqueue process is created/located. Enque Processes are configured by parameter rdisp/wp_no_enq=1. Generally One Enque Process for instance is sufficient,more then one is required in a massive update system. The Lock table size on the memory ranges between 4mb to 100 MB(200 MB in the Net weaver 7.3 Systems ) It is defined by parameter enque/table_size=4 to 200 MB. For 4mb of enqueue table size, the Number of lock/owners/objects/arguments can be restricted up to 3715. Enqueue Flow: User submits the Request for an Update. The Dialog or Background Process Handles the Request Dia or BTC Processes communicates with Enqueue Process and obtains a lock on the record so that no other user has to write access to that r...
Read more

DIALOG PROCESS

Dialog Process: It is the only process that is used to communicate with end users Interactively using Classic GUI or Through RFC or through Http Protocol. The Average Response Time for each dialog step is 600 ms.it is displayed through ST03n Each Process can execute up to a maximum runtime of 600 seconds.if any process goes beyond this time an additional time of 60 seconds is given and the process is timed out.(ST22)(it is not mandatory to allocate additional 60 seconds Each Process Serves 5-10 users.(Calculated based on ST07) Each Process Requires 75mb to 300 mb Memory Each Process can Handle the requests that are initiated for background, spool & update and update them in temporary tables. Dialog Process is not restricted to a User and Users are not restricted to a process which is referred as process multiplexing Parameters to configure dialog processes is rdisp/wp_no_dia There should be at least minimum two dialog processes and maximum up to 100 processes. The ...
Read more