Error "No Receiver Found"

hi,
I have designed a simple scenario wherein a file is picked up from SAP directory and transfered to an FTP server. Used weblog # 4383 to design the scenario. Now when i execute, getting the message "No receiver found; message stopped but has no errors".
Have checked the reciever determination, i can see it says for receiver agreement "does not exist". Is this the problem or something else i need to check?

Hi Preet,
Check your configuration part, have you created the receiver aggreeement in the configuration and assigned the receiver communication channel to receiver aggreement.
If receiver aggrement is not created then create it and assign the Receiver comm channel to it.
Check I think that is the problem.
Thnx
Chirag
Edited by: chirag Gohil on Jan 5, 2008 2:48 PM

Similar Messages

  • No receiver found for sender

    Hello,
    Scenario:
    Idoc from R/3 to XI and external partner LI.
    The idoc has to be converted to xml and sent by email (Email is a Business Service in XI).
    Question:
    I got an error "no receiver found for sender" when sending the idoc to XI. In the soapheader of the message I see that the service of the receiver stays empty. How can I fill the service of the receiver in the soap header?
    Thanks for your reactions,
    Erik van Lisdonk

    You have to define a Receiver Determination for the Sender & Interface (sending SAP Business System plus IDoc interface) and specify the Receiver there. Furthermore, you will need an Interface Determination to determine the interface of the outgoing email and the mapping that is required to transform the IDoc to this interface.
    Finally you will require a Receiver Agreement for the Service 'Email' that specifies the receiving communication Channel (in your case an Email Channel).
    This is all well described in the SAP online help. As a starting point, you can have a look <a href="http://help.sap.com/saphelp_nw04/helpdata/en/19/8dba88b1db634f891622e909565f7a/frameset.htm">here.</a>
    regards,
    Peter

  • Error in BPM: "no interface action for sender or receiver found"

    hello,
    i configured a interface scenario SOAP - PI - Idoc using a BPM sync/async bridge.
    i followed the document
    when i try to call interface with my soap client i have the follow error in SXMB_MONI:
    Timeout condition of pipeline reached
    if i check the detail in trace i can found the follow message:
    <Trace level="1" type="T">select interface SI_MATREQ_ABS</Trace>
    <Trace level="1" type="T">select interface namespace http://pmf/orders</Trace>
    <Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
    <Trace level="1" type="T">Hence set action to DEL</Trace>
    in BPM monitor i cannot see any interesting logs for determine the problem.
    I clear cache many time and reimported Integration Process more time.
    Have u some suggestion?
    thanks in advance

    Hi,
      Check whether this thread help you or not....
    SXMB_MONI: no interface action for sender or receiver found
    Regds,
    Pinangshuk.

  • BPM Error: no interface action for sender or receiver found

    Dear All
    I am doing an HTTP to Proxy scenario using BPM Synch Asynch bridge. The error in HTTP is error 500 (Internal Serve Error)
    I am getting following error in moni
    <Trace level="1" type="T">select interface namespace urn:WorkDelivery</Trace>
      <Trace level="1" type="T">--start determination of receiver interface action</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface LocationSynch_Abs</Trace>
      <Trace level="1" type="T">select interface namespace urn:WorkDelivery</Trace>
      <Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      </SAP:Trace>
    I have seen some posts on sdn regarding the same problem but couldn't get any solution out of it.
    Please let me know how can this problem be solved.
    Sourabh

    I am using Two Synchronous interfaces:
    Synh_Out: Used before BPM
    Sync_Abs inside Synch/Asynch bridge:
    I am using an switch step to check a condition then in both the branches I have a send step and a transformation step:
    Send step1 is using one Asynch Abstract Interface
    Send step2 is using Another Asynch Abstract Interface. These Interfaces have different message types.
    The Transformation step in both the branchs have same operation mapping.
    The laststep after switch step is closing A/S bridge.
    There are two RDs after after BPM. They are having the same Interfaces as there in the respective send steps.
    I can see the xml version of my BPM
    Edited by: Sourabh Nirmal on Mar 30, 2010 8:56 AM

  • Receiver JMS ( websphere MQ ) error  - No transition found from state:ERROR

    Hi all
    we are using JMS adapter to connect to the Queue manager . whenever the queue manager restarts , the messages is not getting thru and it is struck in the adapter engine with status " not to be delivered "
    i am getting error in receiver communication channel audit log....its showing
    *MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_XXXXXXXXX:15fa03eb9fd837849906f512610314c4*
    note : already i have gone thur many forum  and nothing helps.
    Thanks in advance
    Faheem

    If you are using the FCC then this could be because of that. What is the connection status with MQ? Are there any connection errors with MQ.
    If you are using FCC in your Receiver JMS channel then just to confirm, first remove the FCC configuration and try to send a xml file. If the xml file goes in successfully then the problem is in your FCC configuration.

  • RMAN receives: OSB error: UUID not found OB cached object manager

    I am receiving an error when backing up :
    Starting backup at 17-MAR-2009 10:00:00
    allocated channel: ORA_SBT_TAPE_1
    channel ORA_SBT_TAPE_1: sid=137 devtype=SBT_TAPE
    channel ORA_SBT_TAPE_1: Oracle Secure Backup
    channel ORA_SBT_TAPE_1: starting full datafile backupset
    channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=+DGROUP1/seattle/datafile/system.826.679693097
    channel ORA_SBT_TAPE_1: starting piece 1 at 17-MAR-2009 10:00:02
    RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 03/17/2009 10:02:57
    ORA-27191: sbtinfo2 returned error
    Additional information: 2
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_cat_query: Query for piece 07ka4pt2_1_1 failed.
    *(Oracle Secure Backup error: 'UUID not found (OB cached object manager)').*
    Prior to this (when everything was working) I merely tried to re-label a tape. Why this has caused the problem I do not know but I can't seem to fix it.
    Does anybody know what has happened and what the fix is?
    On the HTTP administration page, when I try to configure the device I get the following error message:
    Error:      cannot read location object associated with device - UUID not found
    It looks as though the device definition has been corrupted some how.

    The fix has been found (from Oracle Support). The cause is not yet understood.
    I document it here for others who may run into the same problem.
    It seems that the device "went missing". The fix was to add it.
    ob> mkloc dat72
    It is still being investigated and I will update the notes when I am in possession of more information.

  • Error: no interface action for sender or receiver found

    Hello,
    I have configured a asynchronous RFC to JDBC scenario.
    When i try to execute the end to end scenario , the message in SXMB_MONI is with a green flag(scheduled)  and queue status is yellow and when i double the message , the trace shows following message:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="1" type="T">Work Process ID: 25711</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</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 = HXD</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2010-05-24T12:23:09Z 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 = 3CA00D0C20460CD10B3CA18E3C804118</Trace>
      <Trace level="1" type="T">PLNAME = RECEIVER</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 = RECEIVER</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_RECEIVER</Trace>
      <Trace level="1" type="T">Queue name : XBTR0004</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTR0004</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="T">--start determination of sender interface action</Trace>
      <Trace level="1" type="T">select interface</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">--start determination of receiver interface action</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface Z_SD_HP_SALESORG</Trace>
      <Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:rfc:functions</Trace>
      <Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      </SAP:Trace>
    The pipeline steps on the left hand side in sxmb_moni shows only inbound Message i.e remaining steps are not executed.
    When i try the execute message by directly sending message from Runtime Workbench , the scenario is executed successfully.
    Please help.
    Thanks & Regards,
    Loveena

    Hello,
    The problem was with the Client. Our Xi is running on Client 200 wheras at runtime it was picking up the default client 001.
    So after changing the default Client 001 to 200.
    The scenario was working fine.
    But from the third time onwards again it is taking the default Client and I am facing the issue.
    I guess it is some Cache problem. Can anybody tell me how to refresh the cache.
    Thanks ,
    Loveena

  • Error in Receiver Communication Channel in FCC

    I have a simple scenario of Proxy to File. I have to just one field in complete row. So my structure is as below : MT_RecordIB -> Records.  So my XSD looks like this :
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://XXXl.com/INF31018/SAPSerOrd_DaysIn" targetNamespace="http://hnwl.com/INF31018/SAPSerOrd_DaysIn">
       <xsd:element name="MT_RecordIB" type="DT_RecordIB" />
       <xsd:complexType name="DT_RecordIB">
          <xsd:sequence>
             <xsd:element name="Records" type="xsd:string" />
          </xsd:sequence>
       </xsd:complexType>
    </xsd:schema>
    I have used FCC and the parameters are :
    Recordset Structure                                  Records
    Records.fieldSeparator             'nl'
    But I am getting following error in Receiver Communication Channel :
    Failed to process message content. Reason: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns0:MT_RecordIB' found in document', probably configuration error in file adapter (XML parser error)' (Software version: 3.0.21)
    Thanks,
    Pankaj Singh

    Hey Pankaj,
    Your content conversion parameter might be configured improperly.
    Refer this blogs
    /people/shabarish.vijayakumar/blog/2007/08/03/file-adapter-receiver--are-we-really-sure-about-the-concepts
    /people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
    Refer the following threads for your problem
    [ Unknown structure 'ns0:MT_dbglgtr_FileName' found in document'|Unknown structure 'ns0:MT_dbglgtr_FileName' found in document']
    Rgds
    Ramesh

  • Error File not Found in CS 5.5

    When I go to open up PP CS 5.5 it provides a list of possible projects I can open up. Click on a project and it opens accordingly. However, over the past 2 days it has become problematic. I can click on the listed project but I now receive an error message: Error file not found. PP will not open up. I haven't moved any files, folders or projects around. I have simply closed the project, quit PP and then opened it again when wanting to edit. I have tried opening up the auto saved project file and I receive the same message?

    Hi Todd both your solutions (and the one suggested by Colin) works initially. Dbl click the project file and it opens PPro.  However, I tried this on another project which has a 3rd party pllugin (Smartsound Sonic Fire Pro) in it. Things get interesting with Smartsound being activated with me unable to quit out of it and I am not able to access Premier Pro. I have to Force Quit both programs. Then when I try to dbl click on the program that opened up OK the error message returns: File format not supported. There is no Smartsound file involved in this project? Same thread? New thread? many thanks for your responses

  • Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED

    Hi experts,
    I have a big issue in production server,
    the Queues are stuking in smq2 " command to tRFC/qRFC: execute LUW again"
    if i am reprocess or press F6 it is going manually.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
      <SAP:P1>400</SAP:P1>
      <SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><html><head><title>Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY text="#172972" link="#808080" vlink="#808080" alink="#8e236b" bgcolor=white leftmargin="0" topmargin="0" marginheight="0" marginwidth="0"> <table height="61" width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td background="http://xidist:8000/sap/public/icman/img/bluebar_tile.gif" height="30"><table> <tr> <td width=5></td> <td width=20% nowrap><font face=arial size="-1" color=white>SAP NetWeaver Application Server </font></td><td width=75% align="right" nowrap><font face=arial size="-1" color="white"><a href="http://help.sap.com/">Help </font></td><td width=5% nowrap></font></td> </tr></table> </td><td rowspan=2 width=122 height=61 valign=top><img src= "http://xidist:8000/sap/public/icman/img/theme.jpg" width=122 height=61 border=0 alt="SAP"></td> </tr><tr><td background="http://xidist:8000/sap/public/icman/img/graybar_tile.jpg" height="31">  </td></tr> </table> <br><br> <table width=800> <tr><td width=50 nowrap> </td><td> <H2><b>404 Resource not found</b></H2><br>Partner not reached<br><br><hr> <table border="0"> <tr><td>Error:</td><td>-20</td></tr> <tr><td>Version:</td><td>7000</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Wed May 14 15:50:24 2014 </td></tr> <tr><td>Module:</td><td>icxxconn.c</td></tr> <tr><td>Line:</td><td>2341</td></tr> <tr><td>Server:</td><td>xidist_GXI_00</td></tr> <tr><td>Error Tag:</td><td>{004654a1}</td></tr> <tr><td>Detail:</td><td>Connection request from (110/28816/0) to host: xidist, service: 50000 failed (NIESERV_USED) EX-T110, U28816, 001 PIAFUSER, 10.1.57.50, 15:50:24, M0, W1, , 1/0</td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">&copy; 2001-2009, SAP AG</a></FONT> </td></tr></table> </body></html></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while receiving by HTTP (error code: 400, error text: ICM_HTTP_CONNECTION_FAILED)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Regards,
    Kiran polani

    Dear Sriram Ramani,
    in ths case some scenarios are working good. proxy to soap, idoc to soap and jdbc to proxy, proxy to jdbc all are working with out error.
    but my problem is in Soap to RFC case..
    for all RFC communication channels are working but some time it is throwing RFC_COMMUNICATION_ERROR and messages are stucks in smq2 with retry.
    when i check with retry error with in sxmb_moni log showing ICM_HTTP_CONNECTION_FAILED with error code 400.
    not for all signals for few signals for some time..
    Why it is happening i can't understand.
    in repository it is saying Repsitory object hmi failed and address already in use.
    is there any problem with loading IR objects.
    Please suggest me good suggestion for this type of issue what can do for this to resolve.
    Regards,
    Kiran Polani

  • Consistency error:more fields found in XML structure than specified in conv

    Hi,
    I am doing a File 0 RFC- File in PI 7.1 and facing the following error:
    2009-12-07 09:45:05 Error        MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value '20000000|3022|800.99|10.11.2009|Testing 22222|')', probably configuration error in file adapter (XML parser error)'
    2009-12-07 09:45:05 Error File processing failed with com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'java.lang.Exception: Consistency error: more fields found in XML structure than specified in conversion parameters! (Value '20000000|3022|800.99|10.11.2009|Testing 22222|')', probably configuration error in file adapter (XML parser error)'
    my output file record structure :
    DT_out
        itab_out                       0.........1
           item                          0...... unbounded
             STR                        0........1
    So i have given in the receiver FCC parameters as:
    Record structure : item
    Content conversion parameters:
    item.fieldFixedLengths               255
    item.endSeparator                      'nl'
    could anyone pls help me in solving this error at the earliest.
    thanks

    my problem has been solved by giving the FCC parameters as shown below:
    my output file record structure :
    DT_out
    itab_out 0.........1
    item 0...... unbounded
    STR 0........1
    So i have given in the receiver FCC parameters as:
    Record structure : item,ITAB_OUT
    Content conversion parameters:
    item.fieldFixedLengths 255
    item.endSeparator 'nl'
    ITAB_OUT.fieldFixedLengths 255
    ITAB_OUT.endSeparator 'nl'

  • ** File Content Conversion Error in Receiver CC - How to solve this?

    Hi friends,
    My target structure looks like below.
    EmployeeJobDetails                                        --> Message Type
       JobCode                                                      --> Node
            EmployeeNumber            xsd:string
            Domain                           xsd:string
       JobTrack                                                     --> Node
             Department                    xsd: string
             Position                         xsd: string
    I use the FCC parameters in the receiver CC as below:
    Recordset Structure:    JobCode,JobTrack
    JobCode.fieldSeparator = |
    JobCode.endSeparator = 'nl'
    JobTrack.fieldSeparator = |
    JobTrack.endSepartor = 'nl'.
    Because, we want the output like below
    1099|Raja
    Accts|JuniorAccountant
    1100|Ram
    HR|Recruiter
    like this.
    In this scenario Source is XML and target is txt file.
    I am using XSLT Mapping. The FCC works fine, if my source input file contains some records. But, when we send empty source XML file as below
    <?xml version="1.0" encoding="UTF-8"?>
    <EMPLOYEE_DATA/>
    Mapping works fine. Message is processed successfully in SXMB_MONI. The payload in response also comes with Message Type name like below
    <EmployeeJobDetails    namespace >
    </EmployeeJobDetails>
    While convert this, the system throws below error.
    Error Message:
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)'
    Friend, how to convert this when source XML is empty.
    But, if we remove JobTrack node in target strucutre and remove the JobTrack parameters in CC, then if we send the same empty XML file FCC is working  fine and  we  get the target text file 0 KB. (Amazing !!)
    But, in the first case, how to solve the issue?
    Kind Regards,
    Jegathees P.

    Hi friends,
    If we remove JobTrack node in target strucutre and remove the JobTrack parameters in CC, then if we send the <b>same empty XML file</b> FCC is working fine and<b> we get the target text file 0 KB</b>. (Amazing !!)
    But, if we give parameters like JobCode,JobTrack then send pass the same empty file, we face the problem 'File Content Conversion' Error.
    Searching solution for this problem ...

  • JDBC : error in receiver communication channel?

    Hi Experts ,
    I am doing a JDBC to JDBC scenario. The following error comes in my receiver communication channel monitoring.
    Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'VIN_STG_STORER_RMS' (structure 'Statement'): java.sql.SQLException: FATAL ERROR document format in structure 'Statement': expected 'access' tag(s) not found
    My receiver data type has got the 'access' tag. What other reason can cause this error?
    Receiver table name : VIN_STG_STORER_RMS
    Regards,
    Shamly

    Hi Ranjit,
    My moni shows processed successfully. but the error is in communication channel.
    I have pasted below the target xml structure. Any suggestions?
    Thank you.
    Shamly.
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://mg.adityabirla.com/mg/wms/store_supps" targetNamespace="http://mg.adityabirla.com/mg/wms/store_supps">
    <xsd:element name="MT_WMS_Store_Supps" type="DT_WMS_Store_Supps" />
    <xsd:complexType name="DT_WMS_Store_Supps">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    1f3cf480f98411dcb83a0003ba0adbbd
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:element name="Statement">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    33dd8ee0ef5c11dcb812001d7df81104
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="VIN_STG_STORER_RMS">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    33dd8ee1ef5c11dca724001d7df81104
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="access" minOccurs="0" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    a31a45f0ef5c11dca305001d7df81104
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="STORERKEY" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    a31a45f1ef5c11dcb3c3001d7df81104
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:simpleType>
    <xsd:restriction base="xsd:string">
    <xsd:minLength value="0" />
    <xsd:maxLength value="15" />
    </xsd:restriction>
    </xsd:simpleType>
    </xsd:element>
    <xsd:element name="TYPE" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    a31a45f2ef5c11dcc33e001d7df81104
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:simpleType>
    <xsd:restriction base="xsd:string">
    <xsd:minLength value="0" />
    <xsd:maxLength value="30" />
    </xsd:restriction>
    </xsd:simpleType>
    </xsd:element>
    <xsd:element name="WHSEID" minOccurs="0">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    a31a45f3ef5c11dcabb7001d7df81104
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:simpleType>
    <xsd:restriction base="xsd:string">
    <xsd:minLength value="0" />
    <xsd:maxLength value="30" />
    </xsd:restriction>
    </xsd:simpleType>
    </xsd:element>
    ...and so on for many other fields.
    Edited by: Shamly MM on Mar 24, 2008 10:27 AM

  • XML Monitor: no interface action for sender or receiver found

    Hi,
    I am new to XI and currently working on Supplier Network Collaboration ( SNC) to Integrate PO's from ECC to SCM system via XI. I have successfully triggered PORDCR1 message for which I was able to see the XML message in XI. The message is stuck on the Inbound of SCM system ( seen in SMQ2 with error message "Internal error, calling address update without address ID Message no. SR053).
    When i double click on Inbound queue (SMQ2) in SCM system it takes me to SXI_Monitor
    Below is the log from bottom screen for Trace. Can you please check and see if you could help to resolve the issue?
    Thanks,
    Tejinder
    Below is the Trace bottom screen details
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Inbound Message
    -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"> 
    <Trace level="1" type="T">http content length 7569</Trace> 
    <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" /> 
    - <!-- ************************************
    -->  
    <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace> 
    <Trace level="1" type="T">Process ID: 27633</Trace> 
    <Trace level="1" type="T">Work Process ID: 0</Trace> 
    <Trace level="1" type="T">COMMIT is done by XMB !</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 = AM2</Trace> 
    <Trace level="1" type="T">client = 001</Trace> 
    <Trace level="1" type="T">language = E</Trace> 
    <Trace level="1" type="T">user = ALE_SNC</Trace> 
    <Trace level="1" type="Timestamp">2014-09-10T15:06:15Z CST</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 = 005056B61D0E1ED48E9F7E70255B98CE</Trace> 
    <Trace level="1" type="T">PLNAME = RECEIVER</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 = RECEIVER</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_RECEIVER</Trace> 
    <Trace level="1" type="T">Queue name : XBTR0005</Trace> 
    <Trace level="1" type="T">Generated prefixed queue name = XBTR0005</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="T">--start determination of sender interface action</Trace> 
    <Trace level="1" type="T">select interface</Trace> 
    <Trace level="1" type="T">select interface namespace</Trace> 
    <Trace level="1" type="T">--start determination of receiver interface action</Trace> 
    <Trace level="1" type="T">Loop 0000000001</Trace> 
    <Trace level="1" type="T">select interface ReplenishmentOrderNotification_In</Trace> 
    <Trace level="1" type="T">select interface namespace http://sap.com/xi/SNC/Global</Trace> 
    <Trace level="1" type="T">--no interface action for sender or receiver found</Trace> 
    <Trace level="1" type="T">Hence set action to DEL</Trace> 
    </SAP:Trace>

    Hi Tejinder
    Check this link
    NO INTERFACE ACTION FOR SENDER OR RECEIVER FOUND
    SXMB_MONI: no interface action for sender or receiver found
    Error: no interface action for sender or receiver found
    no interface action for sender or receiver found - SMQ2 SYSFAIL
    Regards
    Osman
    Message was edited by: Osman Jabri

  • Terminating event -- No active receiver found

    Hi -- on an Integration project I just need a workitem that stays active until explicitly closed via an event..
    It's easy enough to create a triggering event which starts a process.
    I've followed all the rules (as far as I can see) to create a terminating event but it doesn't work.
    I've created a test Bus Obj ZZJIMBO which simply has a key of the SAP user ID.
    I've defined 3 events
    STARTSYN  ====> Synchronous
    STARTASY  =====> Asynchronous
    FINISHED ======>  terminating
    Using SAP_WAPI_CREATE_EVENT the STARTSYN and STARTASY  are triggered and the relevant processes start - both for the synchronous and asynchronous tasks.
    However on raising the FINISHED event the system just errors with NO Active receiver found.
    All the binding etc is fine and SWU0 doesn't find any problems.
    Looking at the instance table (transaction SWE3)
    I see that the eventid is the same as the current workitem but the object key is empty
    object key  <empty> 
    eventid    000000250100
    The only possibility I can see is that my Business object doesn't really have "instances" like say a sales order as it only exists at run time.
    Would I have to say trigger the event finished using something like the Work item itself which does have a valid individual instance -- I can extend the WORKITEM bus obj and add an event FINISHED to it instead.
    I can get the workitem id via the container so that shouldn't in theory be a problem to "instantiate"  the Workitem (or ZWORKITEM) business object.
    I really hoped to have all the events in the SAME business object however.
    Any ideas
    Cheers
    jimbo

    Hi James.
    1. Yes, I think the workitem in runtime would expect the triggering event should be from the instance of the object either from
            a. standard workitem relevant obejct instances like _WORKITEM, ATTACHOBJECTS, RULERESULT
           b. or the associated BO in the task i.e WIOBJECT_ID
    2. However as you say >>I really hoped to have all the events in the SAME business object however>>. I can suggest the following
           a. create a parallel fork to the step which is creating your workitem
           b. In this parallel branch create step 'Wait for Event; and refer it to your ZZJIMBO.FINISHED.
          c. define necessary branches required to complete the fork as 1. meaning, if any one of the branch ends flow will continue to next step in main workflow.
    So, when the event ZZJIMBO.FINISHED is raised with the correct instance which was used in workflow. 'Wait for event' will receive it and this branch will end and eventually other branch will get logically deleted. You can put some flag in the 'Wait for event' branch using which u can understand whether the workitem is completed in normal way or through exeption.
    Hope this helps !!
    Regards
    Krishna Mohan

Maybe you are looking for