How can you configure the printer? Explain the spool admin? The configuration of the spool system is a system administration task. The central tool for this is transaction SPAD.

To create an output device, choose Output Devices on the Devices / Servers tab page. If there is already a large number of devices in your system, you can restrict the output list in the field next to the button (for example .PR*.).Important information for a device:ü Output deviceName, maximum of 30 characters long (case-sensitive).

ü Short nameFor internal system purposes (can be automatically generated).

ü Device typePrinter model/family (more information about this below). The device type SWIN transfers the SAP system format to the Microsoft Windows printer driver. This is useful, for example, if various printers are used for front end printing in a Microsoft Windows environment.

ü Spool serverSAP application server with spool work processes or logical server.

ü LocationFor example, building and room number (so that users can find their output).

ü MessageUsed to temporarily override the location (such as .Is currently in maintenance.)

ü Lock printer in SAP systemOutput requests for printers for which this indicator is selected are created but not transferred to the printer. The user receives the message ...no immediate printing.

ü Host spool access methodHow does a spool work process contact the operating system spooler?

ü Host printerName of the printer at operating system level. Note that this name is case-sensitive. Under Microsoft Windows, there must not be a space in the printer name, and network printers are addressed using their UNC names (in the format \\R12345\P42). The specification __DEFAULT calls the defaultMicrosoftWindows printer (for example, for front end printing in a Microsoft Windows environment).

ü HostOnly for local printing, is calculated automatically from the spool server.

ü Destination hostsOnly for remote printing. Name of the host on which the operating system spooler (such as lpd or saplpd) is running.

SAP Spool number administration and common issues

SAP has a default spool request number of 32,000, and default clean up job SAP_REORG_SPOOL does not clean up output request by background job.

You can view the status of your SPOOL numbers through:

1. Transaction SNRO > Table SPO_NUM > Number Ranges (button) > StatusNote: Do not change anything unless you are sure or this is in sync with a parameter change limit.

2. RZ20 > SAP CCMS Monitor Template > Spool System > Spool wide > Spool > Spool number

HOW TO CLEAN UP SPOOLI. Make sure that you have SAP_REORG_SPOOL job enabled. This uses the SPOOL reorg program RSPO0041 that deletes old spool requests. See link below for more details: II. Configure a custom SPOOL purge.It is highly recommend to create a new custom variant, e.g. ZDELETESPOOL60 with following parameters:

1. Client number: 0002. Username: Any user who can create variant with SE38 and modify job in SM373. Variant name: ZDELETESPOOL604. Expiry Date - Requests past expiration date: Disable5. Minimum age in days: 606. Completed req. with min. age: Disable7. All requests with min. age: Enable8. Do you want to log everything?: Disable9. Log instead of dialog boxes?: Enable10. Log only without deletion?: Disable11. COMMIT all...Spool requests: 1,000 to 10,000

Step 1, 2, and 4 are important not to change. 

To create a variant:

1. Go to SE38 and enter RSPO0041. 2. Choose Variants in radio button 3. Click Display4. Enter the UNIQUE name of a new variant. example ZDELETESPOOL605. change other value according to your requirement.

To create a job:

Execute transaction code SM37. 1. Find SAP_REORG_SPOOL2. Modify job SAP_REORG_SPOOL in any client number. 3. Modify the job and replace variant SAP&001 (default) with ZDELETESPOOL60. 4. Duplicate the this job, and execute it immediately. 

In a typical spool size of 1 GB, it takes about 15 min to cleanup. 

Use sm37, sp12 - TemSe data storage, and spad - print request overview - client to monitor the progress

III. Common errors:

If after cleanup and you encounter one of these errors:

A. SPOOL_INTERNAL_ERRORB. spool overflow (assume you have not adjust max spool number before)C. ...no more free spool request numbers...

SAP note 48284 mentioned that change:

1. In Client 000, execute transaction SNRO -Number Range button - Interval. Default numbering range is 100 - 32,000 (which can print up to 31,900 requests)To do this:Transaction SNRO > Table SPO_NUM > Number Ranges (button) > Modify > change the max limit to desired number.

2. Define profile parameter rspo/spool_id/max_number up to 2^313. Define rspo/spool_id/loopbreak to same value as above. This is optional.

We don't see a need to have more than 31,900. Well if this happens, do the things above.

Indirectly, database table size going to grow to few GB, and indirectly slowing down all print request, as well as unnecessary database size

If custom variant not defined in Client 000, then background job SAP_REORG_SPOOL will shown following error. Create the custom variant in Client 000 to fix it.

what is spool overflow ? How to troubleshoot spool overflow issue ? This article answers the following queries :

What is spool overflow ? How to troubleshoot spool overflow ? How to delete old spool requests ? How to avoid spool overflow issue ?

How to check spool numbers? How to set the spool number in SAP ? How to define storage location (Temse) of spool requests ?

What is spool overflow ? :

Spool request that got generated are stored in a temporary sequential file called Temse. Please note that these are stored in Temse because these are not stored permanently. The size of the Temse is limited by the parameter definition.

The default size of Temse is 32,000 and it can be increased till 2 billion. However, defining very high value can effect the database performance. Due to limited storage capacity of Temse, when this file got full, this throws an SAP spool overflow error.

If this happens, customers could not print from SAP. If you check in SM21 and ST22 transactions, you may encounter some error log or dumps like

ERROR IN SPOOL call : SPOOL OVERFLOW SPOOL_INTERNAL_ERROR System internal error in the spool system

How to troubleshoot spool overflow ?

To resolve this spool issue, some of the old spools can be deleted from the sap system. Goto transaction SPAD. From the initial screen, navigate to Administration -> Clean_up_spool. Once you click this, Spool Administration : Delete old spool requests screen will be displayed.

In that screen, you will be prompted to choose requests for deletion like

Old spool requests older than the maximum set age Requests already printed All spool requests

and enter value for minimum age (in days) text box.

Select the check boxes as per the requirement (eg:  delete all requests already printed and minimum age in days equal to 30 days) and execute to delete old spool requests, which will clear Temse and will resolve spool over flow issue.

Apart from this there are others ways of resolving spool overflow issue. They are

1) Run the report RSPO0041 from SE38 transaction to delete old spool requests

2) Run the report RSPO0043 from SE38 transaction, which checks the Temse/spool consistency and reorganizes the spool

How to avoid spool overflow issue ?

These reports RSPO0041 and RSPO0043 should be scheduled as background jobs with proper variants on a periodic basis which avoids spool overflow issue.

You can try to increase the spool numbers from default 32000 to a bit higher value but please note donot set this too high as it may impact database performance

Proactive monitoring check can be made in RZ20 transaction to see how much is the fill level of spool numbers.

          How to check spool numbers ?          To check spool numbers : Goto RZ20 transaction, navigate to SAP CCMS Monitor Templates -> Spool System.

Here you can check the status of spool servers and the used numbers percentage of spool numbers. If you find that used numbers is greater than 80%, you can manually run above mentioned reports or delete old spool requests from SPAD tcode as mentioned earlier.

How to set the spool number   in SAP ?

Using Transaction SNRO (Number range object maintenance) and object SPO_NUM, you can set the spool number in an SAP system.

Once you provide object as SPO_NUM, click on change icon. It displays another screen. In that screen, click on Number Ranges push button. It displays another screen "Number range for spooler numbers". Click on change icon here and set the value of spooler(from number and to number). Please note that a change request may be generated here based on the client settings(if automatic recording of changes is set in SCC4 transaction of the client)

How to define storage location (Temse) of spool requests ?

Every Temse object contains a header in TST01 table and the actual object. This can be either stored in table TST03 or in file system. You can set a parameterrspo/store_location in RZ10 to define whether to store Temse objects  TST03 table or in filesystem.

If value G is set to this parameter, it will be stored in filesystem and if it is db it is stored in TST03 table.

How to change a SAP parameter ?

This article answers following query :

How to change or set a SAP parameter

SAP parameter can be set using RZ10 transaction. Go to RZ10, select the respective instance profile of the application server on which you would like to change the parameter.From the dropdown of profile, select the instance profile (of the application server) on which you would like to change the parameter.

After selecting the profile, select extended maintenance button and press change push button.

It displays a screen with all the parameters as shown below :

You can  either search the parameter or create the parameter and then set the value to the desired and save the same as below.

Set the parameter value in the text box provided and click copy button to copy the same and then press back button and press copy again in the next screen. After that press the back arrow to come to the following screen

Click on Save button to save and activate the profile.

Press no to goto the next screen

Press yes, to activate the profile.

The parameter will take effect after restart of the application server

PROCEDURE

Creating a Printer in SAP

Before defining a printer in the SAP system, the printer must already exist in the UNIX host.  To define a printer:

1. Bring up the Spool Administration screen by using transaction code SPAD or System ® Administration ® Spool ® Spool administration.

2. Select Printer Names and click the ü pushbutton to bring up the Spool Administration: List of Output Devices screen.

3. Click the Create pushbutton to bring up the Spool Administration: Create Output Device screen.

4. Enter a four character printer code in the Output device field.  This code should follow the standard: XX01, XX02, XX03, and so on, where XX is any two characters.  Use a code that is not already in use.

5. Enter the SAP device type in the Device type field.  To see a listing of possible entries, click in the field and then click the down arrow to the right of the field.  Double click on the item in the list to select it.  For HP LaserJet printers, select _Z_LJIIID_ (if this selection is unavailable, select HPLJIIID).

6. Select the host that will process requests for the printer in the Aufbereitungsserver field.  To see a listing of possible entries, click in the field and then click the down arrow to the right of the field.  Double click on the item in the list to select it.  Each row in the list has a Server name and a Host name.  The list is divided into servers with active spool processes and servers without an active spool process.  Double click on a server with an active process.  This will fill in the Aufbereitungsserver and Host name fields.

7. Enter the name of the UNIX printer in the Host printers field.8. Enter a space in the first Device class field to designate a Printer device class.  This should

be the default entry.  To see the possible entries, click in the field and click the down arrow to the right of the field.

9. Enter N in the first Access method field.  This entry translates to Print locally via LP/LPR.  To see the possible entries, click in the field and click the down arrow to the right of the field.

10.  Enter S in the first LPQ format field.  This entry translates to System V LPSTAT.  To see the possible entries, click in the field and click the down arrow to the right of the field.

11.  Enter a short description of the printer in the Location field, e. g. Printer in IS Dept. by Stephanie Engel’s Office (DPLASER).

12.  Click the Save pushbutton (icon with yellow folder) to save the definition.

Changing a Printer in SAP

To change an existing printer in SAP:

1. Bring up the Spool Administration screen by using transaction code SPAD or System ® Administration ® Spool ® Spool administration.

2. Select Printer Names and click the ü pushbutton to bring up the Spool Administration: List of Output Devices screen.

3. Click the Change pushbutton to bring up the Spool Administration: Change Output Device screen.

4. Make the necessary changes and click the Save pushbutton (icon with yellow folder) to save the definition.  Follow steps 5 through 12 above to change the printer definition.

Monitoring Spool Requests  in SAP

To monitor and maintain print jobs in SAP,

1. Bring up the Spool: Request Screen by using transaction code SP01 or menu path System ® Administration ® Spool ® Output controller.  An alternative menu path is System ® Services ®Output controller.  The screen allows you to query specific spool jobs.

2. Enter the criteria for query in the given fields.  The fields include:

Spool request number Spool request name User name (defaults to SAP ID used to log on) From Date (defaults to current date) Client (defaults to current client number) Output device Format Title Recipient Department

To get a list of all jobs, clear out all the field entries.

1. Click the ü pushbutton to bring up the Spool: Requests screen.   The screen displays the results of the query.  The information on the screen shows the following fields:

Spool request number Client number User name Time of request Output status Print request size Print request title

To see the attributes of a spool request, select the spool request and click the Attributes pushbutton.  This will bring up the Spool: Attributes screen.

A spool request may have more than one print request; it may print more than one document or report.  To see all the output requests for a spool request, select the spool request and click the Output requests pushbutton.  This will bring up the Spool: Output Requests for Spool Request screen, which lists all the print requests associated with the single spool request.  The individual print requests may be maintained from this screen.  Display the attributes for a print request by selecting the print request and clicking the Attributes pushbutton.  Delete a print request by selecting the print request and clicking the Delete pushbutton.  Note that successfully completed print requests will not appear if the print request used the Delete immediately option.

To see what is actually printed in a spool request, select the spool request and click the Display pushbutton.

To resubmit a spool request, select the spool request and click the Print pushbutton.  SAP will attach this print request  to the same spool request.

To see the date spool request were made, click the Date pushbutton.  The date will replace the user name column in the listing.  To see the user names again, click the User name pushbutton.

To delete spool requests, select one or more spool requests by clicking the boxes on the left and then select Delete from the Spool request menu.  This will delete all print requests in the spool request.

To see information on a spool request with an Error status:

1. Select the spool request and click the Output requests pushbutton.  This will bring up the Spool: Output Requests for Spool Request screen.  The unsuccessful print requests will be listed in this screen with incorrect in the Status field. 

2. Select the print request and click the Display log pushbutton to get the Spool: Display Error Log screen.

3. To expand the information in the log, click the More info pushbutton repeatedly.  To shorten the log, click the Less info pushbutton. 

Cleaning Obsolete and Inconsistent Spool Requests and Temporary Sequential Objects

SAP stores spool information in several tables.  To purge obsolete and inconsistent spool information:

1. Bring up the Spool Administration screen by using transaction code SPAD or System ® Administration ® Spool ® Spool adminstration.

2. Select Delete obsolete spool requests and click the ü pushbutton to bring up the Spool Administration: Delete Old Spool Entries screen.

3. Select the desired criteria and click the Start pushbutton to delete the spool requests.  The default is Old spool requests that have exceeded their life.

4. Bring up the Spool Administration screen again by clicking the green arrow pushbutton.5. Select Consistency check and click the ü pushbutton to bring up the Spool: Consistency

Check screen.  The screen will list any inconsistent spool objects.6. Delete all inconsistent spool objects by clicking the Delete all pushbutton.7. Bring up the TemSe Administration screen by using transaction

code SP12 or System ® Administration ® Spool ® TemSe administration.  TemSe stands for Temporary Sequential objects.

8. Select Reorganization from the TemSe data base menu to bring up a pop-up box.9. Select the desired criteria and click the Delete pushbutton.  The default is Obsolete TemSe

Objects.

10.  Select Consistency check   from the TemSe data base menu to bring up the TemSe: Data Consistency Check window.  The screen will list any inconsistent TemSe objects.

11.  Delete all inconsistent spool objects by clicking the Delete all pushbutton.

SPOOL Administration It is used to output the document to a printer, fax, email and SMS etc.It is only the process which is used to display the documents before they get printed.Once a spool request is generated in the system, It can be printed to any printer with n no of

copies, at any time.Where as normal printing, the document will not be available once it is printed.We can change the output format at any time.

Spool work flow:

A dialog user or a background process initializes a print request.The print requests are stored in a location which is determined by a parameter ‘RSPO/Store_location = G/DB’.G- Global directory at OS levelDB- In database tables.

This location is referred as “Temse”( Temporary Sequential File).Temse is stored in Global directory when it is referred as ‘G’. It is stored in database tables TST01 ; TST03. If it is referred as ‘DB’ .

By default the value is ‘DB’.

G: (Global Directory on Application Server):

1. If G is specified it is stored at OS level2. The printing will be faster if there are less no of documents. Because from file system to spooler

The communication faster than database to host spooler

Disadvantages:

1.A dedicated backup has to be planned to save the contents of Global directory.2. When the records are more the printing consumes more time because of ‘Lack of indexes’ at file system.

Advantages:

1. No special attention is required to backup the spool requests.2. RDBMS rules are inherited to spool requests, because they are in the Database.

‘Temse’ stores spool requests

Spool process gets initiated and reads the contents from ‘TST01’ name of the Author, no of copies name of the printer and spool data from ‘TST03’. And converts spool requests into “Output Requests’ (Printer specific requests).

The communication between the spool process & Host spooler depends upon the type of “Access Method”.

1. Local Access Method: The spooler process and the host spooler resides on the same server, then LAM is used.On UNIX- OS Access Method ‘L’ is used (SAPLPD)

(To print the spool requests ------à # lpstat (Queue Name))

On windows Local Access Method ‘C’ is used.

It is direct OS called method.

Note: The printer can be connected to directly or we can send request too print server.

2. Remote Access Method : The ‘Spool Process’ &’Host Spooler’ request on different machines

On UNIX machines Remote Access Method ‘U’ is used It is derived from UNIX Berkley Protocol.On windows SAP proprietary protocol type ‘S’ is used.

3. Front end printing:

The spool process is dedicated to the user requests and it will not be freed until the process finishes the task.

The spool process are configured by parameter ‘RDISP/WP_NO_SPO’Depending on the resources as many no of spool processes can be configured.

In order to avoid spool congestion configure front end printing process to either 2 or 3 i.e. at any given point of time 2 or 3 work process can go into front end mode.

Goto SPAD to define printer.

Click on ‘Output Device’------à Create -------à

Specify the name of the output device. Ensure that the naming conversation are followed to define the name of the printer.

Provide a short name

Specify the device type (i.e. serial no & manufacturer of the printer)

If the device types are not available, communicates with SAP or the vendor, get the device types and import it to SAP system.

Goto SPAD ------à Utilites-------àdevice types ---à Import

We can also import ‘Character sets’.

Specify the spool server

Spool Servers: The application Server which is configured with at least one spool process is called as spool server.

Spool servers can be logical or real

Goto SPAD -----à click on spool servers--àclick on change(F8)---------à Create

We can create our own spool servers.

Logical Spool Serever:

Define the logical spool server and assign it to a real spool server

In order to select Logical ServerSelect [ ] Logical Server ------àspecify mapping real server alternate server

Also [ ] Allow load balancing.

Device Class : Specify whether it is a printer , Archiving , fax etc…Authorization Group: For securing the printerSpecify Model, Location & Message

Access Method : Specify the Access Method specify the host name

[ ] Do not query host spooler for output status.

Output Attributes: Specify

Tray info:

“RDISP/WP_NO_SPO_PRO_Max” to limit the users for front end printer.

Spool Monitoring: Spool requests are monitored in transaction SP01

Go to SP01 to display ‘Spool requests’ and ‘Output requests’ specify the ‘Spool request ‘ number or user id, Date & Time, Output device to display the Spool requests.

The spool request has the following statuses:

‘-‘ : The request is not sent to the host system (output request does not exist)‘+’ : Spool request is generated and stored in “Temse’.‘Waiting’ : The spool request is waiting to be processed by a spool process.‘in process’ :Te spool work process is processing the spool request into output request for printing.‘Printing’ :Te host spool is printing the request. If the RS system does not receive any status from the host spool, the status is dispatched for one minute and shifts the status to ‘Completed’

Note: There are instances where the printing is continued and the status is set to “Completed”. This is due to the option set “[ ] Do not query host spooler for status”

‘Completed’: Generally the completed status donates that output request completed successfully, because the ‘spool system’ communicates with ‘Host Spool’ and if it doesn’t receive any status update within one minute , the status is set to “ Completed”

‘Problem’ : The output request is printed with minor error (Page Format, Margins).

‘Error’ : Indicates an error that the ‘Host Spool’ system is not reachable can a network error.

‘Archive’ : The request is waiting to be archived. Archived requests will be stored in external devices and are available to print at any time SARI & SARA.

Transaction SPIC is used to check the consistency of Spool MechanismGo to SP12 for “Temse” administrationIt is used to identity the size based on users and applications in the “Temse”

SP02 - Display Spool Requests  Basis - Print and Output Management

SPAD - Spool Administration  Basis - Print and Output Management

SP00 - Spool and related areas  Basis - Print and Output Management

SPAT - Spool Administration (Test)  Basis - Print and Output Management

SPOV - Spool Request Overview  Basis - Print and Output Management

RSPO0055 - Installation Check: Spool  Basis - Audit Information System

RSPFPAR_SPOOL - Spool Parameters  Basis - Audit Information System

OMMZ - Spool Parameters for WM Print Ctrl  Logistics Execution - Other Functions

  -- More SAP "spool" Transaction Codes ----SP01 - Output Controller   Basis - Print and Output Management

SPAD - Spool Administration   Basis - Print and Output Management

SM37 - Overview of job selection   Basis - Background Processing

SP02 - Display Spool Requests   Basis - Print and Output Management

SE38 - ABAP Editor   Basis - ABAP Editor

SM36 - Schedule Background Job   Basis - Background Processing

SP12 - TemSe Administration   Basis - Print and Output Management

SCOT - SAPconnect - Administration   Basis - Communication Services: Mail, Fax, SMS, Telephony

SM21 - Online System Log Analysis   Basis - R/3 Syslog

F110 - Parameters for Automatic Payment   FI - Financial Accounting

The Need for Spool Administration: 

The SAP system has a printing architecture that needs close administration and monitoring. It is organized in such a way that when users send a print job in the system, the spool work process prepares data in the spool request and generates output requests that contains the formatting details of the printer. Long running active print jobs is probably an indication of spool problems and needs to be investigated. You need to check that old spools are deleted from the SAP system. Transaction SP01 provides an environment to get a clue of the cause of a printing or spool problem. 

Basic features of the SAP spool system are the following: 1. manages the output requests for printing, for the SAP communication server, and for the archiving devices 2. Provides a uniform interface for different host spool systems 3. Supports local, remote, and PC printing 4. Supports multiple print and output devices, formats, paper types, and character sets 5. Better look of spool administration transactions 6. Multiple spool work processes per instance 7. Open interface to external output management system (OMS) 

8. Spool accounting exit 9. Workload balancing 

SAP Printing System Administration Tasks The SAP printing system and associated tasks are a subset of those general administration tasks for the daily operation of the SAP system. R/3 system managers should be in charge of the following tasks: 

o Periodically checking and monitoring the spool system, both at SAP and at the operating system level.

o Deleting old spool requests or scheduling the background job which automatically deletes them.

o Defining new printers, device types, and other device elements.o Using the statistical information of the system for fine−tuning the planning strategy.o Troubleshooting the spool system

  Managing Spool Request 

o There are several ways of calling the spool request management functions:o From the main menu, select Tools CCMS Spool Output managemento From any menu, select System Services Output controllero Directly enter transaction code SP01 in the command fieldoo This initial output controller display behaves like a selection screen, where you can

search spool requests by spool request number, spool request name, user name, date, client, and so forth. By default, the screen always presents the logon user name, the logon client, and the system current date−but these parameters can all be overwritten.

o Once the selection criteria is entered, just press the Enter key or click on the Overview (Continue)  icon on the standard toolbar to display a list of spool requests matching the criteria. The spool requests which have been successfully printed and for which the user had selected the flag Delete after print are automatically deleted from the system, and therefore will not appear on this list. On this screen, the system displays information about the spool requests arranged by columns. These columns are

oo Spool no.  It's the spool request number as it has been automatically assigned by the

system.oo Generation date. Date in which the spool request was generated. This column can be

toggled with the client and user name information by clicking on theoo User name push button on the application toolbar.o Time. Time when the spool request was generated.oo Output status.  Indicates what the status is of the spool request. The system can

display the following output statuses For this spool request no output request (order to print) has been generated.

oo Wait: The output request is waiting to be processed by the spool system. It has not yet

been sent to the host spool system.oo Process: The spool work process is formatting the spool request to be sent to the

printer.

oo Print: The host system spool is processing (printing) the SAP output request.oo Compl: The output request has been completed and successfully printed.oo <F5>: This status indicates that there is more than one output request for the same

spoolo Request. You can double click on this status field to show all the associated output

requests or, alternatively, select the check box to the left and click on the Output requestpush button on the application toolbar.

oo Problem: A problem has occurred during the output request processing. The printing

might have been generated; however, it might not be correct or correspond actually to the expected printed format.

oo Error: There is a severe printing error. No output request is generated at the physical

printer.oo Archive: For spool requests that were sent to an archiving device. The spool request

has been processed by the spool system and is waiting for archiving.oo Pages.  Indicates the number of pages of the output request.oo Title. Displays the title of the spool request if the user entered one when submitting a

spool request, otherwise the system by default shows as the title the type of request, the device name, the program, and the first three characters of the user name.

Check the spool for printing problems (Transaction SP01): What The spool is the R/3 System’s output manager. Data is first sent to the R/3 spool and then to the operating system for printing Why You should check for active spool jobs that have been running for over an hour. These long running jobs could indicate a problem with the operating system spool or the printer. Login to the SAP System 1. In the Command  field, enter transaction SP01 and choose Enter 2. Delete information in Created by. 3. Set the Date created  field to, for example a week ago, or to any other date range to check for other problems.The range of data There may be problems with the printer at the operating system level. These problems need to be resolved immediately for time-critical print jobs (for example, checks, invoices, Shipping documents, etc.) Or there may be an operational impact. will depend on your installation. If you generate hundreds or thousands of spools a day, you would choose every day. This data range would be much shorter, possibly only two days. 4. Delete information in Client.

 

5. Choose .    6. Look for jobs with an error in the Output Status column.   

 

  7. Double click on the Error.   

 

  8. Select the error. 

9. Choose.   10. Review the error. 

  11. From this point, troubleshooting depends on the specific problem. 

12. Choose.  13. Select the error.   

 

  

14. Choose.    

 

  15. Use the log to investigate the problem (for example, this job was Unable to establish connection to the Berkley LPD). Check total no. of Spool Request (Transaction SPAD): Login to the SAP System 1.In the Command  field, enter transaction SPAD and choose Enter   

 

  2. Click on Admin   

 

  3Click on Print Request Overview This will show you the Total spool request count. If the count is goes beyond 150000 then delete the old spool request by transaction SP01   

 

. Checking that Old spools are deleted (SP01): What : The SAP spool is the output manager for R/3. From the SAP spool, the print job goes to the operating system’s print spooler or manager. You need to check that old spool jobs are being properly cleared by the daily batch job Why: 1. Depending on how the spool system has been configured, old spools will use database space or file system space.Whether it is database or file system space, potentially available “space” is being used by these spools. 2. Look for any errors that may indicate problems in the printing process. 

1. In the Command  field, enter transaction SP01 and choose Enter   

 

  2. Enter *CMM* or *JMM* or *SRM_SERVICE* in the Created by  fields: Date created (date) 3. Enter date into To date field 

4 .Choose     

 

  Go to Edit – click on Select All   

 

  Go to Spool Request – click on Delete 

  

 

  

 

  Click on Yes 

Troubleshooting Printing Problems 

The following is a list of possible steps to perform when you notice printing problems in the system. These problems can be very different: no printing at all, slow printing, printing garbage, and so forth. In any case, you should ¨ Check and monitor the spool work process from the Process overview  transaction as well as from the operating system spool (print daemon or print manager). Also, check that the message server is working properly. ¨ Particularly, check that you can print normally from your operating system. Find which printer is causing the problems. Use transaction SP01 System Services Output controller. 

¨ Check the output request attributes, the log files, and the size of the print job ¨ For remote printers, check the network connection. ¨ If a print job has been printed out but contains unreadable characters, check whether the device type is the most appropriate, whether the printer is working in emulation mode, and

what the access method is for the device. ¨ When nothing is output at the printer and the output controller is in wait status, check the system developer traces and the system log and look for timeout messages. Check that all application servers running spool work processes are reachable. ¨If the job has status Complete or problem and nothing is output at the physical printer, it might be related to a wrong output device definition, a problem in the host spooler, the physical printer, or the SAPLPD transfer program. Carefully check the access method. ¨ If printing is very slow, possible causes might be lost indexes in the spool tables, too many spool table entries, slow WAN connections, or incorrectly defined access methods. Often you will need to review the printing strategy about distribution of output devices in several application servers according to their expected volume and size of print jobs. Refer to the SAP online documentation and the SAP net about some interesting planning strategies for the spool system.

Spool Administration in SAP

What is Spool Administration In SAP What is SAP Spool process work flow How to configure Frontend printer in SAP ( SPAD ) How to setup a Default Printer in SAP ( SU3 ) Access Methods in SAP Spool Administration What is Device Type in Spool / Printing administration of SAP How to Import Device Type (Printer Type) for Spool / Printing administration in SAP What are Status of Spool Requests in SP01 How to check the spool requests generated in SAP ( SP01 ) Printer (Spool) Troubleshooting in SAP & Common errors in SAP Spool Administration What is spool overflow ( SPAD, RZ20 & SNRO )