ww

w.s

even

thw

avet

ech.

com

R/3 Spool Administrator Modified Date: Printed Date:

Table of Contents

1.0 SAP SPOOL ADMINISTRATION (SPAD)............................................................... 3

1.1 R/3 SPOOLING PROCESS OVERVIEW ............................................................................. 3

1.2 LOCATION FOR STORING SPOOL DATA ............................................................... 5 1.3 CREATING AN R/3 OUTPUT DEVICE .............................................................................. 7 1.4 MONITORING PRINT OUTPUT REQUEST. (SP01)......................................................... 10 THE FOLLOWING STEPS ILLUSTRATE HOW TO MONITOR AND DISPLAY THE STATUS OF PRINT QUEUES. ................................................................................................................................... 10 STEP 1: LOGIN TO THE R/3 SYSTEM....................................................................................... 10 STEP 2: EXECUTE THE R/3 TRANSACTION SP01. ................................................................ 10 1.5 CHECKING SPOOL CONSISTENCY. ............................................................................... 12 1.6 TEMSE DATABASE ADMINISTRATION (SP12) ............................................................ 13

1.6.1 Consistency Checks ................................................................................................ 14 1.6.2 Reorganizing TemSe Database.............................................................................. 15 1.6.3 Automating TemSe Cleanups................................................................................. 17

1.7 TROUBLE SHOOTING R/3 PRINTING ............................................................................ 18 1.7.1 Check the printer output device status................................................................... 18 1.7.2 Check the printer network connectivity................................................................. 21

1.0 SAP Spool Administration (SPAD) 1.1 R/3 Spooling Process Overview

The spool work process is one of several work processes that can run on an R/3 application server. The spool work process is responsible for generating a device-specific output stream, for an output request, from the print data in a spool request. Generating such an output stream, requires, that the spool work process does the following:

• Resolve R/3 print controls into printer commands

• Add device-specific printer initialization and output event sequences (end of line, end of page, and so on)

• Convert from the character set used by the R/3 System to the character set of the output device

• For SAP script output, use the services of the designated SAPscript printer driver to format the data for output.

The spool work process is also responsible for transferring the data either:

• Directly to a host spool system, output management system, or network printer; or

• To the SAPLPD transfer program, which then passes the output data to a host spool system or print manager.

The following steps illustrate how to display R/3 spooling processes that is currently running in your R/3 PR2 production system.

Step 1: From the R/3 main menu select Tools�CCMS�Spool�Spool Administration. Alternatively executed R/3 transaction SPAD.

Step 2: Click on Spool Server to display the list R/3 Spool server status and their hostname.

1.2 Location for Storing Spool Data

Use the following parameter to specify where the spool system is to store its data:

rspo/store_location: Specifies whether the spool system is to store data in the R/3 System's database or in files in the host system.

Possible values:

db: spool requests are stored in the database in table TST03.

• Advantage: spool files are protected by the backup and recovery mechanisms of the database system.

• Disadvantage: Slower than file system storage. Increased database load.

G: spool requests are stored in the standard R/3 "global" directory: /usr/sap/PR2/SYS/profile/200SPOOL (UNIX systems).

• Advantages: faster access to spool data; more flexibility. • Disadvantage: files are not protected by database backup and recovery

mechanisms. The following steps describe how to verify the parameter setting for storing spool requests in PR2. Step 1: Execute R/3 transaction RZ11 – Maintain Profile Parameters

Step 2: Enter the parameter called rspo/store_location in the Param. name field and click on Display.

Since the parameter is set to G, all spool requests for PR2 are located at the Unix level in the directory /usr/sap/PR2/SYS/profile/200SPOOL

1.3 Creating an R/3 Output Device

The following steps illustrate how to create an R/3 output device.

Step 1: Log on to R/3 system.

Step 2: Execute transaction SPAD.

Step 3: From the Spool Administration :Initial Screen click Full Administration.

Step 4: Click the button Output Devices.

Step 5: The Spool Administration: List of Output Devices will be displayed. Click the Display/Change.

Step 6: Click the Create button

Enter the required parameters as described below.

• Output Device: Descriptive name of printer.

• Short Name: 4- characters unique identifier for this device. This field is optional. If a short name is not specified the system will generate one.

• Device Type: The type of printer. Example HP LaserJet 5 Si. Prompt (F4) this field for a list of SAP supports printer devices. From the resulting list select the one that represents your printer.

• Spool Server: The R/3 instance that will control th e print spooling .

• Host Printer: The name of the printer queue which has been defined at the Unix level on the same R/3 instance named above,

• Device Class: This is one of Standard Printer, Archive, Fax or Telex devices.

• Access Methods: Select L: Print locally via LP/LPR

• The Model, Location and Message fields are used to provide optional information about the printer. This info can be used to better select the correct printer for an output request or to better diagnose problems.

• Lock Printer in R/3 System: This option, when active, will cause a spool work process to remain dedicated to a single output request until the request is printed. When not active, a spool work process becomes available to other output request as soon as the first is entered into the operating system queue. This is usually left unchecked.

• SAP Title Page: Select this option if you want each print job to have an SAP cover page.

• Click on SAVE icon when completed.

1.4 Monitoring Print Output Request. (SP01)

The following steps illustrate how to monitor and display the status of print queues.

Step 1: Login to the R/3 system.

Step 2: Execute the R/3 transaction SP01.

Step 3: For example if an administrator wants to review all the print queues output for user ZLOGBATCH. Enter ZLOGBATCH in the User name filed and click on the �Overview icon. A list of all spool requests for ZLOGBATCH are displayed.

Step 4: Display the detail information regarding the spool number. For example, if an administrator wants to find-out the detail log of the spool number 0000069035. Select the spool number 0000069035 and click on the Display Icon. select

Add a section here about out to check which output device the spool request went to. Click on a spool request, and then click on output device. Provide a screen shot showing the output device and status.

1.5 Checking Spool Consistency.

The following steps illustrate how to monitor the spool database: NOTE: A Spool Consistency check should be performed at an off-peak period when there is little activity on the system.

Step 1: Logon to the R/3 system.

Step 2: Execute R/3 transaction SPAD

Step 3: Select the menu option, Administration�Check consistency.

Step 4: Check for any errors or extremely old spool objects. Delete any objects that may not be needed.

1.6 TemSe Database Administration (SP12)

The spool system uses the TemSe (temporary sequential objects) database to store print data. The TemSe database is also used for storing background processing job logs and other sequential text objects that are temporary in nature (such as application data from FI and HR).

1.6.1 Consistency Checks

NOTE: A TemSel Consistency check should be performed at an off-peak period when there is little activity on the system.

Step 1: Logon to the SAP system

Step 2: Use menu path Tools�CCMS�Spools�TemSe Administration or enter transaction SP12.

Step 3: Select menu option TemSe Database�Consistency check. (This may take some time to complete).

Step 4: From the resulting list, select any inconsistent objects and press Delete button.

1.6.2 Reorganizing TemSe Database

The following steps illustrate how to reorganize the TemSe Database.

Step 1: Logon to the R/3 system. Step 2: Execute SP12 R/3 transaction.

Step 3: Select menu option TemSe database�Reorganization.

Step 4: On the TemSe – Administration of Temporary Sequential Data popup window select:

• Obsolete TemSe Objects – To delete inconsistent objects • All TemSe objects older than ___ Days – Delete all objects (consistent

and inconsistent) older than the specified number of days. • Click the Delete button.

1.6.3 Automating TemSe Cleanups.

The TemSe database can occasionally cause space problems in the R/3 System’s database. The reports required for automating TemSe cleanup are RSBTCDEL and RSPO0041. RSBTCDEL is usually scheduled with job name SAP_REORG_JOBS and RSPO0041 with name SAP_REORG_SPOOL. Together these two jobs maintain the consistency of the TemSe database, however, periodic manual checks should still be performed.

Step 1: Log on to the R/3 system.

Step 2: execute R/3 transaction SM37 to verify that the SAP_REORG_JOBS, SAP_REORG_SPOOL background process is running every night.

Step 3: If either of these is not scheduled correctly see the OSS note 16083 and documentation on R/3 Background Jobs, the administrator should schedule it.

1.7 Trouble Shooting R/3 Printing

1.7.1 Check the printer output device status

Follow the steps described below to check the status of the R/3 output devices. For example, we may want to check the status of the R/3 output device named HP8000DN017

Step 1: Login on the R/3 system.

Step 2: Execute the R/3 transaction SPAD

Step 3: Validate the printer existence in SAP R/3 by click on Output devices and make sure the R/3 output device name exists.

Step 4: Validate that printer is not locked by highlighting the output device named HP8000DN017 and double-click on the device name. Make sure the Lock printer in R/3 System is unchecked.

Step 5: Validate there are Output Requests for the printer in question. Execute the R/3 transaction SP02 and enter the output device named HP8000DN017 in the Output device field. Click on Execute to view the list of print queues sent to HP8000DN017 output device.

Step 6: Validate SPOOL servers are active via transaction SM51.

1.7.2 Check the printer network connectivity

Step 1: Check general UNIX printer status. For Example, if you need to check the status of the printer named HP8000DN017.

• Logon to the host system that printer named HP8000DN017 has been created.

• $ lpstat –p HP8000DN017

Step 2: Make sure the printer in question is enabled and accepting requests.

• Logon to the host system that printer named HP8000DN017 has been created.

• $ lpstat –p HP8000DN017

Note: if the printer is disable. Following the procedures described below to enable the printer.

• $ enable HP8000DN017

• $ accept HP8000DN017. Start accepting print requests for the printer.

Step 4: Make sure the printer system and printer queue is setup properly.

• $ lpstat -p HP8000DN017 -l

Step 5: Check printer network availability

Step 6: Check to see if the printer name can be pinged on each of the SPOOL Servers.

Step 7: If the printer in questioned can not be pinged from a SPOOL server validate the IP address

Step 8: If the printer in questioned cannot be pinged from the SPOOL server(s) check from a PC on the network.

Step 9: If the printer in question cannot be ping from multiple systems on the network physically check the printer power and proper network cabling.

Step 10: Collect the following information if the printer appears functional: Cube Number, Network Port Address, Printer IP Address, Printer type, & Printer Name and contact EUS.

Step 11: Check UNIX Level Queue On All SPOOL Servers

Step 12: Check UNIX's print scheduler.

• Logon to the host system.

• $ lpstat –r. Check to see if the print scheduler is running.

• If the printer schedule is not running, start it $ lpsched

Step 13: Check UNIX printer queues in question on all SPOOL servers.

• Logon to the host system.

• $ lpstat –r . Check to see if the print scheduler is running.

• If the printer schedule is not running, start it $ lpsched

Step 14: Check UNIX output queue via lpstat -o <printer name>

Task Ownership Contact Info

Comments

Set Spool storage location

Create Output Device

Monitor Output requests

Check TemSe Consistency

Reorg TemSe Database

Initialize TemSe standard Jobs