cancel
Showing results for 
Search instead for 
Did you mean: 

Debug FI-CA Check

aidaj_hilton
Participant
0 Kudos

Can anyone help me to debug the FI-CA check developed in PWB.

I am trying to debug the printing of the check through the payment run. I enter <b>dbug</b> in the transaction code field to debug the payment run which successfully activates the debugger. However, although I have put breakpoints in the PWB user exits and in event 724 and 725 and activated the debugger for the SAPscript, the program does not stop at any of ehse breakpoints.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Jill,

I had the same problem and solved it by buidling an endless loop into the exit. (of the application form or any FICA event). The loop is only triggered if a parameter is set. You need to add the parameter to table TPARA end, then you can transport it to your test system. By doing so you can now debug the background proces, but only if you have set the parameter in your user settings. After starting the printrun (FPCOPRA), go to SM50, select your running process and start the debugger from there.

DATA: X TYPE N.

GET PARAMETER FIELD LB_DEBUG_LOOP ID 'ZEND_LOOP'.

IF LB_DEBUG_LOOP = 'X'.

WHILE X = 0.

ENDWHILE.

Btw don't forget to make sure that your events are active (see FQEVENTS) in the client your testing in.

You can use this trick to debug any background job in FICA (or anywhere in SAP).

Hope this helps, if so don't forget to reward some points.

Regards,

Hans van der Kooij

Uphantis

aidaj_hilton
Participant
0 Kudos

Thank you so much for your help Hans

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Jill,

Look at the trace whether the sapscript is called or not.

Activate the trace using ST05 and then analyse it.

Regards,

Atish

aidaj_hilton
Participant
0 Kudos

Hi Atish,

The SAPscript is called. I am able to print the check. It is just that one of the variables does not print and I wanted to be able to break at the point where I populate this variable and see why it does not retain the value.

Thanks,

Jill

Former Member
0 Kudos

Hi Jill,

If you know the variable name and the program then create a watchpoint while debugging.

Regards,

Atish

aidaj_hilton
Participant
0 Kudos

Thanks Atish. Like I said, the program is not stopping at any of my breakpoints. If it did then I would be able to create watchpoints etc. My problem may be that I have to create an online check to allow me to debug. Unfortunately this is not configured here. I need to do a payment run. Thanks again.

Jill