<?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: Difference between loop and provide in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-loop-and-provide/m-p/3964221#M946889</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The statements PROVIDE and ENDPROVIDE define a loop through a statement block. In this loop, any number of internal tables itab1 itab2 ... are processed together. A single table can appear several times. For every table itab you must specify a FIELDS clause. After FIELDS you must specify the character * for all components or a list comp1 comp2 ... for specific components of the relevant table. The names of the components comp1 comp2 ... can only be specified directly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To be able to process internal tables using PROVIDE, all tables itab1 itab2 ... must be fully typed index tables and contain two special columns that have the same data type (d, i, n, or t) for all relevant tables. For every table you must specify the names intliml1 intliml2 ... and intlimu1 intlimu2 ... of these columns using the addition BOUNDS. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The columns intliml1 intliml2 ... and intlimu1 intlimu2 ... in every row of the relevant internal tables must contain values that can be interpreted as limits of closed intervals. Within a table, the intervals specified in these columns must not overlap and must be sorted in ascending order. The intervals therefore make up a unique key for every row. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For every table you must specify a work area wa1 wa2 ... compatible with the row type and a variable flag1 flag2 ..., for which a character-type data type with length 1 is expected. In the PROVIDE loop, the components specified after FIELDS are filled with values in the relevant work areas wa1 wa2 ... for every specified internal table. The variables flag1 flag2 ... are also filled. A work area wa1 wa2 ... or a variable flag1 flag2 ... cannot be specified more than once. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the BETWEEN addition you must specify an interval extliml, extlimu. It must be possible to convert the data objects extliml and extlimu into the data types of the respective columns intliml1 intliml2 ... and intlimu1 intlimu2 ... of the individual tables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The interval limits intliml1 intliml2 ... and intlimu1 intlim2 for every row of all relevant internal tables itab1 itab2 ... that are within the closed interval made up by extliml and extlimu divide the latter into new intervals and every interval limit closes one interval in the original direction. If, within a relevant table, a lower interval limit follows an upper interval limit with no space or gap between them and the components of the corresponding rows specified after FIELDS have the same content, the two intervals are combined and the corresponding interval limits intliml1 intliml2 ... and intlimu1 intlimu2 ... are ignored for the new intervals. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For every interval that is created in such a way and overlaps with at least one of the intervals of a table involved, the PROVIDE loop is passed once. The components of every work area wa1 wa2 ... specified after FIELDS and the variables flag1 flag2 ... are filled with values as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The components intliml1 intliml2 ... and intlimu1 intlimu2 ... of every work area wa1 wa2 ... are filled with the interval limits of the current interval. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the current interval overlaps with one of the intervals of an involved table, the remaining components of the corresponding work area are assigned the contents of the relevant components of this table row and the variable flag1 flag2 ... is set to the value "X". Otherwise, the work area components and the variables flag1 flag2 ... are set to their Initial value. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Except for intliml1 intliml2 ... and intlimu1 intlimu2 ..., the components not specified after FIELDS are always set to their initial value. The components intliml1 intliml2 ... and intlimu1 intlimu2 ... are always assigned.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Jun 2008 06:43:48 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-06-10T06:43:48Z</dc:date>
    <item>
      <title>Difference between loop and provide</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-loop-and-provide/m-p/3964219#M946887</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the difference between loop and provide statement&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Title edited by: Alvaro Tejada Galindo on Jun 12, 2008 6:38 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jun 2008 06:36:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-loop-and-provide/m-p/3964219#M946887</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-10T06:36:03Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between loop and provide</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-loop-and-provide/m-p/3964220#M946888</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Function group can be defined it as collection of Function &lt;/P&gt;&lt;P&gt;modules. This Function groups are presents in the Packages &lt;/P&gt;&lt;P&gt;where we can create in the SE38. So,that all packages are &lt;/P&gt;&lt;P&gt;consists in the Function Groups.All function groups are &lt;/P&gt;&lt;P&gt;consists Function Modules.This function modules are created &lt;/P&gt;&lt;P&gt;at enhancements/Exists. These are 4 types i.e are&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Menu Exist&lt;/P&gt;&lt;P&gt;2.Screen Exist&lt;/P&gt;&lt;P&gt;3.Field Exist&lt;/P&gt;&lt;P&gt;4.Function Exist&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above are created at Customizing the screens with &lt;/P&gt;&lt;P&gt;menus,screens and fields.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the screen is having the customization or not? for that &lt;/P&gt;&lt;P&gt;we are using press F1 button and click on the Technical &lt;/P&gt;&lt;P&gt;Information button. So, that we can identify the &lt;/P&gt;&lt;P&gt;Customization field has "+PGE" code. If it is present we &lt;/P&gt;&lt;P&gt;can do the menu exist.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this case we can have "Function Exist" and "Menu Exist" &lt;/P&gt;&lt;P&gt;is done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some of them does't have Menu,Screen,Field.So, in this case &lt;/P&gt;&lt;P&gt;only one "Function Exist" done.(Means only we can write the &lt;/P&gt;&lt;P&gt;program).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;SPAN __default_attr="red" __jive_macro_name="color"&gt;&amp;lt;REMOVED BY MODERATOR&amp;gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Dhan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Alvaro Tejada Galindo on Jun 12, 2008 6:39 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jun 2008 06:37:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-loop-and-provide/m-p/3964220#M946888</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-10T06:37:34Z</dc:date>
    </item>
    <item>
      <title>Re: Difference between loop and provide</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-loop-and-provide/m-p/3964221#M946889</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The statements PROVIDE and ENDPROVIDE define a loop through a statement block. In this loop, any number of internal tables itab1 itab2 ... are processed together. A single table can appear several times. For every table itab you must specify a FIELDS clause. After FIELDS you must specify the character * for all components or a list comp1 comp2 ... for specific components of the relevant table. The names of the components comp1 comp2 ... can only be specified directly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To be able to process internal tables using PROVIDE, all tables itab1 itab2 ... must be fully typed index tables and contain two special columns that have the same data type (d, i, n, or t) for all relevant tables. For every table you must specify the names intliml1 intliml2 ... and intlimu1 intlimu2 ... of these columns using the addition BOUNDS. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The columns intliml1 intliml2 ... and intlimu1 intlimu2 ... in every row of the relevant internal tables must contain values that can be interpreted as limits of closed intervals. Within a table, the intervals specified in these columns must not overlap and must be sorted in ascending order. The intervals therefore make up a unique key for every row. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For every table you must specify a work area wa1 wa2 ... compatible with the row type and a variable flag1 flag2 ..., for which a character-type data type with length 1 is expected. In the PROVIDE loop, the components specified after FIELDS are filled with values in the relevant work areas wa1 wa2 ... for every specified internal table. The variables flag1 flag2 ... are also filled. A work area wa1 wa2 ... or a variable flag1 flag2 ... cannot be specified more than once. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With the BETWEEN addition you must specify an interval extliml, extlimu. It must be possible to convert the data objects extliml and extlimu into the data types of the respective columns intliml1 intliml2 ... and intlimu1 intlimu2 ... of the individual tables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The interval limits intliml1 intliml2 ... and intlimu1 intlim2 for every row of all relevant internal tables itab1 itab2 ... that are within the closed interval made up by extliml and extlimu divide the latter into new intervals and every interval limit closes one interval in the original direction. If, within a relevant table, a lower interval limit follows an upper interval limit with no space or gap between them and the components of the corresponding rows specified after FIELDS have the same content, the two intervals are combined and the corresponding interval limits intliml1 intliml2 ... and intlimu1 intlimu2 ... are ignored for the new intervals. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For every interval that is created in such a way and overlaps with at least one of the intervals of a table involved, the PROVIDE loop is passed once. The components of every work area wa1 wa2 ... specified after FIELDS and the variables flag1 flag2 ... are filled with values as follows: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The components intliml1 intliml2 ... and intlimu1 intlimu2 ... of every work area wa1 wa2 ... are filled with the interval limits of the current interval. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the current interval overlaps with one of the intervals of an involved table, the remaining components of the corresponding work area are assigned the contents of the relevant components of this table row and the variable flag1 flag2 ... is set to the value "X". Otherwise, the work area components and the variables flag1 flag2 ... are set to their Initial value. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Except for intliml1 intliml2 ... and intlimu1 intlimu2 ..., the components not specified after FIELDS are always set to their initial value. The components intliml1 intliml2 ... and intlimu1 intlimu2 ... are always assigned.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jun 2008 06:43:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference-between-loop-and-provide/m-p/3964221#M946889</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-10T06:43:48Z</dc:date>
    </item>
  </channel>
</rss>

