No receiver found;

Hi,
Scenario : IDOC --> XI --> JMS
Here i has configured the ReceiverCC properly, but when i trigger the IDOC am getting the error saying that,
No receiver found; message stopped but has no errors
Please give me any suggestions here and i cross checked twice my receiver channel.
Thanks & Regards,
Y.Raj.

Yesh,
You need to go step by step then only you can solve you problem. The problem doesn't seems very big.
Step1. First refresh the cache in XI by tcode SXI_CACHE and in Integration Directory go to menu Environment ---> Clear SLD DATA Cache.
Step2. Do header mapping in Receiver Agreement (tick the check box Receiver Service and enter the Receiver Service name as it is, you can also take F4 help) as suggested by experts.
Step3. if still nothing works, then change the receiver to some File_system and use Receiver File adapter and then check if you are able to receive the IDOC xml atleast. This test will confirm the cause problem.
Best of Luck!!
Sarvesh

Similar Messages

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.

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" ?>
- 
- <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

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" ?>
- 
- <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

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

Trace level="1" type="T" -no interface action for sender or receiver found

Hi Experts,
I try to integrate PI and abap 7.0 using XI adapter (feel doubts about type).
RWB and SXMB_MONI at PI side show that test message was successfully sent. But I cant see it in DQ
http://cnh.com/XI/SDIIOC01/RCVR</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>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type
What could be the problem which I'm facing and how could I fix this
regards
nagendra

i understood its ur SAP XI to inbound proxy scenario?
Do the message in MONI of XI is showing correctly?
R u getting an error message in R3 moni?
Did u configure ur scenario correctly both at Xi n R3 using sproxy tcode.
chirag

SXMB_MONI: no interface action for sender or receiver found

Hi Experts,
I try to integrate PI and BI 7.0 using XI adapter (feel doubts about type).
I used 2 giudes: "How to Push Data into BW from XI" and "How to Send XML Data to BW".
SLD check is ok. Proxy is active at BW side. Quality of Service - Exactly Once.
RWB and SXMB_MONI at PI side show that test message was successfully sent. But I cant see it in DQ (RSA7).
xml from SXMB_MONI at PI and reciever part:
<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 data_tobw</Trace>
<Trace level="1" type="T">select interface namespace http://integrate/xi/bw</Trace>
<Trace level="1" type="T"><b>--no interface action for sender or receiver found</b></Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
Help me to send xml to BW please.
Thanx in advance,
Alex

>
Alexander Rychkov wrote:
> Hi Experts,
> I try to integrate PI and BI 7.0 using XI adapter (feel doubts about type).
> I used 2 giudes: "How to Push Data into BW from XI" and "How to Send XML Data to BW".
> SLD check is ok. Proxy is active at BW side. Quality of Service - Exactly Once.
>
> RWB and SXMB_MONI at PI side show that test message was successfully sent. But I cant see it in DQ (RSA7).
>
> xml from SXMB_MONI at PI and reciever part:
>   <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 data_tobw</Trace>
>   <Trace level="1" type="T">select interface namespace http://integrate/xi/bw</Trace>
>   <Trace level="1" type="T"><b>--no interface action for sender or receiver found</b></Trace>
>   <Trace level="1" type="T">Hence set action to DEL</Trace>
>
> Help me to send xml to BW please.
>
> Thanx in advance,
> Alex
confirm if interface data_tobw with namespace http://integrate/xi/bw is present in IR and also if it is activated.
Also do a cache refresh from sxi_cache

NO INTERFACE ACTION FOR SENDER OR RECEIVER FOUND

Hi Masters of SRM
Into SRM/SUS client received an message XML across XI the SXMB_MONI in trace section show the next message

<Trace level="3" type="T">Persisting message Status = 003</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline SENDER</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface PurchaseOrderRequest_Out</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/Procurement/Global</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</Trace>
<Trace level="1" type="T">select interface namespace</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
NO INTERFACE ACTION FOR SENDER OR RECEIVER FOUND
what can I do ?
thanks.

Hi Nikhil .
yes the Receiver Determination is Active.
I can see other message into message in SUS client these is the complete message.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Work Process ID: 884922</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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = SND_CENTR</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = SENDER</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<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="3" type="T">system-ID = SRD</Trace>
<Trace level="3" type="T">client = 009</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2011-03-08T02:25:46Z 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 = 4D71A759FF9E00D8E1008000B9F06E02</Trace>
<Trace level="1" type="T">PLNAME = SENDER</Trace>
<Trace level="1" type="T">QOS = EOIO</Trace>
<Trace level="1" type="T">Queue-Id = ORD4000000482</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="3" type="T">QOS = EOIO</Trace>
<Trace level="3" type="T">Message-GUID = 4D71A759FF9E00D8E1008000B9F06E02</Trace>
<Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = SENDER</Trace>
<Trace level="3" type="T">Internal PLID = SAP_SENDER</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBQSORD4000000482</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBQSORD4000000482</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = 4D71A759FF9E00D8E1008000B9F06E02</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = SENDER</Trace>
<Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline SENDER</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface PurchaseOrderRequest_Out</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/Procurement/Global</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Work Process ID: 725194</Trace>
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<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 SENDER</Trace>
<Trace level="3" type="T">system-ID = SRD</Trace>
<Trace level="3" type="T">client = 009</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2011-03-08T02:25:46Z CST</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 SENDER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = SENDER</Trace>
<Trace level="3" type="T">Internal PLID = SAP_SENDER</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_SENDER</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INTEGRATION_SERVER</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2011-03-08T02:25:46Z CST Begin of pipeline processing PLSRVID = SENDER</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
<Trace level="1" type="Timestamp">2011-03-08T02:25:46Z CST Start of pipeline service processing PLSRVID= PLSRV_CALL_INTEGRATION_SERVER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_INTEGRATION_SERVER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INTEGRATION_SERVER</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="1" type="T">URL for integration server read from global configuration</Trace>
<Trace level="1" type="T">URL= dest://SAP NETWEAVER XI</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">Addressing mode: CallIntegrationServer</Trace>
<Trace level="3" type="T">URL = dest://SAP NETWEAVER XI</Trace>
<Trace level="3" type="T">Host =</Trace>
<Trace level="3" type="T">Port =</Trace>
<Trace level="3" type="T">Transport protocol = HTTP</Trace>
<Trace level="3" type="T">Message protocol = 003000</Trace>
<Trace level="3" type="T">Path =</Trace>
<Trace level="3" type="T">Attributes of destination: SAP NETWEAVER XI</Trace>
<Trace level="3" type="T">Type = H</Trace>
<Trace level="3" type="T">Pipeline =</Trace>
<Trace level="3" type="T">Action = EXECUTE</Trace>
<Trace level="3" type="T">Host = mxwpides</Trace>
<Trace level="3" type="T">Port = 50000</Trace>
<Trace level="3" type="T">Client = 001</Trace>
<Trace level="3" type="T">User = PIAPPLUSER</Trace>
<Trace level="3" type="T">Language =</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">SSL not active</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="1" type="T">HTTP Multipart document length: 8089</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="1" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="1" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="1" type="T">sap-xi-messageid 4D71A759FF9E00D8E1008000B9F06E02</Trace>
<Trace level="1" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="1" type="T">HTTP-client: parsed & response message object created</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2011-03-08T02:25:47Z CST End of pipeline service processing PLSRVID= PLSRV_CALL_INTEGRATION_SERVER</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline SENDER</Trace>
</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="3" type="T">system-ID = SRD</Trace>
<Trace level="3" type="T">client = 009</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = WF-BATCH</Trace>
<Trace level="1" type="Timestamp">2011-03-08T02:25:47Z CST</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 003</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline SENDER</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface PurchaseOrderRequest_Out</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/Procurement/Global</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</Trace>
<Trace level="1" type="T">select interface namespace</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>
Thanks.
best regards

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

How to cancel the No receiver found messages in XI

Hi Experts,
Could you please help me here, how to cancel the no receiver found error messages in XI?
I have tried to cancel it , but it is not working. Please let me know know the process?
Thanks in Advance.
Best Regards,
Madhu.

Hi,
If the error message is of red flagged, then you can cancel the message.
You can use the report 'RSXMB_CANCEL_MESSAGES' to cancel the error messages.
If the message is of synchronous, it cannot be cancelled.
Thanks,
Kanda

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

No receiver found in Receiver Determination

Hello Experts,
Sub: Calling integration process (which in software component1) from sender service interface_Out (which is in another software component2) in Receiver Determination Fails.
       There are two software components, S/W C1, S/W C2,
        In S/W C1,->
        Integration process (IP1)created in S/W C1, with name space NS1,
        Service interface1(abstract) SI1 with message type MT
        In S/W C2,->
        Sender service interface2 SI2(outbound) with message type MT with namespace: NS2
(MT message type, in both service interface holding the same,
used SI1 In receive step in IP1.
Interface Determination from BS2,SI2,NS2<->   IP1,SI1(No mapping).)
In Receiver Determination,
Business system BS2;
Sender Service Interface: SI2;
Name space: NS2,
In Receivers : IP1
Problem is : do not find this receiver.
I have to call this process, like this. Please help on this.
Use case is:
single Soap request is coming, many application are using the same using common Receiver determination( which in S/W C2),
Now i have to use the same receiver determination to send this message in IP1 which is in SW C1;
-> any alternative solutions for this
Thanks,
Deviprasad.

hi,
when you use Integration Process the configuration in the ID must be
Receiver Determination 1:
Sender System: XXX
Enterprice Services (outbound)
Namespaces
Target System: Integration Processes
No Mapping requiered in Interface Determination
Line:
Receiver Determination 2::
Sender System: Integration Process
Enterprice Services (Abstract)
Namespace
Target System: YYYY
No Mapping requiered in Interface Determination
Sender Agreement=1
Receiver Agreement=2
Interface Determination=2
Communication Channels=2
Take in mind that in the Interface determination you have to define as receiver structure the Service Interface (Enterprice Service in PI7.1) type Abstract. if you cant select it delete all filter in the popup qhen you have to select the Inteface in the reciver structure.
Check the Integration PRocess if you define the SI_XXX_abs in the reciver step.
check all changes in the ESR were activated
Check this out and let me know
Edited by: Rodrigo Alejandro Pertierra on Sep 3, 2010 2:42 PM

No receiver found - Scenario works fine in Test in Integration Directory

Hello Everyone,
I'm receiving the following in SXMB_MONI when I run my xmlFile to RFC scenaro:
... (10 lines)
I have tried the following to remedy this:
- CPA Cache Refresh
- SXI_CACHE refresh on ABAP
- Repository, Runtime, and Directory Cache refreshes (ALL).
Please help! I do appreciate your time and help on this issue.
Regards,
John

Hi,
check you RD Condition for your Business System and check your configured correct Service and receiver for your System in ID.
This will help you
/people/paul.medaille/blog/2005/06/24/test-your-xi-configuration-with-the-new-test-tool
Regards
Agasthuri Doss

How to cancel messages in SXMB_MONI with status "No receive found"

Dear All,
I need to cancel message with error status as mentioned in captioned subject.
Can you please guide me how to do it?
Regards,
Saras Jain

One more thing to check.....confirm if there is any background job scheduled to cnacel the message once it goes into error....if it is cancelled in this manner...if so you wont be allowed to cancel the (already cancelled) message manually
Regards,
Abhishek.

No receiver found;

Similar Messages

Maybe you are looking for