ABAP Tutorials, Guides, Training, Manuals
ABAP programs are checked statically when they are created and dynamically when they are running. Error states, which are not statically predictable and only occur at runtime are dynamically identified by the ABAP runtime environment. States of this type lead to exceptions. If an exception is not handled or cannot be handled, a runtime error occurs.
Try to remove all but one marble from the board. You can remove a marble by skipping over it to an empty spot. Select a marble by clicking on it and move it by selecting the spot that you want to move to.
Marble Game
As an ABAPer, you probably know how combursome it is to work with classical exceptions (discussed in last post), since you must handle all of them immediately after a function or method call. Beside being labourious, these mappings clutter our code and make it difficult to read.
SAP also have Object Oriented Class based exceptions which are easy to handle and less cumbersome.
Normally, if any exception occurred it will go to dump immediately in a program, then we will process this through the tcode ST22(dump analysis). This code comes handy when the behaviour of function module is not predictable.
Explicit Error Handling
We will convert the dump into an error message (like in above snap) or some text statement. For this we need to call this statement
RECEIVE RESULTS FROM FUNCTION ‘function module’
Image display (using OAER)
