topic Re: Debug RFC destination system in Application Development and Automation Discussions

Debug RFC destination system

joan_ayala — Fri, 30 Apr 2010 11:56:40 GMT

Hi,

debugging production system A, I call an RFC function module in production system B, but instead of starting debugging system B, it continues debugging next step of system A.

I don't know why this is happening, I can debug both systems A and B separately, but when calling B from A, I cannot debug system B.

My user in system A is: des005

My user in system B is: des005

The passwords are not the same.

Thanks in advance

Re: Debug RFC destination system

Sandeep_Panghal — Fri, 30 Apr 2010 12:12:36 GMT

Put a break-point in the target system for RFC call or what you can try is put an while endwhile statement at the starting of rfc call in remote system and debug it.

Re: Debug RFC destination system

joan_ayala — Fri, 30 Apr 2010 12:15:10 GMT

I tried putting 2 breakpoints:

- break des005.

- break-point.

But it doesn't stop. It seems that there must be a configuration parameter of the system, allowing debugging from another system or not.

Re: Debug RFC destination system

Former Member — Fri, 30 Apr 2010 12:19:33 GMT

Hi,

Put an external breakpoint in system B and make sure you have a session open in system B.

Thanks,

Wenonah

Re: Debug RFC destination system

Sandeep_Panghal — Fri, 30 Apr 2010 12:20:13 GMT

Check St22 if there are any runtime errors for this rfc ...

Re: Debug RFC destination system

joan_ayala — Fri, 30 Apr 2010 12:31:04 GMT

How can I put an external breakpoint in 4.6 C ?

Re: Debug RFC destination system

joan_ayala — Fri, 30 Apr 2010 12:31:44 GMT

Yes, something is appearing ST22, but I do not understand it at all. The error says:

The termination occurred in the ABAP/4 program "SAPLCJWB " in

"%_CTL_OUTPUT".

The main program was "SAPLCJWB ".

The termination occurred in line 37

of the source code of program "<SYSINI> " (when calling the editor 370).

Re: Debug RFC destination system

uwe_schieferstein — Fri, 30 Apr 2010 19:55:57 GMT

Hello Joan

Your SAP user in the RFC system B is irrelevant but who is the RFC user defined in the RFC destination that you use to go to system B. Check the RFC destination and whether this RFC user is of type "Dialog". If not then you cannot debug in the remote system.

If the RFC destination is not suitable you may create an additional RFC destination to system B without RFC user. In this case the logon for system B will show up where you can enter your User name and password. Then you can continue debugging in the remote system. However, take care of the fact that the authorizations may be different for you and the RFC user.

Regards

Uwe

Re: Debug RFC destination system

Sandra_Rossi — Fri, 30 Apr 2010 22:35:34 GMT

Joan, to complete Uwe's answer, it's valid for synchronous RFC, but you didn't tell us what kind of RFC it is, i.e. how is the CALL FUNCTION statement? (because if it's asynchronous, you won't be able to debug (without external break-points which don't exist in 4.6C), and transactional RFC calls occur later at COMMIT WORK, and anyway it's finally an asynchronous call...)

Could you paste the whole CALL FUNCTION statement please?

Re: Debug RFC destination system

joan_ayala — Mon, 03 May 2010 07:46:30 GMT

The RFC user defined in the RFC destination is: des005

and all mentioned users are of type "Dialog". I don't want the logon for system B to be showed up.

My RFC is like this:


                    call function 'ZRFC_UPDATE_PROJECTE' destination 'EDURFC'
                      exporting
                        i_projecte       = lwa_projecte
                      tables
                        o_messtab        = it_messtab
                      exceptions
                        no_exist_pepampl      = 1
                        system_failure        = 2
                        communication_failure = 3
                        others                = 4.

Re: Debug RFC destination system

uwe_schieferstein — Mon, 03 May 2010 07:53:24 GMT

Hello Joan

Here is my recommendation to facilitate debugging:


DATA:
  ld_rfcdest     TYPE rfcdest.

  ld_rfcdest = 'EDURFC'.

call function 'ZRFC_UPDATE_PROJECTE' destination ld_rfcdest
                      exporting
                        i_projecte       = lwa_projecte
                      tables
                        o_messtab        = it_messtab
                      exceptions
                        no_exist_pepampl      = 1
                        system_failure        = 2
                        communication_failure = 3
                        others                = 4.

If you cannot debug using RFC destination "EDURFC" then I recommend to define a dummy RFC destination (e.g. "SysB" which just contains the technical details of the remote system.

Set a break-point at the CALL function statement and then overwrite LD_RFCDEST with the dummy RFC destionation.

The login popup will appear and if you are allowed to do debugging in the remote system you should be able to do so.

Regards

Uwe

Re: Debug RFC destination system

joan_ayala — Mon, 03 May 2010 09:13:00 GMT

Hi,

I created the dummy RFC destination in 2 ways:

- With Trusted System = NO --> I got system failure when executing the RFC

- With Trusted System = YES --> The debugging did not go into system B, and no popup to introduce login and password was shown. The execution continued in next step of system A.

Re: Debug RFC destination system

Sandra_Rossi — Mon, 03 May 2010 13:03:44 GMT

Try as Uwe said: define your RFC destination without user name and password.

Re: Debug RFC destination system

joan_ayala — Mon, 03 May 2010 13:08:54 GMT

that's what I did Sandra.

Re: Debug RFC destination system

Sandra_Rossi — Mon, 03 May 2010 13:23:25 GMT

please paste the dump (respect 2500 char. max)

Re: Debug RFC destination system

joan_ayala — Mon, 03 May 2010 13:55:18 GMT

if you refer to the ST22 dump, I have to say that I am getting no dump nor entry in ST22.

Probably I had a confusion when I wrote about the ST22 dump in a previous post.

Re: Debug RFC destination system

Sandra_Rossi — Mon, 03 May 2010 14:21:47 GMT

you may retrieve a description of the error using MESSAGE keyword:


DATA msg TYPE c LENGTH 80.
CALL FUNCTION func DESTINATION dest 
    ... 
    EXCEPTIONS 
        SYSTEM_FAILURE = 1 MESSAGE msg 
        COMMUNICATION_FAILURE = 2 MESSAGE msg.

Re: Debug RFC destination system

joan_ayala — Mon, 03 May 2010 14:56:44 GMT

ok Sandra, if you mean the 'system failure' produced when I use the dummy RFC destination with Trusted System = NO, this is the message stored in variable 'msg':

"User is locked. Please notify the person responsible"

Re: Debug RFC destination system

Sandra_Rossi — Mon, 03 May 2010 15:37:32 GMT

Could you tell me how is it possible that SAP tries to log with a (locked) user if you removed this user from the RFC destination? (you told me it was removed but it's not)

I guess you have the solution now.

Re: Debug RFC destination system

joan_ayala — Mon, 03 May 2010 15:57:39 GMT

I removed the user and password from the RFC destination !!!

I don't know why this is happening.