Table Type Definitions

The following table provides descriptions of the types of tables in the Siebel database.

Table Type	Description
Data (Intersection)	Data (Intersection) tables contain application or end-user data. An intersection table implements a many-to-many relationship between two data tables. The name of an intersection table is usually composed by concatenating the two table names, abbreviated if needed. For example S_OPTY_POSTN is the intersection table between tables S_OPTY and S_POSTN. Intersection tables cannot be extended using extension tables, but can be extended using extension columns, subject to database restrictions.
Data (Private)	Data (Private) tables contain application administration or system data. Private tables cannot be extended using extension tables or extension columns.
Data (Public)	Data (Public) tables contain application or end-user data. Public data tables can be extended using extension tables and, subject to database restrictions, extension columns.
Database View	Database View objects appear as tables with regular columns. These tables represent database views. Objects of this table type are not created by the ddlimp Siebel database utility. Underlying views are created by SQL scripts during install and upgrade.
Dictionary	S_APP_VER is the only table in this category. This table has only one row and contains information about the application such as major and minor version, application name, unicode flag, and so on. This table contains information about the data dictionary.
Extension	Extension tables implement a one-to-one relationship with a data table to provide additional columns to the data table. These tables are named with an _X suffix and contain generic columns with the ATTRIB_ prefix, which are useful to define customized fields in a business component. These tables can be further extended using extension columns, subject to database restrictions. Note that there are also tables that implement a many-to-one relationship to a data table. Those tables have an _XM suffix and their columns have generic names with the ATTRIB_ prefix. However, they are not considered extension tables. Their type is Data (Public).
Extension (Siebel)	Extension (Siebel) tables also implement a one-to-one relationship with a data table to provide additional columns to the data table. However, these columns are configured in advance in Siebel Business Applications. Do not use extension tables for any other purpose. These tables can be extended using extension columns, subject to database restrictions, but cannot be extended through extension tables.
External	External tables are tables that reside outside the Siebel database. The Siebel object manager provides some support for accessing data in these tables through business components. In Siebel Tools, the Table object type includes properties that support external tables.
Interface	Interface tables are EIM tables, which are used when moving data between the Siebel application and external applications.
Log	Log tables are used to log events. There are three Log tables: S_DCK_INST_LOG, S_PROC_INST, and S_PROC_INST_LOG.
Repository	Repository tables contain information about the Siebel Repository. Data in some of these tables might be compiled into the Runtime Repository.
Virtual Table	Virtual tables represent database tables or data in an operating system file that resides outside the Siebel database. Virtual business components are defined on these tables.
Warehouse	Warehouse tables are used byOracle Business Analytics in theOracle Business Analytics Warehouse table. These tables have names starting with 'W_'.

Note: Tables of the following types: Data(Public), Data(Intersection), Extension(Siebel), and Extension are designed to hold user data. These tables, as well as some of their columns, are occasionally marked as obsolete in the comments whenever they are no longer used by the current version of Siebel Business Applications. The status of the table or column indicates the support that will be provided for it in future versions of the Siebel database schema, see the following table.