SAP XI receiver not found for scenario having multiple namespaces???

[Former Member]

Dear Experts,

I have a query while working on SAP PI integration scenario. Which Like I am sending data from BI to XI using Client proxy at BI and Received at application directory path of SAP XI.

The Scene is like:

1. I have created 3 namespace each one for BI side data type (Outbound), second of XI side data type, message type, message interface(Inbound) and last for the Message mapping & Interface mappings for the scenario.

2. I have developed proxy and is perfect able to see xml message processed successfully on BI side.

3. Create Receiver communication channel for FTP (No Sender is reqd as Proxy calls...)

4. Receiver determination

5. Interface determination

6. Receiver agreement

So Now everything is place.

But I am getting Interface mapping not found error while I am testing using Test tool of Integration Builder. And When I check with the SXMB_MONI on PI side I see message saying no receiver found.

SAP PI (SXMBMONI)_

<?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:P1> 
  <SAP:P2></SAP:P2> 
  <SAP:P3></SAP:P3> 
  <SAP:P4></SAP:P4> 
  <SAP:AdditionalText></SAP:AdditionalText> 
  <SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage> 
  <SAP:Stack>No receiver could be determined</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

Message appears while testing scenario with Test tool

Interface Mapping      Not found
 
Runtime error
com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_ZSNOINVIT_to_InTransitInventory~: Fatal Error: com.sap.engine.lib.xml.parser.Parser~

Can anybody help me with this? Can anybody confirm that having multiple namespace like above need some extra efforts or what?

Regards,

Gaurav Patwari

[VijayKonam · Accepted solution]

Make sure you are passing the same values for your sender system and sender interface just the way you specified in your reciever determination. Otherwise, the configuration would not work.

VJ

[Former Member · Accepted solution]

Hi VJ,

Make sure you are passing the same values for your sender system and sender interface just the way you specified in your reciever determination. Otherwise, the configuration would not work.

Thanks for your reply. I am not getting what sender system and interface can you give more details. And important thing is that the scenario I am configuring is about Client Proxy to XI so it will be native call so we won't require the sender agreement & sender communication channel.

Let me know if I am wrong or I am missing with some thing.

Regards,

[Gaurav Patwari|http://gauravpatwari.wordpress.com]

[former_member200962 · Accepted solution]

No channel for PROXY sender....No Receive Case Async is due to CACHE issue or you have not included the receiver properly in RD.

Whya re you having so many namespaces?

[Former Member · Accepted solution]

Hi Abhishek,

First of all thanks for your reply.

No channel for PROXY sender....No Receive Case Async is due to CACHE issue or you have not included the receiver properly in RD.

Why are you having so many namespaces?

1. Agree with no sender channel for ABAP Proxy. - Done

2. For Cache issues - What are the probable ways to deal with it. I already got Cache refreshed but still it gives...

3. What is RD? Can you explain more about it.

Thank you for your time & Support.

Regards,

[Gaurav Patwari|http://gauravpatwari.wordpress.com]

[justin_santhanam · Accepted solution]

Gaurav,

Copy the inbound payload and paste it here, if it's here paste the first few lines.

raj.

[Former Member · Accepted solution]

Hi Raj,

Copy the inbound payload and paste it here, if it's here paste the first few lines.

The Payload :

  <?xml version="1.0" encoding="utf-8" ?> 
- <n0:MT_ZSNORECIP xmlns:n0="http://namespace/bi" xmlns:prx="urn:sap.com:proxy:BI7:/1SAI/TASCE0B927E5DA384528654:701:2009/02/10">
- <RECIPES>
- <ITEM>
  <PLANT>2010</PLANT> 
  <ZPRIMMAT>XXXXXXXXXXXX</ZPRIMMAT> 
  <MATERIAL>xxxxxxxxxxxxxxxxxx</MATERIAL> 
  <FISCPER>xxxxxxx</FISCPER> 
  <ZWTDRWQTY>xx.xxx</ZWTDRWQTY> 
  </ITEM>

I have change few identity related things in the payload. Else let me anything else is required.

Regards,

[Gaurav Patwari|http://gauravpatwari.wordpress.com]

[Former Member · Accepted solution]

Hi,

there are many possibilities for the receiver determination error.

1) Configuration mistake

Receiver determination depends upon:

a) Sender business system

b) Sender Interface

c) namespcae under which sender interface is configured in ESR

Check for the values in MONI and compare them with the config (Receiver determination) in ID.

The above values should match in MONI and ID.

So please check each and everything.

2) Cache refresh (please check cache notifications in ID)

3) When the business system not found in SLD.

If all are fine, then please let me know what is the type of receiver determination ur using (standard/extended)???????

[Former Member]

Dear Experts,

Sorry my mistake it was silly mistake was using wrong system having an identical name in the landscape.

No problem got the problem and is now working fine.

Thank you for your time & support.

Regards,

Gaurav Patwari [www.gauravpatwari.wordpress.com]

[Former Member]

Hi Gaurav,

njoy as the problem is solved and thanks for the points...

Thanks,

Shabbir.