The document provides instructions for using SAP's DBUG command to debug mass transactions and determine the relevant FQ events. Users can enter "/h" at the command field to launch a debugger session, set a breakpoint on FM "FKK_FUNC_MODULE_DETERMINE", and continue debugging to stop at that FM, where the I_FBEVE parameter will show the FQ event number and T_FBSTAB will list follow-up FMs called under that event.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
496 views
DBUG Tcode and ISU Debug
The document provides instructions for using SAP's DBUG command to debug mass transactions and determine the relevant FQ events. Users can enter "/h" at the command field to launch a debugger session, set a breakpoint on FM "FKK_FUNC_MODULE_DETERMINE", and continue debugging to stop at that FM, where the I_FBEVE parameter will show the FQ event number and T_FBSTAB will list follow-up FMs called under that event.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3
SAP has a reserve command DBUG for you to
debug mass activity transactions such as FPVA
(Dunning Proposal). Once you enter DBUG at command field and hit return key.
You will see this Pop Up Message.
In SAP IS-U, most of the FICA and Billing
related enhancements are using FQ-Events. To debug/ find out what FQ Events to use for certain transaction, use the following steps: 1. In command field, enter /h
2. When Debugger Controls Session is
launched, set break point for FM 'FKK_FUNC_MODULE_DETERMINE '.
3. Continue and Debugger will stop at
FM 'FKK_FUNC_MODULE_DETERMINE '.
4. I_FBEVE is the FQ Event Number, and at the
end of this FM, T_FBSTAB will contains all the FMs that will be called under this event. You can get more information of this event via command FQEVENTS.