Auto batch determination for component in process order

[ibrahemy]

Hi experts,

My scenario automatic batch determination for component done while release process order

but i face a problem when process order component exceed 17 component per order i get run time error while release

i read error and i found that can't perform auto.batch for more than 17 component !

so i tried to select 16 and press batch icon for batch determination it works well !

and select rest of component as second step it works well also !

so my question is is this normal? is there was setting for solve this?

Thanks in advance

Regards,

Muhamed Ibrahem

[Caetano]

Hello

SAP KBA 2215866 - DBSQL_TOO_MANY_OPEN_CURSOR explains the system behavior:

"There is a hardcoded Kernel limit for the number of database cursors that can be open at the same time. Refer to SAP Note 2213554 for Kernel compatibility. If an application or customized program tries to open more than 16 database cursors at the same time, the cursor triggers runtime error DBSQL_TOO_MANY_OPEN_CURSOR."

I have never seen this kind of error in the standard batch determination, so I guess you have some kind of custom code in an exit or BAdI being executed during the batch determination. When the dump happens in your system, you have the option to open the ABAP debugger and then you can see the call stack and determine exactly where the dump is triggered.

Regards,
Caetano

[former_member42743]

Did you ask SAP yet about this?

C

[ibrahemy]

Hello criag,

Not yet,

May be this error exposed to experts before.

So if no one answered my question I will ask SAP

Regards,

Muhamed

[former_member42743]

This doesn't really seem like its a functionality that SAP would put in place.

I'd make sure you have you no customizations running.

Craig

[ibrahemy]

Hello Caetano,

thanks for your appreciated help

I tried to attach file with .txt format but get invalid file so below screen shot may be helpful

1-run-time-error.png

Regards,

Muhamed

[Caetano]

Hello Muhamed

A short dump may have different root causes.

Please provide more details about the short dump you are facing, such as the exact exception and the piece of code where it happens.
Regards,

Caetano