SOAP->XI->RFC "NO_RECEIVER_CASE_BE"

[Former Member]

Hi:

The scenario is SOAP->XI->RFC.

When i try to execute the scenario i get an error "NO_RECEIVER_CASE_BE"

receiver determination is true

Edited by: sky yuyi on Dec 23, 2008 6:36 AM

[dharamveer_gaur2 · Accepted solution]

Hi

The message NO_RECEIVER_CASE_BE shows that there is no suitable Receiver Determination for the sender interface.

So make sure your Sender and Receiver objects are correct.

[Former Member · Accepted solution]

HI

I believe my Sender and Receiver objects are correct.

[dharamveer_gaur2]

Hi

Your scenario is Synch so make sure using service "Best Effort". Also check your Receiver Determination, mentioned right sender and receiver service.

[Former Member]

Hi

my scenario is Synch with service "Best Effort". Receiver Determination is true .

[aashish_sinha]

Hi,

Have a look into these threads.

Reply by Udo.

Regards

Aashish Sinha

[Former Member]

HI

there are some error log from Message Display Tool (Detail Display) .

Error Category: XI_J2EE_ADAPTER_XI_HANDLER

Error Code :CALL_CONSUMER_ERROR

Audit Log for Message: b6577f11-d31e-11dd-cc12-000f1f6bbad3

Time Stamp Status Description

2008-12-26 07:27:55 Success SOAP: request message leaving the adapter (call)

2008-12-26 07:27:55 Success Application attempting to send an XI message synchronously using connection AFW.

2008-12-26 07:27:55 Success Trying to put the message into the call queue.

2008-12-26 07:27:55 Success Message successfully put into the queue.

2008-12-26 07:27:55 Success The message was successfully retrieved from the call queue.

2008-12-26 07:27:55 Success The message status set to DLNG.

2008-12-26 07:28:03 Error Received XI System Error. ErrorCode: NO_RECEIVER_CASE_BE ErrorText: ErrorStack: Es konnte kein Empfänger ermittelt werden.

2008-12-26 07:28:03 Error Returning synchronous error notification to calling application: XIServer:NO_RECEIVER_CASE_BE:.

2008-12-26 07:28:03 Error Transmitting the message using connection http://dlxt:8000/sap/xi/engine?type=entry failed, due to: XIServer:NO_RECEIVER_CASE_BE:.

2008-12-26 07:28:03 Error The message status set to FAIL.

pls give me some ideas.

[Former Member]

Hello,

How are you doing the scenario,i mean using BPM ??

If not using BPM are you handling the response message from the RFC (have defined required config objects)

Regards

Rajesh

[Former Member]

HI,

I handled the response message from the RFC without using BPM .

Regards

SKY

[Former Member]

Hi,

1. Are you able to see any messages in SXMB_moni?

2. Are you able to see the inbound message soap sender message?

3. Did the request sent to RFC?

4.Did the response received from the RFC.?

Where exactly you are stuck with?

Regards

Rajesh

[Former Member]

Hi Sky

Is your scenario a Sync one? and QOS BE.

QOS BE is required for Sync cases only and if you use it for Async then also you can face this error.

Another this as suggested above do a cache refresh. and check if the system user is locked.

Thanks

Gaurav

[Former Member]

Hi,

1. Check your settings in receiver determination, Interface determination and Receiver agreement

2. Make sure the receiver business service/system is pointing to the correct R/3 system

3. Refresh the cache in directory (SXI_CACHE)

4. Integration builder -> Administration ->Cache Overview ->Refresh all the caches for Repository, Directory and Runtime.

regards

Ganga

[dharamveer_gaur2]

Hi

Refresh your CPA Cache using user PIDIRUSER with URL

http://XIHost:<Port>/CPACache/refresh?mode=full

also check with similar solved thread

[Former Member]

Hi

I refresh CPA Cache using user PIDIRUSER with URL

http://XIHost:<Port>/CPACache/refresh?mode=full,but getting the same error.

my scenario is synchronous.

[Former Member]

Hi

I have refreshed CPA Cache using user PIDIRUSER with URL

http://XIHost:<Port>/CPACache/refresh?mode=full,but getting the same error.

my scenario is synchronous.