Skip to Content
avatar image
Former Member

outbound binding exception: No receiver agreement found


We have a synchronous scenario in XI HTTP -> RFC.

This scenario is working fine in all environment dev,qa,prod.

It is strange to me that the scenario is working in most of the times but some time it gives the error OUTBOUND_BINDING_NOT_FOUND (outbound binding exception: No receiver agreement found for , PR0CLNT400, , PRODREQ_LABELS_P,, I15_WorkOrderNumber_OB)

I have seen in the sxmb_moni that in the errored messages the interface names in the sender and receiver is same i.e. I15_WorkOrderNumber_OB but in the successful messages the interface name in the sender is I15_WorkOrderNumber_OB and in receiver is "BAPI_PRODORD_GET_DETAIL".

I need a quick help on this. Because only for few messages this error comes and for all other same messages this error is not comming.

I guess this might be an issue related to some cache problem. but i have checked that in cache no error there.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    May 26, 2006 at 02:34 PM

    Hi Gopesh,

    Are you able to reproduce these errors ? I mean to say , check the same message once again and check are you getting the same error...

    Check These SAP note# 760435,774497,832965

    Hope this helps,



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      <i>As i have already written that this error is not comming always and some times it is comming in prod env, so i can not reproduce the same error again, but at the same time the other messages with same data is working fine.</i>

      Are you sure you are not able to reproduce in QA environment? If you can reproduce this error once again, if you raise SAP customer message then they may help you on this..Still you can raise this to SAP

      Probably timing is the issue here !!!

      Just one thought-If you are getting this type of error while multiple message processing , then

      Increase the maximum number of connections in your RFC reciever Adapter..

      Also check try to make your Sender Adapter EOIO and chek are you able to get this type of error.