Proxy to File--- NO_RECEIVER_CASE_ASYNC

[Former Member]

I have a proxy to xml file scenario getting data from ECC. I am getting the following error:

<?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>

I have noticed one thing in my error in SXMB_MONI. The sender Service appears to be incorrect from what my SLD and configuration is set to. We actually create an entry in the SLD that we actually deleted and re-created. The old entry (deleted one) is still showing up in the moni-error. We have cleared all the cache. We have deleted everything in ID and IR and rebuilt everything twice. Test configuration is also working fine. Any help would be greatly appreciated.

[naveen_chichili · Accepted solution]

Hi Tanuja,

Make sure if it is deleted from deleted from ID, not just from the configuration scenario(check in objects tab also).

If it is also deleted there just refresh the cache in SXI_CACHE and also CPACACHE.

Also check if the cache is clear in R/3 side also.

Regards,

Naveen.

[markangelo_dihiansan]

Hello,

You can clear the SLD Cache by going to ID -> Environment -> Clear SLD Data Cache. If that does not work, use tcode SLDCHECK. As a last resort, execute the function module LCR_CLEAR_CACHE so that the list of business systems will be cleared.

Hope this helps,

Mark

[baskar_gopalakrishnan2]

It is typical cache issue. Check your business system areas in RD and interface determination and agreement objects. Make sure you reference right business system name in SLD and proxy configuration. Also make sure there is no cache issue.