IDoc-Tunneling -- No Receiver Agreement

Hi, i am trying to do the IDoc-Tunneling scenario from Michal.
Well everything looks fine so far except that i get following error:
+<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>-Q01CLNT010</SAP:P1>
  <SAP:P2>0000010007-,urn:sap-com:document:sap:idoc:messages.DELFOR.DELFOR01</SAP:P2>
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>Es konnte keine Empfängervereinbarung für den Sender -Q01CLNT010 zum Empfänger 0000010007-,urn:sap-com:document:sap:idoc:messages.DELFOR.DELFOR01 gefunden werden</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>+
Well i have Receiver Agreement that looks like:
Sender Service: Q01CLNT010
Receiver Service: EDI
Interface: DELFOR.DELFOR02
Namespace: urn:sap-com:document:sap:idoc:messages
CC: IDOC_RECEIVER_EDI
In this Receiver-CC i also activated
- Apply Control Record Values
- Take sender from payload
However, i have no clue what is wrong.
Can somebody help? br Jens

Hi Jens
(6) 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.
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.
Please refer the follwoing blog for details
<b>/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Thanks
AbhishekMahajan
*****Please reward points if helpful*********

Similar Messages

  • SAP PI Party setup IDoc - HTTP: no receiver agreement found

    Hi,
    We have setup SAP IDoc -> SAP PI --> HTTP with 2 parties, as described in the the 'HOW..TO Sample IDoc - XI scenario's' case 7:
    For the clarity of the example, the sender at our side is 'AAA', and the receiver side is 'BBB'.
    1. Sender Party
    Agency -
    Scheme -
    Name
    http://sap/com/xi/XI -
    XIParty -
    PA_AAA
    BS_BBB    -
    ALE#LI -
    0000100581
    2. Receiver Party
    Agency -
    Scheme -
    Name
    http://sap/com/xi/XI -
    XIParty -
    PA_BBB
    AD2_200 (SAP system) -
    ALE#KU -
    DE217560
    The other components in XI are as follows:
    3. Business component: PA_BBB | BS_BBB (party and Business System)
    4. Receiver determination: sender AD2_200, receiver party: PA_BBB, receiver component: BS_BBB
    5. Receiver agreement: sender AD2_200, receiver party: PA_BBB, receiver component: BS_BBB
        Header mapping: sender comm party: PA_AAA, receiver comm party: PA_BBB
    6. Communication channel (HTTP):  CC_HTTP_RCV_BBB
        Identifiers: sender agency: BS_BBB ALE#LI, receiver agency: BS_BBB ALE#KU
    When we send an IDoc with SNDPRN=AD2_200, RCVPRN=DE217560, RCVPRT=KU, SAPXI doesn't seem to find receiver determination, iinterface determination and receiver agreement
    <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Start with given receiver PA_BBB -</Trace>
      <Trace level="2" type="T">Using Receiver Determination 00000000000000000000000000000000</Trace>
      <Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>
      <SAP:AdditionalText>No receiver agreement found for , AD2_200, PA_BBB, , urn:sap-  com:document:sap:idoc:messages,
    Can someone explain why these parties have to be indicated in all these different places (the party descriptions, the receiver agreement, the communication channel), and why the receive determination with receiver party PA_BBB is not found, although it is created and refreshed in the cache ?
    Regards,
    Jan Macken

    I am also facing same issue when using 2 parties. Could you please let me know if you got solution for this?

  • No Receiver Agreement found - IDOC RCVPRN = Party

    Hello,
    I have created all the receiver agreements required and they are in the configuration scenario. 
    I have a receiver determination that is using the IDOC vendor number (RCVPRN) to determine the party for delivering purchase orders and another RD with the same config for delivering po changes. 
    In tests my POs are sending successfully and my PO Changes are failing even though they use the same party setup/config.  In SXMB_MONI I can see that the receiver determination for the POs are creating the correct party:
    PO Results:
    <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Ventura</SAP:Party>
    But the PO Changes seem unable to connect the vendor number to the party:
    PO Change Results:
    <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">0000557129</SAP:Party>
    In the sample above the party Ventura is set up under the party identifiers as follows:
    Agency:
    http://sap.com/xi/XI
    http://stc.com/pi/SAPR3
    Scheme:
    XIParty
    Vendor
    Name:
    Ventura
    0000557129
    How is it that PI 7.10 is getting the same value in RCVPRN and assigning the Party correctly in one case and incorrectly in another?
    Any ideas?
    Thanks,
    Matt

    Sometimes you just need to walk a way for a day or two...  I rechecked the standard configurations over and over.  But I didn't review the Party Extended selection.  In the Receiver Determination I chose to use RCVPRN to identify the Party but upon further investigation I realized I was using the wrong scheme and agency on the Party extension.
    So my party had the following:
    Agency:
    http://sap.com/xi/XI
    http://stc.com/pi/SAPR3
    Scheme:
    XIParty
    Vendor
    Name:
    Ventura
    0000557129
    My Receiver Determination was not using http://stc.com/pi/SAPR3 Vendor 0000557129 to determine the Party it was attempting to use http://sap.com/xi/SI XIParty Ventura.  So it was unable to find a matchinig party using the Vendor Numbers.
    Thanks for all the help.
    Matt

  • IDOC to FTP File - Error : SAP:Stack No receiver agreement found for send

    Hello Friends,
    I need to configure a senario Idoc to FTP File, Í did required settings in R3 and in PI... , did mapping and configuratino in PI... and when I send my idoc I got error msg in monitor
    <SAP:Stack>No receiver agreement found for sender ,BMG_ASN_File_Component to receiver ,GTN_224,http://adis-bmg.de/asn,SI_BMG_ASN</SAP:Stack>
    I search the fourm but did not got my answer, me just a bit confused...
    In my senario I have having followings:
    1. Bussiness System ( RFT : sender R3 system).  ( I have define a party and make a connection under Idoc Partner )
    2. Bussiness Component ( ZTEST_COMP as on Reciever side is File Server, so I define the reciver as bussiness component )
    3. Communicatin Channel
        File with protocol FTP having communicatin component as my Bussiness Component ( reciver ). there I defied the required info for FTP
    4. Reciever Determination
        Sender:
        - RFT
        - Idoc-Interface
        - urn:sap-com:document:sap:idoc:messages
       Reciever
        communication party  = space
        communicatin component = ZTEST_COMP
        Configure Reciever:
       There I again define the communication component as  ( ZTEST_COMP)
    5. Interface Determination
        -RFT
        - Idoc-Interface
        - urn:sap-com:document:sap:idoc:messages
       Reviever:
        ZTEST_COMP
    and define the mapping which I did in design ( although I have seen some threads where mentioned we dont need maaping in this case ) ?
    6. Reciver agrement
    sender:
    - RFT
    Reviver:
    - ZTEST_COMP
    - SI interface ( SI_BMG_ASN )
    - http://test-etc.de/asn
    and included my CC for file .....
    Now when I send Idoc I got error msg that Reciver is not found : am I dong something wrong ?  do I have to defien a bussiness system instead of Bussiness Component ?
    Pls suggest...

    ( I have define a party and make a connection under Idoc Partner
    Do you really need a party in your communication? Should it not be a partly-less communication.
    In the receiver agreement ensure that you have included the inbound message interface.
    communication party = space
    No need to give any space.
    In the Interface Determination i hope that you have included the receiver meessage interface and then the corresponding Interface Mapping.
    If still not works then make some dummy changes and again activate....correspondingly check the cache status of the ID-objects
    Regards,
    Abhishek.

  • Getting Receiver Agreement issue in IDOC to File scenario

    Hi Gurus,
                Need your help. I'm working on a IDOC to File scenario. I'm using CREMDM.CREMDM04 as outbound Interface & small structure VEND_FILE_IN_MI as Inbound Interface. Though I've configured the receiver Communication Channel as a File Adapter with proper Inbound Interface I'm seeing the message getting failed which is showing CREMDM.CREMDM04 as both Outbound & Inbound interface and pointing a Receiver Agreement issue . The Receiver service is coming Properly, only the Interface is coming wrong as the sender interface. I've checked both Receiver Agreement & Receiver determination and found the Receiver Service, Communication Channel & Interface are perfectly mapped there, I cross checked the same Configurations in IE via SXI_CACHE after full Cache copy.
    Error Message:
    No receiver agreement found for sender -SAPERP to receiver -IDOC2FileReceiver,urn:sap-com:document:sap:idoc:messages
    Error  Category : Outbounding
    Error ID : CO_TXT_OUTBINDING_NOT_FOUND
    My IR design:
    Sender:
          Interface : VEND_IDOC_OUT_MI
          Message Type : CREMDM.CREMDM04
    Receiver:
          Interface : VEND_FILE_IN_MI
         Message Type : VEND_IN_MT , Data Type VEND_FILE_DT
    My ID Config:
    1. Sender / Outbound  Message:  Service Type --> Business System
                                                  Service  ---> SAPERP
                                                 Interface--> VEND_IDOC_OUT_MI
                                                 Adapter Type : IDOC
    2. Receiver / Inbound Message: Service Type --> Business Service
                                               Service       --> IDOC2FileReceiver
                                               Interface    ---> VEND_FILE_IN_MI
                                               Adapter Type--> File
    3. In Sender Agreement : Specified the Sender Communication Channel
                                         VEND_IDOC_OUT_Channel
    4. In Receiver Agreement Configured the receiver service IDOC2FileReceiver aging sender service SAPERP & Interface VEND_IDOC_OUT_MI.
    5. In Interface Determination Specified the Inbound Interface VEND_FILE_IN_MI and Interface Mapping VEND_IDOC_FILE_IMAP
    6. In Receiver Agreement specified the receiver communication Channel IDOC2FileChannel against Receiver Service & Interface.
    I used the Configuration wizard in my second attempt to make sure the sequence of configuration.
    Can anyone help me identifying what's going wrong. I'm very new to XI and basically this  is the first assignment I'm working on.
      Regards,
    Subhadip

    Hi Babu,
               In the Inbound data type all the fields have MinOccurance = 0 and MaxOccurances unbounded.
    Please find the XSD:
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://adc.com/poc/sample" targetNamespace="http://adc.com/poc/sample">
         <xsd:complexType name="VEND_FILE_DT">
              <xsd:annotation>
                   <xsd:appinfo source="http://sap.com/xi/TextID">
                   8f584d80456311dccd680018fe79f69b
                   </xsd:appinfo>
              </xsd:annotation>
              <xsd:sequence>
                   <xsd:element name="VENDCODE" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb0390c11dc843000188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor Code
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="VENDNAME1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb4390c11dc84e800188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor name4
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="ORT01" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb5390c11dcbe3400188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor City
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="PFACH" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             a8653cb6390c11dc896100188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor PO Box
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="STRAS" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4811db0335fd11dc9e9600188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor House No &amp; Street
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="PSTLZ" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4811db0435fd11dc98b000188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor Postal Code
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="LAND1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             4811db0535fd11dc870500188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Vendor Country
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="STCD1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             7ca8d600403b11dcc9bd00188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Tax Number 1
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="TELF1" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7040e611dcce4300188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Telephone number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="STCEG" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7140e611dc8f3900188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             VAT Registration Number
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="LIFNR" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7240e611dccef700188bd09370
                             </xsd:appinfo>
                             <xsd:documentation xml:lang="EN">
                             Account Number of Vendor or Creditor
                             </xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
                   <xsd:element name="ALTKN" minOccurs="0" maxOccurs="unbounded">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             9abaee7340e611dcb3bc00188bd09370
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:simpleType>
                             <xsd:restriction base="xsd:string">
                                  <xsd:minLength value="0" />
                                  <xsd:maxLength value="50" />
                             </xsd:restriction>
                        </xsd:simpleType>
                   </xsd:element>
              </xsd:sequence>
         </xsd:complexType>
    </xsd:schema>

  • IDoc adapter - Receiver Agreement

    For IDoc Adapter, y should the receiver agreement should be created.
    I know y sender agreement is not created.
    -Naveen.

    Hi Naveen,
    The Integration Server pipeline converts the received XML to IDoc XML, and then transfers this IDoc XML to the IDoc adapter. The IDoc adapter converts the IDoc XML to native IDoc format and sends the IDoc to the identified receiver system using the standard IDoc interface, this receiver system is identified because you specify it in your <b>receiver agreement</b>. The IDoc adapter can also call external subsystems.
    I hope you have understood the need of receiver agreement incase of  IDoc adapters...
    Regards,
    Abhy

  • Missing receiver agreement for incoming IDoc

    Hi guys,
    I transfer IDoc's from a SAP-system to XI to start a ccBPM-process
    For that I don't need a receiver agreement.
    But why I get always the error message "<b>No receiver agreement found for sender -<SAP-SYSTEM> to receiver -<integration process>"</b> ?
    For other IDoc which coming from the same system but starting another process everything is working fine!!!
    I don't understand that.
    Could somebody help me please? Thanks very much in advance.
    Regards, Thomas

    Hi,
    please can you check in transaction SXI_CACHE if the return code for the IP is 0.
    Also, for the Interface that are working is it the same scenario SAP to IP with IDocs on the Outbound?
    Regards
    Vijaya

  • Receiver agreement - IDOC

    hi all.
    i have a simple question.
    Why i must define a sender service at header mapping in receiver agreement??
    if the sender service is not defined, i get the error, cannnot conver sender service to an ALE logical system.
    Rgds
    RP

    You don't need to define your system META4 as an ABAP System.
    You can create it as a Business System (3rd Party) in your SLD or as a Business Service in your ID depending you need.
    What adpaters are you using ?
    If you use IDOC for R/3 you can choose from where the sender is taken :
    http://help.sap.com/saphelp_nw70/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm
    Regards,
    Chris

  • Problem when creating receiver agreement for File to IDOC scenario

    I have done the following :
    1. Created two business systems one for the file system and other for the R3 system and also I created two communication channel, one as sender communication channel and one as receiver communication channel.
    2. Created the receiver determination
    3. Created the interface determination
    4. Created the sender agrement
    5. Now when I was trying to create the receiver agreement I want to assign the receiver communication channel i have created to the receiver agreement but the F4 help gives me no records and I am thus stuck at this point.
    Please suggest me how to proceed forward from here.

    Hi ,
    <i>5. Now when I was trying to create the receiver agreement I want to assign the receiver communication channel i have created to the receiver agreement but the F4 help gives me no records and I am thus stuck at this point.</i>
    Make sure that your created communication channel for reciever is under the respective reciever business system and give the same while creating the reciver agrement.
    sekhar

  • No Receiver agreement found for Sender

    Hello,
    I have a scenario like this : sending an IDoc from R/3 4.6c to R/3 4.7 through XI 3.0.
    I am struck up with the follwoing Error in SXMB_MONI
    "outbound binding exception: No outbound binding found for , R46, , ENT, urn:sap-com:document:sap:idoc:messages, ORDERS.ORDERS04"
    The Complete TRACE is as follows:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Technical Routing
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="IDX_INBOUND_XMB" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
      <Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
      <Trace level="1" type="T">Syntax-Check-Flag X</Trace>
      <Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace>
      <Trace level="1" type="T">Queueid</Trace>
    - <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
      <Trace level="1" type="T">Get the Metadata for port SAPR46</Trace>
      <Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
      <Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
      </Trace>
      <Trace level="1" type="T">Set Receiver Routing-object</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" />
      <Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
    - <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA">
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" />
      </Trace>
      <Trace level="1" type="T">COMMIT is expected by application !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = XI3</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = SMART01</Trace>
      <Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = F0EAB201EEA5F74A814EF22C32394FD0</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0009</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0009</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = XI3</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = SMART01</Trace>
      <Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTO____0000</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = XI3</Trace>
      <Trace level="1" type="T">client = 800</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = SMART01</Trace>
      <Trace level="1" type="Timestamp">2004-12-27T20:08:46Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="1" type="T">No mapping required</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
      <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="1" type="T">processing the outbound binding</Trace>
      <Trace level="1" type="T">search outbound bindings</Trace>
      <Trace level="1" type="T">outbound binding exception: No outbound binding found for , R46, , ENT, urn:sap-com:document:sap:idoc:messages, ORDERS.ORDERS04</Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
    I have made neccesary Configurations for the Receiver agreement in the Configuration Directory...
    Anybody could please help me out...
    Regards,
    Romit Arun Shankar

    Hi Frank,
    Many Thanks for your reply.The problem got sorted out and the IDoc(ORDERS04) which i send in SAP 4.6c gets into SAP 4.7 AS ORDERS04 but i have a new problem now....
    I didnt use any mappings until now...but now i have to have the segment E1EDK14 filled up for Sales organisation, Distribution Channel, Division details as well as the material number. These segments will not be filled up when a PO is sent from the source system.These segments has to be filled only in the XI system...Is it ? or is there any other solution for it....
    Now how we can have this segment E1EDK14 which can occur any number of times with constant values for SORG,DV,DC in the mapping process....
    Waiting for ur replies....
    Bye,
    Romit Shankar Arun.
    For this

  • No receiver agreement found.

    Hi Experts,
    I am doing one scenario i.e idoc to file .
    I am getting an error that is "no receiver agreement found" in sxmb_moni, but i did the test configuration in ID which is working fine.
    can any one help on this.

    Hi,
    Check the following.
    1. Any cache problems in the ABAP stack and java stack.
    2. Check your receiver whether it is case sensistive.
    3. Check the receiver determination pipeline step in soap header whether the sap receiver anything filled in or blank. If blank, definitely there is an error in your config.
    Since you have tested it in ID, I would assume it would be cache problem.
    Regards
    Krish

  • Error in AEX Itegrated Configuration Testing "No receiver agreement found."

    Hi,
              I am working on PI 7.3, doing a File to Idoc by using the AEX(Advance Adapter Engine Extended). While doing the configuration testing i am getting the below error "
    Problem occurred in receiver agreement for sender -BC_XXXXXXX to receiver -BS_XX5_100,urn:XXXX.com:POC:MasterData:Article:ECC:Sender.SI_OA_POC: No receiver agreement found for , BC_xxxxx, , BS_xx5_100, urn:xxxx.com:POC:MasterData:Article:ECC:Sender, SI_OA_POC."
            I gone through the SDN but not got usefull links. I tryied to recreating whole scenario, Cache refresh, but no luck. Can you pls let me know where is the problem. Do i need to do any additional configuration other than creating RFC in Java stack for AEX?
    Thanks & Regards,
    Dev

    Hi RK,
            Thanks for your reply.
                  Yes i have created the Idoc_AAE channel and assigned this channel in my Outbound Processing tab.
    What do you mean by java channel in Inbound Processing? My sender is File so i created File channel and assigned in the Inbound processing tab.
    @ Raghu,
                I have created the Receiver channel. I no need to create Receiver agreement because i am using the ICO so if i give the Receiver and Inbound interface details that is enough. And one more thing i am doing testing in ID Test confiuration.
    Thanks ,
    Dev

  • Sender and receiver agreement not cerated

    Hi .
    I am creating configuration scenario in ID by importing the integration scenario which i created in the IR.
    I crated communication channel template also and i added it to the integration scenario in connections.
    Query 1?
    do i have to create Communication channels also.....even After creating communication channel template (because it is not seen the ID below communication channel )
    Query 2 ?
    once i transfer this integration scenario from IR to ID and cerate the configuration scenario (sender and receiver agreements are not getting created automatically)peace tell me what is the reason???.
    and how can i resolve this...
    thanks
    shakif

    Hi Mohamed,
    <b>Query 1?</b>
    <i>do i have to create Communication channels also.....even After creating communication channel template</i>
    Yes You have to create as it's just a template that u created in IR. But u can use the same for creating CC.
    Check this link for what's the Diff. B/w CCT in IR and CC in ID
    Re: Communication Channels
    <b>Query 2 ?</b>
    <i>once i transfer this integration scenario from IR to ID and cerate the configuration scenario</i>
    Yes. it will create automatically.
    Just check my posting in Wiki for simple File to IDOC scenario might be u missing something
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
    and check my reply in this thread
    Re: Doubt in transfering integration scenario from IR
    Regards
    Sachin

  • PI 7.3 receiver AAE idoc scenario-No receiver comm channel found in ICO

    Hi,
    I am working in PI 7.3 receiver AAE idoc scenario.When I try to configure Integrated Configuration(ICO),I am not able to see the receiver comm channel in receiver agreement.
    What is the reason for this??I have configured the communication channel,but still its not shown in reciver agreement dropdown.
    Please help.
    Regards,
    Sriparna

    Hi Sriparna,
    In PI 7.3 there is are two separate IDoc adapters: "standard" IDoc adapter and one that is dedicated for AAE (ICO). Make sure that you have used the right one - most probably not, which is why you cannot see the channel in the dropdown list.
    Hope this helps,
    Grzegorz

  • Receiver Agreement problem in XI

    Hi,
    The problem is that when the idoc calls adapter in XI, the following error message is thrown(Display XML Message Versions- window, SOAP Header):
    com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=our_sender;TS=our_receiver;AN=WorkCenterMasterData;ANS=our_namespace
         I have checked that the Receiver Agreements are configured right, there should not be problem with that. So what could be the problem? We just updated our XI to SP19, could this affect to idoc processing?

    Hi,
    I have got a couple of times that Receiver agreement not found even though I have receiver agreement. Also I have done some dummy changes and tried out. Also I have stopped and started the receiver communication channel. But it have not worked. Then I have started and stopped the File Adapter but that doesnot worked. I have done all the cache refreshes but the issue is not resolved.
    Then finally just restarted the machine and it worked fine. So there are some caches which is not refreshing when we do the cache refreshes. They are only refereshing when we reboot. Can you also try all these steps and if you dont get success then try to bounce the system and check.
    ---Satish

Maybe you are looking for

  • ERROR:MapLib:973 - Tri-state buffers are not supported in this architecture.

    Hi, I face a ERROR:MapLib:973 problem with inout port in a pcore component. I need ton instantiate an inout port at the top level to communicate wih my peripherical. This inout port is driven by an XPS IP core (pcore). The .mpd is  : PORT fdata = "",

  • Material Type in Material & Chapter ID combination_J1ID

    Dear Guru's, While entering the material & Chapter ID combination in J1ID, we have a tab material type with options as, Raw materials, Assets, Tools,Consumables, Noncenvatable & RG1. For ERSA(Stores & Spares) mat type, what i need to select here ? Pl

  • Acquiring data from EMG (data socket?)

    Hi! I have to use the Porti TMSi to acquire an EMG signal, that I want to use to control a vibration motor with vibration frequency proportional to the muscular activation. My problem is that I don't know how to make the TMSi communicate with Labview

  • I can't change my location in my app ID.

    I've tried to buy an app in appstore but it said I need to change the location to my present location. It said i need to change my location in order to buy app in Thai store. I (My id was in Japan but now i'm in Thailand) I changed my location and up

  • Apple TV IP Address-- without remote

    Is there a way to find my Apple TV IP address without having an apple remote?