Skip to Content

BPC 10 odd ENDROUTINE behaviour

Hi guys! Struggling with the rather strange problem for the past 4 hours. I've created the routine BADI, pretty simple, pretty standard, all filters and classes are in place. The ENDROUTINE call bit in Transformation's Options area is set. The break point in CL_UJXD_PACKAGES_RES is also set and triggers every time I start the package.

But after that nothing, silence. It looks like the system doesn't even go to the Routine.

I've set breakpoints in the routine. They were ignored.

I've explicitly set the debugger break point to trigger in the Runroutine. Ignored.

I've changed the code of the routine for it to produce a shortdump. Nothing.

I'm really frustrated, because no matter what I do it's like the routine doesn't exist from BPC's point of view (even though in DM package log it claims that the routine was triggered) .

Any ideas are much appreciated!

Cheers.

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Mar 07, 2013 at 04:25 PM

    Hi Vadim,

    If you want to debug the code, then you must execute it through UJKT.

    DM package will ignore the breakpoints.

    Hope this helps.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Mar 08, 2013 at 03:26 AM

    Hi Vadim,

    Like Nilanjan said DM package will not trigger the breakpoints.

    But if you must want to trigger it, Simply create an infinite loop in top of the code so that you can catch your BAdi in SM50 transaction.

    There you have option to debug the code.

    Infinite loop :

    DATA : LV_DEBUG TYPE C VALUE 0.

    WHILE LV_DEBUG EQ 0.

    ENDWHILE.

    Don't forget to change the variable value before execute in debugging mode.

    Hope it helps!!

    Thanks,

    Suresh

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Mar 08, 2013 at 08:45 AM

    Well, guys, on other implementations I can debug DM routine through the breakpoint in CL_UJXD_PACKAGES_RES (then setting if_debug to X) and the following break point in the routine itself.

    Firstly, I'm not sure that it's possible to test DM transformation routine in UJKT.

    Secondly, as I wrote, in my routine I didn't assign any values to field symbol, but used it in the code.

    That explicitly should trigger the GETWA_NOT_ASSIGNED short dump (it just should), but it doesn't, meaning that the system doesn't call the routine in the first place!

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Gersh,

      The odd thing is that when I start DM package without endroutine in transformation, it successfully completes. Then I add endroutine to the transformation, start DM package and it still successfully completes (and the line "end routine was called in convert" is being added). But if I try to get to the routine's breakpoints - nothing happens and, as I wrote before, even if I create the shortdump situation, nothing happens...

      Thanks!

  • Posted on Apr 25, 2013 at 03:11 PM

    Still experiencing the same problem on the same system. STARTROUTINE breaks like a charm, ENDROUTINE breakpoints just always ignored.

    Add a comment
    10|10000 characters needed characters exceeded

    • Go to tn SE80 and find the CLASS/Interface CL_UJXD_PACKAGES_RES. In Method / Redefinitions, find the method DO_POST.

      Create an external break-point (Ctrl_Shift+F9) on the line 179: lo_package->run_package (EXPORTING ...

      Set a break-point on any line of your BADI implementation.

      When running any king of package the debug screen will pop up. Replace the content of the variable LS_PACKAGE_RUN-if_debug to "X".

      Hit F8 do go directly to the break-point on your implementation.

      Hope it helps.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.