No Sender or Receiver Info found

Hi,
We are getting an error message " no sender or receiver interface definition found" while trying to send the messages from XI to ECC.
From ECC we are able to send the message to XI through PROXY. But not able to receive the messages from XI to ECC. In the SXMB_MONI transaction it displays the below error.
No implementing class registered for the interface (ABAP interface, request message , )
Thanks,
CS.

where do you see the error message mentioned? in Pi system?.
what is the scenario you are trying to configure?

Similar Messages

Read Xml file for Sender and Receiver Info

Hi
Is it possible to customize B2B to read Sender/Receiver/Document Information from the xml file which is supposed to be transmitted?
I do NOT the option to specify this information in channel configuration under file name since file name will not have this information.
But I am fine with writing any plug to set this information somewhere to achieve the same.
Regards
Punit

For outbound transactions, file name is the only option available currently if you are using Generic File internal listening channel. You may use any other transport like JMS/AQ/Fabric and partner and document information can be set in headers.
Can you let us know the complete use case?
Regards,
Anuj

My BB 8900 constantly is trying to send and receive info from the network

The connectivity arrows are on almost constantly - thereby draining the battery within a 8hr period.
I have checked to make sure there is no programs that are running. I even had rogers replace it, only to have it happen again.
Does anybody know why this would be happening?
thanks!

Hi and Welcome to the Forums!
You have some app running that is constantly using your network connection to do something. It could be your browser -- if it's left on an active web page that auto-refreshes, that will do what you describe. It could be a news app -- if you leave it running in background and it has a short interval for refreshing it's news articles, that would result in what you describe. It is doubtful that this is an email issue -- if you have BIS email conduits, traffic to your BB is only generated when there is a change at your email server that needs to be pushed to the BB...there is no check for new email directly between your BB and your email server...BIS functions as that bridge.
Hold down your BBKey and look at the ribbon of apps...one (or more) of them is the offending app here. Check them all and always properly close apps when you don't want them to be able to do this. The red and the back keys do not, btw, properly close apps...only pressing the BBKey and selecting Close or Exit truly closes down apps...the other keys leave it to the apps to decide what to do, and many are traffic generators (e.g., twitter, FB, MySpace, news readers, etc.).
Good luck and let us know!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

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

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

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

Error in BPM (No receiver agreement found from sender to bpm)

Hi all
In a simple bpm scenario, I am getting a error that No receiver agreement found for sender service to bpm integration process.
What might be the reason?

your configuration should like this.
say u are doing File to File using BPM
File to BPM
then BPM to File.
so u need to create RD where sender is fileservice and receiver is BPM.
second u hav to create another RD where BPM is sender and Fileserviceis receiver.
So there should be
one Sender Ag
two RD
two ID
one RA.
Thanks
Farooq.

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.

IDOC - BPM - IDOC Error --no sender or receiver interface definition found

I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
I have read instructions on weblogs:
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
<Trace level="3" type="T">Processing mode is</Trace>
<Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
<Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
<Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
<Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
<Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
<Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
</Trace>
Thanks,
Sergio

Rajeev,
The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
Below is some trace information in the Receiver Determination.
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
Thanks,
Sergio

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

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 sender or receiver interface definition found

Hi,
I have designed an JDBC to R3 scenario.
In the XI system SXMB_MONI the message was processed successully on the outbound side.
On the R3 side. in SXMB_MONI => Trace there is a message like
no sender or receiver interface definition found
What could be the problem. I have checked the IR and ID settings.
Everything seems to be OK. Is there a problem with the Queues.
Please suggest.
Thanks
Kumar

Hi,
We have encountered same error in one of our scenarios. When we restarted these messages they were successfully processed. This could be probably because of the cache update failure at that particular instance when the message was posted.
Restarting the message through SXMB_MONI could probably solve the problem sometimes.
Regards
Sai

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

Unable to send or receive contact info through message

Hi, I am unable to send or receive contact info through message.How to solve this problem? thanks

Business card/vCard is exchanged through MMS and not by SMS.
Make sure your MMS is configured and activated and you have cellular data/3G ON while exchanging MMS.

No Sender or Receiver Info found

Similar Messages

Maybe you are looking for