IDOC to XML in 4.6c , Error while opening the file. Encoding Missing

[Former Member]

Hi Gurus,

we are working on 4.6c system. we are creating XML file from IDOCs using XML port. But when we try to open the file, we get error

" An invalid character was found in text content. Error processing resource 'file:///C:/ . "

this is because we are having some special character in IDOC contents and encoding is missing in XML file.

if we replace first line of our xml file manually from

( <?xml version = "1.0"?> ) to <?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?> or <?xml version="1.0" encoding="ISO-8859-1" ?>, the file gives no error and opens up correctly.

but we do not want to modify anything manually.

is there any way at R3 side to solve this issue without modifying SAP program. any OSS note? any config?

these files are being picked up by PI. can PI solve this issue while reading the file in PI? if yes then how? I have to answer this to PI team. we have to generate XML file in R3 because we have to provide Filename based on some settings in R3.

thanks

Rajpal Sehrawat

[Former Member]

Hi Gurus,

we are working on 4.6c system. we are creating XML file from IDOCs using XML port. But when we try to open the file, we get error

" An invalid character was found in text content. Error processing resource 'file:///C:/ . "

this is because we are having some special character in IDOC contents and encoding is missing in XML file.

if we replace first line of our xml file manually from

( <?xml version = "1.0"?> ) to <?xml version="1.0" encoding="ISO-8859-1" standalone="yes" ?> or <?xml version="1.0" encoding="ISO-8859-1" ?>, the file gives no error and opens up correctly.

but we do not want to modify anything manually.

is there any way at R3 side to solve this issue without modifying SAP program. any OSS note? any config?

these files are being picked up by PI. can PI solve this issue while reading the file in PI? if yes then how? I have to answer this to PI team. we have to generate XML file in R3 because we have to provide Filename based on some settings in R3.

thanks

Rajpal Sehrawat

[Former Member]

There is little hope it could be fixed....

Please refer OSS Note 928675.

[former_member212005]

Check the below link....it might be helpful. it also contains the solution.

http://www.sapfans.com/forums/viewtopic.php?f=21&t=255838

[Former Member]

There is no solution to it.

Please read it state to modify the file manually after download.

[former_member212005]

Here is what the link says in the end.....

By a brute force scan I found that the encoding is stored in a constant called START_TAG in LEDI7TOP - it was necessary to create a new one and where appropriate TRANSFER that one instead in form OPEN_XML_FILE in LEDI7F04.

[Former Member]

That is helpful thanks......