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.

Similar Messages

  • How to use ODI and Planning Adapter.

    How to load the dimensions in planning using ODI and Planning Adapter. I am just looking for a functionality that we used to have with HAL and Planning.

    Hi,
    Have a read of my blog it should give you all the information you need.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • How to Use IDOC and ALE in SAP?

    Hi anybody,
                     I want Use Idoc and ALE in sap ABAP. What is inbound and outbout process of IDOC?
    Please give me sample code for Idoc . and Sample code for ALE.
    anybody Please tell me.
    Thanks
    Regards,
    S.Muthu.
    IT Dept.

    hi,
    Follow the link for step by step ALE/IDOC tutorials.
    http://www.sapmaterial.com/idoc_sample.html
    http://www.****************/Tutorials/ALE/ALEMainPage.htm
    An IDoc is not a process.
    The term IDoc stands for intermediate document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. An IDoc is created as a result of executing an outbound ALE or EDI process. In an inbound ALE or EDI process, an IDoc serves as input to create an application document.
    IDocs are stored in the database.
    In the SAP system, they are stored in database tables. Several utilities are available to display the information contained in an IDoc and present it in different ways. For details, refer to Chapter 11, "Monitoring the Interface."
    Every IDoc has a unique number.
    When an IDoc is generated in the system, a unique number is assigned to it. This number is unique within a client.
    IDocs are independent of the sending and receiving systems. They can be used for SAP-to-SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data.
    IDocs are based on EDI standards, ANSI ASC X12 and EDIFACT, but are closer to the EDIFACT standards. The size and format of data elements in an IDoc type are derived from these standards wherever applicable. For example, if a material number is represented by 20 characters in an EDIFACT message, the corresponding data element in the IDoc is also 20 characters. If there is a conflict in data size between standards, the one with greater length is adopted. This approach ensures compatibility with most standards.
    IDocs are independent of the direction of data exchange. An inbound and an outbound process can use an IDoc. For example, the ORDERS01 IDoc is used by the Purchasing module to send a purchase order, and is also used by the Sales and Distribution module to accept a sales order. Using this technique avoids creating redundant IDoc types for the same information.
    IDocs can be viewed in a text editor and do not contain any binary data. Data is stored in character format. When transferred to the operating system, an IDoc is stored in a file in text format and can be viewed using a regular text editor. However, the contents make sense only if you understand the structure and format of the data in that IDoc. In the Appendix, "FAQs, User Exits, and Miscellaneous Resources," you will find an example of an IDoc file.
    Hope this helps, Do reward.
    Edited by: Runal Singh on Mar 5, 2008 6:09 PM

  • How to use JCO and RFC

    Hi guys, please help me out
    I'm new to JCO and do not have any idea about it.
    Here is my situation, for testing, I want to call an ABP RFC FM in SAP just to return a single text message to Java application through parameter.
    (Of course, I have access to SAP from my company and I do not have any Java compiler in my computer).
    From my understanding, there 2 main things to concern (Please correct me if i'm wrong and please tell me the steps I should do)
    1) Software installation and configuration
       What software do I need to install on my computer, is
       it JCO, SAPGUI, Java Compiler? What kind of
       configurations do I need for JCO?  
    2) Programming
       a) SAP side
          Write an ABAP RFC FM just to return a text message
          to Java application through parameters (No problem
          with this step)
       b) My computer side
          Write a Java application to call ABP RFC FM
          Do you guys have any simple source code example for
          this?? Please remember that this Java application
          simply call an ABAP RFC FM to get just a single
          text message.
    I really appreciate your help
    Thank you

    Hi Dean,
    USe Eclipse for Java programming.
    If you are downloading the latest version of JCO, make sure you have latest version of SAP Gui as there are version issues as the librfc.dll needs to be of compatible version.
    As far as your sample code is concerned, here it is ...
    import com.sap.mw.jco.*;
    public class CallFunction extends Object {
         public static void main(String args[]) {
              CallFunction app = new CallFunction();
         int count;
         JCO.Client mConnection;
         JCO.Repository mRepository;
         public CallFunction() {
              try {
                   // Logon info
                        mConnection = JCO.createClient("500", // SAP client
                                                   "username", // userid
                                                   "password", // password
                                                      null, // language
                                             "server name", // application server host name
                                                    "00"); // system number
                   mConnection.connect();
                   mRepository = new JCO.Repository("MY_connection", mConnection);
              } catch (Exception ex) {
                   ex.printStackTrace();
                   System.exit(1);
              JCO.Function function = null;
              try {
                   function = this.createFunction("ABAP_FM");
                     mConnection.execute(function);
                   System.out.println(
                        function.getTableParameterList().getValue("Exporting_Message"));
              } catch (Exception ex) {
                   ex.printStackTrace();
                   System.exit(1);
         public JCO.Function createFunction(String name) throws Exception {
              try {
                   IFunctionTemplate ft =
                        mRepository.getFunctionTemplate(name.toUpperCase());
                   if (ft == null)
                        return null;
                   return ft.getFunction();
              } catch (Exception ex) {
                   throw new Exception("Problem retrieving JCO.Function object.");
    Here in this mention ur function module in place of ABAP_FM and exporting parameter in place of Exporting_Message.
    Regards,
    Tanveer.
    Please please reward some points if found helpful.

  • 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

  • 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

  • RFC Sender problem  between 46D and RFC adapter

    Hi,
    I have this simple integration scenario where I want to send data to a archiving system;
    SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
    SAP side ***
    A Z-program using a Z func. like;
        CALL FUNCTION 'ZSD_DCF_SEND_TAG'
          IN BACKGROUND TASK
          DESTINATION 'XISYSTEM_TRFC_DCF'
          EXPORTING
            pt_filing_info = gt_filing.
        COMMIT WORK AND WAIT.
    XI side ***
    Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
    The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
    The problem in quality ***
    When sending just 1 msg, everything is just fine, message received and delivered to MQ.
    When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
    RFC_HISTORY
    - Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
    - OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
    My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
    It seems to me that the RFC adapter is kind of confused about the sender..
    I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
    - The SLD config. for bus.system Q93 is ok -
    - The bus.system in ID is showing correct vaues for
    Adapter Specific Identifiers (SID Q93, client 505)
    - Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
    - It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
    - It doesn't matter if I increase initial conn, max conn.
    I have also tried to use qRFC instead, but with the same result.
    Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
    Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
    Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
    best regards
    Torstein

    Hi,
    SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
    <i>Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
    A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".</i>
    - Give correct appserver and gateway service details in XI.
    - Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
    Regards,
    Prateek

  • Idoc and http adapter

    Idoc and http adapter resides in ABAP stack. So how do we monitor these two adapters ? It wont be visible in RWB ?

    Hi,
    To know the difference i suggest u try to do it by ur self only.
    Login in to Runtime Work bench- component monitoring-Adapter engine-communication channel monitoring- Filter the communication channel with name.
    and click on message id of that channel, it will show u the steps by step log for that channel.
    MONI is used for message monitoring.
    chirag

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

  • 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

  • HTTP and RFC Adapter are not Required Sender

    Hi All,
    I have one dought....
    Why Plain HTTP and RFC Adapter are not Required Sender Communication Channel and Sender Agreements...
    I Know this two Adapter are in ABAP Stack....
    Please clarify my dought...
    Regards

    Idoc Adapters do NOT require Sender Communication Channel.
    The Sender System identifies itself at the Integration Server, with the fields SNDPOR and Client of the Control Record.
    Sender Communication channels are used for communication betweeen the Application System and the Integration Server.
    In the case of Idocs, all idocs are tranferred to the Integration Server pipeline and NOT to the regular EDI/IDOC interface.
    The RECEVIER DETERMINATION is based on the values in the Control Record.
    If you are doing ALE, then you have to maintain the idoc types which are NOT to be transferred to the Integration server by executing report IDX_SELECT_IDOCTYP_WITHOUT_IS.
    By maintaining the Idoc Types using this report, only these idoc types are sent to the regular EDI/IDOC interface.

  • 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

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

  • 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

Maybe you are looking for