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 >

Creating a Custom Extension Table

---

Siebel eBusiness Applications provide standard extension tables for the major base tables in the schema. Each extension table has standard extension columns that you can use to hold custom data. In some cases, however, you may need to create a custom extension table. Also, you may not have access to create custom extension tables, only extension columns.

If you wish to create 1:1 or 1:M extensions for tables whose type is Extension (Siebel), you must extend from S_PARTY.

For example, S_CONTACT is an extension table of S_PARTY. Because S_CONTACT is of type Extension (Siebel), you cannot use it as a parent table for an extension table. You must use S_PARTY.

For a business component based on your new table to show data from S_CONTACT, you must create a Join object that references S_CONTACT and has a Join Specification child object with a Source Field property set to Parent Id and Destination Column property set to ROW_ID. The row ID of an S_CONTACT record will be the same as the row ID of the corresponding S_PARTY record.

NOTE:  After creating a new table using the Extend button, you will need to restart Siebel Tools if you want to delete any custom table.

To create a custom 1:1 extension table

Connect to your local development database with Siebel Tools.
In the Object Explorer, select the Table object type.
In the Object List Editor, select the base table for which you want to create an extension table. Verify that its Type property has a value of Data (Public).
Click Extend.

The extension table appears in the list of tables in the Object List Editor. The Database Extension Designer will automatically create the necessary standard columns and standard indexes. Temporary columns in interface tables that are imported to the base table for this extension table are also created automatically.

Create any additional extension columns on the custom extension table, following the instructions in the next section.

Custom 1:1 extension tables do not need new docking rules, as the data contained in these tables is implicitly routed according to the docking rules of their parent tables.

NOTE:  In general, you cannot add more than 20 extension tables to a base table. The number of extension tables is also limited by the underlying database capacity. Finally, you should limit the number of extension tables of a single base table for performance reasons.

If for some reason you need more than 20 extension tables on a base table, you must use the Advanced Database Extensibility option. For more information, see Advanced Database Extensibility. You should also consult Siebel Expert Services.

Bookshelf Home | Contents | Index | Search | PDF