Character '0x....' cannot be represented ... in XML conversion error for BC field value populated in the Siebel UI (Doc ID 2063786.1)

Last updated on JUNE 08, 2023

Applies to:

Symptoms

FUNCTIONALITY:
-----------------------
Siebel EAI XML Converter used convert to Siebel XML text as SiebelMessage (Siebel Integration Object Instance) instatiated to provide data of the accordantBusiness Object / Business Component (result of the EAI Siebel Adapter Query).

ISSUE:
----------
Conversion fails because of non Unicode/UTF-8 compliant character (such as 0x0001) pulled via Integration Component field value via accordant Business Component field.
 where this character.
However apparently Siebel UI permits entering and storying non Unicode/UTF-16 character in the BC field. via applet's UI control.

IMPACT:
----------
Production data are impacted: data fields with incorrect characters cannot be passed to Siebel EAI interfaces

ERRORs reported by EAI XML Converter (example for the character: 0x01):

Cause

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