Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Column Tree: returning to selection screen

peter_atkin
Active Contributor
0 Likes
861

Guys,

In a moment of pure genious I've created a work-of-art with column-trees. The report works great - except for one little problem....

I can't seem to get back to the selection-screen without loosing the original selection-screen values.

I've tried heaps of things without luck:

set screen 0, leave screen

call selection screen 1000

call transaction ....

leave program

leave program to screen 0

Any better ideas?

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
818

Hi.

Have you tried to use memory id in your parameters?

Or instead above, you can do a little trick. Export value to memory during first run and after BACK recieve them in event at selection screen output.

It sounds very strange, but it should work

MB.

7 REPLIES 7
Read only

Former Member
0 Likes
819

Hi.

Have you tried to use memory id in your parameters?

Or instead above, you can do a little trick. Export value to memory during first run and after BACK recieve them in event at selection screen output.

It sounds very strange, but it should work

MB.

Read only

0 Likes
818

MB

Thnaks for the quick reply. I like the export/import option.

Is there an easy way to export all the selection-screen values to memory?

Read only

0 Likes
818

you can use FM RS_SELECTIONSCREEN_READ to read the current sel screen field values and export the return tab to memeoy and then you can use RS_SELECTIONSCREEN_UPDATE to set the value to the selscreen after importing from memeory

Regards

Raja

Read only

0 Likes
818

That's depend to the method you use to call the screen.

CALL SCREEN '0100'.

you back with the LEAVE TO SCREEN 0.

Rgd

Frédéric

Read only

0 Likes
818

Frédéric,

Thanks, that did the trick.

I was using:


set screen 100.
leave to transaction sy-tcode.

I changed it to:

call screen '0100'.

leave to screen 0.

PeteA

Read only

0 Likes
818

From the SAP documentation :

>>

Ends current processing and starts the (new) transaction tcod. All previous internal sessions are deleted from the stack and one new internal session is opened for the program of the transaction that was called. When this session has finished, the system returns to the next higher area menu.

<<

If you close the session, you will loose all the memory, so all the parameters that is not in the memory with a SET PARAMETER ID ...

Fred

Read only

Former Member
0 Likes
818

What are you talking about: Report or module pool (Transaction).

If report: have you ever tried

LEAVE LIST-PROCESSING

EXIT.