OUTBINDING.CO_TXT_OUTBINDING_NOT_FOUND

[Former Member]

Getting no receiver agreement found for sender in the inbound message payload?

Anybody know what this issue is?

[Former Member]

Tom,

Can you check all your configurations in Integration Directory Tools Menu --> Test Configuration. Give all the vaules and give some sample payload from message mapping and check.

...Satish

[Former Member]

Here is what is in the payload:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Technical Routing

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>

<SAP:P1>-Wawa_FileSystem_QAS</SAP:P1>

<SAP:P2>-QA5_300,urn:sap-com:document:sap:idoc:messages.INVOIC.INVOIC02</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>No receiver agreement found for sender -Wawa_FileSystem_QAS to receiver -QA5_300,urn:sap-com:document:sap:idoc:messages.INVOIC.INVOIC02</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

[Former Member]

Looks like to me an IDoc posting issue.

Check your control record(sender port, partner..), also, you may disable the control record in the mapping and let XI post the message itself.

--Wenning

[stefan_grube]

Check if a receiver agreement with this key combination:

Sender Service: Wawa_FileSystem_QAS

Receiver Service: QA5_300

Namespace: urn:sap-com:document:sap:idoc:messages

Interface: INVOIC.INVOIC02

is available in your system. If it is, check in SXI_CACHE if it here also.

Regards

Stefan

[Former Member]

It was a bad receiver agreement....Thank-You All.

[Former Member]

also you must check service filtering at receiver determination.

bye