Dynamic table for infotype 2010 in HCM form

Question

Hi,
I have a project requirement for a form that has got me stuck for days now, so I was wondering if anyone could help.
The form in question is a statement of allowances (recording overtime), which ideally will allow the user to enter in any overtime within a fortnight. For each day in the fortnight, they are to be able to enter in any number of infotype 2010 records. As such, the layout requires a table with the columns being the 14 days, and the rows being the 2010 records (based on wagetypes).
As the user is able to enter in any amount of 2010 records for each day, the table needs the ability to grow dynamically. I have no problem doing this in the Adobe form itself, but my issue right now is defining the fields for the form.
As I understand it, there are some infoypes (such as 0041 and 0008) that are able to be defined in the form scenario fields as a line type. This will allow multiple instances of that infotype to be created/updated. However, since 2010 does not have this option, I am only able to define a single instance of that infotype.
I am still fairly new to this framework, and I did play around with generic services to see if I could define my structure there and map it across to the form, but so far I have not been successful. I was hoping to be able to define a table of type p2010 and pull it across to be used in the form.
My issues in summary are as follows:
1. Need to define a table/structure of type p2010 to be used in the form
2. As the number of rows in the table will only be specified at runtime, how do I map the cells to the corresponding fields?
Any ideas or suggestions would be very helpful.
Joanna

Answer 1

See you will manually get the relevant data from IT2010 and save it an internal table.
now this data for eg contains 3 line items whcih you need to show in the form in a table.
itab-fld1         itab-fld2               itab-fld3
val1                  val2                     val3
val4                  val5                     val6
val7                  val8                     val9
Now you must have defined the fields in the generic service. add the fields in the service_dataset not the standard service fields.
in the get field info method
DATA ls_field_info TYPE hrasr00gs_field_info .
  DATA ls_service_field TYPE fieldname.
  CLEAR field_infos.
  LOOP AT service_fields INTO ls_service_field.
    CASE ls_service_field.
      WHEN c_fieldname1.
Reason
        CLEAR ls_field_info.
        ls_field_info-fieldname = c_fieldname1.
        ls_field_info-field_data_element_name = c_dtel_reason.
        ls_field_info-supports_value_help = true.
        ls_field_info-supports_default_value = true.
        APPEND ls_field_info TO field_infos.
endcase.
endloop.
IN method get operations
DATA ls_operation TYPE hrasr00gs_operation.
  CLEAR operations .
operation GET 2010
  CLEAR ls_operation.
  ls_operation-operation = c_oper_get_reason.
  ls_operation-fieldnames = get_fields_of_operation( ls_operation-operation ).
  APPEND ls_operation TO operations.
in method get fields of operation
  CASE operation.
    WHEN c_oper_get_reason.
      APPEND c_fieldname1          TO fieldnames.      
Now in the initization method you will find your fields in service_field_values. Now for table entry fields increase the index value as mentioned before.