Skip to Content
0

How to Debug std RFFOUS_C report during payment run F110?

Mar 06 at 07:47 PM

61

avatar image
Former Member

Hi Experts,

I have an requirement for which i have customized RFFOUS_C report to Z, and now i am modifying the code based on my requirement, but the issue here is i am unable to debug the program during payment run method using F110. Basically i am in need to debug and understand the control flow of the RFFOUS_C program, so that i can modify code accordingly.

below are the ways i have tried to debug,

1. Using session break points,

2. Using external break points

3. Writing BREAK-POINT explicitly in code

4. Break point using Menu baar SYSTEM-->UTILITIES-->DEBUG ABAP.

none of the above allows me to debug the RFFOUS_C report.

Can anyone suggest me how to debug the same during payment run ?

Thanks in Advance.

Thanveer

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Ramesh Babu Srikakollu Mar 07 at 12:19 AM
1

Hello Thanveer,

We also had the similar issue, tried different ways to debug but no success. We found an option to debug and might not be the right one, but it helped us.

Requested functional consultant to perform the payment proposal run through F110 and complete the steps till it reaches to print the checks and stop there. Executed this program RFFOUS_C thru SE38 and selected the variant that is used by F110 payment run and debugged.

Regards,

Ramesh

Share
10 |10000 characters needed characters left characters exceeded
Wenceslaus Gnana Mar 07 at 03:30 AM
1

F110 submits RFFOUS_C in a background job. That's why the breakpoints won't work.

As Ramesh mentioned you can run RFFOUS_C in SE38 with the variant.


Share
10 |10000 characters needed characters left characters exceeded
Mauricio Reinheimer
5 days ago
0

Hello Thanveer,

As mentioned by Wenceslaus, RFFOUS_C is submitted as a background job. In order to debug a background job, you can check SAP Note 573128 - 'Debugging programs in the background'.

The easiest way is to open SM37, select the finished job and run 'JDBG' in the transaction field. This will prompt to debug the finished job.

Regards,

Maurício

Share
10 |10000 characters needed characters left characters exceeded