<?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: Invalid column Index error - While consuming Calculation view via Native SQL in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/invalid-column-index-error-while-consuming-calculation-view-via-native-sql/m-p/10280805#M1831968</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Suma,&lt;BR /&gt;in addition to Fernando's proposal, can you please check, where exactly the issue occurs? I guess the call of "next_package" fails, right? &lt;BR /&gt;In case yes, the question is if the usage of SEPMAPPS_CLSDINV as type definition for the output parameter is correct respectively should be avoided.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SEPMAPPS_CLSDINV is an external dictionary view for another HANA view, which might lead to issues when using "SELECT *". You can't be sure about the ordering of columns in your calc view output parameter and the external view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a test, you could try to define a type yourself (let's say only containing one field), an internal table of this structured type and perform a "SELECT &amp;lt;field&amp;gt;" into the internal table.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Cheers,&lt;/P&gt;&lt;P&gt;&amp;nbsp; Jasmin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 08 Apr 2014 11:11:59 GMT</pubDate>
    <dc:creator>jasmin_gruschke</dc:creator>
    <dc:date>2014-04-08T11:11:59Z</dc:date>
    <item>
      <title>Invalid column Index error - While consuming Calculation view via Native SQL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/invalid-column-index-error-while-consuming-calculation-view-via-native-sql/m-p/10280803#M1831966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to consume a Calculation view (sql script one) , which has input parameters, via Native SQL in a ABAP program .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Code snippet for the same would be as follows , Upon execution, it throws an error "Invalid Column Index (8) error " . Can anyone help what could be the issue here ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in Advance,&lt;/P&gt;&lt;P&gt;Suma &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT ZTEST_HANA2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*Report to consume Calculation view (script based) from ABAP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PARAMETERS: ip_docnr type BELNR_D,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ip_gjahr type GJAHR,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ip_bukrs type BUKRS,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ip_blgr type FAGL_RLDNR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; DATA: LO_SQL_STMT TYPE REF TO CL_SQL_STATEMENT,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LO_CONN&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TYPE REF TO CL_SQL_CONNECTION,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LO_RESULT&amp;nbsp;&amp;nbsp; TYPE REF TO CL_SQL_RESULT_SET,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LV_SQL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TYPE STRING,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LR_DATA&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TYPE REF TO DATA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; DATA: LX_SQL_EXC&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TYPE REF TO CX_SQL_EXCEPTION,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LT_SEPMAPPS_CLSDINV&amp;nbsp; TYPE TABLE OF SEPMAPPS_CLSDINV,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LV_TEXT&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TYPE STRING.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; TRY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;lv_sql = |SELECT * FROM "_SYS_BIC"."DEMO-ABAP/CA_GET_FI_DATA" | &amp;amp;&amp;amp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |WITH PARAMETERS ('placeholder'= ('$$p_DOCNR$$','{ ip_docnr }'),| &amp;amp;&amp;amp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |'placeholder'=('$$p_GJAHR$$','{ ip_gjahr }')| &amp;amp;&amp;amp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |,'placeholder'= ('$$S_BUKRS$$','{ ip_bukrs }')| &amp;amp;&amp;amp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; |,'placeholder'= ('$$p_base_ledger$$','{ ip_blgr }') )| .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LO_CONN = CL_SQL_CONNECTION=&amp;gt;GET_CONNECTION( ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "Create an SQL statement to be executed via the connection&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LO_SQL_STMT = LO_CONN-&amp;gt;CREATE_STATEMENT( ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "Execute the native SQL query&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LO_RESULT = LO_SQL_STMT-&amp;gt;EXECUTE_QUERY( LV_SQL ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; "Read the result into the internal table lt_sepmapps_clsdinv&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; GET REFERENCE OF LT_SEPMAPPS_CLSDINV INTO LR_DATA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LO_RESULT-&amp;gt;SET_PARAM_TABLE( LR_DATA ).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LO_RESULT-&amp;gt;NEXT_PACKAGE( ).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LO_RESULT-&amp;gt;CLOSE( ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LO_CONN-&amp;gt;CLOSE( ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; CATCH CX_SQL_EXCEPTION INTO LX_SQL_EXC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; LV_TEXT = LX_SQL_EXC-&amp;gt;GET_TEXT( ).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MESSAGE LV_TEXT TYPE 'E'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; ENDTRY.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Apr 2014 10:19:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/invalid-column-index-error-while-consuming-calculation-view-via-native-sql/m-p/10280803#M1831966</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-04-08T10:19:53Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid column Index error - While consuming Calculation view via Native SQL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/invalid-column-index-error-while-consuming-calculation-view-via-native-sql/m-p/10280804#M1831967</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Suma,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Post the SQL you success run directly on Studio together with error message (even if is the Invalid column index error).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check there if the parameters case is working properly... Is it really this confusing options:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8f8f8; color: #333333; font-size: 11.818181991577148px;"&gt;p_GJAHR&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8f8f8; color: #333333; font-size: 11.818181991577148px;"&gt;S_BUKRS&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 11.818181991577148px; background-color: #f8f8f8; color: #333333;"&gt;p_base_ledger&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why not all lower or all upper? Anyhow you must test and find which option works according your modeling&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, Fernando Da Rós&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Apr 2014 10:50:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/invalid-column-index-error-while-consuming-calculation-view-via-native-sql/m-p/10280804#M1831967</guid>
      <dc:creator>former_member182114</dc:creator>
      <dc:date>2014-04-08T10:50:28Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid column Index error - While consuming Calculation view via Native SQL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/invalid-column-index-error-while-consuming-calculation-view-via-native-sql/m-p/10280805#M1831968</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Suma,&lt;BR /&gt;in addition to Fernando's proposal, can you please check, where exactly the issue occurs? I guess the call of "next_package" fails, right? &lt;BR /&gt;In case yes, the question is if the usage of SEPMAPPS_CLSDINV as type definition for the output parameter is correct respectively should be avoided.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SEPMAPPS_CLSDINV is an external dictionary view for another HANA view, which might lead to issues when using "SELECT *". You can't be sure about the ordering of columns in your calc view output parameter and the external view.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a test, you could try to define a type yourself (let's say only containing one field), an internal table of this structured type and perform a "SELECT &amp;lt;field&amp;gt;" into the internal table.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Cheers,&lt;/P&gt;&lt;P&gt;&amp;nbsp; Jasmin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Apr 2014 11:11:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/invalid-column-index-error-while-consuming-calculation-view-via-native-sql/m-p/10280805#M1831968</guid>
      <dc:creator>jasmin_gruschke</dc:creator>
      <dc:date>2014-04-08T11:11:59Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid column Index error - While consuming Calculation view via Native SQL</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/invalid-column-index-error-while-consuming-calculation-view-via-native-sql/m-p/10280806#M1831969</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jasmin,&lt;/P&gt;&lt;P&gt;Use of SEPMAPPS_CLSDINV was the issue, have declared an internal table of type external view created for the calculation view that I created earlier, it worked now.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Suma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Apr 2014 10:18:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/invalid-column-index-error-while-consuming-calculation-view-via-native-sql/m-p/10280806#M1831969</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-04-09T10:18:11Z</dc:date>
    </item>
  </channel>
</rss>

