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.

Similar Messages

  • Different between ALE, IDOC and BAPI?

    Hi Folks,
    What is the different between ALE, IDOC and BAPI? and send me the following steps?
    Thanks in advance.
    Siva

    Hi,
    please read the below lines.
    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.
    BAPI
    BAPIs provide a stable, standardized method for third-party applications and components to integrate into the Business Framework. These interfaces are being specified as part of SAP's initiative with customers, partners and leading standards organizations. Also, SAP has implemented the emerging Object Application Group (OAG) specifications with BAPIs.
    Pros and Cons for both BAPI and Call Transaction
    BAPI
    One of the big plusses for BAPIs is that the interface and function are not supposed to change.  This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction.
    Some of the BAPIs are better documented and easier to use than others.
    You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI.
    The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction.
    You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that.
    BAPIs probably have better performance since they don't do the screen flow processing.
    In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go.
    This is just from my experience working with both BAPI and Call Transaction.  I have had some very good successes with BAPIs, but very occasionally found that I could not get the BAPI to perform the update I needed.
    Regards,
    Anki Reddy.

  • 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

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

  • ALE,IDOC's,EDI,BAPI.

    hi,
    can u help me in getting information about cross applications.
    what is cross application indeed.And i want know about ALE,IDOC's,EDI,BAPI.
    and what is the relation between RFC AND IDOC.
    thanks

    Hi Satya Reddy
    This will expalin you every thing ...pl..go through
    IDOC-Intermediate documents
    BAPI-Business ApplicationProgramInterface
    BADI-Bsuiness Addins
    RFC-Remote Function call
    ALE-Application liniking and enabling
    The interface concept of the classic R/3 is based on two different strategies: 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.
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    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.
    Also refer Ravi's weblog
    /people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
    XI Customer Polling 2006 – Summary of Results
    /people/swen.conrad/blog/2007/01/26/xi-customer-polling-2006-150-summary-of-results
    Please see the below links
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    In " XI"
    IDOC ---> Will be used to sending data in Async mode ...
    It is very standard and for better performance Async case
    RFC --- > Function module and general will be used to make call to function
    sending the function (XI has RFC adapter)
    BAPI ---> Other version of RFC (Objected oriented) mostly we will use for Sync
    calls (Mostly in XI using proxies we will call BAPI's)
    I hope this will answer your question
    regards
    --- prasad

  • 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

  • How to trigger automatically an IDOC and RFC from SAP R/3 system?

    Hi ,
    lets say if we are implementing IDOC to FILE &RFC to FILE scenario ,how can we trigger  on timely basis(schedules)
    1)standard IDOCs and BAPIs?
    2)customized Idocs and Customized Bapis?
    3)Master Idocs and transactiona Idocs?I think we need to use change pointers for master Idocs and donno about Transactional Idocs.
    please explain ,
    thank you very much for your help.
    regards,
    Babu

    sorryfor the late reply, I was busy with my work.thank you for your posts.
    so all of you say just run the RSEOUT00 no matter what interface we use in XI like Master ,transactional Idocs,standard or customized BAPIs?
    And I think we use RSNASTED if we have on recieving side right?
    <b>then when we would use a report of format below to trigger an RFC,is this format for Asunc RFC ?</b>
    REPORT Z_SEND_DATA_TO_XI.
    parameters: dest like rfcdes-rfcdest default '(RFC Destination you defined in SM59)'.
    <<your other variable declaration and ABAP Code here>>
    call function 'ZXI_SEND_DATA'
    in background task
    destination dest
    exporting
    Name = John
    City = Smith. (The values to pass to XI)
    commit work.
    <<Any Write statements or sy-subrc statements here>>
    6) Save and Activate your ABAP program.
    6) After all these steps, execute your ABAP Program to send the data to file via XI.

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

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

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

  • 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 importing error

    when i try to import idoc or rfc  iget this kind of error
                 **Ready for import**
    Import started...
    BAPI_COMPANYCODE_GETDETAIL:
      + com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: The function module "DD_DOMA_GET" not released for 'remote' calls.
    Import failed with 1 error
    pls any body can help me ls

    Hi Sri,
    for your problem, you can just refer the thread as mentioned below:
    The FM "DD_DOMA_GET" not released for 'remote' calls.
    General question:  XI -> older SAP systems?
    If you are replicating the data using standard idoc then you can use the standard option avialable transaction name as "MDM_CLNT_EXTR" shipped by SAP itself.
    I hope it will help you.
    TNR,
    Saurabh...
    Edited by: Saurabh Kumar Sahu on Feb 4, 2008 12:54 PM
    Edited by: Saurabh Kumar Sahu on Feb 4, 2008 12:57 PM

  • RFC Sender and RFC Receiver Sync Scenario . Help required.

    Hi,
    I need to make RFC Sender and RFC Receiver Sync Scenario.
    Any docs/links for it.
    Regards

    Hi,
    I have CRM (r/3) and DM (r/3)system.
    Data from differnent tables of CRM system needs to go to
    DM system different tables , data will be saved there and then return response back to CRM system.
    For this I have given one RFC for CRM system
    For this I have given one RFC for DM system
    So I have to make Sync Outbound Interface
    and Sync Inbound Interface.
    So I think so no BPM is required.I am correct?
    Adapter -- RFC Sender and RFC Receiver Adapter.
    Regards
    Edited by: Henry H on Jan 29, 2008 11:20 AM

Maybe you are looking for

  • HT4437 airplay no longer works...

    Hi I have a bad wifi connection in the house so bought a powerline netgear booster- the signal is now much better but airplay no longer works. Airplay is set up with speakers throughout the house (wired in) with panels on the walls in different rooms

  • N-Level Parent-Child Aggregation

    Hi, We have an account table and a transaction table, the account schema is Account ID Account Name Parent Account ID The account hierarchy level is N-Level. The business user can add account/sub account. Account ID | Account Name | Parent ID 1 | FX

  • Customizing the ICH (UIBSP)BSP application

    Hi All, I am reposting my query here again.I have seen some postings related to this by PradeepReddy/Raja. Could somebody help me on this..... We have implemented the ICH and integrated it into the Portal.In this regard I want to link a BW report to

  • Missing API method writeStateMarker in ResponseStateManager

    API doc of interface ResponseStateManager says something about a method writeStateMarker(), that is not defined anywhere. Since the ResponseStateManager is the only one, that knows (and should only know!) about the implementation dependent state mark

  • Chkdsk partitions without drive letters

    Toshiba computers come with 4 partitions.  I've looked up the partition characteristics using the following:  - Disk Management  - PowerQuest Partition Table Editor  - Partition Type codes at    http://www.win.tue.nl/~aeb/partitions/partition_types-1