Choose  Tools CCMS Spool Output controller .

Enter all available information that you have on the spool request in the selection screen. Especially useful: enter the name of the user who generated the spool request and R/3 printer name (Output device).

In the spool request list, check the Output status column. You should see either Problem or Complete.

If you see <F5>, then there are multiple output requests with varying statuses. Press Output requests to display the status information.

Check to see if the output request is in your host system spool or print manager. If the output request is there, then it is likely that the printing problem is somewhere in the host system. Check the status of the print request in the host spool for possible information. You should also check the printer and the local or remote connection from the host to the printer.

After you have found and corrected the problem, print the spool request again.

If you did not find the output request in the host system spool, then check that the print command you are using is correct.

In UNIX systems, you can find this command in the system profile of an application server. Choose  Tools CCMS Configuration Profile maintenance . Find the profile used by the application server from which the unprinted output request was sent. Then use Extended maintenance to check the value of the rspo/host_spool/print parameter. You may find this parameter set globally for your SAP System in the DEFAULT.PFL default profile.

For help in interpreting the variables in the parameter value, see Setting Spool System Parameters.

Once you have found the command, try it out directly at the host system command line. If you are not able to print successfully using the command, check your host system documentation to find out what is incorrect in the command. When you have corrected the command in the SAP System profile and have restarted the system, you should be able to print output requests successfully.

If you can, try to use the command to print the host system file generated by the SAP spool system. The SAP spool system passes this file to the host spool system or print manager for printing. For help in finding print files in UNIX systems, see Spool Data Storage Location. For help in finding print files in Windows and Windows for Workgroups systems, see Setting Up SAPlpd for Printers and Fax Machines. No print file is created on Windows NT systems where you have specified Access method C for the connection between the SAP spool work process and the NT print manager.

If the host print command is correct, then you should collect additional information about the output request that could not be printed. You can use this information to identify problems with the output data itself. For information about activating this logging, see Logging Print Output Data.

If you are using the SAPlpd transfer program on a Windows or Windows NT PC, then you should also try stopping and restarting the program.

For information about analyzing problems in SAPlpd, see Setting Up SAPlpd for Printers and Fax Devices.

Possible problems in the output data can include:

Start the Output controller and display the spool request that has an error.

Choose the Output requests function to display the output requests generated from the spool request. Mark the most recent "problem" output request and choose the error log function.

The log may contain errors issued from the following sources:

If you find error messages and can correct the problems, you should then be able to print successfully.

If you cannot isolate and resolve the printing problem on the basis of the output request log, repeat the print request with logging of output data switched on. For information about activating this logging, see Logging Output Data.

You can also use the ABAP debugging and trace functions to analyze how the output request was processed.