Exploring Classical Report Events: Page Overflow, At Selection-Screen Output, and More

 Welcome back everyone, we were discussing about Classical Report events, So let’s continue it.

Page Overflow :-

  • There is always a big possibility to get a runtime error when we blindly give line count for End of page event,



  • let’s analysis the reason, why we got a runtime error.

Ans :- Page overflow generates when the size of page is not enough to adjust end of page and header of page, So we need to make sure that their size is compatible before taking any blind decision.

7. At Selection-Screen Output

  • This event calls before displaying the selection screen or input screen.
  • The purpose of this event is to modify the selection screen.

Note :- We have seen that, Initialization event also triggers just before displaying the selection screen. So, What’s the difference

Initialization Vs At Selection Screen Output :-

  • Initialization event calls only first time before displaying the selection screen whereas at selection screen output event calls every time before displaying a selection screen.
  • Initialization event is to assign the default values to parameters and select-options whereas at selection-screen output event is used to modify the selection screen.

At Selection Screen Vs At Selection Screen Output Comparison

  • At selection screen event calls when user performs some action(enter, Click etc.) on to the selection screen whereas at selection screen output event calls before displaying the selection screen.
  • At selection screen event is to validate the input whereas at selection screen output is used to modify the selection screen.
  • At selection screen event is equal to PAI(Process After Input) of module pool whereas at selection-screen output is equal to PBO(Process before Output) of module pool.

Implementation of At Selection Screen Output:-

Requirement :-

  • Suppose, this is our selection screen.



  • And, Now I want that, As soon as I open the selection screen, The currency field should be invisible and there will be a checkbox at the selection screen, and I enable that checkbox, the currency field will become visible.

Solution :-

  • Create a parameter for checkbox.
  • Loop at screen and provide the necessary logic.


Code :-

***********************************************
*Start of Program
***********************************************
*Declaring type strcuture
TYPES: BEGIN OF ty_header,
         order_number TYPE zar_order_number,
         order_date   TYPE zar_order_date,
         payment_mode TYPE zar_payment_mode,
         currency     TYPE zar_curency,
       END OF ty_header.
****************
*Internal Table and Work Area
DATA : lt_header TYPE TABLE OF ty_header,
       ls_header TYPE ty_header.
****************************************
DATA : lv_pm   TYPE zar_payment_mode,
       lv_curr TYPE zar_curency,
       lv_date TYPE zar_order_date.

SELECT-OPTIONS : s_odate FOR lv_date NO-EXTENSION.
SELECT-OPTIONS : s_pm FOR lv_pm NO INTERVALS.
SELECT-OPTIONS : s_curr FOR lv_curr NO INTERVALS MODIF ID CUR.
PARAMETERS : p_chk TYPE c AS CHECKBOX.

****************************
*Initializaton Events.
INITIALIZATION.
*****************
*For Date
  s_odate-sign = 'I'.
  s_odate-option = 'BT'.
  s_odate-low = sy-datum - 100.
  s_odate-high = sy-datum.
  APPEND s_odate.

********
*For Payement Mode
*  s_pm-low = 'C'.
*  APPEND s_pm.

***************
*Currency
  s_curr-low = 'INR'.
  APPEND s_curr.

***********************************
AT SELECTION-SCREEN OUTPUT.
  IF p_chk = ' '.
    LOOP AT SCREEN.
      IF screen-group1 = 'CUR'.
        screen-active = '0'.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
  ENDIF.
  IF p_chk = 'X'.
    LOOP AT SCREEN.
      IF screen-group1 = 'CUR'.
        screen-active = 1.
        MODIFY SCREEN.
      ENDIF.
    ENDLOOP.
  ENDIF.

***********************************
*At Selection Screen
AT SELECTION-SCREEN.
  IF s_pm-low IS INITIAL.
    IF s_pm-low <> 'C'.
      MESSAGE 'Payment mode is not entered' TYPE 'E'.
    ENDIF.
  ENDIF.

**********************************
*Start Of Selection.
START-OF-SELECTION.
  SELECT order_number order_date payment_mode currency
    FROM zar_header
    INTO TABLE lt_header
    WHERE currency IN s_curr.

***********************************
*Displaying data
  LOOP AT lt_header INTO ls_header.
    WRITE :/ ls_header-order_number,
             ls_header-order_date,
             ls_header-payment_mode,
             ls_header-currency.

  ENDLOOP.

*******************************
*End of Selection.
END-OF-SELECTION.
  WRITE :/ TEXT-001.

***********************************
*Top of Page
TOP-OF-PAGE.
  WRITE :/ TEXT-002, sy-pagno.

*************************************
*End of Page
END-OF-PAGE.
  WRITE :/ 'END Of page Number', sy-pagno.
*****************************************
*End OF Program
****************************************

Execute the program :-



Enable the checkbox and press enter :-



So, this is how at selection screen output works.

8. At Selection-Screen On Value Request for <Field> :-

  • This event calls when user clicks F4 on a field of Selection Screen.
  • The purpose of this event is to provide value help for a input field.


9. At Selection-screen On Help Request For <Field> :-

  • This event calls when user clicks F1 on a field of Selection Screen.
  • The purpose of this event is to provide technical information for a field.

Interactive Classical Report Events :-

1. What is the difference between Interactive Classical Report and Classical Report ?

  • In Classical Report, we only display the output on basic list, There is no interaction with the output.
  • In Interactive Classical Report, we interact with the output on basic list and it take us to secondary list.
  • Basic list is the list which is generated at first by our ABAP program.
  • The secondary lists are generated by further navigation or user selection from the basic list.

2. How many number of basic lists are there ?

  • the number of basic list in classical report is 1.
  • The number of secondary list in classical report is 20.

Types of Interactive Classical Report Events :-

  • At line-selection.
  • At user-command
  • Top of page during line selection

So, that’s enough for today.

We will implement the Classical Report Events in our next blog.

Thanx a lot for being a part of this wonderful journey.

Location: India

Comments

Post a Comment

Popular posts from this blog

Understanding Different Types of SAP Function Modules: Normal, RFC, and Update

Image
  1. Normal/Regular Function Module :- It can be called inside the system. Here Pass by value + Pass by reference both is fine. 2. RFC Function Modules :- You can call from same system or from another possible. In RFC function module you can only have pass by value. In the same system if you are going to add the DESTINATION NONE’ while calling the RFC then it’ll be called in separate session. 3. UPDATE Function Modules :- This is generally used to update the database record. Update Function Module can be called from the same system. ( Background RFC / trfc / grfc ) This is used to achieve generally the SAP LUW. Some time we use from performance perspective also. When COMMIT WORK gets executed then Update starts getting executed. Important Questions on Update Function Modules :- When Update function Module gets Triggered ? ON COMMIT WORK IF a update function module gets failed, under which transaction we can see that ? OR What is the T-Code for moni
Read more

Unlocking SAP ABAP Secrets: Interactive Classical Reports with GET CURSOR, At User Command, and a Comparison of HIDE Statements

Image
 Welcome back everyone, We were discussing about the interactive classical reports, so let’s continue it. Interactive Classical Reports- GET CURSOR :- In Interactive Classical Reports, GET CURSOR statement is used to create secondary list according to cursor position. The parameter FIELD provides the name of an output field. The parameter VALUE provide the output value. Syntax : GET CURSOR FIELD <lv_field> VALUE <lv_value>. In the above syntax - the field name and field value will be returned in to variables lv_field and lv_value respectively. Requirement :- If you remember, In our last two blog, We have been displaying the order header table in a basic list and order item table in the secondary list. We have used SY-LISEL and HIDE statements to achieve the requirement. Now, we have to use the get CURSOR to achieve the same to same requirement. Code :- ************************************************************* *Start of Program *Declaring Strcutrure
Read more

Mastering ABAP: A Step-by-Step Guide to Function Modules and Groups for Modularized Programming

Image
  Function Modules :- It is a modularization technique. The transaction code to create a function module is SE37. To create a function module, we need to create a function group. Function Group :- Function group is a container for the function modules. The transaction code to create a function group is SE80. A function group can store up to 99 function modules. Requirement :- let’s create a function module for sum of two numbers. 1. Creation of function group :- Step 1 :- Go to SE80 transaction code → Object Navigator. Step 2 :- From the drop down select function group. Step 3 :- Give a name of function group. Step 4 :- press enter. Step 5 :- Click on yes a popup screen will appear. Step 6 :- Give short description → press enter → Assign package and transaction request and press enter. Step 7 :- Right click on function group and click on activate to activate the function group. Step 8 :- You will see two includes, will be added after ac
Read more