Introduction

Explanation

After the Control Framework has transferred the methods via Remote Function Call (RFC) to the SAPGUI, they are executed one after the other. If a method causes a runtime error on the frontend, method processing terminates. This means that both the method that caused the error and all subsequent methods stop executing.

From the backend point of view, an error does not occur until the FLUSH method is called since the control methods are only buffered but not executed before.

Conclusion

If a flush call triggers an exception, it is not yet obvious which method in the Automation Queue caused the error. This is why you cannot catch these runtime errors dynamically and respond to them. At flush time, you only know that an error has occurred, but not where it occurred.