Thursday 18 August 2016

Events in Classical Interactive Report


  • It is used to get multiple output list.
  • The first output list is called basic list.
  • Based on basic list selected list output is called secondary list.
  • Moving based on from one report to another report is know as drill down report.
  • Including basic report , we can create 21 interactive reports.

Events in Classical Interactive Report 



  • Initialization.
  1. To initialize the value to variables.
  2. To assign the values to parameter as well as select-option.
  • At-selection-screen.
  1. Used to validate  selection screen input.
  • At-selection-screen output .
  1. Used to modify the screen layout.
  • At-selection-screen on <field> 
  1. To validate the particular filed.
  • At-selection-screen on value-request.
  1. Used to provide search help for a particular field. 
  •  At-selection-screen on help-request.
  1. Used to provide documentation help for particular field.
  • Start-of-selection.
  1. Actual program execution starts from here.
  • End-of-selection.
  1. Usually output related  codes are written here.
  • Top-of-page.
  1. If you want put headings for report, then write code here.
  • End-of-page.
  1. Used to put footer .
  • At line selection.
  1. At line selection Occurs after the user double-clicks on a line, clicks once on a hotspot, or chooses Edit-Choose
  • At user command.
  1.   AT USER-COMMAND occurs after the user chooses a self-defined action. SY-UCOMM contains chosen function code.
  2. ·         SET USER-COMMAND <command> triggers event from within the program. Takes effect after the current list is completed. Before the system displays the list, it triggers the event that corresponds to the function code stored in <command>, independent of the applied user interface. 






  • At pf.
  1. ·         AT PF<nn> occurs after the user presses the corresponding function key. Predefined system functions have higher priority than self-defined events. The system does not trigger an event AT PF<nn> for keys whose function code is predefined:


  • Recommended use AT PF for testing purposes only. In final version use AT USER-COMMAND together with self-defined interfaces.  
  • End-of-selection.
  • Top-of-page during line selection.
  • SET PF-STATUS:


  1. Syntax :
    SET PF-STATUS <status> [EXCLUDING <function>|<itab>] [IMMEDIATELY].

  • Sets user-defined <status> for all subsequent list levels until you set another status. SY-PFKEY - status of the current list. <status> is SPACE to set system status. <function>, type C(4), (or list of functions in the <itab>) - function code(s) to be deactivated in the <status>. IMMEDIATELY changes the status of the currently displayed list (SY-LISTI) within the processing block of the interactive event. Without this option, the system changes the status of the current secondary list (SY-LSIND) that is displayed only at the end of the processing block. 
                             more information........



No comments:

Post a Comment