Incorrect (Error in ABAP processing) - Error in Spool request

[keyur_pawar]

Hello friends,

I check my spool request in SP02, there is an error : Incorrect (Error in ABAP processing).

When I gave print order to my smartform which having 500 pages that time this error occurs, but when I go

for only 100 pages to take print that time it works fine, no error occur & I can take printout easily.

But When I go for such bulk printouts (500 - and above pages) that time after creation of spool request it doesn't process &

throw the above error.

Please, guide me & give me solution for this problem.

Where I'm going wrong, is it memory problem or anything else ?

Awaiting for response.

I attached the error analysis given in SP02 log. kindly refer it.

Regards,

Keyur Pawar.

[Former Member]

Hi

do you see also a dump when it happens that error?

It seems to me you are printing in foreground, have you tried to print in background with a predefined printer?

Did you check this  thread? http://scn.sap.com/thread/1093803

Let me know

a

[keyur_pawar]

Thanks for reply Andrea,

There is no dump occur here.

I attach one more image here which shows the status of that spool request.

and please guide me how to print in background with predefined printer & what should

i do to solve this issue ?

Regards,

Keyur Pawar.

[Former Member]

Hi Keyur

i had another thought.

Can you go to RZ11 , specify the parameter rspo/auth/pagelimit and click display (in case your Current Value is 1, you have to modify this to 0)

Forget the print in background because i dont think it is your case but check the note Note 1765559 - Short dump when printing on label printer even if you are not printing on barcode

Let me know

a

[DavidLY]

Hello,

Are you using frontend printing with Access method F or G?

SAP strongly recommends NOT to use frontend printimng for mass or critical printings (SAP note 128105).

Regards,

David

[keyur_pawar]

Hi David,

Thanks for reply,

Access method currently we are using is 'G'.

so please suggest me which access method should I use, then I can solve my problem or

should I focus on other parameters ?? 

Regards,

Keyur Pawar.

[DavidLY]

Hello,

For THIS problem: Per default only one sp_wp can handle frontend printing per instance (see SAP note 351492). You mey need to increase the parameters mentioned in the SAP note.

The problem is the mass printing with access method G. You should check the parameter 'rdisp/wp_no_spo_Fro_max'. The number of  spool processes available for Frontend printing is set by this parameter. You can find this also in the SAP note: 108799.

Also check the SAP note 118057 for mass printing.

Regards,

David

[arindam_m]

Hi,

Check your spool administration details. Following link might give some idea:

https://help.sap.com/saphelp_nw04/helpdata/en/18/2625c6fed011d18e410000e83dd9fc/content.htm

Check the Output Devices section.

Cheers,

Arindam

[keyur_pawar]

Hello friends,

Thanks for reply,

I tried all solutions. I make changes in parameters as per your suggestions with the help of Basis person, but I'm facing same problem for bulk printing. Problem is not solved yet.

Can any one deeply focus on this issue. Your response is appreciable for me.

Regards,

Keyur Pawar.

[Former Member]

Hi Keyur

is it stopping always with a certain amunt of pages / time or it is random?

Let us know

a

[arindam_m]

Hi,

In your case limitations are in the spool printing parameters. There is limit on memory usage when you are processing spools. Can you split your spool processing and generate multiple jobs or spools and process the whole data. Should help you to overcome the issue.

Cheers,

Arindam

[keyur_pawar]

hi andrea,

It stopping always whenever I gives order for more than 100 pages,

I think it is not presentation server memory problem, because I tried on various presentation servers,

It might be database server issue.

Please let me know if you have any solution for this.

Regards,

- Keyur

[Former Member]

Keyur,

have you tried to print that to a local device. (even pdf...)

It would be really helpful to isolate where the problem really is (db - application - presentation)

let me know

a