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: 

Capturing a F3 back click fro, Secondary List in AT LINE-SELECTION

0 Kudos
772

Hi All,

I have a program where I call a NON ALV secondary list where I output several write statements to the screen. If a user just clicks the Green Arrow back it takes him back to the selection screen which is fine HOWEVER the selection screen is not set as if first time "Fresh" : which is what is required. I tried creating a PF-Status and put it before the perform secondary list in AT LINE-SELECTION but the on-command is never called. There is no screen number for this screen How do I capture a user trying to exit to generic window that the secondary list uses so I can do something like "SUBMIT XXX VIA SELECTION-SCREEN."

System Status of Secondary List

3 REPLIES 3

Sandra_Rossi
Active Contributor
474

I'm confused a lot. A "secondary list" comes only after a list is created during the AT LINE-SELECTION in a "basic list". It's illogic to go directly to the selection screen when leaving a secondary list, as it should first return to the basic list. What do you mean "Fresh"? (AFAIK the program is restarted after the basic list is left, if it has been displayed implicitly after the start-of-selection/end-of-selection events). If your question is restricted to only "capturing an exit function in an ABAP list", then you should use AT USER-COMMAND.

retired_member
Product and Topic Expert
Product and Topic Expert
0 Kudos
474

I don't understand your question, but the standard behavior of function code BACK cannot be overwritten.

You have to set you own GUI status, take over the list template, replace BACK with an own function code and react with AT USER-COMMAND on that function code. Navigating through list levels can be achieved by setting sy-lsind (one of the exceptions to the rule not to set system fields in a program).

For more information see, e.g.,

0 Kudos
474

Hi Sandra, Horst,

To better summarize after the secondary list is finished the program returns to the selection screen with the last radio button selected still active, this prevents the users from entering info as if the screen had been initially started. They want it to come back as initial, I do this in a couple other instances in the program after I call a transaction using CALL TRANSACTION XX AND SKIP FIRST SCREEN. Then i use SUBMIT ZPROGRAM VIA SELECTION-SCREEN This returns the selection screen to a "fresh" or initialized version.

Is thee someplace after the secondary list completes that I can do a submit to call the selection screen again OR perhaps a place I can use memory ID to reset the radio buttons?

Thanks,

Jim