<?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: set_table_for_first_display in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781856#M1585519</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The local table must be active in memory in same scope that the ALV is active. This seems obvious to me - for example, if you change the contents of a field in an editable ALV, the ALV must be able to refer to the internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 08 Apr 2011 06:45:28 GMT</pubDate>
    <dc:creator>matt</dc:creator>
    <dc:date>2011-04-08T06:45:28Z</dc:date>
    <item>
      <title>set_table_for_first_display</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781852#M1585515</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;                    When i am trying to pass an internal table which is defined locally to the method  set_table_for_first_display to the parameter it_outtab i am getting an error at the runtime displaying a pop-up message  'program errors: ALV internal table shoule be referred globally but not locally'. When i did declare the internal table globally the ALV is working good. Please explain  the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks  lot in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Ravi.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2011 05:18:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781852#M1585515</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-04-08T05:18:21Z</dc:date>
    </item>
    <item>
      <title>Re: set_table_for_first_display</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781853#M1585516</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Ravi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you post the code which was giving the error? I am aware local internal tables give this error when passed to 'REUSE_ALV_GRID_DISPLAY'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Suhas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2011 05:37:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781853#M1585516</guid>
      <dc:creator>SuhaSaha</dc:creator>
      <dc:date>2011-04-08T05:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: set_table_for_first_display</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781854#M1585517</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ravi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;have you defined the internal table locally within a form routine?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This internal table is only available while form routine is processed. ALV needs globally defined tables which are known after the generation of the report for creation of the field catalog. Locally defined tables are unknown!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2011 05:51:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781854#M1585517</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-04-08T05:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: set_table_for_first_display</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781855#M1585518</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; This internal table is only available while form routine is processed. ALV needs globally defined tables which are known after the generation of the report for creation of the field catalog. Locally defined tables are unknown!&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hello Klaus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But we pass the fieldcatalog while calling the method SET_TABLE_FOR_FIRST_DISPLAY. I don't think displaying the ALV will pose any error if we pass a local internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As a matter-of-fact i created a small test program &amp;amp; checked it out!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your thoughts on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Suhas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2011 06:09:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781855#M1585518</guid>
      <dc:creator>SuhaSaha</dc:creator>
      <dc:date>2011-04-08T06:09:44Z</dc:date>
    </item>
    <item>
      <title>Re: set_table_for_first_display</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781856#M1585519</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The local table must be active in memory in same scope that the ALV is active. This seems obvious to me - for example, if you change the contents of a field in an editable ALV, the ALV must be able to refer to the internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2011 06:45:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781856#M1585519</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2011-04-08T06:45:28Z</dc:date>
    </item>
    <item>
      <title>Re: set_table_for_first_display</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781857#M1585520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; The local table must be active in memory in same scope that the ALV is active.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, i too agree with you Matt. More so given the fact that the param IT_OUTTAB is a CHANGING param which is "passed by reference".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;This seems obvious to me - for example, if you change the contents of a field in an editable ALV, the ALV must be able to refer to the internal table&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think even for sort &amp;amp; filter operations the ALV must be able to refer back to the internal table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2011 08:12:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781857#M1585520</guid>
      <dc:creator>SuhaSaha</dc:creator>
      <dc:date>2011-04-08T08:12:18Z</dc:date>
    </item>
    <item>
      <title>Re: set_table_for_first_display</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781858#M1585521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Experts for your valuable inputs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Apr 2011 06:51:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781858#M1585521</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-04-11T06:51:57Z</dc:date>
    </item>
    <item>
      <title>Re: set_table_for_first_display</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781859#M1585522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe that set_table_for_first_display only retains the reference to the table it is passed, and not the table itself. As a result, if the table is declared locally in a subroutine, when that subroutine ends, that memory will be deallocated and the reference is no longer valid. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another thing to note is that if you pass a field-symbol to set_table_for_first_display, and later reassign that field symbol to a different table (global or otherwise), the newly assigned table will NOT be displayed in the ALV, because the reference used is to the table assigned when set_table_for_first_display is called.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Apr 2011 21:53:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/set-table-for-first-display/m-p/7781859#M1585522</guid>
      <dc:creator>alex_campbell</dc:creator>
      <dc:date>2011-04-13T21:53:19Z</dc:date>
    </item>
  </channel>
</rss>

