cancel
Showing results for 
Search instead for 
Did you mean: 

error message : RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>

Former Member
0 Kudos

Hi,

I am getting following error message

RCVR_DETERMINATION">*NO_RECEIVER_CASE_ASYNC*</SAP:Code>

I have gone through previous threads, checked Receiever determination, receiver CC, adapter sp identifier,

nothing helped.

I see an error message in MONI everytime I send the message

Following is exact trace and error message from MONI.

Trace :

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

- <!-- Receiver Identification

-->

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

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Sender scheme external = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external =</Trace>

<Trace level="1" type="T">Sender party normalized =</Trace>

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

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

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

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

<Trace level="1" type="Timestamp">2008-03-20T03:53:16Z 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 = 2BCD0880F63111DC8BDF00132165C741</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</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 = CENTRAL</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_CENTRAL</Trace>

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

<Trace level="1" type="T">Generated prefixed queue name = XBTI0002</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="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />

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

-->

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


</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = BC6</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">2008-03-20T03:53:16Z CET</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 CENTRAL</Trace>

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

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />

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

-->

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

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

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

-->

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

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>

</Trace>

</Trace>

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

<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>

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

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

-->

</SAP:Trace>

*Error message:*

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

- <!-- Receiver Identification

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area=" RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC </SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>No receiver could be determined</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

regards,

Nikhil.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

As the error is specific to receiver itself you need to check on your receiver for the sender in the receiver determination.

what is your scenario??

Mudit

Former Member
0 Kudos

its SOAP- IDOC.

the receiving system is R3.

I did everything properly

where could be the mistake?

-Nikhil

Former Member
0 Kudos

In interface determination are you creating your own Message Interface for the idoc or using the default one.

Sometimes this also leads to this error.

Mudit

Former Member
0 Kudos

deleted existing ID objects and re created the entire scenario in ID

now the error message is changed n I am getting the following error message :

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

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>

<SAP:P1>BSV_SPO_MCA_PURCH_REQ</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Unable to convert the sender service BSV_SPO_MCA_PURCH_REQ to an ALE logical system</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Nikhil.

GabrielSagaya
Active Contributor
0 Kudos

For the business sytem you have to mention the adapter specific identifiers in the Integration Directory.

Go to Int. Directory -> Double Click on your IDoc Business System -> Menu -> Service -> Adapter Specific Identifiers

Maintain Logical System name and System ID and Client number.

Check the following blog.

/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system

Go to your application IDoc Sending/Receiving system and execute transaction SCC4 and double click on the connecting client and see what the logical system name is. Maintain that name in the business system. If you have done this correctly, refresh the cache

Former Member
0 Kudos

oh yeah

I figured that out...

The LS for my receiving service is : T06CLNT1

but now the LS name assigned is : C06_080

It is a Business system

I cant change it

So, I have created a new Buss service in Business service and i got message

R3 system ID and client already exists in a different system

Even though if I go to SLD and change the name to T06CLNT1 instead of C06_080, I have around 8 oubtound scenarios already working. Wud that not effect the existing scenarios?

please help

Nikhil.

GabrielSagaya
Active Contributor
0 Kudos

since you create LS in BD54 as T06CLNT1

Then perform Partner profile by WE20 for Partner type for Logical system

Give partner no =T06CLNT1

and specify other parameters like type, Receiver Port, Basic type of IDOC in Outbound Parameter.

Make sure that

Your Logical Name for BS in SLD=Your Logical Name for BS in ID by setting adapter specific identifiers

Former Member
0 Kudos

Thanks Gabriel.

I am kind of confused.

I have changed the LS name in the adapter specific identifiers (by going into SLD)

now I still get the same error mesage.

do I need to change any other ALE settings now?

if yes on which side? (R/3 or XI side)

Thanks

Nikhil.

Former Member
0 Kudos

I changed adapter sp identifiers on sender side Service and its working now..

thanks again

Nikhil.

Answers (1)

Answers (1)

Former Member
0 Kudos

hi

Error code NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC

&#56256;&#56526; Inspect receiver determination area in SXI_CACHE

&#56256;&#56452; If necessary, adjust the routing information in the Integration Directory

&#56256;&#56452; If the message is asynchronous, it can be restarted manually, and manual

changes in the SOAP header are permitted

&#56256;&#56452; Common causes of error are discrepancies between the configuration

and the SOAP header of the incoming message

&#56256;&#56452; Sender service does not match (case-sensitive!)

&#56256;&#56452; Sender interface name or namespace does not match (case-sensitive!)

&#56256;&#56452; Condition for content-based routing has not been met

&#56256;&#56459; Double-check message content

&#56256;&#56459; Double-check condition (XPath expression or context object)

note:reward points if solution found helpfull.....

regards

chandrakanth.k