10-21-2015 7:27 AM
10-21-2015 8:53 AM
To debug you must first create and activate an implementation and set the break-point in the method of the implementing class.
Hint: Execute OPP1 to get list and documentation of available BAdI.
Regards,
Raymond
10-21-2015 8:56 AM
Hi Raymond,
Thanks for the reply.
I have created and activated a ZBADI for MD_PURREQ_CHANGE and put a break-point inside the method. But when I tried to execute MD15. It does not stop on the break-point.
10-21-2015 10:18 AM
You could also set break-point in the caller (execute a where-used search on interfac method, e.g. forms purreq_change_before_save and purreq_post_after_save of include LM61PBAD)
But first activate debug in update task.
Regards,
Raymond
10-21-2015 11:41 AM
Hello
This is the correct BAdI to be used on transaction MD15.
Sometime the BAdI is called in update mode (background), therefore, your break-point will not be called.
You can try another method to check if the BAdI is called, such as saving a value on a custom table or you can try to activate update debugging on the debugger, so that you can debug the update process.
BR
Caetano
10-21-2015 9:15 AM
Hi,
I have tried to put a code inside the method CHANGE_BEFORE_SAVE_CONV to update the created PR.
I have succesfully update the PR during creation. But I still wonder howcom my breakpoint does not execute or do not stop in that line.