Getting senderAgreement not found: lookup of binding via CPA-cache failed!

[gopalkrishna_baliga]

Hi Experts,

I am making RFC call from R/3 system to SALERT_CREATE function module in XI.

R/3--

---

RFC----->XI

I am using this to trigger alert.

I have the all the parameters of the function module correctly but it is giving following error:

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

What I have to do to resolve this? This is just a function module call. Why it is asking for sender agreement?

Please help me! URGENT!

Thanks

Gopal

[bhavesh_kantilal]

Hi,

What is the end to end flow of the message in XI?

As hyou are sending soem data from the R3 system you need a sender rfc adapter in XI and a TCP IP Connection in the R3 system. Have you done all this?

Regards

Bhavesh

[gopalkrishna_baliga]

Hi Bhavesh,

In R/3 I have written a ABAP code that has some business logic. If business validation fails then I have to send a alert. So in the ABAP code I am just calling the XI function SALERT_CREATE like below.

CALL FUNCTION 'SALERT_CREATE' DESTINATION 'SYXI250'

EXPORTING

ip_cat = 'BUS_ALRT'

TABLES

it_container = i_cont.

[bhavesh_kantilal]

><i>CALL FUNCTION 'SALERT_CREATE' DESTINATION 'SYXI250'

EXPORTING

ip_cat = 'BUS_ALRT'

TABLES

it_container = i_cont.</i>

You are triggering the SLAERT FM to XI. So this will need another interface in XI to get the Alert call.

Just as when you call another FM from R3 to XI, you need an interface you will need one here as well for the SLAERTCREATE RFC.

Regards

Bhavesh

[gopalkrishna_baliga]

Hi Bhavesh,

I did this now. I have created the sender agreement where

Sender service = SYXI250

Interface = SALERT_CREATE

Communication channel - gave my sender RFC channel

I think ONLY sender agreement is fine right? Do I have to create interface determination, receiver determination etc. I don't have any receiver for this.

Now I am getting another error:

RFC state: " "

RFC error text: "RFC_ERROR_SYSTEM_FAILURE"

CPI-C error text: "call to messaging system failed:

com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:"

Kindly help!

Thanks

Gopal

[bhavesh_kantilal]

Hi,

You need to have a separate Interface for triger the alert.

This would mean receiver determination interface determination etc.

Also, in the report you will be using a separate TCP IP connection for this and this new TCP IP's Program Id will be used in the new sender RFC adapter etc.

Regards

Bhavesh

[gopalkrishna_baliga]

Hi Bhavesh,

On second thought can't I use TYPE 3 remote destination to connect to XI system?

If I create a sender agreement then it is asking for receiver determination and interface determination. In my case the receiver is the XI system itself.

In other words, my RFC call is going to XI system. After that it is not going anywhere. So no other receiver.

What receiver agreement I can create to connect to the same XI system?

My requirement is simple. I want to execute a function module residing in XI system from a remote R/3 system.

Kindly help!

[Former Member]

Gopal,

>>I want to execute a function module residing in XI system from a remote R/3 system.

But why would you need that?

Can you tell us your business requirement here.

Regards,

Jai Shankar

[gopalkrishna_baliga]

Hi Jai,

Here is my business reqmt:

XI reads inventory file and makes a RFC Function module (YREAD_INVDATA) call to R3 system.

In R3 system function module I have written business validation logic.

If any validation fails then I have to trigger alert. The CCMS alert is setup in the XI system. So to trigger alert I am making a RFC call (CALL FUNCTION SALERT_CREATE DESTINATION 'SYXI250'...) to XI.