WD4A Dynamic ALV Table with dynamic tables

Question

Hi all,
first I want give you the information what I try to do.
I have an another WD4A application for administrative use in which I can assign certain tablefields to a certain user. You can say it's something like a customizing application.
In the next application (with my issues) I will display the tables for the user, but these tables are not the complete table.
I have a node in my context of the component controller which is bound to my ALV. I add during the runtime attributes to my node.
* .... coding ....declaration
* get the node
  lr_node = wd_context->get_child_node( 'M_TABLE' ).
  lr_node_info ?= lr_node->get_node_info( ).
* remove the attributes, if exists
  lr_node_info->remove_dynamic_attributes( ).
* .... coding ....
*   add attributes
    LOOP AT l_t_m_table INTO l_s_m_table.
      CLEAR ls_attribute.
*     name of the attribute
      MOVE l_s_m_table-NAME TO ls_attribute-NAME.
*     DDIC type of the attribute
      MOVE l_s_m_table-TYPE_NAME TO ls_attribute-TYPE_NAME.
*     If the DDIC has a gen namespace like /B135/ replace the / with _
      REPLACE ALL OCCURRENCES OF '/' IN ls_attribute-NAME WITH '_'.
*     add the attribute
      lr_node_info->add_attribute( EXPORTING
                                     attribute_info = ls_attribute ).
    ENDLOOP.
This coding works fine I get the columns in my ALV. Then I tried to fill my ALV table with data from a database table.
I created dynamicly an internal table with the following coding:
*   Create dynamic table
    CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
      EXPORTING
        IT_FIELDCATALOG = l_t_FLDCAT
      IMPORTING
        EP_TABLE = l_t_NEW_M_TABLE.
*   assign the table
    ASSIGN l_t_NEW_M_TABLE->* TO <M_TABLE>.
*   structure of table
    CREATE DATA l_s_NEW_M_TABLE LIKE LINE OF <M_TABLE>.
    ASSIGN l_s_NEW_M_TABLE->* TO <l_s_m_table>.
* get data from database
SELECT * FROM (l_m_table) INTO CORRESPONDING FIELDS OF TABLE <M_table> WHERE OBJVERS = 'A'.
With this coding I get the data from the database and only the required fields that means I have e.g. an itab with columns1, columns3, columns4 from the database.
I also added e.g. these columns  (columns1, columns3, columns4 from the database) to the node as attribute. Now it should be possible to bind the table to the structure with this coding:
lr_comp_usage_m = wd_this->wd_cpuse_usage_alv_M_table( ).
*   create component if not active
    IF lr_comp_usage_m->has_active_component( ) IS INITIAL.
      lr_comp_usage_m->create_component( ).
    else.
* set data if node exists
      l_ref_interfacecontroller = wd_this->wd_cpifc_usage_alv_M_table( ).
      l_ref_interfacecontroller->set_data( lr_node ).
    endif.
*   bind table
    lr_node->bind_table( <M_TABLE> ).
Now, I get an error, which is caused by the table binding.
In ST22 I get:
Short text
    Line types of an internal table and a work area not compatible.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_WDR_CONTEXT_NODE_VAL=======CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    The statement
       "INSERT wa INTO TABLE itab"
    requires the lines of the internal table "TABLE" and the
    work area " wa" to be compatible. Compatibility means
    equivalence in the context of ABAP/4 type checking.
    In this case, the condition is not satisfied because the internal table
    "TABLE" has the line type "u" and the length 28, but the work area " wa"
    has the type "C" and the length 2.
    (If the work area " wa" is the header line of the internal
    table "TABLE", the above inconsistency can arise if an internal
    table t with the line type T1 is passed to a subroutine (FORM or
    FUNCTION) as an actual parameter and the corresponding formal
    parameter p is declared in the subroutine by "TABLES p STRUCTURE T2".
    If then T1 and T2 are incompatible, the header line p
    has the type T2 (specifed by STRUCTURE), but the internal
    table p has the line type T1 (passed from the actual parameter)).
Source Code Extract
Line  SourceCde
    1 method if_wd_context_node~get_static_attributes_table .
    2
    3   field-symbols:
    4     <element> like line of me->collection,
    5     <static_attributes> type data,
    6     <table> type index table.
    7
    8 * check whether elements are supllied or not
    9   if me->elements_supplied = abap_false.
   10     me->supply_elements( ).
   11   endif.
   12
   13   clear table.
   14
   15   if me->table_ref is not initial.
   16     assign me->table_ref->* to <table>.
   17     table = <table>.
   18   else.
   19     loop at me->collection assigning <element> from from to to.
   20       assign <element>->static_attributes->* to <static_attributes>.
error in line 21       insert <static_attributes> into table table.
   22     endloop.
   23   endif.
   24
   25 endmethod.
Any suggestions? Is it allowed to use bind_table() with a field symbol?
Another strange thing is that if I try the same with static itab and attributes during runtime it works, but only if the fields of the itab has the same name as the attributes, which means that I can not use itabs with fieldnames like /BI0/S_CUSTOMER and if I can not use them it's difficult to read data from database with SELECT * FROM ... INTO CORRESPONDING FIELDS OF TABLE itab.
Thanks in advance for your suggestions!
Best Regards,
Marcel

Answer 1

Hi Francois,
I solve it with the RTTI and the method    
lr_node_info = lr_node_info->add_new_child_node(
                      name = 'Dynamic_TABLE'
                      IS_MANDATORY = ABAP_false
                      IS_MULTIPLE = ABAP_true
                      STATIC_ELEMENT_RTTI = lr_struct_descr
                      IS_STATIC = ABAP_false
I don't know why it doesn't work with adding attributes and binding the table after adding the attributes.
Anyway thanks for your help.
Best Regards,
Marcel