2009 Oct 16 8:37 AM
METHODS handle_data_changed_pop
FOR EVENT data_changed OF cl_gui_alv_grid
IMPORTING er_data_changed.
I trigger that with methoch check_data_changed..
Er_data_changed delivers the rows that are changed.
With this information I enrich the global table I have for set_table forfisrt_display.
Also I enrich this table with some other information.
I lose the some new information in the global table after I leave these methods - excpesially check data.
I don't know what to do...
---
Database Modify does also not work at that place of code... Is there a reason?
METHODS handle_data_changed_pop
FOR EVENT data_changed OF cl_gui_alv_grid
IMPORTING er_data_changed.
I trigger that with methoch check_data_changed..
Er_data_changed delivers the rows that are changed.
With this information I enrich the global table I have for set_table forfisrt_display.
Also I enrich this table with some other information.
I lose the some new information in the global table after I leave these methods - excpesially check data.
I don't know what to do...
---
Database Modify does also not work at that place of code... Is there a reason?
2009 Oct 18 9:23 PM
Hello Ezachiael
You should use the event handler method HANDLE_DATA_CHANGED only for validating new and modified data.
If you need to enrich your OUTTAB itab based on the input data just trigger PAI from your event handler method using:
CALL METHOD cl_gui_cfw=>set_new_ok_code ( ok_code = 'ENRICH_OUTPUT' ).
PAI is triggered with this new ok-code and HERE you should enrich your OUTTAB because all the changes from the ALV grid control (frontend) have now been forwarded to you ABAP itab (backend).
Regards
Uwe
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |