cancel
Showing results for 
Search instead for 
Did you mean: 

RFC Call from R/3 to XI

Former Member
0 Kudos

Hi there,

I get the following error message with RFC Sender Adapter (R/3 4.6C to XI 3.0):

"lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS".

We are currently on SP9 and i have checked both OSS notes on this topic (730870,775765)

Does anyone have any ideas on this one?

Regards,

Ginish

Accepted Solutions (1)

Accepted Solutions (1)

JiriEhrlich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Ginish,

do you have configured Sender Agreement from your Business System?

Jiri

Former Member
0 Kudos

Sender Agreement has been defined! Thanks

I can see the XML message in the XI XML Monitor however it does not trigger the BPM.

What should the (Message Interface) TYPE be in the container operation be in the first recieve step? I have imported the RFC into XI as Z_BC_CASH, it has a request/response message type.

Should the first recieve step be sync or asynch? I have tried both ways and get a similiar error from the XML Monitor. "The calling of synchrounous messages not supported"

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi - Did you find a solution to your problem? We running SP9 of XI 3.0 too. RFC function module to XI with Dest of XI box. Our error is -> lookup of binding via CPA-cache failed for AdapterType RFC, AdapterN.

Any Idea?

former_member185751
Contributor
0 Kudos

William/Ginish,

I too faced the same problem for quite some time on SP9. I thought it was the adapter problem that persisted ...but it was not !!

After importing the RFC structure into XI, if the name of the imported RFC program is renamed/changed on R/3 side, then you will get the same error "lookup of binding via CPA-cache failed for AdapterType RFC, AdapterN."

So make sure that RFC program name on the R/3 side was not changed/renamed after you have imported the RFC structure into XI.

If the RFC program name had changed, make sure you reimport the RFC structure to avoid this problem.

Regards,

Sridhar

JiriEhrlich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Sridhar,

I hope following procedure is part of our online help:

After changing FM structure you have to:

1. Delete imported RFC (ignore warnings)

2. Import RFC again

3. Activate changes

4. Set status of RFC adapter inactive

5. Activate changes

6. Set status of RFC adapter active

7. Activate changes

It is a quite simple procedure

Jiri

former_member185751
Contributor
0 Kudos

Hello Jiri,

I'm well aware of the procedure listed.

My post is not related to the change in the RFC structure. It is only about the change in the "name of the Function Module/RFC Pgm" on the R/3.

I understand that the RfcAdapter uses the following values for the lookup to find a Sender Agreement for the RFC call:

1.Sender Party/Sender Service

2.Sender Interface: Name of the function module.

3.Sender Namespace

4.Receiver Party/Receiver Service (if empty will match with wildcard '*')

And if anyone of the above is wrong/missing then the error :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..." occurs.

In our case, One of our ABAP developers had inadvertently changed the name of the RFC program when he was transporting from DEV to TST environment. since the "name of the function module" did not match during lookup, the error occured.

-Sridhar