Function Module Exception Handling
Exception handling is the integral part of the designing the application. By raising the exception, we are providing the oppertunity to the Caller program to handle the exception in its own way. Visit Raising & Handling Non-class based exceptions to learn more on exception handling and flow control with flow-chart. Checkout all post related to…
Raising & Handling Non-class based exceptions – I
Exceptions are way to communicate effectiently to the caller about something went wrong. So, the caller of the FM or method, would process them accordingly. Checkout all post related to Exception Raising & handling:
Raising & Handling Non-class based exceptions – II
In continuation to previous post on Raising & Handling Non-class based exceptions, lets see the message addition RAISING along with the overall flow control. Checkout all post related to Exception Raising & handling: Message RAISING When we raise the exception by statement RAISE, it doesn’t provide us the default details. If we are interested in…
Class-based Exceptions I – Basics
Class based exceptions are realized based on the instances of the exception class. Lets explore them.
Class-based Exceptions II – Design Time consideration
In the series of the Class-Based exception raising & handling exceptions, today we’ll see design time considerations. Checkout all post related to Exception Raising & handling: Main classes All Exception classes are inherited from the global exception class’s CX_ROOT these subclasses: CX_STATIC_CHECK – If the exception is defined as a subclass of CX_STATIC_CHECK, it has…
Class based Exceptions III – Runtime flow
Lets continue exploring more about Class based exceptions by checking out the runtime flow when an exception is being raised. Checkout all post related to Exception Raising & handling: Flow .. with code lines To understand it better we’ll use the demo example of Class-based Exceptions I – Basics. I have given the related code…
Class based Exceptions IV – CLEANUP
In the series of Class based Exceptions, lets check out the addition CLEANUP within the TRY..ENDTRY block. Checkout all post related to Exception Raising & handling: TRY .. ENDTRY block also should have a CLEANUP block. This code block should contain cleaning up activity before leaving the TRY .. ENDTRY block. This block would gets…
Exception class to use Messages from T100
Exception class can be defined using to use static Text as well as the messages from the Message repository maintained using transaction SE91. In this article, lets see how to use the message from Message repository T100.
Why NOT to have a wrapper around Exception (RAISE) ?
Class based exception are more powerful compared to the “legacy” exceptions. But you don’t want to create wrapper around the Exceptions?