ABAP & W E B D Y N P R OA B A P@ARJUN IGROWSOF

T
CLASSICAL REPORTS
A report with single input screen (selection screen) and single output screen
(list screen) is called a classical report.

Events in Classical Reports: - All the ABAP programs are developed using
events because ABAP is “EVENT DRIVEN PROGRAMMING LANGUAGE” i.e. the
entire ABAP program execution is based on order of events.

The List of the events are:

Load of Program
Initialization

At Selection-screen output At Selection-screen on field

At Selection-screen on value request At Selection-screen on Help Request At Selection-screen
Start of selection End of selection Top of page
End of page

Load of Program: - This event is used to load the program into memory for
execution. This is internal event, which we cannot see.

ARJUN…….LEARNREALTIMESCENARIOSDONEBYME Page 1
A B A P&WE B D Y N P R O ABA P @ A R J U N IGROWSOFT

Initialization: - This event is used to initialize the default values to program

variables and selection-screen variables.

Examples: v_land1 = ‘IN’

v_bukrs = ‘1001’

p_werks = ‘US’

p_mtart = ‘FERT”

AT Selection-screen output: - This event is used to modify the selection screen

dynamically based on user actions on the selection screen.

This event is triggered (or) executed for every action on the selection screen.

AT Selection-screen on field: - This event is used to validate a single input field

on the selection-screen.

AT Selection-screen on value request: - This event is used to provide a search

help for an input field. This event is triggered whenever the user click on search
help button.

AT Selection-screen on help request: - This event is used to provide help

information for an input field.This event is triggered whenever the user click on
Help button i.e. F1 button.

AT Selection-screen: - This event is used to validate multiple fields of the

selection-screen, whereas AT Selection-screen on field is used to validate a
single input field.

Start of selection: - This event is used to write the original business logic
statements i.e all select statements. It is also used to indicate the starting point
of a program. It is the default event.

ARJUN…….LEARNREALTIMESCENARIOSDONEBYME Page 2
ABAP & W E B D Y N P R OA B A P@ARJUN IGROWSOFT

End of selection: - It is used to indicate the start of selection has been ended.
It is mainly used with logical database, which are absolute in ABAP (LDB’s are
used in old version of ABAP). But LDB’s are stilled used in HR-ABAP, so end of
selection is mainly used in HR-ABAP. It doesn’t have much importance in ABAP,
it is used to indicate the start of selection has been ended

Top of page: - This event is use to display constant page heading for all the
pages in the output screen. This event is triggered after the first WRITE
statement.

End of page: - This event is used to provide constant footer information

across the all pages of the list-screen. To display end of page (or) footer
information we have to reserve some lines as footer lines using the
statement.

Report
Ex <Report
Program: Name>
Will be Line separately.
discussed Count Total Lines(Footer Lines)

Using AT Selection-screen output: - This event is used to modify the selection

screen dynamically based on user actions on the selection screen.

This event is triggered (or) executed for every action on the selection screen.

Modification ID: - It is an ID assigned to a group of Selection- screen fields, So

that the properties of all the selection screen fields can be modified directly
with the help of modification ID.

Suppose if Modification ID is not available then we have to modify each

selection- screen field individually which makes program very complex.

Syntax: -

Parameters: <p_name> type <table-fname> MODIF ID <modification ID name>.

Ex Program: Will be discussed separately.

ARJUN…….LEARNREALTIMESCENARIOSDONEBYME Page 3
A B A P&WE B D Y N P R O ABA P @ A R J U N IGROWSOFT

What is difference between AT Selection-screen on field and AT selection-screen?

1)ATItSelection-screen onafield
is used to validate single filed AT selection-
1)It is used to validate multiple fields

2) Whenever there is an error on a 2) Whenever there is an error on a

field, field the entire screen will be the entire screen will be
disabled enabled.

Except the error field,

Ex Program: Will be discussed separately.

ARJUN…….LEARNREALTIMESCENARIOSDONEBYME Page 4
A B A P&WE B D Y N P R O ABA P @ A R J U N IGROWSOFT

INTERACTIVE REPORTS
Display the basic information on the basic list and the detailed information in
the Secondary list is called Interactive report.

The first list is called basic list and the number is 0.

The remaining lists are called as secondary lists and the number start from 1 to
20. So totally there are 21 lists.

The lists no are stored in a system variable SY-LSIND.

If you select any line, then the selected line data is stored in SY-LISEL.

Interactive Reports Events:-

AT Line selection

AT User command

Top of page during line

selection AT PF <Function Key>.

AT Line Selection: - This event is triggered whenever the user double clicks on
any list line. To know the selected line contents, we have two keywords or
statements

1) HIDE
2) GET CURSOR

At User command: - This event is triggered whenever the user clicks on custom
GUI buttons.

Top of page during line selection: - This event is used for providing the
constant page heading for all the secondary lists.

AT PF <Function Key>: - This event is used or triggered whenever the user

clicks on function keys (f1, f2, .etc)

This event is obsolete in new versions (ECC 5.0 or 6.0)

ARJUN…….LEARNREALTIMESCENARIOSDONEBYME Page 5
A B A P&WE B D Y N P R O ABA P @ A R J U N IGROWSOFT

HIDE: - It is a keyword which is used to hide the data into a temporarily

memory called as hide area for further processing. We use the hide statement
within the loop….end loop, so that the HIDE keyword will hide the values into
hide area.

Functionality of hide: - Whenever the user double clicks on any list line, the
event at line selection will be triggered.

The system automatically identifies the line no where the user has double
clicked and reads the corresponding record into hide variable.

Ex Program: Will be discussed separately.

GET CURSOR: - This statement is used to read or get the selected line content
i.e. fieldname, field value into the variables.

Syntax: - GET CURSOR field <v_fname> Value <v_fvalue>.

The main Advantage of get cursor is,

We don’t have any hide area or temporary memory

We can generate interactive report based on field name and field value
which is not possible with HIDE statement.

The other difference between hide and get cursor is, with the hide statement
the system uses line no and gets the value into hide variable without knowing
what is the fieldname.

Whereas the get cursor will get the exact field name and field value with
which we can generate various interactive reports based on filed names.

Ex Program: Will be discussed separately.

ARJUN…….LEARNREALTIMESCENARIOSDONEBYME Page 6
A B A P&WE B D Y N P R O ABA P @ A R J U N IGROWSOFT

Conversion Routine: - It is a function module which is used to convert a value

from internal format to external format and vice-versa.

Conversion exits are maintained at domain level.

Go to the domain and double click on conversion exit.

Conversion exit function module will be displayed

Example: -

Conversion_exit_Alpha_input :- used to convert a value from exeternal format

to internal format.

Conversion_exit_Alpha_output:- used to convert a value from internal format

to external format

AT user command: - This event is triggered whenever the user clicks on Custom
GUI button.

Custom GUI: - It is used to create our menus in the menu bar, our own buttons
in the application toolbar, enabling or disabling the standard buttons on the
standard toolbar.

Syntax: - SET PF-status <CustomGUI MenuName>

‘SE41’is the tcode for creating custom GUI (also called as MENU PAINTER)

FCT CODE (Function code):- It is a shortcut code assigned to a button or menu

to identify the button or menu which is clicked .

The FCT codes are automatically stored in a system variable SY-UCOMM.

Ex Program: Will be discussed separately.

ARJUN…….LEARNREALTIMESCENARIOSDONEBYME Page 7
A B A P&WE B D Y N P R O ABA P @ A R J U N IGROWSOFT

ARJUN…….LEARNREALTIMESCENARIOSDONEBYME Page 8