ECC Spoolfile number limit being reached - not rolling to new number

[former_member257252]

Hello everyone,

We just updated to one of the newest Kernels for ECC and we are running into a new issue..    Our Spoolfile numbers are not rolling to a new number once the "Ceiling" is hit.      Opened an SAP ticket and they are telling us to set the limit to 999,999 which in our business we will hit in 50 days.

spools SPO_NUM number range threshold was changed to 150,000 for now.  Here is the ticket we opened.

Short Text
spools SPO_NUM number range threshold
Long Text
SAP Support, We experience issues while reaching threshold from SPO_NUM number range. We followed Note 48284 in order to increase this number range value – however spool request are being generated at a high rate getting to the number range value threshold too fast. - We checked parameters -- rspo/spool_id/loopbreak. |rspo/spool_id/max_number – in RZ11 but it seems these are surpassed by the value of our current spool request number range – 99000 both parameters - and we don’t see spool request counter loop in as it supposed to do – new spool request number its beyond parameter threshold – 104830 – at this moment. - Jobs SAP_REORG_SPOOL / SAP_SPOOL_CONSISTENCY_CHECK running ok in the system and spool request are being deleted according to job criteria

Here is SAP response..   Does anyone have a solution to reset the spoolfile number once the limit has been hit... 

Dear Customer,

It is correct that the current spool number will not loop

to number 1.

In fact it will never go to 1 as usually the lower limit is set

by

to 100. So this is normally the lowest spool number used. But again

it

will not automatically pick number 100 after the highest spool number

ispicked previously.

We recommand as per note 48284 to increase the upper

limit of interval =interval 01 to 999,999 in client 000.

thanks everyone..

Chris

[bxiv]

I can't answer on how to have the range reset itself, but my team ran into an issue after a go life due to a bad business process generating spools to a spool printer for labels and ended up killing our number range with a few days.

We modified the clean up job to drop these specific spools after 1 day (I believe I would have to verify) as all the spools were in an error state.

Can you add some additional variants to the clean up job to see if that helps?

[former_member257252]

we do that...  we have about 15,000 spoolfiles in the system now...    we are 20,000 away from the top number of 150,000      once we get to spoolfile number 150,000 everything stops printing until we add new numbers.