on 04-27-2009 5:52 PM
HI Experts i got a error in RFC Communication Channel.
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_Bapi_ECC', toParty '', toService '', interface 'GWY_READ_CONNECTED_SYSTEMS', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'cc_bapi_ecc_sender' (channelId ec20a79c0be73c2bac7d18cfaecbd1ee)
Perform a full CPACache refresh using the following URL and PIDIRUSER.
http://Host:5xxxx/CPACache/refresh?mode=full
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi When i go to developer trace of rfc it showing this error / message
======> senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC,
AdapterNS http://sap.com/xi/XI/System, di
Hi Praveen,
I think your sender agreement is not updating properly in cache. Please do a cache refresh as mentioned in this document:
Regards,
---Satish
Hi,
Ask your basis guys to do a full CPACache refresh using PIDIRUSER only..........
Then ask your basis guys to see if some error occurred during this CPACache refresh and ask them to resolve it........if this CPACache refresh did not show any error, then rerun your scenario.
Regards,
Rajeev Gupta
Hi Praveen,
Did you get solution to this issue. I am facing the same issue. Could you please advise me what is the possible solution.
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)
Regards,
Jay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jayaram,
I solved this issue (senderAgreement not found) by reading this link: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
The problem was with the ' * ' value in the PARTY property of the communication channel.
I created another one with an empty value and it worked.
Hopes it help,
Martin
take the help of the SAP Note 730870
also ref: /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If nothing work then delete your sender agreeement and recreate it.
After activating then new sender sgrement please see cache notification from Environment-->Cache Notification in ID. It must be green if sender agreement's entry properly created into the cache.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.