‎2011 Dec 19 9:46 AM
Hi,
I'm generating automatic payment files via program run SAPFPAYM_SCHEDULE.
The file is generated under UTF-8 but when generated on SAP server become UTF-16.
=> When double clicking on the Z_XML20022 and clicking on glasses you can see "<?xml version="1.0"
encoding="utf-8"?>"
=> When you have a look under AL11
/interfaces_sec/DECCLNT300/FI_payment_SAP032/out/PSAPCIT.PAYMENT_CN10_1. it's <?xml version="1.0"
encoding="utf-16"?>
I need to have utf-8.
Thanks in advance for your help.
‎2011 Dec 19 10:36 AM
Hi,
If you using XSLT, you may use this transformation (based on your XML example, but simplified):
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sap="http://www.sap.com/sapxsl"
xmlns:am="http://www.xxx.com/ActionMessage"
version="1.0">
<xsl:strip-space elements="*"/>
<xsl:output encoding="utf-8"/>
"your rest XML data"
</xsl:transform>
PS: I advise you to read the Note 1017101 - Encoding Problems with ABAP XML Processing, which explains better what I said above.
‎2011 Dec 19 11:14 AM
Hi sum_it2,
Thanks for your reply.
How do I determine or write the rest of the XML data?
‎2012 Sep 19 2:46 PM
Hi Marc,
Is your problem solved, actually i am suffering from the same problem.
Regards,
Kartheek,.
‎2012 Dec 19 9:38 AM
Hello,
We are also facing the same problem.
Did you resolve it ?
Thanks
‎2013 Nov 21 4:58 PM
Please follow the steps in the below link, Add your XML formats in BADI,
http://wiki.scn.sap.com/wiki/display/ERPFI/Common+issue+with+SEPA+File+created+by+PMW+program
‎2014 Jan 06 1:21 PM
Hello
I had the same issue with a SEPA XML file that the bank want in UTF-8 instead of UTF-16.
I was getting the UTF-16 format when dowloading the file from FDTA transaction. But if you see the file on FDTA directly, you see the coding and the format is UTF-8 on the original file. So from this screen where you can actually see the xml file I did menu XML - Download. Then the file is not converted to UTF-16 but remains in his original format UTF-8.
I hope this workarround helps you.
David
‎2014 Nov 04 4:51 PM
Hi,
We had same problem and applied the note 1730272 resolve the issue. hope it will be useful to anyone.
Thanks,
Pradeep