Restart RFC Receiver Adapter Channel in XI 3.0

Hi all,
I have a problem when the R/3 Backend receiver of the RFC call through XI 3.0 shutdown the weekend.
When XI restarts but the R/3 is not up, the RFC adapter (receiver communication Channel of R/3 backend) fails. In the Adapter monitor I can see the error:
"Can't connect to gateway".
The only way I know to solve this problem is going to the Integration Directory and Inactivate the communication channel, save changes and activate change list. Then re-activate the channel, save changes and activate change list.
At this moment, the RFC Adapter of the R/3 receiver registers on the gateway and is visible in SMGW transaction.
Is there any other way to restart the RFC adapter channel of one backend (or all at the same time)?
Thank you
Best regards
Luis

Hello Michal,
I can't control the startup process of the R/3 because that system is under another backup policy and shutdown schedulling.
I think the option of disable the initial check parameter of the RFC Adapter could be enough to solve the problem.
Do you know if this parameter impact another runtime behavior?. I prefer in case of failure that temporaly the rfc doesn't run, but after the comunication error automaticaly the adapter works without manual change or administration and support maintenance.

Similar Messages

  • Java.lang.NullPointerException in RFC Receiver Adapter

    Hi Experts,
    i have configured SQL Sender Adapter and this works fine, i can see the payload. and at the receiver adapter i have configured RFC Receiver Adapter this is throwing NullPointerException as mentioned below.. can someone help me out to fix this issue..
    Error Description:
    Error     Exception caught by adapter framework: null
    Success     MP: Processing local module localejbs/AF_Modules/RequestResponseBean
    Error     MP: Exception caught with cause java.lang.NullPointerException
    Error     Delivery of the message to the application using connection   
                    RFC_http://sap.com/xi/XI/System failed, due to:
                    com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException.
    Success     The message status set to WAIT.
    Thanks,
    Srikanth

    Hi Srikanth,
    This error Occurs because of incomplete configuration in the reciever communication channel.Please check all the required configurations in the reciever communication channel and then activate the channel.
    Regards,
    Naveen

  • Dynamic Logon Data in RFC receiver adapter?

    Does someone know if and how the logon data (userid) defined in the communication channel for a RFC receiver adapter can be dynamic overwritten? For example using  information from the payload?
    Scenario: A request for getting HR data is send from a legacy system to XI, mapped to a RFC and routed to R3.
    The audit people want to see a real user login into the R3 system to execute the function module and not the technical user defined in the communication channel.

    That's exactly what principal propagation is.
    You just have to make some (quite a lot, actually) configurations to enable it.
    Check these links:
    Online documentation: http://help.sap.com/saphelp_nw70/helpdata/en/45/0f16bef65c7249e10000000a155369/frameset.htm
    Weblog: /people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
    Regards,
    Henrique.

  • Intermittent problems with a RFC receiver communication channel.

    Hello.
    I want to know how to get the total channel history for a RFC receiver communication channel (in RWB only last 5 calls are available).
    We use this communication channel in a java mapping to run a RFC of the abap engine of XI. Sometimes the rfc doesn't work and mapping throws a mapping transformation exception. Then, without a modification, we reprocess the message in SXMB_MONI and it is processed without errors. We think that it could be caused by a huge message volume.
    How can I get the maximum number of rfc calls that the rfc communication channel can admit simultaneously. Which parameters have influence in these calls?
    Thank you very much.
    Alberto.

    1. Increase the maximum connections
    from help.sap.com
    Additional Parameters
    Parameter ~~~~ Entry
    Maximum Connections ~~ Maximum possible number of initial connections required between adapter and sender system. This value is limited internally to a maximum of 50.
    2. /people/community.user/blog/2006/09/21/xi-rfcadapter-reconnect-issue

  • RFC Receiver Adapter and RFC Destination -- Help

    Hi,
    I would like to configure the RFC Receiver Adapter for the invokation of a RFC on SAP System (Name: ALPHA) using a RFC destination provided by another system named BETA.
    I have set External Server as server type.
    My first question is: I have to quote an application server gateway and a gateway service. Is this information related to a service on ALPHA or BETA?
    My second question is:
    It is also necessary to provide a Programm-ID. The destination on BETA is a R/3 connection and doesn't have a programm id. Where do I get this from?
    And my last question is:
    Is at all possible to use the RFC destination on BETA?
    Any help is really appreciated...
    Kind regards,
    Heiko

    Hi Heiko,
    I don't fully understand your need but:)
    since both of your systems are SAP systems
    why are you trying to use external server?
    can't you just call RFC on BETA
    and inside this RFC on beta call RFC on ALPHA?
    in a sync or async way?
    can you tell a little more about your requirement ?
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • RFC Receiver Adapter Problem- Sending Blank XML Node

    Hi,
    I'm using the RFC receiver adapter to call a RFC in R/3 from XI 3.0
    In the payload XML one node is blank as I want to pass a blank parameter to the RFC. But in R/3 the blank node is getting converted to #
    Can anyone suggest how can I pass a blank node while calling the RFC using RFC receiver adapter in XI 3.0?
    Thanks in advance,
    Dipankar

    Hey
    Please check the outbound payload in sxmb_moni and RWB,if the field is blank there,then it means that PI is passing correct value to ECC.its possible that RFC has been coded in such a way that it converts blank spaces to #.Please look at RFC documentation in that case and see if it helps more.
    If the outbound payload itself in PI is showing as # instead of blank,then check the message mapping in PI.
    Thanx
    Aamir

  • RFC Receiver Adapter (Problem)

    Hi All,
    I have configured RFC Receiver Adapter : Here i have imported a Z FM for example
    "" Z_API_DOCUMENT_CREATE_TEST ""  having below import paramaters:
    LF_DOCNUMBER     TYPE     BAPI_DOC_DRAW-DOCUMENTNUMBER
    IV_PF_HTTP_DEST     TYPE     RFCDES-RFCDEST
    IV_PF_FTP_DEST     TYPE     RFCDES-RFCDEST
    LF_FILENAME     TYPE     BAPI_DOC_DRAW-DOCUMENTNUMBER
    1) Now i use MM to fill in two parameters : LF_DOCNUMBER , LF_FILENAME
    If my FIle is of kind : test55.pdf     --> LF_DOCNUMBER  = test55
                                                           LF_FILENAME       = test55.pdf
    For this i have checked in Sender File Adapter "Adapter Specific Message Attributes"
    So i write UDF to capture Filename and Filename with extension to fill above shown parameters.
    Now i saw target xml after mapping in CC monitor of RWB is as below
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:Z_API_DOCUMENT_CREATE_TEST xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
      <IV_PF_FTP_DEST>SAPFTPA</IV_PF_FTP_DEST>
      <IV_PF_HTTP_DEST>SAPHTTPA</IV_PF_HTTP_DEST>
      <LF_DOCNUMBER>xierror</LF_DOCNUMBER>
      <LF_FILENAME>xierror.doc</LF_FILENAME>
      </ns0:Z_API_DOCUMENT_CREATE_TEST>
    But LF_FILENAME is getting populated to my Z FM at runtime but LF_DOCNUMBER works fine filling up with value.
    But when i run the FM using F8 it works , what could be the problem.
    Any advice
    regards
    Srinivas

    Hi,
    The problem is with the Data types used for LF_DOCNUMBER.
    Make this as Char or Numeric in FM and then try. If its of any packed values then conversion will create the problem
    Thanks
    Swarup

  • How to configure RFC receiver adapter

    HI,
    I have a Proxy-to-RFC scenario. But I have no knowledge in RFC receiver adapter. Could you please provide me the step-by-step guideline or sample about how to configure RFC receiver adapter.
    Thanks in advance.
    Best regards, Johnney.

    Hi,
    Refer these links which will help you understand the concept and configure the Scenario.
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/content.htm
    The specified item was not found.
    Refer this blog for synchronous scenario
    RFC Scenario using BPM --Starter Kit
    Sender RFC Adapter:
    The specified item was not found.
    Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 ***
    RFC -> file scenario: application stopped
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=rfctofile&cat=sdn_all
    RFC to file
    RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
    Send RFC to SAP XI – Asynchronous
    The specified item was not found.
    ABAP Proxies in XI(Client Proxy)
    Regards,
    Nithiyanandam

  • RFC Receiver adapter issue. Pls advice

    Hi All,
    When XI is sending data back to R/3 system though RFC Receiver Adapter  I am getting the below error. Any suggestions
    Error Category   XI_J2EE_ADAPTER_RFC
    Error Code  RECEIVER_GENERAL_ERROR
    Pls advice.

    Rick, your question is very unspecific, so anyone trying to help can only guess very roughly.
    So I only have a very rough hint for you, which is the FAQ for RFC adapter.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_xi/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d373330383730%7d

  • RFC Receiver Adapter Issue

    Hi all,
          I'm sending a sales order from my ftp server to my R/3 system through RFC. I want this sales order to be created in the R/3 system, For this i'm using BAPI_SALESORDER_CREATEFROMDAT2. Now when i'm configuring my RFC Receiver adapter using the help given on the help.sap.com under "adapters"->"rfc adapter"-> "configuring the rfc adapter", i'm not able to find the parameters mentioned under " Advanced Mode" Heading. In this page, it says that after checking the Advanced mode checkbox, one should get the additional parameters and then we need to set the indicater for the parameter "Commit Control for Individual BAPI Calls". Since i'm not able to find these parameters even after checking the chekbox, i'm stuck. I understand that if i don't get this parameter, my BAPI will not commint and hence the sales order will not be created in R/3.
    Kindly suggest.
    Regards.
    Naveen

    Hi Naveen -
    >>><i>In this page, it says that after checking the Advanced mode checkbox, one should get the additional parameters and then we need to set the indicater for the parameter "Commit Control for Individual BAPI Calls". Since i'm not able to find these parameters even after checking the chekbox, i'm stuck.</i>
    For this I agree with Sameer.  It's probably an adapter metadata issue.  As mentioned your XI system needs to be at least on SP14.  Also, in the Int. Repository, check SAP BASIS 6.40 SWC SP Level by right clicking on the SAP BASIS 6.40 SWCV, then Display Support Package - this is where the adapter metatdata is delivered.  By default, the highest one displayed is wha'ts current on the system.  You should see at least SP14 here.  Incidentally, this does not confirm the SP level that the rest of the XI components are on, just this SWC.
    >>><i>When i checked in the integration engine, transaction sxmb_moni, i found that the message was processed successfully ! But when i checked in my R/3 system, i didn't find any sales order ! Kindly give me some inputs for this issue.</i>
    It probably failed in the adapter engine.  Check the adapter engine monitor via the RWB - so once in RWB, goto Message Monitoring, select Adapter Engine (important), then look for your message.
    Regards,
    Jin
    Message was edited by: Jin Shin

  • Error in RFC Receiver Adapter: functiontemplate from repository was null

    Hi Friends,
    i am working on JDBC -> RFC Scenario, JDBC Sender Adapter is working fine, but RFC Receiver Adapter is throwing this error message... can some one help me to solve this issue...
    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: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    Thanks
    Srikanth

    Hi,
    I think the logon details what you are giving in Receiver CC may be wrong. Check all those details like Application Server,System Number,User,Password and client.
    Thanks.

  • Error in RFC Receiver Adapter: functiontemplate from repository

    Hi Experts,
    i am working on JDBC -> RFC Scenario, JDBC Sender Adapter is working fine, but RFC Receiver Adapter is throwing this error message... can some one help me to solve this issue...
    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: functiontemplate from repository was <null>: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
    Thanks
    Srikanth

    Possible reasons are
    The XML document, which was send to the RfcAdapter, is not a RFC-XML document. So the root element name of this document is not the name of a function module and thus can't be found in the metadata repository.
    The metadata repository doesn't contain an entry for this function module name. Normally the metadata repository will be an R/3 system and it's function module repository can be searched with transaction code SE37.
    Here my suggestion is, if you are using Java/xslt mapping, write your code in line with result structure of your mapping instead source pay load structure. May be helpful.
    Cheers
    Madhu

  • SAP PI Issue with RFC Receiver Adapter

    Hello,
    Iam using File-RFC scenario, where every thing executed fine, but in ECC iam unable to get the DATA coming from PI, Iam using Z RFC to insert data to a Z table.
    I did'nt any errors in PI, is there any option to find the output data at receiver adapter where iam using RFC adapter.
    Kindly Help,
    Thanks in Advance,
    Ravi.

    Yes. If you enable the logging you should be able to see the post mapping xml.
    Message Staging and Logging Options in Advanced Adapter Engine of PI 7.3x
    Scenario specific message staging and logging in PI 7.31 AAE
    Did you debug the RFC with test data? were you able to insert something?

  • RFC Destination type RFC Receiver Adapter?

    Hi,
    What is the RFC destination type for Sender RFC Adapter?
    and what is the need a Program ID for sender Adpter.
    What is the RFC destination type for Receiver RFC Adapter?
    Regards
    Gopi

    When we use the RFC Adapter?
    SAP systems up to and including SAP Release 4.6 are not able to exchange data by using XML messages and http. The only way you can connect such systems to the Integration Server directly is by using the RFC adapter (or the IDoc adapter).
    You require the sender adapter if you want to use the Integration Engine to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine.
    You require the receiver adapter if the determined receiver system expects the data from the Integration Engine to arrive in RFC format. In this case, the Integration Engine must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
    The following three scenarios are possible when using the RFC adapter and the Integration Engine:
        1) SAP R/3 to SAP NetWeaver Application Server       
        2) SAP NetWeaver Application Server to SAP R/3
        3) SAP R/3 to SAP R/3
    When we use ABAP Proxy ?
    SAP systems based on Web AS 6.40 and higher are able to exchange data by using messages and HTTP. These systems can use ABAP proxies to connect to the Integration Server.
    To connect the platform-independent message interfaces, which are stored in the Integration Repository, to the Integration Server, use the ABAP proxy interface.
    Please Reward the points if it's helpful...
    Regards,
    Ramana.

  • RFC receiver adapter not getting timed out

    Hello Everyone,
    I have a scenario like this:
    Web-Service --> PI -->RFC (using receiver RFC channel)-->Response back to PI from RFC --> response back to Web-Service
    This RFC is taking more than 5 minutes to give response back to PI but still I am not getting timeout in PI.
    xiadapter.inbound.timeout.default is set to default value 180000.
    Is there any other place where I should check for setting timeout like 10 seconds for rfc receiver channel?
    Thanks,
    Satarupa

    Dear Satarupa,
    You need to set ICM timeouts at Integration Engine level.
    So go to SXMB_ADM and clic on Specific configuration. Edit table and set parameter as follow:
    Category = RUNTIME.
    Parameters = HTTP_TIMEOUT.
    Current Value = [segs] depens your needs.
    If you hasn't this parameter in SXMB_ADM set this parameter yourself.
    Related link.
    http://itsiti.com/increase-sap-icm-http_timeout-runtime
    Regards,
    Jose

Maybe you are looking for