[johangonz]

Ese error está muy bien documentado en una nota SAP, el detalle es que el spool service alcanza la totalidad de los registros definidos para la tabla. Hay dos opciones, cambiar el rango de numeros para el spool o ejecutar un reporte que elimina los registros. En un cliente programé el reporte (RSPO0041 or RSPO1041) en un Job con una variable previamente establecida en donde hasta un mail envia en la ejecución diaria para evitar este problema. Te dejo la nota:

Note 48284 - System can no longer create spool requests
Solution
You can raise the upper limit for spool requests. As of Release 4.0, you can set the upper limit to anywhere between 2 and 31 numbers (previously 99,000). However, we recommend that you do not set the interval higher than 999,999 because the human user finds higher numbers difficult to process.

Proceed as follows:

1. Log on to the system in client 000 and call transaction SNRO.
2. In the "To No." column, change the upper limit of the interval SPO_NUM to 999,999.
The size of the interval also determines the maximum number of spool requests that can exist in the system. To ensure that the system performance does not deteriorate, you must use RSPO0041 or RSPO1041 on a regular basis to delete spool requests that are no longer required. The number of spool requests that can be held "officially" in the system depends to a great extent on the capacity of the database and the database computer. Only the number of spool requests simultaneously held in the system is relevant, not the size of the number intervals.

You can use the spool number monitor in transaction RZ20 to specify threshold values in which the system must create an alert if a certain percentage of the spool numbers are allocated.

Revisa también la "OSS Note 1422843 - Wrong deletion date in spool request"

Ejecuta el reporte depende del release y veras que podrán imprimir nuevamente, igual a futuro debes validar que el reporte se ejecute regularmente para evitarlo a futuro.