Professional Documents
Culture Documents
0 Essentials
1 of 21
Module Objectives
To identify prominent tables in the Siebel database Get to know the various keys and Indexes for the tables.
business implementation
3 of 21
used to store the data used by the Siebel applications Is designed to support the data requirements across Siebel applications
Controls/ List Columns
Screen
View
Applet
Business Object
Business Component
Field
Table
Column
4 of 21
Data in Siebel
Is organized and stored in normalized tables in a relational
database
Each table has multiple columns storing atomic data. Single value cannot be logically further sub-divided
Primary Key is a column that uniquely identifies each row in a
table
ROW_ID serves as the primary key for Siebel tables
Table Primary Key ROW_ID BU_ID NAME
S_ORG_EXT EMAIL_ADDR
Columns
5 of 21
ROW_ID
Is a column in every table that is unique across all tables
Siebel applications
ROW_ID for a particular record
6 of 21
Tables
Data,Interface and Repository are three major types of tables.
S_ORG_EXT
EMAIL_ADDR ROW_ID
EIM_ACCOUNT
MAIN_PH_NUM ROW_ID ROW_ID
S_TABLE
BU_ID
NAME
ALIAS
NAME
NAME
TYPE
LOC
7 of 21
Data Tables
Have names prefixed with S_ Store the user data
Users through the siebel application Server processes such as Assignment Manager, Enterprise Integration Manager (EIM)
Are documented in Siebel Data Reference
8 of 21
Internal Product
9 of 21
Columns
Columns determine the system and user data that can be stored
in the table
Determine the size (Length) and type (Physical Type) of the data that can be stored in column Limit proposed modifications to a standard application Existing properties should not be edited
10 of 21
System Columns
Store the System data. They exist for all tables and are
System Columns
11 of 21
User Keys
Determine the uniqueness of records when importing, integrating or
entering data
Are predefined and cannot be modified All columns in User key may not be Required
Creation of New User Keys will be done by Expert Service Group
12 of 21
Indexes
Used to retrieve and sort data rapidly Separate data structure to store data value for a column
and a pointer to a corresponding row Modifying existing indexes or adding new ones to be done by experienced DBA
_P index based on Primary Key
Position of the column in the index. Sequence affects the sort order
13 of 21
Table Relationships
To support the as-delivered application, Siebel tables have
Employees
S_USER PW_LAST_UPD PASSWORD ROW_ID ROW_ID Siebel Data Model S_ORG_EXT EMAIL_ADDR S_ADDR_ORG ADDR_NAME
Address
ROW_ID
LOGIN
BU_ID
NAME
ADDR
CITY
1:M Relationship
14 of 21
1:M Relationships
On the Many side, Foreign Key columns in the table are
ROW_ID
ROW_ID
OU_ID
BU_ID
NAME
ADDR
CITY
15 of 21
referential integrity and should never be updated directly via SQL. Use the Foreign Key Table property in the column definition to determine the column that serves as the foreign key
S_ADDR_ORG ADDR_NAME
OU_ID
BU_ID
NAME
ADDR
CITY
16 of 21
M:M Relationships
M:M relationships are captured using the foreign keys
S_USER
PW_LAST_UPD PASSWORD ROW_ID ROW_ID Siebel Data Model
S_ORG_EXT EMAIL_ADDR
BU_ID
NAME
Intersection Table
17 of 21
Foreign key for this is located in the Extension table and is known as PAR_ROW_ID A row in an extension table is created only if there is data to store in one of its columns. The ROW_ID for a row in an extension table is same as the ROW_ID of the related row in the base table. This is an exception to the convention that ROW_IDs are unique across all tables
A base and an extension table can be considered as a single logical table.
Provides additional columns for the business components referencing the base table Have the name of the base table with suffix _X Examples of Vanilla 1:1 extension tables: S_CONTACT_X for S_CONTACT,
S_ORG_EXT_X for S_ORG_EXT etc
S_SRV_REQ ASGN_DT
OPTY_ID
ROW_ID
ROW_ID
18 of 21
existing parent table Have the name of the main table suffixed with _XM
Examples of Vanilla 1:M extension tables: S_CONTACT_XM,
S_ORG_EXT_XM
S_SRV_REQ ASGN_DT
S_SRV_REQ_XM
PAR_ROW_ID ATTRIB_01 ROW_ID
OPTY_ID
ROW_ID
NAME
NAME stores the name of the child entity PAR_ROW_ID stores FK to ROW_ID in the main table TYPE defines data classification
TYPE
19 of 21
Module Highlights
Siebel data model defines how the data is stored in the third
party relational database Primary key (ROW_ID) uniquely identifies each row in a table User keys are used to uniquely determine the existence of a row while entering, importing or Integrating data Foreign key columns are maintained by Siebel applications and tasks to ensure the referential integrity. They are used to capture 1:M relationships M:M relationships are captured using foreign key columns in Intersection tables 1:1, 1:M extension tables are prebuilt for many major tables in Siebel database
20 of 21
Lab
In the lab you will:
Examine tables, columns, indexes, and user keys that make up the Siebel Data Model Determine the form of relationships between tables in the Siebel Data Model
21 of 21