‎2008 Apr 20 11:01 AM
‎2008 Apr 20 5:31 PM
Hi Ashish,
The code which is written in the function module can not be debugged . But u can do one thing to know whether it is being triggered or not.. Just write one statement for messages.
like
You can come to know that whether cursor is coming there or not .
I hope that it helps u .
Regards,
Venkat.O
MESSAGE w027(ZMSGCUSTOME) with 'It is being triggered'.
‎2008 Apr 20 11:06 AM
Hi Ashish,
General debugger statements
BREAK USERNAME.
BREAK-POINT.
will work in the field exit but you will have to place them in the function module for that field exit...
You can also place manual break points for the session by using the break point button but in the function module for that field exit
Regards
Byju
‎2008 Apr 20 4:34 PM
Hi,
No. Field exits must be tested separately in the ABAP/4 Development Workbench. For errors which only occur in the screen environment, it is helpful to write interesting variable to the file system using TRANSFER... . These can then be analysed there.
Reward if helpful...
Cheers,
Sowjanya.
‎2008 Apr 20 5:31 PM
Hi Ashish,
The code which is written in the function module can not be debugged . But u can do one thing to know whether it is being triggered or not.. Just write one statement for messages.
like
You can come to know that whether cursor is coming there or not .
I hope that it helps u .
Regards,
Venkat.O
MESSAGE w027(ZMSGCUSTOME) with 'It is being triggered'.