Debugging RFC

I just rolled out a new app and can't get he RFC call to work.   The trace file shows:
---> RFC MESSAGE/ERROR : 104
RFC_ERROR_SYSTEM_FAILURE
CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456
Timeout during connection setup (check that partner exists)
So I did a bit of messing around in SM59. The ONLY thing I would change in SM59 was
the program being called. I changed the called program than ran connection test. All these Unix programs are owned by the same user and have the same rights.
/usr/sap/DEV/SYS/exe/run/tp -> worked OK
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> timed out
copied 'tp' to 'tf80server.csh'
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> worked OK
/usr/sap/DEV/SYS/exe/run/sapftp -> worked OK
copied 'sapftp' to 'tf80server.csh'
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> worked OK
copied orignal tf80server.csh back
/usr/sap/DEV/SYS/exe/run/tf80server.csh -> timed out
The timeout doesn't seem to be consistant what whatever program I put in. I even created a short shell script (called vince.sh) that only had:
   echo "hi"
   exit 0
/usr/sap/DEV/SYS/exe/run/vince.sh -> timed out
BUT copied 'tp' to 'vince.sh'
/usr/sap/DEV/SYS/exe/run/vince.sh -> worked OK.
So I don't think it is a TaxFactory issue but an internal SAP/RFC
issue. I am unsure how to debug further.
Suggestions?
Thanks!
HP-UX 11.31 Oracle 11.2.0.2 SAP 7.00 Kernel 278 Basis Support Pack 22

Though I would still like to know how to further debug RFC turns out it is a BSI issue. The tf80server executable turned out to be the point of failure.

Similar Messages

Debugging RFC function module from ECC to CRM

Hi All,
My requirement is to debug an RFC function module present in CRM(7.0) system from ECC(6.0) system. A report program in ECC will call CRM custom FM. I found many posts in SDN with the same issue and tried to implement suggestions provided there. But I couldn't succeed. The approach I followed is:
I logged in to ECC report program and kept an external breakpoint just before the function module call.
I logged in to CRM system, opened the function module and kept an external breakpoint there.
In both the systems I provided the dialogue userid( id through which I log in to SAPGUI) in the system->settings->debugging option.
In CRM I activated the external break point in transaction SRDEBUG.
Now when I execute the report program in ECC, control stops at the breakpoint. If I press F5 at the function call, control is not going to the external break point set in the CRM FM. I am getting output of FM directly.
I tried with different settings like turning on the check box for IP matching and session breakpoint active immediate, switching to classic debugger etc. I also tried to provide the RFC user id instead of dialogue user but system throws exception saying only dialogue userids are allowed. I found that by inserting an infinite loop statement, control goes inside the RFC CRM FM but I prefer not to change the code.
Please let me know if I missed anything.
Thanks and Regards,
Naren

Hi,
Debug RFC calls
When an RFC function module is called it is usually not possible to debug the call, using the below techniques we can achieve the same. For this example we are calling an RFC enabled FM in ECC system from CRM system.
Scenario 1: Calling a custom RFC FM
STEP 1: Add an infinite loop in the remote custom Function Module (adding a u201CDO. ENDDO.u201D statement at the start of the FM would be enough).
STEP 2: Execute your program in the CRM system. The execution stops at the RFC call, because of the infinite loop.
STEP 3: Now login to the ECC system and go to transaction SM51 select the process which is executing the RFC and navigate to the menu: u201CProgram/Session->Program->Debuggingu201D this triggers the debugger session in a separate window.
Scenario 2: Calling a Standard RFC FM
When we are debugging a standard program we cannot add the infinite loop, hence we cannot go to SM51 and debug the work process. The RFC destination for the ECC system has a User specified, the RFC function module gets executed using this users credentials. Usually the basis team set up the RFC user as non Dialog user, this does not allow debugging. Contact your Basis team and get this changed to a dialog user enabling you to debug RFC function calls via the normal debugger.
Note: User name configured in the RFC destination (transaction SM59)
Note: User type for the RFC User (transaction SU01D)
Hope this will be helpful..

How to debug RFC

hi
could anybody suggest me how to debug RFC
thank you
kalyan.

Hello Kalyan,
What do you mean by debug RFC? RFC can be tested using SM59 transaction code.
Regards
Arif Mansuri

Debugging RFC Calls

I was going thru the Blog
/people/michal.krawczyk2/blog/2006/01/17/xi-debugging-rfc-calls-from-the-xi-not-possible-who-said-that-
I am not understanding what Michal is trying to say? Would some one explain me please.
I understand that when we are talking to an RFC and error occurs how XI is going to handle.
Thanks

Thanks Michal.
Just I have listed what I have understood, please correct me. (I got confused with your naming conventions)
1) Existing RFC    : RFC-OLD (XI calls RFC_OLD)
2) Copy            : RFC-OLD_Copy
3)                 : Delete the function code in RFC-OLD
4)                 : RFC-OLD Calls RFC-OLD_Copy
DATA: queue_name like TRFCQOUT-QNAME.
*setting the queue name
queue_name = 'DEBUG_QUEUE'.
    call function 'TRFC_SET_QUEUE_NAME'
      exporting
        qname              = queue_name
      exceptions
        invalid_queue_name = 1
        others             = 2.
    if sy-subrc <> 0.
    endif.
*call the new function in the background *and passing all the parameters from the old RFC! *so we'll be able to debug the RFC with correct *parameters
CALL FUNCTION 'RFC-OLD_Copy'
in background task
destination 'NONE'
as separate unit
TABLES
    TABLESAMPLE       = TABLESAMPLE.
*remember about the commit work
Commit Work.
Endfunction.

While debuging rfc I'm getting some problems..

HI Guys,
While Debugging RFC's, when passing values to parameters they are entering to BAPI Return,but for some values they are not entering to BAPI Return..
Its very Urgent..Please Rectify As soon as possible
With Regards
kirankp

Hi,
I guess this problem is specific to the BAPI which you are invoking remotely.
It might be giving different output returns on different inputs parameters.
Please provide more detail for making the problem more clear, if issue aint resolved.
Regards,
Tanveer.
<b>Please mark helpful answers</b>

How to Debug RFC Enabled FM ?

Hello All,
         I want to debug an RFC Enabled FM.
I've written a small Test program to check this.
DATA: eenumber           LIKE     bapip2001-pernr,
      subtype           LIKE     bapip2001-subty,
      objectid           LIKE     bapip2001-objps,
      lockindicator     LIKE     bapip2001-sprps,
      validitybegin     LIKE     bapip2001-begda,
      validityend           LIKE     bapip2001-endda,
      recordnumber     LIKE     bapip2001-seqnr.
CALL FUNCTION 'BAPI_ABSENCE_GETDETAIL
EXPORTING
    employeenumber          = eenumber
    subtype                 = subtype
    objectid                = objectid
    lockindicator           = lockindicator
    validitybegin           = validitybegin
    validityend             = validityend
    recordnumber            = recordnumber
* IMPORTING
*   RETURN                  =
*   START                   =
*   END                     =
*   ABSENCETYPE             =
*   ABSENCEDAYS             =
*   ABSENCEHOURS            =
*   NAMEOFABSENCETYPE       =
IF sy-subrc <> 0.
WRITE:/ 'UNsuccessful'.
ENDIF.
When a Break Point is kept at the above FM and When I press F5 the cursor is going into the FM .
But when I specify the Destination in the Call Statement as :
CALL FUNCTION 'BAPI_ABSENCE_GETDETAIL' DESTINATION 'SID_010'
EXPORTING
    employeenumber          = eenumber
    subtype                 = subtype
    objectid                = objectid
    lockindicator           = lockindicator
    validitybegin           = validitybegin
    validityend             = validityend
    recordnumber            = recordnumber
* IMPORTING
*   RETURN                  =
*   START                   =
*   END                     =
*   ABSENCETYPE             =
*   ABSENCEDAYS             =
*   ABSENCEHOURS            =
*   NAMEOFABSENCETYPE       =
The control is not going into the FM.
Can any one tell me how to debug the FM within a different system ?
Regards,
Deepu.K

Hi Deepu,
Your function module is at other system and you are calling it at some other system.
I hope you know on which system your function module exists.
First debug your coding at your system where you are calling this RFC Function Module and go to that point where your function module starts, now check the export data here
And
go to that system where this function module exists and give the same export data there and debug this Function Module at that system.
Reward points, if helpful,
Sandeep Kaushik

External DEBUG RFC.

Hi all,
When I call a RFC from portal It seems to work fine, but when I put an external debug It doesn't call the RFC and create an exception.
In R3 I can see this dump RFC_DEBUGGING_NO_DIALOG_USER. But the user is a dialog user.
Plz any help?.
At PRD it doesn´t have the external break but doesn´t call the RFC.
The call of this RFC was working fine, please can you tell me what configuration should I check?
Thanks

HI,
When you are trying put external Debugger then you have change login credential in the respective JCos (Model and Meta data)
please make sure that your have loging with same user Ids in R/3 system and Portal and JCO connection login details also should same. then only your external debugger start working .
Thanks
Suresh

Debugging RFC - EBP and R/3

Hello people,
I´m debugging in EBP, and sometimes a function in R3 is called (a RFC function in R/3 system).
I´m debugging with F5 (step by step) and I want to debug step-by-step inside the function called (in R3). In this moment, when the RFC function is called, the debug session acts as I had pressed F6 and the debug continues in EBP.
I don´t know where I have to configure it! Do you have any tip?
Thank you!

Hi,
Please check the following things
1) Transaction SM59 --> check the entry you have maintained for your R/3 system.
2) get in to details of the RFC destination ---> click on the tab Logon/security.
3) You will find the following details
Language        EN
Client          ---> Client of the R/3
User            ---> RFC user for R/3
password     --> password of this user in R/3
4) click on 'connection test' ---> system would take you to R/3 system. (this is just test to check the connection).
5) Get in to details of this RFC user in R/3 ---> Transaction -->SU01 ---> User type should be dialog.
6) then you should be able to do RFC debugging.

General topic: debugging RFC's called remotely

I don't know if this is the right forum to ask this, but I thought I would give it a try. It seems that I often find myself with the following dilemma:
1. I build a function module in SAP (and unit test it).
2. I call the function module as an RFC from the web using a connector, and the results are not as I intended. Sometimes the situation occurs only in a limited scenario that seems to only happen in production.
If I am programming in only R/3, I of course would be able to set a breakpoint in the ABAP code. However, when calling remotely via a connector, the breakpoint does not fire. As a workaround I usually do one of the following:
1. Run ST05 to view the SQL and RFC trace of the remote call.
2. Add in code to write to dataset file in unix via Al11 to see what the variable output of a program is at various points.
3. Set server to debug mode and set breakpoint in the class making the call to R/3.
I guess my question is this: what means do use as developers to troubleshoot R/3 function modules when calling from the web? Are there any tips and tricks to do this that I am overlooking?
Thanks in advance for your help!
Brandon

Hi Gayatri,
Now I am also stuck in a similar scenario. Did you found a solution for the same?
It will be of great help if you can let me know if you have a solution by now.
Regards
Avishek

Debug RFC called from external system with no dialog user

Hi all,
We need to debug the rfc function module which is called from the external system( Siebel ) .
The user id is not dialog user so can not set external debugger.
Need you help.
Thanks,
Anmol.

Hi Suhas,
Nice to know you became Moderator...
Hmmm the solution you provided was the last option..
Any ways the issue is resolved we changed the user to dialog user and then debugged the code.
Thanks a Lot,
Anmol.

How to debug RFC connection using RfcOpenEx?

Hi,
I use COOPC1 to test a RFC connection and this transaction uses RfcOpenEx which fails.
How can I debug this connection?
Best regards
Marty

Hi,
in fact the conection from SAP to the destination works using SM59. but the system reply with a connection using RfcOpenEx but this function fails because there is a mixup with the parameters maybe a wrong type.
I will try to debug from the tcode COOPC1 when I start a subscription.
Thanks
Marty

Debugging RFC-call in ERP-system

Hi experts,
I've a similar problem as decribed Values for FM structure not delivered as expected - but the opposite direction:
we send data from PI, which received a FTP-file, to ERP by RFC-Function.
last week we enhanced the output structure for this fm in PI (resp. in ERP: input structure)
result: the field is filled in the xml-file, which leaves PI - but the field comes blank into ERP-system
we've already emptied PI-cache!
is there any chance to debug the process in ERP-system???
thank you and regards
Andreas from germany

Hi Andreas,
We had the same problem.
Clearing all the caches and even restarting the PI system did not help.
Reactivating all the configuration objects for the specific scenario fixed the problem.
This means:
- sender agreement (if existing)
- receiver determination
- interface determination
- receiver agreement
- communication channel
If you want to debug the rfc that is called, insert an external breakpoint on the userid that is connecting from PI towards ERP (configured in receiver communication channel). You can change this userid via:
Utilities --> settings --> abap editor -->debugging --> external debugging userid
Hope this helps.
Kind regards
Joris
Edited by: Joris Verberckmoes on May 31, 2010 9:33 AM
Edited by: Joris Verberckmoes on May 31, 2010 9:36 AM

Debug RFC destination system

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

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

Debugging RFC FM

Hi,
I have a doubt that how to debugg a RFC FM. Could any one tell me Step by Step.
Thanks & Regds,
Harkesh Dang

hi Harkesh
you can do this by following the steps given below
you need to put a break point at the first check statement before calling the RFC. now in debugger, click Settings, system debugging. Now you need to step through the programs with F5. Keep pressing the F5, you will see it pass through SAPLSUNI. If you want you can set a break point at the end of this function module(once inside it) and hit F8 to skip to the end of it. Next program will be SAPLSUSF. Do the same thing here, break point at ENDFUNCTION and hit F8, now it F5.
Now you will see the RFC function module in debug mode.
If the debugging is stopping at SAPMSYST, just keep pressing F5 untill it comes out of it.
follow these steps and i hope they help you out
regards
Aakash Banga

Debugging RFC FM from WSDL web services

Hi friends,
I am using WSDL as my web services and calling SAP RFC FM to send some files, I would like to Debug and test the FM....
I have same user ID and pwd for both SAP login and WSDL credentials, activated external debugging to set some break-points..but whenever I run the external WSDL application(already logged into SAP n RFC FM session is ready with external break-points) there is no pop up of a different session with debugging.
I hope the above information helps in understanding my issue, please provide me the appropriate steps/solution to Debug an RFC FM which is called from a non-sap like WSDL application.
Moderator message - Please do not offer points or rewards
Thanks & Regards,
Santosh
Edited by: Rob Burbank on Aug 5, 2010 4:41 PM

Hi Raghavendra,
Thanks for ur reply, I understand that you are giving me the steps to test for uploading of input text files but this RFC FM is working fine with the files coming from WSDL webservices, the actual issue is with the handling of dynamic files i.e. no. of file attachments may vary from time to time in getting saved in SAP system.
For this we are trying with a work around solution by creating a table type parameter in changing parameters and to get the no. of file attachments sent from WSDL, so to test for this scenario defnetly we need to run the WSDL application and debug our
RFC FM to tess it.....
I hope you have understand my requirement....orelse please post ur query to give more details on the issue so that you can provide me with the better solution....
Thanks,
Santosh

Debugging RFC

Similar Messages

Maybe you are looking for