Application Development 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: 

Double click not functioning properly in alv grid using OOPS

chethankyadav
Explorer
0 Kudos
558

Hi,

I am having a problem like when, I double click the second time it is immediately exiting program.

Like, I have created a 2 docking containers, 1st screen has notifications details. 2nd screen has orders based on aufnr from 1st screen.

Now, I have written a condition after reading from internal table as ( if ls_qmel-aufnr is initial. message e001(msg_class). If this condition is true message triggers after I double click 1st time. But the same if I double click 2nd time it exits the program.

Can you check and let me know on this.

Thanks.

4 REPLIES 4

UweFetzer_se38
Active Contributor
144

Can you please try with an Info or warning message instead of the error message? For example i001(msg_class). Please report back whether this makes a difference or not. Then we may look deeper in your code.

0 Kudos
144

Hi Uwe Fetzer,

Here, as you said I have tried with following,

MESSAGE 'Its a message' TYPE 'I' DISPLAY LIKE 'E' ---- Its working i.e in 2nd double click or more it stays inside prg.

MESSAGE 'Its a message' TYPE 'E' DISPLAY LIKE 'S' ---- Its not working it exits prg after 2nd double click.

MESSAGE 'Its a message' TYPE 'W' DISPLAY LIKE 'E' ---- Its not working it exits prg after 2nd double click.

MESSAGE 'Its a message' TYPE 'E' DISPLAY LIKE 'S' ---- Its working but navigates to next screen after 2nd double click.

But it is working as per our requirement,

MESSAGE 'Its a message' TYPE 'S' DISPLAY LIKE 'E' ---- Its working i.e in 2nd double click or more it stays inside prg.

Thanks.

satyabrata_sahoo3
Contributor
0 Kudos
144

Debug and check what Function code is being executed upon double click.

0 Kudos
144

Ok, when I double click 1st time, debugger stops exactly at event class implementation READ statement and executes the message statement. But, for 2nd time if I use External debugger and even if I write BREAK-POINT statement it doesn't hit the debugger at all.

I have not checked with sy-ucomm let me check and let you know.