ODI 10g Generates Incorrect XML Elements from Unicode SAP IDoc Files
(Doc ID 557142.1)
Last updated on JULY 24, 2024
Applies to:
Oracle Data Integrator - Version 10.1.3.2.0 to 10.1.3.4.2 [Release 10gR3]Information in this document applies to any platform.
Symptoms
Note that the grace period has ended for ODI releases where this issue may occur. It is recommended to upgrade to the latest version possible.
For more information reference: Document 456313.1 Primary Note For Oracle Data Integrator (ODI) and Legacy Sunopsis, Releases and Patches
For more information reference: Document 456313.1 Primary Note For Oracle Data Integrator (ODI) and Legacy Sunopsis, Releases and Patches
NOTE: In the examples below, the names represent a fictitious sample for clarity. Any similarity to actual environments, past or present, is purely coincidental and not intended in any manner.
For UNICODE SAP iDocs, the Oracle Data Integrator (ODI) OdiSAPALEServer tool generates XML files containing incorrect (shifted, truncated) data.
For example, instead of:
CODE_EDITOR: 0110006320 (is correct)
TYPE_EDITOR: TEST_TY
RAISON_SOCIALE: TEST_RAISON
CRAISON_SOCIALE: 2000
the XML generated file may contain:
<CODE_EDITOR> <![CDATA[ 0110006320 ]]> </CODE_EDITOR>
<TYPE_EDITOR> <![CDATA[ TEST_TY ]]> </TYPE_EDITOR>
<RAISON_SOCIALE> <![CDATA[ TEST_RAISON ]]> </RAISON_SOCIALE>
<CRAISON_SOCIALE> <![CDATA[ 2000 ]]> </CRAISON_SOCIALE>
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! |