Enhanced interface determination - two step message mapping - Split mapping created no messages

[Former Member]

Hello expert,

I use enhanced interface determination in ID for a 1:4 message split mapping, the interface mapping contains two step message mapping, and when test end-to-end,

it will fails at the interface mapping with "Split mapping created no messages". but when it's a one step message mapping, I have no problem with it. Can anyone give an insight on this? below is the details of my scenario:

1: Sender agreement:

File adapter will reads in a plain text file, and converts it into a simple XML file.

2. Receiver detemination.

3. interface detemination:

An interface mapping is used to split the source file into 1-4 message interface and send them to different places.

two step message mapping:

Step 1 message mapping: some cross value mapping using xref table in PI system.

Step 2 message mapping: a 1-4 message splitted mapping, this will split the source XML into 1 to 4 messages base on some condition.

3. Receiver agreement.

I have read many posts in SCN, like http://scn.sap.com/message/5722354. But my source XML does not contains the namespace "http://sap.com/xi/XI/SplitAndMerge" mentioned by lots of the post. and I tried to add a XLST mapping before the 1:4 message mapping start. All these do not solved my problem.

When I use one step message mapping, the end-to-end test will success, but using one step message mapping will complicated the logic of the graphic mapping.

I wonder if there is any difference between one-step and two-step mapping in interface mapping that caused the error? How could I solve this issue?

can you please help? thank you!

The detail error:

- <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="MAPPING">GENERIC</SAP:Code>

<SAP:P1>Split mapping created no messages</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Split mapping created no messages</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

  </SAP:Error>

[Former Member]

Hi Tom,

I already came across that issue, it is not possible to split 1:n messages with 2 steps mapping : you will have to use a ccBPM I am afraid or merge the 2 mappings in one.

Best regards,

Guislain

[Former Member]

thanks Guislain, do you know the possible reasons for this? why are you so sure about this?

[Former Member]

Hi Tom,

I think it is a limitation of the product (I personnaly had the issue on PI 7.11). I have done a whole project where the client wanted to use pivot formats in mappings, so I have developped all the Operation Mappings with 2 mapping steps (source -> pivot and pivot -> target) and it has always worked except that particular case of 1:N.

Best regards,

Guislain

[nabendu_sen]

Hi Tom,

Please check in Monitor if the inbound message has an extra tag similar to this:

<ns0:Messages xmlns:ns0="http://abcd/efgh/SplitAndMerge">

<ns0:Message1>

Remove it and closing tag too and test the scenario once again.

These tags are only added during design time but needs to be removed at runtime.