‎2012 Feb 06 2:34 PM
Hello friends,
I've searched the forum on how to implement this BTE to send dunning letters thru email with transaction F150 and i have followed all the steps, but can't get it stop at the breakpoint im setting.
These are the steps i've followed:
1. Added a new product on transaction FIBF (Settings/Products/of a customer) and activated it.
2. Added the new product created on step 1 on (Settings/Process Modules/of a customer) under the process 00001040.
3. Copied the FM SAMPLE_PROCESS_00001040 into a Z one and added the following code:
BREAK-POINT.
c_finaa-nacha = 'I'.
c_finaa-intad = EMAIL.
I think these steps are all i need to do for it to work, but as i run the F150 its not stopping on the break-point.
Any suggestions will be really appreciated.
Regards,
Roberto
‎2012 Feb 06 3:17 PM
Hi Roberto,
1) First make sure the event interface process 1040 is being called. Put break-point in the function PC_FUNCTION_FIND and confirm the field I_PROCS.
2) If you are calling the event, make sure the process is not "in update task". Check the "update debugging" in the debugger or if you prefer you can also use for this transaction SRDEBUG activating your function Z.
Regards
Bruno Xavier.
‎2012 Feb 06 3:17 PM
Hi Roberto,
1) First make sure the event interface process 1040 is being called. Put break-point in the function PC_FUNCTION_FIND and confirm the field I_PROCS.
2) If you are calling the event, make sure the process is not "in update task". Check the "update debugging" in the debugger or if you prefer you can also use for this transaction SRDEBUG activating your function Z.
Regards
Bruno Xavier.
‎2012 Feb 06 3:51 PM
Hello Bruno,
I checked as you said on FM PC_FUNCTION_FIND and the process 1040 is not being called. There are other two that are being called: 1051 and 1060.
Any ideas why this is happening?
I dont understand number 2.
Regards,
Roberto
‎2012 Feb 06 3:52 PM
Hi Roberto,
See SAP Note 156985 - Reference Note: BTE for dunning. It says in point 5 (test the program)
c) The test in debugging cannot be carried out via Transaction F150
because a background job is always triggered here. Instead, after
maintaining the parameters start the report SAPF150S2 via
Transaction SE38 (or SA38).
I hope this helps you
Regards
Eduardo