<?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: Ranges Vs Select-options in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774379#M908198</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Surendrenath,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here both SELECT-OPTIONS &amp;amp; RANGES works for the same purpose.  They both are used for the range selection from selection screen.  &lt;/P&gt;&lt;P&gt;The main diff. between them is, while we use &lt;STRONG&gt;SELECT-OPTIONS system implicitly creates the select options internal table&lt;/STRONG&gt; which contains the fields of SIGN,OPTION,LOW and HIGH.  &lt;/P&gt;&lt;P&gt;But in case of &lt;STRONG&gt;RANGES, this internal table should be defined explicitly.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Eg. to SELECT-OPTIONS :&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;REPORT YARSELECT. 
TABLES YTXLFA1. 
SELECT-OPTIONS : VENDOR FOR YTXLFA1-LIFNR. 
INITIALIZATION. 
VENDOR-LOW    =   1000.               " It specifies the range starting value. 
VENDOR-HIGH    =   2000.               " It specifies the range ending value. 
VENDOR-OPTION  =  'BT'.                " specifies ranges value is in between. 
VENDOR-SIGN      = 'I'.                     "specifies both inclussive. 

APPEND VENDOR. 

- - - - 
- - - - 
SELECT LIFNR LAND1 NAME1 FROM LFA1 INTO TABLE ITAB  
WHERE LIFNR IN VENDOR.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Eg. to RANGES:&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;REPORT YARRANGE. 
TABLES YTXLFA1. 
RANGES: VENDOR FOR YTXFLA1-LIFNR. 

- - - -  
- - - -- 
- - - -  

SELECT LIFNR LAND1 NAME1 FROM LFA1 INTO TABLE ITAB  
WHERE LIFNR IN VENDOR.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Here with RANGES  user has to design an internal table with fields -&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SIGN,OPTION,LOW and HIGH EXPLICITLY.&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;&lt;STRONG&gt;&amp;lt;REMOVED BY MODERATOR&amp;gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;raam&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alvaro Tejada Galindo on Apr 30, 2008 1:37 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Apr 2008 14:13:32 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-04-30T14:13:32Z</dc:date>
    <item>
      <title>Ranges Vs Select-options</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774375#M908194</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi friends&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the difference between Ranges and Select-options...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Suren&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Apr 2008 14:03:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774375#M908194</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-30T14:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: Ranges Vs Select-options</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774376#M908195</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Select-options are screen elements and Ranges is a data type that describe select-options.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Apr 2008 14:05:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774376#M908195</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-30T14:05:05Z</dc:date>
    </item>
    <item>
      <title>Re: Ranges Vs Select-options</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774377#M908196</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here both SELECT-OPTIONS &amp;amp; RANGES works for the same purpose.  They both are used for the range selection from selection screen.  The main diff. between them is, while we use SELECT-OPTIONS system implicitly creates the select options internal table which contains the fields of SIGN,OPTION,LOW &amp;amp; HIGH.  But in case of RANGES, this internal table should be defined explicitly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg. to SELECT-OPTIONS : &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="----------------------------------------" /&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT YARSELECT. &lt;/P&gt;&lt;P&gt;TABLES YTXLFA1. &lt;/P&gt;&lt;P&gt;SELECT-OPTIONS : VENDOR FOR YTXLFA1-LIFNR. &lt;/P&gt;&lt;P&gt;INITIALIZATION. &lt;/P&gt;&lt;P&gt;VENDOR-LOW    =   1000.               " It specifies the range starting value. &lt;/P&gt;&lt;P&gt;VENDOR-HIGH    =   2000.               " It specifies the range ending value. &lt;/P&gt;&lt;P&gt;VENDOR-OPTION  =  'BT'.                " specifies ranges value is in between. &lt;/P&gt;&lt;P&gt;VENDOR-SIGN      = 'I'.                     "specifies both inclussive. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;APPEND VENDOR. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- - - - &lt;/P&gt;&lt;P&gt;- - - - &lt;/P&gt;&lt;P&gt;SELECT LIFNR LAND1 NAME1 FROM LFA1 INTO TABLE ITAB  &lt;/P&gt;&lt;P&gt;WHERE LIFNR IN VENDOR. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg. to RANGES: &lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="------------------------" /&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT YARRANGE. &lt;/P&gt;&lt;P&gt;TABLES YTXLFA1. &lt;/P&gt;&lt;P&gt;RANGES: VENDOR FOR YTXFLA1-LIFNR. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- - - -  &lt;/P&gt;&lt;P&gt;- - - -- &lt;/P&gt;&lt;P&gt;- - - -  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT LIFNR LAND1 NAME1 FROM LFA1 INTO TABLE ITAB  &lt;/P&gt;&lt;P&gt;WHERE LIFNR IN VENDOR. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here with RANGES  user has to design an internal table with fields -  &lt;/P&gt;&lt;P&gt;SIGN,OPTION,LOW and HIGH EXPLICITLY. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="--------------------------------------------------------------------------------------------------------" /&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example: &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;select-options: bukrs for zstock-bukrs. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;Should the user fill in 'ABFI' in BUKRS on the selection screen, BUKRS will look like this: &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;IEQABFI &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;This is because BUKRS is set as a table as follows: &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;begin of bukrs occurs 0, &lt;/P&gt;&lt;P&gt;  SIGN(1)    type c, &lt;/P&gt;&lt;P&gt;  OPTION(2) type c, &lt;/P&gt;&lt;P&gt;  LOW         like bukrs, &lt;/P&gt;&lt;P&gt;  HIGH         like bukrs, &lt;/P&gt;&lt;P&gt;end of bukrs. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;Now, when you create the following range, it will have the exact same fields set inside its table: &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;Ranges: bukrs for zstock-bukrs. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;The difference is, because ranges doesn't show on the selection screen, you will have to fill it yourself, meaning you will have to fill bukrs-sign, bukrs-option, bukrs-low &amp;amp; bukrs-high all manually. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;Some tips: &lt;/P&gt;&lt;P&gt;Sign is always I (for Include) or E (for Exclude) &lt;/P&gt;&lt;P&gt;Option can be a whole range, which includes: &lt;/P&gt;&lt;P&gt;EQ        (Equal)  &lt;/P&gt;&lt;P&gt;BT        (Between))  &lt;/P&gt;&lt;P&gt;CP        (Contain Pattern) &lt;/P&gt;&lt;P&gt;So let's say you want to have the range check for all company codes not starting with AB, you will set your code as follow: &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;ranges: bukrs for zstock-bukrs. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;bukrs-sign = 'E'.             "Exclude &lt;/P&gt;&lt;P&gt;bukrs-option = 'CP'.        "Pattern &lt;/P&gt;&lt;P&gt;bukrs-low = 'AB*'.            "Low Value &lt;/P&gt;&lt;P&gt;bukrs-high = ''.                "High Value &lt;/P&gt;&lt;P&gt;append bukrs. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;Always remember to APPEND your range when you fill it, as the WHERE clause checks against the lines of the range table, not against the header line. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;Hope this explains it well enough. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="--------------------------------------------------------------------------------------------------------" /&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What does SIGN "I" &amp;amp; "E" mean? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The "I" stands for Include, and the "E" for Exclude. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;The easiest way to learn how the range selections work is, create the following dummy program: &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;report dummy. &lt;/P&gt;&lt;P&gt;tables: mara. &lt;/P&gt;&lt;P&gt;select-options: matnr for mara-matnr. &lt;/P&gt;&lt;P&gt;start-of-selection. &lt;/P&gt;&lt;P&gt;loop at matnr. &lt;/P&gt;&lt;P&gt;write: / matnr-sign, &lt;/P&gt;&lt;P&gt;           matnr-option, &lt;/P&gt;&lt;P&gt;           matnr-low, &lt;/P&gt;&lt;P&gt;           matnr-high. &lt;/P&gt;&lt;P&gt;endloop. &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;Run this program, and fill in a lot of junk into MATNR. Fill in some includes, some excludes, some ranges, etc., and you will soon realise how the system builds ranges (select-options). Once you know that, you can fill your own ranges quickly and efficiently. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ramalakshmi&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;&lt;STRONG&gt;&amp;lt;REMOVED BY MODERATOR&amp;gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alvaro Tejada Galindo on Apr 30, 2008 1:36 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Apr 2008 14:11:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774377#M908196</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-30T14:11:12Z</dc:date>
    </item>
    <item>
      <title>Re: Ranges Vs Select-options</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774378#M908197</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Select-oprions are used in selecton screens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Both have the same structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sign&lt;/P&gt;&lt;P&gt;options&lt;/P&gt;&lt;P&gt;low&lt;/P&gt;&lt;P&gt;high&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;Fernando&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Apr 2008 14:11:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774378#M908197</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-30T14:11:58Z</dc:date>
    </item>
    <item>
      <title>Re: Ranges Vs Select-options</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774379#M908198</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Surendrenath,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here both SELECT-OPTIONS &amp;amp; RANGES works for the same purpose.  They both are used for the range selection from selection screen.  &lt;/P&gt;&lt;P&gt;The main diff. between them is, while we use &lt;STRONG&gt;SELECT-OPTIONS system implicitly creates the select options internal table&lt;/STRONG&gt; which contains the fields of SIGN,OPTION,LOW and HIGH.  &lt;/P&gt;&lt;P&gt;But in case of &lt;STRONG&gt;RANGES, this internal table should be defined explicitly.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Eg. to SELECT-OPTIONS :&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;REPORT YARSELECT. 
TABLES YTXLFA1. 
SELECT-OPTIONS : VENDOR FOR YTXLFA1-LIFNR. 
INITIALIZATION. 
VENDOR-LOW    =   1000.               " It specifies the range starting value. 
VENDOR-HIGH    =   2000.               " It specifies the range ending value. 
VENDOR-OPTION  =  'BT'.                " specifies ranges value is in between. 
VENDOR-SIGN      = 'I'.                     "specifies both inclussive. 

APPEND VENDOR. 

- - - - 
- - - - 
SELECT LIFNR LAND1 NAME1 FROM LFA1 INTO TABLE ITAB  
WHERE LIFNR IN VENDOR.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;U&gt;Eg. to RANGES:&lt;/U&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;REPORT YARRANGE. 
TABLES YTXLFA1. 
RANGES: VENDOR FOR YTXFLA1-LIFNR. 

- - - -  
- - - -- 
- - - -  

SELECT LIFNR LAND1 NAME1 FROM LFA1 INTO TABLE ITAB  
WHERE LIFNR IN VENDOR.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Here with RANGES  user has to design an internal table with fields -&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;SIGN,OPTION,LOW and HIGH EXPLICITLY.&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;&lt;STRONG&gt;&amp;lt;REMOVED BY MODERATOR&amp;gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;raam&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alvaro Tejada Galindo on Apr 30, 2008 1:37 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Apr 2008 14:13:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774379#M908198</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-30T14:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: Ranges Vs Select-options</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774380#M908199</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;u should have known the diff from the previous posts...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but given a chance use select - options compared to ranges...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ranges will reduce the performance... ranges is like a table again, inherited into the select statement...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Apr 2008 17:41:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774380#M908199</guid>
      <dc:creator>former_member156446</dc:creator>
      <dc:date>2008-04-30T17:41:02Z</dc:date>
    </item>
    <item>
      <title>Re: Ranges Vs Select-options</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774381#M908200</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;check this thread.&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="748979"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Apr 2008 17:47:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774381#M908200</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-30T17:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: Ranges Vs Select-options</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774382#M908201</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi!&lt;/P&gt;&lt;P&gt;A ranges table type is a special case of a table type. A ranges table type describes the structure of an internal table for administering complex areas, i.e. the type of an internal ranges table in the ABAP program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ranges tables can be used for example in logical conditions (IN operators) in the SELECT, IF, WHILE and CHECK statements or to pass data to selection tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The row type of a ranges table type has a fixed structure. The row type consists of the 4 components SIGN (sign), OPTION (comparison operator), LOW (lower limit) and HIGH (upper limit) in this order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The type of components LOW and HIGH is defined by an elementary associated type. It can be defined by specifying a data element or by directly defining the data type, number of places and if necessary the number of decimal places.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A ranges table type always has Standard table access mode and a standard key that is non-unique.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; The main diff. between them is, while we use SELECT-OPTIONS system implicitly creates the select options internal table which contains the fields of SIGN,OPTION,LOW &amp;amp; HIGH.  But in case of RANGES, this internal table should be defined explicitly&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;&lt;STRONG&gt;&amp;lt;REMOVED BY MODERATOR&amp;gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alvaro Tejada Galindo on Apr 30, 2008 4:03 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Apr 2008 18:33:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/ranges-vs-select-options/m-p/3774382#M908201</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-30T18:33:58Z</dc:date>
    </item>
  </channel>
</rss>

