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

[Former Member]

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?

[moorthy · Accepted solution]

Hi,

Have a look into SAP note 730870 Question no 15.

Go to Integration Directory->Open Business system->go to Menu i.e Services->Adapter Specific Identifiers

check that is the RFC destination etc is pointing to correct R/3 system i.e ZULIA system.

Also just cross-verfiy with this blog once-

/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step

Regards,

Moorthy

[Former Member · Accepted solution]

Hi,

I checked the note and the question 15.

This are the parameters that I found:

IDOC Adapter

Logical System DEV210

IDoc Adapter and RFC Adapter

R/3 System ID DEV

Client 210

Marketplace Adapter

DDID <i>[EMPTY]</i>

By the way, I followed the blog in order to check my configuration steps and they are the same.

[Former Member · Accepted solution]

Any ideas?

[moorthy · Accepted solution]

Is the RFC destination created in the R/3 is pointing correctly to the XI system and vice -versa. Test the connection.

Try to refresh the Cache, RFC metadata. i.e recreate your Sender Agreement.

Also you check that Business System is correct ?

Regards,

moorthy

[Former Member · Accepted solution]

<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

[moorthy · Accepted solution]

The only error I feel is , your business system is not correclty pointing to R/3 system.

Check the business system in the SLD and check is it pointing to correct Technical system of R/3

Activate the RFC sender Adapter by changing some desc..and activate it.

And then go to SXI_CACHE and delete Adapter cache.

and run again.

Are you getting any error in the Adapter monitor for RFC channel ?

Also you can try to restart the RFC Adapter from the visual admin.

Regards,

moorthy

[Former Member · Accepted solution]

Hi,

I re-active the RFC sender Adapter, I delete Adapter cache by TCODE: SXI_CACHE, there is no

Adapter Monitor for RFC Channel and I restart the RFC Adapter from the visual administrator.

My Business and Technical System look fine.

I get this new error:

"connection to partner broken" / "CPI-C error CM_PRODUCT_SPECIFIC_ERROR"

"CPI-C error CM_PRODUCT_SPECIFIC_ERROR"

Status of connection.... "CODE=CM_PRODUCT_SPECIFIC_ERROR CM_NO_STATUS_RECEIVED
 CM_NO_DATA_RECEIVED SAPCODE=223 CONV=08032286"
Internal error code.... "RFC_IO5"

Thanks in advance.

[Former Member · Accepted solution]

Hi,

I have a very similar problem... how do you restart the RFC Adapter from the visual admin? where is the visual admin?

Thank you very much!!

Isabelle

[Former Member]

Hi Luis,

You could have an issue because the RFC definition has changed and the cache is out-of-synch

1) Reimport and activate the RFC.

2) Restart the RFC Adapter service in the Visual Administrator. This will flush the metadata cache in case the RFC has changed.

If this doesn't work, verify that your Sender Agreement is setup correctly

1) A common mistake is to create a Message Interface in the IR (Design) for RFC and IDoc senders and point the sender agreement to this Message Interface which won't work. The Sender Agreement should be setup as follows:

Service: SAP Business System

Interface: RFC name

Namespace: urn:sap-com:document:sap:rfc:functions

Thanks,

Jesse

[Former Member]

Hi Luis,

Pls check the note no 730870 for RFC adapter and also make sure that the cache is fine in SXI_CACHE transaction.

Cheers

JK