cancel
Showing results for 
Search instead for 
Did you mean: 

Error: no interface action for sender or receiver found

Former Member
0 Kudos

Hello,

I have configured a asynchronous RFC to JDBC scenario.

When i try to execute the end to end scenario , the message in SXMB_MONI is with a green flag(scheduled) and queue status is yellow and when i double the message , the trace shows following message:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Inbound Message

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />

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

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="1" type="T">Work Process ID: 25711</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />

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

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />

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

-->

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

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

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = HXD</Trace>

<Trace level="1" type="T">client = 001</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

<Trace level="1" type="Timestamp">2010-05-24T12:23:09Z CET</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />

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

-->

<Trace level="1" type="T">Message-GUID = 3CA00D0C20460CD10B3CA18E3C804118</Trace>

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

<Trace level="1" type="T">QOS = EO</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />

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

-->

<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>

<Trace level="1" type="T">Queue name : XBTR0004</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTR0004</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

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

-->

<Trace level="1" type="T">--start determination of sender interface action</Trace>

<Trace level="1" type="T">select interface</Trace>

<Trace level="1" type="T">select interface namespace</Trace>

<Trace level="1" type="T">--start determination of receiver interface action</Trace>

<Trace level="1" type="T">Loop 0000000001</Trace>

<Trace level="1" type="T">select interface Z_SD_HP_SALESORG</Trace>

<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:rfc:functions</Trace>

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

<Trace level="1" type="T">Hence set action to DEL</Trace>

</SAP:Trace>

The pipeline steps on the left hand side in sxmb_moni shows only inbound Message i.e remaining steps are not executed.

When i try the execute message by directly sending message from Runtime Workbench , the scenario is executed successfully.

Please help.

Thanks & Regards,

Loveena

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

The problem was that default client 001 was not changed to client 200

Former Member
0 Kudos

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

Former Member
0 Kudos

Hi Rajesh,

Thanks for your reply.

Where do I maintain this Logical system , i mean in our report in R/3 we only call the RFC as background task and destination as RFC Destination of type 'T' . Then where do we specify the Logical System in the Sender System.

Please help.

Thanks,

Loveena

Former Member
0 Kudos

In SAP system I have created RFC Destination of type T and mentioned the Program ID and used the same program ID in the Sender CC.

Apart from these are there any other configuration I am missing, Should the program ID also be registred somewhere also?

Please help.

Thanks,

Loveena

Former Member
0 Kudos

HI,

No need to register the program id any where else except in CC as you said already done...

looks like the business system of sender is not matching with the one you created the receiver agreement..

check the logical system has been maintained for the business system/service used as sender

it might have worked when you test using RWB as you are manually passing the sender business service there

HTH

Rajesh