topic ALV Editable ( Validate changed Value ) in Application Development and Automation Discussions

ALV Editable ( Validate changed Value )

Former Member — Thu, 16 Jul 2009 03:32:12 GMT

Hi Gurus,

I have a requiremnet on ALV.

I have a program ZTEST with screen no 9000.

I have a container places on the screen 9000

from PBO module of screen 9000

I am passing an internal table gt_xvbep with 3 values

VBELN , TIMEFROM , TIMETO

234000 10:00:00 12:00:00

234002 13:00:00 15:00:00

Fields TIMEFROM and TIMETO are 'editable" and of type DATS

When user enters a values on screen

TIMEFROM should be always greater than TIMETO.

I need to validate the above scenario

When ever user enters TIMEFROM > TIMETO ans press enter I need to show an error message "TO time should be greater than FRom time"

Please let me know how I can catch "ENTER" event in ALV in OOPS and validate the fields

Regards

Avi.

Re: ALV Editable ( Validate changed Value )

Former Member — Thu, 16 Jul 2009 03:46:04 GMT

in your module user command, have this as the first statement.

To capture the changed data on ALV grid & chack the changed data

CALL METHOD g_alv_grid->check_changed_data.

Then write a perform to validate the dates with a simple comparision logic.

If you are handling the dates for several zones....make sure you convert the timezone which will be some thing like...

CONVERT TIME STAMP.... INTO DATE <>. tAKE F1 HELP AND CHECK OUT.

Thanks,

Kiran

Re: ALV Editable ( Validate changed Value )

Former Member — Thu, 16 Jul 2009 07:55:57 GMT

check the standard report bcalv_test_grid_editable

Re: ALV Editable ( Validate changed Value )

Former Member — Tue, 03 Nov 2009 02:10:58 GMT

Re: ALV Editable ( Validate changed Value )

Former Member — Tue, 03 Nov 2009 20:39:26 GMT

Hi Avi

1) Catch the enter event or modified event. Enter event is caught whenever you press enter after edit a field. If you edit a field and then press TAB to go to another field than the Enter event is NOT CAUGHT. However if you use MODIFY

event then ENTER event is also caught.

Example:

* Create the event or modified hanlder object

CREATE OBJECT g_events.

SET HANDLER g_events->data_changed FOR gref_alv_list.

* Modify Event

CALL METHOD gref_alv_list->register_edit_event

EXPORTING

i_event_id = cl_gui_alv_grid=>mc_evt_modified.

* Or Enter Event

CALL METHOD gref_alv_list->register_edit_event

EXPORTING

i_event_id = cl_gui_alv_grid=>mc_evt_enter.

2) To be able to check data, you could do the following

First, create class definition

-

CLASS lcl_events DEFINITION.

PUBLIC SECTION.

METHODS:

data_changed FOR EVENT data_changed OF cl_gui_alv_grid

IMPORTING er_data_changed

e_onf4

e_onf4_before

e_onf4_after

e_ucomm.

ENDCLASS.

Second, implementation

-

METHOD data_changed.

DATA: ls_mod TYPE lvc_s_modi,

ls_ins TYPE lvc_s_moce,

ls_del TYPE lvc_s_moce.

* To get rows that have been deleted if needed

LOOP AT er_data_changed->mt_deleted_rows INTO ls_del.

ENDLOOP.

* To get rows that have been inserted if needed

LOOP AT er_data_changed->mt_inserted_rows INTO ls_ins.

ENDLOOP.

* To get cells that have been changed if needed

LOOP AT er_data_changed->mt_mod_cells INTO ls_mod.

* You do your verififcation here

* Add Message error if necessary by calling add_protocol_entry

call method er_data_changed->add_protocol_entry

exporting

i_msgid = sy-msgid

i_msgty = sy-msgty

i_msgno = sy-msgno

i_msgv1 = sy-msgv1

i_msgv2 = sy-msgv2

i_msgv3 = sy-msgv3

i_msgv4 = sy-msgv4

i_fieldname = Your table filed name here or any other value

i_row_id = Your table row number here or any other value

* Display message error if necessary by calling add_protocol_entry

CALL METHOD er_data_changed->display_protocol.

ENDLOOP.

ENDMETHOD. "data_changed

Dean Q.

Good luck

Edited by: Dean Q on Nov 3, 2009 9:52 PM