Error code - NO_RECEIVER_CASE_ASYNCV

[Former Member]

Hi All

I am a sap sd cons and I am getting the following error from production XI system. Any idea what this could be?

Attribute

Engine - Integration egine

Status - System Error

Repeatble - Yes

Cancelable - yes

Start - 24.09.2009 4:45

End - 24.09.2009 4:45

Sender party -

Sender service - PRD_100

sender interface - urn:sap-com:doc:sap:idoc:messages

ZKIT.ZKITDR_KIT

Receiver party

Receiver service

Receiver Interface

Quality service - Exactly Once

Error category - RCVR determination

Error code - NO_RECEIVER_CASE_ASYNCV

Message - A6BCE7BCHDFGHKFLORHTKJGJ.. this is a long number i have just entered something in random..

Reference

[Former Member · Accepted solution]

Refresh the cache by tcode SXI_CACHE and also perform full CPA Cache refresh then try again.

Regards,

Sarvesh

[Former Member · Accepted solution]

Hi All,

for your valuable answers. but like i told you, I am not a XI guy. I am sd guy and what i wanted to know is

- What needs to be checked from my side in ECC?

- How do I verify that there is nothing thats needs to be fixed from ECC end?

- How do I find out about this IDoc which is leaving the system for XI ?

regards

Mahesh

[former_member200962 · Accepted solution]

What needs to be checked from my side in ECC?

The message that you are sending from ECC to XI should have all the fields as desired by the condition mentioned in Receiver Determination (ask what is the condition to some XI person)

How do I verify that there is nothing thats needs to be fixed from ECC end?

Once you are 100% sure that you are sending all the required values.

How do I find out about this IDoc which is leaving the system for XI ?

Refer this blog on monitoring the IDOC from XI: /people/kamalkumar.ramakrishnan/blog/2008/02/13/monitoring-the-idoc-adapter-in-xipi-using-idx5

Regards,

Abhishek.

[Former Member]

There is a Test Configuration in the ID that can be used to validate your configuration without actually sending out a message. It's useful to debug in production. Try using it to determine what is missing. Copy paste what it says if you need help.

[Former Member]

Hi,

This error means that there is no receiver found for the sent message...

i.e no action has been determined for the sent idoc from the R/3 system....

if it was running fine already.. then check the cache status in tcode SXI_CACHE...and ensure that it will be in green...

if it is the new one then check the recievers has been created properly...

for this go to ID and there check the receiver determination and check the sender service and interface name is same as what you see in the audit logs...

Hope this clears you

Rajesh

[former_member200962]

There is an object called Receiver Determination (RD) in integration Directory and can have some condition to route the message to the receiver system only if the condition is satisfied......now check if the message that you are sending satisfies this condition in RD....if not satisfied then you get the above kind of error.

Regards,

Abhishek.