Skip to Content
avatar image
Former Member

How to Debug Billing IDOC User Exit ZXEDFU02 ?

Hi,

I have wriiten the Billing IDOC User Exit ZXEDFU02. but whenerver i put the break-pint internal or external the debug does not get activated. i have gone thru many SDN messages but i am not able to debug the Billing IDOC user exit. the Transaction i am using is VF01.

pl. help.....

Regards,

Umesh

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Mar 26, 2010 at 09:25 AM

    Hi

    You must block the queue. when the document is inbound, you can start the debug

    Regards

    Marco

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      I am not getting what u guys are suggesting. WE19 is for Re-processing the IDOC.

      i want the debug to get set when i am triggering VF01 transaction. ?

      can you pl. write step by step.

  • avatar image
    Former Member
    Mar 26, 2010 at 11:07 AM

    Hi ,

    Please check if you have created a project for user exit in SMOD and activated the same in CMOD. The control will not reach in your user exit until u create a project and activate it in CMOD.

    If you have already done so then it means you have to search for another exit as this is not a suitable exit for you. Before implementing any exit put a break point and then test it.

    Hope it helps.

    Thanks,

    Vivek Gupta

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 28, 2010 at 01:39 AM

    Hi Umesh,

    In Order to debug the IDOC enhancement in outbound billing document you have to do following -

    1. When output type is put in the billing document header , change the further processing to value (1 or 2), the value shouldn't be 4.

    2. Now save the billing document, ( the output in above document should be in yellow - ready to process)

    3. Now put break point in your code and then call program RSNAST00 and give value in selection parameter for - output type you have used, application is V3, object key ( billing document number), transmission number as 6 .... etc. Now execute the program it will stop in your code.

    Hope this helps!

    Harry

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Umesh,

      Ideally if your enhancement project is active then the control should stop at the break-point in the include.

      Just try putting break point with break <user id> and see if the controlis stopping there(As if the controlis going through ur code then it should definitely stop at the break point.

      Thanks,

      Vivek Gupta

  • avatar image
    Former Member
    Mar 29, 2010 at 10:26 AM

    Hi Umesh,

    Which method are you using to trigger this INVOIC idoc?? I guess its message control which is driven through an output type.

    You need to get this configured in NACE by giving o/p type so that when ever u create a billing document automatically through this o/p type idoc is triggered. Once idoc is triggered while creating billing document, the control will stop at the break point in include.

    I am sure now idoc is not triggered and hence the control is not stopping at the BP.

    Thanks,

    Vivek Gupta

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi, Umesh,

      I met the same problem as you and finally found the reason was because the outboud IDOC was calling background.

      So you could use VF31 to run your foreground, then the break-point will all work.

      The parameters are the one used in your billing for output type.

      Output type

      Transmission medium

      Sort order

      Processing mode must be 2

      Hopefully this thread could be closed.

      Regards

      David