User Exit module in DMEE

[Former Member]

Hi Experts,

I have created a user exit by name ZDMEE_EXIT_ACCNUMBER in a package ZDMEE for a customized DME tree. Now I want to debug the source code of the FM when I run F110. I found some posts on this issue, but still I am unable to solve the problem.

Can any one please advice how to debug the FM usinf F110, Is there any special procedure to do this?

Thanks,

sapuser

[Former Member]

Hi Experts,

I have created a user exit by name ZDMEE_EXIT_ACCNUMBER in a package ZDMEE for a customized DME tree. Now I want to debug the source code of the FM when I run F110. I found some posts on this issue, but still I am unable to solve the problem.

Can any one please advice how to debug the FM usinf F110, Is there any special procedure to do this?

Thanks,

sapuser

[Former Member]

Hello ,

try to use Tcodes : FBPM(creates a new DME ) or FDTA.

so if u want to debug , then Put a break point in that FM and run FBPM for that payment run .

may be your source mapping is wrong....check the node of that DMEE

regards

Prabhu

Edited by: Prabhu Peram on Aug 23, 2010 3:36 PM

[Former Member]

Hi,

I have tried it by setting a break point in the FM, even then the FM screen is not popping for Debug, it's directly generating the output File. It's not checking for the FM. and mapping the fielad to blank.

Thanks,

Sapuser

[Former Member]

Hi!

You can't debug F110 directly since it schedules batch job to generate payment file.

You could set external breakpoint in your DMEE exit function and run DMEE online (get the program name/variant from job)

There is also simple test functionality in trx DMEE - that should be enough for unit tests.

WBR -

Pauls

[anuj_srivastava]

Hi ,

You can follow the following steps to debug the function module that you created.

Step 1: Run the F110 transaction and the print option.

Step 2: Running the F110 transaction will create a background job ( say F110-20100813-XXXXXXXX)

Step 3: Put a breakpoint in your FM

Step 4: Goto tcode SM37 and select F110-20100813-XXXXXXXX and enter 'jdbg' in the command prompt and press enter.

Step 5: Press F8. The debugger will halt at the breakpoint created by you if that function module is being called through the node in which you have maintained this exit module.

Regards,

Anuj

[SuhaSaha]

As already mentioned you can't debug directly via F110. To debug you've to put the break-point in the Exit module & then re-run the payment run via trxn. FBPM (program SAPFPAYM).

BR,

Suhas

PS: I hope the exit module uses the template of the FMs: DMEE_EXIT_TEMPLATE_ABA or DMEE_EXIT_TEMPLATE_EXTEND_ABA.

Edited by: Suhas Saha on Aug 25, 2010 3:23 PM

[Former Member]

Another solution is scheduling payment run without "Create payment medium" and then running program SAPFPAYM_SCHEDULE in SE38 or SA38, with 'Execute online" option.

[Former Member]

Please note that you may run SAPFPAYM_SCHEDULE several times for the same F110 job; you will get several versions of your payment file. It is useful in your tests if you want to change your user exit: you can test the effect of the change without creating a new payment job.

[former_member239892]

Please Keep the break points in FM and run the f110 with payment run, then goto sm37 tcode find the payment run job then do the JDBG.