Developing and Deploying Siebel eBusiness Applications > Configuring the House and Opportunity Entities > Configuring the House Detail View >

Extending the Database by Adding New Columns to the Base Table

You add columns to a base table using the Database Extension Designer. This involves adding columns to the base table using the Object List Editor in Siebel Tools and then applying the changes your local database schema.

Adding New Columns to the Products Table

First you must add the columns to the base table. You do this by creating additional Column object definitions for the base table object. For example, you are adding columns to the products table, S_PROD_INT.

To add a new column to a base table

  1. In the Object Explorer, expand the Table object type.
  2. In the Tables window, Find and select S_PROD_INT.
  3. Lock the project locally by choosing Tools > Lock Project.

    4. NOTE:  The project field is read-only for tables. You cannot change the project to from Newtable to NREC Configuration.

    Notice that the table is of type Data (Public). Only public tables can be extended.

  4. In the Object Explorer, select Column object type (child of table).

    5. The names of the columns for the S_PROD_INT table appear in the Object List Editor.

  5. In the Columns window, add the following records.

    6. Name
    Physical Type
    Length
    X_ADDRESS
    Varchar
    30
    X_BATHROOMS
    Varchar
    30
    X_BEDROOMS
    Varchar
    30
    X_CITY
    Varchar
    30
    X_PRICE
    Varchar
    30
    X_STATE
    Varchar
    30
    X_SQFT
    Varchar
    30
    X_ZIP_CODE
    Varchar
    30

    NOTE:  Names of extension columns begin with X_ (for example, X_ADDRESS). The User Names of extension columns end with Ext (for example, X_ADDRESS Ext). Siebel Tools automatically enforces these conventions.

    The logical database schema is changed based on the information you entered, but you still need to physically apply the changes to your local database.

Applying Schema Changes to Your Local Database

After you have added columns to the base table as described in the previous section, you have to physically apply the schema changes to your local database.

To apply schema changes to the local database

  1. In the Object Explorer, select the Table object type.
  2. In the Tables window, select S_PROD_INT.
  3. Click the Apply button.

    4. A warning appears saying that you are connected to a local database and asking if you want to continue.

  4. Click OK.

    5. The Apply Schema dialog box appears.

    Click for full size image

  5. In the Tables pick list, select Current Row.

    6. This will update the database to reflect the schema change to the current selected row only (S_PROD_INT).

    Other options are:

  6. Enter the password for the Siebel database owner in the Password text box.

    7. NOTE:  The default password is SIEBEL.

    Do not specify a table space or index space.

  7. Verify that the ODBC (Open DataBase Connectivity) connection specified in the ODBC Data Source text box is correct for your environment.

    8. NOTE:  You cannot apply schema changes to any database other than the one to which you are currently connected. If you are connected to the Sample database, be sure that the OBDC Data Source points to the correct driver. For example, if your Sample database is installed in your client directory on the D drive, the connect string is SEAW Samp Db D:/sea702/client.

  8. Click Apply to apply the new columns to the physical schema on your local database.

    9. After this process has been completed, the columns you added to the logical schema as described in Extending the Database by Adding New Columns to the Base Table now physically exist on your local database and are available to use in your configuration.

NOTE:  Typically, after you have tested changes in the local database environment, you would need to apply these changes to the server database. Checking in a project copies configuration changes to the server, but this process does not apply physical database extension changes. Therefore, you would need to go through a separate process to apply database extension changes to the server database. For information on this process, see Siebel Tools Reference.


 Developing and Deploying Siebel eBusiness Applications 
 Published: 18 April 2003