E1: TC: Table Conversion with Output Format Type "XML" Does Not Use the Flat File Encoding UTF8 that is Set in P93081; The Flat File is Always Created with UTF-16 Encoding
(Doc ID 2928178.1)
Last updated on JULY 22, 2024
Applies to:
JD Edwards EnterpriseOne Tools - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
A custom Table Conversion (TC) is created which outputs a flat file using the format type "XML".
In P93081 - Work With Flat File Encoding application, UTF8 encoding is set up for this custom TC.
However, when the TC is submitted, the output XML file is always encoded in UTF-16.
Steps to Duplicate:
- Create a Table Conversion UBE
On the Table Conversion Properties , Outputs tab
User Defined Format - Type
Format Type : XML - Outputs are in Extensible Markup Language (XML) format
Row Formats: Single Format - All rows have the same format - Run table conversion program on fat client or on server (after package deployment), the XML output flat file is always in UTF-16 encoding although P93081 is set up to be UTF8
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |