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

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..

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

Issue in external debugging in comm_bupar application

Hi All,
I am currently working in SAPCRM 5.0 and on enabling a pop-up to be displayed when one of the partner belonging to a particular relationship category in the partner relationship tab in the PCUI is modified.
I am facing the below issue:
1) When I login using my SAP login credentials into SAPGUI and the comm_bupar pcui application url in my laptop and with the external debugging activated, it does not take me into the debug mode.
2) When I login using my SAP login credentials into SAPGUI and the comm_bupar pcui application url in my colleagues' laptop and with the external debugging activated, it does take me into the debug mode.
3) When I login using my colleagues SAP login credentials into SAPGUI and the comm_bupar pcui application url in my laptop and with the external debugging activated, it does not take me into the debug mode.
4) When I login using my colleagues SAP login credentials into SAPGUI and the comm_bupar pcui application url in his laptop and with the external debugging activated, it does take me into the debug mode.
I had got in touch with the sap basis and sap security teams in our project and they could not help me with this issue. They have given me all the requisite access.
Well, if anyone of you had come across this kind of an issue earlier, please let me know as to what needs to be done to rectifiy this issue.
Are there any settings that need to be done to work with the external debugging? I have also tried searching for this on the forums but was not able to find the solution.
It looks like an issue with the settings or components in my laptop as of now.
Thanks,
Ravi Kiran
Edited by: Ravi Kiran Madabhushi on Apr 7, 2008 12:51 AM

Dear GLM/Bala,
I am trying to debug BAPI in R3 externally ie through my portal as we normally do to check if the backend rfc is executing well for portal application .
For your information i am able to do normal debugging at the backend but unable to do external debugging , might be issue at the portal side or J2EE server.
Please reply back if you require any other clarification.

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

How to specify a variable in the path prefix of an External HTTP (RFC) connection (in transaction SM59)

Hi There,
Please can someone tell me how to specify a variable in the path prefix of an External HTTP (RFC) connection in transaction SM59?
For example if my path prefix is /invoke/test/example?input=XYZ; how do I replace "XYZ" with a variable so that I can pass in any value after "=" ?
Thanks,
Brendon

Hi,
This is SAP Business one system administration forum. Please find correct forum and repost above discussion to get quick assistance.
Please close this thread here with helpful answer.
Thanks & Regards,
Nagarajan

Error after import external webservice(RFC) wsdl url to Process Composer

Hi all,
I try to use RFC webservice in my BPM as below:
1. Expose RFC as webservice using CAF (import external service RFC and then create application service use this external service)
2. Define Destination in NWA.
3. Create a Process Composer project, and import the external webservice(RFC) wsdl file as service interface in the project.
After importing, i get error : the port type specified for the ...binding is undefined. Check port type name and ensure it is defined.
If i import another external service, not RFC (such as business object), there is no error.
My system is NWCE 7.11
Thanks in advance,
Sinh.
Edited by: Sinh Nguyen Van on Jul 20, 2009 8:29 AM

Hi Bharath,
Below is content of wsdl url and error message, thanks
Error message:
The 'zfm_rfc_caf_as' port type specified for the 'zfm_rfc_caf_asBinding' binding is undefined. Check the 'zfm_rfc_caf_as' port type name and ensure it is defined.
wsdl url :
- <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.sap.com/caf/demo.sap.com/s00_caf_rfc/modeled/zfm_rfc_caf_as" xmlns:b0="http://www.sap.com/caf/demo.sap.com/s00_caf_rfc/modeled/zfm_rfc_caf_as">
<import namespace="http://www.sap.com/caf/demo.sap.com/s00_caf_rfc/modeled/zfm_rfc_caf_as" location="http://sinhnv-lap:50000/zfm_rfc_caf_as/zfm_rfc_caf_asBeanImpl?wsdl=binding&mode=ws_policy" />
- <service name="zfm_rfc_caf_as">
- <port name="zfm_rfc_caf_asBindingPort" binding="b0:zfm_rfc_caf_asBinding">
<address xmlns="http://schemas.xmlsoap.org/wsdl/soap/" location="http://sinhnv-lap:50000/zfm_rfc_caf_as/zfm_rfc_caf_asBeanImpl" />
</port>
</service>
</definitions>
Edited by: Sinh Nguyen Van on Jul 22, 2009 4:18 AM

External Debugging in CRMD_ORDER_BP

Hi Expert,
I've set external breakpoint in
class cl_crm_cckpt_view
method get_report
but it does not hit in crmd_order_bp.
I tried to set external breakpoint in
class CL_CRM_CCKPT_CSCFS
method REFRESH
the breakpoint can be hit, which means the external debugging is successfully activated.
I analyzed on another system, which can have the breakpoint hit, the calling stack is
CL_CRM_CCKPT_VIEW=============CP
METHOD GET_REPORT
CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP
METHOD IF_HTTP_EXTENSION~HANDLE_REQUEST
CL_HTTP_SERVER================CP
METHOD EXECUTE_REQUEST_FROM_MEMORY <<<< system debugging
SAPLHTTP_RUNTIME
FUNCTION HTTP_DISPATCH_REQUEST <<<< system debugging
SAPMHTTP
MODULE (PBO) %_HTTP_START <<<< system debugging
then I tried on
CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP
METHOD IF_HTTP_EXTENSION~HANDLE_REQUEST
breakpoint not hit
And tried to put breakpoint in the previous system debugging coding, all not hit.
It seems that those codings are not executed, but the factsheet data can be displayed.
Any idea about the possible reason?
thanks a lot
Ruth

Further to this, there is a transaction code that calls this function module: SRDEBUG (see OSS Note 1004248). It's a little quirky but it does work.
1) Set your external breakpoint.
2) run transaction SRDEBUG. This will display a pop-up asking if you want to stop debugging. This pop-up must remain active until you want to stop debugging, so just leave it hanging there while you debug.

ABAP server proxy-External Debugging

I have a server ABAP proxy implementation in a R/3 where i m sending message from XI,
I want to debug the the ABAP Proxy using External debugging (http breakpoint),
Pls tell me if it is mandatory to:
1. login in R/3 (for debugging) using the same user, which is used by XI proxy adapter,
2. the user should be a dialogue user.
Is it OK to use this debugging in a production environment ?

Hi,
1. login in R/3 (for debugging) using the same user, which is used by XI proxy adapter,
A. Its not like that you will have login details like user name and password for R/3 and also for XI
2. the user should be a dialogue user.
A. No i dont think so.
Is it OK to use this debugging in a production environment ?
A.Never do this. If something goes wrong in production system entire business will stop.But i dont thing you have production system details like username and password.
Please reward points if it helps
Thanks
Vikranth

External Debugging not working

Hi,
in my solution manager system i have activated the external debugging, still im not able to debug from webdynpro. i checked the below setttings .
in abap editor -> utilities -> settings -> debugging -> activate ( Checked )
in SICF -> edit -> debugging -> activate debugging .
but still im not able to debug from webdynpro . what could be the problem ?/?
thanks

Hi,
Also make sure that the Application server on which your Wedbynpro application is running and the Application server which your R/3 session is using are the same.
You can shift between the application server for R/3 in the SAP Logon.
Regards,
Sesh

External debugging of ABAP from NWDS in web dynpro java

Hello Experts,
Like a while a ago, I remember on SDN there was a video for external debugging tutorial. Can any one point me to that or any other documentation for doing external debug from NWDS.
Thanks,
Sharath

HI James!!!
You can find a video presentation for external debugging of WD JAVA application at:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/com.sap.km.cm.docs/library/elearning/user-interface-technology/web%20dynpro/wd%20java/web%20dynpro%20java%20with%20an%20adaptive%20rfc%20model/web%20dynpro%20java%20with%20an%20adaptive%20rfc%20model%3a%20debugging/resources/eventplayer.htm
I hope this would help you. If you seek something else, you can revert back. I'll be happy to help you
Cheers!!!
Umang

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.

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.

** External Debugging is not working in Proxy inbound scenario

Hi Friends,
In our File to Proxy scenario, the user which is mentioned in reciver XI adapter of type as 'C Communication Data'.
The message is processed successfully (SXI_MONITOR). But the records in the Z table are not updated.To debug this, I am not able to set external debugging (Utilities --> Settings --> Debugging) for this user. (the user which is mentioned in the CC). i.e it gives the message 'Logon with a dialog user'.
So, How do I bug my inbound proxy, when the message is processed ?
We use ECC 6.0 as application server.
Kind regards,
Jegathees P.

Jegathees,
If you want to debug inbound proxy you need to set hard-coded break point "break-point" in your abap code.
Then stop the queue manually and re-run your interface. You will find your message in an inbound queue. Goto sxmb_moni and process this message. This time it will stop to a point where you have set the hard coded breakpoint.
Hope this will help.
Thanks,
Nilesh

External DEBUG RFC.

Similar Messages

Maybe you are looking for