<?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 Program in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256317#M146263</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &amp;lt;b&amp;gt;Tina&amp;lt;/b&amp;gt;:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The &amp;lt;b&amp;gt;TYPE-POOL: SLIS&amp;lt;/b&amp;gt; contains all the logic information for the ALV (The ability to group fields, make sum and average calculations, give a zebra look, etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;PF-Status&amp;lt;/b&amp;gt; sets a custom Status Bar...We need to use it either in we want extra functionality (other than the standard status bar provide)...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Blag.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Mar 2006 16:53:50 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-03-09T16:53:50Z</dc:date>
    <item>
      <title>Alv Program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256315#M146261</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;            I wanted to know why do we use TYPE-POOL: SLIS in Alv programming, and also what is PF-Status, &amp;amp; why do we use it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help e to understand the basic concepts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Tina&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Mar 2006 16:49:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256315#M146261</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-09T16:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: Alv Program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256316#M146262</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tina,&lt;/P&gt;&lt;P&gt;  Type-pool: slis.&lt;/P&gt;&lt;P&gt; This is used to use the structures in that in the FM to get ALV output.&lt;/P&gt;&lt;P&gt;PF-Status is used to define any user defined buttons on the menu bar,if you dont define, ALV takes the standard.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Mar 2006 16:51:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256316#M146262</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-09T16:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: Alv Program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256317#M146263</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &amp;lt;b&amp;gt;Tina&amp;lt;/b&amp;gt;:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The &amp;lt;b&amp;gt;TYPE-POOL: SLIS&amp;lt;/b&amp;gt; contains all the logic information for the ALV (The ability to group fields, make sum and average calculations, give a zebra look, etc).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;PF-Status&amp;lt;/b&amp;gt; sets a custom Status Bar...We need to use it either in we want extra functionality (other than the standard status bar provide)...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Blag.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Mar 2006 16:53:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256317#M146263</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-09T16:53:50Z</dc:date>
    </item>
    <item>
      <title>Re: Alv Program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256318#M146264</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check the documentations of function REUSE_ALV_LIST_DISPLAY - it gives clear idea about all parameters. I am attaching a piece of documentation here. If you are not clear, resposne back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Set EXIT rountine to status                                                            &lt;/P&gt;&lt;P&gt;    Description                                                                         &lt;/P&gt;&lt;P&gt;    Passing an EXIT routine tells the ALV that the caller wants to set his             &lt;/P&gt;&lt;P&gt;    or her own user status.                                                                                &lt;/P&gt;&lt;P&gt;In this case, the default ALV status is not set.                                                                                &lt;/P&gt;&lt;P&gt;The form routine interface must be defined as follows:                                                                                &lt;/P&gt;&lt;P&gt;FORM set_pf_status USING rt_extab TYPE slis_t_extab                                                                                &lt;/P&gt;&lt;P&gt;The table RT_EXTAB contains those function codes that are hidden on the            &lt;/P&gt;&lt;P&gt;    standard interface.                                                                                &lt;/P&gt;&lt;P&gt;If the caller wants to use his or her own interface (to offer other                &lt;/P&gt;&lt;P&gt;    functions on the list or transfer existing functionality, for example),            &lt;/P&gt;&lt;P&gt;    it is recommended that he or she copy the standard status STANDARD from            &lt;/P&gt;&lt;P&gt;    function group SALV and make the appropriate changes. Standard ALV                 &lt;/P&gt;&lt;P&gt;    function codes always begin with '&amp;amp;'.                                                                                &lt;/P&gt;&lt;P&gt;Please consult the documentation on the  I_CALLBACK_USER_COMMAND                   &lt;/P&gt;&lt;P&gt;    parameter as well.                                                                                &lt;/P&gt;&lt;P&gt;If, however, the user chooses to use his or her own interface that                 &lt;/P&gt;&lt;P&gt;    contains the standard interface's function codes, the function codes               &lt;/P&gt;&lt;P&gt;    from the excluding table passed must also be taken into consideration.                                                                                &lt;/P&gt;&lt;P&gt;This means that the user status should always be set as follows:                   &lt;/P&gt;&lt;P&gt;        SET PF-STATUS usrstatus EXCLUDING rt_extab.                                                                                &lt;/P&gt;&lt;P&gt;Excluding table rt_extab can be appended to include those application        functions that are to be deactivated.                                                                                &lt;/P&gt;&lt;P&gt;The system calls this routine whenever the standard interface is set  &lt;/P&gt;&lt;P&gt;     using SET PF-STATUS.                                                                                &lt;/P&gt;&lt;P&gt;Default                                                                                &lt;/P&gt;&lt;P&gt;If no exit routine is entered, then the ALV sets a status that        &lt;/P&gt;&lt;P&gt;     corresponds to the STANDARD status of function group SALV.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Mar 2006 16:56:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256318#M146264</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-09T16:56:15Z</dc:date>
    </item>
    <item>
      <title>Re: Alv Program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256319#M146265</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tina,&lt;/P&gt;&lt;P&gt; 1.This statement allows you to use all the data types and constants defined in the type group after type-pools (here TYPE-POOLS : SLIS )in your program ..&lt;/P&gt;&lt;P&gt;this SLIS has all the predefined TYPES...&lt;/P&gt;&lt;P&gt;for eg like &amp;lt;b&amp;gt;slis_layout_alv&amp;lt;/b&amp;gt;...&lt;/P&gt;&lt;P&gt; it has all the functionalities associated with LAYOUT of ALV like zebra , detail_popup , ..&lt;/P&gt;&lt;P&gt; lot similar functionalities are already defined..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.SET PF-STATUS 'XYZ'.This statement defines the user interface for all subsequent screens of a screen sequence until&lt;/P&gt;&lt;P&gt;another is set using a new SET PF-STATUS statement..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The GUI status 'XYZ'  must be a&lt;/P&gt;&lt;P&gt;component of the current ABAP program,...&lt;/P&gt;&lt;P&gt; unless you use the OF PROGRAM addition in the SET&lt;/P&gt;&lt;P&gt;PF-STATUS statement to set a GUI status of another program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;satesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Mar 2006 16:56:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256319#M146265</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-03-09T16:56:37Z</dc:date>
    </item>
    <item>
      <title>Re: Alv Program</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256320#M146266</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Take the following example....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;

REPORT ZRICH_0003 . 

* Tables. 
TABLES: MARA. 

* Global ALV Data Declarations 
&amp;lt;b&amp;gt;TYPE-POOLS: SLIS.&amp;lt;/b&amp;gt; 

* Internal Tables 
DATA: BEGIN OF ITAB OCCURS 0, 
      MATNR TYPE MARA-MATNR, 
      MAKTX TYPE MAKT-MAKTX, 
      END OF ITAB. 

&amp;lt;b&amp;gt;DATA: FIELDCAT  TYPE SLIS_T_FIELDCAT_ALV.&amp;lt;/b&amp;gt;

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When we create the tables for the field catelog or the layout table, etc, we use the types like SLIS_T_FIELDCAT_ALV which are defined in the type group SLIS.  So in order for the program to recoginized the type that we are using, you must include the type group in your program.  We do this using the TYPE-POOLS statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PF-STATUS is used to trigger the current gui status. The gui-status is the deinition of the buttons/function codes that the user can use during that screen processing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Mar 2006 16:57:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-program/m-p/1256320#M146266</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2006-03-09T16:57:00Z</dc:date>
    </item>
  </channel>
</rss>

