Preface – This post is part of the ABAP Beginner series.
Events in ABAP
ABAP is an event driven Programming language. ABAP Report Events are used to handle different kinds of events during runtime. It starts with the event name, followed by the programming codes belonging to that event.
It is advisable to use Comment line to declare the end of an event, since Events do not have a closing Keyword and it ends as soon any other Event starts.
There are different kinds of events in ABAP, SAP has categorized these events together.
Categories of Events in ABAP:
There are three categories of Events in ABAP:
Event Category
Explanation
Events in the Category
Program Constructor Events
Except Pool programs it occurs in every programs.
LOAD-OF-PROGRAM
Reporting Events
These events occur only in Executable Reports.
INITIALIZATION
START-OF-SELECTION
END-OF-SELECTION (obsolete)
Selection Screen Events
These events occur during Selection Screen Processing
AT SELECTION-SCREEN OUTPUT
AT SELECTION-SCREEN
List Events
These events occur during Classical List Processing [List can be a table or consecutive Write statements, etc.]
TOP-OF-PAGE
END-OF-PAGE
AT-LINE-SELECTION
AT USER-COMMAND
AT PFnn
SET USER-COMMAND
Events in Classical Report:
Classical Reports have following events:
LOAD-OF-PROGRAM : First event fired, loads program in memory
INITIALIZATION: Initialize variable
START-OF-SELECTION : Actual Business Logic (After START-OF-SELECTION)
END-OF-SELECTION : To end above
AT SELECTION-SCREEN : To validate Multiple Input fields (After Initialization and before START-OF-SELECTION) (After
AT SELECTION-SCREEN OUTPUT: To manipulate Dynamic screen
AT SELECTION-SCREEN ON
AT SELECTION-SCREEN ON END OF
AT SELECTION-SCREEN ON BLOCK
AT SELECTION-SCREEN ON RADIOBUTTON GROUP
AT SELECTION-SCREEN ON VALUE REQUEST
TOP-OF-PAGE : To print heading
END-OF-PAGE: To print footer
Programming Guidelines:
Never use Selection Screen Events in Function Module
Use LOAD-OF-SCREEN to load default values for the type of Reports executed via SUBMIT or using a transaction code
Use INITIALIZATION to load default values for the executable type of Reports
It is advised not to specify an event more than once [Except AT-SELECTION-SCREEN & GET event, all other can be specified multiple times.]
If you are not specifying any event name, still specify START-OF-SELECTION to improve readability
After every execution of events NEW-LINE event is executed automatically
Preface – This post is part of the ABAP Programs series.
Type Casting in ABAP Class
Note: If you are searching for basic type casting/conversion of ABAP variable in Reports/Program, click here.
Prerequisite:
1. You must have a basic Idea of local class and instance/reference of class.
2. Inheritance and Polymorphism concept
Note: Parent Class is also called base class and Child class is also called Sub class.
What is Static and Dynamic Type?
Before we talk about type casting, we need to know what are static Type and Dynamic type. Each reference variable has a dynamic type and a static type.
Suppose we have a class C1 and its child class C2.
So, in our program we will write following code to make reference and create object.
DATA: obj1 TYPE REF TO C1.
Here obj1 is our reference variable and C1 is the Static Type.
Thus anything that comes after TYPE REF TO is a static type because the object obj1 is pointing to fixed or static type [here class C1].
Now, in our code, we proceed as below:
CREATE OBJECT obj1.
In this line we actually point to the class C1 using our object obj1. This pointing is called Dynamic Type and it is pointing to C1 same as the static type above.
We can also write following code:
CREATE OBJETC obj1 TYPE C2.
In this line we are pointing to child class C2 of C1. This pointing is defined at runtime and called as Dynamic Type, and this time it is not same as the static type.
Thus we conclude that Dynamic type is defined at runtime of the program while static type is declared with the declaration of reference variable. Static type can be same as Dynamic type or less specific than it [it means, it can just point to the parents and not all the child unlike the dynamic type which can].
What is a Type casting?
Type Casting in ABAP is just like casting in other computer languages. It is one way of inheriting the properties from either base/parent class or sub/child class into one another. It is used to cast one data type, class or Interface into another data type, class or interface.
Type casting is a process of converting reference of class or interface to another, given both the class are from same hierarchy i.e. either one of them must be a parent class and the other a child class.
Preface – This post is part of the ABAP Programs series.
To delete duplicates in ABAP either from a string or an internal table, we need to use ABAP statement “DELETE ADJACENT DUPLICATES FROM”. In this article, we have taken an example, which implements deletion of duplicate data when two strings are merged. This process also involves internal table.
Introduction
DELETE ADJACENT DUPLICATES FROM <Internal Table> COMPARING <field name>.
Using the ABAP statement mentioned above, we can compare values of a column of any table/ internal table and delete the duplicates. Once the duplicates are deleted, we get unique values from a string/ internal table.
SPLIT <variable> AT ‘,’ INTO TABLE <internal table>.
Using the ABAP statement mentioned above, we can divide a string in to a form of internal table where each data is separated by comma ‘,’.
Delete Duplicates in ABAP – Image Illustration
ABAP Program to Delete duplicates
DATA : lv_string TYPE string,
lv_string2 TYPE string,
lv_string_final TYPE string.
TYPES: BEGIN OF ty_data,
auth TYPE c,
END OF ty_data.
DATA: ls_user TYPE ty_data,
ls_user2 TYPE ty_data,
lt_user2 TYPE TABLE OF ty_data,
lt_user TYPE TABLE OF ty_data.
lv_string = 'a,b,c,a'.
lv_string2 = 'd,b,c,a'.
SPLIT lv_string AT ',' INTO TABLE lt_user.
SPLIT lv_string2 AT ',' INTO TABLE lt_user2.
LOOP AT lt_user2 ASSIGNING FIELD-SYMBOL(<fs_field>).
INSERT <fs_field> INTO TABLE lt_user.
ENDLOOP.
SORT lt_user BY auth.
DELETE ADJACENT DUPLICATES FROM lt_user COMPARING auth.
IF sy-subrc = 0.
LOOP AT lt_user ASSIGNING FIELD-SYMBOL(<fs_user_table>).
IF lv_string_final IS INITIAL.
lv_string_final = <fs_user_table>-auth.
ELSE.
CONCATENATE lv_string_final <fs_user_table>-auth INTO lv_string_final SEPARATED BY ','.
ENDIF.
ENDLOOP.
ENDIF.
WRITE lv_string_final.
Explanation
Here, we have written program which tIn the above program, following steps have been implemented:
Initially, we have defined variables: lv_string, lv_string2 and lv_string_final of type string. These variables will be used to feed two input strings and save the merged the string.
Now, we have defined a structure with one field. We have created this so that we can use this field to perform duplicate deletion.
Again, we have defined variables: ls_user, ls_user2, lt_user2 and lt_user. These are the work areas (ls) and internal tables (lt). These will be used to store data line by line from the strings defined in step 01 above.
Now, we will feed some default data in form of strings i.e. lv_string = ‘a,b,c,a’ and lv_string2 = ‘d,b,c,a’. These variables do contain duplicate data.
Here, we converted the strings into internal table.
Then, we deleted duplicates from the internal table created above.
Then, we have again concatenated the new internal table data i.e. unique data into a string divided by comma ‘,’.
In this article we have just mentioned imported keys related to ODATA in ABAP. To learn OData in detail view our OData tutorial here.
Index
What is ODATA? Why we need it?
How to Create an ODATA Service?
Exploring ODATA
CRUD Operation via ODATA
Calling CLASS, FM in ODATA
Checking your Service: CRUD
Exploring ODATA
Data Model
Entity Types
Association
Entity Sets
Vocabularies
Service Implementation
Runtime Artifacts
Service Maintenance
What is ODATA
ODATA stands for Open Data.
It was created by Microsoft
Based on REST API.
Definition:
ODATA is the representation of Data in form of XML/JSON.
XML for ios based device, JSON for Android based device.
Why ODATA
To communicate between different Interfaces
How to create ODATA
Go to SEGW.
Create a new project
Import a DDIC Structure
Redefine the methods
Generate your ODATA
Register your Service
Data Model
A Data model can be anything : A table, A structure, A View.
When we import a DDIC structure, its Entity Types, Entity Sets, Service Implementation, Runtime Artifacts are created automatically.
A Data Model is the one that decides on which fields the CRUD operations will be performed
Runtime Artifacts
DPC& DPC_EXT
MPC & MPC_EXT
The mentioned above are four classes generated by SAP. We only redefine methods of EXT classes, because the codes written in DPC and MPC are provided by SAP, and will override our codes once ODATA is generated.
In DPC_EXT we perform CRUD operations
IN MPC_EXT we write annotations.
Annotations are the extra functionality we want to achieve that is not provided by SAP by default.
Operations in ODATA
CRUD Operation
Same codes that we write in ABAP report will be written here
Calling FM & Class
Same codes that we write in ABAP report will be written here
1.To read all files just open your entity and click GET and press Execute
2.To read one file -Write the primary keys in bracket just after the URI as mentioned here: (ACQ_ID=’NEW1′,BUKRS=’7070′).
3.To Create, you need to read one file. After reading, click USE AS REQUEST. Change the values of primary keys and other fields you want, click POST Radio Button, remove the Primary keys from URI and click Execute.
4.To Update Perform Step 02, Click Use as request, just change the fields other than primary keys, Click PUT Radio Button, and Execute.
5.To Delete, perform Step 02. Click Delete Radio Button, Execute.
Preface – This post is part of the ABAP Programs series.
TYPE-POOLS truxs.
PARAMETERS p_file TYPE rlgrap-filename.
TYPES : BEGIN OF t_tab,
workstream TYPE char50,
task TYPE zci_task,
task_type TYPE char50,
END OF t_tab.
DATA : t_upload1 TYPE STANDARD TABLE OF ZDEMO_TEST2,
wa_upload1 TYPE ZDEMO_TEST2.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
field_name = 'P_FILE'
IMPORTING
file_name = p_file.
START-OF-SELECTION.
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
EXPORTING
i_tab_raw_data = it_type
i_filename = p_file
TABLES
i_tab_converted_data = t_upload[]
EXCEPTIONS
conversion_failed = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 .
ENDIF.
CALL FUNCTION 'UPLOAD_XLS_FILE_2_ITAB'
EXPORTING
i_filename = p_file
tables
e_itab = t_upload1
EXCEPTIONS
FILE_ERROR = 1
OTHERS = 2
.
IF sy-subrc <> 0.
Implement suitable error handling here
ENDIF.
END-OF-SELECTION.
DATA : ls_cc_impl TYPE ZDEMO_TEST2,
lt_cc_impl TYPE STANDARD TABLE OF ZDEMO_TEST2.
LOOP AT t_upload1 INTO wa_upload1.
ls_cc_impl-mandt = sy-mandt.
ls_cc_impl-INCIDENT = wa_upload1-INCIDENT.
APPEND ls_cc_impl TO lt_cc_impl.
ENDLOOP.
MODIFY ZDEMO_TEST2 FROM TABLE lt_cc_impl.
CLASS cl_grand DEFINITION.
PUBLIC SECTION.
CLASS-DATA v_test TYPE char40.
CLASS-METHODS class_constructor.
METHODS constructor.
DATA a type i.
CLASS-DATA b TYPE i.
ENDCLASS. "cl_grand DEFINITION
*----------------------------------------------------------------------*
* CLASS cl_grand IMPLEMENTATION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
CLASS cl_grand IMPLEMENTATION.
METHOD class_constructor.
v_test = 'Static Constructor - Grand Parent'.
b = 30.
WRITE: /3 v_test.
ENDMETHOD. "class_constructor
METHOD constructor.
a = 30.
v_test = 'Instance Constructor - Grand Parent'.
WRITE: /3 v_test.
ENDMETHOD.
ENDCLASS. "cl_grand IMPLEMENTATION
*----------------------------------------------------------------------*
* CLASS cl_parent DEFINITION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
CLASS cl_parent DEFINITION INHERITING FROM cl_grand.
PUBLIC SECTION.
CLASS-METHODS class_constructor.
METHODS constructor.
ENDCLASS. "cl_parent DEFINITION
*----------------------------------------------------------------------*
* CLASS cl_parent IMPLEMENTATION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
CLASS cl_parent IMPLEMENTATION.
METHOD class_constructor.
v_test = 'Static Constructor - Parent'.
b = 20.
WRITE: /3 v_test.
ENDMETHOD. "class_constructor
METHOD constructor .
* data a type i.
super->constructor( ).
a = 20.
v_test = 'Instance Constructor -Parent'.
WRITE: /3 v_test.
ENDMETHOD.
ENDCLASS. "cl_parent IMPLEMENTATION
*----------------------------------------------------------------------*
* CLASS cl_child DEFINITION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
CLASS cl_child DEFINITION INHERITING FROM cl_parent.
PUBLIC SECTION.
CLASS-METHODS class_constructor.
METHODS constructor.
* DATA a.
ENDCLASS. "cl_child DEFINITION
*----------------------------------------------------------------------*
* CLASS cl_child IMPLEMENTATION
*----------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
CLASS cl_child IMPLEMENTATION.
METHOD class_constructor.
v_test = 'Static Constructor - Child'.
WRITE: /3 v_test.
b = 10.
ENDMETHOD. "class_constructor
METHOD constructor.
data a type i.
a = 10.
super->constructor( ).
v_test = 'Instance Constructor - Child'.
WRITE: /3 v_test.
ENDMETHOD.
ENDCLASS. "cl_child IMPLEMENTATION
START-OF-SELECTION.
DATA obj_child TYPE REF TO cl_child.
CREATE OBJECT obj_child.
data: a type i,
b type i.
a = obj_child->a.
write a.
write sy-uname.
delete from ztms_score .
delete from ztms_ans .
TYPES: BEGIN OF TY_DATA, "user defined type
ID TYPE N ,
NAME TYPE CHAR20,
SALARY TYPE I,
END OF TY_DATA.
DATA : ITAB TYPE TABLE OF TY_DATA. "internal table
DATA : WA TYPE TY_DATA. "work area
WA-ID = 1.
WA-NAME = 'Sapnuts'.
WA-SALARY = 5000.
COLLECT WA INTO ITAB. "collect
CLEAR WA.
WA-ID = 2.
WA-NAME = 'SAPabap'.
WA-SALARY = 50000.
COLLECT WA INTO ITAB. "collect
CLEAR WA.
WA-ID = 1.
WA-NAME = 'Sapnuts'.
WA-SALARY = 15000.
COLLECT WA INTO ITAB. "collect
CLEAR WA.
LOOP AT ITAB INTO WA.
WRITE:/ WA-ID, WA-NAME, WA-SALARY. "loop and display data
ENDLOOP.
**delete from ztms_score .
**delete from ztms_ans .
delete from ztms_user .
delete from ztms_set .
delete from ztms_ques .
Preface – This post is part of the ABAP Programs series.
CLASS a1 DEFINITION.
PUBLIC SECTION.
DATA: num1 TYPE i VALUE 100.
METHODS:m1.
ENDCLASS.
CLASS a1 IMPLEMENTATION.
METHOD m1.
WRITE: 'a1:',num1.
ENDMETHOD.
ENDCLASS.
CLASS b1 DEFINITION INHERITING FROM a1.
PUBLIC SECTION.
METHODS:m2, m1 REDEFINITION.
ENDCLASS.
CLASS b1 IMPLEMENTATION.
METHOD m1.
num1 = num1 .
WRITE: 'b1:',num1.
ENDMETHOD.
METHOD m2.
WRITE: 'M2 in class b1'.
ENDMETHOD.
ENDCLASS.
START-OF-SELECTION.
DATA: a TYPE REF TO a1.
DATA: b TYPE REF TO b1.
*data: c type REF TO c1.
****************************************************************
CREATE OBJECT b.
a = b. "upcasting
CALL METHOD a->m1( ).
*call METHOD a->m2( ). " we can't access the own sub class methods using super class ref.
NEW-LINE.
b ?= a. " down casting
CALL METHOD b->m1( ).
NEW-LINE.
CALL METHOD b->m2( ).
*****************************************************************
" error null ref
create OBJECT a.
b ?= a. "down casting still its giving dump
call METHOD b->m1( ).
*****************************************************************
CREATE OBJECT a.
TRY.
b ?= a. "u r attempted to use a 'NULL' object reference dump
CATCH cx_sy_move_cast_error.
CALL METHOD b->m1( ).
ENDTRY.
*****************************************************************
CREATE OBJECT a.
CREATE OBJECT b.
TRY.
b ?= a.
CATCH cx_sy_move_cast_error.
CALL METHOD b->m1( ).
call METHOD b->m2( ).
ENDTRY.
CLASS lcl_shape DEFINITION.
PUBLIC SECTION.
METHODS draw.
ENDCLASS.
CLASS lcl_circle DEFINITION INHERITING FROM lcl_shape.
PUBLIC SECTION.
METHODS: draw REDEFINITION,
calc_area.
ENDCLASS.
CLASS lcl_shape IMPLEMENTATION.
METHOD draw.
WRITE :/ 'Drawing any Shape'.
ENDMETHOD.
ENDCLASS.
CLASS lcl_circle IMPLEMENTATION.
METHOD draw.
WRITE :/ 'Drawing specific shape: Circle'.
ENDMETHOD.
METHOD calc_area.
WRITE :/ 'Area Of Crcle = 2iiR'.
ENDMETHOD.
ENDCLASS.
START-OF-SELECTION.
DATA : o_cir TYPE REF TO lcl_circle.
CREATE OBJECT o_cir.
CALL METHOD o_cir->draw( ). " calls subclass Draw() method
CALL METHOD o_cir->calc_area( ).
ULINE.
"--------- Narrow cast(Upcast)---------------"
DATA : o_shp TYPE REF TO lcl_shape.
o_shp = o_cir. " Narrow cast(Upcast)
CALL METHOD o_shp->draw( ). " calls sub class Draw() method
"call METHOD o_shp->calc_area( ) . " compilation error
ULINE.
"---------- Widening Cast(Downcast) -----------"
DATA : o_cir1 TYPE REF TO lcl_circle.
" o_cir1 = o_shp. " complilation error
o_cir1 ?= o_shp. " Widening Cast(Downcast)
CALL METHOD o_cir1->draw( ). " calls subclass Draw() method
CALL METHOD o_cir1->calc_area( ).
CLASS a1 DEFINITION.
PUBLIC SECTION.
DATA: num1 TYPE i VALUE 100.
METHODS:m1.
ENDCLASS.
CLASS a1 IMPLEMENTATION.
METHOD m1.
WRITE: 'a1:',num1.
ENDMETHOD.
ENDCLASS.
CLASS b1 DEFINITION INHERITING FROM a1.
PUBLIC SECTION.
METHODS:m2, m1 REDEFINITION.
ENDCLASS.
CLASS b1 IMPLEMENTATION.
METHOD m1.
num1 = num1 .
WRITE: 'b1:',num1.
ENDMETHOD.
METHOD m2.
WRITE: 'M2 in class b1'.
ENDMETHOD.
ENDCLASS.
START-OF-SELECTION.
DATA: parent TYPE REF TO a1.
DATA: child TYPE REF TO b1.
*data: c type REF TO c1.
****************************************************************
CREATE OBJECT child.
parent = child. "upcasting
CALL METHOD parent->m1( ).
CALL METHOD child->m1( ).
CALL METHOD child->m2( ).
*call METHOD a->m2( ). " we can't access the own sub class methods using super class ref.
NEW-LINE.
child ?= parent. " down casting
CALL METHOD child->m1( ).
NEW-LINE.
CALL METHOD child->m2( ).
******************************************************************
*" error null ref
*create OBJECT a.
*b ?= a. "down casting still its giving dump
*call METHOD b->m1( ).
******************************************************************
*
CREATE OBJECT a.
TRY.
b ?= a. "u r attempted to use a 'NULL' object reference dump
CATCH cx_sy_move_cast_error.
CALL METHOD b->m1( ).
ENDTRY.
******************************************************************
*
CREATE OBJECT a.
CREATE OBJECT b.
TRY.
b ?= a.
CATCH cx_sy_move_cast_error.
CALL METHOD b->m1( ).
call METHOD b->m2( ).
ENDTRY.
******** Unique Values******************
DATA : lv_string TYPE string,
lv_string2 TYPE string,
lv_string_final TYPE string.
TYPES: BEGIN OF ty_data,
auth TYPE c,
END OF ty_data.
DATA: ls_user TYPE ty_data,
ls_user2 TYPE ty_data,
lt_user2 TYPE TABLE OF ty_data,
lt_user TYPE TABLE OF ty_data.
lv_string = 'a,b,c,a'.
lv_string2 = 'd,b,c,a'.
SPLIT lv_string AT ',' INTO TABLE lt_user.
SPLIT lv_string2 AT ',' INTO TABLE lt_user2.
LOOP AT lt_user2 ASSIGNING FIELD-SYMBOL(<fs_field>).
INSERT <fs_field> INTO TABLE lt_user.
ENDLOOP.
SORT lt_user BY auth.
DELETE ADJACENT DUPLICATES FROM lt_user COMPARING auth.
IF sy-subrc = 0.
LOOP AT lt_user ASSIGNING FIELD-SYMBOL(<fs_user_table>).
IF lv_string_final IS INITIAL.
lv_string_final = <fs_user_table>-auth.
ELSE.
CONCATENATE lv_string_final <fs_user_table>-auth INTO lv_string_final SEPARATED BY ','.
ENDIF.
ENDLOOP.
ENDIF.
WRITE lv_string_final.
Preface – This post is part of the ABAP Programs series.
In ABAP, you might have learned to create global classes using SE24, Transaction code. But some time, there is a requirement to create a local class and its method call altogether in a report. In this article, we will learn how to implement Local Classes in ABAP.
Introduction
Local Classes in ABAP are just like classes of Programming language C/C++. We define following while doing Local classes implementation in ABAP:
Class: We define a class with different section: Public, Private and Protected
Method: We define Importing, Exporting and Exception parameters for a Method
Create Object: This we create for our Global classes too, used to create an object for a Class in our regular ABAP programs
CALL METHOD: To call the methods of class, using the object created above.
Local Class Implementation in ABAP – Image Illustration
ABAP Program
Program Requirement: Get basic and salary details of an employee from two different classes. Take Employee ID as input.
CLASS class_test DEFINITION DEFERRED.
PARAMETERS: p_empid TYPE char8.
DATA: wa_emp TYPE zBarry_emp,
wa_emp2 TYPE zBarry_sal.
DATA: obj TYPE REF TO class_test.
INTERFACE interface.
METHODS: method2
IMPORTING imp2 TYPE char8
EXPORTING exp2 TYPE zBarry_sal.
ENDINTERFACE.
CLASS class_test DEFINITION.
PUBLIC SECTION.
EVENTS: event1.
INTERFACES: interface.
METHODS: method1
IMPORTING imp TYPE char8
EXPORTING exp TYPE zBarry_emp.
METHODS: eventhandler FOR EVENT event1 OF class_test.
ENDCLASS.
CREATE OBJECT obj.
SET HANDLER obj->eventhandler FOR obj.
CALL METHOD obj->method1
EXPORTING
imp = p_empid
IMPORTING
exp = wa_emp.
CALL METHOD obj->interface~method2
EXPORTING
imp2 = p_empid
IMPORTING
exp2 = wa_emp2.
WRITE:/ wa_emp.
write:/ wa_emp2-empid, wa_emp2-tid,wa_emp2-mon.
*&---------------------------------------------------------------------*
*& Class (Implementation) class_test
*&---------------------------------------------------------------------*
* Text
*----------------------------------------------------------------------*
CLASS class_test IMPLEMENTATION.
METHOD method1.
SELECT * FROM zBarry_emp INTO exp WHERE empid = imp.
ENDSELECT.
IF sy-subrc NE 0.
RAISE EVENT event1 .
ENDIF.
ENDMETHOD.
METHOD interface~method2.
SELECT * FROM zBarry_sal INTO exp2 WHERE empid = imp2.
ENDSELECT.
ENDMETHOD.
METHOD eventhandler.
WRITE:/ 'wrong empid'.
ENDMETHOD.
ENDCLASS. "class_test
Code Explanation
In the above code, we have done following implementation, step by step:
Initially, we have defined Parameters to take Employee ID as input, variables to define work area to store data of Employee basic details and Salary details and object obj
Implementation of one local class and an interface.
Exporting Employee ID and getting relevant data from these classes/interface.
Preface – This post is part of the ABAP Programs series.
Lock Objects in SAP ABAP are global reusable component which generates function modules i.e. ENQUEUE_E_TABLE and DEQUEUE_E_TABLE that are used to set and release locks on data record. This Enqueue and Dequeue method is used to lock and unlock any object in SAP ABAP. In this article, we will learn these methods with the help of a program. Before starting this, you must read the basic concepts of Lock Objects in SAP ABAP.
Introduction
It is very important to lock an object that is under development. By object we mean everything i.e. Tables, Views, Reports, Methods, Function Modules, and all. ABAP too provides these features by default for their standard interfaces. But what if you need to create one for your own table. Then you need to use the given two Function Modules:
ENQUEUE_E_TABLE: To Add Lock
DEQUEUE_E_TABLE: To Remove Lock
Enqueue and Dequeue in ABAP- Image Illustration
ABAP Program to perform Enqueue and Dequeue Operations
DATA: varkey LIKE rstable-varkey.
varkey = sy-mandt.
CALL FUNCTION 'ENQUEUE_E_TABLE' "Add Lock
EXPORTING
* MODE_RSTABLE = 'E'
tabname = 'ZBarry_TEST'
varkey = varkey
* X_TABNAME = ' '
* X_VARKEY = ' '
* _SCOPE = '2'
* _WAIT = ' '
* _COLLECT = ' '
EXCEPTIONS
foreign_lock = 1
system_failure = 2
OTHERS = 3.
CASE sy-subrc.
WHEN 1.
MESSAGE i184(bctrain) WITH 'Foreign lock'.
WHEN 2.
MESSAGE i184(bctrain) WITH 'system failure'.
WHEN 0.
MESSAGE i184(bctrain) WITH 'success'.
WHEN OTHERS.
MESSAGE i184(bctrain) WITH 'others'.
ENDCASE.
CALL FUNCTION 'DEQUEUE_E_TABLE' "Remove Lock
EXPORTING
* MODE_RSTABLE = 'E'
tabname = 'ZBarry_TEST'
varkey = varkey
* X_TABNAME = ' '
* X_VARKEY = ' '
* _SCOPE = '3'
* _SYNCHRON = ' '
* _COLLECT = ' '
.
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.
Code Explanation
The above program is self explanatory, still we will explain key points below:
Initially, we have defined a variable varkey which will give the client information. It tells, ABAP, for which client, you want to block/unblock the table. It is taken automatically using sy-mandt.
Then we have called Function ‘ENQUEUE_E_TABLE’, it returns either either success, failure or Foreign lock exception.
Later, when we are done with our changes regarding our table, we need to unlock the same. For that we call Function ‘DEQUEUE_E_TABLE’.
Preface – This post is part of the ABAP Programs series.
Interactive Report in SAP ABAP is a report where you can interact with the output page of report. You can click on an item of a list to get its details. In this article, we will discuss an example of Interactive Reports. To know more about Events in Interactive Report click here. Do check Interactive Reporting – FAQs for more clarification.
Introduction
ABAP report has more often a requirement to display expandable lists.
For example, On first page you have been provided basic details of employees.
Report – Page 1 Illustration
On click of a line item i.e. Employee ID (Here, we have clicked, 1117582), you are navigated to another page where you can see the employee Annual Salary.
Report – Page 2 Image Illustration
If you still want to know further, you again clicked on Employee ID(Here, we have clicked, 1117582) here and now you are navigated to third page where you see employee’s salary structure.
Report Page 3 – Image Illustration
These all things are possible in SAP ABAP using Interactive Reports.
ABAP Interactive Report Program
Program Requirement: Create an ABAP report to take Employee ID as Input and display basic details i.e. Employee ID, First Name and Last Name on First page (list 0). On click of Employee ID, display employee salary details on list 1. Again on click of Employee ID, display address details on list 2.
TABLES zBarry_emp.
TABLES zBarry_sal.
DATA : it_emp1 TYPE TABLE OF zBarry_emp,
it_emp2 TYPE TABLE OF zBarry_sal,
wa_emp TYPE zBarry_emp,
wa_emp2 TYPE zBarry_sal,
it_emp3 TYPE TABLE OF zBarry_add,
wa_emp3 TYPE zBarry_add,
fnam TYPE char20,
fval TYPE INT4,
fnam1 TYPE char20,
fval1 TYPE INT4.
set PF-STATUS 'PFSTATUS'.
SELECT-OPTIONS : p_empid FOR zBarry_emp-empid.
AT USER-COMMAND.
CASE SY-UCOMM.
WHEN 'MAIN'.
sy-lsind = 1.
PERFORM display_data.
ENDCASE.
AT SELECTION-SCREEN.
PERFORM validate_input.
START-OF-SELECTION.
PERFORM get_data.
PERFORM display_data.
TOP-OF-PAGE.
FORMAT COLOR COL_HEADING INVERSE.
WRITE 'BASIC EMPLOYEE DETAILS'.
TOP-OF-PAGE DURING LINE-SELECTION.
IF sy-lsind = 1.
FORMAT COLOR COL_HEADING INVERSE.
WRITE 'EMPLOYEE SALARY DETAILS'.
ELSEIF sy-lsind = 2.
FORMAT COLOR COL_HEADING INVERSE.
WRITE 'EMPLOYEE ADDRESS DETAILS'.
ENDIF.
AT LINE-SELECTION.
PERFORM primary_list.
PERFORM secondary_list.
*&---------------------------------------------------------------------*
*& Form VALIDATE_INPUT
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM validate_input . "validating input
IF p_empid IS INITIAL.
MESSAGE 'Please Enter Employee Number' TYPE 'E'. "if the employee id field is left blank
ELSE.
SELECT empid FROM zBarry_emp INTO TABLE it_emp1 WHERE empid IN p_empid.
IF sy-subrc <> 0.
MESSAGE 'Please Enter Correct Employee Number' TYPE 'E'. "if wrong employee id is entered
ENDIF.
ENDIF.
ENDFORM.
*&---------------------------------------------------------------------*
*& Form GET_DATA
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM get_data . "fetching basic employee details from table
SELECT * FROM zBarry_emp INTO TABLE it_emp1 WHERE empid IN p_empid.
ENDFORM.
*&---------------------------------------------------------------------*
*& Form DISPLAY_DATA
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM display_data . "displaying data
FORMAT COLOR COL_NEGATIVE INVERSE.
WRITE:/,3 'Employee ID',
20 'First NAME',
35 'Last NAME'.
SKIP.
LOOP AT it_emp1 INTO wa_emp.
FORMAT COLOR COL_POSITIVE INVERSE.
WRITE : /3 wa_emp-empid,20 wa_emp-emp_fname,35 wa_emp-emp_lname.
ENDLOOP.
ENDFORM.
*&---------------------------------------------------------------------*
*& Form PRIMARY_LIST
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM primary_list . "fetching employee salary details on list 1
IF sy-lsind = 1.
GET CURSOR FIELD fnam VALUE fval.
IF fnam = 'WA_EMP-EMPID'. "if employee id is selected
SELECT * FROM zBarry_sal INTO TABLE it_emp2 WHERE empid = fval .
FORMAT COLOR COL_NEGATIVE INVERSE.
WRITE:/,3 'Employee ID',
20 'Transaction ID',
35 'Month',
55 'Date Of Salary'.
SKIP.
LOOP AT it_emp2 INTO wa_emp2.
FORMAT COLOR COL_POSITIVE INVERSE.
WRITE : /3 wa_emp2-empid,20 wa_emp2-tid,35 wa_emp2-mon,55 wa_emp2-dos.
ENDLOOP.
ENDIF.
IF fnam = 'WA_EMP-EMP_FNAME'. "if employee name is selected
WRITE: / 'name'.
ENDIF.
ENDIF.
ENDFORM.
*&---------------------------------------------------------------------*
*& Form SECONDARY_LIST
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM secondary_list . "fetching employee address details on list 2
IF sy-lsind = 2.
GET CURSOR FIELD fnam1 VALUE fval1.
IF fnam = 'WA_EMP-EMPID'. "if employee id is selected
SELECT * FROM zBarry_add INTO TABLE it_emp3 WHERE empid = fval1 .
FORMAT COLOR COL_NEGATIVE INVERSE.
WRITE:/,3 'Employee ID',
20 'Flat No.',
35 'Street Name',
55 'City Name'.
SKIP.
LOOP AT it_emp3 INTO wa_emp3.
FORMAT COLOR COL_POSITIVE INVERSE.
WRITE : /3 wa_emp3-empid,20 wa_emp3-flat_no,35 wa_emp3-street_name,55 wa_emp3-city_name.
ENDLOOP.
ENDIF.
ENDIF.
ENDFORM.
Important Points to Consider
The fields fval and fval1 will hold the value of field that you will double click. In our usecase, we store Employee ID in it and use the same to fetch data from table, hence its field type is similar to the Emp ID, i.e. INT4 .
Also, You need to double click on set PF-STATUS ‘PFSTATUS’.
And enter the following as shown below:
If F2 value is not set as ‘PICK’ as shown above then it will cause issue and you will wonder why double click is not working for ABAP Interactive report.
Code Explanation
In the program mentioned above, we have discussed Interactive operation in ABAP Report. This program has comments wherever required. Still, we will be explaining the key points of this program. This program utilizes ABAP Interactive Events, do read it here, before proceeding.
Initially, we have defined Parameters to take Employee ID as input, variables to perform query and have set PF-STATUS as ‘PFSTATUS’. This PF Status is used to display standard Menu buttons on the top i.e. Execute, Close, Back, etc
Forms/Performs : Here we have written following forms as per the requirement:
validate_input: Here we check if the employee id field is left blank or if wrong employee id is entered. In both cases we raise error
get_data: Here we are fetching basic employee details from table
display_data: Here we are displaying data (list 0)
primary_list: Here we are fetching employee salary details on list 1
secondary_list: Here we are fetching employee address details on list 2
Output
Screen 1:
Screen 2:
Screen 3:
Tutorial Video
You can watch the below video to learn implementation:
