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 MARCH 02, 2017
Applies to:Siebel CRM - Version 188.8.131.52 [IP2014] and later
Information in this document applies to any platform.
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).
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.
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):
Character '0x0001' cannot be represented in XML(SBL-EAI-00245)
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|