01-21-2019 1:31 PM
Hi All,
I am trying to stop the creation of output messages when the user modifies a custom PO
I created a VOFM routine, application EF, with number 902. Activated it. Checked table TFRM to make sure it is active.
But when I put a breakpoint there, the code execution doesnot seem to pass from that part. Breakpoints do not get hit.
Any ideas as to what might be happening?
01-21-2019 1:46 PM
Please check whether your output has been regenerated while processing the transaction code for ME22N!
Thanks,
01-21-2019 2:40 PM
01-21-2019 5:45 PM
Just goto ME22N, click on message here check if your message output has been done, then system should not allow you to make changes!
Thanks,
01-21-2019 9:39 PM
01-21-2019 9:46 PM
RV80HGEN being only needed in target system right after routines have been transported. Otherwise the ABAP code is not regenerated and is unchanged.
01-22-2019 9:19 AM
01-21-2019 9:48 PM
The VOFM routines are often called from within the update task, so you must switch on the "update debug" mode (cf procedure here: https://archive.sap.com/discussions/thread/1586576)
01-22-2019 9:24 AM
I did
FORM KOBED_902.
BREAK-POINT 'myusername'.
ENDFORM.
FORM KOBEV_902.
BREAK-POINT 'myusername'.
ENDFORM.
used /h in the tcode text field to activate the debugger
when I got into debugging, I went into settings==> change debugger profile/settings and checked update debugging
still it is not stopping at my routine
01-22-2019 9:56 AM
Could you run an ABAP trace to make sure this form is called? (or MESSAGE ... TYPE 'X' to make it short dump, check ST22 afterwhile)
(PS: it's either the macro BREAK 'myusername', or BREAK-POINT alone)
01-22-2019 3:52 AM
Mike,
Refer to my reply in the below mentioned thread...
https://archive.sap.com/discussions/thread/3518177
K.Kiran.