Page tree
Skip to end of metadata
Go to start of metadata

During execution of print processes, the system automatically stores the spool requests of the applications. Because of this, the spool table, that contains the requests, is filled up after a time and the system won’t be able to execute additional print processes.


In this case use program RSPO1041 to delete unneeded spools. RSPO1041 can be run as a regular program in transaction SE38, but due to possibly long runtimes, it is recommended to schedule RSPO1041 as a repeating Batch Job in transaction SM36. RSPO1041 is the enhanced version of RSPO1040 and provides better functionality. For more information about the program read SAP Note 130978.


In the program are seen different sections, which help customizing the conditions of deletion.

This page is part of:

Printing

Tiny link (useful for e-mail):

https://wiki.scn.sap.com/wiki/x/ggcgIg

Important sections are:

  • Without output request
    • (These involve the spools which have the status "-" in transaction SP01)
  • In processing
    • (These involve the spools which have the status "In Proc." in transaction SP01)
  • Completed
    • (These involve the spools which have the status "Compl." in transaction SP01)
  • Incorrect/ With Errors
    • (These involve the spools with any other status in transaction SP01)

Within these, it is possible to set 5 conditions:

ConditionsRole of conditions
Checkbox with the name of the sectionWith checking this box, the section will be enabled. Otherwise, it won’t be considered and applied during deletion.

Older than … days

Based on the entered number and the date the spool was generated on, the program determines which spool requests have to be deleted.

And

Logical operator. In case of setting of it, both the “older than … days” condition and the “Obsolete” condition will be considered by RSPO1041 when it is searching for spools to be deleted.

Or

Logical operator. In case of setting of it, RSPO1041 will mark a spool for deletion if either the “older than … days” condition, or the “Obsolete” condition is true.

Obsolete

Setting of this option results, that during deletion the “Deleted On” date of the spool request will be considered instead of the generation date of the spool request.


Before setting the field “older than …days”, make conversation with Business People to know, how old spool requests have to delete.


Section Calendar:

FieldsDescriptions

Factory calendar ID

A factory calendar distinguishes between working days and non-working days. In case of entering an exception rule for non-working days and having selected factory calendar, enter a factory calendar that is relevant to the company.

Only include workdays

Only the workdays will be considered during deletion.

Include all days

Both the workdays and non-working days will be considered during deletion.


Section Further conditions:

FieldsDescriptionsAdditional Notes

System name

ABAP system field. AS ABAP name, for example "S01" or "K99".


Client

ABAP system field. Client ID used by the current user to log on, for example '401', or '800'.


Creator

ABAP system field. Logon name of the user.


Title

The title that is to appear on the cover sheet of the request. (Only available, if the output request prints the SAP default cover sheet.)  

Enter any title for the output request to make it easier for the user and for the system administrator to identify the request.

If users or print programs enter a title by default when processing a print request, it is possible to use this title to select the relevant spool requests.

A spool request can have both a spool request name and a title. The former is generated automatically by the spool system, the latter must be entered explicitly by the user or program generating the request.

If a titel is entered, it replaces the three-part spool request name on the cover sheet and in the request list in the Output Controller.

Spool request name

Three-part name of a spool request.

The name is determined automatically by the spool system, but can be entered by the user or the program generating the request. There is no specified naming convention.

Applications may apply their own naming conventions. For information on this, refer to the documentation of the respective application.

Some common naming conventions:

  • Report lists:  LIST1S <PRINTER NAME> <REPORT>_<USER NAME>
  • Printout from the ABAP editor:  EDITOR PG <REPORTNAME> <TIME> <RELATIVE NUMBER OF THE OUTPUT REQUEST>

A spool request can have both a spool request name and a title. The former is generated automatically by the spool system, the latter must be entered explicitly by the user or program generating the request.

When the user enters a title for a request, this title is displayed in the spool output controller in place of the request name. However it is still possible to search for the request name from the spool output controller's request screen.

Spool request (suffix 1)

Second part of the (automatically generated) three-part spool request name.


Spool request (suffix 2)

Third part of the (automatically generated) three-part spool request name.


Output Device

Long name of an output device. The name can be up to 30 characters. The name of the output device is case-sensitive.


Requests without Output Device

In seldom cases it may happen that the “Output Device” field of a spool request is empty. Enable this option, so RSPO1041 will consider such spools for deletion. Otherwise, such spools might not get deleted.



Check whether the system name in section further conditions is same as the used system.


Other settings: 

FieldsDescriptions

Only log without deleting?

If this checkbox is checked, the system will generate a test run, where it is possible to test the settings, that are set former. Keep in mind, that during the test run, the program does not delete the spool requests from the system.

COMMIT all … Spool requests

A database COMMIT command will be only sent to the database after RSPO1041 has reached this many number of spools-to-be-deleted. If you do not face any database issues, the value of this field does not need to be changed.




For an example configuration of RSPO1041 read KBA 3042383.

  • No labels