topic Re: Maximum Internal Sessions in Application Development and Automation Discussions

Maximum Internal Sessions

former_member51562 — Tue, 03 Mar 2009 19:18:57 GMT

I have a module pool that is designed to allow users to input budget data. As part of the functionality of these screens, there is a button that the user can click to review the data that he just input. This data is being displayed via ALV grid.

In the ALV grid, I have a hot-key defined to take the user back to a specific point in the module pool, editing the data that was clicked on from the ALV grid.

The problem is that I am getting "Maximum Internal Sessions" error. I understand why, but cannot figure out a resolution.

From the module pool, I am doing a SUBMIT ALVPROGRAM. (with no return).

From the ALV Grid program, I am doing a CALL TRANSACTION. (to get back into my module pool at a specific point.).

Is there a way to cancel or exit an internal session so that I do not leave all of these 'orphaned' sessions after I return from the ALV Grid program?

Re: Maximum Internal Sessions

Former Member — Wed, 04 Mar 2009 03:32:34 GMT

Please check this [link|https://www.sdn.sap.com/irj/scn/advancedsearch?query=maximumInternalSessions&cat=sdn_all] and i hope when you are going away from ALV it will be good if you flush memory.

Regards,

~Satya

Re: Maximum Internal Sessions

Former Member — Wed, 04 Mar 2009 05:13:09 GMT

Hi,

By calling the transaction with "CALL TRANSACTION ..." statement, you keep the current transaction's program data and open a new internal session. That why getting error as maximum internal sessions.

The solution is to use "LEAVE TO TRANSACTION ..." which ends the current transaction session, and then opens the new session.

Thanks,

SMITA

Edited by: Smita Gupta on Mar 4, 2009 6:17 AM