cancel
Showing results for 
Search instead for 
Did you mean: 

Message is going to wrong MI and NS

Former Member
0 Kudos

My interface is Proxy-SOAP.

My receiver MI and NS is wrongly shown for few executed messages as....

Recevier MI: InterfaceCollection

Receiver NS : http://sap.com/xi/XI/System

Actually they are not my actual MI and NS.

There is Bulk message ticket in green for these specific messages.

I dont see any messages in Queues...

What is http://sap.com/xi/XI/System?

Why does my mesage is going to this?

PS:

I am using Multi mapping and Enchanced ID

in my ID, I checked check box"maintain order at runtime" but still the QOS I see for these messages is EO ( I dont think this is an issue coz for mesages showing correct MI and NS, also shows QOS as EO)

Thanks,

Venkat.

Accepted Solutions (1)

Accepted Solutions (1)

prateek
Active Contributor
0 Kudos

I am using Multi mapping and Enchanced ID

Thats why you are getting the interface name as InterfaceCollection.

Are you facing some problem in end to end scenario?

Regards,

Prateek

Former Member
0 Kudos

Thanks for your replies,

The functionality seems to be working...

If that is the URL for multi mapping, why is it not showing for all the messages?

For few messages it shows up as Interface collection and for few messages it shows up as original Interfaces

@ Mark - the MM was succesful with test payload and did generate target nodes.

why is it showing for only few messages?

Regards,

Venkat.

markangelo_dihiansan
Active Contributor
0 Kudos

Hi,

That is the default namespace until the proper interface has been identified. I'm not sure why some messages are in green status. Maybe the data that was sent is too large or that you may have added steps such as database insert, etc

Regards,

Former Member
0 Kudos

Mark,

All messages were shown with a checkered flag and for InterfaceCollection messages there is Green color ticket mark in the coloumn for Bulk message.

I am not using any Select queries.

It is a Proxy - SOAP scenario.

One more question Mark,

What do you mean by the NS is default NS for Multi message mapping and Enhanced ID?

if we use Multi MM and Ehnaced ID, does the source messages placed into that NS or does the target messages placed into that?

Please explain more,

Thanks for your help.

Venkat..

markangelo_dihiansan
Active Contributor
0 Kudos

Hi,

First, open your multi-mapping, then click the src button, you will see something similar to this:

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/XI/SplitAndMerge" targetNamespace="http://sap.com/xi/XI/SplitAndMerge">

I'm not really sure about the processes, but in interface collection, the target namespace is the one that is specified as http://sap.com/xi/XI/. Then after the enhanced interface determination has been identified, only then will the system return the correct receiver namespace.

The green flag shows that the message is recorded for outbound processing. Is your scenario IDOC to GUSI/XCBL? If yes, you can search your message using DOCNUM in IDX5.

What does the trace in SXI_MONITOR show?

Regards,

Edited by: Mark Dihiansan on Feb 26, 2009 1:33 PM

Former Member
0 Kudos

Mark,

It is something like this...

in your Multi MM rule, if more than one target messages are generated, then it will send to that NS and InterfaceCollection MI.

On the other hand, if none or one message gets generated, it processes directly to the receiver NS and MI mentioned..

Prateek was close but I wish he would have elaborated it furthrur

anyways, I spent some time in researching n pretty useful to me.

Thanks for your help...

Prateek, thanks to you as well.

Venkat.

Answers (1)

Answers (1)

markangelo_dihiansan
Active Contributor
0 Kudos

Hi,

Would you be able to test the message that has green flag to your mapping in IR? I guess the conditions that were set in your enhanced interface determination were not met.

The http://sap.com/xi/XI/System is the default namespace when you do multi-mapping (Enhanced Interface Determination)

Hope this helps,

Edited by: Mark Dihiansan on Feb 26, 2009 12:57 PM