Sap spool file retention

Existing spool requests that have not yet been processed are not lost but they cannot be processed. Spool requests for which output requests have already been passed to the host spooler or SAPSprint Service before the database service failure are processed by the host spool system. However, it is not possible to write a corresponding entry indicating success in the log table for the spool request. The spool service is unavailable for the period when the database is down. You must now check the consistency of the spool database.

In this case the spool request cannot be successfully processed. In this case the dispatcher restarts the failed spool work process. The new spool work process then takes over the work of the terminated one. For example, this situation might arise because the host spool system incorrectly reports successful processing. Or it might arise because the host spool system does not report anything and processing is assumed to be complete, once the output request has been passed to the host spool system.

If an equivalent device is unavailable, then it is not possible to satisfactorily print the output requests that were prepared for the failed device type on a different device type. You need to regenerate the spool requests in this situation, or alter them, so that they can be printed on a different device type.

For more information about printing on a different device type, see Displaying and Changing Spool Request Information. You can redirect spool requests from list-type output that is, from SAP reports , assuming the spool type and print control exist on the different device type, but not output from SAPscript. If a device defined in a device pool fails, you must remove the failed device from the device pool using the spool administration transaction SPAD so that the failed device does not receive any further requests.

The device pool continues operating after the failure of a device but with reduced throughput. Any requests that were assigned to the failed device before it was removed from the pool are not automatically redirected to functioning devices in the pool. Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy.

Enter the email address associated with your account. We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox. The output request is to be sent or is being sent to the spool work process, or for formatting, in the host spool system. If this status is displayed for a request for an extended period of time more than one minute , the corresponding spool work process may have terminated, or there may have been a problem establishing a connection to a remote output device.

The spool work process automatically reprints the output request affected by the problem. In Processing. The spool work process is formatting the output request for printing. The request has been passed to the host spooler or to an output device, and a final status has not yet been returned to the SAP spool system. The output request has been successfully printed. In systems in which the SAP spool system cannot get information from the host spooler, the status becomes Complete as soon as the output request has been passed to the host spooler.

More than one output request has been generated and the requests have different statuses. Some requests may not yet have a final processing status. To display the status of individual requests, choose Output requests or double-click the request status. There is a minor problem; the output request was printed, but probably contains errors. Example: If the printer character set is incomplete, a missing character is replaced with another.

There is a problem with severe consequences. Requests of this type could not be printed and remain in the spool system until you delete them or the retention period is exceeded and they are deleted by a reorganization. Example: The system cannot find the printer in the network. Use the error log to determine the cause of the error. For spool requests sent to an archiving device. The spool request has been processed by the spool system and is waiting to be archived.

Time or Scheduled. The user who created the request specified a time when the request is to be output. Click on execute to view the below list of spool requests. Common errors:. If after cleanup and you encounter one of these errors: A. Spool overflow assume you have not adjust max spool number before C.

No more free spool request numbers SAP note mentioned that change: 1. Default numbering range is - 32, which can print up to 31, requests. This is optional. We don't see a need to have more than 31, 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.

Spool request that got generated are stored in a temporary sequential file called Temse. The default size of Temse is 32, and it can be increased till 2 billion. However, defining very high value can effect the database performance.