Bookshelf Home | Contents | Index | Search | PDF

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

Using Standard Database Extensibility

---

You can use Standard Database Extensibility to implement database extensions that meet various business requirements, without having to resort to Advanced Database Extensibility. For example:

• Many: One Tables

  Requirement: You need to track an entity that does not exist in the Siebel eBusiness Applications Data Model and that bears a Many: One relationship with a Base Table.

  Case 1: The Base Table already has an _XM table associated with it.

  In this case, you can use this table to track multiple entities by using the TYPE column to group records.

  Case 2: The Base Table does not have an _XM table associated with it, but there is another table in the Data Model that bears a Many: One relationship to the Base Table and is not being used in the Siebel implementation.

  In this case, you may repurpose this table for your needs by adding columns to it to track the necessary attributes.

• Intersection Table

  Requirement: You need to implement a Many: Many relationship between two tables (T1 and T2).

  • Look for an existing _XM table for T1 or another table that bears a Many: One relationship to T1 and is not used in the implementation. If such a table exists, you may be able to use it as an Intersection table.
  • If the table identified in step a is an _XM table, use the NAME column as the Foreign Key to the table (T2). You will also need to make the configuration changes necessary to make sure that the TYPE column gets populated with a default value.
  • If the table identified in step a is an unused table, then you will need to choose an appropriate (required) column that can serve as a Foreign Key to the table (T2). You will also need to make the configuration changes necessary to make sure that all other required columns are populated.
• Stand-Alone Table

  Requirement: You need to create a table that is not related to any other tables in the data model; this table does not have to be available through synchronization.

  Case 1: The data exists in an external system or database.

  You should consider using a Virtual Business Component to access this table. This option has the added advantage that there is no need to replicate the data within the Siebel Data Model. For more information about Virtual Business Components, see Integration Platform Technologies: Siebel eBusiness Application Integration Volume II.

  Case 2: The data does not exist in an external system or database.

  You could create the table, possibly in the same database and under the same table owner as the rest of the Siebel Data Model. Though this table is not represented in the Repository, its data can be accessed through the Virtual Business Component mechanism.

Bookshelf Home | Contents | Index | Search | PDF