Debugging ECC FM called via RFC

[nisha_vinod]

Hello experts,

From a CRM Function Module, we are trying to invoke a custom ECC FM. On debugging, the flow does not go to the ECC module for debugging (although it returns the values). We tried several options like adding RFC param in su01, Activate Remote Debugging in ECC, sm51, sm50 etc. But none of this helps.

Any suggestions on debugging would be most welcome.

Regards,

Nisha

[SuhaSaha]

Hello,

Since the connection is R3, check the user which is used to connect to the ECC system. What is the "user type"?

BR,

Suhas

[nisha_vinod]

Hi Suhas,

The user type is 'Dialog' user. Unfortunately, we cannot login using dialog user credentials in ECC and have to make do with our own user Id.

So any inputs?

Regards,

Nisha

[Former Member]

You can follow these steps to indirectly debug your ECC FM.

1) Put an infinite loop in your ECC FM, say

DATA TEMP.

DO.

IF TEMP = 'X'.

EXIT.

ENDIF.

ENDDO.

2) Execute your CRM FM in which your ECC FM is being called.

3) Go to ECC, Transaction SM50 (Process Overview). You will see your FM's entry. Select your FM's entry then from the menu select Program/Session>Program>Debugging. This will open your ECC FM in debug mode. Put value of TEMP as 'X' and continue debugging.

[nisha_vinod]

Hi Siddharth

We already tried this. In this case it just opens a pop-up in ECC but the control does not go anywhere from there.

Are we missing any authorizations?

Regards,

Nisha

[Former Member]

There should not be any authorization issue. Actually there are limited debug modes available through SM50, thats the reason sometimes it does not go to debug mode. You need to keep trying because those modes are already occupied someone else.

[SuhaSaha]

Hello Nisha,

If the user type is "dialog" it should not be a problem. Can you check if the user has debug auth in ECC system?

Did you set break point in the ECC RFM? You can also check the "Session Breakpoint Active Immediately" in the debugger settings.

BR,

Suhas

[Former Member]

Hello,

May be you need to change your debugger setting to New debugger. Just check & give a try.

Regards

Balaji R

[nisha_vinod]

Hi Siddharth,

Your approach helped us resolve the issue. Full marks to you on this one.

Btw, why is this required? Is there a "cleaner" approach for the same?

Regards,

Nisha