How to debug a RFC function mod in background?

Hi all,
I am uploading a file thru a portal application & the output will go to a mail box. Everything happens in background.
First the portal application will call a XI devlopment & then the data processed will call a RFC fun mod and the output is going to a mailbox.
In the function modules, I am getting the errors. Since it is a protal application & it runs in backgrnd, I am unable debug the fun modules. I tried both external break point & internal breakpoints. But I am unable to debug the program.
can anyone help me how to keep external breakpoints & debug it in background?
Thanks,
Vijay.

HI ,
you can do Debugging , what you need to do is need not use the login as Public . there will be another   group server .
i am sure you are using PUBLIC   in this only the front end   will work   means only   inside the sap objects will be stopped . for Portal other thigs you need to take other gropu server .
Your Basis Knows it well ....
Normally , in SAP   You will have PUBLIC ,SPACE, MESSAGE ,dialog servers.
Take the last one which will have   all facilities ,so that it will stop in the break Points which you kept.
it means the Dialog proces will take care of the screens and also takes Break Point and stops it in sap .
Reward points if it is usefull....
Girish

Similar Messages

How to debug a RFC function when the user is non-dialog type? Please help!

hi Experts,
I am calling a RFC FM residing in B from R/3 system A.
R/3 A -
Call FM residing in B----
> R/3 B
The user attached to the remote destination is a non-dialog type.
I cannot change the user type of this user.
Therefore how to debug the RFC FM in System A?
Are there any alternatives?
Please help
Thanks
Gopal

in your RFC FM, code an endlees loop.
something like:
data: gv_x type xfeld value 'X'.
do.
if gv_x = space.
exit.
endif.
enddo.
now you can catch the mode in TA SM50, go in it, change gv_x to space and debug what is coming further.

How to debug a RFC function module remotely from another R/3 system?

Hi experts,
   I have RFC function module in one R/3 system. I am calling this from another R/3 system that is cross apps (Xapps).
   This function module is Synchronous.
Is it possible to debug this function module from cross apps?
Can somebody give me the steps?
Thanks & Regards
Gopal

Hi Shree,
   Can you explain it bit more?
   Do I have to call the function module with "IN BACKGROUND TASK"?
   Or is it that I have to just put external breakpoint in the function module?
   Please help
Thanks
Gopa

V Urgent : Debugging an RFC function Module in another R/3 system

Hi All
I have a function module in a R/3 system ( say WB1 ) and i am calling it from another R/3 system (say WD1) . Both have their RFC destinations set up as trusted system mutually . However when i try to debug that FM while in WD1 ( which basically exists only in WB1) i am not able to get inside that FM . Are there some settings that we need to do to allow us to debug function module in another R/3 system ? .
Yes ,we cant do this debugging if RFC function module is in a non SAP system but am sure it can be done atleast for R/3 to R/3 .
Any pointers to this as to what setting needs to done ?
Does some system parameter needs to be set in RSPARAM program for debugging RFC?
Please help
Regards
Shovit

Hi
Can you do a remote logon through the SM59 connection (the trusted one)?
If so, then the only thing preventing you would be debugging autorization.
If not, make sure you have trusted system logon auth (not part of SAP_ALL!).
Cheers
Dom

Calling Synchronous RFC Function Module in Background

Hi all,
Currently we are working on some requirement where in we have to retrieve data from one system(CRM) and update the same into another system(ECC). We have developed a RFC Function in CRM system and it is being called from ECC system as in synchronous mode via a batch program.
Now since all sychronous call to a RFC function will be dialog there is a constraint on the runtime which is being set by maximum run time for each dialog work process. So my question is there an option to call an RFC function synchronously in background (background task) so there is no runtime performance.
The standard TRFC, QRFC calls in background runs asynchronously and so I am trying to check with the SDN world as whether has anyone tried SRFC(Synchronous) call in background?
Thanks in advance,
Jagath

So my question is there an option to call an RFC function synchronously in background (background task) so there is no runtime performance.
One solution would be to increase the value of the "time out" parameter defined the CRM system. This i feel is not a fool-proof solution as the run-times cannot be predicted. Check this thread: Re: RFC timeout profile parameter
For me a better solution would be to implement tRFC call instead of a synchronous call. Any reasons why you don't want to implement a tRFC ?
BR,
Suhas
Edited by: Suhas Saha on Jun 26, 2010 8:52 AM

How to debug a remote function module in calling system? Help!

Hi Experts,
   I have a ABAP report (in System A) from where I am calling a remote function module which exists in a different system B.
ABAP Program(System A)<----calls--
RFC(System B)
Can I debug the RFC funnction module in system A using ABAP debugger? In other words if i put a breakpoint on the "call function" statement then in debug mode I want to see that the control is going to system B and I should be able to process the FM code line by line. Is this possible?
Is there any special transaction or settings?
Is there any alternative?
Please help
Thanks
Gopal

hello,
Try this method.
first check whether RFC connection is working b/w 2 systems.
if connection is working, then do like this.
In System B , put endless loop in FM before some main select statement.
like
DATA : v_a TYPE c VALUE space
DO .
   IF v_a = 'X'.
     EXIT.
   ENDIF.
ENDDO.
the above code will be endleep loop.
In system A, when cursor goes to CALL FUNCTION DESTINATION 'XXXXX'.
u shud be logged in system B. the moment control comes to system B.goto tcode SM50 . check ur username . choose that particular checkbox then in menu bar --> program/session --> Program --> Debugging.
i hope it will help u.
try & let us know.
Thanks,
Manjunath MS

How to debug smartform in display mode?

Hi,
How to debug smartforms program lines in display mode? Need help on this issue?
<MOVED BY MODERATOR TO THE CORRECT FORUM>
Edited by: Alvaro Tejada Galindo on Jan 12, 2010 11:32 AM
Moderator message - Cross post locked
Edited by: Rob Burbank on Jan 12, 2010 11:57 AM

Please search before posting
<< Cut and paste without attribution from http://it.toolbox.com/wiki/index.php/SAP_Smart_Forms removed >>
<< Please don't ask other to follow the forum rules and violate them yourself! >>
*In simple way---follow these steps:-
If you are in a non-modifiable client:
Display your SmartForm.
Go to Environment and copy the function module name.
Go to SE37 and display the function.
Go to Smartforms and copy the node name where you want to debugg.
Go to the function and search for the name in main program. Put a soft break point.*
Manas M
Edited by: Kumar Manas Mishra on Jan 12, 2010 12:05 PM
Edited by: Kumar Manas Mishra on Jan 12, 2010 12:06 PM
Edited by: Rob Burbank on Jan 12, 2010 11:52 AM

How to debug a Package / function in PL SQL developer ??

How can we debug a Package / function in PL SQL developer ??
i want to debug a code line by line

Karthick_Arp wrote:
This question does not belong to this fourm. We have a {forum:id=260} forum for such question.Not even there Karthick. PL/SQL Developer is a 3rd party tool, not Oracle's SQL Developer, so it doesn't even belong on the Oracle forums.

How to debug PL/SQL functions? Passing parameter and debugger error

Hi,
How to debug a PL/SQL function in JDeveloper? There are two problems with it:
1) Don't see how it's possible to pass parameters required by function call (in the dialog opening after Debug -> Debug FUNCTION_NAME)
2) In a function returning table_name%ROWTYPE (and having a record declaration for table_name%ROWTYPE), debug gives error:
PLS-00103: Encountered symbol "/" when expecting one of ... in line
v_Return PL/SQL RECORD;
Debugging procedures works as expected.
Found a similar question without answer here:
Debugging PL/SQL with parameters

Check
http://www.oracle.com/technology/obe/obe9051jdev/plsqlobe/obeplsql.htm#t2
Frank

How to debug Adaptive RFC

hi folks,
How to debug an adaptive RFC connection and plz leave some idea about the Bapi_Input and Bapi_output structures
thanks in advance
nikhil

Hi
If you want to debug the backend then put and external breakpoint in the abap code.
make your jco connect to a single instance
login using the user which is configured for jco.
For the front end
put a break point in your code before you call the execute method on the RFC and after it and use the debug perspective to evaluate the values.
Regards
Ayyapparaj

Regarding: RFC Function Mod

Hi all,
Can any body Tell me whats the Difference between Synchroner RFC and Asynchroner
All i KNow is that
Synchroner RFC
CALL FUNCTION func DESTINATION dest
                     parameter_list.
Asynchroner RFC
2. CALL FUNCTION func STARTING NEW TASK task
                [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
                parameter_list
                [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
Can any body Please explain ...
Thanks
Srinivas

hi,
A remote function call (RFC) is the call of a function module that runs in a different system to the calling program. Although it is also possible to call a function module in the same system as an RFC, normally RFCs are used when the caller and the called function module run in the same system.
In the SAP system, these functions are provided by the RFC interface system. The RFC interface system enables function calls between two SAP systems, or between an SAP system and an external system.
The RFC- interface system is made up of the following interfaces:
Calling interface for ABAP programs
Each ABAP program can call a remote function module using the command CALL FUNCTION...DESTINATION. The parameter DESTINATION informs the SAP system that the called function module runs in a different system to the calling system. RFC communication with the remote system takes place as a part of the CALL FUNCTION command.
RFC function modules in an SAP system must be proper function modules and must be registered in the SAP system as remote.
If the calling program and the called program are both ABAP programs, the RFC interface provides both communication partners. The calling program can be any ABAP program, and the called program must be a function module that is registered as remote.
For more detailed information on calling function modules that are registered as remote, see Calling RFC Function Modules in ABAP.
For more information on writing function modules that you want to call remotely, see Writing RFC Function Modules in ABAP.
Interfaces for calling non-ABAP programs
If either the calling program or the called partner is not an SAP program, this program must be programmed in such a way that it can play the role of the other partner in RFC communication.
To support you when implementing RFC partner programs in non-SAP systems, read: Components of the SAP Communication Technology
RFC-supported and GUI-supported interfaces can be used by external programs to call function modules in SAP systems, and execute them in these systems. Likewise, ABAP programs can also use these interfaces to use functions supplied by external programs.
These are the types of RFC :
Asynchronous RFC (aRFC)
Synchronous RFC (sRFC)
Transactional RFC (tRFC)
Queued RFC (qRFC)
Parallel RFC (pRFC)
RFC:
Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Asynchronous RFC :
This is used when you need to increase the performance of ABAP program by having system call more than one function module in parallel than forcing the program to wait for results .
Synchronous RFC:
The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.
Transactional RFC:
If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
Queued RFC:
When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously.
For More Info,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694

How to call a RFC function from ABAP to external C/C++ system

Hi
Can some one describe me what are the steps that needs to be done to call a RFC function in external C++ system and to handle errors.
Any previous experience,please share

Hi,
i think this is the wrong Forum.
Better use the SAP NetWeaver .NET Technologies Forum on this site.
Henning

How to Debug the RFC when the call is made from XI

Hi
I will give the brief about the problem
this call is from Webservice >XI-> R/3 BW (RFC)
Some transaction were failed with error 'Reason Code not valid ..e.t.c " this error returning from the RFC of the BW system, but as per the inputs from the business t,he reason code are valid and some of other transactions went through sucessfully with same reason code.
My requiremnt is,,
i had the XML's of the failed transactions , and i need to push them From XI to BW, and Simultaneously i need to debug the RFC of BW system and trace the reason for that error.
Is there any possiblity to do this.
Please help.
Thanks in Advance
Mallik

Hi
I will give some more details abou my requirement.
Some transaction passed from B2B bridge >-XI (RFC)>BW, Failed due to the error returned by BW system in Production environment.
The RFC is standard one and intern it is calling BAPI (I need to debug a method inside the BAPI which is returning the particular error).
And i have the XML's of the failed transactions.
If i want to do this Dev. environment.i will fallow the below steps.
1) I will add the external break-point on my user-ID (BREAK USERID)
2) And in XI i will change the user in the RFC communicational channle to my USER ID and password.
3) From XI Runtime workbench i will send the test message with XML's provided.
Can any one please confirm that i am going in a correct way...?
Please correct me if i am wrong.
Thanks for your help
Mallikharjuna Reddy

Problem while calling an RFC Function Module in Background

Hello,
I have created a RFC function module for reading data from an external DB system. The FM calls an external RFC program (coded in C++ using RFC SDK), which delivers the required data. This external program is maintainged as an TCP RFC Connection in SM59.
Further I have created a report, that calls the RFC function module to get the data from the external RFC programm.
My problem is, when I call the report in foreground, everything works OK, the RFC connection works and data can be read from the external program.
However, when I schedule the report to run in background as a job, the report is stating in the protocoll that there was a problem calling the defined RFC connection (although the connection is working properly at that time).
More funny is, this particular problem with running in background occurs only in the productive system, in test and development system the report works correctly also while running as a job in background.
Can you suggest the solution to this problem? Could it be something with authorisations or server settings?
I will be on holiday for the next 6 weeks, so take your time to answer .
Regards,
Dusan.
Edited by: Julius Bussche on Jan 22, 2009 7:19 PM
Please read the forum rules about u r g e n t ...

This is an external RFC server program, not a remote enabled ABAP RFC function module as the others seem to be assuming, right?
Is it possible that your DEV and QAS systems only have one application server, but the PROD has many and dedicated one(s) for processing low priority background jobs?
It might be that the target server of your TCP connection is not this BTC instance, and your RFC server is returning the data "locally" - so, into nirvana...
Just guessing, but might be worth checking.
Cheers,
Julius

How to debug the report which isrunning in Background?

Hi all,
1.How to debug the report which is running in Background?
thanks & regards
vishnuvardhan

Hello,
Do like this.
Create an infinite loop before the line u want debug.
data: lf_flag.
do.
if lf_flag = 'X'.
exit.
endif.
enddo.
Now execute the report in background. In Tcode SM37 select ur job and in menu job--> Capture Active Job
IT will stop at the point of infinite loop.
Regards,
Vasanth

How to debug a RFC function mod in background?

Similar Messages

Maybe you are looking for