Split mapping created.. No message exists

[Former Member]

I see the above error message in Moni with a red flag

Actually, I dont think it really is an error message

becuase I have mapped in such a way that It shouldnt create any messages, if the condition fails.

Mapping:

If del_indicator exists ---> generate delete mapping

if del_indicator not exists ---> generate import mapping

this is the logic I did in Multi mapping.

so obviously delete will not generate if there s no deletion indicator.

the exact error message I see is "Split mapping created no messages"

there are no issues with output. its perfect.

but I still am able to see that error message in MONI

1. how do I control this? and remove the error message from moni?

2. why is it generating a error message?

Regards,

Nikhil.

[Former Member · Accepted solution]

Hi,

Thanks to a BPM, you will be able to manage Fork and Exception...

But about BPM perform, I join you.

Eventually, in your case you will have perhaps another way, but I need to know one point: where is your field "del_indicator" ?

is it a field present in your SOURCE message (so before mapping) ?

Mickael

[Former Member · Accepted solution]

yes,

the delete indicator exists in the source payload of IDOC only if the delete was performed .

Nikhil.

[Former Member · Accepted solution]

...

If yes...so I have a solution for you !

But you will declare TWO Business Services for one receiver system:

.. Receiver_1

.. Receiver_2

you have to do some concessions as you do not want to use a BPM

In your Receiver Determination of ID, just write a condition based on your field "del_indicator".

in order to have something like that:

1. Sender --> Condition "del_indicator = Yes" --> Receiver_1
2. Sender --> Condition "del_indicator = No"  --> Receiver_2

and then in the Interface Determination, you have:

1. Sender --> Mapping_for_delete_flow         --> Receiver_1
2. Sender --> Mapping_for_NON_delete_flow     --> Receiver_2

That means also that in your IR, you have TWO Interface Mappings:

1. Mapping_for_delete_flow     : Source --> Target_for_delete     (occurance 1 -> 1)
2. Mapping_for_NON_delete_flow : Source --> Target_for_NON_delete (occurance 1 -> 1)

Hope this help you.

Mickael

[Former Member · Accepted solution]

Hi Mickael,

I did the same way but same error message.

I am using Interface mapping with 0....unbounded (not 1...1 ) because that mapping I have declared as Multi mapping ( with 0....unbounded occurance with Messages and messages1 as root nodes)

regards,

nikhil.

[Former Member · Accepted solution]

Hi Nikhil,

With your flow, I don't understand the necessity to use a Multi-Mapping...

Else if Multi-mapping is mandatory for your business, I just see BPM like a solution of your problem that we can resume by "Management of Exception".

Block inside BPM => possibility to manage Exception:

http://help.sap.com/saphelp_nw04/helpdata/en/f6/e1283f2bbad036e10000000a114084/content.htm

Exception inside BPM:

http://help.sap.com/saphelp_nw04/helpdata/en/33/4a773f12f14a18e10000000a114084/content.htm

Regards

Mickael

Edited by: Mickael Huchet on Apr 17, 2008 11:43 AM

[Former Member · Accepted solution]

Hi Mickael

how are u doing?

finally i have solved it without BPM usage.

The solutions is : have changed my MM such a way that a dummy message gets created without the contents of the message.

thanks a lot for all your help !

Nikhil.

[Former Member · Accepted solution]

Hi Nikhil,

thanks for this feedback.

see you later

Mickael

[Former Member · Accepted solution]

Hi,

could you explain me how to create this dummy message in MM?

I'm facing the same problem.

In my scenario I'm putting multi files to and external server, when no files are created I see a red flag message in XIP MONI.

I do not want this red flag message to come.

Thanks

Fabio Boni

[Former Member]

hi,

Do you use a BPM ?

if not, you should it. because if i understood your flow you never generate the two flows (delete / not_delete).

Indeed in your Interface Mapping, you say to XI that it should done that:

inbound --> outbound_delete
         --> outbound_no_delete

That means TWO outbound messages has to be created for ONE inbound message. So if one is missing (as it's your case), then XI genereate an error in order to say it to you !

Do I correctly understood your pb ? or not ?

Mickael

[Former Member]

Hi,

thanks for your reply

You did understand the problem.

now that the data is posting properly, wat is the necessity of using BPM?

is there any other way to supress this error message?

I do not want to use BPM in my scenario for performance reason, and thats the reason, i am using extended interface determination to send each of these messages.

Please suggest me how to suppress this message.

thanks and regards,

Nikhil.