Skip to Content

Receiver service not found in IDoc LS (Bussiness-Service) to Party type KU

Hi,

I have the following setup:

- R/3 -> XI -> R/3

- IDoc comunication with simple mappings

- Sender is a locial system without party - configured as Business-System

- Receiver is a party

The receiver identification is configured, in monitoring I can see the XI party.

the problem is, that no Service is found for this party.

Some inforamtions from monitoring:

ERROR Log:

...

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>-SENDER_SERVICE</SAP:P1>

<SAP:P2>RECEIVER_PARTY-,urn:sap-com:document:sap:idoc:messages.IDOC_TYP</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Es konnte keine Empfängervereinbarung für den Sender -SENDER_SERVICE zum Empfänger RECEVIER_SERVICE-,urn:sap-com:document:sap:idoc:messages.IDOC_TYP gefunden werden</SAP:Stack>

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

...

MAIN Info:

...

<SAP:Sender>

<SAP:Service>SENDER_SERVICE</SAP:Service>

<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">IDOC_TYP</SAP:Interface>

</SAP:Sender>

<SAP:Receiver>

http://sap.com/xi/XI" scheme="XIParty">RECEIVER_PARTY

<SAP:Service />

<SAP:Interface namespace="" />

</SAP:Receiver>

<SAP:Interface namespace="urn:sap-com:document:sap:idoc:messages">IDOC_TYP</SAP:Interface>

</SAP:Main>

...

IMO the problem is the missing Service on receiver site.

Any idea?

Regards

J.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on May 20, 2008 at 11:49 AM

    Error Category - CO_TXT_OUTBINDING_NOT_FOUND

    The problem is in Technical routing.

    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.

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

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      I created a party with name party1 (for receiving). In the identification for this party I set:

      Agency: BS of sender

      schema: ALE#KU#WE

      Name:123456789

      In the monitoring I can see the XI party but no Service. I assigned the Receiving System to the the party party1.

      In the RD and the ID, I have a set on sender site only the service and on receiver site party + service

      Regards

      J.

  • author's profile photo Former Member
    Former Member
    Posted on May 20, 2008 at 11:55 AM

    Hi,

    Check in this For IDOC related Errors

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

    REgards

    Seshagiri

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.