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

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.

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

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">--no interface action for sender or receiver found</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">--no interface action for sender or receiver found</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

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

TS3276 I have no sound on my MacBook Air for sending and receiving messages. All sound settings have been checked and are OK. This problem has arisen many times and is intermittent in the sense that the sound returns and disappears for no apparent reason.

I have no sound on my MacBook Air for sending and receiving messages. All sound settings have been checked and are OK. This problem has arisen many times and is intermittent in the sense that the sound returns and disappears for no apparent reason.

Open System Preferences > Sound > Sound Effects
Select: Play user interface sound effects
And make sure the Mute box is not selected.
Now open Mail. From the Mail menu bar clik Mail > Preferences then select the General tab.
Make a selection from the: New messages sound pop up menu.

Prerequisites for Sender and Receiver FTP adapter

Hi Experts,
I am new to PI and configuring simple file to file scenario. I need to know the prerequsites for sender and receiver FTP adapter. Scenario is System A -> XI -> System B .
What I want to know is:
1> What ports need to be opened?
2> Any service that I need to activate?
3> Do I need to install FTP server in any of the machine?
If I have missed something, please add.
Br,
Nilz

Hi,
1> What ports need to be opened?
mentioned in below link as said its 21.
2> Any service that I need to activate?
No
3> Do I need to install FTP server in any of the machine?
THere are two ways by which u can pick ur file.
1) NFS by which u can put the file on XI appplication directory and pick up ur file.
2) FTP u have to put ur file on FYP server and XI will pick up the file from there. U can use freeware FTP and install it on ur Desktop search on goolge u will get ti FTP installtion.
refer the below configuration requirement for FIle adapter.
http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
ALso refer the end to end file to file scenario.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/flatFILETOFLATFILE&
chirag

My phone number is not coming up as an option for sending and receiving imessages

My phone number is not coming up as an option for sending and receiving imessages

You do not have a "phone number". Your ipad has a cellular access number and can't make phone calls.
You must use your apple ID email for imessage and FaceTime on iPad.

COPA: how to identify which cost element for sender and receiver in IMG

Hi Guru,
I know my cost element for sender and receiver from the settlement document, but where in IMG, i can identify how it settup to use which cost element for my sender - order , which cost element should be used for my reciever profit segment.
Thanks,
Kick

Hi,
Go to KEI1
Select your transfer structure
double click on assignment lines
check the source and value fields to get the mapping.
Regards,
Sridevi
Pls. assign points, if useful

Hi i use iphone 4 with iso 6.1.3!! Am not getting an option to register my phone number in imsg!! Am just getting an option to set my email address for sending and receiving the imsgs!! How do i register my phone number??

Hi i use iphone 4 with iso 6.1.3!! Am not getting an option to register my phone number in imsg!! Am just getting an option to set my email address for sending and receiving the imsgs!! How do i register my phone number??

Hello Nikkii,
Thanks for using Apple Support Communities.
For more information on this, take a look at:
iOS: Troubleshooting FaceTime and iMessage activation
http://support.apple.com/kb/ts4268
Troubleshooting telephone-number activation (iPhone only)
After each step, toggle FaceTime and iMessage off and then on in Settings > Messages and Settings > FaceTime.
Update to the latest version of iOS.
Ensure that your iPhone is set to the correct time zone. Tap Settings > General > Date & Time.
Note: If Set Automatically is on but the incorrect time zone is displayed, turn Set Automatically off and then choose the correct time zone, date, and time. Then turn Set Automatically on again.
Ensure that FaceTime has not been restricted: Settings > General > Restrictions > FaceTime.
Verify that you can send SMS messages. You need a valid SMS messaging plan to activate FaceTime.
Contact your carrier to verify that there are no restrictions or blocks on text messages. Blocks on text messaging will prevent iMessage and FaceTime registration.
If you are unable to activate iMessage or FaceTime on a device after remote wiping it, wait at least 24 hours and try again.
If "Waiting for Activation" is displayed, leave FaceTime and iMessage enabled for 24 hours. Toggling FaceTime or iMessage off and on will cause the registration process to start over.
Best of luck,
Mario

FAX machine with Manual function & option to connect PC for Send and receive

Nearly every MFD out there has these capabilities. I know the Ricoh, Konicaminolta, and the Kyocera can do this. The larger machines the fax needs to be installed as an option. Once installed you have walk up fax, scan to PC, Scan to e-mail, Fax forwarding to PC, or e-mail and if the driver is installed you can fax from your PC through the copier.

Hi to the Community
We have a requirement of FAX machine which should fulfill
our below requirements
Manual mode for sending and receiving Fax as Traditional
Second option required is it can be connected to PC so that
fax can be sent and receive directly from computer as well
I know to set up windows fax option to fulfill the second
requirement, but we need both options
If anyone knows a specific model, kindly let me know
This topic first appeared in the Spiceworks Community

Please..how to instal libero mail on mi Ipad. I need the parameter for send and receive mail..Thanks

Please..how to instal "libero" mail on my Ipad. I need the parameter for send and receive mail..Thanks

FYI: POP will by default, delete messages from the server after downloading them (This applies to most pop clients, computer or mobile). POP is old tech and is not recommended if IMAP or Exchange are available. The default when setting up a g-mail type account is IMAP. Full synchronization with the server. You may also be able to set it up as an Exchange account, allowing for push e-mail and sync of calendars and contacts as well. See the Gmail help pages for instructions.

Message protocol is different for sender and receiver JDBC

In File adapter the message protocol can be either FTP or NFS for both sender as well as receiver. but for JDBC adapter the message protocol is JDBC and for receiver adapter the message protocol is XML SQL Format or native sql string only. Why this is different ? Why cant we use JDBC as message protocol for receiver also ?
I thought JDBC is the message protocol for JDBC adapters irrespective of whether they are sender or receiver. Can someone throw light on this ?

Hi,
You can find more about JDBC scenario at following links:
Configuring the Sender JDBC Adapter
[http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm|http://help.sap.com/]
[http://help.sap.com/saphelp_nw04/helpdata/en/1d/756b3c0d592c7fe10000000a11405a/content.htm|http://help.sap.com]
Configuring the Receiver JDBC Adapter
[http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm|http://help.sap.com]
[http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm|http://help.sap.com]
[https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6d36d51d-0b01-0010-b3aa-9cb313b63cf4|https://help.sap.com]
Regards,

XML Monitor: no interface action for sender or receiver found

Similar Messages

Maybe you are looking for