Recently I designed a code in customer exit mb_cf0001 to capture some info from material docs in to a custom table. I set a breakpoint in the code and omg! Debugger does not stop. After playing around a little bit, I found that this exit is taken in the update task. As it is very sensitive place (also very dangerous), the debugger stops here only if the update debugger option is on. This can be set from the debugger screen. How? Easy. Enter /h in the command window, to bringup the debugger screen. From settings menu this option can be set. Noooo still the breakpoints are not active. I do not know why? But that is what happens. The debugger stops at the first line of code in the update task. The breakpoints that were set in abap editor before executing this tcode do not work. To work round this issue, this is what I did. I created a breakpoint from the debugger to the fm. I thought I was stupid not to know this after so many years experience in sap. I was not alone. So this is for t...
This blog gives some very useful articles on SAP process, mapping business processes to SAP, simple tricks, development using ABAP and BADI, smartforms. Specific topics can be requested by posting a comment.