topic Re: Internal Sessions in Application Development and Automation Discussions

Internal Sessions

Former Member — Mon, 07 Dec 2009 07:33:53 GMT

Hi Guys,

We have developed a Tree on clciking node it calls another transaction, and again on clicking on another leaf , call another trnsaction. Now as we know SAP limits the internal sessions, after 6 clicks/ calls the maximum internal sessions are reached and system throws up error. Is there any way to increace number of internal sessions?

It looks something like se80.

Can any one give any idea how to handle these navigations, i cannot use leave to Transaction instead of call transaction as i need to have bckwrd navigation as well.

Regards, Trivenn

Re: Internal Sessions

Sm1tje — Mon, 07 Dec 2009 07:49:15 GMT

There is a profile parameter rdisp/max_alt_modes which can be maintained in transaction RZ11. However, this is normally only done by basis administrators. So I would suggest to consult with them first. Since this is system wide parameter, I can (and probably will) have quite an impact on the system load (performance).

After clicking a node (subnode) and a new session is opened, don't the users close this session? Six sessions per user should, in most cases, be more than sufficient.

Re: Internal Sessions

Former Member — Mon, 07 Dec 2009 08:00:12 GMT

Different nodes in tree represent different objects. Each oject has an Id and can be created/changed/viewed through transacions. So On double click of a node , i am calling transaction by setting some parameters, and the Tree is re-initiated for that transaction. so at a given point of time user is able to see only one screen.

Edited by: Trivvka on Dec 7, 2009 9:00 AM

Re: Internal Sessions

RaymondGiuseppi — Mon, 07 Dec 2009 08:13:09 GMT

You may try to use FM DY_IS_EXTRA_IMODE_AVAILABLE to check if another mode is available, take a look at [Note 1229222 - Data loss with message: Maximum number of internal sessions|https://service.sap.com/sap/support/notes/1229222] and (old) [Note 34154 - Maximum number of internal sessions reached|https://service.sap.com/sap/support/notes/34154]

Else manage yourself in your report a "stack" of the "calls", holding data needed to re-display the screen when user press "back" function (data, cursor, etc.)

Regards,

Raymond

Re: Internal Sessions

Former Member — Tue, 08 Dec 2009 08:54:16 GMT

hi,

Try this code..It will solve UR problem...

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

REPORT ZSAMPLE.

data: ipid type table of RFC_SPAGPA.

data: xpid type RFC_SPAGPA.

data l_flag type i VALUE 1.

SELECTION-SCREEN PUSHBUTTON /50(10) but1 USER-COMMAND cli1.

SELECTION-SCREEN PUSHBUTTON 70(10) but2 USER-COMMAND cli2.

INITIALIZATION.

but1 = 'Call'.

but2 = 'Exit'.

AT SELECTION-SCREEN .

CASE sy-ucomm.

WHEN 'CLI1'.

if l_flag = 2.

CALL FUNCTION 'TH_DELETE_MODE'

EXPORTING

MODE = 5.

endif.

l_flag = 2.

xpid-PARID = 'MAT'.

xpid-parval = 'M-10'.

append xpid to ipid.

call function 'ABAP4_CALL_TRANSACTION'

starting new task 'TestTask'

exporting

tcode = 'MM03'

SKIP_SCREEN = 'X'

TABLES

SPAGPA_TAB = ipid.

WHEN 'CLI2'.

LEAVE PROGRAM.

ENDCASE.

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

Regards,

Arun

Re: Internal Sessions

Former Member — Wed, 16 Dec 2009 10:56:56 GMT

Hi Raymond:

That information was very valuable. But i cannot find this Function Module : DY_IS_EXTRA_IMODE_AVAILABLE , although we use ECC 6.0 .

I think, as you suggested, stacking up is the only solution.

Regards,