Spool overflow

[Former Member]

Hello,

I am getting the below Spool error

************************************************

Internal error in the spool system.

What happened?

The current ABAP program had to be terminated because the

ABAP processor detected an internal system error.

The current ABAP program "ZBDC_MAT_MASTER_HR" had to be terminated because the

ABAP

processor discovered an invalid system state.

What can you do?

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

When calling the SAP spool system, an (unspecified) internal

error occurred.

More detailed description of error: "spool overflow "

Further information:

See below under "Spool error information".

How to correct the error

Probably the only way to eliminate the error is to correct the program.

-

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

"SPOOL_INTERNAL_ERROR" C

"ZBDC_MAT_MASTER_HR" or "ZBDC_MAT_MASTER_HR"

"MESSAGES_DISPLAY"

-

---

Can you help me in finding out the solution

Appreciate your help.

[Former Member]

Dear Ruchit,

In spo1, i have got 28,394 entries by keeping time and date and user fileds as empty.

Can i have ur personnel email id ?

[Former Member]

Dear Vadivambal,

As per the forum policy e-mail address must not be published and I would like to stick by that policy. I am sorry for that.

I suppose there is some thing you want to inform through spool. I guess some screenshot of the SP01 transaction.

Anyways the information I need I have got it. 28,394 is pretty huge number considering the fact that your are running the spool deletion job.

I faced a similar error long time back and this is what I did.

1. From SP01 I got the list of all spool requests that were present in the system.

2. Next I identified the dates on which they were really created.

3. I deleted the oldest spools through SP01 transaction itself. The reason being if I run the spool deletion job it will also try to create a spool request which since in this case maay not be possible; will also get cancelled. Of course you may retain the spool requests that are business critical though very old spools are not really needed.

4. Next I executed the report RSPO1041. In that selection criterion is critical.

Select all check boxes

Without output request

In processing

Completed

Incorrect

and give time period as older than the number of days based on your analysis.

Also under category and/or select or radio buttons. Also select all check boxes under obsolete. and requests with output devices that no longer exist-

Select radio button option Every day and keep the field Factory calender id blank.

I ran the report in Log with deleting mode in order to confirm what was it deleting in the first place. The output of this test run will be the spool number that will be deleted if this report is run in actual mode.

After I was satisfied with the output I actually deleted the spool requests.

This is a bit iterative but will solve your issue.

Regards.

Ruchit.