A success message will confirm that break point is set. Step 5 – In the pop up screen, enter “call function” and click on the green check. Step 3 – From the top menu in the debugger screen, navigate to Breakpoints > Breakpoint at > Breakpoint at Statement. In the command window, write /H and press enter.Īfter pressing the enter, you should see a success message at the bottom of the screen. Step 2 – Go to the transaction execute until the last step where the logic triggers. Step 1 – Execute the transaction until the last possible point you know for certain that (standard) logic has not triggered. Strap on you seat belt, it is going to be a wild ride. A quick google search may give you some options. A common requirement in custom report is to replicate the logic of standard transaction and we need function module (or BAPI) for that. Many functional consultants are in the business long enough to know the common BAPI and function modules, but no one can know it all.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |