Skip to Content

Error related to CPA cache encountered in RFC Sender


Recently I encountered an error when Configuring an RFC connection in a newly Installed SAP PI 7.1 system.

I got the solution and wanted to share with everyone of what I did.RFC configuration steps can easily be found on the Blog by Michal Krawczyk

 The specified item was not found. and OSS note 730870 also discusses many errors encountered But even going thru these did’nt help my error of “ lookup of binding via CPA-cache failed…”

was not removed.

The solution is PI creates channels and sender agreement always with party = ‘*’. Especially when you use the Wizard to do the configuration.So when you are Implementing a Sender RFC adapter.
So copy the Communication channel and sender agreement to empty party (without star).

I also wanted to discuss some best Practises related to Sender RFC.

One thing in all the implementation I noted was that I had to maintain a separate RFC channel for each Sender Interface simply because the way RFC works for sender they require an independent Channel, RFC cannot share a common channel between ECC and PI. 

 This resulted in many RFC channels and they had to be maintained in a bespoke table as RFC name differ form System to System.The long term Impact is that whenever there is clients refresh all the maintenance of these tables had to be done.

I would like you to post your experience with RFC and how you overcame them and if you are aware of some best practises.


Gagan Kasana  




You must be Logged on to comment or reply to a post.