cancel
Showing results for 
Search instead for 
Did you mean: 

ABAP client proxy send message fialed

Former Member
0 Kudos

I developed one ABAP client proxy to send msg. status in SXMB_MONI is 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>

After I test it in RWB,I'm sure that IR and ID is right. Then what's wrong?

Accepted Solutions (0)

Answers (8)

Answers (8)

Former Member
0 Kudos

I created a business service 'BS_ECC_800' and confiure the scenario. It can work now.

Former Member
0 Kudos

I found that sender service is BS_ECC_800 in SXMB_MONI, which didn't exist.

prateek
Active Contributor
0 Kudos

This could be name of some Business Service. I would suggest to recreate the ID objects and refresh the CPACache. If u have same sender interface for two receiver, then use multiple receivers in the same receiver determination.

Regards,

Prateek

Former Member
0 Kudos

For this you can do the header mapping in Receiver Agreement.

Former Member
0 Kudos

Hi,

please go thru this link.

/message/675155#675155 [original link is broken]

Thanks ,

Shweta

aashish_sinha
Active Contributor
0 Kudos

Hi ,

if you're not using LS partner profile

you need to do as shown here:

Regards

Aashish Sinha

Former Member
0 Kudos

Hi,

plz refer to this link

Thanks,

Shweta

Former Member
0 Kudos

pls compare ur receiver determination in ID with that

of the incoming message ...and see if any mismatch b/w

namespaces/services/interface is there...as this error

comes only when there is inconsistency b/w ID details and runtime messages..so cross-check in sxmb_moni

Former Member
0 Kudos

Hi,

There could be a chache problem. Have you tried after cache refresh?

regards,

Sarvesh

Former Member
0 Kudos

There are two scenarios with the same outbound interface.Is it the problem?

ABAP proxy send message, and then there are two route

Former Member
0 Kudos

> There are two scenarios with the same outbound interface.Is it the problem?

>

> ABAP proxy send message, and then there are two route.

Yes this could be the reason, because at the time of Receiver Determination it tries to send the message to both the interface. Are both the scenario Proxy to XI??

Try to change the Message Interface in IR and accordingly change in ID also and then try.

Regards,

Sarvesh

Edited by: Sarvesh Singh on Oct 17, 2008 2:24 PM

prateek
Active Contributor
0 Kudos

U may try the following:

1. Edit the description and reactivate the receiver determination step in ID.

2. Perform a complete CPACache refresh.

3. Delete and recreat your ID steps.

Regards,

Prateek