Siebel Tools Reference > Adding Custom Extensions to the Data Model > Database Extension Planning and Design >

Naming Conventions for Extension Tables and Columns


The Database Extension Designer enforces a naming convention for extension tables and columns to prevent naming conflicts and make sure that you can upgrade your application.

Extension Table Names

The table name for an extension table comprises the name of the base table, an underscore, and a suffix. The "X" suffix denotes a one-to-one (1:1) extension table; the suffix "XM" denotes a one-to-many (1:M) extension table. For example:

NOTE:  Custom extension tables have a prefix of CX_. This prefix is used to distinguish custom tables that have been created from tables provided by your Siebel application. Prefix CX_ is used to distinguish custom tables from all Siebel tables, not just Siebel Extension tables.

The user name of an extension table (in the User Name property) comprises the user name of the base table, a space, and a suffix. The suffix Extension denotes a 1:1 extension table; the suffixes M:1 Extension or 1:M Extension denote a many-to-one or one-to-many extension table. For example:

Extension Column Names

The column name for an extension column in a base table consists of a prefix, an underscore, and a column name. For example:

The user column name for an extension column in a base table uses a column name and a suffix. For example:

NOTE:  The Database Extension Designer imposes no naming convention on extension columns in an extension table. Be careful not to use database reserved words.

There are eight predefined system columns added to a Customized Extension table you create. However, as part of the standard Siebel application, there are 47 predefined data columns of varying types in standard extension tables.


 Siebel Tools Reference, Version 7.5, Rev. A 
 Published: 18 April 2003