<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: type conflict when calling a function module in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996387#M1967510</link>
    <description>&lt;P&gt;You are nice to say "With header line is not necessary for your requirement", because it's just completely obsolete since 7.0 (2005), essentially because it's &lt;STRONG&gt;error prone &lt;/STRONG&gt;(good experience for the OP, I hope he will never do it again :-D).&lt;/P&gt;</description>
    <pubDate>Tue, 23 Jul 2019 07:33:37 GMT</pubDate>
    <dc:creator>Sandra_Rossi</dc:creator>
    <dc:date>2019-07-23T07:33:37Z</dc:date>
    <item>
      <title>type conflict when calling a function module</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996382#M1967505</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
  &lt;P&gt;i am getting type conflict error while executing the code, please help out to go my practice forward&lt;/P&gt;
  &lt;P&gt;REPORT ztest_m03_inner_joins.&lt;BR /&gt; TYPE-POOLS: slis.&lt;BR /&gt; TABLES: vbrk, vbrp.&lt;BR /&gt; TYPES: BEGIN OF ty_vbrk,&lt;BR /&gt; vbeln TYPE vbeln_vf,&lt;BR /&gt; fkart TYPE fkart,&lt;BR /&gt; fktyp TYPE fktyp,&lt;BR /&gt; vbtyp TYPE vbtyp,&lt;BR /&gt; END OF ty_vbrk.&lt;BR /&gt; &lt;BR /&gt; TYPES:BEGIN OF ty_vbrp,&lt;BR /&gt; vbeln TYPE vbeln_vf,&lt;BR /&gt; posnr TYPE posnr,&lt;BR /&gt; fkimg TYPE fkimg,&lt;BR /&gt; vrkme TYPE vrkme,&lt;BR /&gt; END OF ty_vbrp.&lt;BR /&gt; &lt;BR /&gt; TYPES: BEGIN OF ty_out,&lt;BR /&gt; vbeln TYPE vbeln_vf,&lt;BR /&gt; fkart TYPE fkart,&lt;BR /&gt; fktyp TYPE fktyp,&lt;BR /&gt; vbtyp TYPE vbtyp,&lt;BR /&gt; posnr TYPE posnr,&lt;BR /&gt; fkimg TYPE fkimg,&lt;BR /&gt; vrkme TYPE vrkme,&lt;BR /&gt; END OF ty_out.&lt;BR /&gt; &lt;BR /&gt; DATA: wa_out TYPE ty_out,&lt;BR /&gt; it_out TYPE TABLE OF ty_out,&lt;BR /&gt; &lt;BR /&gt; wa_fcat TYPE slis_fieldcat_alv,&lt;BR /&gt; it_fcat TYPE slis_t_fieldcat_alv WITH HEADER LINE.&lt;BR /&gt; &lt;BR /&gt; SELECT-OPTIONS: s_vbeln FOR vbrk-vbeln.&lt;BR /&gt; &lt;BR /&gt; START-OF-SELECTION.&lt;/P&gt;
  &lt;P&gt;&lt;BR /&gt; wa_fcat-col_pos = 1.&lt;BR /&gt; wa_fcat-fieldname = 'VBELN'.&lt;BR /&gt; wa_fcat-tabname = 'IT_OUT'.&lt;BR /&gt; wa_fcat-seltext_m = 'BILLING DOC NO'.&lt;BR /&gt; APPEND wa_fcat TO it_fcat.&lt;BR /&gt; CLEAR wa_fcat.&lt;BR /&gt; &lt;BR /&gt; wa_fcat-col_pos = 2.&lt;BR /&gt; wa_fcat-fieldname = 'FKART'.&lt;BR /&gt; wa_fcat-tabname = 'IT_OUT'.&lt;BR /&gt; wa_fcat-seltext_m = 'BILLING TYPE'.&lt;BR /&gt; APPEND wa_fcat TO it_fcat.&lt;BR /&gt; CLEAR wa_fcat.&lt;BR /&gt; &lt;BR /&gt; wa_fcat-col_pos = 3.&lt;BR /&gt; wa_fcat-fieldname = 'FKTYP'.&lt;BR /&gt; wa_fcat-tabname = 'IT_OUT'.&lt;BR /&gt; wa_fcat-seltext_m = 'BILLING CATAGERY'.&lt;BR /&gt; APPEND wa_fcat TO it_fcat.&lt;BR /&gt; CLEAR wa_fcat.&lt;BR /&gt; &lt;BR /&gt; wa_fcat-col_pos = 4.&lt;BR /&gt; wa_fcat-fieldname = 'VBTYP'.&lt;BR /&gt; wa_fcat-tabname = 'IT_OUT'.&lt;BR /&gt; wa_fcat-seltext_m = 'SD DOCUMENT CATAGERY'.&lt;BR /&gt; APPEND wa_fcat TO it_fcat.&lt;BR /&gt; CLEAR wa_fcat.&lt;BR /&gt; &lt;BR /&gt; wa_fcat-col_pos = 5.&lt;BR /&gt; wa_fcat-fieldname = 'VBTYP'.&lt;BR /&gt; wa_fcat-tabname = 'IT_OUT'.&lt;BR /&gt; wa_fcat-seltext_m = 'SD DOCUMENT CATAGERY'.&lt;BR /&gt; APPEND wa_fcat TO it_fcat.&lt;BR /&gt; CLEAR wa_fcat.&lt;BR /&gt; &lt;BR /&gt; wa_fcat-col_pos = 6.&lt;BR /&gt; wa_fcat-fieldname = 'POSNR'.&lt;BR /&gt; wa_fcat-tabname = 'IT_OUT'.&lt;BR /&gt; wa_fcat-seltext_m = 'BILLING ITEM'.&lt;BR /&gt; APPEND wa_fcat TO it_fcat.&lt;BR /&gt; CLEAR wa_fcat.&lt;BR /&gt; &lt;BR /&gt; wa_fcat-col_pos = 7.&lt;BR /&gt; wa_fcat-fieldname = 'FKIMG'.&lt;BR /&gt; wa_fcat-tabname = 'IT_OUT'.&lt;BR /&gt; wa_fcat-seltext_m = 'QUANTITY'.&lt;BR /&gt; APPEND wa_fcat TO it_fcat.&lt;BR /&gt; CLEAR wa_fcat.&lt;BR /&gt; &lt;BR /&gt; wa_fcat-col_pos = 8.&lt;BR /&gt; wa_fcat-fieldname = 'VRKME'.&lt;BR /&gt; wa_fcat-tabname = 'IT_OUT'.&lt;BR /&gt; wa_fcat-seltext_m = 'SALES UNIT'.&lt;BR /&gt; APPEND wa_fcat TO it_fcat.&lt;BR /&gt; CLEAR wa_fcat.&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt; SELECT a~vbeln&lt;BR /&gt; fkart&lt;BR /&gt; fktyp&lt;BR /&gt; vbtyp&lt;BR /&gt; posnr&lt;BR /&gt; fkimg&lt;BR /&gt; vrkme FROM vbrk AS a INNER JOIN vbrp AS b&lt;BR /&gt; ON a~vbeln = b~vbeln INTO TABLE it_out UP TO 30 ROWS&lt;BR /&gt; WHERE a~vbeln IN s_vbeln.&lt;BR /&gt; &lt;BR /&gt; *END-OF-SELECTION.&lt;BR /&gt; *DATA: tb_lines TYPE i.&lt;BR /&gt; *DESCRIBE TABLE it_out LINES tb_lines.&lt;BR /&gt; *WRITE: 'NO.OF RECORDS', tb_lines.&lt;BR /&gt; &lt;BR /&gt; CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'&lt;BR /&gt; EXPORTING&lt;BR /&gt; i_callback_program = sy-repid&lt;BR /&gt; it_fieldcat = it_fcat&lt;BR /&gt;&lt;BR /&gt; TABLES&lt;BR /&gt; t_outtab = it_out&lt;BR /&gt; EXCEPTIONS&lt;BR /&gt; PROGRAM_ERROR = 1&lt;BR /&gt; OTHERS = 2&lt;BR /&gt; .&lt;BR /&gt; IF sy-subrc &amp;lt;&amp;gt; 0.&lt;BR /&gt; * Implement suitable error handling here&lt;BR /&gt; ENDIF.&lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 04:52:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996382#M1967505</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2019-07-23T04:52:26Z</dc:date>
    </item>
    <item>
      <title>Re: type conflict when calling a function module</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996383#M1967506</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;when you have a type conflict, you have a dump. Inside the dump, you will have the description of the type conflic, the FM &amp;amp; the field. Start from here, read your dump (trans ST22)&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 05:31:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996383#M1967506</guid>
      <dc:creator>FredericGirod</dc:creator>
      <dc:date>2019-07-23T05:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: type conflict when calling a function module</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996384#M1967507</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;You are calling 'REUSE_ALV_GRID_DISPLAY' Function module with wrong input parameter. With header line is not necessary for your requirement.&lt;/P&gt;&lt;P&gt;Try removing with header line in the declaration for it_fcat.&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;Data: it_fcat TYPE slis_t_fieldcat_alv WITH HEADER LINE.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Try this &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;Data: it_fcat TYPE slis_t_fieldcat_alv.&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 23 Jul 2019 07:00:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996384#M1967507</guid>
      <dc:creator>bhanuprakash5</dc:creator>
      <dc:date>2019-07-23T07:00:19Z</dc:date>
    </item>
    <item>
      <title>Re: type conflict when calling a function module</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996385#M1967508</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;1.Remove with header line.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it_fcat TYPE slis_t_fieldcat_alv." WITH HEADER LINE.&lt;/P&gt;&lt;P&gt;2.and also remove duplicate field catalog&lt;/P&gt;&lt;P&gt;wa_fcat-col_pos = 4.&lt;BR /&gt; wa_fcat-fieldname = 'VBTYP'.&lt;BR /&gt; wa_fcat-tabname = 'IT_OUT'.&lt;BR /&gt; wa_fcat-seltext_m = 'SD DOCUMENT CATAGERY'.&lt;BR /&gt; APPEND wa_fcat TO it_fcat.&lt;BR /&gt; CLEAR wa_fcat.&lt;BR /&gt;&lt;BR /&gt; wa_fcat-col_pos = 5.&lt;BR /&gt; wa_fcat-fieldname = 'VBTYP'.&lt;BR /&gt; wa_fcat-tabname = 'IT_OUT'.&lt;BR /&gt; wa_fcat-seltext_m = 'SD DOCUMENT CATAGERY'.&lt;BR /&gt; APPEND wa_fcat TO it_fcat.&lt;BR /&gt; CLEAR wa_fcat.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 07:08:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996385#M1967508</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2019-07-23T07:08:36Z</dc:date>
    </item>
    <item>
      <title>Re: type conflict when calling a function module</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996386#M1967509</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;data g_vblen type vbrk-vbeln.

select-options: s_vbeln for g_vblen .

select vbrk~vbeln, fkart, fktyp, vbtyp, posnr, fkimg, vrkme
       from vbrk inner join vbrp
       on vbrk~vbeln = vbrp~vbeln
       where vbrk~vbeln in @s_vbeln
       into table @data(db_values) up to 30 rows.


try.
    cl_salv_table=&amp;gt;factory( exporting list_display   = if_salv_c_bool_sap=&amp;gt;false
                            importing r_salv_table   = data(salv)
                            changing t_table        =  db_values ).


    salv-&amp;gt;get_functions( )-&amp;gt;set_all( ).
    salv-&amp;gt;display( ).
  catch cx_salv_msg cx_salv_not_found.
endtry.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;1. The TYPE-POOLS-Statement isn't needed. The system includes all Type-Pools!&lt;/P&gt;&lt;P&gt;2. Forget the Tabels-Statement&lt;/P&gt;&lt;P&gt;3. Why not using the SALV-Framework for output?&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 07:26:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996386#M1967509</guid>
      <dc:creator>ascm</dc:creator>
      <dc:date>2019-07-23T07:26:35Z</dc:date>
    </item>
    <item>
      <title>Re: type conflict when calling a function module</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996387#M1967510</link>
      <description>&lt;P&gt;You are nice to say "With header line is not necessary for your requirement", because it's just completely obsolete since 7.0 (2005), essentially because it's &lt;STRONG&gt;error prone &lt;/STRONG&gt;(good experience for the OP, I hope he will never do it again :-D).&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jul 2019 07:33:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/type-conflict-when-calling-a-function-module/m-p/11996387#M1967510</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2019-07-23T07:33:37Z</dc:date>
    </item>
  </channel>
</rss>

