SOAP Error in HCI PI Content is not allowed in trailing section

[hsonnenahalli]

Dear Experts-

I have created a SOAP to SOAP scenario in HCI-PI. In which am receiving the data from SAP through consumer proxy and posting it to some web service. I have tested my mapping and it is all working fine, but when triggered from SAP am receiving the following error in HCI PI

"com.sap.xi.mapping.camel.XiMappingException: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Content is not allowed in trailing section., cause: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 738; Content is not allowed in trailing section."

I have tested the mapping stand alone in HCI PI with the same payload which I am receiving from SAP and it is executing all fine. I have checked my payload in W3 XML validators and no errors found. I have tried to find hidden characters using note pad++ encoding and show symbol features and nothing was found. Please find my XML payload below. I am not sure if there are any payload swap beans or module configuration available to handle this kind of exception in HCI PI.

It would be really appreciated if any valuable inputs are provided.

Regards

HS

<nm:Z_FM_1865_DDC_RECEIPT xmlns:nm="urn:sap-com:document:sap:rfc:functions" xmlns:prx="urn:sap.com:proxy:ECD:/1SAI/TAS8DE6A6C4D1486DC9A1A7:731"> <ZECC_DDC_RECEIPT> <ZZLOAD>610014</ZZLOAD> <COMMDID>1</COMMDID> <COMMDNAME>Cream</COMMDNAME> <CHECKINDATE>2016-09-08</CHECKINDATE> <CHECKINTIME>06:48:56</CHECKINTIME> <RECPTDATE>2016-09-08</RECPTDATE> <RECPTTIME>06:51:03</RECPTTIME> <APPTDATE/> <APPTTIME>00:00:00</APPTTIME> <CHECKOUTDATE>2016-09-08</CHECKOUTDATE> <CHECKOUTTIME>06:51:59</CHECKOUTTIME> <MILK_TYPE_S/> <USNAME>ST</USNAME> <EBELN>4501159579</EBELN> <READYSETTLE/> <LOCID>514</LOCID> <LOSEMNGE>49680</LOSEMNGE> <LLIEF/> <BUTTERFAT> 44.2000</BUTTERFAT> <SOLIDSNONFAT> 5.0000</SOLIDSNONFAT> <ID>0</ID> <NAME/> </ZECC_DDC_RECEIPT> </nm:Z_FM_1865_DDC_RECEIPT>

[hsonnenahalli]

m:Z_FM_1865_DDC_RECEIPT xmlns:nm="urn:sap-com:document:sap:rfc:functions" xmlns:prx="urn:sap.com:proxy:ECD:/1SAI/TAS8DE6A6C4D1486DC9A1A7:731"> <ZECC_DDC_RECEIPT> <ZZLOAD>610014</ZZLOAD> <COMMDID>1</COMMDID> <COMMDNAME>Cream</COMMDNAME> <CHECKINDATE>2016-09-08</CHECKINDATE> <CHECKINTIME>06:48:56</CHECKINTIME> <RECPTDATE>2016-09-08</RECPTDATE> <RECPTTIME>06:51:03</RECPTTIME> <APPTDATE/> <APPTTIME>00:00:00</APPTTIME> <CHECKOUTDATE>2016-09-08</CHECKOUTDATE> <CHECKOUTTIME>06:51:59</CHECKOUTTIME> <MILK_TYPE_S/> <USNAME>ST</USNAME> <EBELN>4501159579</EBELN> <READYSETTLE/> <LOCID>514</LOCID> <LOSEMNGE>49680</LOSEMNGE> <LLIEF/> <BUTTERFAT> 44.2000</BUTTERFAT> <SOLIDSNONFAT> 5.0000</SOLIDSNONFAT> <ID>0</ID> <NAME/> </ZECC_DDC_RECEIPT> </nm:Z_FM_1865_DDC_RECEIPT>

[hsonnenahalli · Accepted solution]

Issue is resolved. The above mentioned error was happening because I was using genral splitter to get a MPL while processing the data. Once the general splitter was removed everything is working as expected.