CL_SQL_STATEMENT versus direct SELECT

Hi Guys,

at this moment I want to create a generic function that is able to fetch data directly from the database via a query.

Since I want to have some freedom in adding nested selects etcetera I wanted to use the CL_SQL_STATEMENT class.

Unfortunatly this class doesn't return the same result as a direct select. It seems that the numerical fields get shifted (after 3000 characters). See screenshot/code sample and database definition below. Any suggestions?

Please consider the following (very large) database definition for my table (ZTB_IU_NBI_RAW):

Please consider this code:

REPORT ztest_cl_sql_statement.DATA scr_messageid TYPE zde_iu_nbi_messid.
SELECT-OPTIONS so_mess FOR scr_messageid.INITIALIZATION.  so_mess[]=VALUE #(SIGN='I'OPTION='EQ'(LOW='1-IAENKH')  (LOW='1-IDS6SW')  (LOW='1-IDSL1O')  (LOW='1-II9KK6')  (LOW='1-IIKMUM')  (LOW='1-IIKMUS')  (LOW='1-IKM9L9')).START-OF-SELECTION.  DATA lv_query TYPESTRING.  DATA lt_test TYPESTANDARD TABLE OF ztb_iu_nbi_raw.  DATA lt_testd TYPESTANDARD TABLE OF ztb_iu_nbi_raw.  lv_query = |SELECT*FROM ZTB_IU_NBI_RAW WHERE mandt ='261'|.  DATA lv_sub TYPESTRING.  LOOP AT so_mess ASSIGNING FIELD-SYMBOL(<fs_m>).    IF sy-tabix EQ1.      lv_sub = |AND messageid IN('{ <fs_m>-low }' |.    ELSEIF sy-tabix EQLINES( so_mess ).      lv_sub = |{ lv_sub },'{ <fs_m>-low }')|.    ELSE.      lv_sub = |{ lv_sub },'{ <fs_m>-low }'|.    ENDIF.  ENDLOOP.  IF sy-subrc EQ0. lv_query = |{ lv_query }{ lv_sub }|.ENDIF.* New SQL approach  TRY.      DATA(lo_query)= NEW cl_sql_statement().      DATA(lo_result)= lo_query->execute_query( lv_query ).      lo_result->set_param_table( REF #( lt_test )).      lo_result->next_package().      lo_result->CLOSE().    CATCH cx_sql_exception INTODATA(lx_sql).      DATA(ev_message)= lx_sql->sql_message.  ENDTRY.* Versus old SQL approach  SELECT*FROM ztb_iu_nbi_raw INTOTABLE lt_testd WHERE messageid IN so_mess.* This statement fails - numeric fields in lt_nbid are shifted  ASSERT lt_test = lt_testd.