Exception Class in Object Oriented Programming

 

  • Exception is a problem that arises during execution of the program.
  • The purpose of exception class is to raise and handle the exception.
  • We use try block to raise a exception and catch block to handle a exception.
  • The exception class name must start with CX.
  • CX_ROOT is the global class ( parent class ) for all the exceptions.

  • There are 3 subclasses of parent class CX_ROOT.

    1. CX_STATIC_CHECK :- It is checked by both the compiler and runtime system.
    2. CX_DYNAMIC_CHECK :- It is checked only at runtime system.
    3. CX_NO_CHECK :- It is not checked either during compile time and runtime.


Note :-

  • While creating the exception class, system by default provides CX_STATIC_CHECK as the super class.

Ways to Create Exception Class :-

  • There are 2 ways to create the exception class.
    1. Exception class with messages of message class.
    2. Exception class without messages of message class.

Creating Exception Class without using messages :-

  • Step 1 :- Go to transaction code SE24.

  • Step 2 :- Give a name for your exception class.



  • Step 3 :- Click on create button.

  • As soon as you will click on create button, SAP will automatically provide CX_STATIC_CHECK as the superclass for our exception class.



    • Give short description and enable checkboxes according to your need.
    • Click on save button and assign packages and transport requests.
    • Many attributes from super class will be inherited automatically.

  • Step 4 :- In texts tab we will be proving a exception id.



  • Step 5 :- Open the attributes tab, you will find a constant attribute declared automatically.



    • Save and activate the class.

How to check this Class?

  • We have a function module SOTR_GET_TEXT_KEY.
  • Execute this Function module from SE37 and provide the initial value of above constant attribute.


  • Press F8.


  • We will see more features of exception class in next part.

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