cancel
Showing results for 
Search instead for 
Did you mean: 

Encoding issue and message failing in Integration Engine

Former Member
0 Kudos

Hi Experts,

We are facing an issue with encoding in file to file scenario.

We receive xml files from SAP BI 7.3 system in ANSI format(i am checking the same using Notepad++).

The xml encoding is UTF-16 (<?xml version="1.0" encoding="UTF-16"?>)

The sender channel "FiIe Type" is set to "Binary"

The xml files get picked up from the sender directory and fails in the Integration Engine using the following error:

<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_SAPFinance_BW_2_Clarity_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Content is not allowed in prolog.</SAP:Stack>

But when i change the file manually to "Unicode" (By using "Save As" option in windows notepad --> Encoding "Unicode"

) in my local system and upload the same file to the source directory. Then the message gets successfully processed.

Please let me know if anyone have faced this issue and the fix.

Thanks,

Sudhansu

Accepted Solutions (0)

Answers (2)

Answers (2)

Ryan-Crosby
Active Contributor
0 Kudos

Hi Sudhansu,

It sounds like you are getting files with the BOM (byte order mark) in the prolog of the file.  The easiest way to solve this is to make sure from the sender side these bytes do not exist in the file.  Otherwise you might have to play around with conversions of the file encoding or writing code for a java mapping or adapter module to remove them.

Regards,

Ryan Crosby

stefan_grube
Active Contributor
0 Kudos

When the SAP BI systems stores a file in the file system and you notice that the encoding is not identical to the XML encoding declaratin, then you have to fix this in the SAP BI system.

If the file is downloaded by a standard report, check if there is an setting for this, otherwise create a ticket for SAP.