RFC Sender Problem...

Hi all,
I configured the RFC Sender communication channel in the XI . The RFC Server parameter and Metadata Repository for this CC, point to a R/3 Application System. In SM59 I configured the TCP/IP connection and it work fine.
Was configured, too, the Sender Agreement and Receiver Determination for the RFC message.
When I test the RFC call in XI server with the destination configured in SM59, the RFC is not processed in the target R/3 system and no message is returned. In the Channel communication I get the error: Message processed for interface ZBR_RFC_SD_BPMAG_START_WKFIORD: com.sap.aii.af.rfc.RfcAdapterException: failed to identify XML document:org.xml.sax.SAXParseException: Premature end of file.
Any idea about this error?  Is there any configuration to set the username and password to connect wikth R/3 target system using this channel comunnication?
thanks.

Hi,
>In the Channel communication I get the error: Message processed for interface ZBR_RFC_SD_BPMAG_START_WKFIORD
1) Check the User ID & password  is Correct
2) With the help of Basis team Find it out whether the User Id  has the RFC Role to Connect
3) From XI test the Connection..tcode Sm59 whether RFC Connection is  existing between SAP XI & R3
4) Check Whether the  Function Module - ZBR_RFC_SD_BPMAG_START_WKFIORD  Exists
Regards
Sangeetha

Similar Messages

  • Rfc sender problem(sap r/3 -se37) 'alternativeServiceIdentifier: party/serv

    Rfc sender problem: While executing the rfc in sap r/3 system
    It is showing abap run time errors are
    'alternativeServiceIdentifier: party/service from channel
    configuration are not       
    (i have taken hint from this weblog /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step)
    These are the configuration at sap xi and sap r/3 system
    1) SAP XI (ID)
    I have created rfc sender commuication channel in I.D.
          Rfc server Parameters->
                A.S.(Gateway)-> server    {sap r/3 server name}
                A.S.S.(Gateway) -> sapgw00 
                program id         -> PDPT
         AND RFC Metadata repository parameter
    2)SAP R/3 (SM59)
        Rfc destination ->  PPPP
        Connection type -> T
        Technical Settings->
             (*)  Registered Server Program
          Program ID  ->    PDPT
    Gate way options
          Gateway host -> server
          gateway service -> sapgw00
    Testconnection-> connected
    3) testing rfc at sap r/3(se37)
    But when i am executing a rfc in sap system
    Rfc target system -> PPPP
    and some import parameters
    and it is showing the error message as
    'alternativeServiceIdentifier: party/service from channel
    configuration are not  '
    4)SAP R/3( SMGW)
    CONNECTION TO CLIENT FOR PDPT(TP NAME) REGISTER STATUS IS WAITING
    Please help me how to solve this problem

    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

  • 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

  • RFC Sender Problem. Pls advice

    Hi All,
    I have a RFC interface between Sap R/3 and XI.
    I am getting error in SM58 in R/3 :
    Commit fault com.sap.aii.af.mp.module.ModuleException: call to messaging.
    If I do test connection on in SM59 on TCP connection it's ok.
    For the above error I also receive for some time the below SLD error message in RWB of XI
    "Error during communication with System Landscape Directory: HTTP response code: 503 (Not Ready)"
    Please advice
    Regards

    Hi Rick,
    commit fault error is seen in SM58 when there are more transactions to the database parallely . ask your basis guys to increase the screen numbers in the database.this error wont come again.
    thanks.

  • Rfc Destination problem in RFC Sender Adapter

    Hi experts
    I created a Rfc destination type TCP/IP for Rfc Sender adapter.
    while creating i passed following parameter:
    1) I selected Activation Type option-> Registered Server  
    2)Given a Program id , same as i given in Rfc sender Adapter config.   
    3)Gateway option:
       i) Gateway Host:Server IP address where i created  Rfc.
      ii) Gateway Service:sapgw00
    After making these entry, i m unable to receive message at XI end (I am executing Rfc at R/3 site due to Rfc sender)

    Hi
    please check for the following things.
    1. check the RFC destination using the connection test tab in the R/3 system.
    2. check whether the program id that u have given is registered or not.
    to check the program id go to the transaction SMGW, in the menu select Goto-->LoggedonClients
    check for ur program id name in the table.
    3. when you configure the RFC sender adapter in XI then you have to give the same program id name that you will give while creating the RFC destination in the R/3 system.
    if u still face the problem please reply me back.
    Thanks
    Rinku

  • Problem RFC sender

    Hello,
    I have a new Problem about a sending RFC in XI.
    Once I send a test-RFC from R/3 se37 it reaches the rfc sender channel but there I get an error in cc-monitoring(the same is displayed in R/3 then as well).
    The error says:
    Processing error caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'CC_RFC_sender_RFC2JDBC' (104238c5fe4c345e8e85752a84330c5c, party '', schema 'TechnicalSystem', identifier 'E10#400')
    Can you help me?
    I don't understand the error.
    CPA-Cache Refreshs do not work.

    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".
        * 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

  • Problem in receiving messages via RFC Sender Adapter

    Hi,
    I have problems in receiving messages from SAP backens systems. Sometimes we are getting all messages sometimes not. Strange.
    We are transfering report-results via asynchronous RFC calls. To avoid big message sizes we split them up in max. 1000 rows blocks.
    Each RFC call on backend side is completed with COMMIT WORK!
    We increased the number of connections in the RFC sender adapter. Then it was better, but the problem still exists! Not so often, but sometimes !?!?!
    I hope everybody can help me. Thanks a lot!
    best regards,
    Hannes

    hi,
    when you don't receive messages what do you see in SM58
    on the r3?
    any errors over there?
    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>

  • Problems in RFC Sender adapter

    Hello
    I am having a scenario where I am sending the message through RFC sender. The message is getting posted on integration server but its giving error in SXMB_MONI.
    The error says
    "HTTP response contains status code 503 with the description Service Unavailable XML element Envelope missing in SOAP message header (SAP XI Extension)" in call adapter.
    I checked some notes mentioning about poll parameter of sap af messaging in visual admin but still the problem is same.
    Thanks in advance.
    Regards
    Rajeev

    Udo,
    I checked the file adapter but the status is green which says "No message processing till now" and also it is not listed in Message monitoring.
    Also as described in note mentioned by shekhar I tried to change the Visual Admin poll interval. also i tried that URL which gave "Messaing servlet is active"
      <?xml version="1.0" encoding="UTF-8" ?>
    - <scenario>
      <scenname>MSG_SCEN</scenname>
      <scentype>SERV</scentype>
      <sceninst>MSG_001</sceninst>
      <scenversion>001</scenversion>
    - <component>
      <compname>SERVLET</compname>
      <compdesc>Messaging System</compdesc>
      <comphost>localhost</comphost>
      <compinst>MSG_001</compinst>
    - <message>
      <messalert>OKAY</messalert>
      <messseverity>100</messseverity>
      <messarea>QR</messarea>
      <messnumber>801</messnumber>
      <messparameter>na</messparameter>
      <messtext>MessagingServlet is active.</messtext>
      </message>
      </component>
      </scenario>

  • Problems at receiving messages at RFC-Sender

    Hi all,
    i have configured the following scenario in NWDS for testing a message flow in PO:
    SOAP request comes into PI -> map Request to RFC -> send request to ERP Test System -> wait for RFC Response -> send to PI -> map Response to SOAP -> send to File
    Therefore i have, amongst others, created a RFC Channel for sending the RFC response to the mapping operation.When i run the scenario for the first time everything worked pretty well without any error messages. But after testing it the second time the message got stuck in the ERP Test System and couln't be forwarded anymore. It turned out that whenever i deployed the channel with some config changes, the message flow worked for the first time, but crashed after every following.
    In the error log i get the following message:
    java.lang.RuntimeException: Bean Z_PP_PDES_RESPONSE not found on host xxx, ProgId =RFC_HMC100_POD: Object not found in lookup of Z_PP_PDES_RESPONSE.
    at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:121)
    at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:267)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
    Caused by: com.sap.engine.services.jndi.persistent.exceptions720.NameNotFoundException: Object not found in lookup of Z_PP_PDES_RESPONSE.
    When i look in the message log at the same position of a successful message, the log says...
    MP: processing local module localejbs/RfcAFBean
    ... which is actually the module defined in the channel.
    So for me it looks like that after the first run something in the module config crashes and the channel tries to use Z_PP_PDES_RESPONSE instead of the RfcAFBean.
    Any help very much appreciated!!!
    Thanks,
    Maurice

    Issue has been solved! There has been a running jco server with same program id as the one of the scenario. This led to complications. After stopping the server it worked perfectly...

  • Help with RFC sender, Program And RFC Destination

    Hi!!
    my scenary is asynchronous
         RFC Sender -> SAP-XI -> Oracle reciever
    I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI  receive the message but the message is empty.
    1. In my program on the line
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
    2. I rewrite my program, that line to
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
    3. I rewrite my program, that line to
              CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
              No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
    What is my Error?
    Where am i making a mistake?
    RFC
    FUNCTION zbapi_sd_ped_ord_servic.
    *"Interfase local
    *"  TABLES
    *"      PED_ORDEN STRUCTURE  ZSD_RFC_T04
    *"      RETURN STRUCTURE  ZSD_RFC_R06
      TABLES: zsd_ped_orden, zsd_rfc_r01.
      DATA: tb_ped_orden LIKE zsd_ped_orden  OCCURS 0 WITH HEADER LINE,
                     tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
    *Get Pedido by Ordenes
      SELECT  *  INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
              FROM zsd_ped_orden
              WHERE estatus  EQ  space.
      LOOP AT tb_ped_orden.
        MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
        APPEND ped_orden.
        tb_ped_orden-estatus = 'X'.
        tb_ped_orden-fecha_actualiz = sy-datum.
        tb_ped_orden-hora_actualiz = sy-uzeit.
        MODIFY tb_ped_orden.
      ENDLOOP. 
      MODIFY  zsd_ped_orden FROM TABLE tb_ped_orden.
      COMMIT WORK.
    *Errors in Ordenes
      SELECT  *  INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
              FROM zsd_rfc_r01
              WHERE estatus  EQ  space.
      LOOP AT tb_rfc_orden_error.
        MOVE-CORRESPONDING tb_rfc_orden_error TO return.
        APPEND  return.
        tb_rfc_orden_error-estatus = 'X'.
        tb_rfc_orden_error-fecha_actualiz = sy-datum.
        tb_rfc_orden_error-hora_actualiz = sy-uzeit.
        MODIFY tb_rfc_orden_error.
      ENDLOOP.
      MODIFY  zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
      COMMIT WORK.
    ENDFUNCTION.
    PROGRAM
    REPORT  ZBAPI_SD_PED_ORD_SERVIC.
    DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
          return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
    CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
         TABLES
              ped_orden             = ped_orden
              return                = return
      EXCEPTIONS
        communication_failure = 1
        system_failure        = 2
        OTHERS                = 3.
    IF sy-subrc <> 0.
      MESSAGE 'error' type 'I'.
    ENDIF.
    COMMIT WORK.
    RFC DESTINATION
    RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
    Connection TYpe: TCP/IP Connection
    Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
    Gateway host: host00
    Gateway service: sapgw00

    hi
    For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
    a) RFC destination
    b) RFC channel in the XI directory
    This weblog is a response to a few question about the basic configuration of the RFC sender adapter
    that were posted on the XI forum (and also on my e-mail)
    So here we go, basically we have to configure 2 things:
    a) RFC destination
    b) RFC channel in the XI directory
    RFC destination:
    1. To create the RFC go to TCODE: SM59
    2. Create new destination of type T (TCP/IP)
    3. Make sure you select Registered Server Program option before writing your program ID
    4. Write you program ID (remember it's case-sensitive)
    5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
    7. No configuration in the J2EE administrator nessecary
    Now we can proceed to RFC channel configuration:
    1. Enter your Application Server
    2. Your Application Server Service
    3. Enter your Program ID from the RFC destination
    And we're done:)
    Now you can test the RFC destination in SM59 to see if it works.
    Please chk this following link.
    1. RFC Processing with the RFC Adapter
    http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
    2. Configuring the Sender RFC Adapter -
    http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
    3.  /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
    regards
    Manas

  • RFC Sender Adapter - MP: exception caught

    Hi Friends,
    We have one RFC to SOAP scenario in our PRD system.
    When we execute an RFC in the R/3 side, the sender RFC CC receives the message. (The message id is generated). But, the message is not entered into SXMB_MONI.
    When we checked the audit log. The error is as below:
    RfcAdapter received sRFC for Z_RFC_SUPER_ACK from P88/300. Trying to send message synchronously.
    MP: entering1
    MP: processing local module localejbs/RfcAFBean
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection RFC_http://sap.com/xi/XI/System is currently not started.
    We have checked Program ID, RFC Connections in R/3 system. It is correct. The standard module "  localejbs/RfcAFBean -  Local Enterprise Bean " is used in the sender CC, only this module.
    We have few RFC receiver communication channels, all are working fine.
    Only this Sender RFC CC, we are facing this problem.
    We found the similar thread "RFC-Connection not started ?".  The same problem we are facing. They suggested to bounce the system and restart.
    Since it is PRD system, it is not able to do that immediately.  Since all RFC receivers are working fine, we feel that it is not required to bounce.
    Can you kindly help me friends, how to solve this problem.
    Thanking you,
    Kind regards,
    Jegathees P.

    Hi Sabarish
    The RFC sender cc is active in ID and started. 
    The status of the channel in CC monitoring is red. (due to this error).

  • RFC 2 File Error in RFC sender: java.lang.ArrayIndexOutOfBoundsException

    Hello,
    I'm sending data asynchronously from R3 to a file through XI, I've got the RFC destination (in R3) and sender RFC channel (in XI) configured and tested. Working fine.
    Then in my report I've got the following code that sends 1 string and 4 internal tables 2 to XI:
      CALL FUNCTION 'Z_RFC_ENVIAR_DATOS_PSP'
        IN BACKGROUND TASK DESTINATION 'SAP_2_XI'
        EXPORTING
          RUTA                       = p_ruta
        TABLES
          IT_DEMANDA           = p_gt_demanda
          IT_STOCKS              = lt_stocks
          IT_CUARENTENAS   = lt_cuarent
          IT_COMPRAS           = lt_repartos.
      COMMIT WORK.
    I've done that king of connection several times and allways worked but now I've got that error in the communication channel monitoring at RWB:
    Error in processing caused by: java.lang.ArrayIndexOutOfBoundsException
    And no message is created in XI. What can it be?
    Thanks for your help

    Hi Chen Lin,
    The problem is with the adapter but no message is generated yet in XI, so I don't have XML yet.
    The RFC sends the data to XI through the RFC destination and at this point something is wrong because that error is produced. The error is visible in both sides, In transaction SM58 at R3 I can see the error that tRFC hasn't been precessed because the ArrayIndexOutOfBoundsException.
    But if I go to communication channel monitoring I can see the same error too, so that confirms that the communication between R3 and XI works fine but something is wrong and the error don't give me more details

  • How to send data to RFC Destination(RFC SENDER Adapter)

    Hi ,
    Scenario:  R/3 Backendà RFC Sender Adapterà XIàsome other system.
    I have configured the RFC destination (of the type TCP/IP) at R/3 System and have registered the Program ID (specified in the RFC destination) in the XI server and using it in the configuration parameters of the RFC Sender Adapter.
    Problem: I do not know how I can send data to the RFC destination. (Should I use a report program/ ABAP Function Module?) Can anybody provide me with a sample code of Report Program/Function module (whichever is required), how to send data to the RFC Destination, so that it may be picked up by my RFC Sender Adapter.
    Thanks and Regards,
    Siva Maranani

    I have one query for you that
    I am trying to develop a scenario in SAP XI
    SAP R/3 ( RFC function module) sends a synchronous request to the XI and SAP XI will send this request to a third party web application using HTTP receiver adapter.
    I am able to send the data/message and it is successfully received at the third party web application.
    But I am facing one issue that I am unable to receive any message/data in my RFC module back.i have seen in sxmb_moni that the two messages are displayed in successfuly processed but in SAP R/3 side nothing get happedned
    Can you tell me how to use some waiting mechanism in function module to wait for the response from SAP XI.
    Regards
    Gopesh

  • Errors in RFC sender Adapter

    Hi Guys,
    I am configuring a RFC sender Adapter in a newly installed system.
    I configured the adapter as per the parematers given in SAP help in the exact way and started getting the error
    Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '*', fromService 'RD1CLNT020', toParty '', toService '', interface 'Z_TEST', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'RD1CLNT020_IN' (channelId 897afca12ee93b86a5bfcd738c037099)
    If I go into SXI_CACHE of the PI system I can see the entry.
    My gut feeling is that the adapter is not fetching the metadata properely.
    Because I switched the metadata loging from the ECC system to PI system and I got the error
    JCO.Server could not find server function 'Z_TEST'
    I think in the basis setup we have missed something The version on which we are working is the Latest PI 7.1
    If somebody has a document at the the config for JCO or a solution for this problem will be much appreciated.
    Thanks & Regards
    Gagan Kasana

    Hi,
    there is no magic with this error - it's a common one
    1. my blog - RFC sedenr adapter config -
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    then is still does not work:
    2.check out OSS note  730870 - FAQ RFC Adapter
    "Question 19:
    While sending a RFC call to the RFC Adapter I get a error message like "com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of binding via CPA-cache failed..." or "com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed...". What is missing?"
    and you have it working
    please let me know if this helped
    Regards,
    Michal Krawczyk

  • Communication Channel RFC Sender getting error suddenly

    Hello gurus,
    I'd like to ask you about a problem, we have many interfaces from RFC to SOAP synchronous, the CC RFC sender, in an average of once per day, gets into red colour with this error:
    Sender channel 'CC_RFC_SENDER_L0_MAESTROS' for party '', service 'BS_LD0_100'
    Error can not instantiate RfcPool caused by:
    com.sap.aii.adapter.rfc.RfcAdapterException: error
    initializing RfcServerPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException:
    can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION:
    Connect to SAP gateway failed
    Connect_PM TYPE=A ASHOST=10.1.4.191 SYSNR=00 GWHOST=10.1.4.191 GWSERV=sapgw00 PCS=1
    LOCATION CPIC (TCP/IP) on local host with Unicode
    ERROR partner 'XX.X.X.XXX:sapgw00' not reached
    TIME Thu May 27 03:56:04 201
    RELEASE 711
    COMPONENT NI (network interface)
    VERSION 39
    RC -10
    MODULE nixxi.cpp
    LINE 3151
    DETAIL NiPConnect2: 10.1.4.191:3300
    SYSTEM CALL connect
    ERRNO 111
    ERRNO TEXT Connection refused
    COUNTER 5
    I don't know the reason of this.. but simply just stopping and starting the CC it gets into green colour again..
    Does anyone know how to solve this?
    Regards,
    Juan.

    Hi,
    This happens if the RFC connection pool is not instantiated or may be cache failed to auto-refresh....And manual restart of RFC channel resolves it.
    Refer page 8 in the RFC troubleshooting guide.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f3f93ee7-0c01-0010-2593-d7c28b5377c2?quicklink=index&overridelayout=true
    Thanks
    Swarup

Maybe you are looking for