Verifying Function Module Call during a transaction – Step by Step Method
If you already know (or suspect) that a certain function module is triggered from a SAP transaction, then you can verify this by one of the two ways:
First Method: Direct put a breakpoint in the function module (top most executable line). Note – Data declaration is not an executable line. So in this example, lets put a breakpoint in FM – BAPI_SALESDOCUMENT_CHANGE
Now, if any SAP transaction is executed which calls this FM, the debugger will stop and you know for sure whether the FM is called or not. You can also check the values from the stack.
Method 2: Go to debug mode by typing /H on the command prompt and pressing enter.
After pressing the enter, you should see a success message at the bottom of the screen.
Now go to the top menu – Breakpoints >> Breakpoint at >> Breakpoint at Function Module. Now enter the function module name here.
Now press enter or green tick mark. The breakpoint is set. Execute the transaction and processing will stop for all occurrence of the FM call.
Thus you can verify the call of the FM in a particular transaction. Sometime, the transaction may be triggering in update task then the breakpoint method will not work but those cases are rare. You can also check what the are input parameters to this Function call.
