QRFC and tRFC outbound-queue

in SXMB moni entries,
when the message is
for example inbound: IDOC and outbound: AENGINE, the queue seen is a tRFC outboud-queue,
and when inbound: IDOC and Outbound: PE, the queue seen is a
qRFC outbound-queue
can u explain me why this>?
but nowhere i can see inbound-queues in the MONI. means XBTI* or XBQI*...
can u explain me why?

Hi,
Please see the below link
Eo/EOIO?BE - Queue - ? - /people/sap.india5/blog/2006/01/03/xi-asynchronous-message-processing-understanding-xi-queues-part-i
Please go through these links
For queues in message mapping
/people/venkat.donela/blog/2005/06/09/introduction-to-queues-in-message-mapping
Here are the Queues for Asynchronous Message Processing
http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/94553b4d53273de10000000a114084/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694
Regards
Chilla

Similar Messages

The difference between qRFC and tRFC

I am studying RFC now,i don't understand when i should use qRFC or tRFC.can any expert tell me.
thanks

Hi kim,
welcome to sdn.
The qRFC Communication Model
qRFC Properties and Possible Uses
All types of applications are instructed to communicate with other applications. This communication may take place within an SAP system, with another SAP system, or with an application from a remote external system. An interface that can be used for dealing with this task is the Remote Function Call (RFC). RFCs can be used to start applications in remote systems, and to execute particular functions.
Whereas the first version of the RFC, the synchronous RFC, (sRFC) required both systems involved to be active in order to produce a synchronous communication, the subsequent generations of RFC had a greater range of features at their disposal (such as serialization, guarantee for one-time-only execution, and that the receiver system does not have to be available). These features were further enhanced through the queued RFC with inbound/outbound queue.
Communication between applications within an SAP system and also with a remote system can basically be achieved using the Remote Function Call (RFC). Here, the following scenarios are possible:
·         Communication between two independent SAP systems
·         Communication between a calling SAP system and an external receiving system
·         Communication between a calling external system and an SAP receiving system
The following communication model shows what these communication scenarios may look like in reality. The actual sending process is still done by the tRFC (transactional Remote Function Call). Inbound and outbound queues are added to the tRFC, leaving us with a qRFC (queued Remote Function Call). The sender system is also called the client system, while the target system corresponds to the server system.
Scenario 1: tRFC
This scenario is appropriate is the data being sent is independent of each other. A calling application (or client) in system 1 uses a tRFC connection to a called application (or server) in system 2. In this scenario, data is transferred by tRFC, meaning that each function module sent to the target system is guaranteed to be executed one time only. You cannot define the sequence in which the function modules are executed, nor the time of execution. If an error occurs during the transfer, a batch job is scheduled, which sends the function module again after 15 minutes.
Scenario 2: qRFC with outbound queue
In this scenario, the sender system uses an outbound queue, to serialize the data that is being sent. This means that function modules which depend on each other (such as update and then change) are put into the outbound queue of the sender system, and are guaranteed to be sent to the target system one after each other and one time only. The called system (server) has no knowledge of the outbound queue in the sender system (client), meaning that in this scenario, every SAP system can also communicate with a non-SAP system. (Note: the programming code of the server system must not be changed. However, it must be tRFC-capable.)
Scenario 3: qRFC with inbound queue (and outbound queue)
In this scenario, as well as an outbound queue in the sender system (client), there is also an inbound queue in the target system (server). If a qRFC with inbound queue exists, this always means that an outbound queue exists in the sender system. This guarantees the sequence and efficiently controls the resources in the client system and server system. The inbound queue only processes as many function modules as the system resources in the target system (server) at that time allow. This prevents a server being blocked by a client. A scenario with inbound queue in the server system is not possible, since the outbound queue is needed in the client system, in order to guarantee the sequence and to prevent individual applications from blocking all work processes in the client system.
Properties of the Three Communication Types
To help you decide which communication type you should use in your system landscape for your requirements, the advantages of the three communication types are listed below:
       1.      tRFC: for independent function modules only
       2.      qRFC with outbound queue: guarantees that independent function modules are sent one after each other and one time only (serialization). Suitable for communication with non-SAP servers.
       3.      qRFC with inbound queue: in addition to the outbound queue in the client system, an inbound queue makes sure that only as many function modules are processed in the target system (server) as the current resources allow. Client and server system must be SAP systems. One work process is used for each inbound queue.
       The qRFC Communication Model
Purpose
Communication within an SAP system or with a remote system can take place using Remote Function Call (RFC). This enables the following scenarios:
·        Communication between two independent SAP systems
·        Communication between a calling SAP system and an external receiving system
·        Communication between a calling external SAP system and an SAP system as the receiving system
Implementation Considerations
The following communication model shows how these communication scenarios can occur in practice. tRFC (transactional Remote Function Call) is still responsible for actually sending communications. tRFC is preceded by inbound and outbound queues, which have led to the name qRFC (queued Remote Function Call). The sending system is called the client system, and the target system represents the server system.
There are three data transfer scenarios:
Scenario 1: tRFC
This scenario is suitable if the data being sent is not interrelated. A calling application (or client) in system 1 uses a tRFC connection to a called application (or server) in system 2. In this scenario, the data is transferred using tRFC. This means that each function module sent to the target system is guaranteed to be processed once. The order in which the function modules are executed, and the time they are executed, cannot be determined. If a transfer error occurs, a background job is scheduled that resends the function module after a defined period of time.
Scenario 2: qRFC with Outbound Queue
In this scenario, the sending system uses an outbound queue to serialize the data being sent. This means that mutually dependent function modules are placed in the outbound queue of the sending system and are guaranteed to be sent in the correct sequence, and only once, to the receiving system. The called system (server) has no knowledge of the outbound queue in the sending system (client). Using this scenario, every SAP system can communicate with a non-SAP system (the program code of the server system does not need to be changed, but it must be tRFC-compliant).
Scenario 3: qRFC with Inbound Queue (and Outbound Queue)
In this scenario, in addition to the outbound queue in the sending system (client), there is also an inbound queue in the target system (server). qRFC with an inbound queue always means that an outbound queue exists in the sending system. This guarantees that the sequence of communications is preserved, and at the same time the resources in the client and in the server system are controlled efficiently. The inbound queue is processed using an inbound scheduler, which only processes as many queues in parallel as the current resources in the target system (server) will allow, This prevents a server from being blocked by a client.
Features
Features of the Three Communication Types
To help you decide which communication types you need to implement according to your system landscape and your requirements, the advantages of the three types of communication are explained below:
·        tRFC
Suitable only for independent function module calls; the sequence of the calls is not preserved
·        qRFC with outbound queue
Function modules in a queue are guaranteed to be processed only once and in sequence (serialization). Also suitable for communication with non-SAP servers.
·        qRFC with inbound queue
The function modules created in the outbound queue are transferred from the outbound queue to the inbound queue; the sequence of the function modules is preserved. An inbound scheduler processes the inbound queues in accordance with the specified resources. Both the client and the server system must be SAP systems. One work process is used for each inbound queue.
Queued Remote Function Call (qRFC)
Purpose
All types of applications are instructed to communicate with other applications. This communication may take place within an SAP system, with another SAP system, or with an application from a remote external system. An interface that can be used for dealing with this task is the Remote Function Call (RFC). RFCs can be used to start applications in remote systems, and to execute particular functions.
Integration
In contrast the first version of RFC, synchronous RFC (sRFC), which required both participating systems to be active to form synchronous communication, subsequent generations of RFC now provide a considerably extended range of functions (for example, serialization, guarantee that processing occurs once, and the receiving system does not have to be available). These features were further enhanced through the queued RFC with inbound/outbound queue.
Contents:
The information about qRFC is organized into the following main sections, with more detailed subsections:
The qRFC Communication Model
·        qRFC with Outbound Queues
·        qRFC with Inbound Queues
qRFC Administration
·        qRFC Administration: Introductory Example
·        Outbound Queue Administration
·        Inbound Queue Administration
qRFC Programming
·        qRFC Programming: Introductory Example
·        Outbound Queue Programming
·        Inbound Queue Programming
·        qRFC API
For an introduction to the new bgRFC (Background RFC), use the following links:
bgRFC (Background RFC)
·        bgRFC Administration
·        bgRFC Programming
Using Asynchronous Remote Function Calls
Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user does not have to wait for their completion before continuing the calling dialog. There are three characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
·        When the caller starts an asynchronous RFC, the called server must be available to accept the request.
The parameters of asynchronous RFCs are not logged to the database, but sent directly to the server.
·        Asynchronous RFCs allow the user to carry on an interactive dialog with the remote system.
·        The calling program can receive results from the asynchronous RFC.
You can use asynchronous remote function calls whenever you need to establish communication with a remote system, but do not want to wait for the functionu2019s result before continuing processing. Asynchronous RFCs can also be sent to the same system. In this case, the system opens a new session (or window). You can then switch back and for between the calling dialog and the called session
To start a remote function call asynchronously, use the following syntax:
CALL FUNCTION Remotefunction STARTING NEW TASK Taskname
DESTINATION ...
EXPORTING...
TABLES   ...
EXCEPTIONS...
The following calling parameters are available:
§         TABLES
passes references to internal tables. All table parameters of the function module must contain values.
§         EXPORTING
passes values of fields and field strings from the calling program to the function module. In the function module, the corresponding formal parameters are defined as import parameters.
§         EXCEPTIONS
See Using Predefined Exceptions for RFCs
RECEIVE RESULTS FROM FUNCTION Remotefunction is used within a FORM routine to receive the results of an asynchronous remote function call. The following receiving parameters are available:
§         IMPORTING
§         TABLES
§         EXCEPTIONS
The addition KEEPING TASK prevents an asynchronous connection from being closed after receiving the results of the processing. The relevant remote context (roll area) is kept for re-use until the caller terminates the connection.
Transactional RFC (tRFC)
Transactional RFC(tRFC, previously known as asynchronous RFC) is an asynchronous communication method that executes the called function module just once in the RFC server. The remote system need not be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function, together with the corresponding data, in the SAP database under a unique transaction ID (TID).
If a call is sent, and the receiving system is down, the call remains in the local queue. The calling dialog program can proceed without waiting to see whether the remote call was successful. If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch.
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls
·         are executed in the order in which they are called
·         are executed in the same program context in the target system
·         run as a single transaction: they are either committed or rolled back as a unit.
Implementation of tRFC is recommended if you want to maintain the transactional sequence of the calls.
Disadvantages of tRFC
·       tRFC processes all LUWs independently of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.
·       In addition, the sequence of LUWs defined in the application cannot be kept. It is therefore impossible to guarantee that the transactions will be executed in the sequence dictated by the application. The only thing that can be guaranteed is that all LUWs are transferred sooner or later
thanks
karthik
reward me if usefull

QRFC and TRFC Difference...

Hello All,
I need some help in understanding TRFC and QRFC in CRM middleware.
Please answer the following to help me in understandin the TRFC and QRFC:
1. During data replication between CRM and R/3, when system will use QRFC and when it uses TRFC... I mean in which scenarios.....
2. TRFC error's can be checked in transaction: SM58... During what context system will create the entry in SM58..
Regards,
Srini.

Hi Srini,
a qRFC is a serialized (queued) tRFC. Technically these two are the same, just that the qRFC makes sure that all predecessors of the contained LUW are already committed.
Data replication via CRM Middleware always uses the qRFC.
HTH
Thomas

Clearing of qrfc and trfc tables c

Hi all
we planned to have a bi system
created a client and defined rfc's from r/3 system
no we stoped the bi project...removed client for bi
but the rfc's are still there...so the rfc tables grew up huge
How to clear those RFC tables
And how delete the defined RFC's
thanks in advance
jameel

Hey Jameel,
Those queue saves the information that has changed in the R/3 system,
this is done in order to move the "delta changes" from R/3 to BI.
They are created by customization changes,
and every relevant change in the R/3 (of the object that is being inspect)
would create a record in the queues.
If you would schedule the relevant extractors in the BI
they would read this information and the queues would be empty.
if you don't want to transfer this information to the BI,
than you will have to disable the delta queue in the customization,
and delete those queues.
(if you will only delete the queues without changing the customization
than they would re-create).
About the trfc,
I don't know if they are relevant,
please write more information (what is the destination of the TRFC, what are the functions and the error messages)
p.s
this is a BI questions

How to debug qRFC and Trfc.

Hi All,
how to debugging asynchronyos finction module and Transactional function module when call in Background?
Regards,
Anuj Jain

Hi Anuj,
In transaction SM50 (process overview), you can select a background process and choose Program/Mode -> Program -> Debugging from the menu.
Debugging TRFC
1. Go to the program 'ZREPORT' and go to the CALL FUNCTION 'ZFUNCTIOn' IN BACKGROUND TASK .
2. Keep breakpoint in 'ZREPORT' just before the CALL FUNCTION start .
3. when you reach the breakpoint, Go to menu -- > Settings-> Display/Change debugger settings-> select the flag "tRFC (In Background Task): Block Sending".
4. Execute SM58, Select the background task, and choose menu --->edit -
>debug LUW, the "background task" will start and the debugger will stop at the FM.
Let me know If any further queries
Edited by: Raj on Jul 27, 2010 1:07 PM

Deleting Outbound Queues in SMQ1

Dear Experts,
System landscape: ECC 6.0, SRM 5.0
I started intial load using DNL_CUST_PROD1 in R3AS and my outbound queue in SMQ1 (ECC) contained an SYSFAIL status. So I would like restart the initial load again from SRM.
Can you please let me know if I need to delete this outbound queue or resetting the status to READY is enough.
If I need to delete the queue, can you please let me know how to delete this outbound queue.
Points will be rewarded.
Thanks in advance,
Bob.

Hi Bob,
I'm not sure if I completely understand your question.
You can delete the outbound queue and start the initial load again. In order to do so, just select the queue (click on it once) and then select the trash can icon on the top left side. Or else you can just right click on the queue and select the "Delete" option.
Hope this helps!
Thanks,
Aravind

Gerneric Datasources and Outbound Queue

Dear Experts,
I've got some generic Datasources (Delta and Full Update) that work properly with productive BW-System.
Now I'm starting to build up an developement system (wrong order I know) and want to load data using the mentioned Datasources from time to time to get relevant data for testing.
Problem now is, that the generic delta Datasources fail accourding to doublicate keys (loading to dev-system) although in the basic tables for these datasources no doublicate keys are existing (or even are possible due to the table key).
I realized in smq1, that every time when data is transfered to productive BW-System, the counter to the queue for dev-System is incremented. When I delete all the entries in smq1 all the updates for dev-System work fine.
In one of the threads here I read, that generic Datasources do not have outbound queues. (Re: Generic Data Source issue).
So is there any way to turn of the outbound queues for specific (generic) Datasources? I do not want to turn them of in general as we use standard delta Datasources for Controlling.
Or how is the "normal" way to transfer data to a dev-System?
(One more information: productive system is 3.5; dev-system is 7.1.)
Thank you in advance
Kind regards
Philip
Edited by: Philip Munz on Nov 17, 2009 8:50 AM

ok,
after some days of searching and reading I now understand my problem.
For all, who face the same problems in understanding delta-updates, qrfc, rsa7 and so on, please have a look at
http://www.sdn.sap.com/irj/scn/index;jsessionid=(J2EE3417800)ID0216771750DB11245246034303112354End?rid=/library/uuid/40427814-376a-2c10-5589-bc1aaa6692c3&overridelayout=true
again thanks for the help
kind regards
Philip

Monitoring qRFC outbound queues

Hi,
I need a CCMS monitor on qRFC outbound queues (tcode SMQ1), so that I get notified whenever messages gets stuck for some reason.
I tried with MTE class "CCMS_qRFC_Outbound_Queues_Summary", but it stays green, even after several messages are not processed in the outbound queue.
Does anyone have experience with this?

Read SAP Note 441269 - Setting up tRFC/qRFC monitoring in the alert monitor
That should put you in the right direction.
Regards
Juan

QRFC Outbound queue errors

Hi All,
I have some "qRFC Outbound queue errors" in the production system of R/3 and the target system is CRM.
The status is "SYSFAIL " .
Can anybody tell me how to solve them.
Regards,
Anindya

HI Anindya,
It's a very simple error. You have to check with your Security System Administrator if the user has included in your profile the authorization object S_RFCACL. Before this you have to define RFC Trusted / Trusting Systems in your Landscape.
Reward Points if helpful
Cheers
Manohar

Significance of Inboun and Outbound queue in sales order replication

Hi CRM Leads,
What is the significance of Inbound Queue and Outbound queue in saleas order replication from CRM to ECC.
What exactly happens in Outbound Queue and Inbound Queue.
Thanks,
Sandeep
What

Inbound - Tcode: SMQ2 : Inbound in the context of CRM and this queue shows the business transaction, master data and configuration data that are coming from ECC into CRM .
Naming Convention for Queues
The names of queues for data transfers from an ERP back end to the CRM server are made up as follows:
R3A (from ERP back end to CRM)
    I for the initial data transfer / for Data Synchronization
    D for the delta data transfer
    U for loading to the ERP back end
    R for Defining Requests
    <Object> Name or part of object name, or the name of the higher-level independent object
    <Key> Only delta queues are subdivided by keys
Outbound - Tcode SMQ1 - Outbound in the context of CRM and this queue shows the transactions and data that are going from CRM to ECC
See more on [Using CRM Queues|http://help.sap.com/saphelp_crm70/helpdata/EN/49/2d9d9707361903e10000000a42189c/content.htm] following the link.
Read the [CRM Adapter Framework|http://help.sap.com/saphelp_crm70/helpdata/EN/49/2e33a2a6c51d24e10000000a421937/content.htm] for advanced learning.

About qRFC Monitor (outbound queue)

Hi Experts,
we are upgrading the r/3 system from 4.6 to 4.7 and i am responsible for BW activities, i was asked to take care of the outbound queue what does that mean? and what needs to be done with this queue during r/3 upgrade? and there are some queues(in SMQ1) with destination None and entries 1 what are those???
Does any one have the check list what needs to be done on the BW side during R/3 upgrade?
Thanks in Advance.

all the guides can be found on sapnet
https://www010.sap-ag.de/instguides
the particular guide for your particular upgrade is THE place to look for help. it's very detailed w/ links to all the oss notes you need to review as well.

QRFC Monitor (Outbound queue)

Hello friends,
I have to delete and fill up the setup tables for the application 18. I have successfully deleted the data from the setup tables in LBWG. But when I am going to delete the entries in extraction queue(LBWQ), I find two queus for application 18. They are MCEX18 & MCEX18_1. Could you pls let me know the reason for the 2 entries. Should I delete both? Same is the case for allication 17.
Thanks in advance.
Vishwa

Hi,
The entries in LBWQ are those which have only been captured in outbound queues and have not reached RSA7. It is absolutely normal for them to have destination as NONE.
Go to SMQ1, and execute, there you would find multiple entries for application 18
e.g.
Queue Name                                   Destination                      Entries
BWXXX2LIS_18_I0NOTIF               BWCLNTXXX                      100
BWXXX2LIS_18_I0TASK               BWCLNTXXX                       200
MCEX18                                         NONE                                   2000
The first two entries here are the ones which have already been processed from outbound queue to RSA7. Therefore now they have destination as BW system.
Please check if here you get entries for 2 different BW systems. This may be the reason for 2 entries MCEX18 and MCEX18_1 in LBWQ.

Diff. between using inbound queue and outbound queue.

Hello All,
Can somebody please explain me the diff. between using inbound and outbound queue?Thanks.
Best Regards,
Tushar

Hi Tushar,
I hope you will find the answers here:
/people/somnath.manna/blog/2006/12/21/demystifying-cif
/people/somnath.manna/blog/2006/12/31/demystifying-cif--part-ii
Regards
Alper

Impact of inbound and outbound queue

Hi,
I have created the service request in CRM and replicated to r/3, what is the impact on inbound and outbound queue of R/3 and CRM server.
Thanks in advance

Hi
if the mb doc is passed to R3 ok if not you can come to know in smw01 if it gets bounced to crm you need to check for error analysis why bounced, if it get posted R3 inbound queue to r3 is succefull if get bounced back to crm the out bound of crm is failed then depending up on error analysis you should proceed in order to proceed further how to push the transaction to r3 by clearing the middlle ware struck up
CRM Impact is : succefully sent to r3 using mb docs by out bound quue
R3 : if gets bounced in bound quueue is failed to receive the CRM's out bound so you need to rectify in CRM only.
Reward for useful
Venkat

QRFC outbound queue

Hello all,
In the outbound queue of a R3/ECC system, I find messages with status as "Message edited in the target system".
What could be reason for this and what is the work around to solve this problem ?

Hi,
Did you get resolutoin to your problem here? We have BI queues in ECC which have been running just fine for over a year now and out of no where this just started happening to one of our LO extraction processes in ECC. We have raised our issue to SAP but at this point can not find any notes pertaining to this type of message being in a ECC outbound queue for BI.
thanks

QRFC and tRFC outbound-queue

Similar Messages

Maybe you are looking for