RFC adapter not responding

Hi guys,
We are facing the following problem:
We have a receiver RFC adapter that executes some RFC functions on a SAP R/3 system connected to XI. When the R/3 system is down (e.g. for maintenance reasons) the RFC adapter (communication channel) has a red "error" status in Communication channel monitor (that could not connect to R/3), which is ok. However, when the R/3 system goes up, the RFC communication channel remains in the same error status, irrespective of the fact that the R/3 is now up. Morever, it needs some manual stop and start from CC monitor in order to be able to "see" that the R/3 is now up. This has an impact on our interfaces that it may be the case that sometimes the administrators, fail to notice this and the corresponding interfaces that make us of the RFC adapter, fail for no reason.
Is there a way to avoid this undesirable situation?
Best Regards
Evaggelos Gkatzios

Hi Gkatzios,
                      we also facing same problem as your,,when the R3 system is down for some maintenance reason at the same time XI expects something from R3 ,in this situation RFC adapter is going to error state,when R3 is up RFC adapter works fine but CC still shows error status.but some times we have to stop and start CC manually.
everytime when we open the CC monitoring particular CC always in error state eventhough it is working fine..
If you find any solution for this please let me know.
Thanks for your time.
Regards
Rao

Similar Messages

  • RFC Adapter not Call

    Hello Friends,
    I am working on XI 2.0
    My Scenario is
    IDOC --> XI --> RFC Adapter --> R/3 System
    I am configuring the RFC adapter for the SAP system.
    But when I am able to try to call using the Integration Engine it’s not call the RFC adapter.
    I define the end point as
    RFC Adapter
    (X) Load Balancing Deactivated
           Application Server -- <host name>
           System Number      -- 00
    When I run the scenario it show me in the <b>sm58</b> transaction as
    <b>Connection Close (no Data)</b>
    And in the SXMB_MONI Transaction it shows
    <b>A. Status</b> as <b>Green Flag</b> means <b>Message schedule on outbound side</b>.
    So can you please identify and suggest me the solution or what else configuration is required.
    Thanks & Regards,
    Gaurav Jain

    try to register all queues in SXMB_ADM -> Manage queues.
    I think that should help you solve the issue.

  • RFC Adapter not getting data

    Hi experts!
    I am developing a RFC to File scenario on PI 7.1 EHP1 and ECC 6.0 which is synchronous. Following the Help page Setting Up an RFC Destination for the RFC Adapter I created two destinations. The fist one is a TCP/IP, name RFCDE1COMPANY2, program id BAPI_COMPANY_GETLIST and corresponding gateway host and service I found at SMGW (Parameters). The second one is a Logical with name RFCDE1and reference entry RFCDE1COMPANY2.
    At my RFC Sender Adapter I configured the same gateway info and the same program id. After that I tested both destinations and it worked. I created the following report to call the bapi on that destinations::
    REPORT  ZREP_BAPI_COMPANY_GETLIST.
    DATA: company_list TYPE STANDARD TABLE OF BAPI0014_1.
    CALL FUNCTION 'BAPI_COMPANY_GETLIST'
      IN BACKGROUND TASK
      DESTINATION 'RFCDE1'
      TABLES
         COMPANY_LIST = company_list.
    COMMIT WORK.
    At SXMB_MONI the request message was processed and the output file generated, but it has only the root tag. At moni the inbound message has no data (company data).
    I tested the BAPI_COMPANY_GETLIST at SE37 and there are 149 entries. When I executed this same BAPI with RFC target sys configured to my destination, it didn´t show any data and has an exception called SYSTEM_FAILURE. I think probably the error is on RFC destinations but I can´t figure it out what is wrong.
    Best Regards,
    Gabriela

    Hi experts,
    Thank you all for your quick response.
    At the TCP/IP Destination there is a button "Unicode Test", according to this test my target system is unicode (character size 2). I changed the option at MDPM&Unicode on that TCP/IP Destination like Madhusudana described. I also selected the checkbutton "Unicode" on sender RFC communication channel.
    About the sync/async, I will not use sync async bridge because this scenario can be async. One think that I realized is that when I call my report, I am implicitly calling PI asynchronously and when I call the BAPI directly by the test tool, I am implicitly calling PI synchronously. That is why most part of my tests did not work before.
    Now I can see on SXMB_MONI that the scenario worked and the file was generated. But the data are still not being showed on inbound payload. I think something is wrong with my destinations but I can´t figure it out what is.
    Ps.: I would prefer to use XI proxies, but this scenario will be configured (not now) on a XI 3.0 with ERP 4.6 C. Now I´m just learning how to handle with RFC Adapter.
    Any ideia?
    (Points granted)
    Thank you and best regards,
    Gabriela

  • RFC adapter not  started (Error starting AS Java Service XPI Adapter)

    Dear Experts,
    We have recently Upgraded our sustem from XI3.0 to PI 7.1, and have encountered a peculiar error in RFC adapter which could not be started
    error says:   Error starting AS Java Service XPI Adapter: RFC
    corresponding instance when started says
    Error starting AS Java Service XPI Adapter: RFC on DVEBMGS00
    Hence our RFC channels are not functioning
    Please help
    Regards,
    Rana De

    can you try to restart XPI Adapter:RFC in NWA. if still it throws error then try to restart java stack.

  • Rfc adapter not recommended.

    Which are the scenarios when RFC adapters are not recommended,  and wat are the prerequisite for using RFC adapters.?

    Hi Rahul,
    >>Which are the scenarios when RFC adapters are not recommended,
    RFC adapters are not suited for scenarios which involves large amnt of message processing. If you are sending big data from R/3 the its always advisable to go for Proxies..
    >>wat are the prerequisite for using RFC adapters.?
    RFC Adapter is used for conncting with SAP and for sending and reciving data frm SAP systems... Apart from that can u tell what pre-requisites you are looking for??
    Regards
    Suraj

  • RFC adapter not found in RWB

    Hello,
    I have a problem with RFC adapters (From ECC and from BW)
    When I try to found the problem in RWB  communication channel monitoring (I choose RFC in adapter type section)
    I'm not seeing these channels.
    Any idea how I can found this channels?
    Elad

    Hi Elad,
    I hope you were not able to see the communication channel in CC Monitoring.
    First check whether the channel has been activated in the Integration Directory?
    Thanks,
    kumar.

  • Windows 10 and MarvellYukon Network Adapter not responding properly

    With W10 preview the "Marvell Yukon Network-Adapter" does not work properly.
    It destroys the ethernet-integrity (some nodes are not shown on other computers anymore when W10 is up) und the network speed is about a few kilobits!
    RDP connection to W10 machine will lost unexpectedly! It seems to be a massive driver problem.
    Regards

    I found the reason: after installing the new build "Jumbo Frames" were activated to 9000 .
    Really mysterious, I never touched these settings ...

  • Receiver file adapter not responding

    Hi guys,
    I have 2 interfaces in XI development system that make use of receiver file adapter in order to receive some .txt files. Although these communication channels used to work until yesterday, for some strange reason they stopped functioning, but only in development system. However, I cannot see any error in Runtime Workbench (Communication channel monitoring), it's status is "correctly configured and started" and has a green sign. But, when I sent a file from sender adapter, it is sent correctly, but it never gets received from receiver communication channel.
    There is no error in SXMB_MONI either.
    In XI production system, the same interfaces are functioning well.
    Any ideas?
    Best Regards
    --Evaggelos

    Hi Amit,
    I went into Message Monitoring for this interface and I can see all the messages for the last 24 hours that should be written into a file that have status "to be delivered".
    When I go into Details -->Audit Log  for a single message:
    2007-06-13 11:49:33 Success Processing child message of multi-message with message ID ff896d50-198a-11dc-cdfa-00145e694b16
    2007-06-13 11:49:33 Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2007-06-13 11:49:33 Success Message successfully put into the queue.
    And in Message Data there is the following information:
    Status To Be Delivered
    Repeatable Yes
    Cancelable Yes
    Error Category  
    Error Code  
    Start 13.06.2007 11:49:33
    End  
    Sender Party  
    Sender Service TPBS_GR
    Receiver Party  
    Receiver Service TPBS_GR
    Interface http://famar.gr:LoyaltyDataMNSToSRS
    MI_LoyaltyDataMNSToGR_IB
    Quality of Service Exactly Once
    Message b2685674-7626-5141-bfa1-13155ad0d25a
    Reference  
    Conversation ID  
    Serialization Context  
    Direction INBOUND
    Message Type Recv
    Profile XI
    Connection File_http://sap.com/xi/XI/System
    Transport HTTP
    End Point http://fmgralxi01:50000/MessagingSystem/receive/AFW/XI
    Authorization  
    Sequential Number 0
    Number of Retries 3
    Failed 0
    Retries 300000
    Valid to  
    Persist Until 13.07.2007 11:49:33
    Schedule Time 13.06.2007 11:49:33

  • Is this possible: SAP Java Connector - XI - R3 with XI RFC Adapter?

    Hi,
    I try to call a RFC on a remote R/3 System over the XI Server in a Java Application with SAP Java Connector.
    I have configured a RFC Sender Adapter in XI. I get the
    following Exception:
    "lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'SenderChannel_RFC"!
    Is this scenario possible? Or do the connection from
    a SAP Java Connector App to the XI RFC Adapter not work?
    You can't set the Client and System ID of a Third-Party or
    Standalone Java system in the SLD.
    Thanks for any help!
    Regards
    Wolfgang

    Hi,
    We use a JCO for directly connecting to sap systems.
    In that case we need not use any XI also.
    But if you want to use RFC adapter and java application the best way is to use java proxies as sender and reciever as RFC adapter.
    I donot think there is any  architectural significance in using rfc adapter of XI while using JCO.
    Let me know if I mis-understood the context.

  • RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C

    Here is the scenario.
    An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format.  This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
    call function 'BAPI_TRANSACTION_COMMIT'
    The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
    Here is what happens within XI and our SAP system.
    The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer.  All seems to be working properly except that when the original RFC is sent from XI to SAP,  SAP creates a short dump stating
    "call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
    I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
    Any ideas.
    Thanks,
    Jim d'Hulst

    Hi,
    I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
    CALL FUNCTION 'ZABCD'
    destination <tcp/ip destination>
    exporting
    input = ack.
    In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
    Also, check your config with the blog mentioned below:
    <a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
    Regards,
    Amitabha

  • XI / PI SOAP Adapter - MessageServlet not found / not responding

    I am in trouble with XI SOAP Adapter. When I try to reach the <b>MessageServlet</b> ( http://host:port/XISOAPAdapter/MessageServlet ) I get the response that document dont exists. Why MessageServlet do not respond? Anyone can help me?
      In my Adapter Monitor ( http://host:port/mdt/amtServlet ) I see about the SOAP adapter a grey status and the information: "SOAP Adapter Monitoring is now part of Channel Monitoring". This is not a problem, according to Suraj: "SOAP Adapter will become active only when you sent a message through that for atleast one time.")
      See also these topics:
      SOAP adapter installation and activation
      Adapter monitoring: SOAP is grey although it is used?
    how can i enable SOAP Adapter?
    https://websmp208.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000286382005 (<b>SAP Note 856597</b>)
    <i>  I have readed these topics (and others), but my problem seems to be a little different.
    </i>
      My XI runtime cache contents (SXI_CACHE) are up-to-date.
      <b>Information of some of my XI components:</b>
    Software Components 
    Vendor  Name  Version  Location  Applied 
    sap.com  SAP-JEE  6.40 SP17 (1000.6.40.17.0.20060516064307)  SAP AG  20060612185606 
    sap.com  SAP-JEECOR  6.40 SP17 (1000.6.40.17.0.20060516064111)  SAP AG  20060612185559 
    sap.com  NWMADMIN  6.40 SP17 (1000.6.40.17.0.20060515153837)  MAIN_APPL63VA_C  20060612185601 
    sap.com  SAP_XITOOL  3.0 SP17 (1000.3.0.17.0.20060504222004)  SAP AG  20060613105756 
    sap.com  SAP_XIPCK  3.0 SP16 (1000.3.0.16.0.20060220233019)  SAP AG  20060612185556 
    sap.com  LM-TOOLS  6.40 SP17 (1000.6.40.17.0.20060417111655)  MAIN_APPL63VA_C  20060612185603 
    sap.com  SAP-XICONS  3.0 SP16 (1000.3.0.16.0.20060220232901)  SAP AG  20060612185600 
    sap.com  SAP-XIAFC  3.0 SP12 (1000.3.0.12.5.20050712085155)  SAP AG  20060612185555 
    sap.com  SAP_XIAF  3.0 SP17 (1000.3.0.17.0.20060522230043)  SAP AG  20060613103623 
    sap.com  SAP_JTECHF  6.40 SP17 (1000.6.40.17.0.20060516064445)  SAP AG  20060612185559 
    sap.com  SAP_JTECHS  6.40 SP17 (1000.6.40.17.0.20060516064629)  SAP AG  20060612185606 
    <b>sap.com  com.sap.aii.af.mp  3.0 (3.0.1720060522104934.0000)  SAP AG  20060613102037  sap.com/SAP-XIAFC  </b>
    sap.com  com.sap.aii.af.soapadapter  3.0 (3.0.1720060522104934.0000)  SAP AG  20060613103506  sap.com/SAP_XIAF 
      Thanks a lot! If you need other information, please, let me know.
      <b><i>Ivan, from Brazil</i></b>

    <i>"https://websmp208.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000286382005 (<b>SAP Note 856597</b>)
    I have readed these topics (and others), but my problem seems to be a little different."</i>

  • HTTP Response code 404 - RFC Adapter des not connect to Integration engine

    Hi,
    I seem to have problem with XI Integration engine. My integration process does not go beyond adapter engine and it fails with the following error,
    Begining of the erorr report -
    2006-01-23 13:35:53 Success RFC adapter received sRFC for ZSCEN2_XI from <sysno>/<client>. Attempting to send message synchronously
    2006-01-23 13:35:54 Success Application attempting to send an XI message synchronously using connection AFW.
    2006-01-23 13:35:55 Success Trying to put the message into the call queue.
    2006-01-23 13:35:55 Success Message successfully put into the queue.
    2006-01-23 13:35:55 Success The message was successfully retrieved from the call queue.
    2006-01-23 13:35:55 Success The message status set to DLNG.
    2006-01-23 13:35:55 Error Returning synchronous error notification to calling application: Received HTTP response code 404 : Not Found.
    2006-01-23 13:35:55 Error Transmitting the message using connection http://<host>:55300/sap/xi/engine?type=entry failed, due to: Received HTTP response code 404 : Not Found.
    2006-01-23 13:35:55 Error The message status set to FAIL.
    2006-01-23 13:35:55 Error Returning to application. Exception: Received HTTP response code 404 : Not Found
    end of error report -
    and the runtime workbench does not connect to Integration engine and fails with the following error,
    begin error report -
    javax.ejb.CreateException: Unable to log on to system XID in language en with user XIRWBUSER
         at com.sap.aii.mdt.server.integrationengine.IntegrationEngineMonitoringBean.ejbCreate(IntegrationEngineMonitoringBean.java:374)
         at com.sap.aii.mdt.server.IntegrationEngineHomeImpl10.create(IntegrationEngineHomeImpl10.java:185)
         at com.sap.aii.mdt.server.IntegrationEngineHome_Stub.create(IntegrationEngineHome_Stub.java:56)
    end of report -
    Have anyone experienced the same issue?. Are we missing some post installation configuration?.
    Thanks in advance
    Regards,
    Arul

    HI Anulraja,
    Your Adapter Engine searches the pipeline url of the integration engine from the SLD.
    Check the Bussiness System in Sld , which you'll have defined for XI Server.
    It should have ROLE : Integration Server And
    pipeline url: http://ux0800:55300/sap/xi/engine?type=entry
    should be this if your http port is 55300.
    Check if this url is right in SLD-Bussiness System.
    You can check the exact http port in transaction sxmb_adm.
    Go to Integration engine configuration and then click on check icon(F7).
    It should match with that provided in the BS in SLD.
    By default it should be 8000.
    Check all these things and then try.
    Regards,
    Yomesh

  • Jco error RFC adapter field PT F not defined

    Hi Experts,
    I am in a strange situation as I have become clue less on this issue
    It is a file to XI to RFC scenario.. runs fine in dev environment
    When I change the parameters in teh rfc communication channel  to point to QAS it throws
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_TRAX_PO_CHG_IV in remote system (RfcClient[CC_QAS]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Field selection PT F not defined:
    There is no such field as PT F and besides the version of the bapi in QAS is in sync with the dev..
    pls help me ou ton this
    Edited by: Ravindra Teja on Feb 27, 2011 8:45 AM

    Hi,
    First of all, can you please elaborate what you want?
    secondly, why don't you transport your developments to QAS?
    Third, what is the reason behind changing the receiver RFC adapter parameter to QAS?
    4th, do you want to post data to QAS, if yes, did you transported the RFC to QAS ? Please re import the rfc to your swcv from QAS system.
    Please check communication channel if you getting any error?
    Regards
    Aashish Sinha

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

  • RFC-Adapter, order not put in

    Hi,
    my scenario File -> XI -> R/3-Backend will be precessed successful. The Response Payload have the items and in detail of messages appears  succes status
    "RFC adapter received an asynchronous message. Attempting to send tRFC for BAPI_PO_CREATE with TID XIfr1OyAQS4Td..."
    But in R/3 the order ísn't put on.
    Does one of you have an idea why???????
    Thanks
    Hüsniye

    Try this code. This works perfectly for us:
    CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
      EXPORTING
        SALESDOCUMENTIN               =  SALESDOCUMENTIN
        ORDER_HEADER_IN               =  ORDER_HEADER_IN
        ORDER_HEADER_INX              =  ORDER_HEADER_INX
        SENDER                        =  SENDER
        BINARY_RELATIONSHIPTYPE       =  BINARY_RELATIONSHIPTYPE
        INT_NUMBER_ASSIGNMENT         =  INT_NUMBER_ASSIGNMENT
        BEHAVE_WHEN_ERROR             =  BEHAVE_WHEN_ERROR
        LOGIC_SWITCH                  =  LOGIC_SWITCH
       TESTRUN                       =  TESTRUN
        CONVERT                       =  CONVERT
    IMPORTING
       SALESDOCUMENT                  =  SALESDOCUMENT
      TABLES
       RETURN                         =  RETURN
       ORDER_ITEMS_IN                 =  ORDER_ITEMS_IN
       ORDER_ITEMS_INX                =  ORDER_ITEMS_INX
        ORDER_PARTNERS                =  ORDER_PARTNERS
       ORDER_SCHEDULES_IN             =  ORDER_SCHEDULES_IN
       ORDER_SCHEDULES_INX            =  ORDER_SCHEDULES_INX
       ORDER_CONDITIONS_IN            =  ORDER_CONDITIONS_IN
       ORDER_CONDITIONS_INX           =  ORDER_CONDITIONS_INX
       ORDER_CFGS_REF                 =  ORDER_CFGS_REF
       ORDER_CFGS_INST                =  ORDER_CFGS_INST
       ORDER_CFGS_PART_OF             =  ORDER_CFGS_PART_OF
       ORDER_CFGS_VALUE               =  ORDER_CFGS_VALUE
       ORDER_CFGS_BLOB                =  ORDER_CFGS_BLOB
       ORDER_CFGS_VK                  =  ORDER_CFGS_VK
       ORDER_CFGS_REFINST             =  ORDER_CFGS_REFINST
       ORDER_CCARD                    =  ORDER_CCARD
       ORDER_TEXT                     =  ORDER_TEXT
       ORDER_KEYS                     =  ORDER_KEYS
       EXTENSIONIN                    =  EXTENSIONIN
       PARTNERADDRESSES               =  PARTNERADDRESSES
    **checking if the BAPI returned some errors*****
    LOOP AT return ASSIGNING <bapiret>.
        IF <bapiret>-type = 'E' OR <bapiret>-type = 'A'.
          success = space.
          EXIT.
        ENDIF.
      ENDLOOP.
    IF success = 'X'.
    ****in case of success commit the BAPI*********
         CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait   = 'X'
          IMPORTING
            return = wa_bapiret.
    ELSE.
          ROLLBACK WORK.
         ENDIF.
    Also you need to pass on the information for "inx" structures. What I mean is , if you are sending data to field REF_1 in header_in, then ref_1 in header_inx needs to be passed witha value of 'X'.
    The update flag in inx structure needs to be 'C' for create.
    If have items in your sales order, then you have to pass the values for item_in and item_inx. Additionally you need to pass values for schedule lines also.
    Hope this helps.
    Thanks,
    Bhaskar

Maybe you are looking for