ICO Scenario - MONI Error

[Former Member]

Hi All,

My scenario is SOAP to File  Asynchronous ICO Scenario.

It is working at ESR Mapping level, but failed in ID Test configuration with error as " Receiver could not be determined".

I have tried below options to resolve this error

1) NWA Setttings  --> Value is 0 for xiadapter.version.minor

2) RFC Destinations

a) SAPSLDAPI

2) LCRSAPRFC

3)SXI_CACHE is up to date.

Please guide me to resolve this error

Thanks in advance,.

Regards,

Jeevitha N

[Former Member]

Hi All,

We are not maintaining any entries for other ICO scenarios also,but Other ICO Scenarios are working fine..

Caches are up dated

Regards,

Jeevitha N

[former_member182412]

Hi Jeevitha,

• For classical scenarios are executed in integration engine of PI ABAP stack, if your global configuration in SXMB_ADM is pointing to Integration engine of PI ABAP stack like below screen shot.

• ICO interfaces are executed in only java stack of the PI so you must maintain the entry in SXMSIF transaction for that particular interface in order to point to adapter engine of PI.
• You don't have entry in SXMSIF that is why based on global configuration the message is going to PI abap stack and it is failing with "Receiver could not be found"

Regards,

Praveen.

[Former Member]

Hi

Thanks  for your valuable input.

I tried the same in classical ,its working fine,

But not working in ICO, its throwing same error "Receiver Determination : No receiver could be determined"

All configuration seems correct.

Pls give me some idea to make it work in ICO also

Regards,

Jeevitha N

[former_member182412]

Hi Jeevitha,

Have you done two steps in ERP??

1) Create sender ID in transaction SXMSIF

2) Maintain IS_URL parameter in SXMB_ADM->Integration Engine Configuration.

Regards,

Praveen.

[former_member186851]

Hello Jeevitha,

check the cache,Seems like an issue with cache.

Also check as Praveen suggested.

[rasjoshi]

Hi,

Did you check cache components in ESR and ID?

BR,

Rashmi

[former_member191435]

Can you please chare your ICO screen shot and Sender soap CC .

[rasjoshi]

I guess you have PI Dual Stack. Please check your ID objects are correctly configured. If so check cache components and perform End to End message flow. Let me know results.

Check points on ECC side -

1. SM59 - Type G (Check path prefix provided for both the Destinations)

2. SXMB_ADM - Provide correct RFC Destination

3. Check SLDAPICUST

4. Check SLD_CHECK

BR,

Rashmi

[former_member183908]

Please try to test end to end integration and see if it works or not.testings on AAE or AEX will available with certain release versions.

cheers

Pawan

[former_member182412]

Hi Jeevitha,

Test configuration in Integration Directory does not work for ICO configuration because Test configuration executes in ABAP stack and ICO configuration is saved and executed in only java stack hence you are getting "No receiver could be determined".

Regards,

Praveen.

[manoj_khavatkopp]

Hi Jeevitha,

This issue is due to incorrect ICO setup done on sender ECC side .

ICO setup in ECC :

1.RFC destination to be created in ECC which points to PI system AE.

2.SXMSIF : new entries to be added for your outbound service interface with namespace.

2.IS_URL parametre to be set in SXMB_ADM.

Please check this with your Basis team.

Regards,

Manoj

[Former Member]

Hi Manoj,

Thanks for your reply..

1st and 3rd steps are in place in SAP ECC System

But I don't see any entries in SXMSIF tcode in both ECC and PI system.

But other outbound and inbound scenarios are working fine,.,.

Regards

Jeevitha N

[manoj_khavatkopp]

Jeevitha,

follow the steps mentioned in the below document :

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef4...

[former_member186851]

Hello Jeevitha,

Are you having any conditions in the Receiver determination?

Check the below link

https://scn.sap.com/thread/2136032

[Former Member]

Hi Raghu,

No conditions in receiver determination..

[manoj_khavatkopp]

Jeevitha,

Are their any other outbound interface with ICO coming from the same source system?

If yes then please cross the check the setup which I mentioned above with existing one.

So being an ICO scenario the source system should target to send message to PI-AE but in your case it is sending to PI-IE. Since the source system is sending message to IE it is trying to search receiver determination(abap stack)  but it can't find because you have ICO here(Java stack).

We would request you to put screenshot of your ICO and screenshot from ECC system for these tcode sm59- ( rfc destination type g ), sxmsif and sxmb_adm.

Br,

Manoj

[former_member186851]

Jeevitha,

Ok. Got it.

you cant test in ID since it is a ICO object. Of course mapping you can check from ESR.

To test the scenario use Run time workbench test message or use soap UI.

[former_member202642]

Hi Jeevitha,

Make entries in ECC system with t-code SXMSIF >> change>> >> New entries.

Then provide sender/receiver ID with party and component as *.

Under message category provide O/B Service interface name and namespace and save the changes.

Regards,

Aamir