Siebel Connector for Oracle Applications > Developer Procedures >

Unicode to Codepage Deployments

The following section provides special procedures and guidelines for Siebel Connector for Oracle Applications deployments in which one application is operating in a Unicode environment while another application is operating in a codepage environment. One of the main issues to consider is that complete character conversion may not be possible if you are using applications with different character set encodings (such as Unicode UTF-16 and a codepage).

CAUTION:  Failure to properly address potential character conversion shortcomings may result in data corruption.

Consider the following example:

In this situation, you may not be able to convert non-Western European language data from Siebel Business Applications 8.0 (UTF-16) to the Oracle application (1252). This limitation occurs because:

• Non-Western European languages such as Japanese, Korean, and Chinese (Simplified and Traditional) require multibyte data representation and the Western European (1252) codepage can only represent data in single-bytes.
• Non-Western European language data in Unicode UTF-16 may not have equivalent characters in the Western European (1252) codepage.

NOTE:  The reverse case of this example is also true. For example, you have similar conversion issues when Siebel Business Applications 8.0 is operating in a codepage environment and the Oracle Application operates in a Unicode environment.