Bookshelf Home | Contents | Index | Search | PDF |
Siebel Tools Reference > Data Objects Layer > Tables >
Properties of the Table Object Type
The following are the key properties in a table object definition:
- Name. Provides the name of the table in the DBMS.
- Type. Indicates which of the following styles describes the table.
- Data (Public). Public data tables are among the original set of tables implemented in Siebel applications. They hold data that is made available through business components to developers and users. Public data tables can be extended using extension tables and extension columns. These extension are subject to database restrictions.
Data tables are discussed in Data Tables.
- Data (Private). Private data tables are similar to public data tables, but cannot have extension columns.
- Data (Intersection). Identifies an intersection table. An intersection table implements a many-to-many relationship between two data tables.
Intersection tables are discussed in Intersection Tables.
- Extension. An extension table adds additional columns to a data table that the original data table is unable to hold due to DBMS platform or Siebel application design restrictions. Extension table names have an _X suffix, or _XM or one-to-many, or _T for TAS extension tables.
NOTE: Extension tables that have _XM suffix have table type of "Data (Public)."
Extension tables are discussed in Extension Tables.
- Interface. Interface tables are used by Siebel Enterprise Integration Manager (EIM) to import initial data for populating one or more base tables and subsequently to perform periodic batch updates between Siebel applications and other enterprise applications. Interface table names end in _IF or _XMIF.
Interface tables are discussed in Column Objects.
- Database View, Dictionary, Journal, Log, Repository, Virtual Table, and Warehouse styles. These are all table types that are reserved for Siebel internal use.
- Extension (Siebel). These tables are reserved for Siebel use only. They are usually extensions from S_PARTY. If customers want to extend person- and organization-related tables they need to extend from S_PARTY.
For example, S_CONTACT is an extension table of S_PARTY. Because S_CONTACT is of type Extension (Siebel), you cannot use it as a parent table for an extension table. You must use S_PARTY.
For a business component based on your new table to show data from S_CONTACT, you must create a Join object that references S_CONTACT and has a Join Specification child object with a Source Field property set to Parent Id and Destination Column property set to ROW_ID. The row ID of an S_CONTACT record will be the same as the row ID of the corresponding S_PARTY record.
- Base Table. Identifies the base table if the table in the object definition is an extension table. If the table in the object definition is a base table, this property is blank. An extension table always identifies a base table.
- User Name. A longer, descriptive name that aids in identifying the table when used in configuration.
- Alias. A name that can be used as a synonym for the table name to make the name more understandable. For example, an alias such as S_Organization_External could be specified for the S_ORG_EXT table.
Bookshelf Home | Contents | Index | Search | PDF |
Siebel Tools Reference Published: 20 October 2003 |