Siebel学习笔记

-----------------------------------------------------------------Siebel Notes----------------------------------------------------------------------------

About tables
*Are logical representations in the Siebel repository of the physical tables in the underlying database management system
*Extend the Siebel data model using extension tables and extension columns to base tables but cannot add new base tables, delete base tables and
   columns, or modify the properties of base columns.
*Private data tables are similar to public data tables, but cannot have extension columns
*Public data tables can be extended using extension tables and extension columns
*What is the difference between columns in an extension table and entension columns??(Already known)
*One-to-one extension tables always create a new table based on a certain base table that ends with the suffix_X
*One-to-many extension tables require that you create new fields for the business component of the base table and map them to available 
 columns in the one-to-one extension table
*The implicit join makes the extension table rows available on a 1:1 basis to the business component that uses the extension table.
*Implicit joins allow data to be updated in columns(Unknown)
*Can use 1:M extension tables to track additional entities that have a 1:M relationship with a parent business component but are not represented by
 existing Siebel business components

static extension tables:Oracle provides a set of preconfigured extension tables that are set aside for customer use.
Static extension tables include generic columns (ATTRIB_) that you can use to store custom attributes. Static extension tables are already part of 
the data model, so using them does not require updating the physical database. (From : About Extension Tables)

** One-To-One Extension Tables:Rows in the extension table have one-to-one relationships with corresponding rows in the base table. 
They are basically an extension of the base table record. 

** One-To-Many Extension Tables:One-to-many extension tables require that you create new fields for the business component of the base table and map them to
          available columns in the one-to-one extension table.(Dynamic PickList)
Like 1:1 extension tables, 1:M extension tables have a set of generic columns (ATTRIB_xx) that you can use to store custom attributes. 
1:M extension tables have a Type property value of Data (Public) rather than Extension.
track additional entities that have a 1:M relationship with a parent business component but are not represented by existing Siebel business 
components