No messages created from split mapping

[Former Member]

Hello,

My Scenario is JDBC to Proxy and there is 1:n Mapping

I had done the multi mapping and done the all the necessary configuration in the MM, IM and ID

I tested the payload in the MM and IM and it is working fine.

But while iam doing the end to end testing in the ID --- Test Configuration,It is showing the error at Interface Determinmation and Mapping step.

In SXMB moni, iam getting error as

- <!-- Request Message Mapping

-->

- <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>No messages created from split mapping</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>No messages created from split mapping</SAP:Stack>

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

</SAP:Error>

The below is my source payload.

<?xml version="1.0" encoding="utf-8" ?>

- <ns:mt_vendor_fusiondb xmlns:ns="http://loreal.com/poc_vendor">

- <row>

<ID>1</ID>

<LIFNR />

<NAME1>SriTest</NAME1>

<PSTLZ>07066</PSTLZ>

<LAND1>USA</LAND1>

<TELF1>1234567890</TELF1>

<Status>READY</Status>

<LastUpdated>2008-11-20 09:20:00.0</LastUpdated>

</row>

- <row>

<ID>2</ID>

<LIFNR />

<NAME1>GilderTest</NAME1>

<PSTLZ>07066</PSTLZ>

<LAND1>USA</LAND1>

<TELF1>1234567890</TELF1>

<Status>READY</Status>

<LastUpdated>2008-11-20 09:20:00.0</LastUpdated>

</row>

- <row>

<ID>3</ID>

<LIFNR />

<NAME1>KarthikTest</NAME1>

<PSTLZ>07066</PSTLZ>

<LAND1>USA</LAND1>

<TELF1>1234567890</TELF1>

<Status>READY</Status>

<LastUpdated>2008-11-20 09:20:00.0</LastUpdated>

</row>

</ns:mt_vendor_fusiondb>

Please help me in resolving this error

Srinivas

[Former Member · Accepted solution]

Hi Sirinivas,

Did you set your ocurrence parameter of target Message to 0..unbounded in both

your Message Mapping and Interface Mapping?

Carlos

[Former Member · Accepted solution]

Yes

[Former Member · Accepted solution]

Hi,

Let fme ind out a little bit more about your scenario...

Could you post both structures (XSD), your source structure and target structure in your Message

Mapping?

Carlos

[Former Member · Accepted solution]

Hi Carlos,

Now my message mapping is working, the error is in the messagetype i declared 'row' as capital letters,due to this in the runtime it is erroring out in the request message mapping.

But still I had one more issue,iam getting error in Technical routing, the error is

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Technical Routing

-->

- <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="OUTBINDING">CO_TXT_MMF_ENGINETYPE</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Messages in multi message format can be sent to one adapter engine only</SAP:Stack>

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

</SAP:Error>

In the ID i checked the radio button extended.

But still iam getting the above error.Can you guide me in resolving the error

[Former Member · Accepted solution]

Hi,

the question is, are your using routing rules in your receiver determination and each receiver use a

communication channel located in different adapter engines?

Carlos

[Former Member · Accepted solution]

the question is, are your using routing rules in your receiver determination and each receiver use a 
communication channel located in different adapter engines?

No,there is only one receiver in my scenario

Srinivas

[Former Member · Accepted solution]

HI Srinivas

1:N will not work for Server proxy. You need to use BPM for this. Creating IDOC is one of the solution as stated above. You need to create IDOC with repeating segment to handle this data.

When you do 1:N mapping the target message is Messages -> Message1 and it comes under namespace SplitandMerge. That is not recognized by R/3 as the proxy is not generated for this namespace.

Thanks

Gaurav

[Former Member]

Thanks for all your answers,

Thanks

Srinivas

[vrkrishnaraju_mudunuri]

Hi Srinivas,

1:N mapping can't be done using server proxies as the XI adapter and IDOC adapter resides on IE.

This can be achived only through BPM, but the performance issue comes into the picture if we use BPM.

So, create an custom inbound IDOC and solve your case.

If you try to post the data using proxies using loop in the code, it will be difficult to handle the ERRORS.

So, go for the custom IDOC.

Regards,

Krishnraju