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

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

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

My IPad want charge I've bought a new charger and use difference outlets but it still want charge.

My IPad is getting hard to charge,I have to wiggly the charger to get it to charge. I've bought a new charger and used difference outlets. I need to know what is wrong?

Consider where you are wriggling the charger (I suspect you mean the cable. Why does everybody refer to a cable as "the charger"?) and make sure all the contacts there are free from pocket fluff and such.

How to get exact date and time difference?

Hi,
When i am using the below sql statement:
SELECT (TO_DATE('7/27/2006 05:00:15 PM','MM/DD/YYYY HH:MI:SS PM') - to_Date('7/27/2006 8:30:13 AM','MM/DD/YYYY HH:MI:SS AM')) * 24 hours FROM DUAL;
the output is:
Hours
8.50055555555556
But Actually it is 8.30
So how can i get exact days and time difference between two dates in Oracle?
Thanks....
Regards,
Suman Sakinala
Edited by: SSN on Sep 19, 2008 1:27 AM

Or more clearly (this time I have my date_from and date_to the right way around hehe!)
SQL> ed
Wrote file afiedt.buf
1 WITH t as (select TO_DATE('7/27/2006 05:00:15 PM','MM/DD/YYYY HH:MI:SS PM') as dt_to,
2                    TO_DATE('7/27/2006 08:30:13 AM','MM/DD/YYYY HH:MI:SS AM') as dt_from FROM DUAL)
3      ,d as (select (dt_to-dt_from)*24 as diff_hrs from t)
4 -- end of dates
5 SELECT TRUNC(diff_hrs) as hours
6        ,TRUNC(((diff_hrs) - TRUNC(diff_hrs))*60) as mins
7        ,TRUNC(((((diff_hrs) - TRUNC(diff_hrs))*60) - TRUNC(((diff_hrs) - TRUNC(diff_hrs))*60))*60) as secs
8* FROM d
SQL> /
     HOURS       MINS       SECS
         8         30          2
SQL>

Frequency response and phase difference

Hi,
I generate "Sine-Swept" with a function generator, which is the input of my device.
Then, I measure the output(vibration) via a photodiod (which is as voltage).
Now, I want to obtain FRF and Phase difference between these two wave (output and input).
In most of the examples, the input and swept has been generated by the software itself, but if the input has been acquired externally and also the swept has been done via a function generator, how would be the FRF?
I have installed "Sound and vibration toolkit", Could you please give me a heads up, that how can I do that?
In advance, I really appreciate your help,
Petar

Hi,
I attached the project which I've recorded the data from DUTs. Also, I attached 2 snap-shots of the project, in case of the project file couldn't be launched.
I have connected the signal from a function generator to "ACH0" channel, and performed the swept-Freq in the output signal of function generator. (Red graph in 1st chart). Please note that the swept sine wave is generated via the function generator itself...NOT VI
The generated signal by the function generator is the input, which derives the oscillation of a drop,
A photodiode measures the oscillation of the drop via laser-scattering by drop vibration. SO....the signal generated by the photodiode is the "Response"....(white wave in 1st chart)(connected to "Ach1" channel.
Now, I want to obtain FRF, which the input is the signal generated by the function generator, and Response is the output of the photodiod'
As it's seen in the files...the FRF and phase difference is n't what is expected, also the coherence between in and output is zero!
Please help me out with this problem...
Thanks
Petar
Attachments:
12.seproj ‏419 KB
1.JPG ‏183 KB
2.JPG ‏177 KB

Miro hitting inventory and price difference

Dear All,
I would like to seek advice of the posting during MIRO on point 4 and 5 why there is a hitting on inventory account and price difference of the amount given? How system get the amount in inventory account and price difference account?
Really need advice.
1)
GR - qty 20
dr inventory $1500000
cr GRC $1500000
2) GI - qty 1 and now remained only 19 qty
moving price = $75,000
qty = 19
price unit = 1
value = $1425000
3) MIRO
dr GRC $1500000
cr vendor $1500000
4) MIRO say qty is 21 and amount no change
dr GRC $1571429
cr vendor $1500000
cr inventory $64626
cr price diff $6803
5) MIRO say qty is 20 and amount i enter $1507500
dr GRC $1500000
cr vendor $1507500
dr inventory $7125
dr price diff $375
thanks

refer my remarks in BOLD
4) MIRO say qty is 21 and amount no change
This scenario is not possible as you have taken GR for Qty 20 only.
*still you have added $ 71429 in GRC so this should be uploaded on Inventory ($71429 / 21 = 3401.38) hence Inventory account will get updated with $3401.38 * 19 (available stock) ie $ 64626 & diff of 21 - 19 = 2 * 3401.38 ($6803) will be updated in Price Diff account*
dr GRC $1571429
cr vendor $1500000
cr inventory $64626
cr price diff $6803
5) MIRO say qty is 20 and amount i enter $1507500
* Goods receipt is posted with 1500000 but vendor has presented invoice of 1507500 hence the additional cost ie 7500 has to be loaded on inventory but available inventory is 19 as 1 qty is already issued from stock hence (7500/20 = 375) for 19 qty inventory account will updated with $7125 (375*19) & for material which is already issued prior to taking invoice receipt ie 1 Qty (375 * 1) = 375 will hit to Price Diff Ac.*
dr GRC $1500000
cr vendor $1507500
dr inventory $7125
dr price diff $375

Landed costs and price differences

I'm trying to figure out what PS does to adjust for total value discrepancies between an invoice voucher and associated PO. Say on my PO I have a line item with quantity of 2 and unit price of $10. Therefore total value is $20. When I create a voucher, that same line item is now 2x$11 = $22. I approve that voucher for $22. Now I run the Extract Landed Cost batch process. What does this process do to "compensate" for the difference between voucher and PO? Does it change the unit price of that item in inventory from $10 to $11?

Hi, yes you are right: Using this approach ML would use price differences for other batches and increase their value instead of posting them as loss like the initial cost.
The way around that would be to post some unplanned material good receipt for the loss production order, e.g. a material called scrap. In account determination you might make sure that these materials have own stock and price difference accounts that you could treat special in your balance sheet.
This would be shown in ML like a joint production between the planned product and the scrap material and multi-level variances would be distributed using following an apportionment structure from material master.
If it is difficult to maintain a reasonable apportionment structure you might implement BADI cost_split described in note 997264.
Also a good possibility would be to use a quantity-proportional split that can be derived from the ML quantity structure.
I could provide an example implementation of that.
best regards, Udo

Transfer (IDocs and TRFC): Missing messages or warnings

Hi,
While loading data from ECC to BI, I'm getting the following Error. It is for all DataSources...even for Full loads with 15 records also.
Requests (messages): Everything OK
Extraction (messages): Missing messages
-->Missing message: Request received
-->Missing message: Number of sent records
-->Missing message: Selection completed
Transfer (IDocs and TRFC): Missing messages or warnings
Info IDoc 1 : sent, not arrived ; Data passed to port OK
Info IDoc 2 : sent, not arrived ; Data passed to port OK
Info IDoc 3 : sent, not arrived ; Data passed to port OK
Info IDoc 4 : sent, not arrived ; Data passed to port OK
Request IDoc : Application document posted
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
Processing (data packet): Everything OK
Data Package 1 ( 10 Records ) : Everything OK
Note: I tried with following options, so please don't repeate again.
1. No LUWS in ECC in SM58.
2. Connections are OK an dtested in SM59.
3. WE20 is also OK.
4. Job Finished successfully in ECC.
5. No Dumps in ST22 in ECC.
6. Dumps in BW in ST22.
Error Message is:
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSSM" or "LRSSMU36"
"RSSM_OLTPSOURCE_SELECTIONS"
7. Tried with BD87 in ECC and BI also.
Thanks
Ganga

Hi,
Every thing is fine. And I searched for OSS note and I found some notes but I'm unable to resolve it. My data Target is Cube and DSO's.
Note 852443 - Dump in include LRSSMU36 RSSM_OLTPSOURCE_SELECTIONS
Note 869628 - Constant WAITUPDA in SMQ1 and performance optimization
Note 901878 - Information IDoc Sent, but did not arrive
Note 913330 - tRFC LUWs are not created
Thanks
Ganga

Transfer(IDocs and TRFC) error when use infopackage to load data from R/3

I create an infopackage to load data from R/3, when start immediately ,there is no data transfered. The return error is :
transfer(IDocs and TRFC): Errors occurred
request IDoc: Application document not posted
Does anybody know how can correct this error?
Thanks great.

Hi Yimeng,
Check in SM58 transaction code in R/3 and see if any LUWs are stuck there. If so you can execute them manually and complete the data load.
regards,
Sumit

Error in Transfer (IDOC and TRFC )

Hi experts
I am getting the error in Transfer (IDOC and TRFC ) Info IDoc 1 : Sent not arrived : Error posting data to port" when I am trying to Upload data by executing an infopackage.
Pl. advice.
Thankls in advance
Dinesh Sharma

Hi Dinesh,
This latest error code E0 266 & is really a Basis one (BC-MID-ALE); not BW.
If the error occurs all the time then please do the following.
Firstly, please ensure that the relavant RFC destination is set up as per SAP Note 613389. The use of a logon language is a must.
Secondly, please also add the value of SCP2 as well as SCP5 to the role of the RFC user as per Note 784381 (SCP2 isn't mentioned in the note but please add it anyway) - This should resolve your issue.
If you only see this error sometimes, then set the flag in tcode OYEA as per Note 784381.
Hope this helps,
Colum

Credit memo - Price and quantity difference on the same PO item

Hello,
When there are both price and quantity differences between the invoice and the PO/GR on the same PO item, we need two lines on the credit memo to adjust the quantity and the price separately. However, the system gives the error message "Document contains same order item more than once" . If we suppress this message, then we have the error saying the debit and credit of the credit memo does not balance, as it appears the system only read the first credit memo line and ignore the second. Does anyone know how to resolve this (without having two different credit memos for the price and quantity differences)?
Thank you.

Hi,
Please note the following few points.
1.Credit Memo: Credit memo will be posted when you want to reverse a posted invoice.System will reverse the qty and that much amount of invoice.you can post two line items of MIRO for a sigle PO item for qty and amount.you can not have two lines one for qty and other for amount.
If you feel that there is a differance of posting in amount for the INVOICE and GR (normally for GR , the amount postings witll be same as PO price.) reverse the invoice at MR8M or post a credit memo in a single line for amunt and qty and post afresh the invoice amount .
Regards,

What is the conceptual and functional difference between peripheral target and Enterprise peripheral target?

Dear All,
what is the conceptual and functional difference between peripheral target and Enterprise peripheral target?

Does anyone get a chance to see this ?

QRFC and TRFC Difference...

Similar Messages

Maybe you are looking for