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

Problem in Tabs of Module pool program

Former Member
0 Likes
457

Hello,

We have one Module pool program output. There are four tabs. We are facing few problems in it. When we click on button F3 of one tab for ' BACK' the focus remains in same tab. We have coded F3 for BACK with PF-status. Also, we have used activetab.

For ex. in Tab2 one if we click F3 control should be transferred to Tab1. But it is focussing on Tab.1 only.We have written code if Sy-ucomm = 'BACK'

tabstr-activetab = 'Tab1'.

dynno = 110.

endif.

When I debugged the code, Sy-ucomm is not taking any value. What can be the reason?

Initially, Case Tab1, Case Tab2 executes fine. Case BACK is also getting executed in outside loop but in inner loop it is not taking value.

Please suggest.

Regards,

Harish

2 REPLIES 2
Read only

Former Member
0 Likes
351

This is not likely the solution, but consider that the sy-ucomm value will be placed in the "OK_CODE" you set up for the primary screen, and not from the tab. The subscreens imbedded in each tab, iirc, cannot have an "OK_CODE" assigned to them.

If you have a user command or exit command module for the primary screen (PAI), it will handle ithe F3 / BACK there if you test for it. Otherwise a user command module in the subscreen PAI can be set to handle it as it will be passed through to it.

If I understand your goal properly, personally, I would not have a "catch" in the primary screen for the BACK, and then put it either in the EXIT or the USER command modules depending on your desire as to edit the subscreen or not before you act on the BACK action. To have it react in the the EXIT module, you'd need to set the PF-STATUS for it as an EXIT vs Normal.

Read only

Former Member
0 Likes
351

Hello

Thanks for the help.