<?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: Hanatize Ranges in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335186#M1991805</link>
    <description>&lt;P&gt;There are answers below already for how to do what you ask. But what will you be using your gt_ebeln for?&lt;/P&gt;&lt;P&gt;Both with and without HANA there is also the possibility to join tables in one select instead of making two (ore more) selects where the first one is only used to get the keys for the WHERE clause of the second one...&lt;/P&gt;</description>
    <pubDate>Tue, 23 Mar 2021 07:50:38 GMT</pubDate>
    <dc:creator>joltdx</dc:creator>
    <dc:date>2021-03-23T07:50:38Z</dc:date>
    <item>
      <title>Hanatize Ranges</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335183#M1991802</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;
  &lt;P&gt;&lt;BR /&gt;Is it possible to get the result in select statement without using the loop. As hana db is more powerful now, wondering if these kind of statements can be achieved at DB level rather than application server.&lt;/P&gt; 
  &lt;PRE&gt;&lt;CODE&gt;  SELECT ebeln
     FROM ekko
     INTO TABLE @lt_ebeln
     WHERE ebeln = '&amp;lt;demo_value&amp;gt;'.

  LOOP AT lt_ebeln INTO ls_ebeln.
    CLEAR ls_range.
    ls_range-sign   = 'I'.
    ls_range-option = 'EQ'.
    ls_range-low    = ls_ebeln-ebeln.
    APPEND ls_range TO gt_ebeln.
    CLEAR ls_ebeln.
  ENDLOOP.
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 23 Mar 2021 07:15:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335183#M1991802</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2021-03-23T07:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: Hanatize Ranges</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335184#M1991803</link>
      <description>&lt;P&gt;Hi  &lt;SPAN class="mention-scrubbed"&gt;april.&lt;/SPAN&gt; &lt;BR /&gt;Based on your example it might look like the following:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;DATA lr_ebeln TYPE RANGE OF ekko-ebeln.

SELECT 'I', 'EQ', ebeln
  FROM ekko
  INTO TABLE @lr_ebeln[].&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Regards,&lt;BR /&gt;Bartosz&lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2021 07:24:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335184#M1991803</guid>
      <dc:creator>ziolkowskib</dc:creator>
      <dc:date>2021-03-23T07:24:43Z</dc:date>
    </item>
    <item>
      <title>Re: Hanatize Ranges</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335185#M1991804</link>
      <description>&lt;P&gt;No need for the []. There's no ambiguity. Ranges do not have a header line.&lt;/P&gt;&lt;P&gt;You could also use:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;SELECT 'I' AS sign, 'EQ' AS option, vbeln AS low, @space AS high
  FROM vbak
  INTO TABLE @DATA(range_of_document_numbers).&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 23 Mar 2021 07:38:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335185#M1991804</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2021-03-23T07:38:58Z</dc:date>
    </item>
    <item>
      <title>Re: Hanatize Ranges</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335186#M1991805</link>
      <description>&lt;P&gt;There are answers below already for how to do what you ask. But what will you be using your gt_ebeln for?&lt;/P&gt;&lt;P&gt;Both with and without HANA there is also the possibility to join tables in one select instead of making two (ore more) selects where the first one is only used to get the keys for the WHERE clause of the second one...&lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2021 07:50:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335186#M1991805</guid>
      <dc:creator>joltdx</dc:creator>
      <dc:date>2021-03-23T07:50:38Z</dc:date>
    </item>
    <item>
      <title>Re: Hanatize Ranges</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335187#M1991806</link>
      <description>&lt;P&gt;Thanks Bartosz and Matthew for the inputs. It is very helpful.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2021 08:12:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335187#M1991806</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2021-03-23T08:12:42Z</dc:date>
    </item>
    <item>
      <title>Re: Hanatize Ranges</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335188#M1991807</link>
      <description>&lt;P&gt;Also possible in non-HANA system. It just needs a high enough ABAP stack. &lt;/P&gt;</description>
      <pubDate>Tue, 23 Mar 2021 10:24:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hanatize-ranges/m-p/12335188#M1991807</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2021-03-23T10:24:46Z</dc:date>
    </item>
  </channel>
</rss>

