Siebel Tools Reference > Adding Custom Extensions to the Data Model >

Creating New Tables Using the Table Wizard


The Table Wizard allows you to create new stand-alone tables, extension tables, and intersection tables. It provides picklists with appropriate choices for each type of table and makes sure that the naming conventions are observed. You can only create tables of types: Data (Public), Data (Intersection), and Data (Extension). You must explicitly grant permissions on any table that you create.

To use the Table Wizard

  1. Choose File > New Objects.

    The New Objects dialog box appears.

  2. Select the Table Wizard icon.

    The General dialog box appears.

    Click for full size image
  3. In the "Enter a name for the new Table" field, it is noted that you must enter a new table that starts with "CX_" or it will automatically add a prefix.

    NOTE:  The Table Name must be upper case. Mixed case or lower case names may lead to problems when applying the changes on certain databases.
    If you choose 1:1 extension tables, "_X" is suffixed to the table names.

  4. In the "Choose a Project in which you wish to create the Table" field, choose a project.

    NOTE:  The Project list is restricted only to those projects that have been locked by the developer. All picklists are restricted to objects that belong to projects that are locked.

  5. In the "Select the type of the Table" field, choose from the options: A stand-alone Table, 1:1 Extension Table for an existing Table, M:1 Extension Table for an existing Table, An intersection Table between two existing Tables.
  6. Click Next.

    NOTE:  The next dialog box displayed depends on the type of table that is being added.

    1. If you choose Stand-alone Tables, the Parent Specification Table dialog box is not displayed and you are taken to the Finish dialog box, stating that the new table can now be created.
    2. For 1:1 Extension Tables and M:1 Tables, the Parent Specification Table dialog box allows you to select the parent table. See the following figure:
      Click for full size image
    3. For 1:1 Extension Tables, the picklist of available parent tables is restricted to tables of type Data (Public).
    4. For M:1 Extension Tables, the picklist of available parent tables is restricted to tables of type Data (Public).

      NOTE:  Users can add new columns to S_CONTACT, S_ORG_EXT, S_POSTN, or S_USER, for example (and this is generally preferable to adding new columns to S_PARTY); they cannot create new 1:1 relationships to them.

    5. For Intersection Tables, the dialog box allows you to add both parent tables and names of foreign key columns to the parent tables. See the following figure.
      Click for full size image
    • The picklist for the "Select the first Parent Table" field is restricted to all tables of type Data (Public).
    • The picklist for the "Select the second Parent Table" field is restricted to tables of type Data (Public) with the following added restrictions, based on the choice of the first parent table.
    • The names of the Foreign Key columns ("Enter a Foreign Key Column name for the first Parent Table" field and "Enter a Foreign Key Column name for the second Parent Table" field) are verified to make sure that they are unique (that is, do not conflict with each other or the system column names).
  7. Click Next on the Parent Table Specification dialog box.

    The Finish dialog box appears, which allows you to review the changes made before the objects are actually created. The Finish dialog box verifies that "The new Table can now be created" and asks you to make sure that the information about the Name, Project, Type of Table, and Parent Table 1 is correct.

  8. Click Finish to generate the table.

    You then see the new table listed (User Name CX_X) in the Object List Editor (the Type is Extension, the Base Table is CX).

Table Wizard Actions

The following columns are generated by the Table Wizard.

NOTE:  When a custom extension table is added using the Table Wizard, a U1 index is added to the table. However, the User Key column is blank and does not allow the definition of user keys. This is because there is no need to create user keys: they are only needed to resolve foreign keys while using EIM, and EIM does not work with foreign keys to custom tables.


 Siebel Tools Reference
 Published: 20 October 2003