Is "Enter" the only way to let an ABAP OO editable ALV know data's changed?

Question

In the past two years, I've coded numerous ABAP OO editable ALV's, and once Uwe set me straight about how ti use the canned "handle data changed" methods,. it's been very straightforward.
But here's my question.
I have a modal dialog box in a MIGO dialog exit (yes, there is one although it's in a very odd function group - XQSM.)
In the modal dialog box, I have an editable ALV and an OK pushbutton underneath it.
If the user enters data into the ALV and then presses OK immediately afterwards (without pressing ENTER first), the ALV doesn't recognize that data has been entered.  So the underlying itab winds up empty.
What is the right way to handle this?
Is there a way of forcing the ALV to do its thing from within the PAI that handles the OK pushbutton?
At my last client, the customers were willing to live with this as a training issue - tell the users to hit ENTER at least once before pressing OK.
But surely, SAP must have something else in mind here that I'm not yet aware of.
Thanks for any advice anyone can provide.
djh

Answer 1

Hi Vijay -
Thanks for both answers!
Regarding your first answer, here's my current code:
class lcl_event_receiver          definition deferred.
data:
  o_event_receiver                  type ref to lcl_event_receiver.
class lcl_event_receiver definition.
public section.
    methods:
      handle_data_changed
         for event data_changed of cl_gui_alv_grid
             importing er_data_changed.
private section.
endclass.
And this:
  call method o_grid->register_edit_event
               exporting
                  i_event_id = cl_gui_alv_grid=>mc_evt_enter.
  create object o_event_receiver.
  set handler o_event_receiver->handle_data_changed for o_grid
Are you saying that instead of mc_evt_enter, I should use "mc_evt_modified" ????
Please clarify if you have the time.
Thanks
djh