My Oracle Support Banner

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 MARCH 16, 2023

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information 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:

  1. 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

  2. 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

Changes

 

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.