Solved: 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">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.

SAP Managed Tags:
SAP Supplier Relationship Management

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Oscar,

Are you seeing this in SXMB_MONI of XI?

If so then this is because you need to configure the Receiver Determination in your XI scenario.

Regards,

Nikhil

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks Nikhil

I was configurates the receiver detemination but I dont know is ok configurates. let me explain how is that.

Receiver determination

Name : |SRD_009 | PurchaseOrderRequest_out

where SRD_009 IS BUSSINES SYSTEM TO EBP.

SRD_008 IS BUSSINES SYTEM TO SUS

Sender

Communication Component : SRD_009

Interface : PurchaseOrderRequest_out

Namespace: http://sap.com/xi/SRM/Procurement/Global

Receiver :

Communication Party : *

Communication Component : *

Sofware Component:

SRM SERVER 7.0

Configured Receivers :

Local Rule

Condition : empty

Communication Party : empty

Component Comunication :SRD_008.

can I do to fix ?

Thanks.

Oscar,

At the top of this Receiver Determination, can you see if it is 'Active' or 'In process'?

Regards,

Nikhil

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

- <!-- Response

-->

- <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="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>

<Trace level="3" type="T">Getting type of XMB...</Trace>

<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">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="T">Message-GUID = 4D71A759FF9E00D8E1008000B9F06E02</Trace>

<Trace level="1" type="T">PLNAME = SENDER</Trace>

<Trace level="1" type="T">Queue-Id = ORD4000000482</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="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="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="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="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">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">Pipeline elements</Trace>

<Trace level="3" type="T">PLSRVID = PLSRV_CALL_INTEGRATION_SERVER</Trace>

<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">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_DUMMY = 0</Trace>

- <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">Transport protocol = HTTP</Trace>

<Trace level="3" type="T">Message protocol = 003000</Trace>

<Trace level="3" type="T">Attributes of destination: SAP NETWEAVER XI</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">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 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 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="T">----

</Trace>

- <!-- ************************************

-->

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

Please check if the namespace is present in IR.

Then do a cache refresh in XI. Check SXI_CACHE tcode on XI side. Delete the message from the queues and reschedule it once again.

Regards,

Nikhil

Nikhil. in SMXB_MONI SEND THE NEXT ERROR

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<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">Using Receiver Determination 8D38A57FFC3C3A2D87EBD9D0F9CD1A60</Trace>

<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>

<Trace level="3" type="T">...create rule engine</Trace>

<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>

<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:PurchaseOrderRequest/PurchaseOrder")% CE *</Trace>

<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:PurchaseOrderRequest/PurchaseOrder</Trace>

<Trace level="2" type="T">......extracting values found: 1</Trace>

<Trace level="2" type="T">...invalid Receiver: - SRD_008</Trace>

<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>

</Trace>

AND SMQ2.

XI Error NO_RECEIVER_CASE_ASYNC.RCVR_DETERMINATION

THANKS FOR ALL.

Edited by: Oscar vazquez on Mar 9, 2011 1:39 AM

Hi Oscar,

Have you done Cache refresh in XI? Clear the SLD Cache Data from Environment menu in ID and also do the cache refresh and then try again.

If the above works fine, I think then the error lies in your Business System. Try creating a new BS and use it in your scenario.

Regards,

Nikhil

Answers (0)

Ask a Question

Top Q&A Solution Author

User

Count

NO INTERFACE ACTION FOR SENDER OR RECEIVER FOUND

Accepted Solutions (1)

Accepted Solutions (1)

Answers (0)

Re: Error in a service of application MMPUR Functi...

Mileage Rate- UK

Why doesn't SLP recognize suppliers with special c...

Re: Workflow Email notification in CP

Workflow Email notification in CP