Field not validated from ABAP dictionary

Question

HI ,
I have created ALV using OOP. . I implemented  F4 functionality on the field AUFNR on output . for validation on AUFNR i passed ref field(aufnr) and ref tab(aufk) in field catalog but still it is not validating .
field catalog :
i_fieldcat_line-fieldname   = c_aufnr.
  i_fieldcat_line-coltext     = c_prod.
  i_fieldcat_line-scrtext_m   = c_prod.
  i_fieldcat_line-col_opt     = c_x.
  i_fieldcat_line-edit        = c_x.
  i_fieldcat_line-f4availabl  = c_x.
  i_fieldcat_line-ref_table   = 'AUFK'.
  i_fieldcat_line-ref_field   = 'AUFNR'.
*  i_fieldcat_line-checktable  = c_aufk.
  i_fieldcat_line-key         = c_x.
  i_fieldcat_line-col_pos     = 2.
  i_fieldcat_line-outputlen   = 12.
could you please help me ?
Thanks ,
Mayank

Answer 1

Hi Mayank ,
In OO  provided you have an editable grid  register the event ENTER.
Once this is done you can use two methods HANDLE_DATA_CHANGE which will be entered if any data is actually changed and the user presses ENTER and HANDLE_DATA_CHANGE_FINISHED which is  entered after you've done your changes.
If no data is changed then the event is not raised and you don't have to do any validation etc.Using your method with the &SAVE functionality you don't know if the user has actually entered anything or not. You'd have to validate your whole table before saving and also decide what to do on any error(s). Your table could have say 20,000 lines or more -- to validate this would definitely be a beginners way - very inefficient and totally elephantine.With the Data changed method you can work interactively and you are only dealing with changed data. You get control at data entry time which is far better than waiting until  you get to SAVE and then have to decide what to do.
In these methods you should be able to examine your data and take the appropriate action.
You don't need any special toolbar functionality unless you want to say re-display the changed grid and save it to SAP tables / run transactions / create IDOCS etc etc.
I think this is actually better than using a toolbar function as there is nothing to stop the user from either pressing the toolbar when nothing has been changed or you then have to do a whole set of validation after the user has entered a whole lot of data (and you still have to get the user's data anyway).
Why not let the system give it to you in the data changed method --there you can validate it.
By all means add a toolbars for SAVE / UPDATE etc if you want.
You do this by adding the functions to the alv toolbar in ON_TOOLBAR and use the ON_USER_COMMAND method to execute the function when the toolbar button is pressed.
Look for some of my previous posts -- I've posted the code often enough.
However for the Data changed stuff.
in your program add these events, methods and handlers
DATA: g_handler TYPE REF TO lcl_event_handler. "handler DATA grid_container1 TYPE REF TO cl_gui_custom_container . DATA grid1 TYPE REF TO cl_gui_alv_grid..  CLASS lcl_event_handler DEFINITION .   PUBLIC SECTION .     METHODS:  .... your other methods  * data changed handle_data_changed     for event data_changed of cl_gui_alv_grid       importing er_data_changed, *data changed finished handle_data_changed_finished      for event data_changed of cl_gui_alv_grid. ...... ENDCLASS.                    "lcl_event_handler DEFINITION  CLASS lcl_event_handler IMPLEMENTATION.  * Your other methods ........... method handle_data_changed.   perform data_changed using er_data_changed.    endmethod.                    "data_changed    method handle_data_changed_finished.     perform data_changed_finished.   endmethod.                    "data_changed_finished  ENDCLASS.
In your application program
form data_changed   using er_data_changed.    break-point 1. * code validation routines etc here  endform. form data_changed_finished.  * code any requirements after all changes finished   break-point 1. endform.  * before displaying the grid struct_grid_lset-sel_mode = 'D'.   CREATE OBJECT g_handler.   SET HANDLER g_handler->handle_double_click FOR grid1.   SET HANDLER g_handler->handle_hotspot_click FOR grid1.   SET HANDLER g_handler->handle_toolbar FOR grid1.   SET HANDLER g_handler->handle_user_command FOR grid1.   SET HANDLER g_handler->handle_data_changed FOR grid1.   SET HANDLER g_handler->handle_data_changed_finished FOR grid1.     CALL METHOD grid1->register_edit_event        EXPORTING           i_event_id = cl_gui_alv_grid=>mc_evt_enter.
just add your own code in the forms data_changed and data_changed finished.
You can get the contents of the parameter er_data_changed from cl_gui_alv_grid  via SE24.
Hope this will help you.........
Regards ,
Yogendra Bhaskar