Bookshelf Home | Contents | Index | Search | PDF

Siebel Tools Reference > Adding Custom Extensions to the Data Model > Updating the Logical Schema Definition in the Local Environment >

Adding Extension Columns to Tables

---

You can add extension columns to any of the following table types:

Data tables
Intersection tables
Interface tables
Standard extension tables
Custom extension tables
Extension (Siebel)

You should check the Type property for a table to verify that you can extend it:

You cannot add extension columns to private data tables—that is, tables with a Type property of Data (Private).
Some interface tables are private, although most are public.

To add an extension column

Connect to your local development database with Siebel Tools.
In the Object Explorer, expand the Table object type.
In the Object List Editor, select the table to which you will add an extension column or columns.
Make sure that the table is not of type Data (Private).
Select Column in the Object Explorer.
Select Edit > New Record to add an extension column.

NOTE:  Do not use column names that are reserved words on your server or client database.

When you add columns to base tables or interface tables, Siebel Tools enforces the naming conventions described in the section Naming Conventions for Extension Tables and Columns.

You must provide a default value, in the Default property, for any column that you designate as mandatory (with a FALSE value in the Nullable property). Although you can create a mandatory column without providing a default, you will encounter problems when using this column. For example, if you try to add a column to a table that is already populated with data, the database will fail to create the column. If the table does not yet contain data, attempts to add data (through the user interface, Enterprise Integration Manager, or Siebel Remote) may fail.

In an extension column, use only default values for the following properties:

Translate
Use FKey
Sequence Object
Cascade Clear
Foreign Key Table Name

CAUTION:  Be extremely careful when using custom extension columns to track foreign keys. If you choose to implement this, you must consult with Siebel Expert Services concerning the visibility rules applied to the foreign key table. Additionally, you must set the Foreign Key Table Name property to NULL for that column to use the Enterprise Integration Manager to load values into that column.

For information on creating foreign key mappings for EIM, see EIM Table Mapping Wizard.

You are limited to one column of type LONG per table. Each of these columns is limited to 4000 characters maximum. If you attempt to add additional columns of these types, or exceed this length limit, you will receive an error message. In this case, use an extension table.

When adding extension columns to a base table, you need to determine if there are any issues that might appear based upon the type of database you are using. For example, if you exceed the tablespace size on DB2 you will receive an error message.

To create a LONG extension column

Find an appropriate 1:1 extension table that corresponds to the base table that needs the LONG column available.

An example of a 1:1 extension table for S_EVT_ACT, for instance, is S_EVT_ACT_X.

NOTE:  The reason for using a 1:1 Extension Table is you cannot add LONG columns to Siebel base tables like S_EVT_ACT, or S_ORG_EXT_XM, since Siebel Systems reserves the right to implement LONG columns in these tables in the future.

For the column that is created in the table, set the Physical Type to 'Long' and Length set to '0'.

You apply the LONG extension column like any other custom extension column.

Create a new field that maps to the extension column.

Only one LONG column is allowed per table, and it stores a maximum of 16 KB or 16383 characters.

Bookshelf Home | Contents | Index | Search | PDF