<?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: ALV-basics in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561965#M857133</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;Wednesday, June 27, 2007&lt;/P&gt;&lt;P&gt;ALV Function Module &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(1) REUSE_ALV_LIST_DISPLAY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Display an ALV list as per parameters defined in the function call&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(2) REUSE_ALV_GRID_DISPLAY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Display an ALV grid as per parameters defined in the function call&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(3) REUSE_ALV_COMMENTARY_WRITE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;List header information is output according to its type. The output information is put in an internal table. Output attributes are assigned to each line via the TYP field.This module outputs formatted simple header information at TOP-OF-PAGE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(4) REUSE_ALV_HIERSEQ_LIST_DISPLAY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This module outputs two internal tables as a formated hierarchical-sequential list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(5) REUSE_ALV_VARIANT_F4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Display variant selection dialog box.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(6) REUSE_ALV_VARIANT_EXISTENCE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Checks whether a display variant exists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chk out this link too..&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/what-is-alv-programming.htm" target="test_blank"&gt;http://www.sap-img.com/abap/what-is-alv-programming.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps u,&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Arunsri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Apr 2008 04:38:29 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-04-01T04:38:29Z</dc:date>
    <item>
      <title>ALV-basics</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561964#M857132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the meaning of all these in ALV :means purpose of all these statements.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. REUSE_ALV_VARIANT_DEFAULT_GET&lt;/P&gt;&lt;P&gt;2. REUSE_ALV_VARIANT_F4&lt;/P&gt;&lt;P&gt;3. REUSE_ALV_VARIANT_EXISTENCE&lt;/P&gt;&lt;P&gt;4. REUSE_ALV_EVENTS_GET&lt;/P&gt;&lt;P&gt;5. REUSE_ALV_COMMENTARY_WRITE&lt;/P&gt;&lt;P&gt;6. REUSE_ALV_FIELDCATALOG_MERGE&lt;/P&gt;&lt;P&gt;7. REUSE_ALV_LIST_DISPLAY&lt;/P&gt;&lt;P&gt;8. REUSE_ALV_GRID_DISPLAY&lt;/P&gt;&lt;P&gt;9. REUSE_ALV_POPUP_TO_SELECT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Mar 2008 12:44:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561964#M857132</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-31T12:44:14Z</dc:date>
    </item>
    <item>
      <title>Re: ALV-basics</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561965#M857133</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;Wednesday, June 27, 2007&lt;/P&gt;&lt;P&gt;ALV Function Module &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(1) REUSE_ALV_LIST_DISPLAY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Display an ALV list as per parameters defined in the function call&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(2) REUSE_ALV_GRID_DISPLAY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Display an ALV grid as per parameters defined in the function call&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(3) REUSE_ALV_COMMENTARY_WRITE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;List header information is output according to its type. The output information is put in an internal table. Output attributes are assigned to each line via the TYP field.This module outputs formatted simple header information at TOP-OF-PAGE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(4) REUSE_ALV_HIERSEQ_LIST_DISPLAY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This module outputs two internal tables as a formated hierarchical-sequential list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(5) REUSE_ALV_VARIANT_F4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Display variant selection dialog box.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(6) REUSE_ALV_VARIANT_EXISTENCE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Checks whether a display variant exists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Chk out this link too..&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/what-is-alv-programming.htm" target="test_blank"&gt;http://www.sap-img.com/abap/what-is-alv-programming.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps u,&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Arunsri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Apr 2008 04:38:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561965#M857133</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-01T04:38:29Z</dc:date>
    </item>
    <item>
      <title>Re: ALV-basics</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561966#M857134</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;&lt;STRONG&gt;REUSE_ALV_VARIANT_DEFAULT_GET&lt;/STRONG&gt;Read default display variant (description only, w/o field catalog)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;Provides the default variant for the list specified in the structure parameter CS_VARIANT of a program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;REUSE_ALV_VARIANT_F4&lt;/STRONG&gt;Display variant selection dialog box&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;Possible entries help, if the variant is defined explicitly as an input field on a screen. The selection must be specified by at least partially filling the parameter structure IS_VARIANT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;REUSE_ALV_VARIANT_EXISTENCE&lt;/STRONG&gt;Checks whether a display variant exists&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;This function module checks the existence in the database of a display variant passed in the interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;REUSE_ALV_EVENTS_GET&lt;/STRONG&gt;Returns table of possible events for a list type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;This table can be passed to the ALV display module with the form name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;REUSE_ALV_COMMENTARY_WRITE&lt;/STRONG&gt;List body comment block output&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;List header information is output according to its type. The output information is put in an internal table. Output attributes are assigned to each line via the TYP field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This module outputs formatted simple header information at TOP-OF-PAGE.&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;                                         List       &amp;lt;-- Type 'H'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currency     DEM Controlling area currency       &amp;lt;-- Type 'S'&lt;/P&gt;&lt;P&gt;Material     FGS_TEST Test material              &amp;lt;-- Type 'S'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Action info                                       &amp;lt;-- Type 'A'&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="------------------" /&gt;&lt;P&gt; Column headers -&lt;/P&gt;&lt;HR originaltext="---------------------------------" /&gt;&lt;P&gt;-&lt;/P&gt;&lt;HR originaltext="------------------" /&gt;&lt;P&gt; List -&lt;/P&gt;&lt;HR originaltext="-------------------------------------------" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;REUSE_ALV_FIELDCATALOG_MERGE&lt;/STRONG&gt; Create field catalog from dictionary structure or internal table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;Supports the creation of the field catalog for the ALV function modules based either on a structure or table defined in the ABAP Data Dictionary, or a program-internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The program-internal table must either be in a TOP Include or its Include must be specified explicitly in the interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The variant based on a program-internal table should only be used for rapid prototyping since the following restrictions apply:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Performance is affected since the code of the table definition must always be read and interpreted at runtime.&lt;/P&gt;&lt;P&gt;Dictionary references are only considered if the keywords LIKE or INCLUDE STRUCTURE (not TYPE) are used.&lt;/P&gt;&lt;P&gt;If the field catalog contains more than 90 fields, the first 90 fields are output in the list by default whereas the remaining fields are only available in the field selection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the field catalog is passed with values, they are merged with the 'automatically' found information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;REUSE_ALV_LIST_DISPLAY&lt;/STRONG&gt;Output a simple list (single line or several lines)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;This module outputs an internal table with any structure as a formatted one-line or multiple-line list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Principle:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pass an internal table with the set of output information&lt;/P&gt;&lt;P&gt;Pass a structure with general list layout details&lt;/P&gt;&lt;P&gt;Pass a field catalog as an internal table&lt;/P&gt;&lt;P&gt;The field catalog describes the fields to be output in the list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notes&lt;/P&gt;&lt;P&gt;All actions on the list refer directly to the internal output table, e.g. sorting the list also sorts the passed internal output table (passed by reference).&lt;/P&gt;&lt;P&gt;An important consideration for the use of the tools and certain generic functions (totals, subtotals) is the expected amount of data to be displayed.&lt;/P&gt;&lt;P&gt;The application must take this consideration into account.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;REUSE_ALV_GRID_DISPLAY&lt;/STRONG&gt;Output of a simple list (single-line)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;The function module outputs an internal table with whatever structure in the form of a formatted single- oder multi-line list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Process:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Passing an internal table with the set of information to be output&lt;/P&gt;&lt;P&gt;Passing a structure with general layout specifications for list layout&lt;/P&gt;&lt;P&gt;Passing a field catalog in the form of an internal table&lt;/P&gt;&lt;P&gt;The field catalog describes the fields to be output in the list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Notes&lt;/P&gt;&lt;P&gt;All interactions performed on the list refer directly to the internal output table. Sorting the list, for example, also involves a resorting of the internal output table passed (since it was passed by reference).&lt;/P&gt;&lt;P&gt;An important factor determining the usability of the tool or of various generic functions (totals, subtotals) is the expected amount of data to be displayed.&lt;/P&gt;&lt;P&gt;The application is responsible for critically testing this aspect and consider it when it comes to decision-making.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;REUSE_ALV_POPUP_TO_SELECT&lt;/STRONG&gt;List in dialog box to choose one or more entries (or display only)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Functionality&lt;/P&gt;&lt;P&gt;Module for displaying or selecting table entries in internal tables in a popup (single or multiple selection is possible).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Principle:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pass an internal table with the superset of information to be output&lt;/P&gt;&lt;P&gt;pass list layout detail flags&lt;/P&gt;&lt;P&gt;pass a field catalog in the form of an internal table&lt;/P&gt;&lt;P&gt;The field catalog describes the fields to be output in the list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Further information&lt;/P&gt;&lt;P&gt;The module uses the function module 'REUSE_ALV_LIST_DISPLAY' internally. The documentation of this module contains further information about the field catalog.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Apr 2008 05:01:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561966#M857134</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-01T05:01:44Z</dc:date>
    </item>
    <item>
      <title>Re: ALV-basics</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561967#M857135</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;REUSE_ALV_LIST_DISPLAY: Output a simple list (single line or several lines).Both REUSE_ALV_LIST_DISPLAY and REUSE_ALV_GRID_DISPLAY have similar  parameters&lt;/P&gt;&lt;P&gt;  Both Display the contents of an internal table passed by the parameter T_OUTTAB. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REUSE_ALV_COMMENTARY_WRITE: List body comment block output.Using   &amp;#145;REUSE_ALV_COMMENTARY_WRITE&amp;#146;, the internal table containing the headings for top of page event can be passed to the list output. Also, any logo specific to the report can be passed to the function module.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REUSE_ALV_EVENTS_GET: Returns table of possible events for a list type.A list of possible events is populated into an event table (I_EVENTS) when this table is passed to the function module REUSE_ALV_EVENTS_GET. The return table from this function module contains all the possible events.&lt;/P&gt;&lt;P&gt;The function module contains following import and export parameters.&lt;/P&gt;&lt;P&gt;IMPORTING PARAMETERS: I_LIST_TYPE&lt;/P&gt;&lt;P&gt;This parameter has possible values from 0-4.&lt;/P&gt;&lt;P&gt;The parameter I_LIST_TYPE is of TYPE SLIS_LIST_TYPE and is DEFAULT 0 .&lt;/P&gt;&lt;P&gt; EXPORTING PARAMETERS:  ET_EVENTS table. &lt;/P&gt;&lt;P&gt;This table is of TYPE SLIS_T_EVENT and returns to the program the name of all the possible events. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REUSE_ALV_FIELDCATALOG_MERGE: Create field catalog from dictionary structure or internal table.A field catalog is required for every ALV list output to add desired functionality (i.e. Key, Hotspot, Specific headings, Justify, Col. position etc) to certain fields of the output. If not mentioned specifically, then the defaults are taken. The possible values and defaults are listed below.&lt;/P&gt;&lt;P&gt;The field catalog for the output table is built-up in the caller's coding. The build-up can be completely or partially automated by calling the REUSE_ALV_FIELDCATALOG_MERGE module.&lt;/P&gt;&lt;P&gt;The minimal field catalog is documented below. This can be done in a routine using a local variable. The user can use the other optional parameters to assign output attributes to different fields in the output, which differ from the default.&lt;/P&gt;&lt;P&gt;A field catalog need not be built-up and passed explicitly only under the following conditions:&lt;/P&gt;&lt;P&gt;The internal table to be output has the same structure as a Data Dictionary structure which is referred to in the internal table declaration using LIKE or INCLUDE STRUCTURE. In this case the attributes of the different fields is taken directly from the table and the attributes (key fields, length, texts etc) need to state explicitly.all fields in this structure are to be output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REUSE_ALV_POPUP_TO_SELECT: List in dialog box to choose one or more entries (or display only).&lt;/P&gt;&lt;P&gt;REUSE_ALV_VARIANT_DEFAULT_GET: The variants in the list display can be both user-specific and general. The user can programmatically set the initial (default) variant for list display. &lt;/P&gt;&lt;P&gt;Function Module REUSE_ALV_VARIANT_DEFAULT_GET is used to get the default variant.&lt;/P&gt;&lt;P&gt;Sample code:&lt;/P&gt;&lt;P&gt; CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'&lt;/P&gt;&lt;P&gt;       EXPORTING&lt;/P&gt;&lt;P&gt;            i_save     = variant save condition ( A=all, U = user-specific )&lt;/P&gt;&lt;P&gt;       CHANGING&lt;/P&gt;&lt;P&gt;            cs_variant = internal table containing the program name &lt;/P&gt;&lt;P&gt;       EXCEPTIONS&lt;/P&gt;&lt;P&gt;            not_found  = 2.&lt;/P&gt;&lt;P&gt;This Function Module is used during the INITIALIZATION event.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REUSE_ALV_VARIANT_EXISTENCE: Checks whether a display variant exists.This function module checks the user entered variant name in the selection screen. It checks whether a display variant exists. This function module checks the existence in the database of a display variant passed in the interface.This Function Module is used at the event: AT SELECTION SCREEN. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REUSE_ALV_VARIANT_F4: Display variant selection dialog box.This function module REUSE_ALV_VARIANT_F4 provides the list of possible variant entries when the user presses the F4 button. It displays variant selection dialog box and gives possible entries help, if the variant is defined explicitly as an input field on a screen. The selection must be specified by at least partially filling the parameter structure IS_VARIANT.&lt;/P&gt;&lt;P&gt;This Function Module is used at the event: AT SELECTION-SCREEN ON VALUE-REQUEST&lt;/P&gt;&lt;P&gt;REUSE_ALV_GRID_DISPLAY: Output of a simple list (single-line).                                   &lt;/P&gt;&lt;P&gt;REUSE_ALV_POPUP_TO_SELECT: List in dialog box to choose one or more entries (or display only).&lt;/P&gt;&lt;P&gt;REUSE_ALV_VARIANT_DEFAULT_GET: The variants in the list display can be both user-specific and general. The user can programmatically set the initial (default) variant for list display. &lt;/P&gt;&lt;P&gt;Function Module REUSE_ALV_VARIANT_DEFAULT_GET is used to get the default variant.&lt;/P&gt;&lt;P&gt;Sample code:&lt;/P&gt;&lt;P&gt; CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'&lt;/P&gt;&lt;P&gt;       EXPORTING&lt;/P&gt;&lt;P&gt;            i_save     = variant save condition ( A=all, U = user-specific )&lt;/P&gt;&lt;P&gt;       CHANGING&lt;/P&gt;&lt;P&gt;            cs_variant = internal table containing the program name &lt;/P&gt;&lt;P&gt;       EXCEPTIONS&lt;/P&gt;&lt;P&gt;            not_found  = 2.&lt;/P&gt;&lt;P&gt;This Function Module is used during the INITIALIZATION event.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REUSE_ALV_VARIANT_EXISTENCE: Checks whether a display variant exists.This function module checks the user entered variant name in the selection screen. It checks whether a display variant exists. This function module checks the existence in the database of a display variant passed in the interface.This Function Module is used at the event: AT SELECTION SCREEN. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REUSE_ALV_GRID_DISPLAY: Output of a simple list (single-line).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Rajyalakshmi Attili on Apr 2, 2008 2:43 PM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Rajyalakshmi Attili on Apr 2, 2008 2:46 PM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Rajyalakshmi Attili on Apr 2, 2008 2:47 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Apr 2008 09:09:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561967#M857135</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-02T09:09:00Z</dc:date>
    </item>
    <item>
      <title>Re: ALV-basics</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561968#M857136</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;send me ur personal mail_id. i have docus with examples with this, so that u can understand easly. fo rdetails pls view my business card.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Fareedas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Apr 2008 11:31:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-basics/m-p/3561968#M857136</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-08T11:31:18Z</dc:date>
    </item>
  </channel>
</rss>

