The Form debugging has some challenges , like - the form has no versions,there is no message display when exceptions occur and ABAPcode is usually embedded in the specific,program line node.The following steps for debugging a smartform may be helpful:-
Since , whenever a form is activated a Function Module is generated, we can go directly to the FM and insert break-points; as,
All the performs (ABAP Form routines) are included in the *F01 Include
FORM %GLOBAL_INIT, within the Include *F01
FORM %WRITE_TEXT_MODULE FORM %WRITE_INCLUDE_TEXT FORM %WRITE_DYNAMIC_TEXT FORM %RAISE
For each Window/Node that has been created within the form an equivalent Form(ABAP Form Routine) is created in the *F01 Include:-
Like for e.g. for the Node 'Main' Window,following Include is created:
The Form Raise, as specified above, is particularly useful whenever, we see that there is no print-preview appearing , when executing the driver program.This means that exception has occured and that can only be traced, if we set a breakpoint in the FORM routine 'Raise'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
3 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |