No receiver could be determined / NO_RECEIVER_CASE_ASYNC

[Former Member]

Dear experts,

I have created a scenario from file to rfc. I have:

- imported the RFC message

- Created a message interface

- Created a message mapping (file to RFC-message)

- Created a interface mapping

Then set up the proxy in the target system (BW).

Then I set up the configuration builder settings. Created a sender agreement (FTP pickup), and a receiver determination. With a receiving RFC comm. channel.

Now I test it, and it gives me: NO_RECEIVER_CASE_ASYNC

And:

No receiver could be determined

Exception of class CX_RD_PLSRV

I have removed it all and created it again. What did I do wrong?

Kind regards.

[Former Member · Accepted solution]

Hi,

Have you tested it in integration directory? Maybe you made a type in interface name or interface namespace.

Regards,

Wojciech

[Former Member · Accepted solution]

This is all ok. It seems to me anyway...

Could this have something to do with logical system names or so?

[Former Member · Accepted solution]

Hi,

What is inside the header of Service, interface namespace? Is correct with your configuration in directory? Try to run program SAI_CACHE_REFRESH or run transaction SXI_CACHE and refresh directory cache.

What is your receiver type of communication RFC or proxy?

best,

wojciech

[Former Member · Accepted solution]

Will try the cache thing.

The receiving comm. channel is of type RFC.

[Former Member]

Schotanus

Can you explain why u generated a proxy? if u are using a file to RFC scenario there is no need for a proxy. try configuring ur ID objects by setting the receiving comm channel as RFC and give the logon parameters there.try running the config test in ID. if you face a problem in this test the it ihas something to do with ur ID objects and not the RFC connection to BW

ArvindR

[Former Member]

Hi Arvind,

I have created a proxy based on the funtion module of a webservice which i created in BW. This is based on a how to... of SAP.

Either way, this does not explain the NO_RECEIVER_CASE_ASYNC, does it?

Kind regards.

[Former Member]

Problem solved.

Namespace was entered wrongly. To namespaces with same MI.

Thanks for the replies. Will provide points.