I have build simple RFC -> BPM -> File scenario, getting below error.

[yajjala1]

I have build simple RFC -> BPM -> File scenario, getting below 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 'BS_ERPDE2_100', toParty '', toService '', interface 'ZHRO_PBCV3_DEPN_LOAD_OUTBOUND', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_RFCSender_PBC_BenifitEnrollment_DEPOB_DE2CLNT100_V3' (channelId f226a41e3c7f365d9cd7115b9e9c988f)

Thank you

John

[former_member184720 · Accepted solution]

Hi John - The error shows that there is no sender agreement available.

Can you check if your created?

If it is there, please do a cache refresh

[yajjala1 · Accepted solution]

Hello Hareesh,

Unable to upload screens shots here. I can send screens shots if you can have mail id.

Thank you

John

[yajjala1 · Accepted solution]

Hello Hareesh,

Why this is saying INBOUND but I am doing outbound from ERP to INBOUND to PI.

Thank you

John

[former_member184720 · Accepted solution]

That's fine. No need of screenshots

You can verify below things-

-> Cache is updated.

->Sender agreement exists for the above combination

->validate the channel ID i.e. check what is being displayed in error message and what it is in the Integration Builder

[yajjala1 · Accepted solution]

I have done sxi_cache

I have done adapter cache

I have done repository and directory cache

[yajjala1 · Accepted solution]

Yes sender agreement exists, cache updated..

How do I test last steps please explain little detail..

[former_member184720 · Accepted solution]

Can you refer to the Q.no 19 in the below SAP note. It talks about the same issue:

730870 - FAQ XI 3.0/ PI 7.0/ PI 7.1/ PI 7.11/ PI 7.2/ 7.3 RFC Adapter

[yajjala1 · Accepted solution]

I have verified this note this morning, 

Could you please explain about these :

• Sender Party/Sender Service: The values from Party and Service belonging to the sender channel.
• Sender Interface: The name of the RFC function module.
• Sender Namespace: The fix RFC namespace urn:sap-com:document:sap:rfc:functions
• Receiver Party/Receiver Service: These fields are empty. This will match the wildcard '*'.

[former_member184720 · Accepted solution]

First 3 should be fine with your configuration.

The last one - In your sender agreement, do you have "*" in the party/component field ? If it has you need to create a new one without that *

Can you share the screenshot of your sender agreement?

[yajjala1]

I have verified with component monitoring, it works with component monitoring "test message"