<?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: extra pushbutton in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951727#M944672</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Go to the Documenation for REUSE_ALV_GRID_DISPLAY&lt;/P&gt;&lt;P&gt;and review the requirments for the parm I_CALLBACK_PF_STATUS_SET&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You'll find this&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
Set EXIT rountine to status
Description
Passing an EXIT routine indicates to the ALV that the caller wants to set a self-defined user status.

As a result, the default status of the ALV is not set.

The interface of the form routine specified must be defined as follows:

FORM set_pf_status USING rt_extab TYPE slis_t_extab

Table RT_EXTAB contains the function codes that would be hidden on the standard user interface.

If the caller wants to use a self-defined user interface (for example, in order to provide additional list 
functions or use existing functions), we recommend that you copy standard status STANDARD 
from function group SALV and modify it accordingly. ALV standard function codes always start with '&amp;amp;'.

See also the documentation on parameter I_CALLBACK_USER_COMMAND.

If a self-defined user interface is used that includes function codes of the standard user interface, 
the function codes of the excluding table passed should be taken into account.

This means that the user status should generally be set as follows:

SET PF-STATUS user status EXCLUDING rt_extab.
Application functions can be added to excluding table rt_extab if they are to be disabled.

The routine is called whenever the standard user interface would be set with SET PF-STATUS.

Default
If no EXIT routine is specified, the ALV sets a status that corresponds to status STANDARD of 
function group SALV.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is code that sets it up for use&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
FORM list_view.
*
  g_repid = sy-repid.
  CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            i_callback_program       = g_repid
            i_callback_pf_status_set = 'STAT_0100'
            is_layout                = g_layout
            it_sort                  = g_sort[]
            it_events                = g_events[]
            it_fieldcat              = g_fieldcat[]
            i_save                   = g_save
            it_excluding             = g_exclude
       TABLES
            t_outtab                 = it_out
       EXCEPTIONS
            program_error            = 1
            OTHERS                   = 2.

  IF sy-subrc &amp;lt;&amp;gt; 0.
    MESSAGE e208(00) WITH 'Error: ALV Grid'.
  ENDIF.
*
ENDFORM.                    " layout_build


*====&amp;gt; End of Actual Display Routine
*====&amp;gt; This establishes the custom PF Status


FORM stat_0100 USING my_exclude.
*
  SET PF-STATUS 'STAT_0100' EXCLUDING my_exclude.
*
ENDFORM.                "end custom PF Status
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And the FORM that list all the common icons and what to use to exclude the ones you do not want.&lt;/P&gt;&lt;P&gt;Simply uncomment the ones you don't want to see.&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
*--------------------------------------------------------------*
*      Form  exclude_icons
*--------------------------------------------------------------*
FORM exclude_icons.
*  APPEND '&amp;amp;ETA' TO g_exclude.     "Details
**  APPEND '&amp;amp;OUP' TO g_exclude.     "Sort Up
**  APPEND '&amp;amp;ODN' TO g_exclude.     "Sort Down
*  APPEND '&amp;amp;ILT' TO g_exclude.     "Set Filter
*  APPEND '&amp;amp;UMC' TO g_exclude.     "Sum
**  APPEND '&amp;amp;RNT_PREV' TO g_exclude.     "Print preview
**  APPEND '&amp;amp;VEXCEL' TO g_exclude.     "Excel
**  APPEND '&amp;amp;RNT_PREV' TO g_exclude.     "Word processing
**  APPEND '%PC' TO g_exclude.     "Local File
**  APPEND '%SL' TO g_exclude.     "Mail recepient
*  APPEND '&amp;amp;ABC' TO g_exclude.     "ABC Analysis
*  APPEND '&amp;amp;GRAPH' TO g_exclude.     "Graphic
**  APPEND '&amp;amp;OL0' TO g_exclude.     "Change layout
**  APPEND '&amp;amp;OAD' TO g_exclude.     "Select layout
**  APPEND '&amp;amp;AVE' TO g_exclude.     "Save Layout
*  APPEND '&amp;amp;AVE' TO g_exclude.  "Information
ENDFORM.                    " exclude_icons
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Paul Chapman on Jun 5, 2008 6:52 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2008 10:49:04 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-06-05T10:49:04Z</dc:date>
    <item>
      <title>extra pushbutton</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951726#M944671</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;in Function module REUSE_ALV_GRID_DISPLAY  how to add an extra pushbutton along with the layout, Excel buttons...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 10:44:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951726#M944671</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-05T10:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: extra pushbutton</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951727#M944672</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Go to the Documenation for REUSE_ALV_GRID_DISPLAY&lt;/P&gt;&lt;P&gt;and review the requirments for the parm I_CALLBACK_PF_STATUS_SET&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You'll find this&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
Set EXIT rountine to status
Description
Passing an EXIT routine indicates to the ALV that the caller wants to set a self-defined user status.

As a result, the default status of the ALV is not set.

The interface of the form routine specified must be defined as follows:

FORM set_pf_status USING rt_extab TYPE slis_t_extab

Table RT_EXTAB contains the function codes that would be hidden on the standard user interface.

If the caller wants to use a self-defined user interface (for example, in order to provide additional list 
functions or use existing functions), we recommend that you copy standard status STANDARD 
from function group SALV and modify it accordingly. ALV standard function codes always start with '&amp;amp;'.

See also the documentation on parameter I_CALLBACK_USER_COMMAND.

If a self-defined user interface is used that includes function codes of the standard user interface, 
the function codes of the excluding table passed should be taken into account.

This means that the user status should generally be set as follows:

SET PF-STATUS user status EXCLUDING rt_extab.
Application functions can be added to excluding table rt_extab if they are to be disabled.

The routine is called whenever the standard user interface would be set with SET PF-STATUS.

Default
If no EXIT routine is specified, the ALV sets a status that corresponds to status STANDARD of 
function group SALV.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is code that sets it up for use&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
FORM list_view.
*
  g_repid = sy-repid.
  CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
            i_callback_program       = g_repid
            i_callback_pf_status_set = 'STAT_0100'
            is_layout                = g_layout
            it_sort                  = g_sort[]
            it_events                = g_events[]
            it_fieldcat              = g_fieldcat[]
            i_save                   = g_save
            it_excluding             = g_exclude
       TABLES
            t_outtab                 = it_out
       EXCEPTIONS
            program_error            = 1
            OTHERS                   = 2.

  IF sy-subrc &amp;lt;&amp;gt; 0.
    MESSAGE e208(00) WITH 'Error: ALV Grid'.
  ENDIF.
*
ENDFORM.                    " layout_build


*====&amp;gt; End of Actual Display Routine
*====&amp;gt; This establishes the custom PF Status


FORM stat_0100 USING my_exclude.
*
  SET PF-STATUS 'STAT_0100' EXCLUDING my_exclude.
*
ENDFORM.                "end custom PF Status
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And the FORM that list all the common icons and what to use to exclude the ones you do not want.&lt;/P&gt;&lt;P&gt;Simply uncomment the ones you don't want to see.&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
*--------------------------------------------------------------*
*      Form  exclude_icons
*--------------------------------------------------------------*
FORM exclude_icons.
*  APPEND '&amp;amp;ETA' TO g_exclude.     "Details
**  APPEND '&amp;amp;OUP' TO g_exclude.     "Sort Up
**  APPEND '&amp;amp;ODN' TO g_exclude.     "Sort Down
*  APPEND '&amp;amp;ILT' TO g_exclude.     "Set Filter
*  APPEND '&amp;amp;UMC' TO g_exclude.     "Sum
**  APPEND '&amp;amp;RNT_PREV' TO g_exclude.     "Print preview
**  APPEND '&amp;amp;VEXCEL' TO g_exclude.     "Excel
**  APPEND '&amp;amp;RNT_PREV' TO g_exclude.     "Word processing
**  APPEND '%PC' TO g_exclude.     "Local File
**  APPEND '%SL' TO g_exclude.     "Mail recepient
*  APPEND '&amp;amp;ABC' TO g_exclude.     "ABC Analysis
*  APPEND '&amp;amp;GRAPH' TO g_exclude.     "Graphic
**  APPEND '&amp;amp;OL0' TO g_exclude.     "Change layout
**  APPEND '&amp;amp;OAD' TO g_exclude.     "Select layout
**  APPEND '&amp;amp;AVE' TO g_exclude.     "Save Layout
*  APPEND '&amp;amp;AVE' TO g_exclude.  "Information
ENDFORM.                    " exclude_icons
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Paul Chapman on Jun 5, 2008 6:52 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 10:49:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951727#M944672</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-05T10:49:04Z</dc:date>
    </item>
    <item>
      <title>Re: extra pushbutton</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951728#M944673</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;take a look at this code&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
*----------------------------------------------------------------------
* CLASS DECLARATION
*----------------------------------------------------------------------
CLASS lcl_event_receiver DEFINITION DEFERRED.

*----------------------------------------------------------------------
*       CLASS lcl_event_receiver DEFINITION
*----------------------------------------------------------------------
CLASS lcl_event_receiver DEFINITION.
  PUBLIC SECTION.
    METHODS:
      handle_toolbar
         FOR EVENT toolbar OF cl_gui_alv_grid
         IMPORTING e_object
ENDCLASS.

*----------------------------------------------------------------------
*       CLASS lcl_event_receiver IMPLEMENTATION
*----------------------------------------------------------------------
CLASS lcl_event_receiver IMPLEMENTATION.
  METHOD handle_toolbar.
    DATA:
      lwa_tlbar TYPE stb_button.

    lwa_tlbar-function  = '&amp;amp;NEW'.
    lwa_tlbar-icon      = '@0Y@'. "ICON_CREATE
    lwa_tlbar-quickinfo = 'New Record'.
    lwa_tlbar-disabled  = 'X'.
    INSERT lwa_tlbar INTO e_object-&amp;gt;mt_toolbar INDEX 1.
    CLEAR lwa_tlbar.

    lwa_tlbar-function  = '&amp;amp;CHANGE'.
    lwa_tlbar-icon      = '@0Z@'. "ICON_CHANGE
    lwa_tlbar-quickinfo = 'Change Record(s)'.
    lwa_tlbar-disabled  = 'X'.
    INSERT lwa_tlbar INTO e_object-&amp;gt;mt_toolbar INDEX 2.
    CLEAR lwa_tlbar.

    lwa_tlbar-function  = '&amp;amp;DELETE'.
    lwa_tlbar-icon      = '@11@'. "ICON_DELETE
    lwa_tlbar-quickinfo = 'Delete Record(s)'.
    lwa_tlbar-disabled  = 'X'.
    INSERT lwa_tlbar INTO e_object-&amp;gt;mt_toolbar INDEX 3.
    CLEAR lwa_tlbar.

    lwa_tlbar-function  = '&amp;amp;SAVE'.
    lwa_tlbar-icon      = '@2L@'. "ICON_SYSTEM_SAVE
    lwa_tlbar-quickinfo = 'Save Changes'.
    lwa_tlbar-disabled  = 'X'.
    INSERT lwa_tlbar INTO e_object-&amp;gt;mt_toolbar INDEX 5.
    CLEAR lwa_tlbar.

    lwa_tlbar-function  = '&amp;amp;CANCEL'.
    lwa_tlbar-icon      = '@0W@'. "ICON_CANCEL
    lwa_tlbar-quickinfo = 'Cancel Changes'.
    lwa_tlbar-disabled  = 'X'.
    INSERT lwa_tlbar INTO e_object-&amp;gt;mt_toolbar INDEX 6.
    CLEAR lwa_tlbar.
  ENDMETHOD.
ENDCLASS.

DATA: 
  go_alvgd TYPE REF TO cl_gui_alv_grid,
  go_event TYPE REF TO lcl_event_receiver.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create your ALV Grid here,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
CREATE OBJECT go_event.

SET HANDLER  go_event-&amp;gt;handle_toolbar FOR go_alvgd.
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 10:49:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951728#M944673</guid>
      <dc:creator>peter_ruiz2</dc:creator>
      <dc:date>2008-06-05T10:49:44Z</dc:date>
    </item>
    <item>
      <title>Re: extra pushbutton</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951729#M944674</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;u need to define PF_STATUS BAR and pass it to  REUSE_ALV_GRID_DISPLAY in exporting........&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    i_callback_pf_status_set = 'SET_PF_STATUS'&lt;/P&gt;&lt;P&gt;    i_callback_user_command  = 'USER_COMMAND'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and declare the form which will get called when user clicks on the buttons..... in the eg. i have done it for back button....&lt;/P&gt;&lt;P&gt;but the toolbar u create shd be created in TCode SE41 by copying a toolbar from any program which will have all buttons which u want plus the new buttons which u want on the screen ......&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FORM set_pf_status USING rt_extab TYPE slis_t_extab.&lt;/P&gt;&lt;P&gt;  SET PF-STATUS 'TOOLBAR_1' .&lt;/P&gt;&lt;P&gt;ENDFORM.                    "set_pf_status&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*FORM user_command using ucomm LIKE sy-ucomm .&lt;/P&gt;&lt;P&gt;FORM user_command USING r_ucomm TYPE sy-ucomm&lt;/P&gt;&lt;P&gt;                        rs_selfield TYPE slis_selfield.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  CASE sy-ucomm.&lt;/P&gt;&lt;P&gt;    WHEN 'BACK'.&lt;/P&gt;&lt;P&gt;      LEAVE TO SCREEN 1000.&lt;/P&gt;&lt;P&gt;  ENDCASE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDFORM.                    "user_command&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward points if useful......&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 10:50:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951729#M944674</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-05T10:50:49Z</dc:date>
    </item>
    <item>
      <title>Re: extra pushbutton</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951730#M944675</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear &lt;/P&gt;&lt;P&gt;No need to use separate button for ALV download to Excel &lt;/P&gt;&lt;P&gt;you can use Menu-List-Export or Local file tool to down load&lt;/P&gt;&lt;P&gt;if you want to use Button also u may need to use Customer Container in Screen area (like Envelope object)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rewards if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 10:51:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951730#M944675</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-05T10:51:10Z</dc:date>
    </item>
    <item>
      <title>Re: extra pushbutton</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951731#M944676</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;U can add push button using th eimport parameter&lt;/P&gt;&lt;P&gt;I_CALLBACK_PF_STATUS_SET &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;read its documentation in the function module&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 10:51:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951731#M944676</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-05T10:51:43Z</dc:date>
    </item>
    <item>
      <title>Re: extra pushbutton</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951732#M944677</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;U need to create an your own pf-status as copy of the std one: prg. SAPLKKBL status STANDARD_FULLSCREEN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So set your status instead of std one by a routine like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;FORM SET_PF_STATUS  USING RT_EXTAB TYPE SLIS_T_EXTAB.
  SET PF-STATUS 'MY_ALV' EXCLUDING T_EXTAB.
ENDFORM.                    " set_pf_status&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;U need to create a routine for the USER-COMMAND event:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;FORM USER_COMMAND USING R_UCOMM     LIKE SY-UCOMM
                        RS_SELFIELD TYPE SLIS_SELFIELD.
ENDFORM.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it needs to indicates the routine above while calling fm ALV:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;GT_REPID = SY-REPID.

  CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
*         I_INTERFACE_CHECK        = ' '
          I_CALLBACK_PROGRAM       = GT_REPID
          I_CALLBACK_PF_STATUS_SET = 'SET_PF_STATUS'
          I_CALLBACK_USER_COMMAND  = 'USER_COMMAND'&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 10:52:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951732#M944677</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-05T10:52:31Z</dc:date>
    </item>
    <item>
      <title>Re: extra pushbutton</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951733#M944678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;You just copy the standard Pf status in your program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   The interface of the form routine specified must be defined as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;           FORM set_pf_status USING rt_extab TYPE slis_t_extab&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   Table RT_EXTAB contains the function codes that would be hidden on the&lt;/P&gt;&lt;P&gt;   standard user interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   If the caller wants to use a self-defined user interface (for example,&lt;/P&gt;&lt;P&gt;   in order to provide additional list functions or use existing&lt;/P&gt;&lt;P&gt;   functions),I  recommend that you copy standard status STANDARD from&lt;/P&gt;&lt;P&gt;   function group SALV and modify it accordingly. ALV standard function&lt;/P&gt;&lt;P&gt;   codes always start with '&amp;amp;'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In that GUI status just add another Fn code to the application toolbar and you will get the added fn code as button at your application toolbar with sy-ucomm as the fn code&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 11:00:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951733#M944678</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-05T11:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: extra pushbutton</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951734#M944679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Once ur problem is solved , mark the post as answered.... and reward points .....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2008 11:04:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/extra-pushbutton/m-p/3951734#M944679</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-06-05T11:04:29Z</dc:date>
    </item>
  </channel>
</rss>

