Configuring Siebel Business Applications > Configuring Tables > Manipulating Shapes and Lines in an Entity Relationship Designer >

Applying a Custom Table to the Local Database

After you customize a table you must apply your customizations to the local database. Note that Siebel CRM does not support a custom database trigger. If you create a custom trigger on a Siebel base table, then you must disable it before you update the logical database schema. You must redefine the trigger after you finish the update.

This topic describes how to apply a custom table to the local database for databases other than DB2 for z/OS. If you use DB2 for z/OS, then see Implementing Siebel Business Applications on DB2 for z/OS.

To apply a custom table to the local database

  1. In the Object Explorer, click Table.
  2. In the Tables list, locate the table that includes your customization.
  3. In the Tables list, click Apply/DDL.

    Note that Siebel Tools disables the Apply/DDL button for tables whose Type property is External. For more information, see Overview: Siebel Enterprise Application Integration.

  4. In the Choose Option dialog box, do one of the following:
    • Choose the Apply option, and then click OK.
    • For z/OS

      As an option, you can choose Generate DDL to create a DDL file instead of applying the customization.

  5. In the Warning dialog box, click OK.
  6. In the Apply Schema dialog box, complete the fields using values from the following table.


    Choose one of the following options:

    • All. Update the local database to reflect all changes Siebel Tools makes to the dictionary. If you choose this option, then Siebel Tools compares each database object with the data dictionary and updates the dictionary, if necessary.
    • Current Query. Update the local database to reflect modifications Siebel Tools makes to the tables in the current query only.
    • Current Row. Update the local database to reflect modifications Siebel Tools makes to the table in the current row only.

    Table space

    Leave each of these fields empty. These fields are specific to DB2 for z/OS.

    16K table space

    32K table space

    Index space

    Storage control file

    Optional. The DBA provides this file. It is specific to your database.

    Database user

    Enter your database user ID, which is typically SIEBEL. Siebel Tools reads the table owner from the configuration file for Siebel Tools.

    Database user password

    Enter your user password for the local database. For example, SADMIN.

    Because the password is case sensitive, all characters of the password must be in uppercase. For example, assume the remote user JSMITH initialized the local database and used DB2 as the password. If the user applies a schema change to the local database, then the user must use SIEBEL as the Privileged User Id and DB2 as the Password.

    When Siebel CRM initializes the local database for a remote client, Siebel CRM changes the table owner password from SIEBEL to the password of the remote user. In this situation, use the password of the remote user in the password field.

    ODBC data source

    Verify that the ODBC connection in the ODBC Data Source text box is correct for your environment.

    You cannot apply a schema change to any database other than the database to which you are currently connected. You cannot define the ODBC name of a different database.

  7. Click Apply.

    Your custom extension table and columns are now available to use in your configuration.

  8. (Optional) To activate a customization on an Enterprise Integration Manager table, choose the appropriate table, and then click Activate.
  9. Test the customization.
Configuring Siebel Business Applications Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.