4 - ABAP Programming Part2
4 - ABAP Programming Part2
1
Classical Reports
▪ Reports are programs that read data from the database, processes the data and displays
▪ SAP ABAP classical reports are the most basic ABAP reports in which we displayed the
2
Open SQL
▪ It is of 2 types.
3
Open SQL Queries
▪ This query fetches data from database table ztordh_88, based upon the select-options
s_ono.
4
Open SQL Queries(Contd.)
▪ This query fetches data from database table ztordh_88, based upon the parameter
p_ono.
5
Open SQL Queries - For All Entries In
▪ When we fetch the data from multiple tables, ‘For All Entries In’ is the best alternative.
6
Open SQL Queries - Join
▪ With the help of join, we can read from more than one table in a single select
statement.
▪ Join is of 2 types.
1. Inner Join
2. Outer Join
7
Inner Join
▪ An inner join finds and returns matching data from tables based upon specified
conditions.
▪ If one or more criteria are not met, no data records are created in the result set.
8
Outer Join
▪ Outer join finds and returns matching data and non-matching data from tables.
9
Left Outer Join
▪ The left outer join takes all the values from the left table and combines them with the
1
0
Right Outer Join
▪ The right outer join takes all the values from the right table and combines them with the
1
1
Best Performance Practices/Guidelines
▪ Never use * in the query. Fetch the data of only those columns which are required.
sequence.
▪ Where condition column sequence needs to be same as that of data dictionary column
sequence.
▪ For traditional databases avoid using JOIN, use FOR ALL ENTRIES IN.
▪ For fetching data from foreign key tables/dependent tables - check for sy-subrc or
▪ For multiple conditions, use CASE conditional statement rather than IF conditional
statement.
1
3
Best Performance Practices/Guidelines(Contd.)
1
4
Message Class
S(success/status),W(warning), X(exit).
1
5
Message Class(Contd.)
▪ In the above syntax - MESSAGE = keyword , E = error message type , 000 is message
1
6
Transaction Code
1
7
Classical Report Events
▪ Classical reports are the most basic ABAP reports in which we display the output using
WRITE statement.
▪ The example of specific actions are mouse click, pressing a key etc. The example of
1
8
Classical Report Events(Contd.)
▪ The same concept of events is applicable to classical reports. Some events trigger by
specific user action and some events trigger at specific occurrence in classical reports.
Initialization
At selection-screen
Start-of-selection
End-of-selection
1
9
Classical Report Events(Contd.)
Top-of-page
End-of-page
At selection-screen output
At selection-screen on <field>
2
0
Initialization
▪ The purpose of this event is to assign the default values to parameters and select-
options.
2
1
AT Selection-Screen
▪ This event calls when user performs some action (enter, click etc.) on to the selection
screen.
2
2
Start-of-Selection
▪ This event calls when user clicks execute button on the selection screen.
2
3
End-of-Selection
▪ This event calls when selection process ends or after the last statement in the START-OF-
2
4
Top-of-Page
▪ This event calls when the first write statement occurs in a program for
a page.
▪ The purpose of this event is to provide title/header at the beginning of a new page.
2
5
End-of-Page
▪ This event calls when the last write statement occurs in a program for
a page.
▪ The purpose of this event is to provide footer or some information at the end of a new
page.
▪ Example: LINE-COUNT 5(2), It means the total number of lines on a page is 5 and out of
▪ The purpose of this event is to modify the selection screen before it is displayed.
2
7
Initialization and AT Selection-Screen Output Comparison
▪ 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.
2
8
AT Selection-Screen and 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 equal to PAI( Process After Input) of module pool whereas
▪ The purpose of this event is to provide value help for an input field.
3
0
AT Selection-Screen On Help Request For <Field>
3
1
AT Selection-Screen On <Field>
▪ This event calls when user performs some action (enter, click etc.) on to the selection
screen.
▪ This event is used to validate a particular input field present on the selection screen.
3
2
AT Selection-Screen and AT Selection-Screen On <Field> Comparison
screen on <field> event is to validate a particular input field present on the selection
screen.
▪ In case of at selection-screen event to highlight a wrong input field the explicit logic is
required, whereas in at selection screen on <field> the wrong input field highlighted
automatically.
3
3
AT Selection-Screen and AT Selection-Screen On <Field> Comparison
▪ In case of at selection-screen event all input fields remain enable after the wrong input
whereas in case of at selection-screen on <field> event the wrong input field remain
3
4
Interactive Classical Report Events
▪ In classical report we only display the output on basic list . There is no interaction with
the output.
▪ In Interactive classical report is one 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.
3
5
Interactive Classical Report Events(Contd.)
At line-selection
At user-command
3
6
AT Line-Selection
▪ When user double clicks on the line or select a line and press F2 or select a line and click
3
7
AT User-Command
▪ When user clicks on the functions created using pf-status, at that time at user-command
event triggers.
▪ The system variable sy-ucomm is used to capture the value of function code.
3
8
Top-of-Page During Line-Selection
▪ This event calls when the first WRITE statement occurs in a program
▪ The purpose of this event is to provide title/header at the beginning of a new page on
secondary list.
3
9
Interactive Classical Reports Statements - HIDE
interactive reporting.
▪ The above statement places the contents of the variable <f> into the
4
0
Interactive Classical Reports Statements - HIDE(Contd.)
▪ We can consider hide area as a table which stores the field name, field
4
1
Interactive Classical Reports Statements - Working of HIDE
▪ The user selects a line for which data has been stored in the HIDE
area.
▪ The runtime system jumps to the point in the HIDE area where data for
this
line is stored.
▪ The runtime system then inserts all values stored for the selected line
4
2
Interactive Classical Reports Statements - GET CURSOR
▪ In interactive classical reports, GET CURSOR statement is used to create secondary lists
▪ The parameter FIELD provides the name of an output field. The parameter VALUE
▪ In the above syntax - the field name and field value will be returned in to variables
▪ HIDE statement responds for a particular line whereas GET CURSOR statement responds
▪ HIDE statement is used to store the line with line number in the hide area whereas GET
▪ With HIDE statement, we can not display secondary lists based upon Individual field
name and field value whereas with GET CURSOR statement we can display secondary
lists based upon the Individual field name and field value.
4
4
System Variables in Interactive Classical Report Events
▪ The various system variables used in interactive classical report events are as follows:
SY-LISEL - It is a system variable which returns the contents of the selected line.
SY-LSIND - It is a system variable which returns the index of the displayed list. For the
basic list SY-LSIND = 0 and for the secondary lists SY-LSIND > 0.
4
5
Control Break Statements
▪ Control break statements are used to control loop or we can say they are used to control
AT FIRST
AT LAST
AT NEW <fieldname>
AT END OF <fieldname>
4
7
Types of Control Break Statements
AT FIRST - It triggers for the first row/first record/first iteration of the internal table in
loop.
AT LAST - It triggers for the last row/last record/last iteration of the internal table in
loop.
AT NEW <fieldname> - It triggers for the new/first record of a group having the same
4
8
Types of Control Break Statements(Contd.)
AT END OF <fieldname> - It triggers for the end/last record of a group having the same
4
9
Control Break Statements With SUM Statement
▪ SUM statement can only be used in loop- endloop statement and needs to be applied in
▪ SUM calculates the sum of all numeric fields to the right of the current group key.
▪ The sum is for all rows of the current group and assign it to the corresponding fields of
the workarea.
5
0
Control Break Statements - Important Points
▪ Always sort the internal table based upon the fieldname used in AT NEW<fieldname> or
AT END OF <fieldname>.
▪ The event AT NEW <fieldname> and AT END OF <fieldname> also triggers if the value of
other fields change which are present on the left hand side of specified fieldname. If we
fieldname only , then we need to take specified fieldname at the first position in the
internal table.
5
1
Control Break Statements - Important Points
▪ Whenever AT FIRST and AT LAST control break events triggers all character field values
character fields on the right hand side of specified fieldname converted to **** and
Solution : Store the values in a temporary work area before any of the control break
event triggers.
5
2
Database Operations
▪ Database operations deals with database tables. The various database operations are as
follows:
Update - Update is used to update the existing records in the database tables.
Delete - Delete is used to delete the existing records from database tables.
5
3
Database Operations(Contd.)
Modify - It works for both - insert + update. For existing records - It acts as update, for
5
4
Report Variant
▪ When we run the same program with the same set of input or selections, so instead of
passing the input every time, we can save the input values in a selection set which is
called a variant.
5
5
Field Symbols
▪ Field symbols do not reserve any physical memory space, but point to the content of the
data objects.
▪ After declaring a field symbol, we can assign the data object to the field symbol.
5
6
Field Symbols(Contd.)
▪ In the above syntax, FIELD-SYMBOLS = keyword , where fs is the name of the field
symbol. The name of the field symbol is always enclosed between <>.
5
7
Types of Field Symbols
5
8
Typed Field Symbol
▪ When we provide the data type like elementary, complex etc. to the field symbol, then it
compatibility of the field symbol and the data object assigned to that
field symbol.
▪ In the above syntax, the field symbol is of elementary data type Integer(I).
5
9
Generic Field Symbol
▪ When we provide the generic data types like ANY and ANY TABLE to the field symbol,
6
0
Field Symbol as a Replacement of Work Area
▪ We can replace work area by field symbol while performing internal table operations.
▪ This is because work area stores a copy of the internal table row, whereas field symbol
▪ Hence processing of internal table with field symbol is faster than the
6
1
Modify the Internal Table Contents Using Field Symbols
▪ We can declare a field symbol of type any structure, which we can use
▪ If we change any field of structure in field symbol, the corresponding field in internal will
get updated.
▪ So , there is no need to write the MODIFY statement when we use field symbols to
6
2
Thank You
6
3