F110 break point is not triggered.

[Former Member]

Hi all,

I have implement the enhancement with break-point in each FM.

RFFOX101

RFFOX102

RFFOX103

RFFOX104

in T-code: CMOD  and also activated.

In FBZP i have check  the radio butt Use classic payment medium programs (RFFO*) and assigned RFFOUS_T  in the program.

But when i run f110, it doesn't stop at any of the user exit.

Regards,

Shegar.

[pramodrepaka]

This message was moderated.

[Former Member]

Hi Pramod,

I tried the link which you mentioned, the debugger is activated but not at

RFFOX101

RFFOX102

RFFOX103

RFFOX104

My requirement is when i run f110, mail to should got to vendorl

Kindly advice me what to do.

[pramodrepaka]

Hi Rohini,

              Try to activate each components of your enhancements and recheck.

[nabheetscn]

The reason is these programs are executed in background. One option is you can make the prooposal then run it via SE38.

Nabheet

[Former Member]

Hi Nabheet,

I tried executing RFFOUS_T from T-code: se38, with the necessary parameters.

But it gives me the following error "Program RFFOUS_T: No records selected"

Regards,

Shegar.

[nabheetscn]

It will select the record if payment has not been done via F110. Do one thing in your exit code an infinite loop. Then execute F110. You see this exit getting run in SM50. You can debug it via SM50

[Former Member]

Hi Nabheet,

I tried the procedure which you told me,but it is not stopping at the user-exit which i have mentioned.

Rohini.

[former_member386202]

Hi,

It process in background so will not directly stop.

Put endless loop in ur exit and run F110 and then go to tcode SM50 and debug ur process.

Regards,

Prashant

[Former Member]

I tried it but no luck.

My requirement is whenever we run F110, we need mail to trigger to the Vendor.

Regards,

Shegar.

[Former Member]

this is a requirement you can fulfil via a FIBF solution

please refer to process 00002040 - Autom. pmnt transactns: Output of pmnt advice note

you will need to create and activate the process in the FIBF config

ensure you have emails setup on your vendor accounts

when you do your payment runs your vendors should get a print

see the sample paramters from my code for the same solution

....

function zfi_paymentadvice .

*"----------------------------------------------------------------------

*"*"Local Interface:

*"  IMPORTING

*"     VALUE(I_REGUH) LIKE  REGUH STRUCTURE  REGUH

*"  TABLES

*"      T_FIMSG STRUCTURE  FIMSG

*"  CHANGING

*"     VALUE(C_FINAA) LIKE  FINAA STRUCTURE  FINAA

*"--------------------------------------------------------------

[Former Member]

But they want mail with excel sheet as attachment and the attachment should have some format

[Former Member]

...more development for you to do enjoi!

[Former Member]

Hi Steve,

Yes i know but i want to find the break-point were i can write the code.

In the program RFFOUS_T

Rohini

[Former Member]

You need an example PR with a test vendor (use your email) and do the payment run.

Did you look at the FIBF 'user exit' working that will email you - so you can see what you get etc.

You can re-run background jobs that you have scheduled by selecting in SM37 listing it and using the OK_CODE  'JDBG' this will allow you to debug the same finished background job as many times as you like, over and over again. very handy and is a good alternative to the endloos loops, especially if you debugging in a production environment so you dont transport or want to avoid opening up std code etc

[Former Member]

Hi Steve,

I tried with t-code: SM37 and JBDG its debugging but not in the FM or the user exit which we wrote.

Regards,

shegar.

[Former Member]

Sorry, this is a local issue you will need to persevere with. I assume the exits are active and in the client you are testing...are you sure these exits are:

a. fit for your purpose

b. would be hit in the what you are testing i.e. you are not too early or late for the actual invocation of them?

are you able to intercept with an endloos loop...via SM50 debug just to see that a hit is made in and around the exit? can you backtrack from the customer_fucntion exit call in the source to the standard code and see if the exit is bypassed by some logical condition?