short dump while using call selection-screen mdynnr

[Former Member]

Hi ALL,

I need your help and information.

In programmes, We are using the statament " CALL SELECTION-SCREEN MDYNNR "

and passing the screens dynamically into variable mdynnr.

And the programme is going to dump after executing 50 times.

When we

can we use any other statement instead of CALL SELECTION-SCREEN MDYNNR.

Your information helps us lot.

Thanks in advance.

Srinivasa Reddy.

[Former Member]

Hi,

what dump u r getting.. check whether it is calling invalid selection screen while you populate screen dynamically?

[Former Member]

Hi,

Thanks For your Quick Response.

I am Getting the error like "LIST_TOO_MANY_LPROS".

Thanks in Advance

Srinivasa Reddy.

[Former Member]

Hi,

I believe you are calling the selection screens nested manner, this is limited to max 50.

[Former Member]

Yes, we are calling in the same manner and we are getting the short dump after exceeding the limit of 50.

Thanks in Advance

Srinivasa Reddy

[Former Member]

Hi Tangirala,

Instead of using "CALL SCREEN" use "LEAVE TO SCREEN".

Hopes it will help you.

Ali

[Former Member]

Hi,

We are using the statement like CALL SELECTION-SCREEN MDYNNR

we are passing the variable mdynnr dynamically.

we can not pass a variable in the statement leave to screen or leave screen.

please advise.

Thanks in Advance.

Srinivasa Reddy.

[former_member376453]

Hi,

I suggest you to use a function module for this and add the screen in this function module. Then you can call the FM more that 50 times and it will work properly. hope fully this will help you.

Thanks,

[Former Member]

Hi,

Is there any other statement instead of FM and call selection-screen mdynnr.

Thanks inadvance.

Srinivasa Reddy.

[hymavathi_oruganti]

u want to call a selection screen or a normal screen?

[Former Member]

I want to call selection-screen

[former_member376453]

Hi,

As you know Call Screen is the statement, but you will get the problem if you are going to call it in the same LUW repeatedly. So, FM is the only convenient way to do it. This is very easy. Just create a FM and replace you statement with this FM. Hopefully this will solve your problem.

Check this comment " When you call a new main program in order to use a screen sequence (for example, using CALL TRANSACTION), a new SAP LUW begins. This may be an undesired effect, especially when you are trying to modularize a transaction that updates the database.

An alternative to this is to use an external procedure, whose main program is linked to a screen sequence, and which contains the corresponding dialog modules. Procedures run in the same SAP LUW and internal session as their calling program."

Thanks,

[Former Member]

Hi Everybody,

please help me on this issue.

Thanks in advance

Srinivasa Reddy.

[hymavathi_oruganti]

hi, if u want to call selection screen, u have to use

call selection screen <scrno>.

if u want to call noraml screen

u have to use

call screen <scrno>.

which screen u r calling?