CO_TXT_OUTBINDING_NOT_FOUND

[Former Member]

I need your help on Idoc-to-file scenario using Business Service with Party. My Problem is that the Receiver Interface and Receiver Namespace in SXMB_MONI appear same as that of senders and the message goes into the error condition "CO_TXT_OUTBINDING_NOT_FOUND" During technical routing.

No receiver agreement found for sender >> another error in SXMB_MONI

Can you help me, with what needs to be entered in header mapping of received agreement and whether I need to specify anything in Identifiers tab of my Receiver communication channels.

[Former Member]

summary of the solution written above

[Former Member]

The Issue has been resolved.

I went through the SAP NOTE: 792333 . Things are much more well documented here.

Resolution w.r.t this problem: I removed all the Identifiers from the Party and created a Receiver determination with * as party. Initially I had specied the party and service name in the RD.

Now I successfully receive the IDOCs into XI system from Test as well as Support R/3 systems.

[former_member200962]

have you created the following objects in ID:

1) Receiver Determination....with OB MI, and receiver Busines service in the receiver section

2) Interface Determination between source(IDOC) and target(FIle) MIs

3) Receiver Agreement and a corresponding File Receiver File CC

[Former Member]

Yes, These things are in place. Infact I am successfully receiving the Idoc from another application system i.e. Test system, now I have copied the exeiting objects so that I can receive the same Idocs deom R/3 support system as well.

The R/3 Test system to SI test works fine. But R/3 Support system to XI test fails.

[former_member200962]

now I have copied the exeiting objects so that I can receive the same Idocs deom R/3 support system as well.

copying saves time but can cause problems afterward (like the one you are facing).....I suppose the source Business systems will be different.....were you able to change it accordingly the Source (Sender) service section?...i doubt

[Former Member]

Yes, Things seem to be working fine untill technical routing happens where it gives the following error:

No receiver agreement found

I tried cache refresh, re-creating objects etc. I guess something needs to be added in receiver agreement

>> Header mappings

[former_member200962]

No receiver agreement found

Other than a valid Receiver service, MI and CC I dont think you need to add anything special for a normal flow

http://help.sap.com/saphelp_nwpi71/helpdata/EN/56/02e63f48e58f15e10000000a155106/content.htm

Just confirm whether the Receiver Business Service, IN Async MI, Receiver File CC are existing and are in actiavted state.

[Former Member]

All the objects you mentioned are in active state. Do any Identifiers need to be specified in receiver channel ?

[Former Member]

this is a receiverdetermination error,

It occurs when packaging is active, to resolve either deactivate packaging or implement Note- 1163661.

Edited by: NetWeaver Expert on Jul 18, 2009 7:01 AM

[Former Member]

I checked in the transaction SXMB_ADM, There is no "PACKAGING" Parameter defined. Moreover The other scenario where I get the PO's from test system works perfectly fine. Anyother thing that needs to be checked ?

[former_member200962]

Check this blog (pt-6):

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

From the above blog:
Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not 
active, activate the objects.

Also check the if the receiver determination and interface determination objects are referenced to the same namespace or not. 
Sender and receiver interface objects should always refer to the same Namespace.

Regards,

Abhishek.

[Former Member]

All the objects are activated, plus I re-created fresh objects this time. The namespace is also same in ID and RD.

This should be working as the originat scenario still works well. The only change I have made is added the identifiers in the new party that I created for normalization purpose, since without this it would not even go through the message branching step. after this change the message reached till technical routing and errors out.

[Former Member]

try creating the receiver determination with virtual receiver check box enabled and re run the scenario as you are using the service with party.

Rajesh

[Former Member]

Yes, the receiver determination is created with the virtual receiver check box checked.