Bookshelf Home | Contents | Index | Search | PDF

Siebel Connector for Oracle Applications > Developer Procedures > Unicode to Codepage Deployments >

Deployment Scenarios

---

The following scenarios describe integration possibilities between Siebel eBusiness Applications 7.5 and Oracle Applications R10.7 and R11i. Some guidelines that apply to both scenarios are:

While the Siebel Object Manager always operates in a Unicode environment, the Siebel database can operate in either a Unicode (for example, UTF-16) or non-Unicode (for example, codepage) environment.
Character conversion occurs in two places:
Where data moves from the Siebel Database to the Siebel Connector for Oracle Applications on the Siebel Object Manager.
Where data moves from the Siebel Connector for Oracle Applications on the Siebel Object Manager to the Oracle Application.

Integrating with Oracle Applications R10.7

Table 15 describes integrating Siebel eBusiness Applications 7.5 with Oracle Applications R10.7.

Table 15. Integrating with Oracle Applications R10.7

Siebel Database	Siebel Object Manager	Oracle Application
Codepage	Unicode	Codepage
Unicode	Unicode	Codepage

Oracle Applications R10.7 support only codepage execution (National Language System (NLS)) and do not support Unicode (Multi-Language System (MLS)). Although you can configure Oracle Applications to manipulate data encoded in multiple codepages through field engineering work, the Siebel Connector for Oracle Applications does not support exchanging data with this type of field configuration.

Integrating with Oracle Applications R11i

Table 16 describes integrating Siebel eBusiness Applications 7.5 with Oracle Applications R11i.

Table 16. Integrating with Oracle Applications R11i

Siebel Database	Siebel Object Manager	Oracle Application
Codepage	Unicode	Codepage
Unicode	Unicode	Codepage
Codepage	Unicode	Unicode
Unicode	Unicode	Unicode

Bookshelf Home | Contents | Index | Search | PDF