Need authoritative (SAP?) answer on BADI breakpoints in update debugging

Question

I'm doing a very simple BADI implementation of:
IF_EX_INSPECTIONLOT_UPDATE~CREATE_IN_UPDATE
called from FM QPBU_LOT_INSERT in QPBU.
Everything is working fine, but here's the problem
QPBU_LOT_INSERT is being called from an update task inside MIGO (the update task for a goods receipt posting.)
When I was doing a customer exit in MIGO, I had to turn on an update debugging session to see a breakpoint in my exit code - the debugger would not go directly to the hard breakpoint in my exit code.
So I assume this is the same for implementations of BADI methods - the regular debugger will NOT go directly to a breakpoint inside the custom implementation of the interface method - you have to turn on update debugging and wait for your method code to appear.
Is this true or not? 
If it is, then this seems to me something that would be easy to fix.
After all, if we can have external debugging in WDA, why can't the ABAP debugger be fixed to see a hard breakpoint even if the breakpoint is in customer code that is part of a BADI implememntation method ??????
Thanks for whatever authoritative answer anyone can provide.
djh

Answer 1

hi David,
As you said, normal debugging will not always be possible with BAdIs. i dont know about activating update debugging, but there is a way to go to debugger while the BAdI gets executed. Please follow the steps mentioned below:
step1: Goto sE19 and enter the BAPI implementation name->display
step2: choose the interface tab->double click on the method which
is under consideration
step3: code as below
data lv_flag.
        while flag is initial.
         endwhile.
step4: Now activate the BAdI and execute the transaction, and do the necessary actions(save/delete etc)
step5: goto transaction sm50->you can see your program there
step6: select your program from the list->choose PROGRAM/SESSION from the
menu->Select PROGRAM->DEBUGGING
you are now in the debugger with the BAdI.
<b>
This is an infinite loop inside the BAdI; You should take this out, and re-activate the BAdI, once you are done with the debugging</b>
Hope this helps,
Sajan Joseph.