RFC Sender - lookup of alternativeServiceIdentifier via CPA-cache failed

Hello,
I am using RFC Sender for a scenario and while sending message I got following error. I found this error while monitoring communication channel. I looked at several posting on this issue and tried with both checking  and not checking check box of advanced mode (RFC sender communication channel configuration). I am getting the same "lookup of alternativeServiceIdentifier via CPA-cache failed" error. How did you resolved?, please let meknow.
Did any one come across error
Server 0 0_50478 Sender channel 'CC_GET_CUSTOMER_RFC_SENDER' for party '', service 'SAP_DFR' (internal name 'RfcServer[CC_GET_CUSTOMER_RFC_SENDER]')
Server data: {jco.server.gwhost=XXXXXXXXXX, jco.server.progid=DFX_XI_00, jco.server.gwserv=sapgw00, XI_RFC_USER=*****, jco.server.unicode=0}
Repository data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=120, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=XI_RFC_USER, jco.client.sysnr=00, jco.client.ashost=XXXXXXXXXX}
Current pool size: 1, maximum pool size : 1
Channel History
- Error: 2007-09-20 10:32:14 CDT: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'CC_GET_CUSTOMER_RFC_SENDER' (bee9e190f51f3687b1072bf3f5446a70, party '', schema 'TechnicalSystem', identifier 'DFR#120')
Thank you,
Balaji

run tc SXI_cache on the XI
on that screen press Shift+f6, it will start the refresh....and also do the CPAcahe manually trough the link
http://itmisapxi:50000/CPACache/refresh?mode=full
with PIRDIRUSER and then check the interfce....

Similar Messages

  • Lookup of alternativeServiceIdentifier via CPA-cache failed for channel

    Hi,
    In RFC(ECC) to File(PI) scenaio  i am facing the following error in sender CC:
    Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel SND_RFC
    -CC' (f455868123qq3bba4c3dc3dbf93ed1b, party '', schema 'TechnicalSystem', identifier 'ECC#110')
    I have done the following for RFC to File scenario:
    ECC side:
    1. Created a RFC and tagged it to BAPI
    2. In the ABAP program, i am calling the RFC like below:
    CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
    IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
    EXPORTING
    INTERFACE =
    IMPORTING
    FILENAME = FILENAME
    RETURN = RETURN
    TABLES
    ITAB10 = ITAB10
    P_STATUS = P_STATUS
    COMMIT WORK.
    3. Created a RFC destination using SM59
    RFC detination : Z_HR_OUTBOUND_DATA2
    Connection type : TCP/IP
    Enabled Registered Server Program
    Program ID : ECCTOPI_OUTBOUND
    Gateway host : ECC's host number
    Gateway service : ECC's service number.
    In PI side:
    I have created :
    1 DT for File Rcvr
    1 MT for File Rcvr
    1 SI for File Rcvr (async)
    1 MM (sender RFC and receiver File)
    1 OM
    1 CC with RFc as sender with the following parameters:
    Communication component : ECC's component
    application server (gateway) : ecc's gateway
    application server service(Gateway) : ecc's service number
    Program id : ECCTOPI_OUTBOUND
    inital connections 1
    max. connections 1
    And also gave ecc's details in application server , s/y number, auth. mode, logon user ,
    pwd, ecc's client number
    1 CC with File adapter and file content conversion
    1 receiver determination
    1 interface determination
    1 sender agreement
    1 receiver agreement
    When i am executing the ABAP program in R/3 I am getting the following error:
    Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel SND_RFC
    -CC' (f455868123qq3bba4c3dc3dbf93ed1b, party '', schema 'TechnicalSystem', identifier 'ECC#110')
    Please let me know if any of my steps are wrong and how to rectify this error and make
    the scenario working.
    Thanks for your help.

    I have mentioned the Adapter specific parameters properly.
    It contains :
    For ECC s/y(i.e for RFC)
       Logical system :  DECCLNT120
       R/3 system ID : DEC
       Client 120
    For PI (i.e for File)
       Logical system :  DPICLNT100
       R/3 system ID : DPI
       Client 100
    Since i am sending the Response of the RFc to the file, i have used a Service interface where i am passing the RFC.Response as Request.
    if i am passing the RFC directly as i/p in Source operation of Operation mapping then it doesn't pick up the response in the souce message of the mapping program present in Operation mapping.
    So i am passing the same SI_Sender_RFC in the Sender Agreement and  it gives 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 'DEC_RFC', toParty '', toService '', interface 'Z_HR_OUTBOUND_DATA2', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_LOTUSNOTES_OUTBOUND_SND_RFC' (channelId c78f5a88787131a09384c07c2db0e93b)
    why is it so?

  • Error: Sender agreement not found, lookup of binding via CPA-CACHE failed.

    Hi,
    I am doing an RFC to File Scenario in which RFC has to be triggered from CRM system. The TCP/IP connection and communication Channel are working fine. But when i trigger my RFC using the RFC destination following errors occur:
    1. The SYSTEM_FALIURE exception comes on CRM side.
    2. In adapter monitoring the following error comes on XI side:
           Error: Sender agreement not found, lookup of binding via CPA-CACHE failed for Adapter type RFC.
    I have also tried the scenario with RFC request as source message and also after J2EE cache refresh but the problem still persists. And one more thing my file adapter (In receiver communication channel) is not working means it is not started. And no message is coming in SXMB_MONI.
    Could anyone please help me to resolve this issue.
    Regards,
    Vinay Yadav

    Hi Aaron,
    I had the same error and your feedback solved my problem!
    Thank you sooo much!!!!
    Luciana

  • "senderAgreement not found: lookup of binding via CPA-cache failed for..."

    Hi,
         I have configured asynchronous sender RFC to JDBC scenario and when I execute RFC I get short dump "senderAgreement not found: lookup of binding via CPA-cache failed for..."
         My scenario configurations, RFC destination, are all okey..
    A Hint:
         Our XI Server is "LARA"
         Our R/3 4.6C Server is "ZULIA"
    This are the RFC Sender Communication Channel on LARA:
         RFC Server Parameter
         Application Server (Gateway):           ZULIA
         Application Server Service (Gateway):      sapgw00
         Program ID:                     DEV210
         SNC:                          NOT CHECKED
         UNICODE:                     NOT CHECKED
         Inital Connections:               10
         Maximum Connections:               10
         Advanced Mode:                    NOT CHECKED
         RFC Metada Repository Parameter
         Load Balancing:                NOT CHECKED
         Application Server:               ZULIA
         System Number:                    00
         Authentication Mode:               Use Logon Data for SAP System
         Logon User:                    ldiego
         Logon Password:                    **********
         Logon Language:                    ES
         Logon Client:                    210
         Adapter-Specific Message Attributes
         Set Adapter-Specific Message Attributes: NOT CHECKED
    This are the configuration of RFC Destination on ZULIA:
         RFC Destination Name:                XI_RFC
         Connection Type:               T
         ID Program:                    DEV210
         Host Gateway:                    ZULIA
         TCP Service                    sapgw00
    Must I create the RFC Destination on the JCo RFC Provider in Visual Administrator?

    <i>Is the RFC destination created in the R/3 is pointing correctly to the XI system and vice -versa. Test the connection.</i>
    I tested my RFC Destination from R/3 system and the response was successful. What do you mean about vice-versa? How do I test it in the other way?.
    I recreate my Sender Agreement. And my Business System is correct.
    This are the parameters of my Sender Agreement:
    Service:     DES210_DEV
    Interface:     Z_DATOS_SAP
    Namespace:     urn:sap-com:document:sap:rfc:functions
    Sender Communnication Channel: cc_s_rfc_dataCom
    When I execute the FM in R/3 the dump now is:
    Wrong Sender Agreement:The Sender agreement does not have channel

  • RFC Sender error - lookup of alternativeServiceIdentifier

    Hi,
    I am trying to configure an R/3-XI-Java proxy scenario using the RFC adapter as sender. When I execute the RFC on the R/3 system using the RFC destination, I get the exception SYSTEM_FAILURE. In the RFC adapter monitor, the error message  is "com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel". I have verified the settings mentioned in SAP note 730870 (Q. 15), but am still getting the same error. Please let me know how to resolve this error.
    Thanks,
    Sumanth.

    Hi Sumanth,
    Check the <i>Adapter Specific Identifiers</i> in the Business sytem which contians RFC adapter.
    Make sure that R/3 System ID is equal to the one specified in the SLD.
    You can also "compare" the same with that in the SLD.
    You should concider clearing the SLD data cache before comparison
    Cheers,
    Rashmi

  • 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

  • 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

  • R/3 to PI using RFC Sender Adaptor as Asynchronous scenario

    Hello Folks,
              RFC Adp.           SOAP Adp.
    ECC-->XI--
    >ARIBA
    I am new to PI and doing a scenario mention above. we are using RFC sender adaptor to send the data to XI in asynchronous process.
    I have config the Sender comm. channel as below.
    Appl.  Server(Gateway):  My Ecc Server host name
    Appl. Server Service (Gateway) : My Ecc server
    Program Id : XYZ.
    Note : while creating the the Service interface and Message mapping and Operation mapping I am using the RFCname.respone message type is that ok in asynchronous process?
    And then I went to ECC in Tcode SM59 and created a RFC destination of type TCP/IP
    and put the same information as given above and test the connection which is working fine.
    I have created a FM at ECC end make it remote enabled. and calling the FM in back ground task using destination in a Work flow code.
    When I run the Work flow code It ran successfully but i went to XI side there is no msg in the SXMB_MONI.
    Then i went to the component monitoring->Adatptor engine>Comm. channnel Monitoring and found that under my RFC sender comm. channel there is an error msg saying
    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 'BS_ECC', toParty '', toService '', interface 'YFPS_MM_I_0242_PO_APPROVAL_OUT', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_0242_PO_Approval_RFC_Sender' (channelId 19585252a58335ee871e4c3a771b027f)
    Where as i have checked that in the sxi_cache t-code there is a sender agreement for my scenario under the sender agreement tab.
    Please Help me in this to resolve the above error. I am totally stuck at this point.I would really appreciate a quick answer.

    Appl. Server Service (Gateway) : My Ecc server
    Confused with this statement.....
    it should have the format sapgwXX ....
    XX is the system number which comes from the j2ee port mentioned in the XI homepage URL
    http://<hostName>:5XX00:rep/start/index.jsp
    How to configure sender RFC adapter...check this blog:
    https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1438
    Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException:
    senderAgreement not found:
    Sender Agreement is Expected in this communication which does not seem to be present in ID....create sender agreement using the RFC communication channel....
    Regards,
    Abhishek.
    Edited by: abhishek salvi on May 2, 2009 1:24 AM

  • RFC Sender adapter - Sender agreement not found Error

    Hi ,
    I am getting this error when i send an RFC request to XI from SAP.
    Exception thrown [Fri Aug 05 10:10:35,624]:Exception thrown by application running in JCo Server
    com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, dapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fomService 'HORIZONISU', toParty '', toServ
    #at com.sap.aii.af.rfc.afcommunication.Message.getEmptyMsMessage(Message.java:345)
    #at com.sap.aii.af.rfc.afcommunication.Message.buildMsMessage(Message.java:215)
    #at com.sap.aii.af.rfc.afcommunication.ToAdapterFramework.sendSynchronous(ToAdapterFramework.java:341)
    #at com.sap.aii.af.rfc.core.server.RfcServer.handleRequest(RfcServer.java:525)
    #at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code))
    #at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code))
    #at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code))
    #at com.sap.mw.jco.JCO$Server.listen(JCO.java:6926)
    I have configured a sender RFC adapter in XI with a specific "program id". This RFC adapter is available under a Business System of type WebAS ABAP in integration directory.
    I have created an RFC in my SAP system (it just has IMPORT & EXPORT parameters, no SrcCode), i also have an RFC destination of type T in SAP which has the program id specified in my RFC adapter config. The application host & gateway in this RFC destination point to itself(points the same SAP system where the RFC destination is created)
    Now i trigger the RFC from an other function module with destination parameter pointing to the RFC destination of type T created in SAP.
    Is the above config ok ? If not what do i need to check , pointers pls. I get a dump in SAP when i execute the function  module calling the RFC , and i see the above stacktrace in XI log.
    Thanks
    Saravana

    Hi Saravana,
    1. have you created a senderAgreement for your scenario? (senderAgreement not found)?
    2. do you commit your RFC call with commit work? ( just to make sure )
    3. is your RFC dest working? when you test it in SM59?
    Regards,
    michal

  • 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

  • RFC Sender adapter error

    Hi Folks,
    Am trying an RFC to SOAP sync interface.
    Hav configured the Adapter, registered the program at PI, created RFC using registered server program.
    When I trigger the FM as Call Function '..' DESTINATION <rfc dest> i get a system failure.
    IN RWB Channel monitoring I see the error as "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 'SAPECC_SHD', toParty '', toService '', interface 'ZBAPI_WEBSERVICE1', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_SAP_ZUMMATION_RFC_S' (channelId af2f451f1b473ac28063768416ba8a72)"
    Have checked for errors such as * in sender agreement, header data in Receiver agreement note 730870..
    Kindly guide if there is anything to be checked.

    Hi,
    Clear the cache (SXI_CACHE) and stop and restart the RFC sender channel in RWB.
    Cheers,
    André
    Edited by: André Schillack on Mar 30, 2010 5:09 PM

  • RFC sender in PCK

    Hi Experts,
    I have this proposed scenario:
    RFC -> PCK -> PI -> HTTP server
    To do so, I trying to configure the PCK to receive the RFC sender message and forward it to de PI.
    I created in PCK a Party with empty name and two services, one for the ECC sender (RFC) with it's name and other with empty name for the PI receiver.
    The communication channels and its agreements were configurated to only forward the received message to PI.  I don't find any errors on them.
    When I run the RFC, I am receiving this error:
    Error in processing caused by: com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=DE1;TS=;AN=ZTI_RFC_PI;ANS=urn:sap-com:document:sap:rfc:functions; caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIAdapterFramework:GENERAL:com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=DE1;TS=;AN=ZTI_RFC_PI;ANS=urn:sap-com:document:sap:rfc:functions;
    Do you have any ideia about what can be wrong? Wich component should I check?
    I can simple forward the RFC message to the PI or I should map it to another format? If I have to map, how can I import it's definitions to PCK?
    Thanks anyway,

    Hi Stefan,
    The agreements already had the receiver information.
    Anyway, the party and the service were recreated with diferent names. After that, the sender and receiver agreements were also recreated. But, another error began to occur:
    Error in processing caused by: com.sap.aii.af.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 'DE1', toParty '', toService '', interface 'ZTI_RFC_PI', NS 'urn:sap-com:document:sap:rfc:functions'
    for channel 'CC_Sender_RFC_ECC' (channelId 5aa283a1c598bb6be787eeb6460772f8)
    I think that's related to the RFC message header, that contains the receiver service and party empty, as seen in the error message (toParty '', toService '').
    But if I create a party and service with empty names the previous error occurs again.
    Any ideia about how to deal with RFC sender in PCK?

  • RFC Sender Channel Issue : STFC_CONNECTION

    Hi All,
    There has been an issue with the RFC sender channels. When SAP triggers the data, we see an error in the RFC sender channel as below
    Error in processing caused by: com.sap.aii.af.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 '<ServiceName>', toParty '', toService '', interface 'STFC_CONNECTION', NS 'urn:sap-com:document:sap:rfc:functions' for channel '<ChannelName>' (channelId 7f84f67e7efe39949dc12a2f569236fb)
    But the data gets processed at the very next moment.
    Program ID used in the channel is same as the ID registered in SAP. Is there some configuration missing either at SAP PI or SAP R/3 system?
    Regards,
    Prajeet

    Hi Prajeet,
    please refer this wiki [link  |https://wiki.sdn.sap.com/wiki/display/XI/RFC+Faqs?showChildren=false]Q19,hope this helps.
    Check if you are using the same program ID in multiple scenarios. May be  if  you keep different the program ID names in different RFC adapters, it should resolve the error.
    also check here :/people/danny.deroovere/blog/2008/02/26/change-client-in-scenarios-with-sap-business-system
    Regards,
    Srinivas

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

Maybe you are looking for