Debugging remote - ecc 6.0 --> 4.6C

[eduard_reidel]

Hello,

we are developing Web applications in WD Abap on an ecc 6.0 system. The necessary data are provided from a 4.6c System.

Question.

I need to DEBUGG the functionality on the 4.6C system with input from the website (ecc6.0 application). Can anyone give me a hint or tell me which settings are necessary - in 4.6C or in ecc 6.0.

note: in 4.6C there is no tab (at least i don't have one) with 'Debugging' like there is in ecc when you do 'tc_SE80 -> go to -> abap editor -> debugging'.

thank you in advance.

[Former Member · Accepted solution]

I think you should be able to set an external breakpoint in ECC6 at the point where the RFC call to 4.6c happens and then you should then jump to the 4.6C system.

Give it a try.

Regards

Carl

[Former Member · Accepted solution]

no external breakpoints available as there is no option for remote debugging

[thomas_jung · Accepted solution]

>

> I think you should be able to set an external breakpoint in ECC6 at the point where the RFC call to 4.6c happens and then you should then jump to the 4.6C system.
> 
> Give it a try.
> 
> Regards
> Carl

I concur and can say that I have done this myself. Although 4.6C doesn't have any options for external breakpoints (they didn't come until WebAS 6.10), you can just set the break point in the ECC6 system at any point before the call to 4.6C. When you step into the RFC call, the debugger will continue stepping into the 4.6C program. You might need to set your Debugger settings in ECC 6 to classic debugger. I can't remember if you get an automatic switch to the classic debugger when stepping into 4.6C or not.

[alejandro_bindi · Accepted solution]

I did all this steps but still I can't debug R/3 coding.

Like you all I'm calling RFC's in 4.6c but from CRM 5.0 (Web AS 7.0).

I've placed an external breakpoint right before the CALL FUNCTION and switched manually to classic debugger, but still when pressing F5 the debugger steps over the function call.

Anyone knows what else I may check?

Thanks!

[eduard_reidel]

Hallo Alejandro,

on the 4.6c system there is only the old debugger.

on the Ecc 6.0 the debugger was set to 'Old debugger'. After that some breakepoints were set in both systems and it worked.

Just for debugging purpose i usually place some hardcoded breakpoints to my - respectively the rfc-user - name, just to be sure it 'really' stops. Hope this helps.

[alejandro_bindi]

Many thanks Eduard, I couldn't get it to work, but at least I now know why it doesn't: I've put a hardcoded breakpoint on the R3 side with the RFC user and got a dump: RFC_DEBUGGING_NO_DIALOG_USER.

I've been reading a couple of OSS notes and came to know that the RFC user has to be able to use a dialog WP to debug (seems reasonable) - Note 300208 - Single step debugging of RFC calls provides more details.

Regards

[Former Member]

Hello,

Set the external break-point in the ECC 6.0 and take a look on this to enable the debugger.

Regards.