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

Similar Messages

  • Configuring IDOC and RFC Adapters in both Sender and receiver side

    Hi ,
    Kindly tell me the steps to configure IDOC adapters in sender as well as receiver side.
    Similarly for RFC adapters.
    Regards,
    Sweta

    Hi,
    >>>Kindly tell me the steps to configure IDOC adapters in sender as well as receiver side.
    kindly try searching for them first yourself (there are tons of docs for that and similar questions)
    and come back if you any further issues
    Thank you,
    Regards,
    Michal Krawczyk

  • Difference between idoc and rfc

    what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

    IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. 
    IDocs are used for asynchronous transactions:  Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. 
    Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions. 
    A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another. 
    IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands. 
    An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
    layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. 
    The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system
    RFC
    Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
    note:reward points if solution found helpfull.....
    regards
    chandrakanth.k

  • Difference between Seeburger FTP and OFTP adapters

    hi,
    Can anybody tell me the difference between Seeburger FTP and OFTP adapters?
    On what basis should one make a business decision as to which adapter to go for?
    Kindly help urgently.
    Regards,
    Loveena

    Hi ! Loveena
    Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.
    Seeburger Adapters are used to Connect the applications which are using Message protocol/Transport protocol as CrossIndustry(payment), VAN, OFTP, AS2(EDIINT), Generic and EDI based applications.
    Re: Seeburger Adapter
    Reg seeburger seeburger
    installation
    https://forums.sdn.sap.com/click.jspa?searchID=2268965&messageID=3210111
    OFTP ist a communication protocol. This has nothing to do with the format you have to transfer.
    regards the format you have to clear at which standard you have to transfer the messages. This can be any EDI format. At OFTP area the standard are often VDA or ODETTE.
    You can create this messages using different EDI adapters (of course also the mendelson adapter ).
    Regards OFTP you need additional software which handle the transfer based on the OFTP standard. Mostly you also need an ISDN card for using this protocol.
    We can support you with this software for OFTP transport too.
    More info also available at http://www.mendelson-e-c.com/.
    have a look at the ACTIS OFTP Adapter
    Ref: http://www.actis.atosorigin.de/solutions/en/ACTIS_solutions/SAPXI.php
    refer this thread also
    When we need Seeburger AS2 & FTP?
    XI Seeburger adapters
    Adapter for OFTP?!
    Thanks !!

  • Hi friends,  IDOC and RFC are sap related.but idoc is in abap stack rfc is

    1)IDOC and RFC are sap related.but idoc is in abap stack rfc is in java stack.what is difference between two.?

    hi ganga,
    The IDoc adapter is used by SAP systems to connect to a centrally configured Integration Engine using IDocs
    which is properitory to SAP integration
    so it doesn't need the Adapter engine.
    refer:
    http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm
    The Adapter engine is working on the J2EE Engine.
    RFC Adapter is provided by the AdapterEngine.
    So RFC needs Java Runtime where IDoc doesn't.
    refer:
    http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/frameset.htm
    regards,
    nikhilbos

  • Question on IDoc and RFC

    Hi Folks,
      I have few questions on SAP XI.
    1) For IDoc and RFC, why we need to import the metadata again even though we import RFC and IDoc in intergration Repository?
    2) Why we don't need to create Message interface and Message type for IDoc and RFC?
    3) Why RFC and IDoc comes in different namesapce, not in the namespace in which they are impoeted?
    4) For IDoc we need to import metada in tran IDX2. Why the same is not in case of RFC? In case of RFC we need to specify metadata repository parametes in Communication Channels.
    Thanks,
    Punit

    Answer 1) IDoc (Intermediate Document) metadata comprises structures for the corresponding IDoc types that are required by the IDoc adapter to convert these IDocs to IDoc XML format and the other way around
    Answer 4) The adapters are configured in the configuration part of the Integration Builder, or in the configuration part of the PCK. You use the SAP Java Connector (JCo), which enables you to manage metadata. This in turn enables you to map RFC data generically to RFC XML and the other way around.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm.
    Regards
    Abhishek Mahajan
    **Reward points if helpful**

  • ALE/IDOC and RFC/BAPI Integration Scenarios with SAP DS for ESA v3

    Hi,
    we are planning two PoCs of Integration Plattforms. One of our major requirement set is SAP Integration into our existing SOA.
    Because we also have R/3 4.7 Systems in production, we are planning to test ALE/IDOC and RFC/BAPI Integration scenarios with these Integration Plattforms.
    My question is:
    We are looking for are smart solution to get a SAP Test Environment, where we can test ALE/IDOC und RFC/BAPI Integration scenarios.
    It is possible to do this with SAP DS for ESA v3 or shall we better use IDES for that purpose?
    Best regards,
    Steven

    Hi Abhishek,
      This is our scenario. We are doing an integration of SAP HR r/3 system with the CRM system. We need housing information details of the employees which we have in custom infotype 9310 in SAP HR system and we need those details in the CRM system. So am planning out for an ALE/IDOC approach for the integration and gonna  maintain the 9310 details in a custom table. In the CRM system, we gonna build a BOL layer for accessing the 9310 details. Also i'm preparing a HLD for this process. I wanna read and go through few same HLD's before i submit my proposal to my client. Please suggest me and help me out.
    Thanks in advance.
    Regards,
    Arunmozhi.

  • How to use IDOC and RFC adapter in 1 scenario?

    We have AAA field and BBB field and we want to send AAA field to receiver sap system using IDOC adapter and BBB field to receiver sap system using RFC adapter. But how to use IDOC and RFC adapter in 1 scenario and how to map and  what are the design and configuration objects we require to create?

    To achieve this you have to use
    Two Interface Determinations
    Two Communication Channels (IDOC & RFC)
    & Two Receiver Aggrements.
    Use the Enhanced Interface determination and give your conditions there. Based on you condition your interface mapping will be triggered and data will be sent to IDOC & RFC respectively.

  • How to decide which adapter to use from IDOC and RFC?

    Hi All,
    When interating XI with an SAP system,
    How to decide which adapter to use from IDOC and RFC?
    Thanks.

    Hi,
    you can also consider to use ABAP Proxy if you are working with Systems based on SAP Web AS 6.40.
    Here some useful links:
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/02/265c3cf311070ae10000000a114084/content.htm">ABAP Proxy Runtime</a>
    ABAP Proxies in XI(Client Proxy)
    /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
    ABAP Server Proxies
    /people/siva.maranani/blog/2005/04/03/abap-server-proxies
    How do you activate ABAP Proxies?
    /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    XI: Reliable Messaging EOIO in ABAP Proxies
    /people/arulraja.ma/blog/2006/08/18/xi-reliable-messaging-150-eoio-in-abap-proxies
    More links for proxy:
    proxies and performance...
    Hope this help
    Francesco

  • IDOC and RFC/PROXY Scenarios

    Is there a way to practice IDOC or RFC Scenarios if you only have access to the XI System? So you have XI abap and Java but no R/3 System...
    Can someone tell me how I can practice IDOC and RFC scenarios please

    It is possible to practive IDOC & RFC scenarios with XI's abap stack as sender & receiver of IDOCs and RFCs with the "XI" in the middle....
    However, the problem might be the IDocs & RFCs might have to be created from scratch to test these out....
    If you have some IDOcs that you can use in XI abap stack, have the program that generates this IDOc and when(if) XI abap stack receives this, the processing module to process this IDoc...
    Similarly, the RFC FM has to be available on XI ABAP so that it can bhe invoked from the RFC interface..
    Thanks.
    Message was edited by:
            Renjith Andrews

  • Do we need to create message interfaces for idocs and rfcs thatare imported

    do we need to create message interfaces for idocs and rfcs thatare imported
    from sap server
    in scenarios from sap system to file or vice versa
    i knew that we need not create message types
    do we also skip creating message interfaces

    hi,
    you create an abstract message interface for IDOC only if you want to use
    them in a BPM (integration process)
    for more about IDOCs have a look at my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Automatic generation of Proxies and RFC Adapters after change

    After a maintenance on the server, or new transports on the xi, uploading new RFC function modules often the Proxies and RFC Adapters have to be restarted.
    If you are not aware of that kind of changes the messages arrive in the wrong format, funny things happen and so on...
    Question: Is it possible to scedule a job on the xi which automatically generates all proxies and adapters new in order to minimize message/service errors after uploads and changes?

    Did you run program RIMODGEN in SE38 with appropriate variant to generate new integration models ? The spro settings or CFC9 have nothing to do with generation of new integration models. try to do some forum search on Integration Models and you may get some clue.

  • Idocs and rfcs thru proxies

    could any one send examples of how to use idocs and rfcs via proxies

    Hi,
    Refer the following Article.
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93d4e690-0201-0010-8abb-8057c8608803">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93d4e690-0201-0010-8abb-8057c8608803</a>
    Regards,
    Sudharshan

  • Principal difference between an Idoc and a Switch document.

    Hello
    what is the principal difference between an Idoc and a Switch document.
    Thanks

    Hi,
    A switch document documents a process, such as, switch of supplier, in a liberalized market and can be monitored with own transactions. The process steps are usually controlled by workflows.
    An IDoc is used to transfer data from one system to another one in a predefined package. When you import an IDoc containing a market message, a workflow can be started creating/updating switch documents.
    Kind regards,
    Fritz

  • Difference between Master Idoc and Communication Idoc.

    Can anyone list out the difference between Master Idoc and Communication Idoc?

    IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
    Form and content: IDoc terminology
    As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
    A message refers to the contents of a specific implementation of an IDoc; it’s a logical reference. This differs from a reference to the IDoc itself, which specifies the message’s physical representation. Think of it this way: If you’re watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayor’s limousine (which is specific to the mayor) is the IDoc. You’re building a logical object, and the IDoc is both its container and the vehicle that moves it.
    The IDoc control record
    Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDoc’s functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI
    Layout of an IDoc control record
    This “cover slip” format informs the receiving system of the IDoc’s purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
    Data records
    The data records following the control record are structured alike, including two sections: a segment information section and a data section.
    In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner company’s Oracle system, which has no such data dictionary.
    The second part of the record is the data itself, a storage area of 1,000 characters.
    Status records
    If you’ve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, you’re familiar with the list of stops and transfer points through which a package passes on its way to you.
    This collection of records is exactly what you’ll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
    Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records are used to record these errors and the date/time of their occurrence.
    IDoc Base
    IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
    This “IDoc Base” gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
    Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
    Multiple messages
    One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
    IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, it’s no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
    A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system Records in a multiple-message IDoc

Maybe you are looking for