Difference among qRFC, tRFC and  RFC?

Please help. I am sorry if this is too basic because I do not have too much experience on them.
Thanks a lot!

Hi,
This is a much too vast subject to be explained with a few lines forum message.
You'll have to do a lot of reading and you could start here :
[RFC Help|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/22/042578488911d189490000e829fbbd/frameset.htm]
Regards,
Olivier

Similar Messages

  • DIFFERENCE B/W  IDOC  AND RFC   ADAPTERS

    HI FRIENDS,
    WHAT IS THE  DIFFERENCE B/W   IDOC  AND  RFC   ADAPTERS..? AND WHICH ONE IS
    PREFERABLE  TO USE    IN TRANSFERING DATA FROM THIRD-PARTY SYSTEM TO  SAP.?
    REGARDS,
    RAMAKRISHNA.

    Hi
    These links will help you to understand :
    http://help.sap.com/saphelp_nw04/helpdata/en/11/028417f9f8b24cbe1b0b398e1cb76a/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
    Please dont forget to reward with points.
    Edited by: Dheeraj Kumar on Mar 3, 2008 2:59 PM

  • Difference between Web Services and RFC (both Advantages & Disadvantage)

    Hi All,
    will you please explain the difference between  Web Services and RFC (both Advantages & Disadvantage)
    Thanks,
    jyothi.

    Hi,
    If you want have a communications between SAP systems within a network, we can go for an RFC.
    If you want have communication between SAP systems through a medium like internet, we can probably go for a webservice.
    Please refer the following links:
    What is the difference between RFC vs. Web service ?
    Webservice
    If you want to convert an RFC fuction module to an webservice, you can refer the following link,
    Using RFC as WebService in WebDynpro
    Hope this will help you.
    Regards,
    Jithin

  • Difference between tRFC and RFC

    Hi Experts,
    Can any one help me in details to differentiate tRFC from RFC in their application perspective.
    And also let me know the role of ALE and BAPI in both the connection log.ie,Where we have to use ALE and BAPI.
    Regards
    Kumar

    Hi,
    RFC = Remote Function Call and TRFC = Transactional Remote Function Call
    Transactional RFC and Queued RFC are variants of the Remote Function Call that make the data transfer between different SAP R/3 systems more reliable and more secure.
    Transactional RFC 
    http://help.sap.com/saphelp_nw04/helpdata/en/8b/ceea3b31aac554e10000000a114084/content.htm
    RFC Help link
    http://help.sap.com/saphelp_nw04/helpdata/en/b0/eae2a889e711d2956500a0c94260a5/frameset.htm
    Refer BAPI & ALE
    what is difference between BAPI and ALE
    Re: ALE & BAPI communication
    Re: bapi-ale interface
    /Srinivas

  • Difference among BDC eCATT and LSMW

    Hi guys,
       May I have your attention please?
       I encounter difficulities regarding the relation among the above Data Transfer Tools.
       So far,I have learned a little about these tools, and done some data batch input from
    local drive.I find the three tools can deal with the same thing. So my question is what
    distinction exists among them since they are similar so much?
      Thank you

    Refer these links might be useful -
    Differences between  BDC , LSMW, BAPI,CATT
    LSMW Vs BDC
    Difference between BDC and LSMW
    Regards,
    Amit
    Reward all helpful replies.

  • What are the difference among SDMJ, SDHF and SDTM?

    Experts:
    Would you please help explain what are their differences?
    I cannot find their definition.
    Thanks a lot!

    >
    Ashley Ho wrote:
    > Experts:
    >
    > Would you please help explain what are their differences?
    >
    > I cannot find their definition.
    >
    > Thanks a lot!
    Hi Ashley,
    Transaction type SDHF is an urgetn correction.  It is a transport that can go straight through to Production with only unit testing.
    Transaction type SDMJ is a normal correction.  It is a transport that will go to Production as part of a release cycle, usually with other transports.
    Transaction type SDTM is a test message.  This type of correction is created when a normal correction (SDMJ) has some sort of issue which needs to be corrected prior to moving it to Production.  Because the transport for the SDMJ has already been released, it will go through to Production regardless of issues.  The SDTM correction allows you to send the correction through simultaneously with the original transport so no adverse effects are seen in Production.
    Best regards,
    Lori Sanders

  • What is the difference among RSA7, SMQ1 and SMQ2?

    I notice that RSA7 has more entries than the others.
    So what is their relationship?
    Thanks!

    Hi Christy,
    Have a look at this document from August 2009:
    "Delta Queue Demystification"
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/40427814-376a-2c10-5589-bc1aaa6692c3&prtmode=print
    It explains what you see in RSA7 and how it all works with the delta queues. Excellent document.
    kind regards,
    Ralf

  • What's the difference among SDM, JSPM and DeployTool?

    Hi!
    I do not understand why we cannot just have a single tool  to do the java deployment exclusively?
    Please advise. Thanks!

    Hello Jennifer,
    Here is the detailed information about each of these :
    JSPM
    http://help.sap.com/saphelp_nw70/helpdata/en/25/c45b4211aac353e10000000a1550b0/frameset.htm
    SDM
    http://help.sap.com/saphelp_nw70/helpdata/en/22/a7663bb3808c1fe10000000a114084/frameset.htm
    Deploy Tool
    http://help.sap.com/saphelp_nw70/helpdata/en/22/a7663bb3808c1fe10000000a114084/frameset.htm
    In short, If you want to update the SP level of j2ee engine, you would use JSPM. JSPM uses SDM for the deployment however, it takes care of the sequence of the SCAs and lot more checks.
    If you want to deploy a single SCA/SDA/EAR, you would use SDM.
    Deploytool was used in 6.20 extensively for the EAR deployment. You don't use Deploytool directly anymore in later releases.
    Hope this helps.
    Regards,
    Snehal

  • What is difference among LCA, LDA and LEA?

    Please help. Thanks!

    Hi,
    LCA, LDA and LEA are the Live cache connections
    [live cache|http://service.sap.com/instguides]
    Thanks
    sreenivas
    Edited by: Sreenivasu on May 7, 2009 1:42 PM
    Edited by: Sreenivasu on May 7, 2009 1:44 PM

  • Difference among graph,char​t and XY graph

    The difference among graph,chart and XY graph
    I am doing a data collection work . And I need to draw a graph or a chart with the data . But I can't make a choice.
    If I draw a real-time graph, which is the best.  And in which situation I use the others.
    Thanks a lot !!!

    They are not a compactly definiendum. as your test station's condition to select.
    draw a real-time graph, I suggest that Chart is OK.  as a data in. it will draw a point out.
    Try to make everything Automatic

  • Logical system and rfc destination

    hello all,
    what is the difference between logical system and RFC destination?
    thanks for ur help in advance.
    regards,
    vikas

    Hi,
    In any ALE scenario u need one sender and one receiver system.
    Logical systems are just logical representation of these systems but in case of RFC destination u specify technical parameters for those systems like IP address and username and password to connect to that system.
    Thus when u create port i.e.we21 u specify actual RFC destination for the system to which u want to connect and when u create partner profile for that logical system u specify this port so when u want to send data to this logical system i.e receiver system port will be used which in turn has RFC destination which will be used to connect to that system.
    In simple terms logical systems are logical representation of any system and RFC destinations are physical/techinical systems.
    Regards

  • ALE/EDI and RFC

    Dear All,
    Please, can anyone tell me what is the difference between ALE/EDI and RFCs?
    Thanks in advance.
    Kind Regards,
    Umesh.

    Hi prasad,
    1) ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
    2) In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself.
    These r some major difference b/w ALE and EDI:
    ALE: used to transfer IDOC with in the R3 distributed system.
    EDI: used to transfer IDOC from R3 system to non sap system
    ALE --This method is used to transfer master data
    EDI--This method is maximum used to transfer transactional data.
    ALE--RFC port is used
    *EDI*-- FILE port is used
    ALE--Data transfer takes place from one mother client to N different clients
    EDI-- one partner 2 other partner thru customer distribution model
    The philosophical difference between EDI and ALE can be pinned as follows:
    If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to
    reliable replicate data between trusting systems to store a redundant copy of the IDoc data.
    The difference is made clear, when we think of a purchase order that is sent as an IDoc.
    If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order.
    However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
    ALE
    ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. When a new enterprise resource planning (ERP) solution such as R/3 is implemented, companies have to interface the ERP system with legacy systems or other ERP systems.
    ALE provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data.
    ALE technology facilitates rapid application prototyping and application interface development, thus reducing implementation time.
    The ALE components are inherently integrated with SAP applications and are robust, leading to a highly reliable system.
    ALE comes with application distribution/integration scenarios as well as a set of tools, programs, data definitions, and methodologies that you can easily configure to get an interface up and running.
    ALE allows for efficient and reliable communication between distributed processes across physically separate SAP systems.
    ALE is based on application to application integration using messaging architecture. A message defines data that is exchanged between two processes. IDocs are containers that hold data exchanged between the two systems.
    Benefits of ALE:
    • Integration with non-SAP systems: ALE architecture allows third party applications to integrate with SAP system.
    • Reliable Distribution: Once message type created and the receiver of the message is determined, ALE delivers the message to the recipient. If there is any network problem it will buffer the message and delivers the message once the network is restored. It also ensures that the message is not delivered twice.
    • Release Upgrade: Any of the distributed system can be upgraded to the new release of SAP without affecting the functionality. The ALE layer ensures backward compatibility of messages exchanged between systems.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
    REWARD IF USEFUL
    THANKS AND REGARDS
    SUMA SAILAJA PVN

  • Difference among  BAPI,,ALEand EDI

    HI ALL.
    please tell me difference among bapi, ale and edi
    and  also send me the material on those topics,
    please help me
    regards
    hussain

    Hi,
    1) ALE = Application Link Enable: Initially developed for SAP as an abstract layer to extract master and transactional data to be sent ellectronically to other SAP systems. These days is also being used to send data no non-SAP systems. ALE is not a protocol or anything like that, it's just abstract layer composed by a set of applications which are capable of extracting aplication data on a 1-time basis or periodically, by selection criteria or incrementally by deltas.
    2) In contrast, EDI = Electronic data interface, this is a comunication protocol not designed by SAP but it´s an industry standard. Of course most SAP software supports EDI, but EDI it's no software but the specification of the protocol in itself.
    ALE- is used in scenarios between R/3 and R/3
    EDI- is used in scenarios between R/3 and non R/3
    BAPI:SAP has introduced object-oriented technology in the R/3 System by making R/3 processes and data available in the form of SAP Business Objects.
    External applications can access SAP Business Objects through standardized, platform-independent interfaces - BAPIs. SAP Business Objects and their BAPIs provide an object-oriented view of R/3 business functionality.
    Hope this helps.
    rgds,
    latheesh
    Message was edited by: Latheesh Kaduthara

  • Diff among I_T_DATA, E_T_DATA and C_T_DATA?

    Hi,
       Differences among I_T_DATA, E_T_DATA and C_T_DATA?
    Thanks in advance
    Jani SK

    I_T_DATA used in MAster data Datasource with attribute,
    E_T_DATA used in MAster data Datasource with Text
    and C_T_DATA used in Transactional Datasource

  • Difference between TRFC and QRFC

    Dear all,
    i understand that TRFC functions as EO and QRFC functions as EOIO.
    but can anyone of u pls make me understand there significance with a practical example :
    1. in terms of XI
    2. without XI when we say that one R3 is connected to other with say TRFC or QRFC
    pl help

    Hi! Tarang,
    I just adding few points in this forum...Actually your question and some of the answers given are different .Some of them are deviating the topic.
    According to my knowledge and as per SAP documentations also I am adding these points. Correct me if I am wrong.
    At first QRFC , TRFC are different from the BE, EO and EOIO because trfc are message protocols and BE , EO and EOIO are nothing but Quality of Services (QOS).
    You can check this in the below URL::
    http://help.sap.com/saphelp_nw70/helpdata/EN/0d/5ab43b274a960de10000000a114084/frameset.htm
    QOS is one of the property of TRFC's.
    1) See Got o SMQ1 an SMQ2 what you will found:: ?
    QRFC Monitor Outbound Queue and QRFC Monitor Inbound Queue. both Queues QRFC s common.ok its a simple thing.
    2) Also lets take IDOC Adapter for IDOC whether it may be File to IDOC or IDOC to File Scenario where you will monitor the IDOC in SM58 also right ? why because this TRFC's are mainly for communicating with one SAP system to another SAP System. IDOC is mainly sending data via TRFC ports. That is why you ill monitor the IDOC if data doesn't reached means in Transaction COde:: SM58.
    3) QRFC Outbound and QRFC Inbound is mainly for communicating with SAP System and Non SAP Systems. Okay you can get this information in the below further explination and link.
    Note::qRFC communication is an extended form of tRFC communication. It adds a serialization concept to the transactional concept of tRFC.
    http://help.sap.com/saphelp_nw70/helpdata/EN/3b/befa40badbf46fe10000000a1550b0/frameset.htm
    Some applications use qRFC with outbound queue to improve system performance and not for serialization. If this is the case, you can switch automatically from the qRFC LUW with outbound queue to the tRFC LUW to avoid a hanging queue if a SYSTEM_FAILURE occurs
    Note:: To cancel a background job if tRFC errors occur use program RSARFCEX to restart tRFC.
    First What is the purpose of RFC:: ?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.
    There are 3 types of communications::
    Communication within an SAP system or with a remote system can take place using Remote Function Call (RFC). This enables the following scenarios:
    ·      a)  Communication between two independent SAP systems
           b)  Communication between a calling SAP system and an external receiving system
           c)  Communication between a calling external SAP system and an SAP system as the receiving
                system
    Features of the Three Communication TypesTo 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:
    ... 1)      tRFC
    Suitable only for independent function module calls; the sequence of the calls is not preserved
    ·   2)   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.
    ·   3)     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.
    http://help.sap.com/saphelp_nw70/helpdata/EN/3b/befa40badbf46fe10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw70/helpdata/EN/e7/555e3c0f51a830e10000000a114084/content.htm
    XI point of View...
    Basically Once the TRFC or QRFC is funtion is over XI will place the Message into the Adapter engine queues based on the Comminication channel configuration.
    Suppose if it is and EO then XI ill place the message in any  Queue based on the free and priority and if configuration is done as per EOIO then XI ill place all the messages in the Same queue name so that it ill processes in order one after another and if the above message fails and remaining all other messages will be in the queue and doesnt process untill the failed mesages gets removed
    But in case of  EO it may be places in any queue and if one message fails then another message of same interface may processed sucessfully based on another queue order.
    I hope it wil be helpful to you...
    Regards::
    Amar Srinivas Eli

Maybe you are looking for